sodcalculator

10 Tech How-To

SFC ScanNow Error: Fix Windows Resource Protection

Guide 10-58096 · Updated · Step by step

If you see “Windows Resource Protection could not perform the requested operation” when running sfc /scannow, the fix is usually to run the scan in Safe Mode, repair the Windows image with DISM, or clear the Windows Update cache. This error almost always means System File Checker can’t access or modify protected files due to a locked file, a corrupted component store, or a pending operation. Below is a practical guide to resolving it, plus the background you need to understand why it happens.

What System File Checker Actually Does

System File Checker (SFC) is a Windows utility that verifies the integrity of every protected system file and replaces corrupted versions with correct ones. It compares each file’s hash against a catalog stored in the Windows component store (%WinDir%\WinSxS). When you run sfc /scannow from an elevated Command Prompt, the tool:

  • Scans all protected files and checks their digital signatures.
  • Repairs any file that fails verification by copying a fresh copy from the component store.
  • Logs the results in %WinDir%\Logs\CBS\CBS.log.

The “could not perform the requested operation” error typically appears after the scan starts and fails to repair a file. It can also appear immediately if SFC cannot even start its repair phase.

Why the Error Occurs

There are several common causes, and knowing them helps you pick the right fix:

  • Locked files: Some system files are in use by Windows itself or by a driver, so SFC cannot replace them while the system is running normally.
  • Corrupted component store: SFC pulls replacement files from the WinSxS folder. If that store is damaged, SFC has nothing valid to copy.
  • Pending operations: If a Windows Update or a previous repair is incomplete, SFC may refuse to run until the pending actions are finished.
  • Third-party software: Antivirus or security tools can lock protected files, and some “optimizer” utilities alter permissions.
  • Disk errors: Bad sectors on the drive can prevent SFC from reading or writing files.

Fix 1: Run SFC in Safe Mode

Safe Mode loads Windows with a minimal set of drivers and services, which reduces file locks. This is the quickest fix to try first.

  1. Open Settings > System > Recovery (Windows 10/11) and under “Advanced startup” click Restart now.
  2. After the PC restarts, choose Troubleshoot > Advanced options > Startup Settings > Restart.
  3. Press 4 or F4 to boot into Safe Mode.
  4. Right-click the Start button and select Terminal (Admin) or Command Prompt (Admin).
  5. Type sfc /scannow and press Enter.

If Safe Mode fixes the error, the cause was a locked file. If the error persists, move to the next fix.

Fix 2: Repair the Component Store with DISM

DISM (Deployment Imaging Service and Management Tool) can repair the Windows image that SFC relies on. Run DISM before SFC if the component store is suspect.

  1. Open an elevated Command Prompt (Run as administrator).
  2. Run DISM /Online /Cleanup-Image /RestoreHealth.
  3. Wait for the process to complete (it can take 15 minutes or more).
  4. If DISM reports an error, try adding /Source:C:\RepairSource\Windows /LimitAccess after specifying a valid Windows installation source (like a mounted ISO).
  5. After DISM finishes, run sfc /scannow again.

DISM uses Windows Update to fetch needed files. If you have no internet or Windows Update is broken, you may need to provide a local source, but for most users the online repair works.

Fix 3: Clear Pending Operations and Update Cache

If a Windows Update is stuck, SFC might be blocked. Resetting the Windows Update components can clear the path.

  1. Stop the relevant services by running these commands in an elevated Command Prompt:
    net stop wuauserv
    net stop cryptSvc
    net stop bits
    net stop msiserver
  2. Rename the SoftwareDistribution folder:
    ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
  3. Rename the catroot2 folder:
    ren C:\Windows\System32\catroot2 catroot2.old
  4. Restart the services:
    net start wuauserv
    net start cryptSvc
    net start bits
    net start msiserver
  5. Reboot and run sfc /scannow again.

This clears any corrupted download cache and resets the update state. It does not remove your personal files or installed programs.

Fix 4: Check Disk for Errors

File corruption can stem from bad sectors. Run a disk check to rule this out.

  1. Open an elevated Command Prompt.
  2. Run chkdsk C: /f /r (replace C: with your system drive).
  3. If prompted to schedule a check on restart, type Y and reboot.
  4. Let the check complete (it can take a long time on large drives).
  5. Afterward, run SFC again.

Note that chkdsk requires administrator rights and may need a restart because the drive is in use.

What If Nothing Works?

If the error persists after all the above, you have a few remaining options:

  • Run SFC from the Windows Recovery Environment (WinRE): Boot from a Windows installation USB, choose “Repair your computer,” then open Command Prompt from Troubleshoot > Advanced options. Run SFC there.
  • Use the “sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows” syntax when running from WinRE, pointing to the correct drive letters.
  • Perform an in-place upgrade repair: Run the Windows installation media and choose “Keep personal files and apps.” This reinstalls Windows without removing your data.
  • Reset this PC: As a last resort, this reinstalls Windows and can fix deep corruption, but you will need to reinstall apps and possibly back up files.

Frequently Asked Questions

Can I run SFC while Windows is running normally?

Yes, you can, and it works most of the time. The error appears when a file is locked or the component store is damaged. Running in Safe Mode or from WinRE bypasses most locks.

How long does SFC take?

A full scan can take 10 to 30 minutes on a typical system. If it appears stuck at a percentage, wait at least 15 minutes before assuming it hung.

What does “Windows Resource Protection found corrupt files but was unable to fix some of them” mean?

This message means SFC detected corruption but could not repair it because the component store lacks the correct file. Running DISM first usually resolves it.

Will SFC delete my personal files?

No. SFC only replaces protected system files. It does not touch your documents, photos, or other user data.

Do I need to run DISM before SFC every time?

Not always. If SFC succeeds, DISM is unnecessary. But if SFC fails to repair files, running DISM first is a best practice because it fixes the source SFC uses.

Is it safe to use third-party “SFC repair” tools?

It is safer to use built-in Windows tools. Third-party tools may claim to fix SFC but can introduce new problems or malware. Stick with DISM and SFC.

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

The whole Tech How-To bed →