Windows relies on hundreds of system files to keep essential features working correctly. When these files become corrupted, modified, or accidentally damaged, you may experience crashes, error messages, missing Windows features, or unusual system behavior. Fortunately, Windows includes a built-in utility called System File Checker (SFC) that can scan protected system files and repair many common problems.
In this guide, you’ll learn how to run Windows System File Checker, what its results mean, and what to do if SFC cannot repair some files.
What Is Windows System File Checker?
System File Checker, commonly known as SFC, is a Windows command-line utility designed to check the integrity of protected operating system files.
When you run an SFC scan, Windows compares protected system files against expected versions and attempts to replace damaged files with a cached copy. This can help resolve problems caused by:
- Corrupted Windows system files
- Failed software installations
- Interrupted Windows updates
- Malware or unwanted software
- Unexpected shutdowns
- System crashes
- Incorrect system modifications
SFC is available in modern versions of Windows, including Windows 10 and Windows 11.
When Should You Run SFC?
You don’t normally need to run System File Checker on a healthy PC. However, it can be useful when Windows begins behaving unexpectedly.
Consider running SFC if you notice:
- Windows applications suddenly crashing
- Built-in Windows tools refusing to open
- Frequent system errors
- Missing or damaged Windows features
- Strange Windows interface problems
- Error messages referring to corrupted system files
- System instability after an update
- Problems that appeared after an unexpected shutdown
SFC is also a useful troubleshooting step before considering more disruptive solutions such as resetting or reinstalling Windows.
How to Run Windows System File Checker
Running SFC is straightforward, but you need to use an administrator Command Prompt or Terminal.
Step 1: Open Command Prompt as Administrator
Press Windows + S and search for:
Command Prompt
Right-click Command Prompt and select Run as administrator.
If Windows displays a User Account Control prompt, select Yes.
You can also open Windows Terminal (Admin) or PowerShell (Admin) and run the SFC command there.
Step 2: Run the SFC Scan
In the administrator command window, type:
sfc /scannowPress Enter.
Windows will begin checking protected system files.
The scan can take several minutes, depending on your computer and the condition of the Windows installation.
Step 3: Wait for the Scan to Finish
Do not close the Command Prompt or Terminal window while SFC is running.
You will see a progress indicator as Windows verifies system files. When the scan reaches 100 percent, Windows will display a message describing the result.
Understanding SFC Scan Results
The final SFC message tells you whether Windows found and repaired problems.
“Windows Resource Protection did not find any integrity violations”
This means SFC did not find corrupted protected system files.
If you’re still experiencing problems, the cause may be related to drivers, applications, hardware, settings, or another part of Windows.
“Windows Resource Protection found corrupt files and successfully repaired them”
This is generally a good result. SFC found damaged system files and successfully replaced or repaired them.
Restart your computer and check whether the original problem has been resolved.
“Windows Resource Protection found corrupt files but was unable to fix some of them”
This means SFC detected corruption but could not repair everything.
In this situation, you should normally use the Deployment Image Servicing and Management (DISM) tool and then run SFC again.
How to Use DISM Before Running SFC Again
If SFC cannot repair some files, open Command Prompt as administrator and run:
DISM /Online /Cleanup-Image /RestoreHealthPress Enter and allow the process to complete.
DISM checks and repairs the Windows component store that SFC can depend on when replacing corrupted system files.
When DISM finishes, restart the computer if requested. Then open an administrator Command Prompt again and run:
sfc /scannowRunning SFC after DISM can allow Windows to repair files that the first SFC attempt could not fix.
What If SFC Gets Stuck?
Sometimes an SFC scan may appear to stop progressing for an extended period.
First, give it some time. System scans can take longer on slower computers or systems with storage problems.
If Windows appears completely unresponsive, check whether the computer is still responding before forcing a restart.
After restarting, try running DISM first:
DISM /Online /Cleanup-Image /RestoreHealthThen run:
sfc /scannowIf the problem continues, additional Windows troubleshooting may be necessary.
How to Run SFC in Windows Recovery Environment
If Windows cannot start normally, you may need to use the Windows Recovery Environment (WinRE).
You can access recovery options through Advanced Startup or compatible Windows installation/recovery media.
Once you reach Command Prompt in the recovery environment, the Windows installation may not use the usual C: drive letter. You should identify the correct Windows partition before running an offline SFC command.
An offline scan can use a command similar to:
sfc /scannow /offbootdir=C:\ /offwindir=C:\WindowsReplace the drive letter if Windows is installed on a different partition.
Because offline recovery commands depend on the drive configuration, be careful to identify the correct Windows directory before proceeding.
Common SFC Commands
The /scannow option is the most useful command for general troubleshooting, but SFC supports other options.
Scan Without Automatically Repairing
You can verify system files using:
sfc /verifyonlyThis checks system files without attempting to repair them.
View SFC Help
To see available options, run:
sfc /?This displays the command syntax and supported parameters.
Where Does SFC Store Its Results?
SFC records information about its operations in the Windows servicing logs. When troubleshooting more complicated corruption problems, these logs can provide additional information about which files could not be repaired.
For most users, however, the final SFC message is enough to determine the next troubleshooting step.
SFC vs. DISM: What’s the Difference?
Although SFC and DISM are often used together, they have different jobs.
SFC focuses primarily on protected Windows system files.
DISM works with the Windows component store and Windows image that provide the source for system repair operations.
A common troubleshooting sequence is:
- Open Command Prompt as administrator.
- Run
DISM /Online /Cleanup-Image /RestoreHealth. - Wait for DISM to finish.
- Run
sfc /scannow. - Restart Windows.
- Test whether the original problem has disappeared.
This approach is particularly useful when SFC reports that it could not repair some corrupted files.
Tips Before Running System File Checker
SFC is generally safe to use, but a few precautions can make troubleshooting easier.
Save your work first. Although SFC is designed to repair Windows files, it’s good practice to save open documents before performing system maintenance.
Use an administrator account. SFC needs elevated permissions to access and repair protected system files.
Don’t interrupt the scan unnecessarily. Allow the process to finish whenever possible.
Keep Windows updated. If system corruption is related to an older Windows component or update, installing available updates may help.
Back up important data. SFC repairs system files; it is not a data recovery tool and should not be considered a substitute for regular backups.
Can SFC Fix Every Windows Problem?
No. SFC is specifically designed to address protected Windows system-file corruption. It cannot fix every possible cause of Windows problems.
For example, SFC generally won’t solve issues caused by:
- Failing RAM
- A damaged SSD or hard drive
- Faulty hardware
- Incompatible third-party drivers
- Incorrect BIOS settings
- Some malware infections
- Problems with individual third-party applications
- Network configuration issues
If SFC reports that Windows system files are healthy, you may need to investigate other causes.
Final Thoughts
Knowing how to run Windows System File Checker gives you a convenient way to troubleshoot corrupted or damaged Windows system files without immediately reinstalling the operating system.
For most situations, the process is as simple as opening an administrator Command Prompt and running:
sfc /scannowIf SFC finds and repairs corrupted files, restart your PC and check whether the problem has been resolved. If it cannot repair everything, use DISM to repair the Windows component store and then run SFC again.
SFC won’t fix every Windows problem, but it is one of the most useful built-in tools to try when you suspect that damaged system files are causing Windows instability.
