| Previous | Next |
| STATUS_DRIVER_PROCESS_TERMINATED | STATUS_SYSTEM_DEVICE_NOT_FOUND |
STATUS_AMBIGUOUS_SYSTEM_DEVICE
The identification criteria do not select one unique device instance
STATUS_AMBIGUOUS_SYSTEM_DEVICE indicates that device identification produced multiple indistinguishable candidates. Windows device matching uses identification strings such as device instance IDs, hardware IDs and compatible IDs. Those identifiers have different scopes and matching roles; a broad hardware ID can legitimately be shared by many devices of the same model.
The status therefore calls for better identity data, not a random choice among matching devices. If code needs one physical instance, preserve the instance path and topology context used to locate it. If policy intentionally targets a device class or model family, multiple matches may be expected and the API should be used at the appropriate scope.
What to inspect
- The exact identifier or criteria supplied by the failing component.
- Every matching device instance, including parent/child topology and present/nonpresent state.
- Whether a hardware ID was incorrectly treated as a globally unique device instance identifier.
- Custom hardware or compatible IDs added through INF processing or platform device definitions.
Do not resolve ambiguity by taking the first enumeration result; enumeration order is not a stable identity contract. Narrow the request using identifiers documented for the intended device or explicitly handle a set of matching devices.
References
- Microsoft: Device identification strings
- Microsoft: Hardware IDs
- Microsoft: Custom hardware and compatible IDs
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.