SFC Scannow Not Working on Windows? Fixes That Work

If SFC Scannow is not working on Windows, the issue is usually that the System File Checker cannot repair corrupted files because the component store it relies on is itself damaged. This article explains why SFC fails and provides step-by-step fixes, from running DISM to repairing the Windows image manually.

What SFC Scannow Does and Why It Fails

System File Checker (SFC) is a Windows utility that scans protected system files and replaces corrupted ones with correct versions from the Windows component store (located at C:\Windows\WinSxS). When you run sfc /scannow in an elevated Command Prompt, it verifies the integrity of every protected file and repairs those that fail the check.

SFC fails when it cannot read the component store, when the store itself contains corrupted files, or when the scan is interrupted by another process. Common error messages include:

“Windows Resource Protection could not perform the requested operation” – often caused by pending repairs or a read-only system drive.
“Windows Resource Protection found corrupt files but was unable to fix some of them” – means SFC found issues but the component store lacks good copies.
“The system file checker found corrupt files and successfully repaired them” – but the problem persists, which can mean the repair didn’t address the root cause.

Why SFC Can’t Repair: The Component Store Problem

SFC pulls replacement files from the WinSxS folder. If that folder is corrupted or incomplete, SFC has nothing good to copy. This is why running DISM first is so important. DISM (Deployment Imaging Service and Management Tool) repairs the component store itself.

Another reason SFC fails is that the scan is blocked by a pending reboot. If Windows has updates or driver installations waiting, SFC may refuse to run. Also, if the system drive is encrypted with BitLocker or has a recovery partition that is locked, SFC cannot access the files it needs.

How to Fix SFC Scannow Not Working

Follow these steps in order. Each one addresses a common cause.

Run DISM first. Open Command Prompt as Administrator and run: DISM /Online /Cleanup-Image /RestoreHealth. This repairs the component store. Wait for it to complete (it can take 15-30 minutes). Then run sfc /scannow again.
Check for pending reboots. Restart Windows, then try SFC again. If you see “Windows Resource Protection could not perform the requested operation,” a reboot often clears it.
Run SFC in Safe Mode. Boot into Safe Mode (Shift + Restart from the login screen, then Troubleshoot > Advanced Options > Startup Settings > Restart > press 4). In Safe Mode, run SFC. This prevents third-party drivers from interfering.
Use the Windows Installation Media. If DISM with /RestoreHealth fails, use the installation media as a repair source: DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim /LimitAccess (replace D: with your media drive).
Check disk errors. Run chkdsk /f /r on your system drive to fix file system errors that can block SFC.

What to Do If SFC Still Fails

If SFC still cannot repair files, you may need to perform an in-place upgrade (also called a repair install). This reinstalls Windows while keeping your files, settings, and apps. Download the Windows Media Creation Tool, run it, and choose “Upgrade this PC now.” This is a more thorough repair that replaces the entire Windows installation without losing personal data.

Alternatively, you can manually replace the corrupted file. When SFC reports a specific file it couldn’t fix, you can copy a good version from another Windows PC (same version and build) or from the installation media. You will need to take ownership of the file first, which is a more advanced procedure.

Common Misconceptions About SFC

Many users think SFC can fix any system corruption, but it only repairs protected system files. It does not fix registry issues, driver problems, or corrupted user profile files. Also, SFC does not clear the component store; it uses it. If the store is bloated or corrupted, SFC may report errors even after a successful scan.

Another misconception is that running SFC multiple times will eventually fix everything. In reality, if the component store is broken, repeated SFC runs will fail the same way. That is why DISM is the correct first step.

Alternatives to SFC Scannow

If SFC is not working and you cannot repair it, consider these alternatives:

DISM /StartComponentCleanup – removes old versions of updated components, which can free space and fix store corruption.
Windows Update Troubleshooter – resolves update-related corruption that can affect SFC.
System Restore – if you have a restore point from before the corruption, you can roll back to a working state.
Reset This PC – as a last resort, this reinstalls Windows and lets you keep or remove your files.

Frequently Asked Questions

Why does SFC say “Windows Resource Protection could not perform the requested operation”?

This usually means SFC cannot start because of a pending reboot, a locked system drive, or a missing system file. Restart your PC and try again. If it persists, run DISM first to repair the component store.

Can I run SFC from Safe Mode?

Yes, running SFC in Safe Mode is a valid troubleshooting step. It prevents third-party drivers from interfering with the scan. Boot into Safe Mode and run sfc /scannow from an elevated Command Prompt.

Does SFC fix corrupted registry entries?

No. SFC only checks protected system files. It does not scan or repair the registry. To fix registry corruption, you would need to restore a backup or use System Restore.

How long does SFC scannow take?

Typically 10-20 minutes, but it can take longer on slower drives or if there are many files to check. Do not interrupt it; let it finish.

What if DISM fails with error 0x800f081f?

This error means the source files are not available. You need to specify a valid source using the /Source parameter, pointing to a Windows installation media or a network share with the correct version of Windows.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →