SFC Scan in Windows: Step-by-Step Guide

The System File Checker (SFC) is a built-in Windows utility that scans for corrupted or missing system files and repairs them by replacing them with healthy versions from the Windows component store. It’s the first line of defense when you see errors like “Windows Resource Protection could not perform the requested operation,” or when your PC behaves erratically due to system file damage. This guide walks you through running sfc /scannow correctly, what to do if it finds problems, and how to fix common issues.

What You’ll Need

A Windows PC (Windows 10, 11, 8, or 7)
Administrator account access
Internet connection (only if you need to run DISM, which downloads healthy files)
Patience – a full scan can take 15-30 minutes

Step-by-Step

Close all running applications. SFC works best when the system is idle. Save your work and close anything you don’t need.
Open Command Prompt as Administrator. Click the Start button, type cmd, right-click on “Command Prompt” and select “Run as administrator.” If prompted by User Account Control, click “Yes.”
Run the scan. In the black command prompt window, type sfc /scannow and press Enter. The scan will begin. It may take a while – let it run without closing the window.
Wait for the result. When it finishes, you’ll see one of three messages:
- “Windows Resource Protection did not find any integrity violations” – no issues found.
- “Windows Resource Protection found corrupt files and successfully repaired them” – the fix worked.
- “Windows Resource Protection found corrupt files but was unable to fix some of them” – you’ll need to take extra steps (see Troubleshooting below).
Restart your PC. Even if no issues were found, a reboot helps apply any changes.
Check the log (optional). If you want details, open the CBS log: %windir%\Logs\CBS\CBS.log. Look for entries with “Cannot repair” to see which files were problematic.

Common Mistakes

Running SFC without admin rights. If you open Command Prompt normally (not as administrator), SFC will fail with “You must be an administrator running a console session in order to use the sfc utility.” Always right-click and “Run as administrator.”
Interrupting the scan. Closing the window or restarting mid-scan can leave the system in an inconsistent state. Let it finish.
Running SFC while Windows Update is running. Both processes modify system files; they can conflict. Wait for updates to finish.
Assuming SFC fixes everything. SFC only repairs system files, not user files, drivers, or registry issues. It’s not a general PC cleaner.

Tips

Run DISM first if SFC fails. If SFC can’t repair files, the component store (the source of healthy files) may be corrupted. Run DISM /Online /Cleanup-Image /RestoreHealth first, then run SFC again.
Use offline scan if Windows won’t boot. If your PC won’t start, boot into Advanced Startup (Shift + Restart) and choose Troubleshoot > Advanced Options > Command Prompt. Then run sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows (adjust drive letters if needed).
Scan specific files. If you know which file is corrupted, you can scan just that file: sfc /scanfile=C:\Windows\System32\some.dll.
Run in Safe Mode. If SFC is interrupted by a driver or service, boot into Safe Mode and run it there.
Be patient. The scan can take 15-30 minutes on a typical system. Don’t assume it’s frozen; watch the progress percentage.

Troubleshooting

“Windows Resource Protection could not perform the requested operation” – This usually means the scan was interrupted or you don’t have admin rights. Close any third-party antivirus, make sure you’re running as admin, and try again. If it persists, reboot and try in Safe Mode.

“found corrupt files but was unable to fix some of them” – This means SFC found problems but couldn’t fix them. First, run DISM as described in Tips. If DISM fails, try the offline scan. If it still fails, you may need to do a repair install (in-place upgrade) of Windows.

SFC gets stuck at a certain percentage – Wait at least 15 minutes before assuming it’s stuck. If it’s truly stuck, close the window, reboot, and try again in Safe Mode.

SFC finds errors every time you run it – This could indicate a failing hard drive or a corrupted component store. Run chkdsk /f to check the disk, and run DISM to repair the store.

“Windows Resource Protection could not start the repair service” – The Windows Modules Installer service may be disabled. Open Services (services.msc), find “Windows Modules Installer,” set its startup type to “Manual,” and start it. Then try SFC again.

Frequently Asked Questions

Q: How often should I run sfc /scannow?
A: Only when you suspect system file corruption. Running it regularly isn’t harmful, but it’s unnecessary. If you’re troubleshooting, run it once, fix issues, and move on.

Q: Can I use my PC while SFC is running?
A: Yes, but it’s not recommended. The scan uses system resources, and running other programs might interfere with the repair process. It’s best to let it run undisturbed.

Q: Does SFC work on Windows 11?
A: Yes, SFC is available in all modern versions of Windows, including Windows 11. The steps are identical.

Q: What’s the difference between SFC and DISM?
A: SFC scans and repairs system files. DISM repairs the component store (the source of healthy files) and the system image. If SFC can’t fix something, run DISM first, then SFC again.

Q: Will SFC delete my personal files?
A: No. SFC only touches Windows system files. Your documents, photos, and other personal data are completely safe.

Q: How long does a full scan take?
A: Typically 15-30 minutes, but it can be longer on older or heavily used systems. The progress bar shows the percentage, but it may stall briefly at certain points.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →