sodcalculator

10 Tech How-To

Fix Windows Resource Protection Cannot Perform Requested Operation

Guide 10-44407 · Updated · Step by step

If you see “Windows Resource Protection could not perform the requested operation” when running sfc /scannow, the fix is usually to boot into Safe Mode or run the command from Windows Recovery Environment, then try again. This error appears when System File Checker cannot access the protected system files it needs to verify, often because they are locked by the running OS or another process. Below is a complete guide to resolving it, with background on why it happens and step-by-step fixes.

What Does This Error Actually Mean?

System File Checker (SFC) is a built-in Windows utility that scans protected system files and replaces corrupted ones with cached copies. When it reports “Windows Resource Protection could not perform the requested operation,” it means SFC could not even start the scan properly. The most common cause is that the Windows Resource Protection (WRP) service—which protects system files and registry keys—cannot access the files because they are in use by the operating system itself. This is a known limitation of running SFC in normal mode on a live system, especially on Windows 8 and later versions where more system files are locked.

Other triggers include a pending reboot (often after a Windows update), a corrupted Windows Update cache, or a damaged system image that prevents SFC from reading the necessary files. The error is not a sign of a deeper hardware problem; it is almost always a software access issue that can be resolved with the right boot environment.

Why Does SFC Fail in Normal Mode?

Windows Resource Protection is designed to prevent unauthorized changes to critical system files. When you run SFC in normal mode, the operating system is actively using those files, so WRP cannot lock them for scanning. This is especially true for files like ntoskrnl.exe, winload.exe, and many DLLs that are loaded into memory at boot. SFC needs exclusive read access to compare file hashes, and if a file is in use, it cannot open it, leading to the “cannot perform the requested operation” message.

In Windows 7 and earlier, SFC was often able to work around this by using a different API, but modern Windows versions are stricter. The recommended workaround is to run SFC from an environment where the main OS is not running, such as Safe Mode or the Windows Recovery Environment (WinRE). In Safe Mode, only essential drivers and services load, so most system files are not locked. In WinRE, the OS is not running at all, giving SFC full access.

Fix 1: Run SFC in Safe Mode

Safe Mode is the easiest first step because it does not require installation media. Here is how to do it:

  1. Open Settings > System > Recovery (Windows 11) or Update & Security > Recovery (Windows 10).
  2. Under Advanced startup, click Restart now. (If you cannot get into Windows, restart your PC and press F8 repeatedly during boot, or use the power button to interrupt startup three times to trigger WinRE.)
  3. In the blue menu, choose Troubleshoot > Advanced options > Startup Settings > Restart.
  4. After the restart, press 4 or F4 to enter Safe Mode.
  5. Once in Safe Mode, open Command Prompt as administrator (right-click Start and select “Command Prompt (Admin)” or “Terminal (Admin)”).
  6. Type sfc /scannow and press Enter.

If SFC runs without the error, let it complete. It may take 10–15 minutes. If it finds and repairs files, restart normally and run sfc /scannow again in normal mode to confirm the fix.

Fix 2: Use Windows Recovery Environment (WinRE)

If Safe Mode still shows the error, or if you cannot boot into Safe Mode, use the Windows Recovery Environment. This is the most reliable method because the main OS is not running.

  1. Boot from a Windows installation USB or recovery drive. If you do not have one, create a bootable USB using the Media Creation Tool from Microsoft’s website (you will need another PC).
  2. On the first screen, click Next, then click Repair your computer at the bottom left.
  3. Choose Troubleshoot > Advanced options > Command Prompt.
  4. In the Command Prompt, you need to find the drive letter of your Windows installation. Often it is C:, but in WinRE it might be D: or another letter. Type dir C:\Windows to check. If it says “file not found,” try D:\Windows, E:\Windows, etc.
  5. Once you locate the correct drive letter (say it is C:), run the following command:
    sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

The /offbootdir and /offwindir flags tell SFC where the boot files and Windows directory are. This is the standard way to run SFC offline. If the scan finds issues, it will attempt to repair them using the local cache. If it cannot repair some files, you may need to run DISM first (see below).

