| Previous | Next |
| STATUS_CONTEXT_STOWED_EXCEPTION | STATUS_DIRECTORY_IS_A_REPARSE_POINT |
STATUS_REPARSE_POINT_NOT_RESOLVED
The initial path was valid, but traversal could not finish
STATUS_REPARSE_POINT_NOT_RESOLVED is more precise than a generic path-not-found result. Resolution reached a symbolic-link reparse point successfully, then failed while trying to resolve its target. The issue can lie in the target name, a later namespace component, the availability of the target volume, or a policy that prevents traversal.
Diagnose both sides of the link. Checking only the text of the original path misses the state introduced by the reparse target, while checking only the target loses the fact that a reparse boundary was involved.
Useful checks
- Read the reparse metadata from the link object and identify its tag and target form.
- Verify whether the target is absolute or relative to the link's location.
- Check target-volume availability, mount state, and any namespace or security boundary that applies after traversal.
- Distinguish this result from
STATUS_STOPPED_ON_SYMLINK, where traversal was intentionally stopped.
References
Looking for a different code? Search another status or error code.