What Is DISM /RestoreHealth in Windows 11 (and 10)? Complete Guide

When System File Checker (SFC) reports that it “found corrupt files but was unable to fix some of them”, the next tool you should think of is DISM. Well, Deployment Image Servicing and Management (DISM.exe) is a powerful command‑line tool built into Windows 10 and Windows 11. It can scan, repair, and service the Windows system image, also known as the component store (WinSxS). Once the component store is healthy, tools like SFC can properly repair corrupted system files.

This guide explains what DISM /RestoreHealth is, how it works, and how to use it correctly in Windows 10 and 11, including advanced usage with a local source when Windows Update is broken.

What is DISM in Windows 10 and 11?

DISM stands for Deployment Image Servicing and Management. It is a command line tool built into Windows 10 and Windows 11 that lets you:

• Inspect and repair the Windows system image (the files Windows uses to install and repair itself).
• Fix problems in the component store (WinSxS) that prevent updates or SFC from working.
• Add, remove or repair Windows features and packages (more advanced admin tasks).

Usually, to fix corrupted system files, you need to run DISM with the /Online /Cleanup-Image options, especially /RestoreHealth, which repairs the currently running Windows installation.

What Is the Windows Component Store (WinSxS)?

Before you understand DISM /RestoreHealth, you first need to know about the Windows component store, stored in the WinSxS folder.

• The component store contains all the files needed for Windows to function, including many versions of system components.
• When Windows updates or optional features are installed, they use files from this store.
• If the component store becomes corrupted or inconsistent, tools like SFC may fail to repair system files, and you may see update errors, crashes, or blue screens.

DISM /RestoreHealth specifically targets this component store. It checks it for corruption and repairs or replaces damaged components so that Windows can use them again.

Common causes of component store corruption include:

• Failed or incomplete Windows updates
• Power loss during servicing operations
• Malware or third‑party system tools
• Disk errors or failing storage devices

DISM Health Check Commands: /CheckHealth, /ScanHealth, /RestoreHealth

DISM offers three key options for checking and repairing the health of your Windows image:

1. /CheckHealth – Quick corruption flag check
2. /ScanHealth – Deep scan of the image for component corruption
3. /RestoreHealth – Scans and repairs component store corruption

All of these use the /Online switch when you’re working on the running operating system.

DISM /Online /Cleanup-Image /CheckHealth

This is a quick check to see whether the image is flagged as corrupted.

DISM /Online /Cleanup-Image /CheckHealth

• Runs very quickly (usually under a minute).
• Does not perform a full scan.
• Tells you if the image is marked as repairable or not.

DISM /Online /Cleanup-Image /ScanHealth

This performs a more thorough scan of the Windows image for component store corruption.

DISM /Online /Cleanup-Image /ScanHealth

• Takes longer than CheckHealth (often several minutes).
• Logs any issues it finds, but does not attempt repairs.
• Useful when you want to confirm whether deeper corruption exists.

DISM /Online /Cleanup-Image /RestoreHealth

This is the main repair command most users need.

DISM /Online /Cleanup-Image /RestoreHealth

• Scans the Windows image for corruption.
• Attempts to repair the image using Windows Update or another specified source.
• It can take 10–15 minutes or more, depending on your hardware and connection.

Tip: If you repeatedly run sfc /scannow and it cannot repair some files, running DISM /RestoreHealth is the recommended next step.

How to Use DISM /RestoreHealth in Windows 10 & 11

You can run DISM commands from Command Prompt, PowerShell, or Windows Terminal, as long as you open them with administrator rights.

Step 1: Open an Elevated Command Line

1. Press Windows key + S, type cmd.
2. Right‑click Command Prompt and choose Run as administrator.
   – or –
   Open Windows Terminal (Admin) and choose Command Prompt or PowerShell.

Step 2: (Optional) Quick Health Check

Run a quick check to see if the image is flagged as corrupted:

DISM /Online /Cleanup-Image /CheckHealth

If it reports that the image is repairable or corruption is detected, proceed with a full repair.

Step 3: Run DISM /ScanHealth (Optional but Recommended)

For a more detailed scan before repairing, use:

DISM /Online /Cleanup-Image /ScanHealth

This scan might take several minutes. Once it completes, you can move on to the actual repair.

Step 4: Run DISM /RestoreHealth

Now run the main repair command:

DISM /Online /Cleanup-Image /RestoreHealth

What this does:

• Scans the component store (WinSxS) for corruption.
• Contact Windows Update by default to download clean versions of any damaged components.
• Replaces or repairs the corrupted data.

During this process, you’ll see the progress percentage increase slowly. Do not close the window or restart your computer until the operation has finished.

When it’s done, you should see a message that the operation completed successfully.

Step 5: Run SFC /scannow Again

After repairing the image with DISM, run SFC again to fix any remaining system file issues:

sfc /scannow

This time, SFC should be able to repair most or all of the corrupted files because the underlying image is healthy.

Restart your PC once everything has completed, and check whether your original issues are resolved.

Using DISM with a Local Source (WIM/ESD)

Sometimes Windows Update is broken, blocked by a firewall, or you are using a network without internet access. In these cases, DISM /RestoreHealth may fail with errors like 0x800f081f or 0x800f0906.

