Fix Windows Update Error 0x800f0831

Issue type: Windows Update component store corruption | Applies to: Windows 10, Windows 11

Windows update error 0x800f0831 usually means Windows cannot install a cumulative update because the component store is missing or holding corrupted package data. The real fix is to repair the component store with DISM, run SFC after that, check whether a previous update package is missing, reset Windows Update folders, and install the failed KB manually if the automatic route keeps failing.

This error often appears after Windows downloads the update successfully. That matters because the problem is usually not the download itself. The failure normally happens when Windows tries to stage, verify, or apply component data during installation.

Do not keep clicking Retry without repair work. If the component store cannot provide the required package manifest or payload, the same update will fail again until the missing or damaged servicing data is fixed.

Before you start, open Settings → Windows Update → Update history and copy the KB number that failed. If you later need the Microsoft Update Catalog, that KB number is the key detail.

What to Do First: Fix Windows Update Error 0x800f0831

1. Restart the PC once and confirm that windows update error 0x800f0831 still appears.
2. Open Settings → Windows Update → Update history and copy the failed KB number.
3. Make sure the C: drive has enough free space for update staging and DISM repair work.
4. Open Terminal (Admin) or Command Prompt (Admin).
5. Run DISM repair first, then run SFC after DISM completes.
6. Restart the PC and retry Windows Update before moving to manual install steps.

Fix 2: Repair the Component Store with DISM

DISM is the main repair tool for this error because it checks the Windows image and repairs the component store that cumulative updates depend on. If the store is corrupted, Windows Update cannot reliably install packages.

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

CheckHealth is quick. ScanHealth checks more deeply. RestoreHealth performs the repair. Keep the window open even if the percentage appears stuck for several minutes.

If DISM reports that the restore operation completed successfully, continue to SFC. Do not stop after DISM, because individual protected system files may still need repair.

Fix 3: Run SFC After DISM

SFC repairs protected Windows files using the component store that DISM just repaired. Running SFC before DISM is less effective when the component store itself is the source of the update failure.

sfc /scannow

Wait until the scan reaches 100%. If SFC says it found and repaired files, restart the PC and try Windows Update again.

If SFC says it could not repair some files, run DISM again, restart, and then run SFC one more time. Repeating once is reasonable when the component store was damaged.

Fix 4: Check Whether a Previous Update Package Is Missing

Microsoft documents cases where error 0x800f0831 occurs because the update being installed requires the manifest of a previous update package. If that earlier package is missing, the newer update cannot complete.

1. Open Settings → Windows Update → Update history.
2. Look for repeated failures around the same KB number.
3. Search the KB number in Microsoft Update Catalog.
4. Check whether Microsoft lists prerequisites or related earlier updates.
5. Install missing prerequisite updates first, then retry the newer update.

This step is important on systems that skipped several months of cumulative updates, were offline for a long time, or had failed update attempts before the current error appeared.

Fix 5: Reset Windows Update Folders

If DISM and SFC repair the system but the same KB still fails, rebuild the update staging folders. This removes stale download metadata and forces Windows to prepare the update again.

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 msiserver
net start cryptSvc
net start bits
net start wuauserv

Restart the PC after the commands. Windows will recreate fresh update folders automatically.

If the update becomes stuck in a queued state instead of failing immediately, use TechRoke’s guide on Windows Update pending install before repeating repairs.

Fix 6: Install the Failed KB Manually

If one specific KB keeps failing through Windows Update, download it manually from Microsoft Update Catalog. Manual installation can bypass a broken automatic queue, but it will not fix an unhealthy component store by itself.

1. Copy the KB number from Update history.
2. Open Microsoft Update Catalog.
3. Download the package that matches your Windows version and system architecture.
4. Right-click the downloaded package and run it as Administrator.
5. Restart when Windows asks.

If the standalone installer fails, install the package with DISM. Replace the file path with the real location of your downloaded update file.

DISM /Online /Add-Package /PackagePath:"C:\Users\YourName\Downloads\update.msu"

If DISM returns a different error code, use that new code for the next diagnosis. A different code means you moved past the original 0x800f0831 blocker.

Fix 7: Use a Windows ISO as a DISM Repair Source

If DISM /RestoreHealth cannot repair from Windows Update, provide a local repair source from a matching Windows ISO. This helps when Windows Update servers are blocked, the PC is on a restricted network, or the repair source is unavailable.

1. Download a Windows ISO matching your installed Windows version.
2. Double-click the ISO to mount it.
3. Note the drive letter, such as D:.
4. Run a DISM repair using the ISO as the source.

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

If your ISO contains install.esd instead of install.wim, use:

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

If the index number is wrong, list the available editions first:

DISM /Get-WimInfo /WimFile:D:\sources\install.wim

Fix 8: Check CBS.log for the Failed Package

The CBS log can show which package, manifest, or component Windows could not process. This is useful when every general repair step fails.

C:\Windows\Logs\CBS\CBS.log

Open the file in Notepad and search for 0x800f0831, the failed KB number, manifest, and package. The lines above the error often show the exact package identity that failed.

If the log also shows errors such as 0x80070057, read the related guide on Windows Update error 0x80070057, because the root cause may be broader servicing corruption.

Fix 9: Check Disk and File System Health

If the same servicing errors keep returning after repairs, check the system drive. File system damage can break update package staging and corrupt newly rebuilt update folders.

chkdsk C: /scan

If Windows reports problems, schedule a repair:

chkdsk C: /f

Restart and allow the disk check to finish. Afterward, run DISM and SFC again before retrying Windows Update.

Fix 10: Use an In-Place Repair Upgrade as the Final Repair

If 0x800f0831 appears across multiple cumulative updates and DISM cannot make the image healthy, an in-place repair upgrade is the clean final step. It reinstalls Windows over itself while keeping apps and personal files.

Use this only after DISM, SFC, update reset, manual KB installation, ISO repair source, log checks, and disk checks fail. Back up important files first.

Common Mistake

The common mistake is running SFC alone or deleting update downloads only. Windows update error 0x800f0831 is often a component store or missing package manifest problem, so DISM, prerequisite checks, and servicing repair matter more than simple retries.

Best Next Step

If the error continues after normal DISM repair, check whether a previous update package is missing and use a matching ISO source if Windows cannot repair online. Microsoft’s official 0x800f0831 troubleshooting guidance explains that required package manifests can be missing, and Microsoft’s image repair guidance explains DISM repair sources: Error 0x800f0831 when installing an update — Microsoft Learn.

Frequently Asked Questions

What does Windows Update error 0x800f0831 mean?

It usually means Windows cannot install the update because required component store or package data is missing, corrupted, or unavailable during the installation phase.

Is 0x800f0831 a download error?

Usually no. The update may download correctly, but Windows fails while staging or applying the package through the servicing system.

Should I run DISM or SFC first?

Run DISM first, then SFC. DISM repairs the component store, and SFC repairs protected system files using that repaired store.

Can a missing previous update cause 0x800f0831?

Yes. If the current update requires a manifest from an earlier package that is missing, the newer update can fail until the missing prerequisite is installed or the store is repaired.

Does this error require reinstalling Windows?

Not usually. Try DISM, SFC, prerequisite checks, update folder reset, manual KB installation, and ISO source repair before considering an in-place repair upgrade.