WindowsAdvanced

DISM /ScanHealth vs /RestoreHealth: Difference, Correct Order & How to Repair Windows 11/10

Windows includes a powerful built-in repair tool called DISM — Deployment Image Servicing and Management. Two of the most commonly used commands are: DISM /O...

Bison Technical Team Enterprise IT specialists

Updated 12 Oct 2024 17 min read 681 total views

Structured technical guidanceSafety notes included where requiredSources listed below

Windows includes a powerful built-in repair tool called DISM — Deployment Image Servicing and Management.

Two of the most commonly used commands are:

DISM /Online /Cleanup-Image /ScanHealth

and:

DISM /Online /Cleanup-Image /RestoreHealth

Although they look similar, they perform different jobs.

The short answer is:

/ScanHealth checks the Windows component store for corruption but does not repair it.

/RestoreHealth scans for corruption and attempts to repair the Windows image automatically.

For most Windows repair situations, the practical workflow is:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

You can run /ScanHealth first when you specifically want to confirm whether component-store corruption exists before performing a repair.

This guide explains the difference between CheckHealth, ScanHealth, RestoreHealth and SFC, the correct order to run them, what each result means, and how to fix common DISM errors such as 0x800f081f — source files could not be found.

Quick Answer: ScanHealth vs RestoreHealth

Command	What It Does	Repairs Problems?
`DISM /Online /Cleanup-Image /CheckHealth`	Checks whether corruption has already been detected and whether the image is repairable	No
`DISM /Online /Cleanup-Image /ScanHealth`	Performs a more extensive scan of the Windows component store	No
`DISM /Online /Cleanup-Image /RestoreHealth`	Scans the component store and attempts to repair corruption	Yes
`sfc /scannow`	Scans protected Windows system files and replaces corrupted files where possible	Yes

Recommended Repair Sequence

For an ordinary Windows repair:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Microsoft currently recommends running DISM before SFC when repairing corrupted Windows system files.

What Is DISM?

DISM stands for:

Deployment Image Servicing and Management

It is built into modern versions of Windows and Windows Server.

DISM can service and repair:

the currently running Windows installation;
offline Windows images;
Windows Imaging Format files;
virtual hard disk images;
the Windows component store.

For normal troubleshooting on the computer you are currently using, you will typically use:

DISM /Online /Cleanup-Image ...

What Does /Online Mean?

In:

DISM /Online /Cleanup-Image /RestoreHealth

the /Online switch does not mean “use the internet.”

It means:

Service the Windows operating system that is currently running.

This is an important distinction.

For example:

DISM /Online /Cleanup-Image /ScanHealth

means:

Scan the component store of the currently running Windows installation.

It does not simply mean “connect to Windows Update.”

What Does /Cleanup-Image Mean?

/Cleanup-Image tells DISM that you want to perform servicing, analysis or repair operations on the Windows image/component store.

It is used with options such as:

/CheckHealth
/ScanHealth
/RestoreHealth

What Is the Windows Component Store?

The Windows component store is commonly associated with:

C:\Windows\WinSxS

It contains Windows components used for:

servicing Windows;
installing updates;
enabling Windows features;
repairing protected system files;
maintaining component versions.

If the component store becomes corrupted, Windows may experience problems such as:

Windows Update failures;
missing or damaged components;
Windows features failing to install;
SFC being unable to repair files;
DISM errors;
system instability.

This is why DISM is important.

DISM /CheckHealth Explained

The command is:

DISM /Online /Cleanup-Image /CheckHealth

/CheckHealth performs a quick check.

It determines whether the Windows image has already been flagged as corrupted and whether the corruption is considered repairable.

It does not perform a full corruption scan.

It also does not repair anything.

When Should You Use CheckHealth?

Use /CheckHealth when you want a quick status check.

Example:

DISM /Online /Cleanup-Image /CheckHealth

Possible results can indicate that:

no component-store corruption is detected;
the component store is repairable;
the image is non-repairable.

