Microsoft Addresses Critical Windows 11 Shutdown and Remote Desktop Bugs

Microsoft has rushed out emergency out-of-band updates after a recent Windows 11 security patch disrupted core system functions, leaving some PCs unable to shut down or hibernate and blocking Remote Desktop sign-ins. The issue was introduced with last week’s January 2026 security updates for Windows 11. Specifically, Microsoft’s recent Windows 11 security update introduced two bugs that disrupted basic functionality for many users. One issue caused some devices running Windows 11 version 23H2 with Secure Launch enabled to restart instead of shutting down or entering hibernation. This problem affects Enterprise and Education customers, as the Home and Pro editions have already reached end of support. Microsoft has also acknowledged another bug that caused authentication and connection failures when attempting to log in via Remote Desktop. This issue impacted Windows 11 version 25H2 as well as Windows 10 and all supported Windows Server editions. “After installing the January 2026 Windows security update (the Originating KBs listed above), credential prompt failures might occur in some remote connection applications,” Microsoft explained in the release notes. “This includes remote desktop connections using the Windows App on Windows client devices, on Azure Virtual Desktop and Windows 365. The Windows App is affected by this issue on specific Windows builds and can experience sign-in failures.” Microsoft releases out-of-band patches for Windows 11 PCs To address these issues, Microsoft released two emergency patches (KB5077744 and KB5077797) on January 17 for Windows 11 versions 25H2, 24H2, and 23H2. These updates are not available via Windows Update and must be installed from the Microsoft Update Catalog. For larger environments, IT administrators can streamline the process by using management tools such as Group Policy or enterprise update solutions to roll out a Known Issue Rollback (KIR), which allows administrators to quickly reverse the problematic behavior without waiting for full patch deployment. Best practices to prevent widespread update disruptions IT teams can reduce the impact of similar Windows issues by going beyond simply installing emergency patches and adopting a more strategic mitigation approach. A good starting point is deciding when to rely on a Known Issue Rollback versus when to deploy catalog updates for precise, device‑specific fixes manually. Furthermore, administrators can also establish a triage routine that flags affected systems early by monitoring Event Viewer entries, Remote Desktop–related authentication errors, or power‑related Kernel‑Power events. It’s advised to combine these practices with a small pilot deployment group, which helps catch regressions before updates reach the broader fleet to avoid widespread outages.