Microsoft Issues Emergency Patch for Windows 11 Shutdown Bug

Microsoft released the first January update for 2026 last week, which brought multiple fixes and changes to Windows 11. However, it also introduced a bug of its own that prevented some users from shutting down their computers directly or via the remote desktop feature. It was a huge oversight on Microsoft's part, and it wasn't the first time something like that has happened. However, the company quickly acknowledged and provided a workaround that users can apply until a permanent fix is provided. Microsoft has now released an emergency patch to permanently fix the bug. This article briefly discusses this update and explains how to install it immediately. The latest out-of-band patch fixes the shutdown bug in Windows 11 Microsoft has released two out-of-band patches, KB5077744 and KB5077797, on Windows Update to permanently fix the shutdown bug. They are rolling out to all users immediately and will be installed on your PC or laptop. However, you can manually trigger the update by heading over to Settings/Windows Update and clicking on the Check for updates button. This should force Windows 11 to recheck for updates and install both KB5077744 and KB5077797. Once the updates have reinstalled, you may need to restart your PCs. After that, the shutdown bug should disappear, and you will be able to shut down your PC directly or via another PC on the Remote Desktop Protocol. Here are the patch notes of the two updates: Remote Desktop Fixed: Some users experienced sign-in failures during Remote Desktop connections. This issue affected authentication steps for different Remote Desktop applications on Windows such as the Windows App. Power & Battery Fixed: Some devices with Secure Launch enabled restart instead of shutting down or entering hibernation. This shutdown bug should have been caught before the January update was rolled out. After all, one of the goals of the Windows Insider Program was to catch bugs early and provide a better user experience. However, it seems the error somehow managed to slip through. Read more: Windows 11 January update brings compatibility changes and bug fixes