The short version
- 01Run DISM /ONLINE /CLEANUP-IMAGE /SCANHEALTH, then /CHECKHEALTH, then /RESTOREHEALTH.
- 02Run Sfc /Scannow after those, then restart the device.
- 03Read %windir%\Logs\CBS\CBS.log for the store corruption line naming the missing package.
- 04Search the Microsoft Update Catalog for that package ID.
- 05Download the update that matches your operating system version exactly.
- 06Install the downloaded package, then retry the update that was failing.
Raw message
FATAL: CBS called Error with 0x800F0831
Likely causes
- The update being installed requires the manifest of a previous update package.
- That earlier package missing from the component store or not fully applied to the registry.
- No access to Microsoft Update, which Microsoft says makes the problem more likely.
- A machine serviced from WSUS or an offline image, so intermediate packages were skipped.
Why this one is more specific than it looks
0x800F0831 is CBS_E_STORE_CORRUPTION, which sounds like the general component store corruption family. Microsoft's cause is far more precise: the update that can't be installed requires the manifest of a previous update package. Something earlier in the chain is missing, and the update in front of it cannot proceed without it.
Microsoft adds a condition that explains why this appears on some machines and not others: the issue is more likely to occur when there's no access to Microsoft Update. A machine that can reach Microsoft Update can often fetch the missing piece itself; one serviced from WSUS, from an offline image, or behind a restrictive network cannot.
In WindowsUpdate.log the failure appears as FATAL: CBS called Error with 0x800F0831. In CBS.log it appears as store corruption with a manifest missing for a named package, followed by a chain of failures to resolve it.
The repair commands, and then the specific fix
Microsoft's first method is the standard component store repair, run in order from an elevated command prompt: DISM /ONLINE /CLEANUP-IMAGE /SCANHEALTH, then DISM /ONLINE /CLEANUP-IMAGE /CHECKHEALTH, then DISM /ONLINE /CLEANUP-IMAGE /RESTOREHEALTH, then Sfc /Scannow. Restart the device afterwards.
That is worth doing first because it is quick and it resolves the cases where the missing manifest can be fetched. But it is not the interesting part of this code, and if it fails the answer is not to run it again.
The second method is what makes 0x800F0831 different from a general store repair. Because CBS.log names the specific missing package, you can go and get it: open the Microsoft Update Catalog, enter the package ID of the missing package, find the update that applies to your operating system, download it, and install it. Then retry the update that was failing.
Finding the package name in the log
CBS.log lives at %windir%\Logs\CBS\CBS.log. The lines to look for say store corruption with a manifest missing for a package, and failed to resolve that package, each tagged with HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION. Microsoft's own example distinguishes two names in that output: the failed package, which is the one that cannot be installed, and the missing package, whose manifest is absent.
It is the missing package you want, not the failed one. Searching the Update Catalog for the update you were trying to install will find something plausible and will not fix anything, which is an easy hour to lose.
Match the download to your exact operating system version and architecture. The Update Catalog lists several builds per KB number, and a package for a different build will not supply the manifest this repair needs.
Sources and review notes
Checked on . Based on Microsoft's article for error 0x800F0831 and its guidance on fixing Windows Update corruption. Microsoft's article is written with Configuration Manager and WSUS environments in mind; the DISM sequence and the Update Catalog route apply equally to a home PC. The advice to match the download to your exact build is editorial. Glitchary is independent of Microsoft.