11 reasons why SFC /scannow doesn’t work in Windows 10 (and how to fix it)

If SFC /scannow doesn’t work in Windows 10, the usual causes are permissions, a damaged component store, disk or memory problems, third‑party interference, or a corrupted Windows image — and most cases can be fixed with a few targeted commands and checks. This article explains the common reasons SFC fails and shows step‑by‑step fixes so you can run System File Checker successfully.

Key Takeaway

Run Command Prompt as an administrator, then repair the Windows component store with DISM /Online /Cleanup-Image /RestoreHealth before re-running sfc /scannow; if that doesn’t help, check disk health, disable interfering software, and run SFC offline from WinRE.

Quick Fix Guide

Quick Fix Guide

Reason for the Problem	Quick Solution
1. Not running Command Prompt as Administrator	Open Command Prompt (Admin) and run sfc /scannow.
2. Windows Modules Installer or related services disabled	Start Windows Modules Installer (TrustedInstaller) and Windows Update services.
3. Corrupt component store (DISM required)	Run DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow.
4. Pending restart or stuck updates	Reboot or clear pending updates (run wusa /uninstall /kb: or use WinRE to delete pending.xml).
5. Antivirus/third‑party interference	Temporarily disable antivirus or boot to Safe Mode then run SFC.
6. File system errors on disk	Run chkdsk C: /f /r and restart, then rerun SFC.
7. SFC reports “could not perform the requested operation”	Run sfc /scannow from WinRE or offline with /offbootdir//offwindir.
8. System file protection locked by another process	Boot to Safe Mode or WinRE and run SFC offline.
9. Incorrect or missing repair source image	Use DISM with /Source: pointing to a valid install.wim/install.esd or perform in‑place repair.
10. Malware or rootkits prevent SFC	Scan with reputable antimalware (Windows Defender Offline or a rescue disk) and remove malware.
11. Hardware faults or low disk space	Run memory tests, SMART/disk diagnostics and free up space or replace failing hardware.

Detailed Fixes for “tu mets ici le problème du 11 reasons why SFC /scannow doesn’t work in Windows 10 (and how to fix it)”.

H3: 1. Not running Command Prompt as Administrator

Why it causes the problem
SFC needs elevated privileges to replace protected system files. If you run sfc /scannow in a non‑elevated Command Prompt, it may appear to run but will not be able to fix files, or it will fail with permission errors.

Step-by-step solution

1. Press Start, type cmd.
2. Right‑click Command Prompt and choose Run as administrator.
3. In the elevated window type sfc /scannow and press Enter.
   Notes: Always confirm the Command Prompt title bar shows “Administrator”. If UAC is disabled or restricted, enable it temporarily to allow elevation.

H3: 2. Windows Modules Installer or related services disabled

Why it causes the problem
The Windows Modules Installer (TrustedInstaller) and supporting update services are required for SFC to access, install or replace files in WinSxS. If these services are stopped or disabled, SFC may fail.

Step-by-step solution

1. Press Windows + R, type services.msc and press Enter.
2. Find Windows Modules Installer (service name: TrustedInstaller). Double‑click it.
3. Set Startup type to Manual or Automatic, then click Start.
4. Also ensure Windows Update and Background Intelligent Transfer Service (BITS) are not disabled. Set them to Manual or Automatic.
5. Reopen an elevated Command Prompt and run sfc /scannow.
   Tip: You can start TrustedInstaller from CMD with: net start trustedinstaller.

H3: 3. Corrupt component store (DISM required)

Why it causes the problem
SFC repairs files by copying from the component store. If the component store itself is corrupt, SFC cannot retrieve good copies, so it fails or reports irreparable items.

Step-by-step solution

1. Open Command Prompt (Admin).
2. Run these commands in order:
   • DISM /Online /Cleanup-Image /CheckHealth (quick status)
   • DISM /Online /Cleanup-Image /ScanHealth (detailed scan)
   • DISM /Online /Cleanup-Image /RestoreHealth (repair)
