How to Run System File Checker on Windows
Windows quietly manages thousands of system files that keep your computer running. Over time, those files can become corrupted, go missing, or get overwritten by poorly behaved software. System File Checker (SFC) is a built-in Windows tool that scans for exactly this kind of damage — and repairs it automatically when it can.
Here's how it works, how to run it, and what shapes whether it actually solves your problem.
What Is System File Checker?
System File Checker is a command-line utility built into every modern version of Windows (Windows 7 through Windows 11). It compares your current system files against a protected cache of known-good versions stored locally on your machine.
When it finds a mismatch — a corrupted file, a missing file, or one that's been quietly replaced — it attempts to restore the correct version from that cache. You don't need to download anything or buy third-party software. It's already on your system.
SFC is commonly used when Windows is behaving strangely: apps crashing unexpectedly, error messages referencing missing DLLs, blue screens, or general instability that doesn't trace back to a specific program.
How to Run SFC: Step-by-Step 🛠️
Running System File Checker requires administrator privileges. The process is the same across Windows 10 and Windows 11, with minor visual differences.
Step 1: Open Command Prompt as Administrator
- Press Windows + S and type
cmd - Right-click Command Prompt in the results
- Select Run as administrator
- Click Yes if prompted by User Account Control
Alternatively, right-click the Start button and select Windows Terminal (Admin) or Command Prompt (Admin) depending on your Windows version.
Step 2: Run the SFC Command
Type the following and press Enter:
sfc /scannow The scan begins immediately. A progress bar will appear in the terminal window. Depending on your system, this can take anywhere from a few minutes to around 20 minutes. Do not close the window while it's running.
Step 3: Read the Result
When the scan completes, you'll see one of three messages:
| Result Message | What It Means |
|---|---|
| Windows Resource Protection did not find any integrity violations | No corrupt files found — your system files are clean |
| Windows Resource Protection found corrupt files and successfully repaired them | Damage detected and fixed automatically |
| Windows Resource Protection found corrupt files but was unable to repair some of them | Corruption exists but SFC couldn't fix it on its own |
What to Do If SFC Can't Repair the Files
This is where things get more nuanced. If SFC reports files it couldn't fix, the repair cache itself may be damaged — meaning SFC has nothing healthy to copy from.
The standard next step is running DISM (Deployment Image Servicing and Management) first, then running SFC again afterward. DISM pulls fresh file versions from Windows Update servers to restore the repair cache.
Run these commands in order, each followed by Enter, and wait for each to complete before running the next:
DISM /Online /Cleanup-Image /CheckHealth DISM /Online /Cleanup-Image /ScanHealth DISM /Online /Cleanup-Image /RestoreHealth After DISM finishes, run sfc /scannow again. With a restored cache, SFC often succeeds on the second attempt.
Factors That Affect SFC Results
Not every SFC scan plays out the same way, and a few variables significantly shape what happens:
Operating system version and update status DISM relies on Windows Update to pull healthy replacement files. If your system is significantly out of date, or if Windows Update itself isn't functioning correctly, DISM may fail to restore the cache — which limits what SFC can repair.
How the corruption happened File corruption from a sudden power loss or failed update behaves differently than damage caused by malware. SFC handles the former reasonably well. Malware that actively overwrites system files, or that has modified protected areas, may require additional steps beyond SFC.
Whether Windows can even boot If your system is too unstable to reach the desktop, you can run SFC from Windows Recovery Environment (WinRE) — but the command syntax changes slightly, and you'll need to specify the Windows drive letter manually. This is a more advanced process than running SFC from a working desktop.
Drive health SFC works on the software layer, not the hardware. If the underlying drive has failing sectors, SFC may report files as repairable and "fix" them — only for corruption to reappear. Running a drive health check (via chkdsk or your drive manufacturer's diagnostic tool) alongside SFC gives you a more complete picture.
Account permissions 🔐 SFC will silently fail or report incomplete results if not run as a true administrator. A standard user account with administrator privileges isn't always sufficient on all configurations — the elevated Command Prompt method above ensures proper access.
Where SFC Logs Its Findings
SFC generates a detailed log file at:
C:WindowsLogsCBSCBS.log This file records every file it checked, what it found, and what it did (or couldn't do). If you're troubleshooting a persistent issue or passing information to someone helping you remotely, this log is the most complete record of what SFC actually did.
SFC vs. Other Repair Options
SFC is a targeted tool — it handles Windows system files specifically. It doesn't scan installed applications, drivers, or the Windows Registry. Problems caused by corrupted third-party software, outdated drivers, or registry issues sit outside what SFC can address.
For broader Windows health issues, SFC is typically the right first step. What happens after depends on what the scan finds — and what else is going on with your particular system.