| Previous | Next |
| STATUS_UNSUCCESSFUL | STATUS_INVALID_INFO_CLASS |
STATUS_NOT_IMPLEMENTED
The request reached a provider, but the requested operation has no implementation
STATUS_NOT_IMPLEMENTED is most useful when interpreted at the boundary that returned it. The status does not say that Windows as a whole lacks the feature. It says the component handling this particular request has no implementation for the requested operation or code path. A network redirector, file-system provider, filter, or compatibility layer can therefore return it while another provider supports an analogous operation.
Microsoft documents a practical distinction between this status and STATUS_NOT_SUPPORTED in the RDBSS mini-redirector contract. MRxCreate uses STATUS_NOT_IMPLEMENTED for features such as remote boot or a remote page file that the mini-redirector has not implemented, while STATUS_NOT_SUPPORTED is used for unsupported features such as extended attributes. The distinction is provider-specific but important: blindly translating both to a single capability failure can hide which layer needs work.
When diagnosing the status, capture the exact function, information class, FSCTL/IOCTL, provider, and target object. For a locally owned driver, find the dispatch branch that returns the code and determine whether the feature is intentionally absent or the implementation stub is still reachable. For an application, use a fallback only when the API or protocol defines one; retrying the identical request does not create an implementation.
What to inspect
- Identify the component that actually returned the NTSTATUS, not just the top-level API that exposed it.
- Compare the requested operation with the provider's documented capability and version requirements.
- Do not treat the status as transient unless another contract explicitly says the implementation can appear later.
References
- Microsoft: MRxCreate return values
- Microsoft: FltSetSecurityObject return values
- Microsoft Open Specifications: file-system product behavior
- Microsoft: Using NTSTATUS values
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.