SFC /scannow Not Working Windows 11? Here’s What to Do

System File Checker, or SFC /scannow, is one of Windows 11’s most reliable tools for fixing corrupt or missing system files. If your PC is acting strangely—like apps crashing, slow performance, or random errors—this command can often solve the issue quickly. But sometimes, SFC doesn’t work as expected. You might see an error message, or it might fail partway through the scan. If you’re searching for answers about “sfc /scannow not working Windows 11,” you’re not alone—and there are ways to fix it.

In this guide, we’ll walk you through the most effective solutions when SFC /scannow fails to run or finish properly. We’ll cover the most common error messages and what they mean, explain how to run SFC in Safe Mode or during boot, and show how to use DISM to repair the system image before trying again. You’ll also learn when to use CHKDSK instead—and we’ll link to our full guide on CHKDSK, SFC, and DISM so you can better understand how these tools work together.

Part 1. Common SFC Errors and What They Mean

Before jumping into the fixes, it’s important to understand the exact error messages SFC /scannow might show. Each message gives a clue about what’s going wrong—whether it’s a permission issue, system damage, or something deeper. Let’s look at the two most common SFC errors and what they actually mean:

1. “Windows Resource Protection could not perform the requested operation”

This error usually shows up when SFC doesn’t have the proper permissions to access protected parts of the system. It can also happen if the Volume Shadow Copy service, which helps with file backups and system scans, isn’t working correctly. Because of these limitations, running SFC inside normal Windows mode sometimes fails. The best way to get around this problem is to run the scan from Safe Mode or during boot, where fewer background services can interfere with the process.

2. “Windows Resource Protection found corrupt files but was unable to fix some of them”

This message means that SFC was able to scan your system and locate the damaged files, but it couldn’t repair everything. That’s often because the internal system image Windows uses as a repair source is itself corrupted or incomplete. When this happens, you’ll need to use a more advanced tool called DISM, which can fix the system image directly. Once that’s done, you can run the SFC scan again, and it should now be able to complete the repairs properly.

Part 2. Run SFC in Safe Mode or From Boot

When sfc /scannow not working Windows 11 in normal mode, running it in Safe Mode often solves the problem. Safe Mode loads Windows with only the most essential drivers and services, which reduces conflicts and locked files.

How to Boot into Safe Mode:

1. Press Windows + I to open Settings.
   
2. Go to System > Recovery.
   
3. Under Advanced startup, click Restart now.
   
4. After reboot, select Troubleshoot > Advanced options > Startup Settings > Restart.

5. Press 4 or F4 to boot into Safe Mode.
6. Once in Safe Mode, open Command Prompt as an administrator and type: sfc /scannow
7. Press Enter and let the scan complete.

How to Run SFC from Advanced Startup:

1. Hold Shift and click Restart from the Start Menu power options.
   
2. Select Troubleshoot > Advanced options > Command Prompt.
   

       In the Command Prompt window, enter: sfc /scannow

3. Let the scan complete and follow any on-screen instructions.
   

Tip: This method bypasses file locking and is great for more persistent errors.

👉 Back to Parent Post: How to Fix Disk Errors on Windows 11

Part 3. Use DISM to Repair the System Image

If SFC is still not working, the system image it relies on might be corrupted. That’s where DISM (Deployment Imaging Service and Management Tool) comes in. DISM repairs the Windows image that SFC uses to fix files.

Steps to Run DISM:

1. Open Command Prompt as Administrator.
   

Enter the following command: dism /online /cleanup-image /restorehealth

2. Press Enter. This command might take 10–20 minutes to complete.
   
3. Ensure your computer is connected to the internet, as DISM may need to download fresh system files.

After it finishes, rerun: sfc /scannow

This two-step combo often solves even deep-rooted system file issues.

Part 4. Use CHKDSK to Rule Out Drive Issues

Sometimes, SFC fails not because of system files, but because of hard drive problems. If your disk has bad sectors or file system corruption, it can block repair operations.

Run CHKDSK to Check the Disk:

1. Open Command Prompt as Administrator.
   

Type this command and press Enter: chkdsk C: /f /r

2. If prompted to schedule on next reboot, type Y and press Enter.
   
3. Restart your PC. CHKDSK will scan and fix disk errors before Windows loads.
   

This process might take a while but is essential to rule out physical or file system damage.

👉 Related Guide: How to Run CHKDSK from Boot in Windows 11

Frequently Asked Questions

Q1. Can I stop the SFC scan once it starts?
It’s best not to interrupt the SFC scan, as stopping it midway can leave your system in an inconsistent state. If needed, you can cancel it by closing the Command Prompt, but only do this if the system is unresponsive.

Q2. Why does SFC /scannow say it found issues but fixed none?
This usually means the scan found damaged files, but the repair source (system image) is also corrupted. To fix this, run DISM first, then rerun SFC.

Q3. Is it safe to run SFC and DISM regularly?
Yes, both tools are safe to run and don’t harm your files. Running them occasionally can help keep your Windows system stable and error-free.

Conclusion

SFC /scannow not working Windows 11 is a common issue that can often be fixed with a few extra steps. Starting with Safe Mode or boot-time scans, then using DISM or CHKDSK, helps tackle the deeper problems causing the failures. With these methods, you can restore your system’s stability and fix corrupted files without needing to reinstall Windows.