Fix Error Code 0x800f0806 in Windows

Error code 0x800f0806 stops Windows Update from installing certain updates, usually .NET Framework or driver packages, and it appears when the update service cannot verify or replace a system file. The fix is to run the built-in DISM and System File Checker tools, then reset the Windows Update components; these steps resolve the majority of cases. Below is a detailed walkthrough plus the background on why this error happens and what to do if the standard fixes do not work.

What Error 0x800f0806 Means

Windows Update returns 0x800f0806 when the update installation fails during the replacement or registration phase. The error text usually reads “0x800f0806� with no additional message, or it appears inside the Windows Update history with a status of “Failed�. Technically, the code belongs to the 0x800f0800 range, which is reserved for servicing failures—problems that occur while Windows is trying to modify its own components. The most common triggers are:

• Corrupted system files or a damaged component store (the folder that holds files needed for updates).
• A pending update that was interrupted by a shutdown or power loss.
• Third-party antivirus or security software locking update files.
• Disk space shortage on the system drive.
• Outdated or conflicting drivers, especially for graphics or network adapters.

Unlike a network error (like 0x80072efd), this code points to a local problem, so the solution is almost always on your PC, not on Microsoft’s servers.

Before You Start: Preparation Steps

Take two minutes to prepare, because some fixes require a restart and you do not want to lose work or interrupt the repair.

1. Save any open files and close all applications.
2. Make sure your PC is plugged in (if it is a laptop) to avoid a shutdown mid-repair.
3. Temporarily disable third-party antivirus or security software. Windows Defender is fine to keep on; third-party tools sometimes block update files. Re-enable it after the fix.
4. Check that you have at least 10–20 GB of free space on the drive where Windows is installed (usually C:). You can see this in File Explorer under “This PC�.

If you have a system restore point or a full backup, that is a good safety net, but the steps below are non-destructive to your personal files.

Fix 1: Run DISM and System File Checker

These two built-in tools repair corrupted system files and the component store. Run them in order, from an elevated Command Prompt.

1. Click the Start button, type cmd, right-click “Command Prompt� and select Run as administrator.
2. First, run DISM (Deployment Imaging Service and Management Tool) to repair the component store:
   DISM /Online /Cleanup-Image /RestoreHealth
   This can take 15–30 minutes. Do not close the window.
3. After DISM finishes, run System File Checker:
   sfc /scannow
   This also takes 10–20 minutes. It will replace any corrupted system files it finds.
4. Restart your PC and try Windows Update again.

If SFC reports that it found corrupted files but could not fix them, run DISM again and then SFC once more. The two tools work together: DISM repairs the source that SFC uses to replace files.

Fix 2: Reset Windows Update Components

If the error persists, the Windows Update service itself may be stuck. Resetting its components clears the download cache and re-registers the update service. This is a bit more involved, but it is safe and does not affect your personal files.

1. Open an elevated Command Prompt as before.
2. Stop the Windows Update services by typing these commands one at a time, pressing Enter after each:
   net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
3. Rename the Software Distribution and Catroot2 folders (these hold update files and signatures):
   ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old
4. Restart the services you stopped:
   net start wuauserv
net start cryptSvc
net start bits
net start msiserver
5. Close the Command Prompt and restart your PC.

This forces Windows Update to rebuild its download cache from scratch. It is the most common fix for errors that persist after DISM and SFC.

Fix 3: Install the Update Manually

If the failing update is a specific one (for example, a .NET Framework cumulative update), you can download it directly from the Microsoft Update Catalog and install it manually. This bypasses the Windows Update client entirely, which can get around a corrupted update service.

1. Open Windows Update, click “View update history�, and note the KB number of the failed update (e.g., KB5012345).
2. Go to the Microsoft Update Catalog website (catalog.update.microsoft.com) in your browser.
3. Search for that KB number, download the version that matches your Windows edition (Home, Pro, etc.) and architecture (64-bit or 32-bit).
4. Double-click the downloaded .msu file and follow the prompts. If it fails with the same error, the problem is deeper and you should try the next fix.

Only download from the official Microsoft Update Catalog—never from third-party sites, which can host modified or malicious files.

Fix 4: Use the Windows Update Troubleshooter and Reset This PC

If the manual install fails, the built-in troubleshooter can sometimes identify the exact cause. Go to Settings → System → Troubleshoot → Other troubleshooters and run “Windows Update�. It will scan for common issues and apply fixes automatically.

If that does not work, a more drastic option is to “Reset this PC� while keeping your files. This reinstalls Windows but preserves your personal documents, photos, and most settings. It will remove installed applications, so make a list of what you need to reinstall. To do this: Settings → System → Recovery → Reset PC → Keep my files. Choose the cloud download option if you have a stable internet connection; it is usually faster and more reliable than a local reinstall.

Frequently Asked Questions

Will these steps delete my personal files?

No. DISM, SFC, and resetting Windows Update components only repair system files and services. They do not touch your documents, photos, or other user data. The “Reset this PC� option with “Keep my files� also preserves your personal files, but it does remove installed programs.

Why does this error happen after a Windows feature update?

Feature updates (like version 23H2) replace a large number of system files. If any of those files are corrupted or locked by a driver or antivirus, the update fails with a servicing error like 0x800f0806. The DISM and SFC repair steps are designed to fix exactly this scenario.

Can I ignore this error and keep using my PC?

You can, but the failed update may leave your system in a partially updated state, which can cause stability issues or security vulnerabilities. It is best to resolve the error before installing future updates, as the same problem may block them too.

Is there a way to prevent this error in the future?

Keeping your system drive with at least 20 GB of free space, avoiding forced shutdowns during updates, and not using third-party “update blocker� tools reduces the chance. Also, run DISM and SFC regularly if you notice system slowdowns or crashes.

What if none of these fixes work?

If you have tried DISM, SFC, resetting Windows Update, manual install, and the troubleshooter, the last option is a clean install of Windows. Back up your files, create a Windows installation USB using the Media Creation Tool, and reinstall from scratch. This always resolves servicing errors, but it is time-consuming.

Common Misconception: It’s a Network or Server Problem

Many users assume error 0x800f0806 is caused by Microsoft’s servers or their internet connection, because Windows Update often shows a generic “connection� message. However, this specific code is a local servicing failure. The update was downloaded successfully, but the installation could not complete due to file corruption or a locked component. That is why the fixes above focus on repairing your system, not on changing network settings or waiting for Microsoft to fix something on their end.

Related

• How to Use Guest Mode on Android
• Fix AOC USB Monitor Not Working on Windows 10
• Windows 10 Settings to Customize First