DISM /ScanHealth Explained

The command is:

DISM /Online /Cleanup-Image /ScanHealth

/ScanHealth performs a more extensive scan of the Windows component store for corruption.

It can take several minutes or longer depending on:

system speed;
storage performance;
Windows condition;
component-store size.

Important

/ScanHealth:

detects corruption

but:

does not repair corruption

If /ScanHealth finds that the component store is repairable, you normally proceed with:

DISM /Online /Cleanup-Image /RestoreHealth

What Does “The Component Store Is Repairable” Mean?

If DISM displays:

The component store is repairable.

this generally means DISM has detected corruption that it believes can be repaired.

The next logical command is:

DISM /Online /Cleanup-Image /RestoreHealth

After the repair completes successfully, you can run:

sfc /scannow

to scan and repair protected Windows system files.

What Does “No Component Store Corruption Detected” Mean?

If DISM reports:

No component store corruption detected.

the Windows component store appears healthy according to the DISM check.

However, this does not necessarily mean every Windows system file is perfect.

If you are troubleshooting damaged Windows system files, you can still run:

sfc /scannow

DISM /RestoreHealth Explained

The command is:

DISM /Online /Cleanup-Image /RestoreHealth

/RestoreHealth does two important things:

scans the Windows image/component store for corruption;
automatically attempts to repair detected corruption.

This is the primary DISM command used during many Windows-repair procedures.

Does RestoreHealth Need ScanHealth First?

No.

You do not have to run /ScanHealth before /RestoreHealth.

/RestoreHealth performs the corruption scan required for the repair operation itself.

Therefore, if your objective is simply:

Repair Windows

you can normally run:

DISM /Online /Cleanup-Image /RestoreHealth

directly.

When Is ScanHealth Useful?

/ScanHealth is useful when:

you only want to diagnose;
you want to record the state before making repairs;
you are troubleshooting a server and want evidence before changing anything;
you are investigating whether the component store is actually corrupted.

Correct Order: CheckHealth, ScanHealth, RestoreHealth and SFC

There is no requirement to run every command every time.

Diagnostic Workflow

If you want to thoroughly inspect first:

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Practical Repair Workflow

For most repair cases:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Microsoft currently recommends the second order for system-file repair:

DISM first → SFC second

Why Run DISM Before SFC?

This is an important concept.

SFC /scannow repairs protected Windows system files.

But SFC may rely on healthy Windows components when replacing damaged files.

If the component store itself is corrupted, SFC may be unable to complete repairs successfully.

Therefore the preferred workflow is:

Repair the Windows image/component store with DISM

then:

repair protected system files with SFC

How to Run DISM Correctly

Step 1: Open Command Prompt as Administrator

Press:

Start

Search for:

cmd

Right-click:

Command Prompt

Select:

Run as administrator

You can also use Windows Terminal (Admin).

Step 2: Run RestoreHealth

Enter:

DISM /Online /Cleanup-Image /RestoreHealth

Press Enter.

Allow the command to finish.

Do not close the window simply because the percentage appears stuck temporarily.

Step 3: Run SFC

After DISM reports that the operation completed successfully, run:

sfc /scannow

Wait until verification reaches:

100%

Step 4: Restart Windows

After the repair process completes, restarting Windows is generally advisable—especially if you were troubleshooting:

Windows Update;
corrupted system files;
application failures;
Windows components;
servicing problems.

Does DISM /RestoreHealth Use Windows Update?

For an online image, DISM can use Windows Update or another configured repair source to obtain required repair files.

The source behavior can depend on:

Windows configuration;
Group Policy;
repair-source settings;
whether /Source is specified;
whether /LimitAccess is used.

Therefore the simple statement:

“RestoreHealth always downloads files from Windows Update”

is not completely accurate in every environment.

What Is the /Source Option?

If DISM cannot obtain required repair files automatically, you can specify an alternative repair source.

Example:

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

In this example:

C:\RepairSource\Windows