Fix 3: Run DISM to Repair the System Image

Sometimes the “cannot perform the requested operation” error is caused by a corrupted system image, which prevents SFC from accessing the source files it needs. In that case, you should run the Deployment Imaging Service and Management (DISM) tool to repair the image before running SFC again.

  1. Open Command Prompt as administrator (in normal mode, Safe Mode, or WinRE).
  2. Run this command to check the health of the system image:
    DISM /Online /Cleanup-Image /CheckHealth
  3. If it reports issues, run:
    DISM /Online /Cleanup-Image /RestoreHealth
  4. Wait for the process to complete (it can take 20–30 minutes). It uses Windows Update to download healthy files.
  5. After DISM finishes, run sfc /scannow again.

If you are in WinRE and cannot use the /Online flag, you can point DISM to an install.wim file from your installation media. The command would be:

DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim

Replace C: with your Windows drive and D: with the drive letter of your USB. This is advanced, but it is a common fix when the online repair fails.

Fix 4: Check for Pending Reboots and Clear Update Cache

A pending reboot—especially after a Windows update—can lock system files and cause SFC to fail. Before trying more drastic measures, do the following:

  • Restart your PC normally and let any pending updates finish installing.
  • If you have just installed updates, wait a few minutes after boot and then try SFC again.
  • Clear the Windows Update cache. Open Command Prompt as admin and run:
    net stop wuauserv
    net stop bits
    ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
    net start wuauserv
    net start bits
  • Then restart and try SFC again.

This step is often overlooked, but a stuck update can cause exactly this error.

What to Do If SFC Still Fails

If you have tried Safe Mode, WinRE, DISM, and clearing the update cache, and SFC still reports the error, the issue may be deeper. Here are a few final options:

  • Check disk errors: Run chkdsk /f /r from an elevated Command Prompt. This will schedule a check on restart. Disk errors can prevent SFC from reading files.
  • Repair install: Use the “Reset this PC” feature or an in-place upgrade repair using the Media Creation Tool. This reinstalls Windows while keeping your files and apps. It is more thorough than SFC and will replace corrupted system files.
  • Check system drive space: SFC needs free space to create temporary files. Ensure you have at least 10% of your drive free.
  • Run SFC from a different account: If your user profile is corrupted, create a new local administrator account and try SFC from there.

If none of these work, the problem might be failing hardware (especially RAM or hard drive). Run a memory diagnostic (Windows Memory Diagnostic) and check the drive’s SMART status.

Frequently Asked Questions

Why does SFC say “Windows Resource Protection could not perform the requested operation” even in Safe Mode?

Even in Safe Mode, some system files may still be locked by essential services. Also, if the system image is corrupted, SFC may not be able to access the source files. In that case, run DISM first, then SFC. If it still fails, use WinRE with the /offbootdir and /offwindir flags.

Can I run SFC from a command prompt at boot without installation media?

Yes, you can access WinRE by restarting while holding Shift and clicking Restart, or by interrupting the boot three times. From there, you can open Command Prompt and run SFC with the offline flags, as described in Fix 2.

Will running SFC in Safe Mode fix my problem?

It often does. Safe Mode loads minimal drivers, so most system files are not locked. If the error is due to file access, Safe Mode will allow SFC to run. If the error persists, it is more likely a corrupted system image, which requires DISM.

Is it safe to run DISM /RestoreHealth?

Yes. DISM is a built-in Windows tool that repairs the system image using files from Windows Update or a local source. It does not affect your personal files. It can take a while, but it is safe to run.

What does the “/offbootdir” and “/offwindir” flag do?

These flags tell SFC where the boot files and Windows directory are located when you are running it from WinRE. Because the drive letters in WinRE can differ from normal Windows, you must specify the correct paths. For example, if your Windows is on D: in WinRE, you would use /offbootdir=D:\ /offwindir=D:\Windows.

Can I fix this without a Windows installation USB?

Yes, if you can boot into Safe Mode or WinRE from the hard drive. WinRE is built into Windows and can be accessed without external media. If you cannot boot at all, you will need installation media to access the recovery environment.

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 →