Windows command guide

DISM RestoreHealth Explained: Fix the Windows Component Store

DISM /RestoreHealth is commonly used when the Windows component store itself is damaged. That matters because other repair tools, especially SFC, rely on healthy source files in that store. If the component store is corrupted, normal file repair can fail or repeat the same errors.

This guide is written around the specific symptom-command match for restore windows image health, not as a generic dump of terminal lines. That makes the page more useful for real troubleshooting and reduces the chance of running the wrong repair step.

Reviewed guide Updated 2026-04-21

Elevated Command Prompt

DISM /Online /Cleanup-Image /RestoreHealth

Best place to run it

Elevated Command Prompt is the right execution context for this page. Because this repair touches protected Windows state, a normal unelevated shell can return misleading access errors or partial results.

Fast repair workflow

Start from the exact symptom on this page: SFC says it found corruption but could not repair some files
Run the primary repair line exactly as shown: DISM /Online /Cleanup-Image /RestoreHealth.
This workflow is tuned for this repair, so avoid mixing it with unrelated repair commands too early.
Reboot if the servicing stack or protected files were changed, then retry the original Windows action.
Escalate only after reading the output, usually toward CBS.log, DISM source repair, or Windows Update-specific repair.

Copyable wrapper script

Use this wrapper when you want the page command inside a clearer script block with start and finish prompts.

@echo off
echo Run this CMD sequence in an elevated Command Prompt.
echo Starting targeted repair sequence...
DISM /Online /Cleanup-Image /RestoreHealth
echo.
echo Review the output before closing this window.
pause

Verification commands after the repair

These follow-up commands help you check whether the repair actually changed the Windows state that matters, instead of assuming success from a single line.

DISM /Online /Cleanup-Image /CheckHealth
sfc /verifyonly

What problem this command is trying to solve

This command targets corruption in the Windows image and component store. It is useful when system repair tools fail, cumulative updates break, or Windows servicing errors keep returning.

SFC says it found corruption but could not repair some files.
Windows Update fails repeatedly with servicing-related errors.
Built-in repair processes do not finish successfully.

How the command works

DISM checks the online Windows image, looks for corruption inside the servicing store, and attempts to download or reconstruct healthy components needed for repair. Once that source is repaired, SFC usually becomes more effective.

When it makes sense to run it

Run this command when you suspect deeper Windows image corruption, especially after failed updates or failed SFC repairs. A common workflow is DISM first and SFC right after.

Before you run this command

Open an elevated Command Prompt or PowerShell window before running DISM /Online /Cleanup-Image /RestoreHealth.
Confirm that the symptom really matches this guide, especially if you are seeing signs such as: sfc says it found corruption but could not repair some files.
Keep any exact DISM, SFC, CBS, or Windows Update error output because those details matter in the next step.

What result to expect

After running DISM /Online /Cleanup-Image /RestoreHealth, compare the result against the symptom that brought you here. The most useful checkpoint is whether sfc says it found corruption but could not repair some files becomes less frequent, changes form, or produces a clearer error message. A command page is stronger when it helps you verify a real change instead of just assuming the line must have worked.

How to verify that it worked

The best verification step after DISM /Online /Cleanup-Image /RestoreHealth is to repeat the action that previously triggered the problem. If windows update fails repeatedly with servicing-related errors still appears in exactly the same way, the command probably was not the whole answer and you should move to the next targeted check instead of assuming the page is finished.

Why administrator rights matter here

This command changes system integrity and component corruption. Run it in an elevated shell so Windows can apply the repair instead of only returning an access or privilege error.

Before you run it

An internet connection can help, because DISM may need to contact Windows Update for repair sources. The scan can take time, so do not stop it just because it appears slow.

When this is probably the wrong fix

This is not the right first fix for a single third-party app bug, a browser-only issue, or obvious hardware failure. Use it when the symptom points to Windows image health, recurring update corruption, or protected system files.

What to do if it does not help

If DISM /Online /Cleanup-Image /RestoreHealth does not improve sfc says it found corruption but could not repair some files, move to the next repair step that matches the same symptom family instead of piling on random commands. The best follow-up depends on whether the failure is mainly about system integrity and component corruption.

Frequently asked questions

Should I use DISM /Online /Cleanup-Image /RestoreHealth for this exact Windows symptom?

Use it when the behavior on your PC lines up with the repair target on this page: This command targets corruption in the Windows image and component store. It is useful when system repair tools fail, cumulative updates break, or Windows servicing errors keep returning.

What should I check right after DISM /Online /Cleanup-Image /RestoreHealth?

Check whether the original trigger still reproduces the same failure. For this page, a useful checkpoint is whether sfc says it found corruption but could not repair some files becomes less frequent, changes form, or points you toward a more specific next step.