must be replaced with an appropriate Windows repair source.

Microsoft also supports using sources such as:

a mounted Windows image;
Windows installation media;
network repair source;
other supported Windows source locations.

What Does /LimitAccess Mean?

/LimitAccess tells DISM not to use Windows Update as a repair source or backup repair source.

Example:

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

This is particularly useful in:

enterprise networks;
controlled Windows Server environments;
offline systems;
environments where Windows Update access is restricted;
situations where you deliberately want DISM to use your specified source.

DISM Error 0x800f081f — Source Files Could Not Be Found

One of the most common errors is:

Error: 0x800f081f

The source files could not be found.

This means DISM could not locate suitable files required for the repair.

The first command to try is still:

DISM /Online /Cleanup-Image /RestoreHealth

If the automatic repair source fails, you may need to provide a compatible repair source.

Why Does Error 0x800f081f Occur?

Possible reasons include:

Windows Update cannot provide the required files;
the repair source is missing;
the repair source does not match the Windows installation closely enough;
Group Policy restricts repair-source behavior;
the source media is older than the installed Windows servicing level;
required component files are unavailable;
Windows Update itself is damaged.

Using Windows Installation Media as a DISM Source

If you have compatible Windows installation media, mount the ISO.

Assume it appears as:

D:

Look inside:

D:\sources

You may find:

install.wim

or:

install.esd

The correct Windows edition/index must be identified before using the file as a repair source.

Find the Correct WIM Index

If the source contains:

install.wim

run:

DISM /Get-WimInfo /WimFile:D:\sources\install.wim

DISM will display the editions stored inside the image.

Identify the index matching the installed Windows edition.

For example:

Index : 6
Name  : Windows 11 Pro

The actual index varies by installation media.

RestoreHealth Using install.wim

Example:

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

Replace:

D:

with the actual mounted ISO drive letter.

Replace:

with the correct Windows image index.

RestoreHealth Using install.esd

If your installation media contains:

install.esd

first check the available editions:

DISM /Get-WimInfo /WimFile:D:\sources\install.esd

Then use the appropriate source.

Example:

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

Again, replace the drive letter and index with the values appropriate to your system.

Important: Repair Source Must Be Compatible

Do not blindly download any Windows ISO and use it as a DISM repair source.

Microsoft notes that repair-source compatibility matters.

The repair source should correspond appropriately with the target Windows version and servicing level.

A repair can fail when the target Windows installation requires component versions not available in the repair source.

This is especially important on:

Windows Server;
heavily updated Windows systems;
enterprise-managed systems;
older ISO media.

How to Check Your Windows Version

Press:

Win + R

Type:

winver

and press Enter.

You can also run:

DISM /Online /Get-CurrentEdition

and:

systeminfo

to gather additional system information.

DISM RestoreHealth Stuck at 20%, 40% or 62.3%

DISM sometimes appears to remain at one percentage for a long period.

This does not necessarily mean it has frozen.

Depending on the computer and repair operation, progress can pause visually while DISM continues working.

Do not immediately:

close Command Prompt;
restart Windows;
force-stop DISM.

First check whether:

disk activity continues;
CPU activity exists;
DISM is still running;
the system remains responsive.

On slow disks or damaged systems, DISM can take significant time.

How Long Does DISM RestoreHealth Take?

There is no fixed duration.

It can take:

several minutes;
20–30 minutes;
longer on slow or heavily damaged systems.

Factors include:

SSD vs HDD;
system load;
component-store condition;
Windows Update connectivity;
repair-source location;
server workload.

Can I Use My Computer While DISM Runs?

For ordinary desktops, you can often continue light work.

However, during serious repair operations it is better to avoid:

restarting Windows;
shutting down;
forcing DISM to close;
installing major updates simultaneously.

On production servers, schedule servicing appropriately.

What Does “The Restore Operation Completed Successfully” Mean?

If DISM displays:

The restore operation completed successfully.

