How to Fix “Windows Resource Protection Could Not Perform the Requested Operation”

Quick Answer

If SFC stops with “Windows Resource Protection could not perform the requested operation”, first open Windows Terminal or Command Prompt as administrator and run a disk check, then repair the Windows component store, and run SFC again.

chkdsk C: /scan
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

If the same error returns, boot into Safe Mode and run sfc /scannow again. If Windows still blocks the scan, run SFC offline from Windows Recovery Environment using the correct Windows drive letter.

Problem

The error “Windows Resource Protection could not perform the requested operation” appears when the System File Checker tool cannot complete its scan or repair operation.

You usually see it after running:

sfc /scannow

Instead of reaching 100%, the scan may stop early with the message:

Windows Resource Protection could not perform the requested operation.

This can happen on both Windows 11 and Windows 10, especially after failed updates, disk errors, interrupted repairs, damaged system files, or problems with the Windows servicing stack.

Cause

SFC depends on several Windows components to read protected system files and replace corrupted copies. If one of those components is unavailable, damaged, or blocked, SFC cannot finish the operation.

Prerequisites

• Use an administrator account.
• Connect your laptop to power before running repairs.
• Back up important files if the system drive has shown disk errors.
• Close open apps before running CHKDSK, DISM, or SFC.
• Make sure Windows has a stable internet connection for DISM online repairs.

Step-by-step Solution

1. Open Command Prompt or Terminal as administrator

1. Right-click the Start button.
2. Select Terminal (Admin) or Command Prompt (Admin).
3. Click Yes when User Account Control appears.

Now run the commands below in order. Do not close the window while a command is running.

2. Check the system drive for file system errors

Start with an online scan of the Windows drive:

chkdsk C: /scan

If CHKDSK reports problems that require an offline repair, run:

chkdsk C: /f

If Windows asks to schedule the repair at the next restart, type:

Y

Restart the PC and allow the disk check to complete. After Windows loads again, try SFC once more:

sfc /scannow

3. Repair the Windows component store with DISM

If SFC still shows “Windows Resource Protection could not perform the requested operation”, repair the Windows image:

DISM /Online /Cleanup-Image /RestoreHealth

Wait until DISM reaches 100%. It can pause for several minutes at certain percentages, which is normal.

After DISM finishes, run SFC again:

sfc /scannow

4. Run SFC in Safe Mode

Safe Mode loads Windows with minimal drivers and services, which helps when another process is interfering with SFC.

1. Press Windows + R.
2. Type msconfig and press Enter.
3. Open the Boot tab.
4. Check Safe boot and choose Minimal.
5. Click OK and restart.

After the PC starts in Safe Mode, open Command Prompt as administrator and run:

sfc /scannow

To exit Safe Mode, open msconfig again, uncheck Safe boot, and restart.

5. Check the Windows Modules Installer service

SFC relies on the Windows Modules Installer service, also known as TrustedInstaller. If it is disabled, repair operations can fail.

Run these commands in an elevated Command Prompt:

sc config trustedinstaller start= demand
net start trustedinstaller

If the service starts successfully, try:

sfc /scannow

6. Run SFC offline from Windows Recovery Environment

If Windows cannot complete SFC while running normally, use an offline scan from recovery mode.

1. Hold Shift and click Restart from the Start menu power options.
2. Go to Troubleshoot > Advanced options > Command Prompt.
3. Find the Windows drive letter. In recovery mode, it may not be C:.

Run:

bcdedit | find "osdevice"

If the result shows partition=C:, run:

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

If it shows another drive letter, replace C: with that letter. For example:

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

Restart the computer after the offline scan completes.

Examples

Example 1: Standard repair sequence

chkdsk C: /scan
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Use this when Windows boots normally but SFC fails before finishing.

Example 2: Offline SFC command

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

Use this from Windows Recovery Environment when normal and Safe Mode scans fail.

Common Causes

• Bad sectors or logical errors on the Windows partition.
• Interrupted Windows updates.
• Corrupted servicing files in the component store.
• Third-party antivirus or system tuning tools interfering with protected files.
• Disabled Windows Modules Installer service.
• Incorrect drive letter used during an offline SFC scan.

Common Mistakes

• Running Command Prompt without administrator rights: SFC repair commands need elevation.
• Closing DISM too early: DISM may look stuck, but it often continues in the background.
• Using C: automatically in WinRE: Windows may appear as D: or another letter in recovery mode.
• Skipping CHKDSK: If the file system is damaged, SFC may keep failing.
• Running random registry cleaners: They can make servicing problems worse.

Best Practices

• Run chkdsk before repeated SFC attempts if the scan fails early.
• Use DISM /RestoreHealth before SFC when system corruption is suspected.
• Keep at least 10 GB of free space on the Windows drive.
• Create a restore point before making major repair changes.
• Use offline SFC only after confirming the correct Windows drive letter.

Verification

The issue is fixed when SFC completes and shows one of these results:

Windows Resource Protection did not find any integrity violations.

or:

Windows Resource Protection found corrupt files and successfully repaired them.

You can also review the SFC log with:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfc-details.txt"

This creates an sfc-details.txt file on your desktop containing SFC-related entries from the CBS log.

FAQ