Fix 'Windows Resource Protection Could Not Perform the Requested Operation'

Cause 1: Corrupted Component Store Files (Most Common)

You run sfc /scannow and instead of a clean bill of health, you get that maddening message. I know it's frustrating, especially when you're already dealing with a broken Windows install.

The most frequent culprit is a corrupted component store – that's where Windows keeps the original system files it uses to repair others. If the store itself is damaged, SFC literally can't do its job. Think of it like trying to fix a car with a bent wrench.

The fix: Run DISM to repair the component store first, then retry SFC. DISM (Deployment Image Servicing and Management) is the tool that fixes the store itself.

1. Open Command Prompt as administrator. Press Win + X and pick "Terminal (Admin)" or "Command Prompt (Admin)".
2. Run this command:

   DISM /Online /Cleanup-Image /RestoreHealth

3. Wait – this can take 10 to 30 minutes depending on your system and internet speed. Let it finish. Don't close the window.
4. Once it says "The restore operation completed successfully", run SFC again:

   sfc /scannow

This solves it about 70% of the time. If DISM reports an error or says it couldn't find the source files, you're in the second scenario.

Cause 2: Windows Update Can't Download Needed Files (DISM Fails)

Sometimes DISM itself fails because Windows Update is being stubborn. You'll see an error like 0x800f081f or 0x800f0906 – that's DISM saying "I couldn't get the files I need."

This often happens right after a feature update or when the update service has been recently disabled. A real-world trigger: you've just upgraded from Windows 10 to 11 and your first SFC scan fails.

The workaround: Use the Windows installation media as the source instead of Windows Update. Here's how:

1. Download the Windows 11 ISO from Microsoft's official site (or use a USB you already have).
2. Mount the ISO by right-clicking it and choosing "Mount". Note the drive letter – say E:
3. Run this DISM command with the Source pointing to the install.wim file inside the sources folder:

   DISM /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim /LimitAccess

4. If that throws an error about the index, you need to find which index matches your Windows edition:

   DISM /Get-WimInfo /WimFile:E:\sources\install.wim

5. Then add /Index:1 (or whichever number matches your edition) to the command.

After DISM completes, run sfc /scannow again. This should clear the block.

Cause 3: Pending.xml Corruption or Antivirus Interference

Two less common but real culprits:

Pending.xml Issues

Windows keeps a file called Pending.xml that tracks unfinished updates. If that file gets corrupted, SFC throws the "could not perform" error. This happens when a Windows update crashes mid-install and leaves things in a half-baked state.

How to clear it:

1. Boot into Safe Mode (restart holding Shift while clicking "Restart", then go to Troubleshoot → Advanced Options → Startup Settings).
2. Once in Safe Mode, open Command Prompt as admin.
3. Navigate to the Windows folder:

   cd C:\Windows\WinSxS\

4. Rename the problematic file:

   ren pending.xml pending.old

5. Reboot normally and run SFC again.

Antivirus Interference

I once spent two hours chasing this on a client's machine. Third-party antivirus (especially ones with "behavioral detection" like Norton or McAfee) can lock system files SFC needs to access.

The test: Temporarily disable your antivirus protection (not uninstall), then run SFC. If it works, add an exclusion for C:\Windows\WinSxS and C:\Windows\System32 in your AV settings. If it still fails, your AV isn't the problem – re-enable it and move on.

I'm not a fan of disabling AV, but a quick toggle for a scan is fine. Just remember to turn it back on.

Quick-Reference Summary

That's the whole playbook. Run the first fix, and if it doesn't stick, work down the list. You'll have SFC running clean in no time.