Microsoft pulls Windows 11 KB5079391 after install failures spark new update concerns

• Microsoft pulled Windows 11 KB5079391 days after release due to installation failures.
• The error (0x80073712) prevented the update from completing, but systems remained unaffected.
• The issue mainly impacted users who manually installed the preview (optional) update.
• The company may release the Out-of-band update KB5086672 (build 26200.8117) to fix the issue.

Microsoft has pulled the Windows 11 KB5079391 update just days after its release, adding another stumble as the company prepares the April 2026 rollout.

The update was released on March 26 as an optional non-security preview, designed to test fixes before they ship more broadly next month. However, reports of installation failures quickly surfaced, forcing Microsoft to quietly remove the update from Windows Update.

The installation issue

The issue was limited in scope. Systems attempting to install KB5079391 (build 26200.8116) failed with error 0x80073712, so the update never completed. However, computers continued to run normally, with no impact beyond the failed installation.

Related

How to install updates manually on Windows 11

This mainly affected users who actively opt into early updates, meaning most people never encountered the problem. However, the fact that it made it to the public preview stage has raised questions about Microsoft’s testing pipeline.

The root cause hasn’t been confirmed, but this type of error usually points to problems with the update package or missing components during installation. In other words, it’s likely a release issue rather than a deeper flaw on Windows 11.

Microsoft’s response

Microsoft has now pulled the update entirely while it works on a fix. The company is expected to either reissue the update or roll out the contents with the April Patch Tuesday release instead.

However, according to @PhantomOfEarth, the company is expected to roll out the update KB5086672 (build 26200.8117) as another Out-of-band (OOB) update to resolve this issue.

User reactions

Despite the limited impact, the reaction from users has been notably critical, reflecting broader frustration with Windows updates in recent months. On Reddit, sentiment ranges from sarcasm to outright distrust.

One user, brandonb21, wrote, Can they do anything right these days, while ijwgwh added, No they cannot. Others pointed to a pattern, with M4rshmall0wMan questioning, How many faulty Windows updates have released this year? and Raa03842 replying, And it’s only March.

Some users took a more measured view. Vabello noted that this is exactly the purpose of preview updates, writing that issues are meant to surface at this stage before broader rollout. However, others pushed back on that idea, with jManYoHee arguing that Microsoft appears to rely too heavily on its user base for testing.

There’s also confusion about how the update passed earlier validation stages. As trparky put it, How the hell did it get past the Windows Insiders? highlighting concerns about gaps in the testing process.

At the same time, not everyone experienced the issue. Imperius_Fate reported installing the update without problems, suggesting the bug may depend on specific system configurations rather than affecting all devices.

Even so, the takeaway is clear. Confidence in Windows Update remains fragile, and even minor issues like this continue to reinforce that perception, especially after Microsoft recently promised to improve reliability.

Protecting your device

If you want to avoid situations like this, it’s still best to skip preview updates on your main device. I’ve already published a guide that explains how to protect your computer from bad updates, including practical steps to delay risky releases and keep your system stable.

Final thoughts

In the end, KB5079391 didn’t cause major damage, but it didn’t need to. The bigger issue is perception, and right now, every pulled update adds to the growing skepticism around Windows 11 updates.