| Previous | Next |
| STATUS_DEVICE_UNRESPONSIVE | STATUS_ATTRIBUTE_NOT_PRESENT |
STATUS_REPARSE_POINT_ENCOUNTERED
Lookup reached a reparse boundary
STATUS_REPARSE_POINT_ENCOUNTERED reports that Object Manager lookup encountered a reparse point while retrieving an object. The result is useful because it records the point at which normal name lookup stopped; it is not proof that the reparse data is invalid or that the target is unavailable.
Callers that need to inspect filesystem topology, validate a namespace boundary, or avoid following untrusted redirects can treat this as a meaningful control point. A caller that intended ordinary traversal needs to ensure that its open options and the responsible reparse handler permit the next step.
Use the status to preserve context
- Keep the unresolved path, resolved prefix, and reparse tag together.
- State explicitly whether following the point was allowed for this operation.
- Do not diagnose it as a missing-file condition until target resolution has actually been attempted.
- Separate it from
STATUS_NOT_A_REPARSE_POINT, which says no reparse metadata was present.
References
Looking for a different code? Search another status or error code.