System File Checker: 6 Proven Steps to Repair Windows

Written by: Kymakers Support Team · Reviewed by: Kymakers Technical Team Last updated: July 2026 · Applies to: Windows 10, Windows 11, Windows Server 2016–2025 Difficulty: Intermediate · Estimated time: 20–60 minutes

The System File Checker (SFC) scans Windows for corrupted or missing system files and repairs them from a local cache. Run it from an elevated Command Prompt with sfc /scannow. If it reports corruption it can’t fix, that cache itself is damaged — and that’s when you run DISM to repair the cache, then run SFC again.

That order matters, and it’s the part most guides get wrong. This guide covers six proven steps for using the System File Checker and DISM together, what each command actually does, and what to do when both come back clean but the problem persists.

The rule that makes these tools work

SFC repairs Windows files. DISM repairs the source SFC repairs from. If SFC fails, running it again won’t help — you need DISM first to fix the component store, then SFC can do its job. Running them in the wrong order is why people conclude “these tools don’t work.”

Table of Contents

1. Step 1: Run the System File Checker
2. Step 2: Read what SFC tells you
3. Step 3: Repair the component store with DISM
4. Step 4: Run SFC again
5. Step 5: Use an offline source when DISM can’t download
6. Step 6: When both come back clean but problems remain
7. Running SFC when Windows won’t boot
8. FAQ

Step 1: Run the System File Checker

Start here. The System File Checker needs administrator rights, or it will refuse to run.

1. Click Start, type cmd, right-click Command Prompt, and choose Run as administrator.
2. Type the command and press Enter:

sfc /scannow

3. Let it run to 100% — it typically takes 5 to 15 minutes. Don’t close the window or restart partway through.

The System File Checker compares every protected Windows file against a known-good copy stored in the component store (WinSxS), and replaces anything that doesn’t match.

Step 2: Read What SFC Tells You

The System File Checker gives one of four results, and each means something different:

• “Windows Resource Protection did not find any integrity violations” — no corruption found. Your problem is elsewhere.
• “Windows Resource Protection found corrupt files and successfully repaired them” — fixed. Reboot and test.
• “Windows Resource Protection found corrupt files but was unable to fix some of them” — the component store is damaged. Go to Step 3.
• “Windows Resource Protection could not perform the requested operation” — run it in Safe Mode, or from recovery.

Details are logged to C:\Windows\Logs\CBS\CBS.log if you want specifics on what was repaired.

Step 3: Repair the Component Store With DISM

When the System File Checker can’t fix everything, DISM repairs the source it repairs from. In the same admin Command Prompt:

DISM /Online /Cleanup-Image /RestoreHealth

This connects to Windows Update, downloads clean replacement files, and repairs the component store. It usually takes 10 to 30 minutes and may appear stuck around 20% — that’s normal, let it finish.

Two optional commands before it, useful for diagnosis:

DISM /Online /Cleanup-Image /CheckHealth     (quick check for flagged corruption)
DISM /Online /Cleanup-Image /ScanHealth      (fuller scan, no repair)

/RestoreHealth is the one that actually repairs, so if you only run one, run that.

Step 4: Run SFC Again

This step gets skipped constantly, and skipping it wastes the whole exercise. Once DISM has repaired the component store, the System File Checker finally has a clean source to work from:

sfc /scannow

Run it again after DISM completes. This time it can usually replace the files it couldn’t fix before. Reboot afterwards and test whether your original problem is gone.

The full sequence is: SFC → DISM → SFC → reboot.

Step 5: Use an Offline Source When DISM Can’t Download

If the PC has no internet, is on a restricted network, or DISM fails with an error like 0x800f081f, point it at a local source instead.

1. Download or mount a Windows ISO matching your exact version and build.
2. Note the drive letter of the mounted ISO (say D:).
3. Run:

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

/LimitAccess tells DISM not to attempt Windows Update. The ISO must match your installed version — a Windows 11 24H2 ISO won’t repair a 25H2 install.

Step 6: When Both Come Back Clean but Problems Remain

Sometimes the System File Checker and DISM both report success, and the problem is still there. That means the fault isn’t corrupted system files.

At that point, consider:

• A bad update — uninstall the most recent quality update and test.
• Driver conflicts — especially display and storage drivers after a crash or BSOD.
• Failing hardware — a dying drive causes symptoms that look like corruption. Our guide on checking hard drive health covers how to rule it out.
• In-place repair — reinstall Windows over itself from an ISO, keeping files and apps. This replaces system components wholesale when targeted repairs can’t.

Don’t keep re-running SFC hoping for a different answer. If two clean passes say the files are fine, believe them and look elsewhere.

Running SFC When Windows Won’t Boot

If Windows won’t start, you can still run the System File Checker from the recovery environment — but the syntax changes, because there’s no running Windows to scan.

1. Interrupt the boot twice; the third start enters WinRE automatically.
2. Go to Troubleshoot → Advanced options → Command Prompt.
3. Identify your Windows drive letter (it’s often D: in recovery, not C:) using diskpart → list volume → exit.
4. Run:

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

Adjust the letter to match. For DISM offline, use /Image:D:\ instead of /Online. If the PC won’t reach recovery at all, our guide on no operating system installed covers booting from installation media.

FAQ About System File Checker and DISM

What does the System File Checker do? It scans all protected Windows system files, compares them against known-good copies in the component store, and replaces any that are corrupted or missing. Run it with sfc /scannow as administrator.

Should I run SFC or DISM first? Run SFC first. If it reports files it couldn’t repair, run DISM /Online /Cleanup-Image /RestoreHealth to fix the component store, then run SFC again. The correct sequence is SFC → DISM → SFC.

What does dism /online /cleanup-image /restorehealth actually do? It repairs the Windows component store (WinSxS) by downloading clean replacement files from Windows Update. That store is the source SFC uses, so repairing it lets SFC succeed on files it previously couldn’t fix.

How long do SFC and DISM take? SFC typically takes 5–15 minutes. DISM usually takes 10–30 minutes and often appears stuck near 20% — that’s normal. Don’t interrupt either one.

SFC says it can’t repair some files — what now? That means the component store is damaged. Run DISM /RestoreHealth, then run SFC again. If DISM can’t reach Windows Update, use an offline ISO source with /Source and /LimitAccess.

Can I run the System File Checker if Windows won’t boot? Yes, from the recovery environment, using the offline syntax: sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows, adjusting for your actual Windows drive letter.

The System File Checker and DISM repair a genuinely broken Windows install without costing anything. But if corruption is severe enough that even an in-place repair fails, a clean reinstall is the remaining option — and that needs a valid licence to reactivate. Kymakers supplies genuine Windows 11 Pro and Windows 10 Pro keys with instant delivery and activation support, plus Windows Server 2025 licences for server repairs.

Run SFC. If it fails, run DISM. Then run SFC again. That order is the whole trick.

Official reference: Use the System File Checker tool — Microsoft Support