What System File Checker Does and When to Use It

System File Checker (SFC) is a Windows tool that scans your computer for corrupted system files and replaces them with working copies. If Windows is crashing, freezing, or showing error messages about missing files, running SFC often fixes the problem without reinstalling Windows.

You should run SFC when you notice Windows behaving oddly — programs won't start, you see "file not found" errors, or the system is unstable. SFC works by comparing every protected system file against a stored copy and replacing damaged ones automatically. The scan takes 15 to 60 minutes depending on your drive speed and how many files need checking.

SFC requires administrator access and works best when Windows can still start normally. If Windows won't boot at all, you have a different problem that SFC cannot solve from within Windows itself.

Key Takeaways

  • System File Checker runs from Command Prompt with administrator rights, which you must open through the Start menu or Settings.
  • The command you type is sfc /scannow, which scans all protected files and repairs damage automatically.
  • The scan takes 15 to 60 minutes and should run while you are not using the computer heavily.
  • If SFC finds and repairs problems, restart your computer and check whether the original issue is resolved.
  • If SFC cannot repair a file, you may need to run it again in Safe Mode or use the DISM tool as a follow-up step.

Opening Command Prompt as Administrator

System File Checker only works when you run it as an administrator. The steps differ slightly between Windows 10 and Windows 11, but both are straightforward.

On Windows 10: Click the Start button, type cmd into the search box, right-click "Command Prompt" in the results, and select "Run as administrator." Windows will ask for permission — click "Yes" to proceed.

On Windows 11: Click the Start button, type cmd into the search box, and you will see "Command Prompt" appear. Click the option that says "Run as administrator" on the right side of the result. Confirm the permission prompt.

You will know Command Prompt opened correctly when you see a black window with white text and the prompt ends with C:\Windows\system32>. If the window closes immediately or you do not see "Administrator" in the title bar, you did not open it with the right permissions — close it and try again.

Running the System File Checker Scan

Once Command Prompt is open as administrator, type the scan command exactly as shown: sfc /scannow and press Enter. Do not add extra spaces or change the spelling.

The scan will start immediately. You will see a progress bar that says "Scanning system files" and shows a percentage. The window will display messages as it works — this is normal. Do not close Command Prompt while the scan is running, even if it appears to be stuck. Scans can take 15 to 60 minutes depending on your computer's speed and drive type.

When the scan finishes, you will see one of three messages at the bottom of the window. Read which one appears, because it tells you what happened next.

Understanding the Scan Results

After the scan completes, Command Prompt will display a result message. The three most common outcomes are:

"Windows Resource Protection did not find any integrity violations." This means all your system files are healthy and SFC found nothing to repair. Close Command Prompt and check whether your original problem is resolved. If the issue persists, the problem is not a corrupted system file — it may be a driver, malware, or hardware issue.

"Windows Resource Protection found corrupt files and successfully repaired them." This is the best outcome. SFC found damage and fixed it automatically. Restart your computer and test whether the original problem is gone. Most issues resolve after this repair and restart.

"Windows Resource Protection found corrupt files but was unable to fix some of them." This means SFC identified damage but could not repair it automatically. Note any file names shown in the results. Restart your computer, then run SFC again in Safe Mode (see the next section). If the problem persists after that, you may need to use the DISM tool or contact support with the file names SFC reported.

Running System File Checker in Safe Mode

If SFC reported that it could not repair some files, running it again in Safe Mode sometimes succeeds because fewer programs are running and fewer files are in use. Safe Mode is a Windows startup option that loads only essential drivers and services.

On Windows 10: Click Start, then Settings. Go to Update & Security, then Recovery. Under "Advanced startup," click "Restart now." Your computer will restart into a menu. Select "Troubleshoot," then "Advanced options," then "Startup Settings." Click "Restart" and when the menu appears, press 4 or F4 to start Safe Mode.

On Windows 11: Click Start, then Settings. Go to System, then Recovery. Click "Restart now" under "Advanced startup." When the menu appears, select "Troubleshoot," then "Advanced options," then "Startup Settings." Click "Restart" and press 4 or F4 for Safe Mode.

Once Safe Mode starts, open Command Prompt as administrator again (right-click the Start button and select "Terminal (Admin)" or search for Command Prompt and run as administrator). Type sfc /scannow and let it run to completion. When finished, restart your computer normally and test whether the issue is resolved.

What to Do If System File Checker Cannot Fix the Problem

If SFC runs successfully but your original problem persists, or if SFC cannot repair certain files even in Safe Mode, the issue may not be a corrupted system file. At this point, consider whether the problem started after installing new software, a Windows update, or a driver update — rolling back the recent change sometimes solves it.

You can also try the DISM tool, which is a more advanced repair tool that can sometimes fix issues SFC cannot. Open Command Prompt as administrator and type DISM /Online /Cleanup-Image /RestoreHealth. This scan takes longer than SFC but may repair deeper system issues. Run it once and let it complete fully.

If both SFC and DISM report success but your problem remains, the issue is likely not a system file — it could be a hardware failure, a driver problem, malware, or a third-party software conflict. At that point, document what you have tried and consider contacting Microsoft support or a local technician with the specific error messages you are seeing.

Frequently Asked Questions

Can I use my computer while System File Checker is running?

You can use your computer, but the scan will run slower and may be less thorough. It is best to let SFC run uninterrupted — start it when you can step away for an hour. Do not restart your computer or shut it down while the scan is active.

Why does System File Checker say it cannot repair files?

Files in use by Windows cannot be repaired while Windows is running. Running SFC in Safe Mode removes most programs from memory, allowing SFC to access and repair more files. If Safe Mode still does not work, the file may be damaged beyond repair and require a Windows reinstall.

Do I need to pay for System File Checker?

No. System File Checker is built into Windows and costs nothing. If a website or pop-up offers to run SFC for you or charges money for it, that is a scam — close it and run SFC yourself through Command Prompt.

Will System File Checker delete my files or programs?

No. SFC only repairs or replaces corrupted system files that Windows needs to run. It does not touch your documents, photos, or installed programs. Your personal files are completely safe.

How often should I run System File Checker?

Run it only when you notice a problem — there is no benefit to running it regularly on a healthy system. If you run it and it finds no issues, you do not need to run it again unless Windows starts behaving oddly.