the Windows image repair operation completed successfully.

Next run:

sfc /scannow

Then review the SFC result.

Common SFC Results After DISM

Result 1

Windows Resource Protection did not find any integrity violations.

No protected system-file corruption was detected.

Result 2

Windows Resource Protection found corrupt files and successfully repaired them.

SFC detected damaged system files and repaired them.

Result 3

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

Additional troubleshooting may be required.

What If RestoreHealth Fails?

If:

DISM /Online /Cleanup-Image /RestoreHealth

fails, note the exact:

error code;
error message;
percentage where it failed.

Useful areas to investigate include:

repair source;
Windows Update;
servicing stack;
component-store corruption;
disk problems;
Group Policy;
CBS/DISM logs.

Where Is the DISM Log File?

DISM normally writes information to:

C:\Windows\Logs\DISM\dism.log

This log can be useful when troubleshooting:

failed repair operations;
missing sources;
servicing errors;
component problems.

Where Is the CBS Log?

Windows servicing and SFC information can also appear in:

C:\Windows\Logs\CBS\CBS.log

The CBS log can be very large.

Use it when deeper troubleshooting is necessary rather than as the first step for every user.

DISM vs SFC — What Is the Difference?

Feature	DISM	SFC
Full name	Deployment Image Servicing and Management	System File Checker
Main target	Windows image/component store	Protected Windows system files
Detects corruption	Yes	Yes
Repairs corruption	RestoreHealth can repair component store	Yes, where repair data is available
Can use external repair source	Yes	Not in the same way
Typical command	`DISM /Online /Cleanup-Image /RestoreHealth`	`sfc /scannow`
Recommended repair order	First	After DISM

A simplified way to remember it is:

DISM repairs the Windows repair source/component store.

SFC repairs protected Windows system files.

Should I Run SFC First or DISM First?

For the current Microsoft-supported repair workflow:

DISM first

then:

SFC

Use:

DISM /Online /Cleanup-Image /RestoreHealth

followed by:

sfc /scannow

Do I Need to Run CheckHealth and ScanHealth Every Time?

No.

You do not need to run:

CheckHealth
ScanHealth
RestoreHealth

every time.

If you only want to repair Windows, running:

DISM /Online /Cleanup-Image /RestoreHealth

directly is sufficient in many situations.

Run /CheckHealth or /ScanHealth when you specifically want diagnostic information before repairing.

Can DISM Fix Windows Update Problems?

It can fix Windows Update issues caused by component-store corruption.

Microsoft uses DISM /RestoreHealth in current Windows Update troubleshooting guidance for several servicing/component corruption errors.

However:

DISM is not a universal fix for every Windows Update error.

Problems can also be caused by:

network connectivity;
update services;
permissions;
Group Policy;
WSUS configuration;
third-party security software;
disk problems;
update metadata;
insufficient disk space.

Can DISM Fix Blue Screens?

DISM can repair corrupted Windows components that may contribute to instability.

But it is not a universal Blue Screen repair tool.

BSODs can be caused by:

drivers;
failing RAM;
failing SSD/HDD;
overheating;
firmware;
antivirus/EDR drivers;
hardware problems;
software bugs.

Use the BSOD stop code and dump analysis where appropriate.

Can DISM Repair a Broken Windows Installation?

Sometimes.

DISM is useful when:

Windows still boots;
component-store corruption exists;
Windows Update is failing due to servicing corruption;
SFC cannot repair files because the repair source is damaged.

But severe Windows problems may require:

Startup Repair;
System Restore;
repair installation/in-place upgrade;
restoring from backup;
offline servicing;
reinstalling Windows.

Can I Run DISM in Safe Mode?

Some DISM operations can be run in Safe Mode, but the availability of services and repair sources may differ.

For standard online repair, normal Windows mode with an elevated Command Prompt is generally preferable unless troubleshooting requires Safe Mode.

Can I Run DISM from PowerShell?

Yes.

You can run the same executable command from elevated PowerShell:

