| Previous | Next |
| ERROR_PNP_QUERY_REMOVE_DEVICE_TIMEOUT | ERROR_PNP_QUERY_REMOVE_UNRELATED_DEVICE_TIMEOUT |
ERROR_PNP_QUERY_REMOVE_RELATED_DEVICE_TIMEOUT
A related device prevented a coordinated query-remove operation from finishing
PnP removal can involve more than the device named by the caller. The PnP manager also coordinates children and removal relations so that devices which depend on one another are not torn down in an unsafe order. This status means the timeout occurred in the stack of a related device rather than the primary target.
Do not restrict investigation to the device that the user disabled, ejected, or updated. Determine the target device's parent, children, and removal relations, then inspect the related stack that was queried as part of the same operation. A bus, filter, storage path component, or companion function can be the layer that never finished its PnP processing. The distinction from the base query-remove timeout is diagnostic: the initiating device may be responsive while a relationship edge expands the operation to another stalled stack.
What to inspect
- Map the devnode tree and removal relations for the original target.
- Identify which related stack still has a pending PnP request.
- Check whether a child or companion driver is waiting for I/O owned by the target stack.
References
- Microsoft: handling query-remove
- Microsoft: IRP_MN_QUERY_DEVICE_RELATIONS
- Microsoft: when PnP remove IRPs are issued
Looking for a different code? Search another status or error code.