Microsoft update fallout continues as shutdown bug expands to Windows 10 VSM systems

Microsoft has acknowledged a regression where affected PCs fail to shut down or enter hibernation and instead restart. The issue originally surfaced after the January 13, 2026, security update for Windows 11 23H2, KB5073455 (OS Build 22631.6491).

In its Windows release health notes, Microsoft says the same behavior can also occur on some Secure Launch-capable PCs with Virtual Secure Mode (VSM) enabled after installing Windows updates released on or after January 13, 2026.

Affected versions and KBs

For Windows 11, Microsoft lists the shutdown/hibernate issue under KB5073455 and notes that an OOB update (KB5077797, OS Build 22631.6494) addresses the problem for some Secure Launch devices, but not for Secure Launch-capable PCs with VSM enabled.

For Windows 10, Microsoft has added the same VSM-related known issue to:

January 13, 2026—KB5073724 (OS Builds 19045.6809 and 19044.6809), where it says some Secure Launch-capable PCs with VSM enabled may restart instead of shutting down or hibernating.
January 24, 2026—KB5078131 (OS Build 17763.8281) for Windows 10 Enterprise LTSC 2019, which repeats the VSM shutdown/hibernate restart behavior and points to a future fix.

Microsoft’s release health dashboard explicitly lists affected client platforms as including Windows 11 23H2 and Windows 10 (22H2, LTSC 2021, and LTSC 2019), and it notes the problem does not affect AMD or ARM64 processors on the impacted scenario described there.

What to do next

Microsoft says the VSM-enabled variant will be addressed in a future Windows update.

In the meantime, Microsoft and third-party reporting have pointed to using the command shutdown /s /t 0 as a temporary workaround when you can’t apply the relevant OOB updates right away.