DISM /Online /Cleanup-Image /RestoreHealth

Windows also provides DISM-related PowerShell cmdlets such as:

Repair-WindowsImage -Online -ScanHealth

and:

Repair-WindowsImage -Online -RestoreHealth

For many users, the standard DISM command-line syntax is easier to find and troubleshoot.

Windows Server and RDS Considerations

The same DISM concepts apply to supported Windows Server versions.

However, on a production server:

verify backups;
use an approved maintenance window;
check active RDS users;
avoid unnecessary restart during business hours;
verify server roles after repair;
review servicing logs;
use a compatible repair source.

On servers connected to WSUS or controlled by Group Policy, the repair-source behavior may differ from an ordinary home PC.

Recommended DISM Repair Workflow

For Windows 11/10 Desktop

Run:

DISM /Online /Cleanup-Image /RestoreHealth

Then:

sfc /scannow

Restart Windows.

Recommended Diagnostic Workflow

If you want to diagnose before repairing:

DISM /Online /Cleanup-Image /CheckHealth

Then:

DISM /Online /Cleanup-Image /ScanHealth

If corruption is reported:

DISM /Online /Cleanup-Image /RestoreHealth

Then:

sfc /scannow

Common Mistakes to Avoid

Mistake 1: Thinking /Online Means Internet

It means the currently running Windows installation.

Mistake 2: Expecting /ScanHealth to Repair Windows

/ScanHealth only scans.

Mistake 3: Running SFC Repeatedly Without Repairing the Component Store

If the repair source/component store is damaged, run DISM first.

Mistake 4: Using an Incorrect ISO Source

An incompatible repair source can cause errors.

Mistake 5: Stopping DISM Because the Percentage Does Not Change

DISM can appear stuck while still processing.

Mistake 6: Using /LimitAccess Without Understanding It

/LimitAccess prevents Windows Update from being used as a repair source.

Mistake 7: Assuming DISM Fixes Every Windows Problem

DISM primarily repairs the Windows image/component store. Hardware, driver and application problems require separate troubleshooting.

Quick DISM Command Reference

Quick Health Check

DISM /Online /Cleanup-Image /CheckHealth

Detailed Corruption Scan

DISM /Online /Cleanup-Image /ScanHealth

Scan and Repair

DISM /Online /Cleanup-Image /RestoreHealth

Repair Windows System Files After DISM

sfc /scannow

Repair Using a Specified Source

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

Check WIM Editions

DISM /Get-WimInfo /WimFile:D:\sources\install.wim

Frequently Asked Questions (FAQ)

1. What is DISM /ScanHealth?

/ScanHealth performs a detailed scan of the Windows component store for corruption. It does not repair corruption.

2. What is DISM /RestoreHealth?

/RestoreHealth scans the Windows component store and attempts to repair detected corruption automatically.

3. What is the difference between ScanHealth and RestoreHealth?

ScanHealth only detects corruption. RestoreHealth detects and repairs corruption.

4. Does RestoreHealth include ScanHealth?

RestoreHealth performs the scanning required for its repair operation, so you do not have to run ScanHealth first.

5. Should I run ScanHealth before RestoreHealth?

Only if you specifically want a diagnostic scan first. It is not mandatory.

6. What is DISM /CheckHealth?

It performs a quick check to determine whether the image has already been flagged as corrupted and whether the corruption is repairable.

7. Which DISM command should I run first?

For a practical repair, run:

DISM /Online /Cleanup-Image /RestoreHealth

then:

sfc /scannow

8. Should I run SFC before or after DISM?

Microsoft currently recommends running DISM before SFC for Windows system-file repair.

9. Does DISM RestoreHealth delete my files?

DISM image repair is not designed to delete your personal files.

However, maintain backups of important data before significant system-repair work.

10. Does DISM require internet?

Not necessarily.

DISM can use Windows Update or another configured repair source. You can also specify a local/network repair source.

11. What does /Online mean?

