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

Running the built-in System File Checker command (sfc /scannow) in an elevated Command Prompt is standard procedure to repair corrupted system files in Windows 11. However, instead of scanning through 100% verification, the utility may terminate prematurely—often at 4% or 23%—with the frustrating notification: “Windows Resource Protection could not perform the requested operation”.

When this error strikes, Windows Resource Protection (WRP) has encountered a file-system-level obstruction that prevents it from accessing the Windows component store located in %windir%\WinSxS. The failure is typically triggered by pending disk write transactions, corrupted access permissions on the WinSxS directory, active file locks held by third-party antivirus suites, disk bad sectors, or a stalled Windows Modules Installer service (TrustedInstaller). Follow this structured troubleshooting guide to bypass the block and complete your system file repairs.

Method 1: Run SFC in Windows 11 Safe Mode

Third-party security software, background cloud syncing daemons, and low-level system drivers can lock core Windows DLL files, preventing the SFC tool from reading or replacing them. Running the scan inside Safe Mode disables all third-party services.

1. Press Windows + R, type msconfig, and press Enter to open System Configuration.
2. Select the Boot tab.
3. Under Boot options, check the box labelled Safe boot and leave Minimal selected.
4. Click Apply, followed by OK, and click Restart.
5. Once Windows boots into Safe Mode, press the Windows key, type cmd, and click Run as administrator.
6. In the elevated terminal, execute the scan:

   sfc /scannow

7. Safe Mode eliminates file contention locks, allowing SFC to complete through 100% verification.
8. Once finished, open msconfig again, uncheck Safe boot, and restart to return to normal Windows.

Method 2: Check and Repair File System Errors via CHKDSK

If your hard drive or SSD has bad sectors or broken Master File Table (MFT) allocation pointers on the system partition, SFC cannot navigate the component directory and halts with the resource protection error.

1. Open Command Prompt as Administrator.
2. Execute Check Disk on your Windows system partition:

   chkdsk C: /f /r

3. Command Prompt will inform you that the volume cannot be locked and ask: “Would you like to schedule this volume to be checked the next time the system restarts? (Y/N)”.
4. Type Y and press Enter.
5. Restart your computer. Windows will perform a thorough sector audit during the boot sequence before loading the desktop.
6. Once booted back into Windows, open elevated Command Prompt and retry sfc /scannow.

Method 3: Clear the WinSxS PendingDeletes and PendingRenames Folders

When Windows Update stages file changes, it creates temporary entries in the WinSxS component store. If an update was interrupted, orphaned lock files prevent the WRP engine from modifying files.

1. Open elevated Command Prompt as Administrator.
2. Navigate to the WinSxS temporary transaction folder:

   cd %windir%\WinSxS\Temp

3. Take ownership and reset access permissions on pending deletion directories:

   takeown /f PendingDeletes
   icacls PendingDeletes /grant administrators:F

4. Alternatively, boot into Safe Mode and manually inspect C:\Windows\WinSxS\Temp\. Delete any folders named PendingDeletes or PendingRenames.
5. Restart Windows and test the SFC scan.

Method 4: Verify and Restart the Windows Modules Installer Service

The System File Checker operates under the administrative authority of the TrustedInstaller account, governed by the Windows Modules Installer service. If this service is disabled, SFC cannot perform operations.

1. Press Windows + R, type services.msc, and press Enter.
2. Scroll down to locate Windows Modules Installer.
3. Double-click the service to view its properties.
4. Ensure the Startup type is set to Manual or Automatic (do not leave it Disabled).
5. If the service status shows Stopped, click the Start button.
6. Click Apply and OK.
7. Run sfc /scannow again in elevated Command Prompt.

Windows Resource Protection Diagnostics Reference Table

Use the matrix below to assess SFC execution failures and targeted remedies:

Observed SFC Failure Point	Underlying Root Cause	Recommended Solution
Scan fails at 0% or 4% verification	Windows Modules Installer service stopped or disabled	Start Windows Modules Installer in services.msc
Scan fails at 20% to 50% verification	Third-party antivirus locking DLL files in memory	Boot into Safe Mode (msconfig) and re-run SFC
Error accompanied by disk read clicking / lag	Physical bad sectors on primary drive (C:)	Execute chkdsk C: /f /r & inspect drive S.M.A.R.T. health
SFC reports “Pending system repair required”	Interrupted Windows update staged in WinSxS	Reboot PC twice, or execute DISM /RevertPendingActions
Error persists in Safe Mode	Corrupted Windows Component Store (WinSxS)	Run DISM /Online /Cleanup-Image /RestoreHealth first

Repairing the Component Store with DISM Prior to SFC

If the Windows Component Store itself is corrupted, System File Checker lacks verified reference files to replace broken components. Prior to running SFC, execute the Deployment Image Servicing and Management repair tool: DISM /Online /Cleanup-Image /RestoreHealth. Allow DISM to connect to Microsoft’s cloud servers, download uncorrupted component binaries to WinSxS, and reach 100% completion. Once DISM finishes successfully, running sfc /scannow will complete smoothly without resource protection errors.