DISM Commands Explained (Repair Windows Errors Using DISM & SFC)

If your PC feels slow, crashes randomly, shows update errors, or keeps throwing strange messages like:

“Windows Resource Protection found corrupt files”
“The component store is repairable”
“DISM error 0x800f081f”
“There are corrupt system files”

…then DISM is the tool that can fix it.

The problem?
Most tutorials only show a single command — and leave you guessing when things go wrong.

This is the complete, merged DISM commands Windows 10 + SFC guide for 2026.

You’ll learn:

what DISM actually does
how to use DISM correctly (even if you’ve never run it before)
which commands matter
how to repair corrupt Windows files
how to fix DISM errors
how SFC and DISM work together
how to restore Windows even if DISM fails

Let’s keep this simple, clean, and beginner-friendly.

What is DISM? (And When Should You Use It?)

DISM stands for Deployment Image Servicing and Management.
It’s a built-in Windows tool that repairs:

corrupt system files
damaged Windows images
broken update components
component store corruption
missing or invalid system resources

Think of DISM as the heavy-duty repair tool.

When Windows behaves strangely — crashes, freezes, or updates fail — DISM repairs the underlying system image.

Use DISM when:

Windows updates fail repeatedly
SFC cannot fix issues
apps keep crashing
system files are damaged
your PC shows corruption errors
Windows feels unstable

If SFC is the first aid kit, DISM is the surgeon.

Common Symptoms DISM Can Fix

Windows won’t update
Blue screen errors caused by missing files
System file corruption
Apps freezing or refusing to open
Start menu issues
Broken Windows features (e.g., .NET, DirectX)
SFC showing errors it cannot repair

The 3 Main DISM Commands

DISM has many parameters, but for repairing Windows, you only need three commands:

1️⃣ CheckHealth

Checks if corruption exists (instant result).

2️⃣ ScanHealth

Deep scan to detect detailed corruption.

3️⃣ RestoreHealth

Repairs corruption using Windows Update or local sources.

We’ll cover all of these in detail next.

DISM CheckHealth — Quick Corruption Check (dism checkhealth explained)

CheckHealth is the fastest DISM command.
It doesn’t fix anything — it simply checks whether Windows knows it has corruption.

Think of it as a quick diagnostic tool.

When to Use CheckHealth

Use this command when you want to know:

“Is my Windows installation corrupted?”
“Do I need to run a full repair?”
“Is this a minor or major problem?”

CheckHealth finishes instantly because it doesn’t scan deeply — it only reports what Windows has already logged.

Command to Run

Open Command Prompt (Admin) and enter:

DISM /Online /Cleanup-Image /CheckHealth

Press Enter.

What the Results Mean

✅ “No component store corruption detected”

Good news — Windows isn’t reporting any major corruption.

⚠️ “The component store is repairable”

Some corruption exists.
You’ll need to run RestoreHealth (covered in a later section).

❌ “The component store cannot be repaired”

This usually means:

severe corruption
missing system files
damaged Windows image

Don’t panic — deeper commands like RestoreHealth or a repair install can fix this.

Important Notes

CheckHealth does NOT repair anything
It runs instantly
It’s safe for beginners
It tells you if further action is needed

Use it as your starting point before running the heavier DISM commands.

DISM ScanHealth — Deep Scan for Windows Corruption (dism scanhealth explained)

Where CheckHealth is instant, ScanHealth performs a full, detailed scan of your system image.
It checks everything for corruption — and it can take a while.

Think of ScanHealth as a full diagnostic rather than a quick check.

When to Use ScanHealth

Run this when you suspect deeper issues, like:

repeated Windows Update failures
apps crashing for no reason
blue screen errors
SFC showing problems
Windows acting slow or unstable
ongoing corruption that CheckHealth didn’t explain

ScanHealth is safe to run and doesn’t fix anything — it only detects corruption.

Command to Run

Open Command Prompt (Admin) and type:

DISM /Online /Cleanup-Image /ScanHealth

Press Enter.

How Long Does ScanHealth Take?

Typically:

5–15 minutes on SSD systems
15–45 minutes on HDD systems

It may look “stuck” at:

20%
40%
62.3%
80%

This is normal.
Do not close the window.

What the Results Mean

After running, you’ll see one of the following:

✅ “No component store corruption detected”

Windows is clean — no need for repairs.

⚠️ “The component store is repairable”

Corruption exists but can be repaired using RestoreHealth.

❌ “The component store cannot be repaired”

Severe corruption.
You will need RestoreHealth with a source, or a repair install.

This usually happens when:

update components are broken
Windows system image is incomplete
third-party cleanup tools deleted vital files

ScanHealth tells you exactly what the problem is — but not the solution.

