Patch Tuesday updates are supposed to improve security and stability—but in January 2026, things went seriously wrong. Shortly after Microsoft released its regular monthly updates, users began reporting major system-breaking issues across Windows 10, Windows 11, and Windows Server.
Two critical bugs stood out. On some systems, Remote Desktop connections stopped working entirely, bringing business workflows to a halt. On others—specifically Windows 11 23H2 PCs—computers refused to shut down or hibernate, restarting instead.
Faced with growing complaints, Microsoft rushed out a set of out-of-band (OOB) emergency updates on January 17, 2026. These fixes are not delivered automatically through Windows Update and must be installed manually.
Here’s what broke, which updates fix it, and how to install them safely.
What Went Wrong With the January 2026 Patch Tuesday?
On January 13, 2026, Microsoft rolled out its regular Patch Tuesday updates:
These updates were meant to address security vulnerabilities and improve system reliability. Instead, they introduced two serious regressions affecting both consumer and enterprise users.
Bug #1: Remote Desktop Connections Fail Across Multiple Windows Versions
The first issue hit users relying on Remote Desktop services, including:
- Azure Virtual Desktop
- Windows 365
- Microsoft’s Remote Desktop apps (including Windows App)
Affected systems fail during authentication, making it impossible to establish a remote session. For IT teams and remote workers, this effectively meant no access to critical systems, causing significant disruption in professional environments.
Bug #2: Windows 11 23H2 PCs Restart Instead of Shutting Down
The second bug was even more baffling.
On Windows 11 version 23H2, systems with Secure Launch enabled refuse to shut down or enter hibernation. Instead, selecting “Shut down” causes the PC to reboot automatically.
Secure Launch is a virtualization-based security feature designed to protect the system from firmware-level threats during startup. Unfortunately, it appears to conflict with the January update—making proper shutdown impossible on affected machines.
Temporary Workarounds (Before the Fix)
Initially, Microsoft suggested short-term workarounds:
- Using the web-based Remote Desktop client instead of native apps
- Forcing shutdown via Command Prompt using:
shutdown /s /t 0
While functional, these were clearly stopgap solutions, not acceptable long-term fixes.
Four days later, Microsoft finally delivered proper corrections.
Emergency Windows Updates Released on January 17, 2026
On January 17, Microsoft published multiple out-of-band cumulative updates that:
- Include all original security fixes from Patch Tuesday
- Specifically resolve the Remote Desktop and shutdown issues
These updates must be downloaded manually from the Microsoft Update Catalog.
List of Emergency Updates by Windows Version
Windows 11
- KB5077744 – Fixes Remote Desktop issues on Windows 11 25H2 and 24H2
- KB5077797 – Fixes both Remote Desktop and shutdown/restart issues on Windows 11 23H2
Windows 10
- KB5077796 – Fixes Remote Desktop on Windows 10 22H2 and Enterprise LTSC 2021
- KB5077795 – Fixes Remote Desktop on Windows 10 Enterprise LTSC 2019
Windows Server
⚠️ Important:
Only KB5077797 (Windows 11 23H2) fixes the shutdown/restart bug, as no other Windows version is affected by that specific issue.
How to Download and Install the Fixes Manually
Unlike standard Windows updates, these emergency patches will not install automatically. You must install them manually using the Microsoft Update Catalog.
Step-by-Step Installation Guide
- Go to the Microsoft Update Catalog
- Search for the KB number that matches your Windows version
- Locate the correct package for your system architecture:
- x64 for most PCs
- ARM64 for ARM-based devices
- Click Download, then click the link in the popup window
- Once the
.msufile is downloaded, double-click it - Follow the on-screen instructions to install the update
- Restart your PC when prompted
Updates available by Windows version
| System | Update | Download |
|---|---|---|
| Windows 11 25H2 / 24H2 | KB5077744 | Download |
| Windows 11 23H2 | KB5077797 | Download |
| Windows 10 22H2 / Enterprise LTSC 2021 | KB5077796 | Download |
| Windows 10 Enterprise LTSC 2019 | KB5077795 | Download |
| Windows Server 2025 | KB5077793 | Download |
| Windows Server 2022 | KB5077800 | Download |
| Windows Server 2019 | KB5077795 | Download |
Should You Install These Updates Immediately?
Yes—especially if you rely on Remote Desktop or are running Windows 11 23H2.
These updates:
- Restore broken remote access
- Fix shutdown and hibernation behavior
- Include all January 2026 security patches
Skipping them may leave your system unstable or unusable in professional scenarios.
Conclusion
The January 2026 Patch Tuesday was a rare but serious misstep from Microsoft. Breaking Remote Desktop and basic shutdown functionality is no small issue—particularly for businesses and remote workers.
Fortunately, Microsoft acted quickly with out-of-band emergency updates. While manual installation is inconvenient, these fixes are essential for restoring normal system behavior.
If your PC or server is affected, install the appropriate update as soon as possible—and hopefully, February’s Patch Tuesday will be far less eventful.
And if you'd like to go a step further in supporting us, you can treat us to a virtual coffee ☕️. Thank you for your support ❤️!
We do not support or promote any form of piracy, copyright infringement, or illegal use of software, video content, or digital resources.
Any mention of third-party sites, tools, or platforms is purely for informational purposes. It is the responsibility of each reader to comply with the laws in their country, as well as the terms of use of the services mentioned.
We strongly encourage the use of legal, open-source, or official solutions in a responsible manner.


Thank you for posting. I was hoping it wasn’t just me. I just made a big network change for our company this weekend by switching to a new ISP. I did all the due-diligence and made sure everything was working over the weekend (router config, DNS, vendor services, VPN, etc). Then this morning, I get 3 of our 7 remote employees texting me in panic that they can’t connect. Of course, my brain goes into overdrive and starts thinking, “OH Dang! What did I miss?!?!” … but here it’s just another MS fumble. I think they started failing on an exponential scale when they first provided a ‘Check for Updates’ button that checks … then downloads … then installs … without ever offering user interaction. My favorite article written in 2019 by Leo Notenboom, and it’s STILL relevant today in 2026. https://askleo.com/microsoft-we-deserve-better/
thanks