| Previous | Next |
| STATUS_NO_SUCH_DEVICE | STATUS_INVALID_DEVICE_REQUEST |
STATUS_NO_SUCH_FILE
The final file was absent after lookup reached the file-system location
STATUS_NO_SUCH_FILE is a file-system absence result. It is narrower than an invalid object name and different from a missing intermediate path component: the request reached the relevant file-system location, but the named file was not present there.
The same status can be misleading when a reparse point, mount point, or redirector changed the location that was actually checked. A diagnostic that logs only the caller's input path may send investigation to the wrong volume or server.
Confirm the resolved target
- Record the creation disposition and whether the caller expected an existing file or was allowed to create one.
- Log the final resolved path/volume after reparse and mount-point processing where possible.
- Compare with
STATUS_OBJECT_PATH_NOT_FOUNDandSTATUS_REPARSE_POINT_NOT_RESOLVED; both fail earlier in resolution. - On a remote file system, verify the server-side namespace and any case, stream, or share semantics relevant to the request.
References
Looking for a different code? Search another status or error code.