Monday, April 1, 2013

How to Fix "Windows Resource Protection could not Start the Repair Service" Error - Windows 7

Fix "Windows Resource Protection could not Start the Repair Service" Error

We have a solution of How to Repair System files by scan in Windows 7 using the "sfc" command. But unfortunately if you got "Windows Resource Protection Could not Start the Repair Service" error when trying to perform the above action, you have to fix it.

Cause of the error is that Windows Modules Installer service has been disabled on your system.
You just need to enable this.



Lets do it :

1. Type Services in Start menu search box and hit enter.


2. At services window select services(Local) section from the left panel.

3. Locate the service named Windows Modules Installer and Double-click on it.


4. Set the Startup type to Manual.


5. Click Apply and Ok to make the change.

6. Now follow the How to Repair System files by scan in Windows 7 steps to fix your system files.

24 comments:

  1. If this doesn't work, then go to C:\Windows\System32 and you will see the cmd.exe file there. Right click on it & run as administrator. It should run from there. Why it doesn't run from elsewhere who knows! Good Luck!

    ReplyDelete
    Replies
    1. This works for me ! Thanks! I can't understand why...

      Delete
    2. Thanks!! After having tried many options found on internet...it worked for me!!!! Thanks!!!

      Delete
    3. Rock on, man. I consider myself a pro and I laughed at this thinking... no way. But you are absolutely right! Thank you!!

      Delete
  2. THANKYOU THANKYOU THANKYOU!!

    ReplyDelete
  3. Thank you VERY Much....it worked instantly

    ReplyDelete
  4. I get this error (Windows Resource Protection could not Start the Repair Service) however, the indicated process is already running and NOT disabled. This is not the issue in my case.

    ReplyDelete
  5. 10ks it sure helped

    ReplyDelete
  6. Seeing as Windows Module Installer was already on manual, this wasnt helpful in my case.

    ReplyDelete
  7. Thank you! It works for me!!!

    ReplyDelete
  8. Did not work for me either, yet no help for us!!!

    ReplyDelete
  9. Yes, running the "cmd.exe" from within "c:\windows\system32" works as expected, while running it from the "Star menu" item for the command prompt does not.

    This, clearly, is a case of the so-called "enhanced security" which Microsoft keeps adding in, in order to patch over gaping holes in the system design. A properly designed OS would not require blocking off of system functions to "block attacks," because those system functions would not be suscepible in the first place.

    So, he have yet another 'bandaid" within Windows which, far from making the systems "more secure," makes it far harder to maintain a system in proper functional order. Yay, Microsoft... yet again. (sigh)

    ReplyDelete
    Replies
    1. Worked for me..Mine was in Manual mode..Switched it to "disable" "Apply" back to "Manual" Apply...OK...end Ron

      Delete
  10. Seeing as Windows Module Installer was already on manual, this wasnt helpful in my case.

    ReplyDelete
  11. It’s a Fantatsic blog . this blog helps you for any kind of windows7 error . we provide best services for your any type of windows 7 error . go through this site .
    error 1068 windows7
    Thank you
    Aalia lyon

    ReplyDelete
  12. Wow thank you! Microsoft support wanted $100 to "fix it" I appreciate your forum. Kudos for your help

    ReplyDelete
  13. This is very very helpful, thanks.

    ReplyDelete
  14. This was quite helpful, thank you.

    ReplyDelete
  15. I have no Windows Modules Installer service. I have the TrustedInstaller.exe file where it belongs, but System File Checker, Internet Explorer, and Windows Updates (WUSA) are ALL disfunctional. If you have any suggestions it would be most appreciated! Thanks!!

    ReplyDelete
    Replies
    1. Randy, I have the EXACT same issue as your. Did you find a fix?

      Delete