Whenever you run SFC (System File Checker), does the process stop in the middle and give you this error “Windows Resource Protection could not perform the requested operation”? So don’t worry, in this guide we are going to fix this problem In no time, follow the following steps.
This anomalous error has everyone scratching their heads. How do you run diagnostics on a diagnostic tool? Let’s find out. Windows Could Not Perform The Requested Operation / SOLUTION
What is Windows Resource Protection?
The Windows Resource Protection (WRP) is a Windows feature that protects essential system files, folders and registry keys from being replaced. Protect these components to avoid failures in applications and the operating system.
Read:
Why do I get the error Windows Resource Protection could not perform the requested operation when running the SFC command?
- Damaged, corrupt or missing files
- SFC cannot access folder winsxs
- Damaged hard drive partition
- Corrupted Windows files
- Incorrect system architecture
Fix “Windows Resource Protection could not perform the requested operation”
Fortunately, there are a couple of easy ways to put your dilemma to rest. Therefore, let’s solve and fix each of these points individual. Once this is done, hopefully you have gotten rid of the error.
Read Also
1. Use the CHKDSK tool
What better way to fix a diagnostic tool than with another diagnostic tool? The tool CHKDSK It will help you check the status of your hard drive. If the tool finds any errors on the disk, you will know what is causing the problem with the scan CFS.
Press Win+Rwrites cmdand press Ctrl + Shift + Enter to launch an elevated command prompt. Run the following command:
chkdsk /r
You may see a message saying that you need to schedule the disk check since the volume is in use by another process. Press AND to schedule the disk check the next time you restart your computer.
Restart your computer and the CHKDSK tool will now fix any disk errors your system may have. Once it has completed, try running the command again sfc /scannow.
2. Use the SFC tool in safe mode
If the previous method has not worked for you, some system component may be conflicting with the tool CFS. First of all, try to run the command sfc /scannow in safe mode to see if the problem is resolved.
Read Also
Press Win+Rwrites msconfig and press Enter. This should launch the System configuration. Switch to tab boots and look for the boot options at the bottom left of the window.
Check the box next to Secure Boot and select the radio button next to Minimum. Press okay and restart your PC.
This should help you boot into Sade mode with only the essential processes running. Try running the command now sfc /scannow and check if it works.
3. Use the SFC tool in Windows RE
If for some reason you don’t want to boot into the Safe Modeyou can also use Windows Recovery Environment to run the SFC tool without running any conflicting items.
To enter Windows RE, you will have to go to the Settings app. Press Win + I and navigate to Update recovery. In the right panel, click the button Restart now under advanced startup. The computer will reboot and enter Windows RE.
Read Also
Once you are in Windows RE, navigate to Troubleshooting > Advanced Options > Command Prompt. Run the command CFS now and see if the command is executed successfully.
4. Enable Windows Modules Installer
The service TrustedInstaller must be running on your system so that you can restore the resources of WRP missing or corrupted files, as you have full access to the WRP files and registry keys. When you run the SFC tool, the service is activated. However, if you have disabled the service, you might encounter the aforementioned error.
To check if the Installer Windows modules is disabled, you will have to visit the console Services.
Press Win+Rwrites services.msc and press Enter to start the Services console. Find the Windows Modules Installer and double-click it to open the service properties.
Check the startup type of the service. If it is disabled, change it to manual and press Accept.
Read Also
Try running the command now sfc /scannow to see if the problem persists.
5. Perform an automatic repair
At this point, you may want to consider performing a auto repair to carry out a thorough check for anything that is not working as it should on your system.
Automatic repair does not delete any files or revert any settings to default values, so if it does not find anything that needs fixing, it will leave the system as it was before the scan.
If it finds something that needs fixing, it will automatically repair it or notify you that it couldn’t be fixed. . In any case, it is worth a try if none of the above options have worked.
To perform an automatic repair, boot into the Recovery Environment Windows (as illustrated in the third fix) and navigate to Troubleshoot > Advanced Options > Automatic Repair.
Read Also
Once the process starts, let it run.
If Automatic Repair fixes the problem, try running the command CFS after a reboot. However, if no problem was found or Windows RE was unable to fix the problem, you may consider the last resort.
6. Reinstall Windows
Hopefully now you can run the command sfc /scannow No problem. If you can’t, you can consider reinstall windows again. It’s a radical step, of course, but if you’ve wanted to do it for a while, now would be a good time.
You’ll have a fresh copy of Windows if you do this, however since you already have access to the operating system, consider backing up your computer so you don’t have to spend a lot of time putting everything back together from scratch after reinstalling Windows. .
Can you run ScanNow now?
If you encounter the dreaded error “Windows Resource Protection could not perform the requested operation” when using /sfc scannow, it can be a confusing task to solve. Hopefully the tips above help you get your problem solver in shape.
Read Also
If you want to know other articles similar to How to Fix “Windows Resource Protection Could Not Perform the Requested Operation” Error you can visit the category.
Facebook Comments
Disqus