Microsoft has officially acknowledged a significant shutdown issue affecting users of Windows 11, specifically those operating on the Enterprise and IoT editions. This bug, linked to the January 13, 2026 security update (KB5073455) for Windows 11 version 23H2, prevents affected systems from shutting down properly. Instead of powering off, devices either hibernate or restart when users attempt the standard shutdown procedure.
What’s causing the Windows 11 shutdown bug
The root of the shutdown dilemma lies in the System Guard Secure Launch feature, a virtualization-based security measure designed to safeguard against firmware-level threats during the boot process. Notably, this issue does not impact Windows 11 Home and Pro editions; it is confined to enterprise-level setups.
“After installing the January 13, 2026 Windows security update (KB5073455) for Windows 11, version 23H2, some PCs with Secure Launch are unable to shut down or enter hibernation. Instead, the device restarts.”
Temporary workaround for Windows 11 shutdown bug
In response to the inconvenience, Microsoft has provided a temporary workaround. Affected users can execute a command in an elevated Command Prompt to force a proper shutdown. The command to be entered is:
shutdown /s /t 0
This command initiates a shutdown sequence similar to turning off the device using the power switch, bypassing any prompts to save work. Users are advised to ensure all work is saved prior to executing this command. Unfortunately, those relying on hibernation functionality do not have a workaround available at this time. Microsoft has recommended avoiding hibernation altogether until a permanent solution is implemented, as the current issue poses a risk of battery depletion in portable devices.
Looking forward
Security experts suggest that the bug may stem from an issue during the ACPI power-state transition, where the system misinterprets the shutdown command as a restart signal. Microsoft has confirmed that it is “actively working on a resolution” for this shutdown bug and anticipates a fix in a “future update,” although no specific timeline has been provided. In the meantime, enterprise IT administrators are encouraged to consider pausing the deployment of KB5073455 on unaffected devices to mitigate the need for administrative Command Prompt access among users.
