Windows 11 Update Breaks More Than It Fixes, Users Report Chaos
By 813 Staff
If you’re running Windows 11 and your system felt sluggish this morning, there’s a reason you need to pay attention right now. Late yesterday, Microsoft began pushing KB5089573, an optional, non-security preview update for Windows 11 that, according to internal documents reviewed by my sources, is intended to resolve a cascade of performance complaints that have been mounting since the February 2026 Patch Tuesday cycle. BleepingComputer (@BleepinComputer) first flagged the release, and what I’m hearing from engineers close to the project suggests this isn’t a routine maintenance patch.
The update specifically targets file explorer latency, memory allocation bugs tied to the NTFS driver, and a notorious glitch in the Windows Subsystem for Linux that caused CPU throttling under heavy I/O loads. Engineers close to the project tell me the fix for the memory issue was initially slated for the March 2026 security rollup, but was pulled at the last minute after internal tests showed regressions in virtual machine performance. That delay, sources say, led to the accelerated release of KB5089573 as a standalone preview. The rollout, however, has been anything but smooth. Early testers on the Microsoft Update Catalog forums are reporting installation failures with error code 0x800f0922 on devices with specific OEM storage drivers from late 2025. Microsoft has not yet publicly acknowledged those failures as of this writing.
Why this matters for the average user is straightforward: If you’ve experienced unexplained stuttering when opening large folders or random hangs during backup operations, KB5089573 is designed to fix exactly those pain points. It also includes a quiet fix for a kernel-mode driver elevation-of-privilege vulnerability that was disclosed to Microsoft via the Zero Day Initiative in April, though that detail is buried in the changelog. The update is optional, so it will not install automatically unless you check for updates in Windows Update. My advice, based on conversations with incident responders, is to hold off for at least 48 hours if you’re on a managed enterprise fleet. The installation error reports are still being investigated, and a confirmed fix is expected to land in the cumulative update scheduled for the second Tuesday of June. For power users and IT admins comfortable with manual rollbacks, the performance gains are reportedly significant, but the risk calculus remains uncertain until Microsoft updates its release health dashboard.
Source: https://x.com/BleepinComputer/status/2059553707604238756
