0x800F0831 CBS_E_STORE_CORRUPTION: the component store itself is damaged

Fix it now

0x800F0831 is CBS_E_STORE_CORRUPTION: the component store is corrupt. Microsoft’s mitigation is store repair followed by System File Checker, not hunting for a single missing KB. Install the servicing stack update for your build first, because 0x80242017 in the same log says the stack has to be updated before anything else can install.

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
DISM /Online /Get-Packages /Format:Table

1. Read the package table. Anything showing as Install Pending or Staged rather than Installed is unfinished work; reboot fully and let servicing complete it before you try anything else.
2. If the machine also reported 0x80242017, install the servicing stack update for your exact build from the Microsoft Update Catalog and reboot before the cumulative update.
3. If RestoreHealth cannot reach a source, supply one: DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:D:\sources\install.wim:1 /LimitAccess.
4. Reboot, then reinstall the update that was failing.

Do not remove packages with DISM to tidy up while you are here. Removing the wrong one can leave the machine unbootable, and it is far easier to break the store further than to repair it.

If ScanHealth is clean and the update installs, stop here. If repair does not take, the next section covers what the store is checking and which of these codes is telling you what.

Why it happens

Every update Windows installs is registered as a package, and the component store keeps the manifests and payload that describe what is present. Component-Based Servicing verifies that picture before it applies anything, because an update is expressed as a change against a known state. 0x800F0831 is that verification concluding that the store itself is corrupt, and Microsoft’s published mitigation is store repair: DISM /RestoreHealth, then sfc /scannow.

That is worth stating plainly, because this code is widely described as a missing package in a supersedence chain, with instructions to find a KB number in the log and reinject it. That is not what the code says. Reinjecting a package on a corrupt store sometimes clears one symptom and leaves the underlying condition in place, which is why the next month’s update fails in the same way. Repair the store, then reinstall.

The other codes narrow the diagnosis. 0x80242017 is WU_E_UH_NEW_SERVICING_STACK_REQUIRED: the servicing stack must be updated before this update can be downloaded or installed. That one is a straight instruction, and it is often the whole answer on a machine that has been offline for a long time. 0x8007371B is ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE, meaning one or more required members of the transaction are not present, which is what a half-committed servicing operation looks like from the side-by-side layer.

0x80242013 and 0x800F0805 point at metadata and at the file you handed to servicing. 0x80242013 is WU_E_UH_BADCBSPACKAGEID, an invalid CBS package identifier in the update metadata, so the handler cannot match the update to a package in the store. 0x800F0805 is CBS_E_INVALID_PACKAGE, meaning the file itself is not a valid Windows package. In this article’s own workflow that almost always means the wrong cabinet was picked out of an expanded .msu.

Full reference

Reading the store’s own account of itself

Before you inject or remove anything, look at what state the packages are actually in. This costs nothing and frequently ends the investigation, because a machine with a pending transaction needs a restart rather than a repair.

DISM /Online /Get-Packages /Format:Table

rem narrow the servicing log to the failure
findstr /i /c:"0x800f0831" %windir%\Logs\CBS\CBS.log

Every code in this article, with what it actually says

Injecting a package, when it is genuinely the right move

Package injection is a narrow tool, not the opening move. It is appropriate when the store is otherwise healthy and one specific update has to go on by hand, most often to install a servicing stack update the machine cannot fetch. The argument order for expand matters: the documented form puts the source first, then -f:, then the destination.

expand C:\temp\windows10.0-kb0000000-x64.msu -f:* C:\temp\extract

DISM /Online /Add-Package /PackagePath:C:\temp\extract\windows10.0-kb0000000-x64.cab

DISM /Online /Remove-Package is not a tidying tool. It removes a .cab package from the image, and removing something the running system depends on can leave the machine unable to boot. If a package is in the way, work out why before you remove it.

Where to read what failed

• %windir%\Logs\CBS\CBS.log records what servicing was doing when it stopped, including the component or package name. Search on the failure time and read backwards.
• %windir%\Logs\DISM\dism.log records what a repair attempted and which source it used.
• Update history in Settings gives you the KB number and the code, which is enough to find the right standalone package in the Microsoft Update Catalog.
• winver gives the exact build, which is what the catalogue entry has to match. Close enough is not good enough here.

When store repair does not clear it

Microsoft documents an escalation for this family of servicing codes, and it is worth knowing where the ladder ends. If repair from a good source does not clear the corruption, the supported route is an in-place upgrade with media at least as patched as the machine, keeping files and applications. It rebuilds the store rather than patching around it, and on an activated machine it needs no new key. Take a full backup and confirm you hold any encryption recovery keys before you start.

Every code this article covers

Confirm the fix worked

1. Run DISM /Online /Cleanup-Image /ScanHealth and confirm no corruption is reported.
2. Run sfc /scannow and confirm no integrity violations remain.
3. Run DISM /Online /Get-Packages /Format:Table and confirm nothing is left Install Pending or Staged.
4. Install the update that was failing and confirm it completes.
5. Confirm the following month’s cumulative update also installs without intervention.

Questions people ask about this