Microsoft halts Windows 11 update after users report installation errors

[Alfonso Maruccia]

Facepalm: Microsoft has temporarily halted the rollout of KB5079391, a Windows 11 update intended to deliver important changes to the operating system. Soon after receiving the update, users began encountering issues while trying to install the sizable patch. The paused rollout suggests that a significant number of customers are affected, a concerning sign for Microsoft's broader strategy to improve the Windows 11 experience.

According to the official KB5079391 change log, the rollout was paused because users are seeing an "error 0x80073712" message during installation. Microsoft explains that this error occurs when files are missing or corrupted, preventing the update from completing successfully.

In short, Microsoft released its latest non-security update in an incomplete or corrupted state, potentially disrupting Windows 11 for a large number of users. While the installation process appears to be fundamentally broken, some users have reported successfully downloading and installing the update on their systems.

KB5079391 introduces a long list of changes and improvements across many Windows 11 components. The update adds support for monitors with refresh rates above 1000Hz, an enhanced File Explorer experience, a redesigned Settings page, and much more. Additionally, the patch brings new AI-related features to both Copilot+ PCs and traditional Windows 11 machines.

The features and improvements in KB5079391 are expected to become part of the standard Windows experience, and Microsoft is likely to fix the installation issues affecting the update. What seems less likely to change anytime soon is Microsoft's ongoing struggle to address all the problems affecting the Windows 11 platform.

The company recently stated that Windows 11 is undergoing a major overhaul, in response to the growing number of complaints from both enterprise and home users. This effort appears to focus on building native applications rather than relying on heavy and unreliable web wrappers. However, as the KB5079391 rollout demonstrates, Redmond will need to do far more than eliminate wrappers to prevent users from jokingly referring to Windows – or other Microsoft software – as "Microslop."

Image credit: Joshua Hoehne

Permalink to story:

Microsoft halts Windows 11 update after users report installation errors

 

[GeoffreyA]

Get big QA department + testers trying to break Windows + give updates time to bake == update problems gone.

Old programming aphorism: better to build system from scratch than update shaky one. Windows terms: go back to quality version of NT, then reprogram changes properly.

 

[Alfonso Maruccia]

Get big QA department + testers trying to break Windows + give updates time to bake == update problems gone.

Old programming aphorism: better to build system from scratch than update shaky one. Windows terms: go back to quality version of NT, then reprogram changes properly.

"Nah. Best I can do is giving you more vibe-coded slop."

 

[wiyosaya]

Get big QA department + testers trying to break Windows + give updates time to bake == update problems gone.

Old programming aphorism: better to build system from scratch than update shaky one. Windows terms: go back to quality version of NT, then reprogram changes properly.

As an old-timer who used NT, I might agree with you even though updates for NT were notoriously hit and miss; the had update failures back than at a far higher rate.

Back to the future, what you are suggesting is unlikely to happen. The code for 11 is likely too much different from the code for NT and such a tack would almost certainly take a substantial amount of time if it is even possible.

 

[p51d007]

Patch Tuesday or any OOB patch should be renamed BSOD Tuesday.
Oh wait, they can't...Blue Screen of Death is already dead.

 

[Watzupken]

Nothing new here to see. Usual Microsoft behavior.

 

[Axiarus]

Running Arch. Thing breaks from last nights update. Thing is fixed next day.

 

[GeoffreyA]

As an old-timer who used NT, I might agree with you even though updates for NT were notoriously hit and miss; the had update failures back than at a far higher rate.

Back to the future, what you are suggesting is unlikely to happen. The code for 11 is likely too much different from the code for NT and such a tack would almost certainly take a substantial amount of time if it is even possible.

No doubt, updates were worse prior to Vista. I meant all versions of NT, specifically 10. It's stable, recent, and contains all the performance improvements from 8. In a fantasy world, Microsoft would realise it's bad for the future stability and maintenance of Windows to continue working on a (plausibly) low-quality 11 codebase. Rather, in this fantasy, they go back, start stripping away feature creep, then reimplement, very strictly, a subset of changes from 11: only what's good; if it can be cut, cut it. Do the performance testing on old 2010-era hardware so that modern computers cannot mask bad programming. In Redmond HQ, put big posters up saying, "Modern, bad. Old is gold." All right, the last one is a joke, but in reality, none of this will ever happen.

 

[BobHome]

I wonder what broke it this time. Maybe... "Additionally, the patch brings new AI-related features to both Copilot+ PCs AND traditional Windows 11 machines."