
Recent Windows Updates: Issues and Fixes
Patch Tuesdays are crucial for delivering essential security updates to the Windows operating system. However, they can sometimes lead to unintended problems. The recent update for Windows 10, known as KB5058379, was problematic due to a bug affecting BitLocker recovery, which has since been resolved by the out-of-band update KB5061768. In a similar vein, a Recovery update, KB5059442, has addressed a bug concerning the Virtualization-Based Security (VBS) for Windows 11, specifically related to the version 24H2 upgrade.
Installation Complications with Windows 11 Updates
Users of Windows 11 are encountering various installation failures with the recent May 2025 Patch Tuesday update, KB5058411. Affected individuals have reported multiple error codes, such as 0x800f0991
, 0x800f0838
, 0x800736b3
, and 0x800f081f
.
For instance, user Shukang Liang detailed on the Microsoft support forums their trouble with the update, stating:
Problem with Windows Update KB5058411
Hello community,
I’m experiencing a persistent issue when trying to install the KB5058411 cumulative update for Windows 11 Version 24H2 (x64), released on May 13, 2025 (OS Build 26100.4061).
Initial symptoms:
- Windows Update stalls at 6% download.
- It then returns error
0x800f081f
.- After manually downloading and executing the.msu file from the Microsoft Update Catalog, I receive error
0x800f0838
.- The CBS logs and Event Viewer also show error
0x800736b3
.
This forum post has garnered support from 33 users so far, highlighting the widespread nature of this issue.
Error Reports from Other Users
Similarly, another user named PaulK671 reported the same errors, which can be seen in their thread detailing the errors 0x800736b3
and 0x800f081f
. Meanwhile, user Jenny-XS has also experienced the 0x800f081f
error when attempting to install the KB5058411 update.
Microsoft’s Support Challenges
Recently, Microsoft released a support document listing numerous hex error codes that commonly lead to installation failures in Windows 10 and 11. However, it appears that the errors reported by users do not align with the codes for which Microsoft has provided workarounds. This suggests that Microsoft may need to expand its support resources as these unresolved issues continue to mount.
Interestingly, a commenter named ScotBirch shared their successful resolution of the 0x800f0991
error by utilizing the “Fix problems using Windows Update”feature. Microsoft had released guidance on this option back in December 2024, which could be a helpful avenue for those facing similar issues.
For anyone looking for further insights or guidance, you can explore the original article discussing these challenges here.
Leave a Reply