Fix Install Error – 0x800f0991 on Windows

Windows Update error 0x800f0991 is usually resolved by restarting Windows, checking the failed KB number, repairing the Windows component store with DISM and SFC, and retrying the update. If it still fails, reset the Windows Update cache or install that exact KB from the Microsoft Update Catalog. Stop before deleting files if BitLocker recovery or drive errors appear.

For more help with this topic, use the Computers Internet guides.

Check the failed update and basic Windows conditions

Windows Update error 0x800f0991 should first be tied to a specific failed update, because the recovery path depends on whether the failure affects one cumulative update or every update.

1. Open Settings > Windows Update > Update history.
2. Expand Quality updates and record the failed KB number, such as KBxxxxxxx.
3. Restart the PC, then return to Settings > Windows Update and select Check for updates.
4. Check Settings > System > Troubleshoot > Other troubleshooters, run Windows Update if it is available, and apply only the recommended repair.

Success means the update changes to Installing, Pending restart, or Successfully installed. If the same KB immediately returns with 0x800f0991, continue with component repair.

For comparison, the related Windows Update error 0x80070306 also uses staged update and repair checks, but its code and likely failure point are different.

If another update code appears after restarting, compare its recovery path with Windows Update error 0x80070306 before changing system files.

Repair Windows components with DISM and SFC

Windows component repair checks whether damaged servicing files are preventing the update from being applied. Microsoft Learn documents DISM as the tool for repairing the Windows image, while SFC checks protected system files afterward.

1. Right-click Start and select Terminal (Admin) or Windows PowerShell (Admin).
2. Run this command and wait for it to reach 100%:

   DISM /Online /Cleanup-Image /RestoreHealth

3. When DISM finishes, run:

   sfc /scannow

4. Restart Windows, then retry the failed update.

DISM should finish with a repair or no-corruption message, and SFC should report either that it found no integrity violations or that it repaired files. If SFC says it could not perform the requested operation, restart and run it again once. If DISM cannot find source files, stop repeating the command and use matching Windows installation media or Microsoft Support.

Reset the Windows Update download cache

If system files are healthy but the same update still fails, damaged or incomplete cached update data is a reasonable next suspect. This procedure rebuilds the update cache without removing personal documents.

1. Open Terminal (Admin).
2. Run each command separately:

net stop wuauserv
net stop bits
net stop cryptsvc
net stop msiserver

3. Open File Explorer and go to C:\Windows. Rename SoftwareDistribution to SoftwareDistribution.old.
4. Go to C:\Windows\System32 and rename catroot2 to catroot2.old.
5. Return to Terminal and start the services again:

net start msiserver
net start cryptsvc
net start bits
net start wuauserv

6. Restart the PC and select Check for updates.

Windows should create fresh replacement folders. If a folder cannot be renamed, one of the services is still active; stop there, restart Windows, and do not force deletion.

Install the exact failed KB manually

Manual installation is useful when Windows Update repeatedly fails on one known KB while the rest of the system works normally.

1. Search the Microsoft Update Catalog for the exact KB number recorded in Update history.
2. Choose the package matching the PC’s Windows release, processor architecture, language, and package type.
3. Download the package, close open programs, and run the downloaded installer.
4. Restart when prompted, even if the installer appears to finish without an immediate restart.

Verify the result in Settings > Windows Update > Update history. The KB should appear under the appropriate update category without a failed status. If the catalog offers several versions and you cannot identify the correct one, do not guess; return to Windows Update or use Microsoft Support.

Use recovery options when 0x800f0991 keeps returning

Persistent 0x800f0991 after component repair, cache reset, and a matching manual package points to a deeper servicing or installation problem rather than a normal download failure.

1. Check Settings > System > Recovery for Fix problems using Windows Update or a repair reinstall, if that option is offered by the installed Windows version.
2. Before using reset or reinstall options, back up documents, browser data, and any files stored only on the PC.
3. Review Settings > Windows Update > Update history for whether multiple unrelated KBs are failing.
4. If several updates fail, or Windows reports missing source files, contact Microsoft Support or the PC manufacturer with the KB number, Windows edition, and the exact DISM and SFC result.

Do not continue with repeated resets if Windows cannot boot normally, BitLocker recovery appears unexpectedly, or storage diagnostics report errors. Protect the data first and use a qualified repair path.