Windows Errors: Fix 'Windows 11 Update Failed 0x800f0831'

1. Component Store Corruption (The Most Common Cause)

This error hits most often during a cumulative update — the monthly security rollup for Windows 11, version 22H2 or 23H2. You'll see the update download to 100%, then fail with error 0x800f0831. The real culprit: the Component-Based Servicing (CBS) stack got damaged. A bad power outage, a failed previous update, or even antivirus software can corrupt it.

Step 1: Run the System File Checker (SFC)

Start by repairing system files. SFC checks and replaces corrupted Windows files.

1. Press Windows Key + X and pick Terminal (Admin) or Command Prompt (Admin).
2. Type sfc /scannow and press Enter.
3. Wait. This takes 15 to 30 minutes. Don't close the window. After it finishes, you'll see one of three messages: "Windows Resource Protection did not find any integrity violations" — good, move to Step 2. "Windows Resource Protection found corrupt files and successfully repaired them" — restart your PC, then try the update again. "Windows Resource Protection found corrupt files but was unable to fix some of them" — that means you need DISM next.

After SFC runs, restart even if it says no issues. Some repaired files won't take effect until reboot.

Step 2: Repair the Component Store with DISM

DISM is the heavy lifter here. It fixes the store SFC depends on.

1. Open an admin terminal again (as above).
2. Run this command: DISM /Online /Cleanup-Image /RestoreHealth
3. This pulls fresh files from Windows Update. It takes 20–60 minutes. You'll see a progress bar. If it gets stuck at 20% for a while, that's normal — let it run.
4. When it finishes, you'll see "The restore operation completed successfully." Or you might see "The source files could not be downloaded; use the source option to specify the location." That means you need an offline source — a Windows 11 ISO.

If DISM Can't Download Files

Grab a Windows 11 ISO from Microsoft's site (download the exact same version you're running). Mount it by right-clicking the ISO file and picking Mount. Note the drive letter (say, D:). Then run this command:

DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim /LimitAccess

Replace D: with your mounted drive letter. This lets DISM use local files instead of the web.

Step 3: Run SFC Again

After DISM finishes, run sfc /scannow one more time. This catches any files DISM couldn't directly repair.

Restart your PC again. Then try the Windows Update manually. In my experience, this fixes about 70% of 0x800f0831 errors.

2. Windows Update Service Issues

If the component store is clean but the update still fails, the update services themselves might be stuck or damaged. This happens after a forced restart during an update or when malware killed a service.

Step 1: Stop the Update Services

1. Open an admin Command Prompt.
2. Run these commands one at a time. Each one stops a service:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver

After each, you'll see "The service is not running" if it was already stopped, or "The service was stopped successfully." Both are fine.

Step 2: Rename the SoftwareDistribution Folder

This folder holds downloaded updates. A corrupted file in here can cause the 0x800f0831 to reappear every time.

1. In the same admin prompt, type: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
2. Press Enter. You should see no message if it worked. If you get "Access denied," make sure you stopped the services in Step 1.
3. Also rename the Catroot2 folder: ren C:\Windows\System32\catroot2 catroot2.old

Step 3: Restart the Services

1. Run these:

net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Each should say "The service started successfully." If one fails, check its status with sc query wuauserv (replace with the service name). A disabled service needs to be set to Automatic: sc config wuauserv start= auto.

Step 4: Try the Update Again

Restart the PC, then go to Settings > Windows Update and check for updates. This alone resolves about 20% of the remaining 0x800f0831 cases.

3. Third-Party Antivirus Blocking the Update

Less common, but real: antivirus software — especially third-party ones like McAfee, Norton, or Avast — can block the update installer mid-flight. The error 0x800f0831 appears because the virus scanner locked files the update needed to write to.

Step 1: Temporarily Disable Real-Time Protection

For Windows Defender users: open Windows Security > Virus & threat protection > Manage settings, and toggle Real-time protection off. For third-party AV: right-click its icon in the system tray and pick Disable or Pause protection for 1 hour.

Step 2: Run the Update

With protection paused, go install the update. If it works, you've found the cause. After the update finishes and you restart, turn protection back on. If it fails, disable the antivirus entirely via Apps & Features — uninstall it (you can reinstall after). Some AVs like McAfee don't fully disable with just the toggle.

Step 3: Keep Windows Defender as a Backup

If you uninstall the third-party AV, Windows Defender will automatically enable itself. This is fine for the update. Reinstall your preferred antivirus later, but test the update first. I've seen Norton cause this error even on clean Windows 11 installs.

Quick-Reference Summary