Microsoft is now publicly urging millions of Windows 11 users to remove a freshly released security update — a rare acknowledgment that the company’s own software has caused instability across a wide swath of devices. On January 13, 2026, Microsoft began rolling out its first major 2026-01 Cumulative Update for Windows 11, identified as KB5074109 (Windows 11 OS Build 26200.7623). However, shortly after the rollout began, user reports of serious issues started flooding in, ranging from app crashes and black screens to outright system malfunctions, forcing the company to backtrack and recommend uninstalling the update altogether.

At the heart of the controversy is the fact that this update was not optional for many PCs — it was a mandatory security patch, designed to protect systems against more than 100 known vulnerabilities and improve device performance and stability. Yet, instead of strengthening Windows, the patch exposed a raft of critical software regressions, affecting core applications, user workflows, and even fundamental system functions like power management.

The Broken Patch: What Went Wrong

Reports from multiple sources and affected users show a pattern of diverse and serious malfunctions after installing KB5074109:

• Outlook stability issues: Traditional Microsoft Outlook (classic) users on Windows 11 with POP email accounts have experienced the app freezing or hanging indefinitely — particularly when profiles include PST files stored in cloud-synced folders such as OneDrive. Microsoft confirmed these problems and acknowledged that there is no simple permanent fix available yet, recommending users either move their PST files out of OneDrive or remove the update entirely.
• System instability: Users with certain NVIDIA GPUs reported random black screens, error messages, application crashes, and performance slowdowns that were not present before the update. In some cases, applications have failed to launch correctly or show error codes like 0x803F8001.
• Widespread app unresponsiveness: Beyond Outlook, several other applications began exhibiting unresponsiveness or crashes, particularly when interacting with cloud-stored data or files. It appears the update disrupted normal file access patterns and lock handling in apps that rely on synchronized storage.
• Power and shutdown errors: On some devices — especially older hardware — the update caused failures in sleep mode and shutdown procedures. Systems would enter a blank screen or require a hard reboot to recover, undermining basic stability expectations.

Although Microsoft quickly released emergency out-of-band patches — for example, KB5077744 to address Remote Desktop sign-in failures and other issues — the core Outlook and app stability problems remain unresolved, leaving uninstalling KB5074109 as the most straightforward workaround.

Why Microsoft Recommends Uninstallation

It’s very rare for Microsoft to publicly suggest that users remove an update it has just released — but in this case, the scale of the complaints and the severity of the malfunctions appear to have left the company little choice.

Official guidance now strongly urges affected users to roll back the update, at least until a fixed release is made available. According to support notes and community moderators tracking the fallout, Microsoft’s current recommendations include:

• Using web-based Outlook: For users whose desktop Outlook client is failing, switching to the online version may be a temporary solution until a patch arrives.
• Uninstalling KB5074109: The most direct solution, widely described in Windows support documentation and major tech outlets, is to go into Settings → Windows Update → Update history → Uninstall updates, find KB5074109, and remove it. Pausing updates afterward may prevent the patch from reinstalling automatically.
• Relocating critical files: For people who must stick with the update for security reasons yet rely on classic Outlook, moving PST files out of cloud-synced folders like OneDrive or Dropbox is another workaround Microsoft has suggested, though it’s complex and not ideal for many users.

Microsoft has noted that uninstalling a security update can create its own risks — older vulnerabilities remain unpatched — but the consensus among frustrated users is that the current build is worse than remaining on a slightly older, more stable version of Windows 11.

Broader Implications: A Pattern of Update Problems

This incident is not occurring in isolation. Over the past year, Windows 11 updates have increasingly sparked controversy among enthusiasts, IT professionals, and everyday users alike. Prior misfires have included broken features in File Explorer and Task Manager, problematic AI integrations, and emergency patches released mid-month to “fix the fix.” While not all these problems were directly caused by Microsoft’s official updates, they contribute to a growing perception that Windows servicing is less reliable in the AI-driven development era.

For many users, the trust erosion is palpable. Long-time Windows administrators note that having to downgrade a security update is a stark reversal of the usual expectation that updates are an improvement, not a liability. In enterprise settings where compliance and uptime are paramount, this could have significant operational impact.

What Happens Next

At this stage, Microsoft is likely working on a revised build to address the most severe bugs introduced by KB5074109. However, until an official announcement and a tested patch are released, individuals and organizations must choose between security and stability — a dilemma that should not normally exist only days after a major update.

For users who rely heavily on Outlook or other productivity applications, reverting to a pre-KB5074109 system state while watching for updated releases may be the best practical course of action. Others will hope that Microsoft’s development and testing processes improve to prevent similar missteps in the future.

In the meantime, the fallout from KB5074109 serves as a stark reminder: even in 2026, with all the advances in development tooling and AI assistance, software quality remains a human-centric challenge as much as a technical one.