Does ScanHealth Repair Anything?

No — it only detects.

You’ll repair everything in the next stage:

👉 RestoreHealth

Quick Tip

If you want to speed up troubleshooting:

Run CheckHealth → takes seconds
If corruption exists, run ScanHealth → deep confirmation
Then run RestoreHealth → repairs it

DISM RestoreHealth — Repair Windows System Image (dism restorehealth full repair guide)

This is the command that repairs Windows when:

updates fail
Windows Update is broken and needs to be repaired
corruption is found
corruption is found
SFC can’t fix system files
apps behave erratically
the component store is broken

If Windows is “sick,” this is the treatment.— the most reliable way to fix Windows corruption without reinstalling your operating system.

RestoreHealth scans the system image and performs a full Windows image repair, fixing any corrupt or missing components using:

Windows Update (default)
a local Windows image (optional)
a mounted ISO file (advanced)

Let’s keep it simple and walk through everything clearly.

Method 1 — The Standard RestoreHealth Command (Most Common)

Open Command Prompt (Admin) and run:

DISM /Online /Cleanup-Image /RestoreHealth

Press Enter and wait.

⏳ How Long Does RestoreHealth Take?

10–20 minutes on SSD
20–60 minutes on HDD

It may appear stuck at:

20%
40%
62.3%
100% (still processing)

This is normal. Do not close it.

What RestoreHealth Actually Fixes

broken system files
corrupt Windows Update components
missing system resources
servicing stack issues
broken component store
incomplete previous updates

It’s one of the most powerful repair tools Windows offers.

What You Should See When It Works

You want this message:

The restore operation completed successfully.
The component store corruption was repaired.

If you see this, Windows is healthy again.

When RestoreHealth Fails

If the standard command fails with errors like:

0x800f081f
0x800f0906
0x800f0954
DISM source files could not be found
The component store cannot be repaired

It means Windows Update cannot find the repair files.

You’ll need to use Method 2 or Method 3.

Method 2 — RestoreHealth Using a Local Source (Fixes Most Errors)

If Windows Update is broken, you can repair Windows using an ISO by pointing DISM to a local image instead.

Step 1: Download a Windows 10 ISO from Microsoft

Mount the ISO by double-clicking it.
It becomes a drive letter (e.g., D:).

Step 2: Run DISM using the ISO source

Use:

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

If your ISO uses install.esd instead of install.wim, run:

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

Replace D: with the actual drive letter of your mounted ISO.

What “/LimitAccess” Does

It prevents DISM from contacting Windows Update —
so it only uses your local source.

Method 3 — RestoreHealth Using a Local Windows Folder (Advanced)

If you have another healthy Windows install, or extracted system files, you can use:

DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess

Only use this if you specifically maintain a repair image.

Method 4 — Full DISM Repair With Windows Image File (Technician-Level)

For IT technicians using a exported WIM:

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

This calls a specific image index.

RestoreHealth — After the Repair

Always run SFC afterwards, because DISM fixes the system image, but SFC repairs the live running files.

Run:

sfc /scannow

This ensures that:

repaired components are applied
missing files are restored
corrupted live files are replaced

This combination (DISM + SFC) fixes 99% of system corruption issues without a reinstall.

How DISM and SFC Work Together (The Correct Repair Order)

DISM and SFC are both repair tools — but they fix different things and work at different levels of Windows.

Here’s the easiest way to understand it:

SFC repairs the files you actively use.

DISM repairs the system image those files come from.

If the system image is damaged, SFC can’t fix anything — because the source files it’s using are also broken.

That’s why the order matters.

The Correct Repair Order (Windows 10 & 11)

1️⃣ DISM /CheckHealth

Quick check to see if corruption exists.

2️⃣ DISM /ScanHealth

Deep scan to confirm the details.

3️⃣ DISM /RestoreHealth

Repairs the Windows system image.

4️⃣ SFC /Scannow

Repair the live Windows installation using the freshly repaired image.

This sequence fixes:

corrupt system files
update errors
broken Windows features
incomplete updates
servicing stack corruption

It solves 99% of system stability problems without reinstalling Windows.

Protect your PC from malware and ransomware

**Why SFC Must Come After DISM**

If the system image is corrupted, SFC will show:

Windows Resource Protection found corrupt files but was unable to fix some of them.

This is why SFC /scannow not working is almost always a symptom of a broken Windows system image — not a problem with SFC itself.

Or:

Source files could not be found.

Running SFC alone does nothing if DISM hasn’t repaired the base image yet.

DISM = Fixes the blueprint
SFC = Fixes the house

SFC Command to Run After DISM

Open Command Prompt (Admin) and enter:

sfc /scannow

This will:

