Fix “Windows Resource Protection Could Not Perform the Requested Operation” (7 Ways)

Quick answer: The “Windows Resource Protection could not perform the requested operation” error means the System File Checker (sfc /scannow) can’t reach the protected system files it needs to scan — usually because the component store is damaged, a required service is disabled, or the disk has errors. The most reliable fix sequence is: run SFC in Safe Mode, or repair the component store first with DISM /Online /Cleanup-Image /RestoreHealth and then re-run SFC. The seven methods below go from simplest to most thorough.

Windows Resource Protection could not perform the requested operation error in Command Prompt
The error as it appears when an SFC scan fails.

Why This Error Happens

Windows Resource Protection (WRP) guards critical system files, folders, and registry keys inside the WinSxS component store. When you run sfc /scannow from an elevated Command Prompt, SFC asks WRP for access to those protected entries. If WRP can’t read or write them, SFC aborts with this message instead of completing the scan.

It isn’t one single root cause — it’s the catch-all SFC returns when its dependencies fail. The usual culprits:

  • Corrupted component store — the WinSxS store SFC pulls replacement files from is itself damaged.
  • Disabled Windows Modules Installer service — SFC needs this service (TrustedInstaller) running to access protected files.
  • Disk errors — bad sectors or file-system corruption blocking access to system files.
  • Third-party interference — antivirus or drivers hooking file access during a normal-mode scan.

Work through the fixes below in order — start with the least disruptive and only move down the list if SFC still fails.

Fix 1: Run SFC in Safe Mode

Safe Mode starts Windows with only essential drivers and services, which removes the third-party interference that commonly blocks SFC. For many users, this alone resolves it.

  1. Press Windows + R, type msconfig, and press Enter.
  2. Go to the Boot tab, check Safe boot → Minimal, click OK, and restart.
  3. Once in Safe Mode, open Command Prompt as administrator (right-click Start → Terminal (Admin) or search “cmd” → Run as administrator).
  4. Run:
    sfc /scannow
  5. Let the scan finish completely, then run msconfig again, uncheck Safe boot, and restart normally.
Running sfc scannow in Windows Safe Mode command prompt
Running SFC from Safe Mode avoids conflicts that block the scan.

Fix 2: Repair the Component Store With DISM First

If the component store itself is damaged, SFC has nothing healthy to restore from. DISM rebuilds that store — and the correct order is DISM first, SFC second.

  1. Open an elevated Command Prompt.
  2. Run:
    DISM /Online /Cleanup-Image /RestoreHealth
    This typically takes 15–30 minutes. Let it reach 100%.
  3. When DISM completes successfully, immediately run:
    sfc /scannow

If DISM itself fails, add a source explicitly or run it from the Windows Recovery Environment (see Fix 5).

DISM RestoreHealth command repairing Windows image
DISM repairs the Windows component store that SFC depends on.

Fix 3: Check the Disk With CHKDSK

Bad sectors and file-system errors can physically block SFC from reaching protected files — common on aging hard drives.

  1. Open an elevated Command Prompt.
  2. Run:
    chkdsk C: /f /r
    Replace C: with your system drive letter if different.
  3. Type Y when asked to schedule the scan for the next restart, then reboot.
  4. The scan can take a long time on large drives — let it finish, then run sfc /scannow again.

Fix 4: Enable the Windows Modules Installer Service

SFC depends on the Windows Modules Installer service (TrustedInstaller). If it’s disabled, WRP can’t do its job — and this is a very common cause of the closely related “Windows Resource Protection could not start the repair service” message too.

  1. Press Windows + R, type services.msc, and press Enter.
  2. Scroll to Windows Modules Installer and double-click it.
  3. Set Startup type to Manual, click Start, then Apply → OK.
  4. Run sfc /scannow in an elevated Command Prompt.

Fix 5: Run SFC From the Windows Recovery Environment

If SFC fails even in Safe Mode, run it outside of Windows entirely. In WinRE, nothing third-party is loaded at all.

  1. Hold Shift while clicking Restart (or go to Settings → System → Recovery → Advanced startup → Restart now).
  2. Choose Troubleshoot → Advanced options → Command Prompt.
  3. Your drive letters may shift here — confirm the Windows drive with diskpart → list volume → exit if unsure.
  4. Run SFC against the offline installation:
    sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
    Adjust the drive letter if your Windows partition shows up differently in WinRE.