3. After RestoreHealth completes (may take 10–30 minutes), run sfc /scannow.
4. If DISM cannot repair, use an alternate source: mount a matching Windows 10 ISO and run:
   DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:X:\sources\install.wim:1 /LimitAccess (replace X: with mounted drive).
   Notes: Use an ISO matching your edition and build (Home/Pro, and the correct feature update version). If you have install.esd, either convert it or point DISM accordingly.

H3: 4. Pending restart or Windows Update operations

Why it causes the problem
A pending action (like a pending reboot after updates) can lock replacement files so SFC cannot complete operations, producing errors.

Step-by-step solution

1. Reboot the PC and try sfc /scannow again.
2. If a reboot doesn’t clear it, boot to WinRE: Settings > Update & Security > Recovery > Restart now (under Advanced startup) or hold Shift while clicking Restart.
3. In WinRE, choose Troubleshoot > Advanced options > Command Prompt and run:
   • Navigate to %windir%\winsxs and check for pending.xml. If present, rename it: ren pending.xml pending.old (use caution).
4. Exit and reboot; run sfc /scannow.
   Warning: Modifying pending files can affect updates; only rename/delete when necessary.

H3: 5. Antivirus or third‑party software interfering

Why it causes the problem
Some security programs hook into file system APIs and can block SFC from replacing or verifying files.

Step-by-step solution

1. Temporarily disable real‑time protection in your antivirus or uninstall the third‑party AV. For Windows Defender: Settings > Update & Security > Windows Security > Virus & threat protection > Manage settings, toggle Real‑time protection off.
2. Reboot into Safe Mode to minimize third‑party drivers: Settings > Recovery > Restart now > Troubleshoot > Advanced Options > Startup Settings > Restart > press 4 (Safe Mode).
3. From Safe Mode open Command Prompt (Admin) and run sfc /scannow.
   Note: Re-enable antivirus after testing.

H3: 6. File system errors on disk

Why it causes the problem
SFC relies on a healthy NTFS file system. Disk errors or bad sectors can prevent file verification and replacement.

Step-by-step solution

1. Open Command Prompt (Admin).
2. Schedule and run a check: chkdsk C: /f /r and confirm to schedule on next restart.
3. Reboot the PC and allow CHKDSK to complete (may take hours depending on disk size and issues).
4. After CHKDSK completes, run sfc /scannow.
   Tips: If errors persist, check SMART data using a tool like wmic diskdrive get status or third‑party disk utilities.

H3: 7. SFC reports “Windows Resource Protection could not perform the requested operation”

Why it causes the problem
This generic error happens when SFC can’t access required resources (locked files, storage problems, insufficient permissions, corrupt logs).

Step-by-step solution

1. Run chkdsk as above and ensure services are running.
2. If still failing, run SFC offline from WinRE: boot to WinRE > Advanced options > Command Prompt. Identify drive letter for Windows (often D: in WinRE) by running diskpart > list vol > exit. Then run:
   sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows (replace D: with correct drive).
3. Check %windir%\logs\cbs\cbs.log for more details or extract SFC entries:
   findstr /c:”[SR]” %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt.
   Note: Reading the log helps identify which files failed so you can replace individually.

H3: 8. System file protection locked by another process

Why it causes the problem
If another repair tool or process (like a third‑party system optimizer) is running, SFC can be blocked from writing files.

Step-by-step solution

1. Boot to Safe Mode or WinRE to reduce active processes (see previous Safe Mode steps).
2. From Safe Mode run sfc /scannow.
3. If an active process is suspected, check Task Manager (Ctrl+Shift+Esc) and stop suspicious utilities before rerunning SFC.
   Tip: Use Autoruns (Sysinternals) to see startup items that might interfere.

H3: 9. Incorrect or missing repair source image

Why it causes the problem
If the Windows image DISM uses is mismatched (different build/version) or missing required files, repair will fail and SFC can’t get good copies.

Step-by-step solution

1. Download a Windows 10 ISO matching your current build (Settings > System > About → check OS build and edition). Use the Media Creation Tool or MSDN/VLSC if available.
2. Mount the ISO (right‑click > Mount) and note the drive letter (e.g., E:).
3. Run from elevated CMD:
   DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:E:\sources\install.wim:1 /LimitAccess
   (If the ISO has install.esd, either convert or use /Source:ESD:… syntax.)