replace damaged system files
rebuild missing files
repair Windows components
validate hashes
ensure your OS is clean

If SFC still reports errors, repeat:

DISM /RestoreHealth
sfc /scannow

Sometimes it takes 2–3 repair cycles.

Common SFC Messages Explained

❗ “Found corrupt files and repaired them.”

Good — you’re fixed.

⚠️ “Found corrupt files but could not fix some of them.”

Run DISM again, then rerun SFC.

❌ “Windows Resource Protection could not perform the requested operation.”

Run SFC in Safe Mode or use offline repair mode (coming in later section).

Offline SFC (Advanced Repair Method)

If Windows cannot boot:

Use:

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

This scans Windows from outside the OS environment.

Useful for:

boot errors
blue screens
unbootable systems

Summary

The correct sequence is:

DISM → SFC → Reboot

This ensures the deepest possible repair without reinstalling Windows.

Common DISM Errors & How to Fix Them (0x800f081f, 0x800f0906, 0x800f0954, etc.)

DISM is powerful — but when it fails, it fails with confusing error codes that seem impossible to understand.

Good news:
Almost every DISM error falls into just four categories:

Windows Update can’t provide repair files
The repair source is missing or invalid
Permission or servicing stack problems
Network / policy restrictions

Below is the full list of common DISM errors and how to fix each one.

DISM Error 0x800f081f — “Source files could not be found”

This is the most common DISM error.

It means DISM can’t get the repair files from Windows Update.

Fix: Use a local repair source

Mount a Windows 10 ISO and run:

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

(Replace D: with the ISO drive letter.)

If you see install.esd instead of install.wim, use:

/Source:D:\sources\install.esd

This fixes almost every 0x800f081f case.

DISM Error 0x800f0906 — “The source files could not be downloaded”

Almost always caused by:

firewall blocking Windows Update
disabled network features
group policy restrictions
offline PCs

Fix 1: Enable repair content download

Run:

gpedit.msc

Navigate to:

Computer Configuration → Administrative Templates → System → Specify settings for optional component installation and component repair

Set to:

Enabled
Tick “Contact Windows Update directly”

Fix 2: Reset Windows Update components

Run these:

net stop wuauserv
net stop bits
net stop cryptsvc

Then delete:

C:\Windows\SoftwareDistribution

Restart services:

net start wuauserv
net start bits
net start cryptsvc

Error 0x800f0954 — “DISM failed due to WSUS policy”

This means your PC is configured to only get repairs from a corporate WSUS server.

Fix 1: Override WSUS temporarily

Run:

reg add HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate /v DisableWindowsUpdateAccess /t REG_DWORD /d 1 /f

Then run RestoreHealth again.

Fix 2: Use a local ISO

Often easier and faster:

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

Error 0x800f0922 — “DISM cannot process the command”

Usually caused by:

insufficient system reserved partition space
missing WinRE
corrupted servicing stack

Fix: Install latest Servicing Stack Update (SSU)

Run Windows Update → Check for updates.

Error 0x800f082f — Component Store corruption too severe

This happens when the system image is damaged beyond DISM’s automatic repair.

Fix:

Use Method 2 with a source (ISO).

If that fails:

Run SFC /Scannow
Run DISM again
Perform an in-place repair install (no data loss)

Error: “The component store cannot be repaired”

This is the worst-case scenario.

DISM cannot fix the image using:

Windows Update
Local files
Component store

Fix:

Perform a repair install using the Windows ISO.

This keeps your files & apps while reinstalling Windows system files.

Error 87 — The DISM command is incorrect

You typed the command wrong.

Common mistakes:

missing spaces
wrong slashes
incorrect parameters
unsupported commands

Always use the exact format:

DISM /Online /Cleanup-Image /RestoreHealth

Error: “Not enough memory/resources”

Typically caused by third-party antivirus blocking DISM.

Fix:

Disable antivirus
Restart PC
Try again

Summary Table of DISM Errors

Error Code	Meaning	Fix
0x800f081f	Missing source files	Use ISO `/Source:` repair
0x800f0906	Files can’t download	Group policy + reset WU
0x800f0954	WSUS blocking	Override WSUS or use ISO
0x800f0922	Servicing stack issue	Install SSU
0x800f082f	Severe corruption	ISO repair or reinstall
Error 87	Wrong syntax	Correct the command

Advanced DISM Commands (Check Disk, Analyze Component Store, Clean Up WinSxS)

If you want to go beyond basic repairs, DISM includes several powerful advanced commands.
These tools help you:

free up disk space
analyse system health
clean up old Windows update files
check the Windows Component Store (WinSxS)
optimise Windows servicing

These commands aren’t required for normal repairs — but they are incredibly useful when maintaining or optimising Windows.

