| Previous | Next |
| STATUS_NOT_A_REPARSE_POINT | STATUS_IO_REPARSE_TAG_MISMATCH |
STATUS_IO_REPARSE_TAG_INVALID
The tag does not identify a valid reparse format here
STATUS_IO_REPARSE_TAG_INVALID concerns the identifier attached to reparse data. The tag selects the owner and interpretation of the data buffer; it is not a free-form application label. A tag that is malformed, inappropriate for the operation, or inconsistent with the expected reparse-buffer form can be rejected before the file system can process the payload.
Windows distinguishes Microsoft-owned tags from non-Microsoft tags that use a GUID-associated buffer form. That distinction affects how the data is represented and which component is expected to understand it. The hexadecimal tag, not only the symbolic status, is essential evidence.
Useful evidence
- Log the tag value, buffer length, operation, and whether the caller expected a GUID-based or Microsoft-tagged format.
- Validate that the tag is appropriate for the file-system driver and the target volume.
- Compare the complete serialized buffer with the structure required by that tag; do not infer validity from a target path string alone.
- Keep tag validation separate from a tag mismatch on an existing reparse point.
References
Looking for a different code? Search another status or error code.