| Previous | Next |
| STATUS_DS_SENSITIVE_GROUP_VIOLATION | STATUS_JOURNAL_ENTRY_DELETED |
STATUS_PNP_RESTART_ENUMERATION
STATUS_PNP_RESTART_ENUMERATION is a topology-change result: a device disappeared while Plug and Play was enumerating the bus, so the current pass can no longer be trusted. It is not evidence that the removed device needs a different driver package.
The useful boundary is the parent bus and the exact devnode that vanished. A previously collected hardware ID, resource list, or child-device path can be stale after the restart. Let the PnP manager rebuild the affected branch before interpreting later driver-selection or resource-assignment failures.
Evidence that separates the cause
- Record the parent bus, device instance path, container identity, and time of the removal or surprise-removal event.
- Read the matching section of
SetupAPI.dev.logto see whether a new child was identified after the restart. - For a driver, discard cached raw or translated resource data from the previous enumeration pass and wait for a new start sequence.
References
- MS-ERREF: NTSTATUS values
- Microsoft: identifying a newly discovered device
- Microsoft: SetupAPI device-installation log
Looking for a different code? Search another status or error code.