4. After success, run sfc /scannow.
   Note: An in‑place repair upgrade (run Setup.exe from the ISO and choose “Keep personal files and apps”) also fixes image problems.

H3: 10. Malware or rootkits prevent SFC

Why it causes the problem
Malicious software can lock, replace or hide system files and prevent SFC from detecting or repairing them.

Step-by-step solution

1. Update and run a full scan with Windows Defender or a reputable third‑party scanner. For deeper cleaning, create a rescue USB from vendors like Kaspersky, Bitdefender, or Malwarebytes and boot from it to scan.
2. Use Windows Defender Offline: Settings > Update & Security > Windows Security > Virus & threat protection > Scan options > Windows Defender Offline scan.
3. After malware removal, reboot and run DISM /RestoreHealth and sfc /scannow.
   Warning: If rootkit is present, a clean reinstall may be safest.

H3: 11. Hardware faults or insufficient disk space

Why it causes the problem
Failing RAM or disk hardware, or very low free disk space, can cause file operations to fail and SFC to error out.

Step-by-step solution

1. Check free space: open This PC, ensure drive C: has at least 10–15% free. Free space can be regained via Disk Cleanup (right‑click C: > Properties > Disk Cleanup).
2. Test memory: press Windows + R, type mdsched.exe and choose Restart now and check for problems (Windows Memory Diagnostic). For thorough tests use MemTest86 from USB.
3. Check disk SMART: open an elevated CMD and run wmic diskdrive get model,status,serialnumber or use vendor tools (SeaTools, CrystalDiskInfo).
4. Replace faulty RAM or disk if tests show errors, then rerun SFC.
   Tip: SSDs failing can cause intermittent file corruption; back up data immediately if you suspect hardware issues.

Ajoute une section que tu vois necessaire pour pour completer l’article.

H2: Additional Recovery Options and When to Use Them

When the steps above don’t resolve SFC failures, consider these conservative recovery choices:

• System Restore: If you have a recent restore point, use Control Panel > Recovery > Open System Restore to roll back to a known good state. This is quick and preserves files.
• Reset this PC: Settings > Update & Security > Recovery > Reset this PC lets you choose to keep personal files while reinstalling Windows — useful if system files are severely corrupt.
• In‑place repair install: Mount a matching Windows 10 ISO, run Setup.exe from Windows and choose to upgrade while keeping files and apps; this repairs the OS without wiping user data.
• Clean install: If malware or hardware failures are persistent and you have backups, do a full clean install using a Windows 10 USB.

Use these options in order: System Restore → In‑place repair → Reset this PC → Clean install.

FAQ

H4: How long should SFC /scannow take?
SFC typically takes 10–30 minutes depending on disk speed and system size; if it runs hours or hangs, check disk health and consider running chkdsk or DISM.

H4: Can SFC remove malware or restore files changed by viruses?
SFC repairs only signed protected system files; it won’t remove malware or restore user files — use antimalware tools for infections and back up personal data separately.

H4: Can I run SFC in Safe Mode?
Yes — running sfc /scannow in Safe Mode can succeed when third‑party processes block SFC in normal mode.

H4: How do I read SFC results to know what was fixed?
Extract SFC entries from the CBS log with: findstr /c:”[SR]” %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt and open the resulting file on your Desktop.

H4: When should I perform an in‑place upgrade instead of SFC/DISM?
If DISM fails to repair the image or SFC keeps failing with many irreparable files, an in‑place upgrade (repair install) will refresh system files without wiping apps and data.

Conclusion

Most failures of SFC /scannow in Windows 10 come down to permissions, a damaged component store, disk or hardware issues, interfering software, or a corrupted Windows image — repairing the image with DISM /RestoreHealth, fixing disk errors with chkdsk, disabling conflicting software, and running SFC from an elevated or offline environment will resolve most cases. If those steps fail, use System Restore, an in‑place repair, or a clean install as a last resort to fully fix SFC /scannow doesn’t work in Windows 10.