TL;DR
- Second Emergency Patch: Microsoft released KB5078127 on January 24, its second emergency update in seven days following widespread failures from January’s Patch Tuesday.
- What It Fixes: The update resolves Outlook crashes and OneDrive integration failures that emerged after the first emergency patch fixed shutdown and Remote Desktop issues.
- Cascading Failures: The January 13 Patch Tuesday update triggered a chain of problems affecting shutdown, Remote Desktop, Outlook, and cloud storage across multiple Windows versions.
- Quality Crisis: These issues add to a pattern of Windows 11 quality problems, with over 20 major update issues documented in 2025 alone.
Outlook crashes and OneDrive failures forced Microsoft to issue its second emergency Windows 11 patch in seven days, as January’s Patch Tuesday spiraled into a cascading quality crisis.
KB5078127, released Saturday, addresses failures affecting business users after the first emergency update fixed shutdown and Remote Desktop problems but broke Outlook and cloud storage apps.
What KB5078127 Fixes
The emergency patch resolves failures affecting Outlook and cloud storage integration. In certain configurations with PST files on OneDrive, Outlook may hang and fail to reopen unless terminated, with users experiencing missing sent items or emails re-downloading.
After January 13, some applications became unresponsive when opening files to cloud storage like OneDrive or Dropbox.
“An out-of-band (OOB) update was released today, January 24, 2026, to address this issue. This cumulative update includes all protections and improvements from the January 2026 Windows security update released January 13, 2026, as well as from the OOB update released on January 17, 2026 (which introduced fixes for two known issues: remote desktop connections and hibernation failures).”
The update is available for Windows 11 version 24H2 and 25H2, with the same fix rolled out to version 23H2, Windows Server editions, and other versions.
Promo
For now, the temporary workaround is to uninstall the latest security updates, leaving systems vulnerable to 114 security vulnerabilities, including one already exploited in the wild.
This forces IT administrators into an impossible choice between broken productivity tools and security exposure. The cumulative nature of Microsoft’s statement reveals how each patch incorporates previous fixes, creating a dependency chain where failure at any point affects everything downstream.
This impossible choice builds upon similar issues that emerged with the first emergency update earlier this week.
The Cascading Failure Pattern
To understand how Microsoft arrived at this second emergency patch, it’s worth tracing the progression of failures since January 13. That initial Patch Tuesday caused PCs running version 23H2 to fail to shutdown or hibernate, while breaking signing into Windows 11 PCs using Remote Desktop.
The January 17 emergency update fixed those Remote Desktop issues affecting Windows 11 25H2, Windows 10 22H2 ESU, and Windows Server 2025.
However, that first patch left Outlook and cloud storage apps broken. Microsoft published six different OOB updates for Windows 11 (23H2 through 25H2), Windows 10 (22H2), and Windows Server versions from 2019 to 2025. Some updates required manual download from Microsoft Update Catalog.
Original Patch Tuesday Failures
The root cause stems from what the January 13 update was originally meant to accomplish. That update was intended to resolve 114 security vulnerabilities, several rated high severity.
The first issue affected remote desktop connections to Azure Virtual Desktop and Windows 365 cloud services. The second problem affects devices protected by Secure Launch, a virtualization-based security feature designed to block firmware-level threats.
“After installing the January 13, 2026, Windows security update (the Originating KBs listed above) for Windows 11, version 23H2, some PCs with Secure Launch are unable to shut down or enter hibernation. Instead, the device restarts.”
Quality Crisis Context
These cascading emergency fixes reflect a broader pattern of Windows 11 quality problems.
These quality issues come despite Microsoft having a Windows Insider programme for beta testing that has existed for a decade. The Windows 11 24H2 release in October 2024 began a rough period of bugs continuing through the first half of 2025.
Compounding matters, Microsoft ended Windows 10 support three months before these Windows 11 problems emerged, leaving users with fewer stable options.
The timing suggests a structural problem with Microsoft’s quality assurance processes rather than isolated incidents.
CEO Satya Nadella stated last year that 30% of Microsoft’s code is now AI-generated. How does this affect the production code of Windows and other Microsoft products?
Looking ahead, OOB updates will eventually be incorporated into February’s Patch Tuesday updates. Enterprise-managed devices have an alternative: Known Issue Rollback (KIR) can revert the problematic changes without waiting for official updates.