Fix 6: Free Disk Space and Check Permissions

SFC needs working room — a nearly full system drive or broken permissions on WinSxS can trigger the error.

  • Ensure at least 10–15 GB free on the system drive (Settings → System → Storage, or Disk Cleanup).
  • Confirm you’re running Command Prompt as administrator — a non-elevated prompt will fail.
  • If you use third-party antivirus, temporarily disable its real-time protection during the scan; re-enable it immediately after.

Fix 7: In-Place Repair Install (Last Resort)

If every method above fails, the installation’s servicing stack is likely damaged beyond targeted repair. An in-place upgrade reinstalls Windows while keeping your files and apps:

  1. Download the Windows 11 installation media (or Windows 10 equivalent) from Microsoft.
  2. Run setup.exe from the mounted ISO and choose Keep personal files and apps.
  3. Complete the installation, then run sfc /scannow to verify.

Back up important data first — while the keep-everything option is reliable, no major system operation is risk-free.

What If SFC Finds Corrupt Files But Can’t Fix Some of Them?

A closely related outcome: SFC completes but reports “Windows Resource Protection found corrupt files but was unable to fix some of them.” This is different from our main error — here SFC could access the files, but couldn’t repair everything. Handle it like this:

  1. Run DISM RestoreHealth, then SFC again. The component store may have been repaired by DISM after SFC’s first pass — a second SFC run often succeeds where the first failed:
    DISM /Online /Cleanup-Image /RestoreHealth
    sfc /scannow
  2. Check which files failed. Extract the SFC entries from CBS.log and look at the most recent [SR] entries naming unrepaired files. If the same file fails repeatedly across DISM + SFC cycles, it’s a candidate for the in-place repair install in Fix 7.
  3. Don’t chase individual DLL downloads. Manually replacing a system file with one from a random website risks version mismatches and malware. If DISM + SFC + CHKDSK can’t repair it, the in-place upgrade is the safe path.

How to Read the SFC Log (CBS.log)

When SFC reports problems, details go to the Component Based Servicing log at:

%windir%\Logs\CBS\CBS.log

To extract just the SFC entries to a readable file on your desktop, run in an elevated Command Prompt:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt"
CBS log file location in Windows logs folder
When SFC cannot fix everything, CBS.log shows exactly which files are corrupt.

Open sfcdetails.txt and check entries from the most recent scan (the file accumulates older runs too — verify dates). For the official command references, see Microsoft Learn’s documentation on the System File Checker and DISM.

Frequently Asked Questions

What does “Windows Resource Protection could not perform the requested operation” mean?

It means sfc /scannow couldn’t access the protected system files it needs to scan — usually because the component store is corrupted, the Windows Modules Installer service is disabled, or disk errors are blocking access. It is not a virus or a sign Windows is destroyed.

What is the difference between this error and “could not start the repair service”?

They’re closely related. “Could not start the repair service” almost always means the Windows Modules Installer (TrustedInstaller) service is disabled — Fix 4 above resolves it directly. “Could not perform the requested operation” is broader and can also come from component-store or disk problems.

Should I run DISM or SFC first?

Run DISM first (DISM /Online /Cleanup-Image /RestoreHealth), then SFC. DISM repairs the component store that SFC draws replacement files from — running SFC first against a broken store just fails again.

Can I run sfc /scannow in Safe Mode?

Yes, and it’s one of the most effective fixes for this error. Boot into Safe Mode (msconfig → Boot → Safe boot → Minimal), open an elevated Command Prompt, and run sfc /scannow. Remember to uncheck Safe boot afterward.

Will SFC delete my personal files?

No. SFC only verifies and repairs protected Windows system files. Your documents, photos, and installed programs are untouched.

How long does sfc /scannow take?

Typically 15–45 minutes depending on your drive speed and system size. DISM’s RestoreHealth can take a similar amount of time. Let both reach 100% without interrupting them.

More Windows You May Like

Leave a Reply

Your email address will not be published. Required fields are marked *