It means DISM is servicing the Windows installation currently running on the computer.

12. Why is DISM stuck at 62.3%?

The displayed percentage may remain unchanged while DISM continues processing. Give it sufficient time before assuming it has frozen.

13. How long should RestoreHealth take?

It varies from several minutes to considerably longer depending on system speed, corruption and repair-source availability.

14. What does “component store is repairable” mean?

DISM detected corruption that it believes RestoreHealth can repair.

15. What does “no component store corruption detected” mean?

DISM did not detect component-store corruption during the check.

16. What does error 0x800f081f mean?

DISM could not find suitable source files required for the repair.

17. Can I use a Windows ISO with RestoreHealth?

Yes, if the source is appropriate and compatible with the installed Windows version/build and you select the correct image index.

18. What is /LimitAccess?

It prevents DISM from contacting Windows Update as a repair source or backup source.

19. Where is the DISM log?

Normally:

C:\Windows\Logs\DISM\dism.log

20. Where is the CBS log?

Normally:

C:\Windows\Logs\CBS\CBS.log

21. Can DISM fix Windows Update?

It can repair component-store corruption that causes some Windows Update failures, but it does not fix every update problem.

22. Can DISM fix SFC errors?

Repairing the Windows component store with DISM can allow SFC to successfully replace system files that it previously could not repair.

23. Can I run RestoreHealth twice?

If troubleshooting requires it, rerunning RestoreHealth after resolving a source or servicing issue is generally possible. Do not repeatedly rerun it without investigating a consistent failure.

24. Can DISM repair Windows Server?

Yes. DISM is used extensively with Windows Server, but production systems should be repaired using appropriate maintenance and compatible sources.

25. What are the two most useful commands for normal Windows repair?

For most users:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Final Recommendation

For most Windows 11 and Windows 10 repair situations, use:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM completes successfully, run:

sfc /scannow

Remember:

CheckHealth = quick status check

ScanHealth = detailed corruption scan

RestoreHealth = scan + repair

SFC = repair protected Windows system files

You do not need to run every DISM health command every time.

If your goal is simply to repair Windows:

RestoreHealth → SFC → Restart

is usually the most practical workflow.

If RestoreHealth fails with a source-related error such as 0x800f081f, investigate the repair source rather than repeatedly running the same command.

Technical Disclaimer

DISM repair behavior can vary depending on:

Windows version;
Windows Server version;
update level;
repair-source configuration;
Group Policy;
WSUS;
installation media;
servicing state.

On business-critical servers, take appropriate backups and perform servicing during a controlled maintenance window.

DISM ScanHealth vs RestoreHealth: Difference & Correct Order

What is the difference between DISM /ScanHealth and /RestoreHealth? Learn CheckHealth, RestoreHealth, SFC order, fix 0x800f081f, use Windows ISO sources and repair Windows 11/10 correctly.

#DISM #DISMScanHealth #DISMRestoreHealth #DISMCheckHealth #ScanHealth #RestoreHealth #CheckHealth #WindowsRepair #Windows11 #Windows10 #WindowsServer #WindowsTroubleshooting #SFC #SFCScannow #SystemFileChecker #ComponentStore #WinSxS #WindowsCorruption #WindowsUpdate #WindowsUpdateRepair #DISMError #0x800f081f #WindowsISO #InstallWIM #InstallESD #RepairWindows #WindowsCommands #CommandPrompt #PowerShell #WindowsTerminal #SystemAdministrator #WindowsAdmin #ITSupport #EnterpriseIT #ServerRepair #RDSServer #WindowsRDS #WindowsMaintenance #SystemRepair #WindowsSystemFiles #WindowsImage #RepairSource #MicrosoftWindows #WindowsTips #WindowsHelp #TechSupport #DISMTroubleshooting #SystemCorruption #BISONKnowledgebase #BISONKB

YOUR FEEDBACK

Was this guide useful?

Your answer helps us keep BISONKB accurate and practical.