Fix “Windows Resource Protection could not perform the requested operation.”
Windows includes a useful system repair tool called System File Checker, commonly known as SFC. It scans protected Windows system files and attempts to replace corrupted or missing files with a cached copy. You normally run it by opening Command Prompt as an administrator and entering the sfc /scannow command.
However, sometimes the scan does not complete, and Windows displays the following message:
“Windows Resource Protection could not perform the requested operation.”
This usually means that SFC was unable to complete its repair or verification process. The problem can be related to corrupted Windows components, problems with the file system, a service or file that is preventing SFC from working correctly, or an issue that disappears when Windows starts with only essential components.
Let’s learn the process to get rid of this message!
Fix “Windows Resource Protection could not perform the requested operation.”
To fix “Windows Resource Protection could not perform the requested operation,” first restart your computer and run DISM /Online /Cleanup-Image /RestoreHealth from an elevated Command Prompt. After DISM finishes, run sfc /scannow again. If the same error appears, start Windows in Safe Mode and run SFC there. If the scan still fails, check the drive for file-system errors with CHKDSK and then try SFC again. Microsoft specifically recommends Safe Mode for this SFC error.
Let’s explore the steps in detail!
Step 1: Restart Your Windows PC
Before changing any system settings, restart your computer.
A restart is useful because Windows may have temporary files, pending operations, or system processes that are interfering with the SFC scan. Close any programs you are currently using, select Start, select the Power button, and then choose Restart.
After Windows starts again, do not immediately open several applications. Instead, go directly to the next step and try repairing the Windows component store.
If you have unsaved work, save it before restarting.
Step 2: Run DISM to Repair the Windows Image
The next step is to use DISM, which stands for Deployment Image Servicing and Management.
Think of DISM as a repair tool for the Windows image that SFC depends on. Microsoft recommends running DISM before SFC when Windows system files need repair.
First, select the Start button and type Command Prompt. When Command Prompt appears in the search results, right-click it and select Run as administrator.
Windows may display a User Account Control window asking whether you want to allow the application to make changes. Select Yes.
In the administrator Command Prompt window, type the following command:
DISM.exe /Online /Cleanup-Image /RestoreHealth
Press Enter.
DISM will begin checking the Windows image and attempting to repair problems. The process can take some time, so do not close the Command Prompt window while it is working.
When the operation finishes successfully, restart your computer.
Step 3: Run SFC Again
After restarting Windows, try the SFC scan again.
Open Command Prompt as administrator using the same method described in the previous step.
Type:
sfc /scannow
Press Enter.
You should see a message saying that the system scan is beginning. The verification percentage will gradually increase.
Do not close Command Prompt while the scan is running. Microsoft advises waiting until the verification reaches 100 percent before closing the window.
If SFC completes successfully, read the final message. Windows may report that it found no integrity violations, repaired corrupted files, or found corrupted files that it could not repair.
If you again receive “Windows Resource Protection could not perform the requested operation,” continue to the next step.
Step 4: Start Windows in Safe Mode
If SFC cannot complete normally, Microsoft’s guidance for this specific error is to run the scan in Safe Mode. Safe Mode starts Windows with a limited set of files, drivers, and services. This can prevent another program or service from interfering with SFC.
To enter Safe Mode in Windows 11, open Settings and select System. Select Recovery, find Advanced startup, and select Restart now.
Windows will restart and display a recovery screen.
Select Troubleshoot, followed by Advanced options, and then Startup Settings. Select Restart.
After the computer restarts again, you will see several startup options. Select the option for Enable Safe Mode, usually by pressing 4 on the keyboard.
Windows will now start in Safe Mode.
Do not worry if the desktop looks different or the screen resolution changes. That is normal in Safe Mode.
Step 5: Run SFC in Safe Mode
Once you are inside Safe Mode, open the Start menu and search for Command Prompt.
Right-click Command Prompt and select Run as administrator.
Type:
sfc /scannow
Press Enter.
Wait for the scan to reach 100 percent.
Running SFC in Safe Mode is particularly important for this error because Microsoft specifically lists Safe Mode as the next troubleshooting step when SFC reports that Windows Resource Protection could not perform the requested operation.
If SFC completes successfully in Safe Mode, restart the computer normally and check whether the original problem has disappeared.
If the same error still appears, continue with the next step.
Step 6: Check the Windows Drive for File-System Errors
A problem with the file system can also interfere with Windows repair operations. Windows provides another command called CHKDSK for checking a drive for file-system problems.
Exit Safe Mode and start Windows normally if possible.
Open Command Prompt as administrator and enter:
chkdsk C: /f
Press Enter.
If Windows tells you that the drive is currently being used and asks whether you want to schedule the check for the next restart, type:
Y
and press Enter.
Restart your computer.
Windows can then perform the disk check before the normal desktop loads. Allow the process to finish.
The time required can vary depending on the condition and size of the drive.
After Windows starts normally, try the SFC command again:
sfc /scannow
If Windows is experiencing broader storage problems, make sure important personal files are backed up before performing extensive disk repairs.
Step 7: Check the Windows Installer Modules Service
SFC relies on Windows servicing components. If the required Windows servicing infrastructure is not functioning correctly, SFC may have trouble completing.
One service worth checking is Windows Modules Installer, also known as TrustedInstaller.
Press Windows + R to open the Run dialog box.
Type:
services.msc
Press Enter.
The Services window will open. Find Windows Modules Installer in the list.
Double-click it.
Look at the Startup type. Do not randomly disable or modify other Windows services. The Windows servicing environment is important for system repair operations.
If the service is stopped and Windows provides a Start option, select it.
Then close the Services window and try sfc /scannow again from an administrator Command Prompt.
Step 8: Run DISM and SFC in the Correct Order Again
If you have reached this point, run the repair sequence once more.
Open Command Prompt as administrator.
First enter:
DISM.exe /Online /Cleanup-Image /RestoreHealth
Wait for the operation to finish.
Then enter:
sfc /scannow
The order is important because DISM can repair the Windows image that SFC uses when repairing protected system files. Microsoft’s documented repair process places DISM before SFC.
Do not close Command Prompt until both operations have finished.
Step 9: Try an Offline SFC Scan if Windows Cannot Repair It Normally
If SFC continues to fail even after Safe Mode and disk checking, the problem may require an offline repair.
This is more advanced because Windows may use a different drive letter when you are working from the Windows Recovery Environment. For example, the Windows installation that normally appears as C: could appear as another letter in the recovery environment.
For that reason, beginners should avoid randomly replacing drive letters in offline SFC commands.
If you reach this stage and Windows is also experiencing startup, update, or recovery problems, first back up important personal data. An offline repair can then be performed using the correct Windows installation drive and the appropriate /offbootdir and /offwindir parameters. Microsoft Q&A documentation demonstrates this approach for Windows Recovery Environment scenarios.
Step 10: Consider a Windows Repair Installation
If SFC, DISM, Safe Mode, and disk checking do not resolve the problem, the Windows installation itself may have deeper component or servicing corruption.
At this stage, a Windows repair installation, also called an in-place upgrade repair, may be appropriate. This can reinstall Windows system components while retaining personal files and, depending on the method and configuration, installed applications.
Do not jump directly to a clean installation unless necessary. A clean installation can remove applications and personal data, so it should be approached carefully and only after important files have been backed up.
For persistent corruption, Microsoft documentation also describes using an appropriate repair source with DISM when the normal online repair source cannot provide the required files.
Faqs
What does “Windows Resource Protection could not perform the requested operation” mean?
It means that System File Checker could not complete the requested operation. It does not necessarily mean that every Windows system file is corrupted. The failure can have several causes, which is why Microsoft recommends trying the SFC scan in Safe Mode for this particular message.
Can I fix this error without reinstalling Windows?
Yes. You can first try DISM, SFC in Safe Mode, and CHKDSK. Many SFC problems can be addressed without performing a clean Windows installation.
Should I run DISM before SFC?
Yes. Microsoft’s documented repair process recommends running DISM.exe /Online /Cleanup-Image /RestoreHealth and then running sfc /scannow.
How long does SFC take?
There is no single fixed duration. The scan can take several minutes or longer depending on the computer and the condition of Windows. Let the scan reach 100 percent rather than closing Command Prompt because it appears to be taking a long time.
What if SFC works in Safe Mode but not normal Windows?
That usually indicates that something loaded during normal Windows startup may be interfering with the operation. Restart normally and check whether the underlying Windows problem has also been resolved. If the SFC error returns, additional troubleshooting of startup software and Windows components may be necessary.
What if DISM also fails?
If DISM /RestoreHealth fails, note the exact error code and message rather than repeatedly running random repair commands. The appropriate next step depends on the error. In some cases, DISM may need a valid repair source instead of its normal online source.
Will running SFC delete my personal files?
SFC is designed to scan and repair protected Windows system files. It is not a personal-file deletion tool. However, it is always sensible to keep a current backup of important documents, photos, and other personal data before performing extensive system troubleshooting.
Summary
The “Windows Resource Protection could not perform the requested operation” message means that SFC could not finish its system-file operation.
Start with the simplest approach. Restart Windows, run DISM /Online /Cleanup-Image /RestoreHealth, and then run sfc /scannow again. If the error remains, start Windows in Safe Mode and run SFC there. Microsoft specifically recommends Safe Mode when SFC displays this particular message.
If SFC still cannot complete, check the Windows drive with CHKDSK and repeat the repair sequence. For persistent problems, investigate the exact DISM or SFC error and consider an appropriate Windows repair installation rather than immediately performing a clean installation.
The most important thing for a very new Windows user is to follow the commands exactly as written, wait for each repair process to finish, and avoid changing unrelated system settings while troubleshooting.