Independent technical referenceOfficial site
  • Software and digital services
  • Operating system

0x800F0831

Windows 0x800F0831: component store is corrupted

Verified with sources2 sourcesReviewed Oct 4, 2026
Technician coming? See the 2 steps they must show you

Risk level

Low

Usually safe to check without specialist tools.

Urgency

Medium

Quick answer

The update will not install because the Windows component store is corrupted. Repair it with DISM and SFC from a Command Prompt run as administrator, then restart before trying again.

Safety first

Stop and check this first

  • Copy your important files before repairing the store or reinstalling: Microsoft asks for a backup of personal files before its troubleshooting steps.

Safe checks you can perform

  • Repair with DISM and SFC
  • Windows Update troubleshooter
  • Clear the Windows Update cache

Leave these tasks to a qualified professional

  • Do not attempt this professional task: Manual repair of the component store
  • Do not attempt this professional task: Microsoft support with collected data

What a technician must be able to justify

Technician visit

These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.

These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.

  1. Manual repair of the component store

    What they doThe technician finds the damaged component in CBS.log and repairs it with the payload of the partially installed component or a repair source given to DISM.

    They must show youthe CBS.log line naming the damaged component.

    In writingwhich component was repaired, from which source, and the DISM result afterwards.

  2. Microsoft support with collected data

    What they doIf the repair does not work, a case is opened with Microsoft support including the data its deployment collection tool asks for.

    They must show youthe collected data package and the failing KB.

    In writingthe case number and the fix applied.

Before accepting a part or repair

Nothing has been shown yet. Do not accept a part swap based on the code alone.

Follow these steps

Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.

  1. Repair with DISM and SFC

    No special tools

    Who:
    you, from a Command Prompt run as administrator.
    How:
    type Dism.exe /Online /Cleanup-Image /Restorehealth, wait for it to finish, type Sfc.exe /Scannow and restart the PC.
    Result that matters:
    whether DISM succeeds and the update installs after the restart.
    If it installs:
    the damaged store was the cause and is now repaired.
    If DISM ends in an error:
    the store needs a manual repair by a technician.
    Evidence to keep:
    screenshot of the final DISM and SFC messages.

    Evidence: Common Windows Update errors

  2. Windows Update troubleshooter

    No special tools

    Who:
    you.
    How:
    Start, Settings, System, Troubleshoot, Other troubleshooters, Windows Update, Run.
    Result that matters:
    whether it detects and fixes Windows Update problems.
    If it fixes something and the update goes in:
    there was also a Windows Update state problem.
    If it fixes nothing:
    the fault is still in the store.
    Evidence to keep:
    screenshot of the summary.

    Evidence: Microsoft Windows Update troubleshooting

  3. Clear the Windows Update cache

    No special tools

    Who:
    you, with an administrator account.
    How:
    stop the Windows Update service in services.msc, delete the contents of C:\Windows\SoftwareDistribution and start the service again.
    Result that matters:
    whether the freshly downloaded update installs after the DISM repair.
    If it installs:
    the download was corrupted too.
    If not:
    the case goes to the technician.
    Evidence to keep:
    time and result of the attempt.

    Evidence: Microsoft Windows Update troubleshooting

Still not solved

If the error persists, stop here. See what the technician must do and show you.

Where this code applies

A code is meaningful only inside the right product and version context.

Primary scope

System
Software and digital services
Brand
Microsoft Windows
Product type
Operating system

Known code variants

  • 0x800f0831
  • 800F0831
  • CBS_E_STORE_CORRUPTION

What it means

Microsoft defines 0x800F0831 as CBS_E_STORE_CORRUPTION: the Component Based Servicing (CBS) service finds the Windows component store damaged, the folder Windows uses to install and repair updates. The repair it documents is DISM with RestoreHealth followed by sfc /scannow, or a manual repair using the payload from the partially installed component. The code says the store is damaged, not why or which component.

Warnings and stop conditions

  • Lowsource verified

    Copy your important files before repairing the store or reinstalling: Microsoft asks for a backup of personal files before its troubleshooting steps.

    Evidence: Microsoft Windows Update troubleshooting

Symptoms and causes

Probable causes · in order

  • Partially installed componentCommon

    Microsoft links this kind of damage to components left in a partial state; it is confirmed if DISM reports that it repaired the store.

    Evidence: Common Windows Update errors

  • Corrupted update cache as wellPossible

    If DISM repairs but the update still fails, rule out a corrupted download too by clearing the cache.

    Evidence: Microsoft Windows Update troubleshooting

  • Damage DISM cannot repairPossible

    You can tell because DISM ends with an error or no repair source; a technician then needs to do the manual repair.

    Evidence: Common Windows Update errors

Virtual technician

Does 0x800F0831 still appear after these checks?

Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.

Sources and technical references

  1. 1

    Common Windows Update errors

    Microsoft · 2026 · official_doc

  2. 2

    Microsoft Windows Update troubleshooting

    Microsoft · 2026 · official_doc

Sources: Common Windows Update errors · Microsoft Windows Update troubleshootingreviewed 2026-10-04 · verified

Was this entry useful?