| Previous | Next |
| STATUS_IO_REPARSE_DATA_INVALID | STATUS_PWD_TOO_LONG |
STATUS_IO_REPARSE_TAG_NOT_HANDLED
A reparse handler was required but did not claim the tag
STATUS_IO_REPARSE_TAG_NOT_HANDLED says that the layered file-system path needed a component to process a particular reparse tag, but no suitable handler did so. The tag may be valid in another environment; the immediate issue is that this I/O stack could not interpret it at the point where processing was required.
This makes the status different from malformed data. A correct buffer can still be unusable if the responsible filter, driver, redirector, or file system is not present, does not support the tag, or declines the operation.
What narrows the cause
- Record the exact reparse tag and the volume/file-system type.
- Determine whether the operation ran locally, through a redirector, or through a virtualized file system.
- Collect the active filter and driver context from the system where the failure occurs.
- Do not rewrite the tag data as a first response; first establish which layer is expected to own it.
References
Looking for a different code? Search another status or error code.