| Previous | Next |
| ERROR_DLL_INIT_FAILED | ERROR_NO_SHUTDOWN_IN_PROGRESS |
ERROR_SHUTDOWN_IN_PROGRESS
A system shutdown is in progress.
ERROR_SHUTDOWN_IN_PROGRESS is Win32 error 1115 (0x45B). It tells the caller that the target computer already has an active shutdown or restart sequence, so Windows will not start another independent shutdown request.
Operations that can encounter it
InitiateSystemShutdown,InitiateSystemShutdownEx, orInitiateShutdownis called while another request is pending- an orchestration service sends duplicate restart commands after losing an acknowledgement
- two management products independently attempt to reboot the same server during maintenance
- a local agent races with a remote administrator or Windows servicing component
The code describes system state, not necessarily a failed shutdown. The first request can still be counting down, waiting for applications, recording shutdown information, or transitioning into restart. Treating 1115 as proof that the machine ignored every shutdown request can lead to repeated commands and confusing audit trails.
Evidence worth recording
- target computer name and whether the call was local or remote
- requested action, timeout, force-apps-closed flag, planned/unplanned reason code, and user-visible message
- caller identity and whether the shutdown privileges were successfully enabled
- correlation ID of the earlier request, if the management system tracks one
- timestamps from the initiating service, Windows System log, servicing logs, and any cluster or hypervisor controller
Capture GetLastError() immediately after the API returns failure. A management service should log 1115 together with its own request identifier and the intended restart reason so operators can distinguish a harmless duplicate from an unexpected shutdown initiated elsewhere.
Safe response
Do not issue a tight retry loop. First observe whether the existing shutdown completes and whether the host becomes unreachable or restarts as expected. If the prior request is intentionally being replaced, use the supported abort operation only while the shutdown remains abortable, then verify that cancellation succeeded before submitting a new request.
For clustered or remotely managed systems, coordinate ownership of reboot decisions. A single controller should serialize restart requests, persist their state, and reconcile after reconnect. Idempotent orchestration can classify 1115 as “already in progress” while continuing to monitor the original operation rather than marking the node immediately failed.
When escalation is appropriate
- the machine remains available far beyond the configured countdown and no application prompt is visible
- the shutdown repeatedly enters and leaves a pending state without completing
- the initiator cannot be identified in operational logs
- a critical service or driver blocks the transition and the host cannot be maintained safely
In those cases collect shutdown-related events, process or service hang data, and any pending servicing state before forcing power loss. A forced reset can convert a coordination problem into filesystem, database, or update corruption.
Related code
ERROR_NO_SHUTDOWN_IN_PROGRESS is the opposite state and is normally returned when software tries to cancel a shutdown that is no longer pending. Error 1115 appears when initiating another shutdown, whereas access-denied errors indicate that the caller lacks the required privilege.
Example
A deployment controller sends a restart command, loses its network response, and retries after five seconds. The second InitiateSystemShutdownEx call returns 1115 because the original 60-second countdown is active. The controller should attach the retry to the first operation and wait for the host boot identifier to change instead of sending additional restarts.
References
- Microsoft: System Error Codes (1000–1299)
- Microsoft: InitiateSystemShutdownEx function
- Microsoft: System shutdown functions
Looking for a different code? Search another status or error code.