| Previous | Next |
| STATUS_DISK_CORRUPT_ERROR | STATUS_OBJECT_NAME_NOT_FOUND |
STATUS_OBJECT_NAME_INVALID
The failure occurs before a final-object lookup
STATUS_OBJECT_NAME_INVALID means that the supplied object name is invalid for Object Manager resolution. It is different from STATUS_OBJECT_NAME_NOT_FOUND: the latter describes a valid lookup that reached the final component and did not find it, while this status indicates that the name itself cannot be used as supplied.
Native APIs can resolve more than ordinary file paths. A malformed object name can therefore involve an invalid prefix, separator, relative-name context, or name construction error rather than a missing file on disk.
What to inspect
- Log the exact native object name after conversion and normalization, with sensitive segments redacted as needed.
- Record whether
RootDirectorysupplied the base for a relative name. - Verify that path conversion did not mix Win32, UNC, device, and native namespace forms incorrectly.
- Keep this separate from access checks and file-system existence checks; neither has necessarily occurred yet.
References
Looking for a different code? Search another status or error code.