FIX: Windows Resource Protection Could Not Perform the Requested Operation in SFC /SCANNOW Command (Solved)
A few days ago I tried to repair a Windows 10 system, using the SFC /SCANNOW command in Windows Recovery Environment. But, after issued the command "SFC /SCANNOW", I received the error "Windows Resource Protection Could Not Perform the Requested Operation".
In this tutorial you'll find instructions on how to bypass error "Windows Resource Protection Could Not Perform the Requested Operation" when running the "SFC /SCANNOW" command from the Windows Recovery Environment (WinRE). *
How to FIX SFC Error "Windows Resource Protection Could Not Perform the Requested Operation" error in WinRE. *
* Note: If you receive the error when running the command from Windows GUI, restart Windows in Safe Mode and try again. If the problem persists, press the SHIFT key and click Restart to enter in WinRE mode and run the SFC command from there, by following the instructions below.
Method 1. Specify Boot & Windows Directories in SFC command.
Usually the error "Windows Resource Protection could not perform the requested operation" is due to the fact that the Offline Boot & Windows directories are not specified in the SFC command, as required if you are running the command from WinRE. So, to bypass the error apply the following steps:
1. At command prompt give the following command to find the drive letter of the OS partition:
- bcdedit
2. Notice the drive letter of OS partition (e.g. "osdevice –> partition=D: ")
3. Now give the following SFC command, where X is the drive letter you noticed.
4. SFC /SCANNOW /OFFBOOTDIR=X:\ /OFFWINDIR=X:\Windows
e.g. In this example the OS partition has the letter "D", so the command will be:
- SFC /SCANNOW /OFFBOOTDIR=D:\ /OFFWINDIR=D:\Windows
5. Normally now the sfc process will complete the process without the error "Windows Resource Protection Could Not Perform the Requested Operation".
Method 2. Clean Install Windows 10 & Check Hardware.
If the above method cannot resolve the discussed error this indicates that Windows System files are damaged. At this case, I suggest to backup your files and to perform a clean installation of Windows 10 or to RESET your PC. *
* Note: If you experience the same error after a clean install of Windows 10, this indicates a hardware problem. In this case, test the memory (RAM) for problems or try to install Windows on a new drive.
That's it! Which method worked for you?
Let me know if this guide has helped you by leaving your comment about your experience. Please like and share this guide to help others.
We're hiring
We're looking for part-time or full-time technical writers to join our team! It's about a remote position that qualified tech writers from anywhere in the world can apply. Click here for more details.
- FIX: Hyper-V did not find Virtual Machines to import from location. - September 3, 2024
- How to Move a Hyper-V Virtual Machine to another Host? - August 28, 2024
- How to Install Windows 11 in Hyper-V. - July 31, 2024
September 1, 2022 @ 7:25 pm
In "4. SFC /SCANNOW /OFFBOOTDIR=X:\ /OFFWINDIR=X:\Windows"
Windows should be all in lowercase. Is case sensitive.