Windows 10 Shutdown Bug: Microsoft Confirms & Fixes
- A shutdown bug affecting Windows devices is proving more widespread than initially thought, now impacting multiple versions of Windows 10 in addition to Windows 11.
- The problem first surfaced with Windows 11 in January 2026, but has now been identified in Windows 10 22H2, Windows 10 Enterprise LTSC 2019, and Windows 10 Enterprise...
- VSM creates an isolated memory region, safeguarding sensitive data like encryption keys and credentials.
A shutdown bug affecting Windows devices is proving more widespread than initially thought, now impacting multiple versions of Windows 10 in addition to Windows 11. Microsoft has confirmed the issue, which prevents some PCs from shutting down or entering hibernation, stems from interactions between security features and recent updates.
The problem first surfaced with Windows 11 in January 2026, but has now been identified in Windows 10 22H2, Windows 10 Enterprise LTSC 2019, and Windows 10 Enterprise LTSC 2021. The root cause appears to be related to System Guard Secure Launch and Virtual Secure Mode (VSM), security features designed to protect against firmware-level attacks and kernel-level malware respectively.
VSM creates an isolated memory region, safeguarding sensitive data like encryption keys and credentials. System Guard Secure Launch focuses on securing the boot process. While intended to enhance security, the interaction between these features and recent updates – specifically KB5073724 and KB5078131 for Windows 10, and KB5073455 for Windows 11 – is causing the shutdown failures.
Microsoft initially attempted to address the issue with an emergency update, but acknowledged that the fix was not universally effective. The company is now developing a more permanent solution for both Windows 10 and Windows 11. A precise timeline for the release of this fix has not been publicly announced.
The situation is particularly frustrating for users who have paid for Extended Security Updates (ESU) for Windows 10. These updates, available for a fee, are intended to provide continued security and stability for organizations that haven’t yet migrated to Windows 11. The fact that a fundamental function like shutting down is broken on systems receiving paid support highlights the ongoing challenges Microsoft faces in maintaining older operating systems while simultaneously developing and deploying updates for newer ones.
Access to ESUs is limited to customers in the European Economic Area and those who specifically purchase the extended support package. This means a segment of the Windows 10 user base is paying for a stable and secure experience, yet encountering this significant bug.
While Microsoft works on a permanent fix, users experiencing the shutdown issue can employ a temporary workaround. Typing shutdown /s /t 0 into the Command Prompt will force the system to shut down. This command bypasses the normal shutdown process, potentially mitigating the issue caused by the interaction between the security features and the problematic updates.
The bug’s persistence despite Microsoft’s initial attempts to resolve it underscores the complexity of the Windows ecosystem. The company has recently stated a renewed focus on Windows stability, but this incident demonstrates the challenges of delivering reliable updates across a diverse range of hardware and software configurations. The ongoing issues with Windows 10, even after consumer end of support in , suggest that maintaining older versions of Windows remains a significant undertaking for Microsoft.
The affected Windows 10 versions are:
- Windows 10 22H2
- Windows 10 Enterprise LTSC 2019
- Windows 10 Enterprise LTSC 2021
The affected Windows 11 version is:
- Windows 11 23H2
This issue highlights the inherent risks associated with complex operating system updates. Even with rigorous testing, unforeseen interactions between different system components can lead to unexpected problems. Microsoft’s response – acknowledging the issue, providing a workaround, and committing to a permanent fix – is a standard approach, but the continued disruption underscores the importance of prioritizing stability alongside new features and security enhancements.
