What does Windows error code 636 (ERROR_PNP_RESTART_ENUMERATION) mean?

 
Previous Next
ERROR_COMMITMENT_MINIMUM ERROR_SYSTEM_IMAGE_BAD_SIGNATURE

ERROR_PNP_RESTART_ENUMERATION

The bus topology changed while Plug and Play was enumerating devices

Bus drivers report child devices through BusRelations. The PnP manager can query those relations while a bus is active, and a driver can invalidate the relation set when a child arrives or departs. This status indicates that a removal changed the topology enough that the current enumeration pass is no longer a reliable snapshot.

Restarting enumeration is a consistency action, not a hardware-error diagnosis by itself. The important debugging question is why the child set changed during the operation and whether the bus driver reports stable PDO identity for devices that remain present. A hot-plug event can legitimately force a new pass; repeated loops can point to flapping hardware, unstable connection state, or a bus driver that alternates its BusRelations response. Compare consecutive relation sets and the IDs returned for each child.

What to inspect

  • Compare BusRelations results before and after the restart request.
  • Check for repeated arrival/removal notifications from the same physical port.
  • Verify surviving children keep stable device and instance identifiers.

References


Looking for a different code? Search another status or error code.