| Previous | Next |
| ERROR_CORE_DRIVER_PACKAGE_NOT_FOUND | ERROR_FAIL_REBOOT_INITIATED |
ERROR_FAIL_REBOOT_REQUIRED
The failed operation requires a reboot for rollback.
ERROR_FAIL_REBOOT_REQUIRED is Win32 error 3017 (0xBC9). Unlike 3010, the requested action did not succeed. Some changes were made before failure, and the system requires a reboot to complete rollback or restore a coherent previous state. Immediate repetition can collide with pending recovery.
How rollback becomes boot-dependent
- files or drivers changed before failure remain loaded or locked
- the servicing engine scheduled reverse operations that can run only during startup
- a partial device or service update cannot be safely unwound in the current session
- a chained installation fails after one package committed temporary system changes
- rollback itself reaches a resource that is in use and defers completion to reboot
Failure and rollback evidence
Preserve the primary failure that occurred before 3017, package/action identifiers, transaction and rollback log, changed resources, pending reboot markers, maintenance policy, and whether dependent applications are still running. The 3017 code describes required recovery; it is not the original root cause.
Diagnostic sequence
Stop deployment retries and read the producing installer or servicing log backward to the first substantive error. Determine what committed before failure and what rollback work is pending. Check disk space, service/driver state, and package cache needed for recovery.
Plan reboot before assessing final product state. Pre-reboot file or registration checks can show a deliberate transient mixture and should not be used to launch repair automatically.
Recovery procedure
Reboot in a controlled window, then verify that rollback completed and the prior version is operational. Only after the system reaches a stable state should the original defect be corrected and installation attempted again.
Deployment systems should mark the node failed-recovery-pending, block conflicting changes, and retain resume diagnostics across boot. Cluster or fleet automation must avoid moving workload back until rollback health checks pass.
Difference from successful reboot-required result
ERROR_SUCCESS_REBOOT_REQUIRED means the requested change succeeded and awaits activation. Error 3017 means the change failed and reboot is needed to complete rollback to the earlier state.
Example
A driver upgrade copies files, then fails while updating device configuration. Rollback cannot replace the loaded driver and returns 3017. The operator reboots, confirms the old driver is restored, fixes the package issue, and only then retries.
References
- Microsoft: System Error Codes (1700–3999)
- Microsoft: Win32 Error Codes in MS-ERREF
- Microsoft: Windows Installer error codes
- Microsoft: Windows Installer system reboots
Looking for a different code? Search another status or error code.