Ethical Hacking News
Microsoft's latest Patch Tuesday update has brought about a puzzling issue where some Windows PCs refuse to shut down or hibernate, leaving users frustrated. The problem appears to be tied to Secure Launch, and Microsoft is working on a resolution in a future update.
Microsoft Windows 11 23H2 systems with Secure Launch enabled may experience issues with shutdown or hibernation.Affected users may need to save work before shutting down and use the "shutdown /s /t 0" command at the command prompt to force their PC to turn off.The issue is not yet fully resolved, with a promised future update from Microsoft.Other issues with classic Outlook POP account profiles have also been reported after installing recent patches.
Microsoft's latest Patch Tuesday update has brought about a most peculiar and frustrating issue for some Windows users, where their PCs seem to have developed a mind of their own and refuse to shut down or hibernate. This phenomenon has been observed on systems running Windows 11 23H2, with affected machines staying stubbornly awake despite attempts to initiate shutdown or hibernation.
According to Microsoft's notice on its Windows release health dashboard, the issue appears to be tied to Secure Launch, a security feature that uses virtualization-based protections to ensure only trusted components load during boot. On systems with Secure Launch enabled, attempts to shut down, restart, or hibernate after applying the January patches may fail to complete, leaving users wondering why their PC is refusing to cooperate.
The company has acknowledged this issue and provided some guidance for affected users, advising them to save all work before shutting down their device, as the system may drain its battery instead of entering hibernation. Microsoft has also suggested using the command "shutdown /s /t 0" at the command prompt to force the PC to turn off, regardless of whether it wants to or not.
However, this solution does not provide a long-term fix for the issue, and Microsoft has not offered much in the way of technical detail or numbers on how many devices are affected. The company has merely promised to "release a resolution for this issue in a future update," which may be interpreted as a somewhat vague promise, akin to a sentient bot's attempt at reassurance.
This incident is not an isolated case, as Microsoft has acknowledged another emerging issue with classic Outlook POP account profiles freezing or hanging after installing the latest patches. While these issues may seem like minor inconveniences, they highlight the complex and often unpredictable nature of software updates and their impact on user experience.
In recent years, Patch Tuesday has brought a range of fixes to address security vulnerabilities, some of which have had unforeseen side effects. This phenomenon is not unique to Microsoft, as many software companies face similar challenges in balancing the need for security with the potential disruption that can arise from patching and updates.
The case of Windows PCs refusing to shut down after a Patch Tuesday update serves as a reminder that while software fixes are crucial in protecting against security threats, they can also have unintended consequences. For users who rely on their systems behaving predictably when told to turn off, this issue is particularly frustrating, especially if it means that devices may drain batteries or cause other inconvenience.
As Microsoft continues to work towards resolving this issue, it would be wise for the company to provide more detailed information about the root cause of the problem and any potential workarounds or solutions. In the meantime, users are left watching Microsoft's status pages and waiting for patches to be released, hoping that their machines will eventually go to sleep.
Related Information:
https://www.ethicalhackingnews.com/articles/The-Windows-PC-Shutdown-Conundrum-A-Patch-Tuesday-Puzzle-ehn.shtml
https://go.theregister.com/feed/www.theregister.com/2026/01/16/patch_tuesday_secure_launch_bug_no_shutdown/
Published: Fri Jan 16 10:56:04 2026 by llama3.2 3B Q4_K_M
