SFC Scannow Not Working? How to Fix It on Windows 10/11

If sfc scannow not working on your computer, you may be unable to repair corrupted or missing system files, which can lead to persistent Windows errors, crashes, or performance problems. In this guide, you will learn several effective troubleshooting methods to restore SFC functionality.

By Aria    Updated on March 6, 2026

SFC Scannow Not Working

The SFC /scannow command is a built-in Windows tool designed to detect and repair corrupted or missing system files. However, many users encounter situations where SFC scannow not working, such as the scan getting stuck at a certain percentage, failing to start, or returning errors like "Windows Resource Protection could not perform the requested operation". When this happens, it prevents Windows from repairing important system components and can leave underlying system issues unresolved.

This problem may occur due to corrupted system images, disk errors, insufficient permissions, or conflicts within Windows services. As a result, the command may stop responding, fail to complete the scan, or report that it cannot repair certain files.

Common Reasons Why SFC Scannow Is Not Working

Understanding the underlying causes can make troubleshooting much easier. When SFC /scannow fails to run or complete properly, it is usually due to system-level issues that prevent Windows from accessing or repairing protected files. Identifying these factors helps determine the most appropriate fix before attempting advanced repair steps. Some of the most common reasons include:

🔔Corrupted Windows system image

The System File Checker relies on the Windows component store (WinSxS) to replace damaged files. If this image is corrupted, SFC may fail or report that it cannot repair certain files.

💾Disk errors or bad sectors

File system corruption or physical disk issues can interrupt the scanning process, causing SFC to stop responding or fail midway.

✂️Windows Modules Installer service disabled

The Windows Modules Installer (TrustedInstaller) service manages system file modifications. If it is disabled or not running, SFC may display errors such as "Windows Resource Protection could not start the repair service".

🔍Insufficient administrative permissions

Running SFC without elevated privileges may prevent the tool from accessing protected system resources required for the repair process.

🛠️Conflicts with running processes or security software

Some background programs or third-party antivirus tools may lock system files temporarily, preventing SFC from scanning or replacing them.

How to Fix SFC Scannow not Working on Windows 10/11

After identifying the possible causes, the next step is to apply targeted fixes. You can choose the appropriate solution based on your actual situation and the results from the SFC report. Let's explore them one by one.

Fix 1. Run SFC Scan in Safe Mode

Sometimes background services, startup programs, or third-party security software may interfere with the SFC process. Booting Windows into Safe Mode loads only essential system drivers and services, creating a minimal environment where SFC can run without conflicts. This often resolves cases where the SFC freezes, fails to start, or stops responding.

Step 1. Press "Win" + "R", type "msconfig" in the Run dialog, and press "Enter" to open System Configuration window.

Step 2. Go to the "Boot" tab and check "Safe boot", then select "Minimal" and click "OK".

Step 3. Restart your computer to enter Safe Mode. Then, run sfc /scannow again to check if it works normally.

Fix 2. Check the SFC Scan Results

If the SFC scan runs but reports that some files cannot be repaired, reviewing the scan results can help identify which system components are affected. Usually, analyzing these scan results will help you find the solution. Run SFC, wait for the command to complete, and then check the scan results.

👉Windows Resource Protection did not find any integrity violations

This indicates that your system files are normal, and your core system files are healthy, with no corruption or tampering. No action is required.

👉Windows Resource Protection found corrupt files and successfully repaired them

SFC has found corrupted system files and replaced them with the correct versions. You can restart your computer for the repairs to take effect.

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

This means SFC detected issues but lacks the correct file versions to replace the corrupted ones. You can try using the more advanced DISM command to download healthy system files and repair the system component store. Then run the SFC command again.

👉Windows Resource Protection could not perform the requested operation

This is usually caused by a temporary glitch. Some program or service has blocked SFC from starting normally.

Fix 3. Repair Windows Image Using DISM

If the Windows component store becomes corrupted, SFC may fail because it cannot retrieve clean replacement files. In this situation, the DISM (Deployment Image Servicing and Management) tool can repair the Windows system image first. Once the image is restored, running SFC again usually completes successfully.

