FixHub
Windows

Windows Update Error 0x800f0831? Find the Exact Missing Package (CBS Store Corruption)

Published June 10, 2026 · by The FixHub Team

A monthly cumulative update fails with 0x800f0831, and C:\Windows\Logs\CBS\CBS.log shows something like:

“Store corruption, manifest missing for package: Package_for_… ” / CBS_E_STORE_CORRUPTION

Why the standard advice often fails: almost every guide says “run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow” and stops. That works only if the PC can reach Windows Update to pull the missing component. 0x800f0831 specifically means the update requires the manifest of an earlier package that’s no longer in the component store — and on machines without Microsoft Update access (WSUS, metered, or store-corrupted), RestoreHealth can’t fetch it and fails again. The real fix is reading CBS.log to find the exact missing package and installing that from the Microsoft Update Catalog.

Fix 1: Try the standard repair first (it does work sometimes)

In an admin Command Prompt:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Reboot and retry the update. If it fails again with 0x800f0831, don’t repeat it — move to Fix 2.

Fix 2: Read CBS.log to find the named package

  1. Open C:\Windows\Logs\CBS\CBS.log in Notepad (copy it to the desktop if it’s locked).
  2. Search for manifest missing for package or CBS_E_STORE_CORRUPTION.
  3. Note the package name it lists, e.g. Package_for_RollupFix~31bf3856ad364e35~amd64~~<build> — that’s the KB it needs.
  4. Map that build number to its KB number (the build maps to a specific monthly update).

Fix 3: Install that exact package from the Update Catalog

  1. Go to the Microsoft Update Catalog and download the KB identified in Fix 2 for your exact Windows version/architecture (the .msu).
  2. Install it (double-click the .msu, or wusa <file>.msu).
  3. Reboot, then re-run DISM /Online /Cleanup-Image /RestoreHealth — now the missing manifest is present, so it completes.
  4. Retry the original update.

Fix 4: Repair against a known-good source (offline machines)

If the PC can’t reach Microsoft Update, point DISM at a matching Windows image:

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

(Mount an ISO of the same build as D:; adjust the index.) /LimitAccess stops it trying Windows Update.

FAQ

Why did RestoreHealth say it couldn’t find source files? Because the component it needs is the missing package itself — give it a real source (Fix 3 or 4) and it succeeds.

Is my Windows install toast? Usually not — this is component-store corruption, repairable with the right package. A repair/in-place upgrade is the last resort if Fixes 2–4 don’t take.

Different code, similar rollback? If it’s 0x80073712 instead, that’s the same store-corruption family — see 0x80073712 component store fix. For a rollback loop, see the “Undoing changes” guide.

Sources: Microsoft Learn — Error 0x800f0831 when you install a Windows update