[ad_1]
Microsoft’s first Windows 11 security update of 2026 caused two nasty failures, some PCs couldn’t finish a shutdown, and some users couldn’t sign in over Remote Desktop. Microsoft has now shipped emergency updates to fix both.
The updates are out-of-band, meaning they landed outside the normal schedule, and they’re already showing up in Windows Update. If your PC started hanging during shutdown, failing to hibernate, or refusing remote sign-ins after the latest security patch, installing the emergency fix is the fastest path back to a stable machine.
The emergency patches to install
Microsoft has released two out-of-band updates, KB5077744 and KB5077797, and it is rolling them out through Windows Update.
The fixes target two specific problems. First, Windows 11 version 23H2 devices with Secure Launch could fail to shut down or hibernate. Second, connection and authentication failures hit remote connection apps across multiple platforms, including Windows 11 version 25H2, Windows 10 version 22H2 ESU, and Windows Server 2025.
Why these bugs hit so hard
A shutdown failure isn’t a small glitch, and the Remote Desktop issue also punches above its weight. A lot of people use remote access for work, troubleshooting, and hopping between machines, so a sign-in failure can stop a day cold.
This incident also lands in a touchy spot, it’s the first Windows 11 update cycle of 2026, and it shipped with problems that should have been caught earlier. The Windows Insider Program exists to catch bugs before release, but issues this severe still made it through.
What to watch next
If you were affected, check Windows Update and install the emergency patches as soon as they appear. Once applied, your PC should be able to shut down cleanly again, and Remote Desktop sign-ins should work.
If you weren’t hit, you don’t need to panic, but you should pay attention to how quickly this happened. A short cooling-off period before installing brand-new updates can help you avoid the worst surprises, especially when core features are on the line.
For now, the practical takeaway is simple. Update, confirm shutdown works, then get back to work.
[ad_2]
Source link
