| Previous | Next |
| ERROR_REPARSE_TAG_MISMATCH | ERROR_APP_DATA_NOT_FOUND |
ERROR_REPARSE_POINT_ENCOUNTERED
Path traversal encountered a reparse point instead of the expected ordinary object
Some APIs or low-level open options deliberately stop when a reparse point is encountered rather than transparently following it. The result allows security-sensitive, backup, migration, and file-system tools to inspect the reparse object or reject namespace redirection. It does not imply that the point is malformed.
Determine whether following reparse points is appropriate for the operation. A backup tool may preserve the reparse stream; a deletion tool may need to remove the link rather than its target; a security boundary may refuse name-surrogate traversal altogether. Record the component and tag at which resolution stopped, then open with explicit flags and privileges suited to inspecting or handling that specific point.
What to inspect
- Identify the path component that contains the reparse point.
- Choose explicitly between following, preserving, or rejecting it.
- Protect against target substitution between validation and open.
References
- Microsoft: reparse points
- Microsoft: reparse point operations
- Microsoft: reparse point tags
- Microsoft: REPARSE_DATA_BUFFER
Looking for a different code? Search another status or error code.