| Previous | Next |
| ERROR_WMI_SERVER_UNAVAILABLE | ERROR_WMI_INVALID_MOF |
ERROR_WMI_DP_FAILED
Routing succeeded; provider execution did not
Unlike a missing-provider status, this result means that WMI selected a data provider but the provider could not carry out the requested operation. The root cause is therefore usually in the provider's own query, collection, method, or state-change path rather than GUID discovery alone.
In a driver provider, the failure may surface while completing a WMI IRP or while a callback interprets a WNODE buffer. In a user-mode provider, it can arise while the provider obtains the backing device or service data. The precise provider-specific status and event-log entry are more useful than retrying an operation whose prerequisites are still absent.
Evidence to capture
- Log the request kind, block GUID, instance selector, provider version, and underlying status returned by the provider.
- Check that output buffers and input data match the registered MOF layout and required alignment.
- Separate an execution failure from malformed registration, an unknown item, and a transient service outage before selecting remediation.
References
- Windows WDK: WmiSystemControl callbacks
- Windows WDK: WNODE buffer contracts
- Windows WDK: diagnosing WMI provider failures
Looking for a different code? Search another status or error code.