WINDOWS-RESOURCE-PROTECTION-ERROR

Command Prompt "Windows Resource Protection Could Not Perform the Requested Operation" Applies to: Windows 7, Windows 10, Windows 11

What it means

sfc /scannow itself failed to run properly — this isn't a report about your system files, it's SFC saying it couldn't complete the scan at all. Windows Resource Protection (WRP) is the underlying feature that maintains the cache of known-good files SFC compares against; when SFC can't reach or use that cache, this is the message you get.

Also seen as: Windows resource protection could not perform the requested operation

Quick fix steps

Check that the Windows Modules Installer service is actually running: press Windows+R, type services.msc, find "Windows Modules Installer," and confirm its Startup type isn't set to Disabled — SFC depends on this specific service, and it being stopped is one of the most common, specific causes of this exact error.
Try running sfc /scannow from Safe Mode instead of a normal boot — this bypasses a range of conflicts that can trigger this error during normal operation.
Run chkdsk to rule out disk corruption preventing SFC from reaching its reference cache at all.
If it keeps failing, run DISM /Online /Cleanup-Image /RestoreHealth first — this repairs the underlying image SFC and WRP both rely on — then try sfc /scannow again.
If nothing above resolves it, System Restore to a point before the errors started, or a full Reset this PC, are the most reliable remaining options.

For the full step-by-step walkthrough, see sfc /scannow Explained: What It Does and How to Read the Results.

Frequently Asked Questions

Does this mean sfc /scannow is broken permanently?

No — it means something is currently preventing SFC from running properly (often the Windows Modules Installer service being stopped), which is fixable rather than a permanent tool failure.

Should I try running sfc again immediately after this error?

It's better to address the likely cause first (checking the Windows Modules Installer service, trying Safe Mode) rather than just retrying repeatedly, since the same underlying issue will likely block it again otherwise.

Other error codes

CMD-NOT-RECOGNIZED — "is not recognized as an internal or external command"

Command Prompt can't find the program or command you typed, usually because of a typo, a missing space, or the program not being in a location Windows searches by default (its PATH).

CMD-ACCESS-DENIED — "Access is denied" in Command Prompt

The command you ran needs administrator privileges that the current Command Prompt window doesn't have.

DISM-SOURCE-FILES-NOT-FOUND — DISM Error: The Source Files Could Not Be Found

DISM couldn't reach Windows Update to download the repair files it needs, or a local source wasn't specified.

CMD-PATH-NOT-FOUND — "The System Cannot Find the Path Specified"

The folder path in your command doesn't exist, or was typed incorrectly.