How to Fix Corrupted System Files in Windows 10 and 11 with SFC /scannow

If your Windows PC is freezing, crashing, showing random errors, or running slower than usual, corrupted system files could be part of the problem. Windows includes built-in repair tools that can scan for damaged files and replace them when possible.

The main tool for this job is System File Checker, often referred to by its main command: SFC /scannow. In Windows 10 and Windows 11, you can also run DISM /RestoreHealth before using SFC to repair the Windows system image and give SFC a better chance of fixing corrupted files.

– You can also read this guide in Spanish: Cómo reparar archivos dañados de Windows 10 y 11 con SFC /scannow.

In this guide, you’ll learn how to fix corrupted system files in Windows 10 and Windows 11 using DISM /RestoreHealth and SFC /scannow, what the Windows Resource Protection messages mean, and what to do if SFC cannot repair all files.

Quick answer

To repair corrupted system files in Windows 10 or Windows 11, open Command Prompt as administrator and run the DISM command first: DISM.exe /Online /Cleanup-image /Restorehealth

After DISM finishes, run System File Checker: sfc /scannow

DISM repairs the Windows system image, while SFC scans protected system files and replaces corrupted files when possible.

You can use this process when Windows is crashing, freezing, showing system errors, failing to update, or acting unstable after a bad shutdown or malware cleanup.

What Is System File Checker in Windows?

System File Checker, or SFC, is a built-in Windows repair tool that checks protected system files for corruption. If it finds damaged or missing files, it tries to replace them with a correct version. Microsoft also explains this process in its official System File Checker guide.

This can help when Windows features stop working, apps crash for no clear reason, system errors appear, or your PC becomes unstable.

The most common System File Checker command is: sfc /scannow

This command scans protected Windows system files and repairs corrupted files automatically when Windows is able to do so.

How to Fix Corrupted System Files in Windows 10 and 11

Why Run DISM Before SFC?

If the Windows repair image is damaged, SFC /scannow may not be able to fix corrupted system files on its own. That is where DISM /RestoreHealth can help.

DISM repairs the Windows image that SFC may use during the repair process. That is why it is usually a good idea to run DISM /RestoreHealth first, then run SFC /scannow.

What the Windows Resource Protection Messages Mean

After running SFC /scannow, Windows will show one of several Windows Resource Protection messages. Here is what each one means and what you should do next.

– Windows Resource Protection did not find any integrity violations

This means SFC did not find any corrupted or missing protected system files. If your PC is still having problems, the issue may be caused by something else, such as a driver, a recent update, a third-party program, malware, disk errors, or a hardware problem.

– Windows Resource Protection found corrupt files and successfully repaired them

This means SFC found damaged system files and repaired them successfully. In this case, restart your computer and check if the original problem is gone.

– Windows Resource Protection found corrupt files but was unable to fix some of them

This means SFC found corrupted files, but it could not repair everything. Try this:

1. Restart your PC.
2. Run DISM /RestoreHealth again: DISM.exe /Online /Cleanup-Image /RestoreHealth
3. Run SFC /scannow again: SFC /scannow

If the message still appears, you may need to check the SFC log, run the scan in Safe Mode, use System Restore to roll Windows back to an earlier date, or try other Windows recovery options.

Advanced users can also review the CBS.log file or create an sfcdetails.txt file to see which files were affected.

– Windows Resource Protection could not perform the requested operation

This means SFC could not complete the scan. Try running SFC /scannow in Safe Mode. You can also run DISM /RestoreHealth first, then try SFC again from Command Prompt as administrator.

What to Do If SFC /scannow Is Not Working

If SFC /scannow gets stuck, fails, or cannot repair corrupted files, try these fixes.

1. Make sure Command Prompt is running as administrator

SFC needs administrator permissions to scan and repair protected system files. If you opened a normal Command Prompt window, close it and open it again by selecting Run as administrator.

2. Run DISM before SFC

If SFC cannot repair corrupted system files, run DISM /RestoreHealth first: DISM.exe /Online /Cleanup-Image /RestoreHealth

Then run SFC /scannow again: sfc /scannow

This can help when the Windows repair image needs to be fixed before SFC can replace damaged files.

3. Restart your PC and run SFC again

Sometimes Windows needs a restart to complete pending repairs. Restart your computer, open Command Prompt as administrator, and run SFC /scannow again.

4. Run SFC in Safe Mode

If you see “Windows Resource Protection could not perform the requested operation,” try running SFC /scannow in Safe Mode. Safe Mode starts Windows with fewer drivers and background services, which may help the scan complete.

In Windows 11, go to Settings > System > Recovery > Advanced startup. In Windows 10, go to Settings > Update & Security > Recovery > Advanced startup. Then restart into Troubleshoot > Advanced options > Startup Settings, choose Safe Mode, open Command Prompt as administrator, and run: SFC /scannow

5. Check your drive for errors

If system files keep getting corrupted, the problem may be related to your storage drive. In that case, you can check the drive for errors with CHKDSK.

You can also run a quick repair command from Command Prompt: chkdsk C: /f

If Windows says the drive is in use, type Y to schedule the scan for the next restart. Then restart your PC.

Final Thoughts

SFC /scannow is one of the easiest ways to check and repair corrupted system files in Windows 10 and Windows 11. For better results, run DISM /RestoreHealth first, then use System File Checker from Command Prompt as administrator.

After SFC finishes, restart your PC and check whether the problem is fixed. When SFC cannot repair everything, try running DISM and SFC again, use Safe Mode, or check the SFC log for more details.

For more serious Windows problems, you may need to use System Restore or, as a last resort, factory reset Windows.

FAQs