Windows Resource Protection Error: How to Fix It

The message “Windows Resource Protection could not perform the requested operation” means System File Checker could not complete its scan.

That is different from SFC finishing and reporting that it found corrupt files.

When this message appears, the problem is usually not the damaged system file you originally wanted SFC to repair. The immediate problem is that something is preventing SFC itself from completing.

Microsoft’s current guidance is especially useful here: when SFC returns this exact message, Microsoft recommends running the scan in Safe Mode. Before that, I also recommend repairing the Windows component store with DISM because SFC depends on that repair source.

First, Run DISM Before Repeating SFC

Open Terminal (Admin) or Command Prompt (Admin) and run:

DISM /Online /Cleanup-Image /RestoreHealth

Wait for DISM to finish.

Microsoft currently recommends running DISM before SFC because DISM repairs the Windows image that System File Checker may need when replacing damaged protected files.

After DISM reports that the restore operation completed successfully, restart Windows.

Then run:

sfc /scannow

If SFC now reaches 100%, the component-store repair was enough.

If you still receive:

Windows Resource Protection could not perform the requested operation

move to Safe Mode rather than repeatedly running the same command.

Try SFC in Safe Mode

Safe Mode starts Windows with a reduced set of drivers and services.

That makes it useful when a third-party service, security tool, driver, or background process is interfering with SFC.

Open:

Settings > System > Recovery

Under Advanced startup, choose:

Restart now

Then go to:

Troubleshoot > Advanced options > Startup Settings > Restart

Press:

4

or:

F4

to start Safe Mode.

Once Windows loads, open Command Prompt as administrator and run:

sfc /scannow

Microsoft specifically recommends Safe Mode for the “Windows Resource Protection could not perform the requested operation” result.

If SFC works in Safe Mode but not during a normal startup, the Windows repair tools themselves are probably functional. A third-party service, driver, or background application is more likely to be interfering.

If SFC Still Fails in Safe Mode, Check the Drive

System File Checker has to read protected Windows files from the system drive.

File-system corruption can prevent that.

Open Terminal (Admin) and run:

chkdsk C: /scan

This performs an online scan of the Windows drive.

If CHKDSK reports problems that require repair, follow the action Windows recommends.

Microsoft also supports more aggressive CHKDSK options such as /f and /r, but I would not jump straight to a long offline surface scan unless the drive actually shows file-system problems or storage symptoms.

Pay attention to warning signs such as:

• repeated file corruption
• very slow file access
• frequent freezes
• SMART warnings
• blue screens related to storage
• unusual noises from a mechanical hard drive

If the drive appears physically unhealthy, back up important files before repeatedly running repair tools.

Check Whether Windows Modules Installer Is Available

Windows Modules Installer, also known as TrustedInstaller, is involved in servicing protected Windows components.

Press:

Windows + R

Enter:

services.msc

Find:

Windows Modules Installer

Its startup type is normally Manual.

If the service has been deliberately disabled by a tweak or optimization tool, return it to Manual and restart Windows.

I would not force it to Automatic simply because SFC failed once.

The important thing is that the service has not been disabled in a way that prevents Windows servicing from working normally.

If Safe Mode Works, Use a Clean Boot to Find the Conflict

A clean boot is useful when:

• SFC fails during a normal startup
• SFC works in Safe Mode
• you recently installed antivirus, optimization, backup, disk, or system-monitoring software

Open:

msconfig

Under Services:

1. Check Hide all Microsoft services.
2. Disable the remaining third-party services.
3. Open Task Manager from the Startup tab.
4. Disable nonessential startup apps.
5. Restart Windows.

Run:

sfc /scannow

again.

If SFC now works, re-enable third-party items gradually until the problem returns.

That gives you evidence about the conflicting software instead of uninstalling applications at random.

Run SFC Offline When Normal Windows Cannot Complete the Scan

If SFC still cannot complete, use Windows Recovery Environment.

Open:

Settings > System > Recovery > Advanced startup > Restart now

Then choose:

Troubleshoot > Advanced options > Command Prompt

The Windows partition may not use C: inside Recovery Environment.

To identify it, run:

bcdedit

Look for the osdevice entry under Windows Boot Loader.

For example, if it shows:

partition=D:

your offline Windows installation is probably on D:.

You can then run:

sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows

Replace D: with the drive letter shown on your PC.

Microsoft documents /offbootdir and /offwindir specifically for offline SFC repairs.

Do not blindly copy C: into the command because drive letters commonly change inside Windows Recovery Environment.

What If DISM Fails Too?

If:

DISM /Online /Cleanup-Image /RestoreHealth

also fails, the next step depends on the DISM error.

A source-related DISM error is different from a storage error or component-store failure.

For example, if DISM returns 0x800f0915, use DISM Error 0x800f0915: How to Repair the Source Problem rather than continuing to repeat SFC.

The goal is to repair the Windows image first so SFC has a usable repair source.

When Malware Scanning Makes Sense

Malware is not my first assumption for this error.

But a full Microsoft Defender scan is reasonable when the SFC failure appears alongside signs such as:

• unknown startup programs
• security settings changing by themselves
• unexpected pop-ups
• unexplained browser redirects
• Windows Security being disabled
• unfamiliar processes repeatedly returning

Open:

Windows Security > Virus & threat protection > Scan options

Choose Full scan.

If the PC shows no other signs of malware, do not treat this step as mandatory.

When a Repair Reinstall Is Better Than More Commands

At some point, continuing to run DISM, SFC, CHKDSK, Safe Mode, and offline commands stops being productive.

A Windows 11 repair reinstall makes more sense when:

• DISM and SFC both repeatedly fail
• the component store remains damaged
• several Windows features are malfunctioning
• Windows Update is also broken
• offline SFC cannot repair the installation
• the same corruption quickly returns

Windows 11 now provides:

Settings > System > Recovery > Fix problems using Windows Update > Reinstall now

When available, this reinstalls the current Windows version while preserving files, apps, and settings.

For the full process, use Reinstall Your Current Version of Windows to Repair System Files.

That is usually a better escalation than immediately choosing Reset this PC or performing a clean installation.

What the Other Windows Resource Protection Messages Mean

It helps to separate this error from the other SFC results.

Windows Resource Protection did not find any integrity violations

SFC completed and did not detect damaged protected system files.

Windows Resource Protection found corrupt files and successfully repaired them

SFC completed and repaired the corruption.

Restart Windows and test the original problem again.

Windows Resource Protection found corrupt files but was unable to fix some of them

The scan completed, but some corruption remains.

DISM is the next logical step if you have not already run it.

Windows Resource Protection could not perform the requested operation

The scan itself could not complete.

That is the specific situation this article addresses.

Do Not Keep Repeating SFC Without Changing Anything

Running:

sfc /scannow

ten times does not solve the condition preventing SFC from operating.

A more useful sequence is:

DISM succeeds → run SFC again

If that fails:

Safe Mode → run SFC

If that fails:

check the drive and servicing state

Then:

offline SFC

And if Windows still cannot repair itself:

repair reinstall

The important part is changing the environment or repair source after each failure instead of repeating the same command and expecting a different result.