How to Run System File Checker: Step by Step Windows Repair Guide

Windows acting up with crashes or errors? I’ve fixed dozens of machines using this built-in tool. It’s the first thing I run when something feels off.

The process is shockingly simple—just a single command in Command Prompt. No special software, no downloads, and it takes under 15 minutes to scan and repair corrupted system files.

You’ll get a detailed report of any issues found and fixed, often resolving elusive problems that slow down your PC. I’ve seen it revive systems that were seemingly beyond repair.

Works on Windows 10 and 11, and requires only admin access. Here’s how to do it right.

What Youll Need

Instructions

Here’s the procedure I follow to repair Windows without breaking a sweat.

Press the Windows key and type cmd. Right-click Command Prompt and select Run as administrator. You’ll see a User Account Control prompt—click Yes to proceed. This elevated access is required for the tool to function properly.

If you don’t see the option to run as administrator, your account might not have the necessary privileges. In that case, you’ll need to log in with an administrator account or have one created for you.

In the Command Prompt window, type sfc /scannow and press Enter. The scan will begin immediately. Don’t close the window or interrupt the process—it can take 10-30 minutes depending on your system’s speed and health.

You’ll see progress updates in the window. The tool checks every protected system file and replaces corrupted ones with cached copies. If it finds no issues, you’ll see the message “Windows Resource Protection did not find any integrity violations.”

After completion, you’ll see one of three messages. “Windows Resource Protection found corrupt files and successfully repaired them” means the tool fixed issues automatically. “Windows Resource Protection found corrupt files but was unable to fix some of them” indicates you’ll need to run additional commands.

For the latter case, I always run DISM /Online /Cleanup-Image /RestoreHealth first, then repeat the sfc /scannow command. This combination resolves nearly all system file corruption cases.

Regardless of the scan outcome, restart your PC. This ensures any repaired files are properly loaded into memory. Some changes won’t take effect until after a reboot, and you might notice improved system stability immediately.

If you still experience issues after the restart, consider running the scan again. Some deeply embedded corruptions may require multiple passes to fully resolve, especially if they’re actively in use by the system.

For advanced troubleshooting, examine the detailed log. The System File Checker creates a log file at %windir%\Logs\CBS\CBS.log. You can open it in Notepad, though it’s quite technical. Look for entries containing [SR] which indicate scan results.

If you’re not comfortable reading the log, Windows also creates a summary at %windir%\Logs\CBS\CBS.log with the most critical information. This can help identify which specific files were problematic if the automatic repair wasn’t completely successful.

Tips and Common Mistakes

These practical insights will help you avoid common pitfalls when running the System File Checker.

Administrator Access is Non-Negotiable: In Step 1, if you skip the “Run as administrator” option, the scan won’t have the permissions needed to repair protected system files. I learned this the hard way when my first attempt failed to fix a critical corruption because I forgot this step.

Patience During the Scan: The 10-30 minute scan time in Step 2 isn’t arbitrary—it reflects how long it takes to verify every protected system file. Don’t close the Command Prompt window or interrupt the process, even if it seems stuck. The progress percentage will update sporadically, not continuously.

When Automatic Repair Fails: In Step 3, if you see the message about unable to fix some files, don’t panic. Running the DISM command first, as I always do, then repeating sfc /scannow solves most cases. This two-step approach is what separates successful repairs from frustrating dead ends.

Restart is Required: Step 4 isn’t optional. Some repaired files won’t properly load into memory until you restart your PC. I’ve seen cases where users skipped this and wondered why their system still had issues—always restart, even if the scan found no problems.

Frequently Asked Questions

Running the System File Checker is a simple yet powerful way to repair corrupted Windows files. 💡 With just a few commands, you can restore stability and performance to your system. Now that you know how, try running it regularly to keep your PC in top shape!