Microsoft Temporarily Stops Windows 11 Update KB5079391 Deployment
Microsoft's latest update for Windows 11, KB5079391, has been temporarily halted due to problems encountered during installation. This update, meant for versions 24H2 and 25H2, was supposed to bring several improvements, but many users are now unable to install it because of error 0x80073712. The error reports indicate missing or corrupt files that prevent the update from completing successfully.
Details About The Update and Its Issues
The update was released on March 26, offering new OS Builds 26100.8116 and 26200.8116. Microsoft quickly responded to reports of installation failures, updating its support document on March 27th to acknowledge the known problems. They’ve temporarily limited its availability while they work on fixes, thus affecting many users trying to improve their system or access new features.
Current Status and Expected Resolution
According to Microsoft, users who look for KB5079391 in the optional updates section might not see it, which is because the rollout pause prevents its distribution via Windows Update. This isn’t a problem with individual PCs, but rather a company-wide decision to pause installation until the fault is fixed. Windows Central reported that the update has effectively been pulled back after installation issues surfaced, turning what should have been a straightforward update into a short-lived event.
What Was Included in the Update?
- Improvements to File Explorer, especially unblocking downloaded files
- Support for monitors that can report refresh rates higher than 1000 Hz
- Fixes for specific error messages during system scans (sfc /scannow)
- Enhanced reliability of Windows Hello fingerprint recognition on some devices
- Changes affecting Safe Mode, audio functions, Voice Access, and Group Policy in Start Menu
- Adjustments to Remote Desktop PowerShell management
Next Steps and Microsoft's Guidance
Currently, Microsoft has no workaround or updated build available for KB5079391. They are focusing on investigating the issue and have paused further distribution. Users affected by this problem will have to wait for Microsoft to resume or publish a corrected update, or incorporate fixes into subsequent cumulative updates. This situation emphasizes the importance of cautious deployment of preview patches and the need for vigilant testing.
Sources: www.microsoft.com, www.windowscentral.com