Let’s walk through the most important ones.

1. DISM AnalyzeComponentStore (Check WinSxS Size)

The WinSxS folder stores:

updates
backups
system components
old Windows files

Over time, it grows massively.

To analyse it:

DISM /Online /Cleanup-Image /AnalyzeComponentStore

This gives you:

component store size
number of reclaimable packages
whether a cleanup is recommended

When to run it:

low disk space
updates failing
slow Windows servicing

2. Clean Up WinSxS (WinSxS cleanup – remove old updates & backups safely)

This command removes superseded (old) versions of Windows components.

Run:

DISM /Online /Cleanup-Image /StartComponentCleanup

This:

frees space
improves performance
reduces servicing errors

Optional: Remove ALL superseded components

(This makes updates irreversible — use with caution.)

DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase

This permanently deletes all ability to uninstall updates.

3. Repair Windows Using a Mounted Image (Offline DISM Repair)

If the system won’t boot, you can repair Windows offline.

Boot from USB → open Command Prompt → run:

DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim

Replace:

C: with your Windows drive
D: with your USB or ISO drive

This method is extremely powerful for fixing:

unbootable Windows
blue screens
missing system files

Repair or reinstall Windows using USB

4. Check System Image Health Without Using Windows Update

If you disable internet access or don’t want DISM using online sources, run:

DISM /Online /Cleanup-Image /ScanHealth /LimitAccess

or:

DISM /Online /Cleanup-Image /RestoreHealth /LimitAccess

This forces DISM to use only local sources.

5. Clean Up Old Windows Installations (Windows.old Folder)

When you upgrade Windows, the old version is stored in Windows.old.

Delete old installations:

DISM /Online /Cleanup-Image /StartComponentCleanup

or use:

cleanmgr.exe

Useful when:

you need storage
you’re not planning to roll back

6. Reduce Windows Update Cleanup Size

DISM can remove deeply cached update backups:

DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase

Warning: You cannot uninstall updates afterwards.

7. Check Disk Health (DISM + CHKDSK Combo)

After repairing corruption, check disk integrity:

chkdsk /f /r

Doing this after DISM ensures:

the disk is healthy
there are no bad sectors
file corruption won’t return

8. Export a Clean Windows Image (For Tech Users)

Useful for creating customised repair sources.

DISM /Online /Export-Image /SourceImageFile:C:\install.wim /DestinationImageFile:D:\clean.wim /Compress:Max

This is a technician-level tool but useful in enterprise environments.

Summary of Advanced DISM Tools

Command	Purpose
AnalyzeComponentStore	Check size of Windows component store
StartComponentCleanup	Remove old updates & free space
ResetBase	Make updates permanent & reduce size
Offline RestoreHealth	Repair an unbootable PC
LimitAccess	Stop DISM using Windows Update
Export-Image	Create clean Windows images

These commands give you complete control over the health and performance of your Windows installation.

Fix performance issues and free space

Conclusion — The Complete DISM Repair Workflow (2026 Version)

At this point, you now understand what most Windows users never learn:

how DISM works
when to use it
how to fix Windows corruption
what to do when DISM fails
how DISM and SFC support each other
how to use advanced cleanup tools
how to recover Windows even if it won’t boot

This merged guide replaces every fragmented tutorial and scattered command list with one simple, reliable repair process.

Below is the official 2026 DISM workflow, rewritten to be beginner-friendly and technician-ready.

🔥 The Complete Windows Repair Sequence (Step-by-Step)

1️⃣ Check for corruption

DISM /Online /Cleanup-Image /CheckHealth

2️⃣ Deep scan for corruption

DISM /Online /Cleanup-Image /ScanHealth

3️⃣ Repair Windows image

DISM /Online /Cleanup-Image /RestoreHealth

4️⃣ If DISM fails, repair with ISO

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

5️⃣ Repair live system files

sfc /scannow

6️⃣ Optional — cleanup old update files

DISM /Online /Cleanup-Image /StartComponentCleanup

7️⃣ Optional — reduce WinSxS size permanently

DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase

8️⃣ If Windows won’t boot — offline repair

DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim

9️⃣ If everything fails — repair install (keeps your files)

Use the Windows ISO → run Setup.exe → choose:

Keep personal files and apps

This replaces all system files without deleting anything.

What This Workflow Fixes

✔ Windows Update errors
✔ Blue screen errors
✔ Missing or corrupt system files
✔ Programs crashing unexpectedly
✔ Windows features not working
✔ Slow or unstable system behaviour
✔ SFC unable to repair issues
✔ Component store corruption

This single guide now serves as your ultimate Windows repair pillar, merging and improving every previous DISM/SFC article you had.