Tag: Secure Launch

Key Takeaways

1. Microsoft identified a shutdown and hibernation issue in some PCs after the January 13, 2026 security update for Windows 11 23H2 (KB5073455).
2. The problem affects certain Secure Launch-capable PCs with Virtual Secure Mode (VSM) enabled, causing them to restart instead of shutting down or hibernating.
3. An out-of-band update (KB5077797) fixes the issue for some Secure Launch devices, but not for those with VSM turned on.
4. Affected systems include Windows 11 23H2 and specific Windows 10 versions, while AMD and ARM64 processors are not impacted.
5. Microsoft plans to address the VSM issue in a future update, and a temporary workaround is to use the command `shutdown /s /t 0`.

---

Microsoft has recognized a problem where some PCs are unable to shut down or go into hibernation, instead opting to restart. This issue first appeared following the January 13, 2026, security update for Windows 11 23H2, identified as KB5073455 (OS Build 22631.6491).

Issue Details

According to Microsoft’s Windows release health notes, this behavior can also be seen on certain Secure Launch-capable PCs that have Virtual Secure Mode (VSM) enabled, after installing any updates released on or after January 13, 2026.

For users of Windows 11, the shutdown and hibernation problem is categorized under KB5073455, and it indicates that an out-of-band update (KB5077797, OS Build 22631.6494) fixes the issue for some Secure Launch devices, though it does not apply to those Secure Launch-capable PCs with VSM turned on.

Update Timeline

On January 13, 2026, an update identified as KB5073724 (OS Builds 19045.6809 and 19044.6809) noted the same issue where certain Secure Launch-capable PCs with VSM enabled might restart rather than shut down or hibernate. Then, on January 24, 2026, update KB5078131 (OS Build 17763.8281) for Windows 10 Enterprise LTSC 2019 reiterated the restart behavior related to VSM and referenced a fix to come.

Microsoft’s release health dashboard clearly identifies affected client systems as Windows 11 23H2 and Windows 10 (22H2, LTSC 2021, and LTSC 2019), and importantly, it mentions that the issue does not impact AMD or ARM64 processors in the outlined scenarios.

Future Fixes and Workarounds

Microsoft has stated that the variant involving VSM will be addressed in an upcoming Windows update. Meanwhile, both Microsoft and third-party sources have suggested using the command shutdown /s /t 0 as a temporary solution for those who cannot immediately apply the relevant out-of-band updates.

Source:
Link

---

 

Key Takeaways

1. A confirmed issue prevents some systems from shutting down or hibernating after installing the January 13, 2026, Windows security update KB5073455 for Windows 11 version 23H2.
2. The problem is linked to the Secure Launch feature, which uses virtualization-based security to protect against firmware threats during startup.
3. KB5073455 is mainly available for Enterprise and IoT editions of Windows 11 version 23H2, limiting its reach to consumer PCs.
4. A fix for affected Windows 10 systems was included in out-of-band updates KB5077797 and KB5078132, with the latter also available for devices that installed earlier related updates.
5. KB5078132 is cumulative, containing improvements from both KB5073455 and KB5077797, along with additional fixes for app responsiveness issues related to cloud storage.

---

Microsoft’s Windows release health dashboard has identified a confirmed problem where some systems do not shut down or go into hibernation. Instead, they restart after the installation of the January 13, 2026, Windows security update KB5073455 for Windows 11 version 23H2.

Secure Launch Affected

The feature involved, known as Secure Launch, utilizes virtualization-based security to protect systems from firmware threats during the startup process. This issue is particularly relevant for users who rely on this feature for added security.

Limited Availability

It’s worth noting that KB5073455 is primarily available for Enterprise and IoT editions of Windows 11 version 23H2, which significantly limits the number of consumer PCs that will receive the update through standard channels.

Additionally, Microsoft has pointed out that PCs capable of Secure Launch with Virtual Secure Mode (VSM) turned on are also affected by this issue. They have indicated that a resolution for the VSM situation will come in a future Windows update.

Affected Systems

The problem also impacts Windows 10 systems. Microsoft confirmed that a fix for devices using Secure Launch (excluding the VSM case) was included in an out-of-band update on January 17, 2026: KB5077797 (OS Build 22631.6494). This update is only accessible through the Microsoft Update Catalog.

Moreover, Microsoft stated that the same fix can be found in another out-of-band update released on January 24, 2026: KB5078132 (OS Build 22631.6495). This update is available via Windows Update for devices that installed one of the January updates related to this problem.

Cumulative Fixes

Microsoft emphasizes that KB5078132 is cumulative, meaning it contains protections and improvements from both KB5073455 (January 13) and KB5077797 (January 17), along with additional fixes, such as addressing an app unresponsiveness issue linked to cloud storage workflows.

This situation has certainly posed challenges for Microsoft, but they appear to be gearing up for a new update release in the near future.

Source:
Link

---