How to fix Install error - 0x800f0991 [2026-01 Security Update (KB5074109) (26200.7623)] keeps failing

Amratpal, the error 0x800f0983 was shown to lots of people after trying to install the KB5077181 February monthly patch for Windows 11. Later, the error switched to the number with 991 at the end, you just got the same problem a month earlier than we did for some reason. All these people including me with my Vivobook tried all possible deletion of SoftwareDistribution, catroot2 folders, restarting WU related services, SFC, DISM with Scanhealth, Checkhealth, Restorehealth, without source, with source at Windows Update, and even with the full ISO source, and the MSU patch from Microsoft Catalog. Everything fails.

However, all ten+ people who have tried have succeeded a miraculous cure using a new Windows 11 tool. It is in Settings, System (in the left sidebar), Recovery (a right sidebar option), and "Fix Problems Using Windows Update" (second tool in the right sidebar). Click "reinstall now" and don't be afraid of the terrifying verb. It preserves apps, files, and settings. Except for asking whether you want an automatic restart at the end, it is nothing else than a Windows Update process (and has a similarly robust rollback cure if something goes wrong in the middle), just the patch is called "Windows 11 Recovery Edition". And it takes twice as long because it is really installing even things that the regular light Windows Update (incorrectly) decides that your PC does not need (that is really why these 800f errors appear). For me, a fast WiFi downloaded it in 10 minutes, followed by 55 minutes "installing" inside Windows, otherwise like a regular patch, and just 5 minutes of black-screen installation phase outside Windows, plus 2 extra minutes after the first login to a user profile. And when it was completed, I had the newest post-February-patch level of Windows 11.

You should simply do it, trust me, you are no longer a beta tester, this tool simply works (10 out of 10 confirm) and frankly speaking, it may be better to use it after any error of Windows Update.

Amratpal Singh FCCA ACA BSc BFP,

I am checking in to see if you have managed to resolve the 0x800f0991 update error with the steps provided. As a quick summary, this error stems from XML corruption within the update components. The primary fix is to stop the Windows Update services and rename the C:\Windows\SoftwareDistribution and C:\Windows\System32\catroot2 folders to force a completely fresh download of the update metadata. If that simpler method did not clear the blockage, the In-Place Upgrade, executed by running setup.exe from a mounted Windows ISO is the definitive method to repair the underlying system servicing stack while preserving your files and applications.

If the issue has been successfully resolved, please consider accepting the answer as it helps other people sharing the same question benefit too. Thank you!

VP

Hi Amratpal Singh FCCA ACA BSc BFP,

The error code 0x800f0991 typically translates to CBS_E_XML_PARSER_FAILURE, indicating that the Component Based Servicing (CBS) engine is encountering corrupted XML metadata either within the update package itself or, more likely, within your local component store. Since you have been facing this for a month, the corruption has likely settled into the SoftwareDistribution cache or the WinSxS folder, preventing the Windows Update Agent from correctly validating the manifest for KB5074109. Dell is correct that this is an Operating System servicing stack issue rather than a hardware fault.

You should first attempt a complete reset of the Windows Update components to force a reconstruction of the update database. Open Command Prompt as an Administrator and execute the commands net stop wuauserv, net stop cryptSvc, net stop bits, and net stop msiserver to halt all related services. Navigate to C:\Windows\SoftwareDistribution and rename this folder to SoftwareDistribution.old, then navigate to C:\Windows\System32\catroot2 and rename it to catroot2.old. Once renamed, restart the services using net start for the four services you previously stopped. This purges the cached update files and forces the system to re-download a fresh copy of the update metadata, bypassing any local XML corruption in the cache.

If the update still fails with the same error after the reset, the corruption resides in the system image itself, which standard DISM commands often fail to repair for this specific error code. The most reliable fix in this scenario is an In-Place Upgrade (Repair Install). Download the Windows 11 ISO corresponding to your architecture from the Microsoft website, mount the ISO file by double-clicking it, and run setup.exe. Proceed through the setup wizard and ensure you select the option to "Keep personal files and apps." This process reinstalls the core Windows system files and the servicing stack while retaining your data, effectively overwriting the corrupted libraries causing the parser failure.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

VP