Secure Launch is keeping PCs awake. I explain why the latest patch broke the ‘Off’ switch and how to force a shutdown via CMD.
Microsoft released cumulative updates for Windows last week on the January 2026 Patch Day and fixed a critical security issue that is exploited in the wild.
Yesterday, Microsoft acknowledged that some Windows 11 devices are unable to power down after installing the KB5073455 security update.
When users try to shut down or hibernate affected machines, the devices simply restart instead.
Overview: The Secure Launch Shutdown Bug
Who is affected?
- Operating system: Windows 11, version 23H2.
- Target audience: Mostly Enterprise and IoT editions, as Home and Pro editions are no longer support. The Enterprise editions of Windows 11, version 23H2 will reach end of servicing this November.
- Specific hardware: The bug is triggered only on devices with Secure Launch (System Guard Secure Launch) enabled.
Most home users and small to medium-sized businesses should not be affected by the issue.
The workaround
While Microsoft is fixing the underlying issue, it has published a workaround to fix the issue on affected systems.
Users who want to shut down the computer may run the following command from the command prompt: shutdown /s /t 0
Here are the steps:
- Open the Start menu.
- Type cmd.
- Launch the Command Prompt from the search results by selecting it.
- Paste shutdown /s /t 0 and press the Enter-key to execute.
Microsoft notes that it has no workaround currently for entering hibernation. The company recommends that users save all work regularly to avoid that work is lost when devices run out of power.
Windows and its Shut Down bugs: a trip down memory lane
Windows had a fair share of shut down related bugs over the years. The most notorious is a bug that plagued Windows users for nearly a decade before Microsoft finally fixed it in late 2025.
When users selected the update and shut down option from the Start menu, Windows would instead restart the system and load the login screen again. PCs would remain turned on until the user recognized the error.
Microsoft explained that the issue was caused by a race condition in the Windows Servicing Stack that caused the shutdown command to get “forgotten” during the update process.
Fast Start woes
Microsoft introduced Fast Start, also known as hybrid boot, in Windows 8. This new feature was designed to make the PC start up faster by using hibernation.
The problem was that older systems did not support this new hybrid state. This caused blue screens on some systems. The systems would reboot automatically to recover and this looked to the user as if shut down was broken.
This is no longer an issue on modern PCs, but on older PCs, system administrators could disable Fast Startup to resolve the issue.