sodcalculator

10 Tech How-To

Fix Windows Resource Protection Could Not Perform

Guide 10-57162 · Updated · Step by step

If you see “Windows Resource Protection could not perform the requested operation” when running sfc /scannow, it usually means System File Checker cannot start or finish because another program is locking system files, or the Windows Modules Installer service is disabled. The fix is to run SFC in Safe Mode, enable the Windows Modules Installer service, or use DISM to repair the system image first, then retry SFC.

What Causes This Error?

System File Checker (SFC) is a built-in Windows tool that scans protected system files and replaces corrupted ones. The error “Windows Resource Protection could not perform the requested operation” appears when SFC cannot access the files it needs to check. Common causes include:

  • Windows Modules Installer service (TrustedInstaller) is disabled or stopped – SFC depends on this service to repair files.
  • Another program is using system files – Antivirus software, backup tools, or even Windows Update running in the background can lock files.
  • Corrupted system image – If the component store (where Windows keeps clean copies of system files) is damaged, SFC cannot replace files.
  • Running SFC from an elevated command prompt incorrectly – You must run it as administrator; otherwise, you get a different error, but sometimes a non-elevated prompt can cause this message.
  • Disk errors – Bad sectors on the hard drive can prevent SFC from reading files.

How SFC Works and Why It Fails

SFC compares each protected file against a cached copy stored in the Windows component store (usually at C:\Windows\WinSxS). If a file is missing or modified, SFC replaces it with the cached version. The operation requires exclusive access to the file, which is why any process holding a lock can cause the “could not perform” error. Also, SFC uses the Windows Modules Installer service; if that service is not running, SFC cannot complete the repair.

Step-by-Step Fixes

Try these fixes in order. Most users resolve the issue with the first or second method.

1. Run SFC in Safe Mode

Safe Mode loads only essential drivers and services, so fewer programs can interfere with SFC. To boot into Safe Mode:

  1. Open Settings > System > Recovery (Windows 11) or Settings > Update & Security > Recovery (Windows 10).
  2. Under Advanced startup, click Restart now.
  3. After the PC restarts, choose Troubleshoot > Advanced options > Startup Settings > Restart.
  4. Press 4 or F4 to enter Safe Mode.
  5. Open Command Prompt as administrator (type “cmd” in Start, right-click, and select “Run as administrator”).
  6. Run sfc /scannow.

2. Enable Windows Modules Installer Service

If SFC still fails, check the service:

  1. Press Win + R, type services.msc, and press Enter.
  2. Scroll to Windows Modules Installer.
  3. Double-click it. If the service is stopped, set Startup type to Manual and click Start.
  4. Click Apply and OK.
  5. Run sfc /scannow again.

3. Run DISM First

If the component store is corrupted, SFC cannot repair files. Use Deployment Imaging Service and Management (DISM) to fix the store:

  1. Open Command Prompt as administrator.
  2. Run DISM /Online /Cleanup-Image /RestoreHealth.
  3. Wait for the process to complete (it may take 15–30 minutes).
  4. Restart your PC and run sfc /scannow again.

4. Check Disk for Errors

Run chkdsk /f /r to find and fix bad sectors. You will need to restart your PC to run the scan. After it finishes, retry SFC.

5. Use the Windows Update Troubleshooter

Sometimes Windows Update components are corrupted, causing SFC to fail. Go to Settings > System > Troubleshoot (or Update & Security > Troubleshoot in Windows 10), run the Windows Update troubleshooter, and then try SFC again.

What to Do If SFC Still Fails

If none of the above works, try these advanced options:

  • Run SFC with the /offbootdir and /offwindir parameters – This is useful if Windows cannot boot normally. Boot from a Windows installation USB, open Command Prompt (Shift+F10), and run: sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows (adjust drive letters as needed).
  • Use the Media Creation Tool to perform an in-place upgrade – This reinstalls Windows while keeping your files and apps. It can repair system files without losing data.
  • Check for pending reboots – If Windows is mid-update, restart and try again.

Common Misconceptions

Many users think SFC always fixes corrupted files, but it only works if the cached copy in WinSxS is intact. If the cache itself is damaged, SFC cannot help until you repair the component store with DISM. Also, SFC does not scan user data or third-party drivers; it only checks files that Windows protects. So even if SFC completes successfully, you may still have problems caused by drivers or apps.

Frequently Asked Questions

Does SFC require an internet connection?

No, SFC uses local cached copies of system files. However, DISM /RestoreHealth may download files from Windows Update if the local store is corrupted, so an internet connection is recommended for that step.

Can I run SFC while Windows is running normally?

Yes, you can, but it is more likely to fail because other programs are using system files. Running it in Safe Mode gives the best chance of success.

Will SFC delete my personal files?

No, SFC only replaces protected system files. It does not touch personal documents, photos, or installed applications.

How long does SFC take?

It typically takes 10–20 minutes, but it can take longer on slower drives or if many files need repair. Do not interrupt it; let it finish.

What is the difference between SFC and DISM?

SFC checks and repairs individual system files. DISM repairs the underlying system image (the component store) that SFC uses as a source. Running DISM first can fix SFC errors caused by a corrupted store.

Can I use SFC on Windows 11?

Yes, SFC works the same on Windows 10 and Windows 11. The commands and troubleshooting steps are identical.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →