| Previous | Next |
| STATUS_IO_REPARSE_TAG_INVALID | STATUS_IO_REPARSE_DATA_INVALID |
STATUS_IO_REPARSE_TAG_MISMATCH
The target has reparse data, but not of the requested kind
STATUS_IO_REPARSE_TAG_MISMATCH means that the object's existing reparse tag and the tag expected by the current operation are different. This is more specific than “invalid tag”: the target can contain valid reparse data, but it belongs to another handler or represents another kind of reparse object.
That distinction prevents a dangerous repair pattern. Replacing or deleting existing reparse data simply because an application expected a different tag can damage a junction, cloud placeholder, filter-driver object, or other component's metadata.
How to diagnose safely
- Read and record the existing tag before attempting any update or removal.
- Identify which component owns the stored tag and whether the caller is authorized to modify it.
- Confirm that the handle addresses the reparse object itself, not a path reached after traversal.
- Use a tag-specific migration path when changing object semantics; do not overwrite opaque data with a different format.
References
Looking for a different code? Search another status or error code.