In such situations, you can tell DISM to use a local source, such as a mounted Windows 10 or 11 ISO, or a local network share that contains the installation files.

Step 1: Get a Matching Windows ISO

1. Download a Windows 10 or Windows 11 ISO directly from Microsoft’s official site.
2. Make sure the ISO matches your installed edition and language as closely as possible (for best results).

Step 2: Mount the ISO

1. Right‑click the ISO file and select Mount.
2. Note the drive letter assigned to the mounted ISO (for example, D:).

Step 3: Run DISM with Source and LimitAccess

Use a command like this (adjust D: if needed):

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

Explanation:

• /Source:wim:D:\sources\install.wim:1 – tells DISM to use the install.wim file at index 1 inside the sources folder on drive D:.
• /LimitAccess – prevents DISM from using Windows Update; it only uses the specified source.

On some ISOs, you may have install.esd instead of install.wim. You can point DISM directly to the ESD file or convert it to WIM first.

After the command completes successfully, run:

sfc /scannow

Then restart your PC.

Common DISM Errors and How to Fix Them

When using DISM /RestoreHealth in Windows 10 or 11, you may encounter some common error codes.

Error 0x800f081f – The source files could not be found

This usually means that DISM could not find the required files from Windows Update or your specified source.

Try the following:

• Make sure you have a stable internet connection and Windows Update is not blocked by a firewall or proxy.
• Run DISM again with the /Source parameter pointing to a valid Windows ISO (install.wim or install.esd).
• Check that the ISO version and edition match your installed Windows.

Error 0x800f0906 – The source file could not be downloaded

This is often related to Windows Update issues or network problems.

• Restart your router and check your internet connection.
• Temporarily disable any VPN or third‑party firewall.
• Reset Windows Update components (you can use a script or manually stop services like wuauserv and bits, clear the SoftwareDistribution folder, then restart services).
• Use the /Source option with a mounted ISO if Windows Update remains unavailable.

DISM Hangs or Stays at a Certain Percentage

Sometimes DISM appears stuck at a specific percentage for a long time (e.g., 20% or 62%). This does not always mean it has frozen.

• Wait at least 30–60 minutes, especially on slower systems or HDDs.
• Make sure your system is not running on battery saver mode.
• Check Task Manager to confirm dism.exe is still using CPU or disk.

If it truly never completes, try:

• Running DISM again in Safe Mode with Networking.
• Running CHKDSK /f /r on your system drive to rule out disk problems.
• Using a local source ISO instead of Windows Update.

When to Use DISM vs SFC

Many users wonder whether they should run SFC or DISM first. A good, practical approach is:

1. Run SFC first:
   • sfc /scannow
     If SFC reports no problems or repairs them successfully, you may not need DISM.
2. If SFC cannot repair files:
   • Run DISM /Online /Cleanup-Image /RestoreHealth.
   • Then run sfc /scannow again.
3. If DISM fails or reports that the image is irreparable:
   • Check for disk errors with CHKDSK.
   • Install the latest Windows updates.
   • Try System Restore to roll back recent changes.
   • As a last resort, use Reset this PC or a clean installation.

For a full repair workflow using SFC, DISM, CHKDSK, Windows Update, System Restore and Reset this PC, see our guide: How to Repair Corrupted System Files in Windows 10 and 11.

Frequently Asked Questions About DISM /RestoreHealth

Q. What does DISM /Online /Cleanup-Image /RestoreHealth do?
This command scans the Windows component store (WinSxS) for corruption and repairs it using files from Windows Update or a specified source. Once the component store is healthy, SFC can successfully repair corrupted system files.

Q. Is it safe to run DISM /RestoreHealth?
Yes, DISM /RestoreHealth is a Microsoft‑supported command and is safe to run on Windows 10 and Windows 11. It does not erase your personal files. However, you should avoid interrupting the process once it has started.

Q. How long does DISM /RestoreHealth take?
The time varies depending on your hardware and the level of corruption:

• On a fast SSD with a good connection, it may take 10–20 minutes.
• On older hardware or systems with more corruption, it may take 30–60 minutes or longer.

If it seems stuck, give it extra time before assuming it has frozen.

Q. Can I use DISM in Windows 11 the same way as in Windows 10?
Yes. The DISM /Online /Cleanup-Image /CheckHealth, /ScanHealth, and /RestoreHealth commands work the same way in Windows 10 and Windows 11. The tool is designed to service the current running operating system (when using /Online).

Q. Should I run DISM in Safe Mode?
You can run DISM in Safe Mode with Networking if:

• The system is unstable or crashes in normal mode.
• Third‑party security software interferes with repairs.

Safe Mode loads fewer drivers and services, which can sometimes help DISM and SFC complete successfully.

Q. What if DISM and SFC both fail to repair my system?
If both tools fail repeatedly, corruption may be too severe or the underlying disk or hardware may be failing.

In that case:

1. Back up important files.
2. Run CHKDSK /f /r on the system drive.
3. Install all pending Windows updates.
4. Try System Restore to roll back to a working state.
5. Use Reset this PC or perform a clean install of Windows if problems continue.