| Previous | Next |
| STATUS_RETRY | STATUS_ALLOCATE_BUCKET |
STATUS_FOUND_OUT_OF_SCOPE
The object exists; the lookup context cannot legally return it
STATUS_FOUND_OUT_OF_SCOPE is a particularly useful identity result because it distinguishes “not found” from “found elsewhere.” The Windows status text says an object matching by ID was located on the volume but outside the scope of the handle used for the operation. Repeating the same lookup with the same scope is therefore unlikely to change the result.
Windows file identity APIs make scope explicit. OpenFileById takes a volume handle plus a file identifier, while distributed link tracking uses NTFS object identifiers to follow files and directories. A handle that represents a directory, namespace boundary, redirected view, or another constrained context can impose rules narrower than volume-wide identity.
Log the object ID, volume, scope handle type, and requested root or namespace before retrying. Confirm that the handle was opened for the intended volume and that a stale rename or move did not put the object outside the caller’s allowed subtree. Do not treat the status as proof of deleted data: the definition specifically says the ID matched an object on the volume.
What to inspect
- Record the matched object ID and volume identity.
- Describe the scope handle: volume, directory, namespace, or protocol context.
- Check recent moves/renames before attempting recovery or recreating the object.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Distributed link tracking and object identifiers
- Microsoft: FILE_ID_INFO
- Microsoft: OpenFileById
- Microsoft: FSCTL_CREATE_OR_GET_OBJECT_ID
Looking for a different code? Search another status or error code.