DISM + SFC Workflow: Step-by-Step Windows 10 Repair Guide

Deployment Image Servicing and Management (DISM) and System File Checker (SFC) remain the quickest, least-invasive tools to restore a damaged Windows 10 installation — when used in the correct order, with the right sources, and with realistic expectations about what they can and cannot fix. This article walks through a practical, technician‑grade DISM + SFC workflow, verifies command syntax and behavior against official guidance, explains offline source options (install.wim / install.esd), maps common error codes to remedies, and highlights risks and troubleshooting steps you should try before resorting to an in‑place repair or clean reinstall. The step‑by‑step examples below follow the tested sequence: Check the image, scan it, repair it (prefer local source if necessary), then run SFC to heal the running installation. (learn.microsoft.com)

Background / Overview​

Windows maintains two related but distinct stores of system files: the Component Store (WinSxS) — a repository of files and manifests used for servicing — and the running installation in %windir% (C:\Windows). When Windows updates fail, drivers misbehave, or files become corrupted, the Component Store can be damaged; SFC depends on that store to restore protected files, so SFC alone sometimes reports “found corrupt files but was unable to fix some” because its source is compromised. DISM repairs the underlying component store; SFC then repairs the active installation using the now‑healthy store. This is the recommended sequence used by support engineers and community technicians. (mspcmanager.github.io)
The three DISM checks you’ll use in sequence are:

• DISM /Online /Cleanup-Image /CheckHealth — quick, non‑repair check to see if corruption exists.
• DISM /Online /Cleanup-Image /ScanHealth — deeper scan to detect repairable corruption.
• DISM /Online /Cleanup-Image /RestoreHealth — attempts automatic repair, fetching replacements from Windows Update by default or from a specified local source (install.wim / install.esd) when /Source is provided.

These commands operate on the running Windows installation when used with /Online. You can also use DISM against an offline image with /Image: (common in WinRE or when servicing another volume). (learn.microsoft.com)

---

Why the order matters: DISM first, then SFC​

• DISM repairs the component store (WinSxS). If the store is broken, SFC will often be unable to replace corrupted files because its source is damaged.
• SFC (sfc /scannow) repairs files in the running installation by copying them from the component store. Running SFC after a successful DISM RestoreHealth increases the chance SFC will succeed.

This order is consistently recommended across official guidance and technician resources and is the pragmatic, least‑destructive first step before more invasive actions.

---

Quick verification: where logs live and what they tell you​

When commands fail or behave oddly, the two logs to check are:

• DISM log: C:\Windows\Logs\DISM\dism.log
• SFC / CBS log: C:\Windows\Logs\CBS\CBS.log

These files record step‑by‑step detail and often contain the package or file names the tool could not find or repair — essential evidence when troubleshooting codes like 0x800f081f or 0x800f0906. Always inspect these logs before throwing away time on repeat attempts.

---

Preparations: safety, backups, and matching sources​

Before running DISM and SFC, take the following precautions:

• Create a full backup or at least a system image / restore point. Although DISM and SFC are non‑destructive to personal files, deeper servicing, CHKDSK runs, or follow‑up repairs can carry risk.
• Confirm you have a matching Windows 10 ISO if you need a local source. The ISO must match the edition, architecture (x86/x64), and language (or be close enough) for DISM to use its install.wim/install.esd content reliably.
• If you work in managed environments (WSUS, Intune), ensure you understand update routing — DISM /RestoreHealth by default will attempt to pull replacement files from Windows Update unless you use /LimitAccess.
• If you plan to work from WinRE or a different boot environment, verify drive letters with DiskPart → list volume because letters can change under WinRE.

---

Step‑by‑step: Running DISM to check and repair a Windows 10 image​

1) Open an elevated prompt​

Open Command Prompt or Windows Terminal as Administrator. Commands must run elevated or they will fail.

2) Quick check: CheckHealth​

Run:
DISM /Online /Cleanup-Image /CheckHealth

• Purpose: Very fast check. It only reports whether the component store is flagged as corrupt or repairable; it does not perform a repair.
• When to use: As the first, low‑impact check. If it reports “no component store corruption detected,” you can still run the deeper scan when troubleshooting persistent problems.

3) Deeper scan: ScanHealth​

Run:
DISM /Online /Cleanup-Image /ScanHealth

• Purpose: A thorough scan of the component store that may take several minutes or longer depending on disk speed and system state.
• Output: Reports whether the image is repairable. If it is, you proceed to RestoreHealth.

4) Repair attempt: RestoreHealth (default, online)​

Run:
DISM /Online /Cleanup-Image /RestoreHealth

• Purpose: Scans and attempts to repair component store corruption automatically. By default, DISM will use Windows Update to download replacement packages if it needs files not present locally.
• Notes: It’s normal for RestoreHealth to appear “stuck” at some percentage — let it run. Depending on corruption severity and your network, this can take between several minutes and over an hour. These time estimates are approximate; always consult the logs for progress details.

