What a System File Checker does and when to run it
A System File Checker is a built-in Windows tool that scans your computer for corrupted or missing system files and repairs them automatically. Windows relies on thousands of these files to run — if one gets damaged by a crash, malware, or a failed update, your computer may freeze, run slowly, or refuse to start. Running the System File Checker can fix these problems without reinstalling Windows.
You should run it if your computer has started crashing without warning, if programs freeze frequently, or if Windows itself won't start properly. It is also worth running after a major update fails or if you suspect malware has damaged system files. The scan takes 15 to 60 minutes depending on your drive size, and you will need administrator access to your account.
Key Takeaways
- The System File Checker tool is called sfc /scannow and runs from the Command Prompt with administrator rights.
- You must open Command Prompt as administrator — right-clicking and selecting "Run as administrator" is the required step.
- The scan runs in the background and will tell you whether it found and fixed problems, or found problems it could not fix.
- If the tool finds unfixable corruption, you may need to run the Deployment Image Servicing and Management tool (DISM) first to restore system files from Windows Update.
Opening Command Prompt with administrator rights
The System File Checker only works when you run it as an administrator. On Windows 10 or 11, click the Start button and type "Command Prompt" into the search box. You will see "Command Prompt" appear in the results — do not click it directly. Instead, right-click on "Command Prompt" and select "Run as administrator" from the menu that appears.
Windows will ask "Do you want to allow this app to make changes to your device?" Click "Yes" to proceed. A black window will open with white text. This is the Command Prompt, and you are now running it with the permissions needed to repair system files. If you are on Windows 11, you may see "Windows Terminal" instead of "Command Prompt" — either one works the same way.
Running the System File Checker scan
In the Command Prompt window, type exactly this: sfc /scannow and then press Enter. The tool will begin scanning when ready. You will see a progress bar that says "Scanning system files" with a percentage. Do not close this window or restart your computer while the scan is running — interrupting it can cause problems.
The scan usually takes 15 to 60 minutes. While it runs, you can use your computer normally, though it may run slower than usual. When the scan finishes, the Command Prompt will display one of three messages: "Windows Resource Protection did not find any integrity violations," meaning no problems were found; "Windows Resource Protection found corrupt files and successfully repaired them," meaning the tool fixed the issue; or "Windows Resource Protection found corrupt files but was unable to fix some of them," meaning you will need to take additional steps.
What to do if the scan finds unfixable corruption
If the System File Checker reports that it found problems but could not fix them, the next step is to run the DISM tool (Deployment Image Servicing and Management). This tool restores damaged system files from Windows Update before the System File Checker tries again. Open Command Prompt as administrator again and type: DISM /Online /Cleanup-Image /RestoreHealth and press Enter.
This scan also takes 15 to 60 minutes. When it finishes, restart your computer, then open Command Prompt as administrator once more and run the System File Checker again with sfc /scannow. This second run often succeeds because DISM has restored the missing files. If the System File Checker still reports unfixable corruption after this, the damage may be too severe for these tools to repair, and you may need to consider a Windows repair or reinstall.
Restarting after the scan completes
If the System File Checker repaired files, restart your computer to explore the changes. Close the Command Prompt window and click the Start button, then select "Restart." Your computer will shut down and start again, which may take a few minutes longer than usual as Windows applies the repairs.
After the restart, your computer should run more smoothly if the corrupted files were causing the slowdown or crashes. If you are still experiencing the same problems, the issue may not be related to system file corruption — it could be a hardware problem, a failing drive, or malware that the System File Checker cannot address.
Scheduling regular scans to catch problems early
You do not need to run the System File Checker constantly, but running it once every few months can catch corruption before it causes noticeable problems. You can also run it after any major Windows update, after your computer crashes unexpectedly, or if you notice new freezing or slowness.
There is no harm in running the scan more often — it will straightforward report that no problems were found and take up some of your computer's time. If you find yourself running it frequently because problems keep returning, that is a sign that something else is wrong, such as a failing hard drive or a persistent malware infection that antivirus software has not caught.
Frequently Asked Questions
Can I use my computer while the System File Checker is running?
Yes, you can use your computer normally while the scan runs in the background. The scan may slow things down slightly, but you can open programs, browse the web, or work on documents. Do not restart or shut down your computer while the scan is active, as this will interrupt the repair process.
What does "Windows Resource Protection" mean in the scan results?
Windows Resource Protection is the system that monitors and protects critical system files. When the System File Checker reports what it found, it is reporting on behalf of Windows Resource Protection. The message tells you whether any protected files were corrupted and whether the tool was able to fix them.
Do I need to run DISM before the System File Checker?
No. Run the System File Checker first. Only run DISM if the System File Checker reports that it found problems but could not fix them. Running DISM first is unnecessary and takes extra time if the System File Checker can solve the problem on its own.
Will the System File Checker remove my files or programs?
No. The System File Checker only repairs or replaces corrupted Windows system files. It does not touch your documents, photos, programs, or personal files. It cannot cause data loss.
What if the Command Prompt closes before the scan finishes?
If the window closes unexpectedly, the scan was interrupted and may not have completed. Open Command Prompt as administrator again and run sfc /scannow once more from the beginning. The tool will pick up where it left off or restart the scan depending on how far it had progressed.