The Windows 11 KB5079391 update was pulled from circulation within hours of its March 26, 2026 release after users encountered repeated installation failures. Microsoft temporarily halted rollout of this optional preview update for Windows 11 versions 24H2 and 25H2 due to error 0x80073712, which prevented systems from completing the installation process.
Key Takeaways
- Microsoft pulled the Windows 11 KB5079391 update on March 26, 2026, just 1–2 hours after release due to installation errors
- Error 0x80073712 indicated missing assembly files in the WinSxS folder, blocking installation on affected systems
- The update was intended to fix a year-long bug affecting network-share installations of .msu files
- Some users successfully installed the update without issues, suggesting the problem affected a subset of devices
- Microsoft has not announced a resumption timeline or confirmed the update will be re-released
What Went Wrong With Windows 11 KB5079391 Update
The Windows 11 KB5079391 update encountered error 0x80073712 during installation, displaying the message: “Some update files are missing or have problems. We’ll try to download the update again later.”. The error pointed to missing or corrupted assembly files in the WinSxS (Windows Side-by-Side) system folder, preventing the update from completing. Microsoft confirmed to Windows Latest that it pulled the update and is investigating the root cause internally, but provided no timeline for resolution.
The rollout pause was not universal—some users, including tech journalists, installed the update successfully on March 26 without encountering the error. This inconsistency suggests the problem affected specific device configurations or system states rather than all Windows 11 installations. Microsoft’s statement acknowledged the issue: “To prevent additional impact while the issue is investigated, Microsoft has temporarily limited the availability of this update”.
Why Windows 11 KB5079391 Update Mattered
The Windows 11 KB5079391 update was designed to fix a persistent installation bug that had plagued Windows users since May 28, 2025. The underlying issue (ERROR_BAD_PATHNAME) prevented .msu files from installing correctly when accessed from network-shared folders, forcing users to copy files locally before installation. This limitation had persisted for nearly a year despite Microsoft’s earlier Known Issue Rollback in September 2025 and Group Policy workarounds for managed systems.
The timing of KB5079391’s failure is particularly problematic. It arrives just days after Microsoft pledged to improve Windows Update reliability on March 17, 2026. The update’s rapid withdrawal underscores the company’s ongoing struggle to prevent update-related regressions. Users attempting to install Windows 11 KB5079391 faced the irony of a reliability fix that created new reliability problems.
What Users Can Do Now
Microsoft has not provided an official workaround specifically for the Windows 11 KB5079391 installation error. However, for users still experiencing the underlying network-share installation bug (ERROR_BAD_PATHNAME), the recommended approach remains copying .msu files to local storage before installation. Some users have reported success with clearing the SoftwareDistribution folder or restarting Windows Update services, though these are unofficial fixes not endorsed by Microsoft.
Alternatively, users can attempt installation through the Microsoft Update Catalog or Media Creation Tool, which bypass the standard Windows Update mechanism. Given that Microsoft has not announced a resumption date for the Windows 11 KB5079391 update and worst-case scenarios suggest it may not re-release at all, users should not expect this particular fix to become available through normal update channels in the near term.
Broader Pattern of Windows Update Issues
The Windows 11 KB5079391 incident fits into a troubling pattern of update-related problems at Microsoft. Earlier in March 2026, a separate Windows update broke Microsoft account sign-in for inbox applications, compounding user frustration. These recurring issues suggest that Microsoft’s testing procedures may not be catching regressions before rollout, even for optional preview updates with narrower audiences.
The distinction between optional and critical updates matters here. The Windows 11 KB5079391 update was optional, meaning users could decline it without losing security patches. However, the rapid withdrawal still signals that Microsoft’s preview update validation process has gaps. Users on the latest 24H2 and 25H2 builds—who tend to be early adopters willing to test pre-release changes—were the ones affected.
Is the Windows 11 KB5079391 update still available?
No. As of March 28, 2026, the Windows 11 KB5079391 update is no longer available through Windows Update. Microsoft temporarily limited its availability after error 0x80073712 prevented installation on affected systems. The update was only offered for approximately 1–2 hours on March 26 before being pulled.
What does error 0x80073712 mean?
Error 0x80073712 indicates missing or corrupted assembly files in the WinSxS folder, which is critical to Windows system integrity. When Windows cannot locate required system files during an update, it cannot proceed with installation and displays this error. The message directs users to retry the update later, but in this case, the update itself was withdrawn.
Will Microsoft re-release the Windows 11 KB5079391 update?
Microsoft has not announced plans to re-release the Windows 11 KB5079391 update. The company stated it is investigating the root cause but provided no timeline for resolution or confirmation that the update will eventually become available again. Users should not assume the update will return to Windows Update in its current form.
The Windows 11 KB5079391 failure demonstrates that even optional preview updates require rigorous testing before rollout. Microsoft’s decision to pull the update quickly prevented wider damage, but the underlying question remains: how did an update intended to improve installation reliability manage to break installations instead? Until Microsoft publishes a detailed post-mortem, confidence in Windows Update stability will remain fragile.
This article was written with AI assistance and editorially reviewed.
Source: Windows Central
