Microsoft’s latest security update for Windows 11 has triggered an unexpected problem affecting enterprise users: PCs equipped with Secure Launch are unable to shut down or hibernate properly.
Instead of powering off, affected devices restart automatically, disrupting workflows and forcing users to work around the issue until a fix arrives.
Secure Launch Devices Face Shutdown Failures
The issue stems from KB5073455, the January 13, 2026, security update for Windows 11, version 23H2.
Microsoft confirmed the problem on January 15, 2026, acknowledging that computers with Secure Launch enabled cannot complete shutdown or hibernation sequences.
Secure Launch is a virtualization-based security feature that protects systems from firmware-level threats during startup, making it a critical component in enterprise and IoT environments where advanced threat protection is essential.
Only the Enterprise and IoT editions of Windows 11, version 23H2, are affected, as KB5073455 was offered exclusively to these platforms.
The unexpected restart behavior poses risks for data loss and power management, particularly for mobile devices that rely on hibernation to preserve battery life during extended periods away from power sources.
Microsoft has issued a temporary workaround for shutdown failures, but acknowledges no current solution exists for hibernation.
Users can force a proper shutdown by opening Command Prompt (typing “cmd” in the Search bar) and executing the command:Â shutdown /s /t 0. This command initiates an immediate shutdown sequence that bypasses the restart loop.
However, the lack of a hibernation workaround leaves users vulnerable to unexpected power depletion.
Microsoft strongly recommends saving all work frequently and shutting down devices completely when finished to prevent data loss from batteries running out during what should be hibernation.
The company has committed to releasing a resolution in a future update, but has not provided a specific timeline.
Enterprise IT administrators managing large Windows 11 deployments should consider delaying the installation of KB5073455 until the fix arrives, balancing the security benefits of patching against operational disruptions caused by the shutdown bug.
Follow us on Google News, LinkedIn, and X to Get Instant Updates and Set GBH as a Preferred Source in Google.
