When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works. Microsoft's official support proves useless as Windows 11 KB5058411 installs fail Sayan Sen Neowin @ssc_combater007 · May 20, 2025 01:52 EDT While Patch Tuesdays bring important security updates for the Windows OS, they can often introduce major bugs. The one this month on Windows 10, KB5058379, that introduced a BitLocker recovery reboot bug, has now been resolved with KB5061768 OOB update. Alongside that, Microsoft also resolved a Windows 11 24H2 upgrade bug related to VBS with a Recovery update KB5059442. Speaking of Windows 11, users are reporting installation failures with the Windows 11 May 2025 Patch Tuesday update KB5058411 as well. Affected users say that these are failing with various error codes like 0x800f0991, 0x800f0991, 0x800f0838, 0x800736b3, and 0x800f081f. User Shukang Liang on the Microsoft support forums writes: "Problem with windows update KB5058411 Installation fails and error code 0x800f0991 comes up." The query has been upvoted by 33 other users at the time of writing. Another user PaulK671 notes 0x800736b3 and 0x800f081f errors as they write: Error 0x800736b3 and 0x800f0838 when installing KB5058411 (Windows 11 24H2 x64 update) 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. Then returns error 0x800f081f. After manually downloading and executing the .msu file from the Microsoft Update Catalog, I get error 0x800f0838. The CBS logs and Event Viewer also show error 0x800736b3. The thread has been upvoted by 19 people at the time of writing. Meanwhile, user Jenny-XS says they came across the 0x800f081f error code when trying to install the May '25 Patch Tuesday. Microsoft recently published a support article with a long list of Windows 11 and 10 hex error codes that lead to installation failures. Unfortunately, though, none of the codes reported by users match with the ones Microsoft has provided workarounds for. Thus, it looks like Microsoft will have to update its list sooner rather than later as clearly many hex error codes are still pending and are due for addition to its support documentation. Interestingly, one of the commenters on the 0x800f0991 error thread, ScotBirch, added that they were able to resolve the issue using the "Fix problems using Windows Update" option. Microsoft had detailed what that is and how it works back in December 2024. You can read the linked article to find out more and see if perhaps it fixes your issues too. Tags Report a problem with article Follow @NeowinFeed

When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works. Windows 10 emergency update KB5061768 fixes BitLocker boot loops Taras Buria Neowin @TarasBuria · May 19, 2025 15:10 EDT As promised, Microsoft is rolling out an out-of-band emergency update for Windows 10 to address problems with Intel-based systems booting into BitLocker recovery due to LSASS issues caused by KB5058379. The company recently acknowledged a known issue on devices with Intel Trusted Execution Technology (TXT) on 10th-gen and later systems and promised to release a fix as soon as possible. The company did not take too long to address the issue, and the necessary fix is now available on the Microsoft Update Catalog as KB5061768, with build numbers 19044.5853 (Windows 10 version 21H2) and 19045.5853 (Windows 10 version 22H2). Here is the changelog with a single fix: [OS Security (Known Issue)] Fixed: A known issue on devices with Intel Trusted Execution Technology (TXT) enabled on 10th generation or later Intel vPro processors. On these systems, installing the May 13, 2025, Windows security update (KB5058379) might cause the Local Security Authority Subsystem Service (LSASS) process to terminate unexpectedly, triggering an Automatic Repair prompting for the BitLocker recovery key to continue. In the updated post on the Windows Health Dashboard website, Microsoft says that KB5061768 is recommended for those who use affected systems and have not yet deployed KB5058379 (May 2025 security update). It will prevent BitLocker problems from happening. As for systems that already cannot boot due to BitLocker loops, Microsoft suggests the following: To start Windows, temporarily disable Intel VT for Direct I/O (also known as VTD or VTX) and Intel Trusted Execution Technology (TXT) in your BIOS / UEFI settings. This step will require entering your BitLocker recovery key. Install update KB5061768 via the Microsoft Update Catalog. After restarting Windows, return to your BIOS / UEFI settings and re-enable Intel VT for Direct I/O (also known as VTD or VTX) and TXT. (This step will require entering your BitLocker recovery key.) As for known bugs, there is one issue with the Noto font (introduced in the recent preview update as a fallback font): text can appear blurry or unclear in Chrome, Edge, and other Chromium-based browsers in certain languages like Chinese, Japanese, and Korean when the display scaling is set to 100% (96 DPI). Microsoft is investigating this problem, and users can mitigate it by setting the display scaling to 125% or higher. KB5061768, which fixes BitLocker boot loop issues, is only available in the Microsoft Update Catalog. Microsoft is not rolling it out via Windows Update, so grab it using this link. Tags Report a problem with article Follow @NeowinFeed