| Previous | Next |
| ERROR_CAPAUTHZ_SCCD_NO_CAPABILITY_MATCH | ERROR_PNP_QUERY_REMOVE_RELATED_DEVICE_TIMEOUT |
ERROR_PNP_QUERY_REMOVE_DEVICE_TIMEOUT
A device stack stalled while Windows was asking whether removal was safe
Before an orderly removal, disable, or some driver-update operations, the PnP manager sends IRP_MN_QUERY_REMOVE_DEVICE from the top of the device stack downward. Every PnP driver must decide whether removal can proceed and pass the request through the stack. This error points to the query phase itself taking too long, so Windows could not obtain a timely answer from the target stack.
The useful distinction is between a veto and a hang. A normal veto is an explicit failure because the device is still needed; a timeout suggests that a driver did not complete or forward the PnP request promptly. Inspect the stack for pending PnP callbacks, outstanding remove locks, and long-running work executed synchronously from DispatchPnP. A reboot may complete the administrative operation, but it does not explain which layer delayed the query.
What to inspect
- Capture the device instance and full driver stack before rebooting.
- Check PnP and driver framework traces for the pending query-remove request.
- For driver code, verify that DispatchPnP forwards or completes the IRP on every path.
References
- Microsoft: IRP_MN_QUERY_REMOVE_DEVICE
- Microsoft: handling query-remove
- Microsoft: when PnP remove IRPs are issued
Looking for a different code? Search another status or error code.