Windows 11 error 0x800f0991 is a servicing failure that can appear while Windows 11 24H2 is downloading or installing a cumulative update. Microsoft does not currently list this code in its common Windows Update error table, so it does not have one confirmed cause or one guaranteed fix.
The reliable approach is to repair the component store, run System File Checker, reset the Windows Update cache if necessary, and then install the correct update manually. If those steps fail, the CBS log usually provides more useful evidence than the error code itself.
Before fixing 0x800f0991
First check the installed Windows version and system type. Press Win + R, enter winver, and select OK. You can check the processor architecture at Settings > System > About > System type.
Do not assume that every failure involving 24H2 has the same cause. Microsoft documents related servicing errors, including 0x800f0831, 0x800f081f, and 0x800f0906, but does not assign an official description to 0x800f0991. Also, the documented KB5089549 installation issue is 0x800f0922, associated in that release documentation with low EFI System Partition space—not with 0x800f0991.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →#1 Best Overall
- Does Not Fix Hardware Issues - Please Test Your PC hardware to be sure everything passes before buying this USB Windows 11 Software Recovery USB.
- Make sure your PC is set to the default UEFI Boot mode, in your BIOS Setup menu. Most all PC made after 2013 come with UEFI set up and enabled by Default
- Does Not Include A KEY CODE, LICENSE OR A COA. Use your Windows KEY to preform the REINSTALLATION option
- Free tech support
1. Run the Windows Update troubleshooter
Windows 11 has moved the troubleshooter from the old Windows 10 location. Use this path:
- Open Start > Settings.
- Select System > Troubleshoot > Other troubleshooters.
- Find Windows Update and select Run.
- Apply any recommended repair and restart the PC if Windows requests it.
Retry the update after restarting. This step is worth trying, but it may not repair a damaged component store or a package with a missing prerequisite.
2. Repair the Windows component store with DISM
Microsoft’s main repair command for Windows Update problems is DISM with /RestoreHealth. Run it from an elevated Command Prompt:
- Select Start and type Command Prompt.
- Right-click Command Prompt and select Run as administrator.
- Select Yes at the User Account Control prompt.
- Run this command:
DISM.exe /Online /Cleanup-Image /RestoreHealth
DISM normally obtains the repair files through Windows Update or Microsoft Update. The scan can remain at a particular percentage for a while; do not close the window simply because progress appears slow. Wait for a completion message.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →If the computer cannot reach Windows Update, use a repair source from another installation running the same operating-system version:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:\\<servername>\c$\windows /LimitAccess
Replace <servername> with the source computer’s name. The repair source must match the installed Windows version closely enough to provide the required files; using an image from a different Windows version is not the documented equivalent.
3. Run System File Checker, restart, and retry
After DISM completes successfully, run System File Checker in the same elevated Command Prompt:
Recommended Free Tools
sfc /scannow
Wait until SFC reaches 100 percent. Then restart Windows, even if SFC reports that it found no integrity violations. Pending actions from an earlier update may need to finish during the restart.
After Windows starts again, open Settings > Windows Update and select Check for updates. Microsoft’s repair sequence places SFC after DISM and instructs you to try Windows Update again afterward.
4. Reset Windows Update’s cache and services
A damaged download cache or a locked catalog database can prevent a package from being staged. The following Microsoft Q&A sequence stops the relevant services, renames the cache folders, starts the services again, and resets Winsock.
Open Command Prompt as administrator, then run these commands in order:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
net stop wuauserv
net stop bits
net stop cryptSvc
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
netsh winsock reset
Restart Windows when the commands finish, then try the update again. Renaming is safer than deleting: Windows creates new cache folders when the services run. If the catroot2 rename fails, confirm that cryptSvc was stopped before trying again.
This is community guidance published through Microsoft Q&A, not a guarantee that every 0x800f0991 case will be resolved by resetting the cache.
5. Install the update manually from Microsoft Update Catalog
Manual installation can bypass a problem with the Windows Update Agent, but it does not make an incompatible package suitable. You need the exact KB number shown in Settings > Windows Update > Update history, or in the failed-update message.
- Open the Microsoft Update Catalog.
- Enter the KB number in the search box and select Search.
- Choose the package whose Windows version and architecture match your installation.
- Select Add beside the package.
- Select View basket, then Download.
- Select Browse, choose a destination, and select Continue.
- When the download finishes, select Close.
- Open the downloaded MSU file and follow the installation prompts.
Check the package’s Applies To information before downloading. Common reasons for a manual installation failure include:
| Failure | What to check |
|---|---|
| Wrong architecture | Confirm x64 versus ARM64 in Settings > System > About. |
| Wrong Windows release | Confirm that the package applies to Windows 11 24H2 and your installed build. |
| Package superseded | A newer cumulative update may have replaced the KB you selected. |
| Already installed | Check Settings > Windows Update > Update history. |
| Missing prerequisite | Read the update’s Microsoft support article and install required prerequisite packages first. |
6. Install an MSU package with DISM
If opening the MSU package does not work, Microsoft documents installing it from an elevated Command Prompt:
Free tools Windows power users keep installed
One-click scans. No signup required.
DISM /Online /Add-Package /PackagePath:C:\Packages\update.msu
Rank #2
- 1. COMPATIBLE WITH WINDOWS 11, 10, 8.1 & 7 Designed for compatible 64-bit PCs and laptops that support USB booting. Works with Windows 11, Windows 10, Windows 8.1 and Windows 7 installation and recovery options.
- 2. INSTALL, REINSTALL & REPAIR Provides access to installation and recovery options for startup failures, boot errors, system crashes, failed updates, system repair and reinstallation. Results depend on the condition of the computer and the cause of the problem.
- 3. READY-TO-USE BOOTABLE USB Reusable installation and recovery media that helps eliminate the need to download large system files or create bootable media yourself. Insert the USB drive, open the computer’s boot menu and select the appropriate installation or recovery option.
- 4. HELP KEEP OLDER PCS USEFUL Refresh, reinstall or maintain a compatible older computer before deciding whether replacement is necessary. Suitable for home computers, office workstations, PC enthusiasts and technicians who regularly work with supported systems.
- 5. IMPORTANT COMPATIBILITY & LICENSE INFORMATION Supports compatible 64-bit computers with UEFI or Legacy BIOS USB booting. No Windows license, activation key or product key is included. Activation may require an existing digital license or a separately purchased valid product key. Back up important files before installation or repair.
Replace the path with the actual location and filename. For example, if the file is in C:\Packages, use its complete name rather than the placeholder.
This method can bypass Windows Update Agent applicability checks, but it still requires a package that matches the installed Windows version, architecture, servicing state, and prerequisites.
7. Special case: installing KB5089549 on Windows 11 24H2
Microsoft’s May 12, 2026 documentation lists KB5089549 for Windows 11 version 24H2, all editions. The 24H2 package takes the operating system to build 26100.8457. Do not treat it as the latest update indefinitely; check Microsoft’s current Windows 11 24H2 update-history or release-health page before using it as your target package.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteFor a 24H2 x64 installation, Microsoft documents this prerequisite order when installing the individual MSU files:
windows11.0-kb5043080-x64_953449672073f8fb99badb4cc6d5d7849b9c83e8.msu
windows11.0-kb5089549-x64_9a542b5813b003374532dceeba49b7e07c3fc2fb.msu
Install KB5043080 first, followed by KB5089549. For ARM64, use the ARM64 versions of both packages in the same order. Do not use an x64 filename on an ARM64 system.
Alternatively, put all required MSU files in one folder and run the KB5089549 package through DISM. DISM can search that folder for prerequisites:
DISM /Online /Add-Package /PackagePath:c:\packages\windows11.0-kb5089549-x64_9a542b5813b003374532dceeba49b7e07c3fc2fb.msu
Use the ARM64 filename instead if the installation is ARM64.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.8. Check CBS.log when the normal fixes fail
If DISM and SFC complete successfully but the update still returns 0x800f0991, stop repeating the same commands and inspect the servicing log:
%windir%\Logs\CBS\CBS.log
On a normal installation, this is C:\Windows\Logs\CBS\CBS.log. Open it in Notepad or copy it to the desktop first if permissions prevent direct access. Search for terms such as error, failed, 0x800f0991, HRESULT, and CSI.
The log can reveal a missing package, a failed prerequisite, a component-store problem, or a file-access conflict. These cases are not interchangeable. In particular, a non-Microsoft filter driver—including some antivirus software—can cause a sharing violation while Windows is servicing a file. In that situation, DISM and SFC may both report success because the component store is healthy, yet the update still cannot replace or access the required file.
For a suspected sharing violation, Microsoft’s investigation uses a clean restart and Process Monitor, then compares the failed file access with the final entries in CBS.log. Avoid permanently disabling security software; if testing requires a temporary change, follow the product vendor’s supported procedure and restore protection immediately.
When to stop troubleshooting locally
Escalate or use Microsoft support if:
- DISM reports that the source files could not be found and you do not have a matching repair source.
- The CBS log repeatedly identifies a missing or corrupt package that manual installation cannot replace.
- The update fails with different servicing errors after every reset.
- The PC is managed by an organization, WSUS, Intune, or third-party endpoint software.
- Several cumulative updates fail, suggesting a broader servicing-stack or storage problem.
Keep the exact KB number, Windows build from winver, architecture, DISM and SFC results, and relevant CBS.log entries. That information is substantially more useful than reporting only the hexadecimal error code.
FAQ
What does Windows 11 error 0x800f0991 mean?
Microsoft does not currently publish an official description or single cause for 0x800f0991. It should be treated as an unresolved Windows servicing or update-installation failure until the CBS log identifies the specific problem.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsWhere is the Windows Update troubleshooter in Windows 11 24H2?
Go to Start > Settings > System > Troubleshoot > Other troubleshooters. Find Windows Update and select Run. The older Settings > Update & Security path is Windows 10 terminology.
Should I run SFC or DISM first?
Run DISM first with DISM.exe /Online /Cleanup-Image /RestoreHealth. When it finishes, run sfc /scannow, restart Windows, and retry Windows Update.
Can I fix 0x800f0991 by deleting SoftwareDistribution?
Resetting the Windows Update cache can help, but Microsoft Q&A guidance renames SoftwareDistribution and Catroot2 after stopping the relevant services rather than deleting them. It is a possible repair, not a guaranteed fix.
Is 0x800f0991 the same as 0x800f0922?
No. They are different error codes. Microsoft documented a KB5089549 issue involving 0x800f0922 and limited EFI System Partition space; that documentation does not establish the same cause for 0x800f0991.
Which log should I check after the fixes fail?
Check %windir%\Logs\CBS\CBS.log, normally C:\Windows\Logs\CBS\CBS.log. Search for the error code, failed package names, HRESULT values, and sharing-violation messages.
The Bottom Line
Start with the current Windows 11 troubleshooter, then run DISM.exe /Online /Cleanup-Image /RestoreHealth, followed by sfc /scannow. Restart before retrying Windows Update. If the failure remains, reset the update cache and install the exact matching KB manually from Microsoft Update Catalog. Do not assume that 0x800f0991 has one universal cause—the CBS log is the next step when the standard repairs do not work.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
