Microsoft has released an emergency out-of-band (OOB) update after the January 2026 Windows security update caused widespread failures across multiple Windows versions. The company confirmed authentication breakdowns in remote connection apps and shutdown failures on Secure Launch systems, and it now urges affected users and IT teams to install the fixes immediately.
The issue impacts Windows 11 versions 25H2, 24H2, and 23H2, along with Windows 10 22H2 ESU and several Windows Server releases. Users who rely on Remote Desktop, Azure Virtual Desktop, Windows 365, and the Windows App felt the impact first, especially in enterprise and remote work environments.
Remote Desktop Login Failures Hit Cloud and Enterprise Systems
After installing the January security patch, many users could not sign in through Remote Desktop and related remote connection apps. Authentication prompts failed during login, blocking access to Cloud PCs and virtual desktops.
See also: How to Fix KB5074109 Azure Virtual Desktop Authentication Error on Windows 11
Microsoft traced the issue to credential handling inside the Windows App and remote connection stack. The failure affected Azure Virtual Desktop, Windows 365, and local Remote Desktop sessions across multiple builds.
What Microsoft Says Users Should Do
Microsoft recommends installing the emergency OOB update directly from the Microsoft Update Catalog instead of waiting for the next Patch Tuesday rollout. If your environment depends on remote access workflows, the company advises applying the patch immediately to restore authentication reliability.
For organizations that cannot deploy manual updates quickly, Microsoft suggests using a Known Issue Rollback (KIR) policy through Group Policy to restore remote connectivity until the permanent fix arrives through Windows Update.
Secure Launch PCs Failed to Shut Down Properly
The second major issue affected Windows 11 version 23H2 systems that use Secure Launch protection. Instead of shutting down or entering hibernation, affected devices restarted automatically, disrupting normal power management and maintenance workflows.
See also: Windows 11 KB5074109 Update for 25H2 Released: Major Fixes and Direct Download Links
Secure Launch relies on virtualization-based security to protect devices from firmware-level threats during startup. The January patch interfered with this process and caused shutdown failures.
Microsoft’s Temporary Workaround for Shutdown Failures
Until users install the emergency update, Microsoft advises manually shutting down affected systems using the following command:
shutdown /s /t 0Run this command from an elevated Command Prompt. This workaround allows safe shutdown until the permanent fix installs.
Emergency Updates Available Now — How to Install Them Safely
Microsoft released the OOB updates on January 17, 2026. These updates do not appear automatically in Windows Update yet, so affected users must install them manually.
Step 1: Confirm Your Windows Version
- Press Windows + R
- Type winver and press Enter
- Note your Windows version and build number
This ensures you download the correct update package.
Step 2: Download the Correct Patch from Microsoft
Open the Microsoft Update Catalog and search for the appropriate KB:
- Windows 11 25H2 / 24H2 → KB5077744
- Windows 11 23H2 → KB5077797
- Windows 10 22H2 ESU / LTSC 2021 → KB5077796
- Windows Server 2025 → KB5077793
- Windows Server 2022 → KB5077800
- Windows Server 2019 / LTSC 2019 → KB5077795
Download the file that matches your system architecture.
Step 3: Install and Restart
Launch the downloaded update package and complete the installation. Restart your device once the installer finishes. After reboot, test Remote Desktop connectivity and shutdown behavior immediately.
Enterprise Deployment Guidance for IT Teams
IT administrators managing large fleets can deploy a Known Issue Rollback policy through Group Policy to restore remote login functionality quickly. This method helps stabilize production systems without waiting for manual patch distribution across hundreds or thousands of devices.
Microsoft plans to bundle these fixes into the next preview update and the upcoming Patch Tuesday release.
Some Issues Remain Under Investigation
While Microsoft resolved the two most disruptive failures, reports indicate that a few issues remain unresolved, including:
- Black screen delays during login
- Desktop wallpaper resetting to black
- File Explorer desktop.ini behavior inconsistencies
- Outlook Classic freezes in some POP account setups
Microsoft has not published timelines for these fixes yet.
If your system depends on remote access, Cloud PCs, or Secure Launch protection, install the emergency update as soon as possible. If your device does not show any symptoms, you can wait for the next scheduled update cycle.
We will continue monitoring Microsoft’s release health updates and KB advisories. If Microsoft publishes additional fixes, workarounds, or confirmed impact changes, we will update this article accordingly.
