| Previous | Next |
| STATUS_SYSTEM_IMAGE_BAD_SIGNATURE | STATUS_POWER_STATE_INVALID |
STATUS_PNP_REBOOT_REQUIRED
The Plug and Play operation requires a restart to complete
STATUS_PNP_REBOOT_REQUIRED is a lifecycle result, not evidence that the newly installed driver is corrupt. Plug and Play reached a change that cannot be activated safely in the current boot, so the requested device state must be completed after restart.
What to record
- Identify the device instance, driver package, installation or update operation, and the PnP request that returned the status.
- Preserve SetupAPI/PnP events showing whether an older driver or device stack remained in use, a pending replacement exists, or another component requested the reboot.
- Distinguish this result from a device-start failure after reboot. A later
Problem Codeor driver load status is a separate condition.
Correct handling
Finish the current installation transaction, report the restart requirement to the caller, and reboot through the supported system lifecycle when policy permits. Installers should not repeatedly unload devices or rewrite driver state merely to avoid the restart.
After reboot, verify the expected driver version, device state, and absence of a new PnP error. If the device still cannot start, diagnose that post-reboot result rather than continuing to label it STATUS_PNP_REBOOT_REQUIRED.
Official references
Looking for a different code? Search another status or error code.
