| Previous | Next |
| ERROR_INSTALL_REMOTE_DISALLOWED | ERROR_PATCH_TARGET_NOT_FOUND |
ERROR_SUCCESS_REBOOT_INITIATED
The operation succeeded and a reboot has already been initiated.
ERROR_SUCCESS_REBOOT_INITIATED is Win32 result 1641 (0x669). Despite the ERROR_ prefix, this is a successful outcome with disruptive follow-up already in progress. The installation or servicing action completed and Windows has begun restarting so changes can take effect. Automation must not classify 1641 as a failed deployment or immediately launch another installer process.
Why installers return 1641
- the package or bootstrapper explicitly forced an immediate restart
- files, services, drivers, or system components could not be finalized while Windows remained running
- installer restart policy allowed Windows Installer to initiate reboot automatically
- a chained setup propagated a child package’s initiated-reboot result
- servicing reached a successful commit point that requires boot-time completion
Deployment evidence
Record package identity, action and version, msiexec command, reboot-control properties and switches, timestamp, initiating process, user/session context, and the final log lines before 1641. Persist deployment state before starting installation because network reporting may be interrupted as soon as reboot begins.
Correct interpretation
Mark the install phase successful but the overall workflow pending post-reboot verification. Stop starting dependent packages, flush logs, and allow the reboot to proceed. On the next boot, validate product registration, service and driver state, pending rollback, and any resume marker owned by the deployment system.
Differentiate 1641 from 3010 (ERROR_SUCCESS_REBOOT_REQUIRED), which reports success but leaves reboot scheduling to the caller or user. A policy designed for 3010 may be too late for 1641 because shutdown has already been initiated.
Design recommendations
Enterprise installers should avoid unexpected immediate restarts and let the orchestration layer control maintenance windows when possible. Use documented /norestart, /promptrestart, or package properties according to product requirements. Make installation and resume steps idempotent, and never interpret the absence of a final client acknowledgment as automatic failure after 1641.
Success code, not a generic reboot error
Error 1641 indicates that the requested operation succeeded. Reporting it as failure can trigger rollback, duplicate deployment, or incident alerts during normal reboot. It is also different from ERROR_RESTART_APPLICATION, which asks only for a new application process.
Example
A driver package installs correctly and msiexec initiates reboot, returning 1641 to the management agent. The agent stores “installed, reboot in progress” before launch and verifies the driver after startup. A naive agent that retries immediately could start a second transaction during shutdown.
References
- Microsoft: Windows Installer error codes
- Microsoft: Windows Installer system reboots
- Microsoft: msiexec restart options
Looking for a different code? Search another status or error code.