Imagine trying to turn off your computer, only to have it stubbornly ignore your commands, leaving it running all night—wasting energy and testing your patience. That’s exactly what happened to some Windows 11 users after Microsoft’s January Patch Tuesday update. But here’s where it gets even more frustrating: the very update meant to secure systems ended up breaking one of the most basic functions—shutting down your PC. Now, Microsoft has been forced into emergency mode, releasing an out-of-band (OOB) update to clean up the mess. Let’s dive into what went wrong and why it matters.
On January 17, Microsoft rolled out the emergency fix, KB5077797 (https://support.microsoft.com/en-us/topic/january-17-2026-kb5077797-os-build-22631-6494-out-of-band-3fb07d6a-0e35-4510-8518-4e333ed78edc), specifically targeting Windows 11 version 23H2. This update was a direct response to the chaos caused by the earlier January patch, which was supposed to plug over 100 security holes. Instead, it left some users unable to shut down, restart, or hibernate their systems. And this is the part most people miss: the root cause was a clash between the January update and System Guard Secure Launch, a boot-time security feature designed to harden Windows against attacks.
For those with Secure Launch enabled (a default setting in many builds), the shutdown process became a farce. PCs would appear to power down, only to keep humming away or suddenly reboot. This wasn’t just an annoyance—it had real-world consequences, like laptops draining batteries overnight or desktops consuming power long after work hours. Not exactly eco-friendly, right?
Microsoft’s OOB update claims to restore shutdown and hibernation functions to normal, sparing users the wait for the next Patch Tuesday. However, Redmond hasn’t offered much explanation beyond confirming the bug was introduced by the January cumulative update. But here’s the controversial part: Is it fair for users to bear the brunt of such critical oversights, especially when updates are meant to enhance security, not disrupt basic functionality?
And the shutdown bug wasn’t the only issue. The January patches also introduced an authentication problem, leaving some users unable to log in via Remote Desktop due to endless credential loops. Plus, Microsoft recently admitted to another Patch Tuesday-induced bug affecting classic Outlook POP account profiles, which can cause freezing—a fix for this is still pending. All this chaos unfolded as Microsoft pushed one of its largest monthly update bundles, with at least one vulnerability already under active exploitation. Security teams were left scrambling, only to uncover these issues post-deployment.
For now, Microsoft advises affected users to install KB5077797 to resolve shutdown and Remote Desktop issues. For everyone else, it’s a stark reminder that even routine updates can have unexpected side effects. So, here’s a thought-provoking question: Should users trust that monthly patches are thoroughly tested, or is it time for Microsoft to rethink its update rollout strategy? Let us know your thoughts in the comments—we’d love to hear your take on this messy situation. ®
