Skip to content

Published: June 13, 2015 | Applies to:

If the SFC dependency services are not running, you may receive "Windows Resource Protection could not perform the requested operation" error, fix it here.

We have already seen that there are various scenarios where we can employ System File Checker (SFC) to repair our Windows running system, in following article:

[How To] Use System File Checker To Repair Windows

In that article, we have quoted that in some cases the SFC wouldn’t intiate a scan if it’s dependency resources are unavailable or not working. When your run the scan through SFC, if you check the task manager, you’ll find that some services are running with high CPU and memory usage. These are the dependency services for SFC.

Well, if these services are not working properly, the scan would not start and you may receive one of these errors:

Windows Resource Protection could not perform the requested operation.

or

Windows Resource Protection could not start the repair service.

FIX Windows Resource Protection Could Not Perform The Requested Operation

An easy and straightforward solution to this to use the alternative option. That’s is you can scan the system with DISM commands, especially commands 1 and 2 mentioned in following article:

[FIX] Repair Your Windows 8 Using DISM Commands

Although, if you want to scan your system only with SFC, you can make the cross checks to confirm that dependency services for SFC are working properly. If they are disabled, do enable them, so that scan can be initiated:

FIX : Windows Resource Protection Could Not Perform The Requested Operation

1. Press  W8K + R and type services.msc in the Run dialog box, hit Enter key to open Services snap-in.

2. Moving on, in the Services window, scroll down and look for the Windows Module Installer service. Since you’re facing this issue, the service will most probably be Disabled. Double click on the service to open its Properties.

FIX Windows Resource Protection Could Not Perform The Requested Operation

3. Finally, in the Properties window shown below, set the Startup type to Manual. Also click Start button to let the service running for while. Click Apply followed by OK. Close Services snap-in.

FIX Windows Resource Protection Could Not Perform The Requested Operation

Now initiate the SFC scan and this time it would run as expected. After the scan completed, reboot the machine. After restarting computer, the service may not be running (and it shouldn’t be) but it should be set to Manual start.

Hope this helps! Learn how to create a System Restore point before installing a software in Windows.


SHARE: Facebook Google+ Twitter

3 Comments

  • Windows Modules Installer is up and running, tried to reinstall via ISO but that says it will delete all my files and settings. sfc keeps complaining about Windows Resource Protection at the very start.

    Tried to start in safe mode, but that’s completely unstable. The screen keeps flashing and doesn’t react to commands except ctrl+alt+del

  • Kapil Arya

    ^^ See if you can run DISM commands mentioned here:

    http://www.kapilarya.com/fix-do-inbox-corruption-repair-using-dism-in-windows-8

  • I followed your tips, Windows Module Installer is running but sfc still returns an error: repair service could not be started. Are there other dependencies, or does the WMI have dependencies that might prevent operation?

  • Leave a Reply

    Your email address will not be published. Required fields are marked *

    What's New


    Recent Comments

    • Kapil Arya : ^^ Happy to help ☺️...

      1 hour ago

    • frozen nerd : i also tried uninstalling avast, disabling all startup progr...

      5 hours ago

    • frozen nerd : i have a win 10 home OEM from ASUS tried this and got the ...

      5 hours ago

    • Darren : Thank you, Kapil! The first two netsh commands and reboot ju...

      7 hours ago

    • Charles : I followed your steps but got stuck at step 9 since I couldn...

      12 hours ago

    • Barry : Fantastic! You solved my problem with very clear instruction...

      13 hours ago


    Windows Group Policy Troubleshooting