| Previous | Next |
| STATUS_DLL_MIGHT_BE_INCOMPATIBLE | STATUS_CANNOT_GRANT_REQUESTED_OPLOCK |
STATUS_STOPPED_ON_SYMLINK
The caller reached a symlink boundary intentionally or by protocol rule
STATUS_STOPPED_ON_SYMLINK means that an open/create operation reached a symbolic link and stopped there. It is not equivalent to an unresolved link: the important fact is that traversal did not proceed. This can be the intended behavior for code that validates path boundaries or works with the link object itself.
Remote file protocols can expose this boundary to the client rather than following an intermediate symbolic link on the server's behalf. A robust client therefore needs to distinguish “the server stopped at a link” from “the link target does not exist.”
Handle the boundary explicitly
- Record whether the link was an intermediate or final path component.
- Retrieve and validate the link/reparse data before constructing a follow-up name.
- Apply containment and authorization checks to the target before continuing.
- Do not turn this into an automatic follow operation when the original request deliberately prohibited traversal.
References
Looking for a different code? Search another status or error code.