If you’re seeing an SFC scannow error in Windows, the fix depends on the specific error code, but most issues are resolved by running the scan from Safe Mode, repairing the Windows image with DISM first, or clearing the SoftwareDistribution folder. This guide covers the most common SFC errors, why they happen, and the exact steps to get the System File Checker working again.
What Is SFC Scannow and Why Does It Fail?
System File Checker (SFC) is a built-in Windows utility that scans protected system files and replaces corrupted or missing ones with correct versions. You run it by opening Command Prompt as administrator and typing sfc /scannow. The scan compares every protected file against a cached copy in the Windows folder, and when a file doesn’t match, it attempts to repair it.
SFC fails for a few common reasons. The most frequent is that the protected file cache itself is corrupted or missing, so SFC has nothing to restore from. Another common cause is that the scan is interrupted by a running process, a disk error, or a permissions problem. Sometimes SFC simply cannot repair a file because the system is currently using it, and the scan reports an error instead of scheduling a repair at next boot.
Common SFC Error Messages and What They Mean
Here are the errors you’re most likely to see, with a plain-language explanation of each:
- “Windows Resource Protection could not perform the requested operation” — SFC couldn’t start. This usually means the scan was blocked by a policy, a pending reboot, or a corrupted Windows Resource Protection service.
- “Windows Resource Protection found corrupt files but was unable to fix some of them” — SFC found problems but couldn’t repair all of them. The underlying cause is often a corrupted component store, which DISM can fix.
- “Windows Resource Protection could not start the repair service” — The Windows Modules Installer service is disabled or stopped. You’ll need to enable it in Services.
- “SFC scannow failed to initialize” — The scan couldn’t start, often due to insufficient disk space or a permissions issue on the Windows folder.
- “Windows Resource Protection found corrupt files and successfully repaired them” — This is a success message, not an error, but it’s often followed by a reboot requirement.
Step-by-Step Fix: Run DISM Before SFC
The single most effective fix for SFC errors is to repair the component store first using Deployment Imaging Service and Management (DISM). SFC relies on a cached copy of system files, and if that cache is damaged, SFC will fail no matter how many times you run it. DISM repairs the cache itself.
- Open Command Prompt as administrator (right-click Start, select “Command Prompt (Admin)” or “Terminal (Admin)”).
- Type
DISM /Online /Cleanup-Image /RestoreHealthand press Enter. This may take 15-30 minutes. - When it finishes, restart your computer.
- Run
sfc /scannowagain in an elevated Command Prompt.
If DISM fails because it can’t reach Windows Update, you can use a Windows installation media as a source. Insert a bootable USB or DVD with the same version of Windows, then run:
DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim /LimitAccess
Replace D: with the drive letter of your installation media. This tells DISM to use the local files instead of downloading from the internet.
Fix SFC by Running in Safe Mode
If SFC fails because a running process is locking a file, Safe Mode is your best bet. Safe Mode loads only the essential drivers and services, so fewer things can interfere with the scan.
- Open Settings, go to System > Recovery.
- Under “Advanced startup,” click “Restart now.”
- When the PC reboots, choose Troubleshoot > Advanced options > Startup Settings > Restart.
- Press 4 or F4 to boot into Safe Mode.
- Open Command Prompt as administrator and run
sfc /scannow.
If you can’t boot into Windows normally, you can also access SFC from the Recovery Environment. Boot from a Windows installation USB, choose “Repair your computer,” then Troubleshoot > Advanced options > Command Prompt. From there, run sfc /scannow — it will scan the offline Windows installation.
Check the CBS Log to Find the Real Problem
When SFC fails, it writes a detailed log to C:\Windows\Logs\CBS\CBS.log. This file is long and technical, but you can filter it to find the specific errors. Open Command Prompt as administrator and run:
findstr /c:"[SR]" %windir%\logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt"
This creates a file on your desktop with only the SFC-related lines. Look for lines containing “Cannot repair member file” or “Repairing file”. The file path in those lines tells you which system file is corrupted. If it’s a file you recognize, like a DLL for a specific driver, you can sometimes replace it manually from a known-good copy.
If the log shows 0x800f081f or 0x800f0906, DISM couldn’t find the source files. This points to a problem with the component store itself, and the DISM repair method above is the right fix.
When SFC Is Blocked by Policies or Services
Some SFC errors are caused by system settings, not file corruption. Here are the most common blockers and how to clear them:
- Windows Modules Installer service is disabled — Press Win+R, type
services.msc, find “Windows Modules Installer,” right-click and set Startup type to “Manual,” then start the service. - Pending reboot — If Windows has a pending update or file operation, SFC won’t run. Restart the computer and try again.
- Group Policy blocks the scan — Press Win+R, type
gpedit.msc, navigate to Computer Configuration > Administrative Templates > System > Windows File Protection. Ensure “Set Windows File Protection scanning” is not set to “Disabled.” - Insufficient disk space — SFC needs room to create temporary files. Free up at least 5 GB on the system drive.
Alternative: Use DISM with a Windows ISO
If DISM with Windows Update fails and you don’t have installation media handy, you can download the official Windows ISO from Microsoft and mount it. Right-click the ISO file and select “Mount,” then note the new drive letter. Run the same DISM command with the /Source parameter pointing to the mounted ISO’s sources\install.wim file.
This method is more reliable than relying on Windows Update because it uses a pristine copy of the system files. It’s also useful if you’ve already tried the online repair and it timed out or failed to connect.
Frequently Asked Questions
Why does SFC say it can’t fix some files even after DISM?
After DISM repairs the component store, SFC should be able to fix most files. If it still fails on a specific file, the corruption may be in the file itself rather than the cache. In that case, you can try replacing the file manually from a known-good source, or consider a repair install of Windows using the “Keep my files” option. A repair install reinstall the operating system while preserving your personal files and installed apps.
How long does sfc /scannow take?
A typical scan takes 10 to 20 minutes on a modern system, but it can take longer if the disk is slow or heavily fragmented. The scan appears to hang at 0% or 20% for a while — this is normal. Don’t close the Command Prompt window, as that will abort the scan and may leave the system in an inconsistent state.
Can I run SFC while Windows is running normally?
Yes, you can run SFC in normal mode, and it’s the default way most people use it. However, if you get the “unable to fix” error, running it in Safe Mode or from the Recovery Environment gives it the best chance of success because fewer processes are locking files.
What’s the difference between SFC and DISM?
SFC checks and repairs individual system files against a cached copy. DISM repairs the component store — the source files that SFC uses as its reference. If the component store is corrupted, SFC will fail even if the actual system files are fine. That’s why the recommended order is DISM first, then SFC.
Will SFC delete my personal files or programs?
No. SFC only touches protected Windows system files. It will not delete your documents, photos, or installed applications. The worst case is that a repaired file reverts to its default state, which could reset a setting or two, but it won’t remove your data.
Is there a way to see what SFC actually fixed?
Yes. After the scan completes, the CBS log records every file it repaired. Use the findstr command shown above to extract the details, then look for lines that say “Repairing file” followed by the full path. You can also check the .log file in C:\Windows\Logs\CBS\ for a summary at the end of the scan.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- iOS 18 Safari Not Working? Fixes That Help
- How to Check Your Linux Kernel for Spectre
- iPhone Safe Mode: How to Enable or Disable It
- Fix Slow Internet Lag on Samsung Galaxy Note
- How to Get iOS 17 on iPhone X (Safe Methods)
- Fix Gmail IMAP Error in Outlook: Step-by-Step