| Previous | Next |
| ERROR_DHCP_ADDRESS_CONFLICT | ERROR_WMI_INSTANCE_NOT_FOUND |
ERROR_WMI_GUID_NOT_FOUND
A block lookup failed before an instance was selected
Kernel-mode WMI identifies a data or event block with a GUID. This status says that the provider handling the request does not currently expose that block. It is therefore different from an unknown CIM class in a user-mode namespace and different from an unknown instance: the request did not get as far as selecting a particular device or data record.
For a WDM provider, the GUID must be present in the registration data returned for the device, and a request tagged for another provider must be forwarded down the device stack rather than answered locally. A stale consumer request can also target a block that was removed during a registration update or device-removal transition.
Checks that identify the mismatch
- Compare the request GUID with the
WMIREGGUIDentries returned by the provider for the same device object. - Confirm that the request is handled only when
ProviderIdmatches the device object registered with WMI. - Trace registration, update, and deregistration events; do not treat a missing GUID as evidence that the requested instance data is corrupt.
References
- Windows WDK: Handling WMI requests
- Windows WDK: changing a single WMI data item
- Windows WDK: WMI registration information
Looking for a different code? Search another status or error code.