Step 1. Locate Command Prompt in the Start menu and right click on it, then choose "Run as administrator".

Step 2. Run the following command and press "Enter": DISM /Online /Cleanup-Image /RestoreHealth

Step 4. After the DISM command finishes, run "sfc /scannow" again. Wait for the repair process to complete, which may take several minutes. The SFC command should now work properly.

Fix 4. Check Disk for File System Errors

Disk corruption or bad sectors can interrupt system file scanning and prevent SFC from working normally. Running the CHKDSK utility helps detect and repair file system issues on the drive where Windows is installed. Once disk errors are fixed, SFC can operate more reliably.

Step 1. Open Command Prompt and run it as administrator.

Step 2. Enter the following command: chkdsk G: /f /r and press "Enter".

Step 3. Wait for Windows to complete the disk check. Then, run SFC command to check if it works.

Fix 5. Enable Windows Modules Installer Service

The Windows Modules Installer (TrustedInstaller) service is responsible for managing system file updates and repairs. If this service is disabled or not running, SFC cannot modify protected system files, which leads to errors such as "Windows Resource Protection could not start the repair service". Ensuring this service is enabled can resolve the issue.

Step 1. Press "Win" + "R", type "services.msc" in the Run dialog, and press "Enter" to open Services window.

Step 2. Locate Windows Modules Installer in the service list and right click on it, then choose "Properties".

Step 3. Set "Startup type" to "Manual" or "Automatic", then click "Start".

Step 4. Click "Apply" and "OK" to save the changes, and run sfc /scannow again.

Fix 6. Run Offline SFC Scan from Recovery Environment

When Windows cannot repair system files during normal operation, running an offline SFC scan from the Windows Recovery Environment can help. This method scans the Windows installation outside the running system, allowing deeper repairs that are otherwise blocked.

Step 1. Go to "Settings" > "Update & Security" > "Recovery".

Step 2. Click "Restart now" under the "Advanced startup" section to enter Recovery environment.

Step 3. Select "Troubleshoot" > "Advanced Options" > "Command Prompt".

Step 4. Enter the following command:

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

Step 5. Wait for the scan to finish and restart your computer normally.

Fix 7. Use System Restore

If SFC stopped working after a recent system change, such as a driver update, software installation, or Windows update, System Restore can revert the system to an earlier state where everything worked properly. If you have created a restore point before the sfc scannow stopped working, this method restores system files and settings without affecting personal files.

Step 1. Type "Create a restore point" in the Start menu and open it.

Step 2. Under the "System Protection" tab, click "System Restore".

Step 3. Select a restore point created before the issue appeared.

Step 4. Confirm the restore point and click "Finish" to start the process.

After system restore, SFC should work normally again.

Summary

In summary, when SFC scannow not working occurs on Windows 10 or 11, it usually indicates underlying system issues such as corrupted system images, disk errors, disabled services, or permission conflicts. You can resolve the problem effectively with the approaches described above. These methods ensure that SFC can detect and repair corrupted files without interruption.

Additionally, if critical files are accidentally lost or replaced during troubleshooting, using a professional tool like MyRecover can safely restore deleted system or personal files, offering a reliable safety net while performing advanced repairs. It can help you recover files from 500+ complex data loss scenario, such as a crashed computer, emptied Recycle Bin, corrupted SD card, write-protected disk, and more.

MyRecover
Easy & Powerful Data Recovery Software
  • Recover deleted & lost files from HDD, SSD, USB, SD card, camera as you need.
  • Support 1000+ formats of photos, videos, docs, archives, emails, compressed files, etc.
  • Reliable rescue for deletion, formatted disk, emptied Recycle Bin, system crashes and more.
Aria · Editor
I've been specializing in the data recovery industry for years. I am dedicated to translating intricate software features and functions into plain - language explanations, enabling everyone to understand how to utilize the data recovery software effectively and retrieve their valuable data with confidence. My overarching professional objective is to bridge the gap between complex data recovery technologies and users of all skill levels. Through my work, I strive to eliminate the common anxiety associated with data loss, thereby providing a reliable method for safeguarding digital assets.