Microsoft has issued out-of-band updates for Windows 10, Windows 11, and Windows Server to fix two critical issues introduced by the January 2026 Patch Tuesday updates.
Issues Addressed
- Cloud PC / Remote Desktop Failures
- Affected: Windows 10, Windows 11, Windows Server.
- Problem: Credential prompt failures in remote connection apps (Windows App, Azure Virtual Desktop, Windows 365).
- Impact: Users unable to sign in to Microsoft 365 Cloud PC sessions.
- Secure Launch Shutdown Bug
- Affected: Windows 11 version 23H2.
- Problem: PCs with Secure Launch enabled cannot shut down or hibernate; instead, they restart.
- Cause: Secure Launch uses virtualization-based security to protect against firmware-level threats.
Out-of-Band Updates Released
| Product | KB Number | Fixes |
|---|---|---|
| Windows Server 2025 | KB5077793 | Cloud PC connections |
| Windows Server 2022 | KB5077800 | Cloud PC connections |
| Windows Server 2019 | KB5077795 | Cloud PC connections |
| Windows 11 25H2 & 24H2 | KB5077744 | Cloud PC connections |
| Windows 11 23H2 | KB5077797 | Cloud PC connections + Secure Launch shutdown bug |
| Windows 10 | KB5077796 | Cloud PC connections |
These updates are not available via Windows Update. They must be manually downloaded from the Microsoft Update Catalog.
🔧 Alternatives for Enterprises
For organizations unable to install OOB updates, Microsoft recommends deploying a Known Issue Rollback (KIR) via Group Policy.
Examples:
- Windows Server 2022 → KB5073457
- Windows Server 2025 → KB507339
- Windows Server 2019 / Windows 10 LTSC 2019 → KB5073723
- Windows 11 25H2/24H2 → KB5074109
- Windows 11 23H2 → KB5073455
- Windows 10 22H2 → KB5073724
Recommendations
- Immediate action: Admins should manually install the relevant OOB updates if affected.
- Enterprise workaround: Use KIR Group Policy for managed devices if patching is delayed.
- No impact? If your systems aren’t affected, you can wait for the next Patch Tuesday or preview update.
Takeaway
These OOB updates highlight how critical fixes sometimes need to bypass the normal monthly cycle. The Secure Launch bug and Cloud PC credential failures could significantly disrupt enterprise environments, making manual patching or KIR deployment essential for continuity.
Leave a Reply