| Previous | Next |
| STATUS_DEVICE_ALREADY_ATTACHED | STATUS_OBJECT_PATH_NOT_FOUND |
STATUS_OBJECT_PATH_INVALID
A path component cannot act as a container
STATUS_OBJECT_PATH_INVALID identifies an invalid intermediate component during object-path resolution. The path may contain a name that exists, but the resolver cannot continue through it as required. This is a type or namespace-structure problem, not simply an absent final file name.
For file paths, the important distinction is which component failed. The final object may never have been examined because an earlier component did not represent a directory-like container. For native object names, the same principle applies to Object Manager namespace objects.
Make the failing component visible
- Log the original name and the resolved prefix, not only the last segment.
- Check whether a configuration value replaced a directory component with a file or device object.
- Record directory-only or non-directory open options that set the expected type.
- Compare with
STATUS_OBJECT_PATH_NOT_FOUND: that status points to an absent component, while this one points to a structurally unusable component.
References
Looking for a different code? Search another status or error code.