---

When RestoreHealth fails to download files: using a local source​

If DISM returns error codes like 0x800f081f (“source files could not be found”) or 0x800f0906, or if the machine is offline or governed by WSUS, you must provide an alternative local source: a matching install.wim or install.esd extracted from a Windows 10 ISO or installation media.

Obtain a clean Windows 10 ISO​

Use the Microsoft Media Creation Tool on a working PC to download the ISO, or obtain the installation media through your organization. Mount the ISO in File Explorer and note the assigned drive letter (for example E. Confirm whether the image uses install.wim or install.esd in the \sources folder.

Check WIM indexes (if install.wim present)​

If the ISO has install.wim, locate the correct image index with:
DISM /Get-WimInfo /WimFile:E:\sources\install.wim
Select the index corresponding to your edition (e.g., Windows 10 Pro, Home) and use that index in the source command.

Use install.wim as the source​

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

• Replace E: with your mounted ISO drive letter and 1 with the index number returned by /Get-WimInfo if different.
• The /LimitAccess switch prevents DISM from falling back to Windows Update, forcing it to use only the local source you provided. Use /LimitAccess when offline or in managed environments.

Use install.esd as the source​

If the ISO contains install.esd (a compressed format), use:
DISM /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\sources\install.esd:1 /LimitAccess

• Same rules apply: adjust path and index as needed. Some older DISM documentation and environments may have subtle differences, so verify with /Get-WimInfo or dir.

---

Offline repair from WinRE or servicing another volume​

When booted into Windows Recovery Environment (WinRE) or running DISM from another OS instance, use /Image: instead of /Online and point DISM at the offline Windows folder. For example:
DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:wim:\sources\install.wim:1 /LimitAccess

• Replace C: with the drive letter for the offline Windows installation (confirm with DiskPart → list volume) and D: with the mounted ISO drive. This syntax is commonly used when the system won’t boot to desktop. Microsoft documentation and Q&A confirm the /Image: workflow for offline servicing. (learn.microsoft.com)

---

After DISM: run SFC to heal the running installation​

Once DISM reports success:

• Run: sfc /scannow
• Purpose: Scans protected system files and replaces corrupted versions from the now‑healthy component store.
• If SFC reports some files could not be fixed, reboot and repeat sfc /scannow up to three times — community experience and documentation show multiple runs can progressively fix files as locked files get replaced after reboots.

---

Common errors, what they mean, and remedies​

• Error 0x800f081f — “The source files could not be found.”
  Likely cause: DISM couldn’t locate the replacement packages online (blocked by network/WSUS) or the local source does not match the installed Windows edition/build/language. Remedy: Mount a matching ISO and run RestoreHealth with /Source:wim:... or /Source:esd:... and /LimitAccess. Check that the index number is correct.
• Error 0x800f0906 — DISM fails to download files from Windows Update.
  Likely cause: connectivity problems, corporate proxy/WSUS blocking access, or missing client components. Remedy: use a mounted ISO as local source or ensure Windows Update services can reach Microsoft.
• Error 87 — “The parameter is incorrect.”
  Cause: Typo or incorrect spacing in the command. Remedy: Re‑type commands carefully; DISM parameters are case‑insensitive but spacing must be exact.
• DISM stuck at 20%, 40% or 80% — common behavior.
  Often the process is still working; restarting can interrupt legitimate repairs. If it seems truly stuck for a long time, reboot and try again. Run chkdsk C: /f /r /x to check disk health — but only after you have a backup, because CHKDSK on failing media can sometimes make matters worse. If stuck repeatedly, consider an in‑place repair install.

When DISM fails repeatedly, examine the DISM log and CBS.log for exact package or file errors. Look for lines that reference missing manifests, package names, or error codes — these pinpoint the broken component and guide the next action (local source, package install, or in‑place upgrade).

---

Practical examples and edge cases​

Example 1 — Repair while online (typical home PC)​

• Open elevated Command Prompt.
• Run: DISM /Online /Cleanup-Image /CheckHealth
• If flagged: DISM /Online /Cleanup-Image /ScanHealth
• If flagged: DISM /Online /Cleanup-Image /RestoreHealth
• After success: sfc /scannow

This flow will use Windows Update automatically for replacements if available. It’s the fastest route if the PC has a reliable internet connection.

Example 2 — No internet or corporate WSUS blocking replacements​

• Download matching Windows 10 ISO on another PC and mount it.
• Use DISM /Get-WimInfo to find the index if install.wim is present.
• Run: DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:E:\sources\install.wim:1 /LimitAccess
• Then run sfc /scannow.

Use /LimitAccess so DISM does not attempt to fall back to Windows Update, which is helpful when the machine is offline or Update paths are blocked.

Example 3 — Repair from WinRE or when OS won’t boot​

• Boot to WinRE → Troubleshoot → Advanced options → Command Prompt.
• Use DiskPart → list volume to identify the Windows volume letter.
• Mount ISO (or attach USB) if available and note its drive letter.
• Run: DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:wim:\sources\install.wim:1 /LimitAccess (adjust letters/index).
• Reboot and run sfc /scannow from normal boot. (learn.microsoft.com)

---

When DISM and SFC aren’t enough: escalation path​

DISM + SFC fixes many component store and system‑file issues, but they are not cure‑alls. They won’t repair physically failing drives, replace missing user data, or clean deeply entrenched malware. If repeated attempts fail, escalate in this order:

• Try an in‑place repair (run setup.exe from a matching mounted ISO while booted into Windows and choose to keep apps and files). This replaces system files and keeps user data and apps.
• If the in‑place repair fails, create a fresh backup of user data and perform a clean install.
• If the problem appears hardware related (SMART errors or repeated filesystem corruption), image the drive and replace it. Community experience warns that repeated attempts to repair software issues on failing disks can make recovery harder; prioritize a full backup.

---

Advanced tips and gotchas from the field​

• Always match the build and edition when supplying a local source. Using an ISO from a different build or edition is the most common cause of “source files not found” errors.
• If the ISO has install.esd instead of install.wim, you can still point DISM at it using the esd: syntax, but some older DISM builds had limitations; modern Windows 10 builds handle esd sources fine when specified correctly. Confirm with DISM /Get-WimInfo or dir E:\sources\install.* to see which file is present.
• If DISM reports it repaired components but SFC still lists unfixable files, reboot and rerun SFC. SFC may require multiple passes because some files are in use or staged for replacement at reboot.
• Use /LimitAccess only when you must prevent DISM from calling Windows Update — otherwise, letting DISM fetch replacements online can avoid the hassle of obtaining a matching ISO. However, in managed environments with WSUS, local sources are often required.
• Inspect the logs and extract error lines when requesting help; community helpers rarely need the entire log but do need the specific error lines showing failures and package names.

---

Verification and cross‑references​

This guide’s command syntax and workflow align with professional community guidance and Microsoft Q&A/learn references describing DISM’s /Online and /Image modes, the role of /Source and /LimitAccess, and the interaction between DISM and SFC. Community troubleshooting threads and technician writeups support the practical notes about stuck progress percentages, error 0x800f081f remedies via a mounted ISO, and the use of /Get-WimInfo to get WIM index numbers. Where behaviors vary slightly by Windows build, the concrete commands shown above are the current, supported forms used by administrators in the field. (learn.microsoft.com)
Caveat: Some forum reports show DISM returning unusual messages or failing on certain newer builds or recovery environments. When DISM reports it does not support a particular option (for example in Windows PE contexts), the correct approach is to switch to the offline syntax (/Image or run DISM from an elevated environment supported by the image. If you encounter rare error messages not covered above, gather the relevant log snippets and examine the specific DISM and CBS lines — they usually point to the broken package or registry area. (learn.microsoft.com)

---

Security and data safety checklist​

• Backup before making major repairs. While DISM and SFC do not delete user files, running CHKDSK or performing in‑place repairs without backups introduces risk.
• Avoid downloading ISOs from unknown sources. Use official Microsoft tools or internal corporate media to avoid compromised or modified media.
• If malware is suspected, run reputable anti‑malware scans from a known‑good environment before using DISM to repair system files; some infections intentionally corrupt the component store to hide persistence mechanisms.

---

Conclusion​

DISM and SFC remain the first line of defense to repair a damaged Windows 10 installation without reinstalling the OS. The practical workflow — CheckHealth → ScanHealth → RestoreHealth (with a local source when needed) → sfc /scannow — resolves many corruption scenarios when executed from an elevated prompt, with a matching install.wim/install.esd available for offline repairs. Keep realistic expectations: these tools repair software and component store corruption, not failing hardware or irretrievable user data.
If DISM fails with source errors, mount a matching Windows 10 ISO and use /Source:wim:... or /Source:esd:... with /LimitAccess. If the system won’t boot, use WinRE and DISM /Image: syntax after confirming drive letters. When in doubt, inspect C:\Windows\Logs\DISM\dism.log and C:\Windows\Logs\CBS\CBS.log for the package‑level details you’ll need to either provide online for help or to escalate to an in‑place repair.
This guide synthesizes official guidance and community‑tested troubleshooting approaches to give a practical, step‑by‑step path for most repair scenarios. Flag any unexpected command outputs in your logs and treat persistent failures as a cue to back up data and consider an in‑place upgrade or clean install if repair attempts do not complete successfully. (learn.microsoft.com)

---

Source: Windows Central How to use DISM command tool to repair Windows 10 image