| Previous | Next |
| STATUS_IO_REPARSE_TAG_MISMATCH | STATUS_IO_REPARSE_TAG_NOT_HANDLED |
STATUS_IO_REPARSE_DATA_INVALID
The failure is in structured metadata, not necessarily the target path
STATUS_IO_REPARSE_DATA_INVALID indicates that the supplied reparse data cannot be accepted for its tag or operation. Reparse buffers contain a tag, a declared data length, and tag-dependent fields. A path-looking substring may be present while the overall buffer is still invalid because offsets, lengths, flags, or the selected structure do not agree.
This result should be diagnosed at the serialization boundary. It is not enough to log a human-readable target name after the buffer has already been constructed; the lengths and byte layout are part of the contract.
What to capture
- The tag, total buffer size, declared reparse-data length, and operation code.
- The structure variant selected by the caller and its offset/length fields.
- A bounded hexadecimal dump of the buffer, with sensitive path data handled according to the application's logging policy.
- The existing object's tag, if the operation was intended to replace or update metadata.
References
Looking for a different code? Search another status or error code.