Emergency Windows 11 Updates Fix Shutdown And Remote Desktop Failures

Microsoft has issued emergency out-of-band updates for Microsoft Windows 11 after the latest security patches introduced two serious regressions. Affected systems were unable to shut down or hibernate correctly, and Remote Desktop sign-ins failed on certain configurations.
The issues appeared with Microsoft’s first Windows 11 updates released in 2026. Reports quickly surfaced from users who found that shutdown attempts would hang or fail entirely. Separately, Remote Desktop connections could no longer authenticate, preventing sign-ins to affected machines. Both problems were severe enough that Microsoft released fixes outside of the normal update schedule.
Microsoft has now published two out-of-band updates, KB5077744 and KB5077797, which are rolling out through Windows Update. Installing the updates restores normal shutdown behavior and resolves the Remote Desktop authentication failures.
The shutdown issue affects devices running Windows 11 version 23H2 with Secure Launch enabled. On these systems, shutdown and hibernation could fail after the January security updates were installed. The Remote Desktop problem has a broader scope, affecting Windows 11 version 25H2, Windows 10 22H2 ESU, and Windows Server 2025, according to Microsoft’s advisory.
Users who rely on Remote Desktop to access work or home systems were effectively locked out until the emergency patches became available. Microsoft has not provided a detailed explanation for how the issues passed testing, but confirmed that the fixes fully address the reported behavior.
The out-of-band updates are offered automatically via Windows Update. Devices configured to pause updates or managed through enterprise update policies may require manual approval or deployment before the fixes are applied.
These issues add to a growing list of Windows 11 update problems seen over the past year. Previous updates have caused Task Manager to remain running after being closed, leading to resource usage problems over time. Another update introduced a bright white flash when opening File Explorer in dark mode, despite being marketed as an improvement to dark mode behavior.
Microsoft has also had to fix an update that broke the Windows Recovery Environment, preventing users from accessing recovery options when troubleshooting system failures. Each of these issues was addressed after release, but only once users encountered them on production systems.
For now, Microsoft recommends that affected users install the emergency updates as soon as they become available. Systems that cannot shut down properly or accept Remote Desktop connections are expected to return to normal behavior immediately after the patches are applied.
Microsoft should be held accountable for these problems. It’s sad that nobody is doing anything about it. The situation just keeps getting worse every Patch Tuesday. They should impose heavy fines on them for each bug.
They will not be held accountable, because they are a monopoly on the PC market. The sooner Microslop turns Winblows into a bigger piece of garbage and pushes more people away to Linux and Mac, the better. When Microslop one day wakes up and Winblows is below 50% market share and the competitors are over 15% each, then they will try to act like the cool and user-friendly bunch again, but it just might be too late.
They got too big for their britches in the last 20 years and now think they can get away with anything. But losing users and therefore money is going to hit them where it hurts the most. I don’t care when this happens, personally, the sooner the better, but regardless of that, I have moved away from Winblows and Microslop and I have no intention to return, even if they make it the best OS possible in the future.