| Previous | Next |
| ERROR_WMI_TRY_AGAIN | ERROR_WMI_UNRESOLVED_INSTANCE_REF |
ERROR_WMI_DP_NOT_FOUND
The routing target is absent
ERROR_WMI_DP_NOT_FOUND concerns the WMI data provider selected for a data block. It is more specific than a general service outage: the request cannot be routed to a provider that has registered the required block for the requested target. A provider may be missing because its driver has not registered, its namespace registration is incomplete, or the relevant device stack is no longer present.
For kernel WMI, registration data ties block GUIDs and instance rules to a provider device object. For user-mode providers, WMI must know the provider registration and supported classes. Repairing a repository or restarting a service without confirming the missing registration can hide the actual deployment or device-lifecycle problem.
What to verify
- Verify that the provider is registered before clients issue requests and that the correct device or namespace is targeted.
- Check that the intended GUID or class is advertised by the installed version, not only by a development build.
- Correlate provider load, driver start, PnP removal, and registration failures in the WMI provider logs and System event log.
References
- Windows WDK: provider registration information
- Windows WMI SDK: registering a provider
- Windows WDK: WMI provider troubleshooting
Looking for a different code? Search another status or error code.