How to Run System File Checker (SFC) on Windows
Windows quietly depends on hundreds of protected system files to keep itself running. When one of those files gets corrupted, overwritten, or goes missing, the effects range from annoying — random crashes, slow performance — to serious, like a system that won't boot properly. System File Checker (SFC) is a built-in Windows tool designed to scan for and repair exactly these problems, and knowing how to use it can save you hours of troubleshooting.
What Is System File Checker?
System File Checker is a command-line utility that has shipped with Windows since Windows 98. Its job is straightforward: it scans protected operating system files, compares them against a cached reference copy stored locally on your machine, and replaces any damaged or missing files automatically.
It doesn't require a download, subscription, or third-party software. It's already on your PC — you just need to know how to call it up.
SFC works closely with another tool called DISM (Deployment Image Servicing and Management), which repairs the Windows component store that SFC draws from. If SFC finds problems it can't fix, DISM is typically the next step.
How to Run SFC: Step by Step
Opening an Elevated Command Prompt
SFC requires administrator privileges to run. You can't execute it from a standard user prompt.
- Press the Windows key, type
cmd - Right-click Command Prompt in the results
- Select "Run as administrator"
- Click Yes if prompted by User Account Control (UAC)
Alternatively, press Windows + X and choose Windows Terminal (Admin) or Command Prompt (Admin) depending on your Windows version.
Running the Basic Scan
At the administrator prompt, type:
sfc /scannow Press Enter. The scan begins immediately. A progress indicator fills across the screen — expect it to take anywhere from 5 to 20 minutes, depending on your drive speed and system configuration.
When it finishes, you'll see one of three results:
| Result Message | What It Means |
|---|---|
| Windows Resource Protection did not find any integrity violations | No corrupted files detected — your system files are intact |
| Windows Resource Protection found corrupt files and successfully repaired them | Problems were found and fixed automatically |
| Windows Resource Protection found corrupt files but was unable to fix some of them | Problems exist that SFC couldn't resolve on its own |
Reading the Log File
SFC generates a detailed log at:
C:WindowsLogsCBSCBS.log This file contains the full scan results, including which specific files were flagged. It's dense reading, but useful if you're tracking down a specific problem or passing information to a support technician.
When SFC Can't Fix Everything: Running DISM First
If SFC returns the third result — corrupt files it couldn't repair — the issue is often that the Windows component store itself is damaged. SFC can't repair files using a broken reference library.
Running DISM before or after SFC restores the health of that component store:
DISM /Online /Cleanup-Image /RestoreHealth This command contacts Windows Update servers to download clean replacement files, so an active internet connection is required. After DISM completes (which can take longer than SFC — sometimes 20–30 minutes), run sfc /scannow again.
The typical recommended sequence when you suspect deeper corruption:
- Run DISM first to repair the component store
- Restart your PC
- Run SFC to repair individual system files using the now-healthy store
Other Useful SFC Options
SFC has a few additional flags worth knowing:
| Command | What It Does |
|---|---|
sfc /scannow | Full scan and repair of all protected files |
sfc /verifyonly | Scans without making any repairs — useful for diagnosis |
sfc /scanfile="path ofile" | Scans and repairs a single specific file |
sfc /verifyfile="path ofile" | Verifies a single file without repairing |
The /verifyonly flag is particularly handy if you want to check the state of your system without making changes yet — for example, before deciding whether to proceed with a deeper repair process.
Running SFC Offline (Advanced)
🔧 Some corruption is deep enough that SFC can't repair it while Windows is actively running. In these cases, running SFC from the Windows Recovery Environment (WinRE) is more effective.
You can access WinRE by:
- Booting from a Windows installation USB
- Using the Advanced Startup options (Settings → System → Recovery → Advanced Startup)
From the WinRE command prompt, SFC requires additional parameters to point it at the correct Windows installation and scratch directory — the syntax is more involved and depends on which drive letter Windows is assigned in recovery mode.
This approach is generally reserved for situations where the system won't boot normally or where standard SFC scans repeatedly fail.
Factors That Affect What You'll Find (and Fix)
Not every system responds to SFC the same way. Several variables shape what the tool encounters and what it can do:
- Windows version — Windows 10 and Windows 11 behave slightly differently, and the component store structures vary. SFC has been updated across versions.
- Drive type and health — SFC running on a failing HDD may misidentify hardware-related read errors as file corruption. Running a separate disk health check first helps rule this out.
- How corruption occurred — Files damaged by a sudden power loss, a bad Windows update, or malware each present differently. SFC handles some of these scenarios better than others.
- Whether Windows Update is functional — DISM depends on Windows Update to pull clean files. If your update service is broken, DISM may not complete successfully, which affects what SFC can fix downstream.
- User account setup — SFC must run as a true administrator. On some managed or enterprise systems, even administrator accounts may have restrictions that interfere.
What SFC Doesn't Cover
It's worth being clear about scope. SFC protects Windows system files — not your personal documents, application data, third-party software files, or drivers. If a problem stems from a corrupted app installation, a faulty driver, or user-level file damage, SFC won't catch or fix it.
It also won't detect malware that's replaced system files with functional-but-malicious versions, since those replacements may pass integrity checks if they're signed correctly or if the reference store itself has been compromised.
The results SFC gives you are a reliable starting point for diagnosing Windows instability — but what those results mean for your specific situation depends on what else is happening on your system at the same time.