Microsoft yanks windows 11 patch after brick loop goes viral

Redmond slammed the brakes on its newest Windows 11 cumulative update last night after KB5079391 locked an undisclosed slice of PCs in a failed-install reboot cycle.

The glitch, tagged error 0x80073712, surfaced within hours of Tuesday’s rollout to 24H2 and 25H2 machines. Microsoft’s terse service note admits the failure rate crossed an internal red line, forcing a global pause that vanished the package from every Windows Update mirror.

What the phantom patch actually promised

Insiders who snagged the release before the pullback got a trove of fringe-grade goodies: Narrator finally learned to announce emoji by short name, Smart App Control whitelists updated in real time, and the kernel unlocked refresh rates north of 1000 Hz—a spec that matters only to the eight humans who already own an 1080-panel from ZisWorks. For everyone else, the payload was standard housekeeping: .NET tweaks, Bluetooth power trims, and the usual post-month-end certificate root refresh.

Now those fixes sit in limbo while Microsoft’s servicing team traces the corruption to a component store clash that appears when a dormant 22H2 language pack stub is still resident. The company won’t quantify “how many is too many,” but telemetry from Update Compliance shows the failure cluster mapped to machines that upgraded from early Insider dev channels—exactly the cohort most likely to hoard obsolete pack files.

Instead of the yanked patch, users today see KB5085516, a spot-fix that unbreaks Microsoft-account sign-ins inside Mail, Calendar, and the Tips app. It delivers none of the headline features, but at least it installs without looping.

Why rushing the red button matters

This is the second non-security bundle Microsoft has pulled this quarter; March’s servicing stack update met the same fate on Arm devices. The cadence undercuts the firm’s claim that the new annual moment model would reduce “update friction.” Each retraction erodes the trust currency the company spent years rebuilding after the Vista era.

Enterprise admins feel the sting twice: they already approved 9391 for pilot rings, and now must yank it from WSUS pipelines, a process that still requires manual SQL incantations. For consumers, the takeaway is blunt—wait 72 hours before clicking “Download now,” no matter how shiny the changelog reads.

Microsoft says a refreshed payload “will reappear when confidence metrics recover,” but offered no calendar hint. Translation: the fix will ship when telemetry graphs flatten, not when the code is actually repaired. Until then, 1000 Hz monitors will keep running at pedestrian 240 Hz, and Narrator will keep mispronouncing the melting-face emoji. The digital future, paused at 0% complete.