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.

33 comments:

  1. AnonymousJuly 15, 2013 at 4:31 AM

    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. AnonymousNovember 4, 2013 at 2:57 PM

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

      Delete
    2. AnonymousJune 1, 2014 at 10:58 AM

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

      Delete
    3. AnonymousJuly 15, 2014 at 7:18 AM

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

      Delete
    4. AnonymousAugust 19, 2014 at 3:17 PM

      You could also just type CMD in the start menu search and right click > run as administrator from there, no need to go delving into the system32 folder.

      Delete
    5. AnonymousAugust 29, 2014 at 2:23 AM

      This is strange! Anyways, thanks a lot!!

      Delete
    6. AnonymousMarch 23, 2015 at 8:28 PM

      Thank you that work for me to. On windows 8.1.

      Delete
    7. AnonymousSeptember 13, 2015 at 2:11 AM

      Thanks man!

      Delete
  2. AnonymousJuly 23, 2013 at 10:54 PM

    THANKYOU THANKYOU THANKYOU!!

    ReplyDelete
  3. AnonymousAugust 6, 2013 at 12:26 AM

    Thank you VERY Much....it worked instantly

    ReplyDelete
  4. AnonymousAugust 13, 2013 at 6:14 AM

    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. AnonymousAugust 22, 2013 at 10:25 AM

    10ks it sure helped

    ReplyDelete
  6. kamzherNovember 16, 2013 at 4:21 AM

    It works!!! THANK YOU

    ReplyDelete
  7. AnonymousNovember 22, 2013 at 2:44 AM

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

    ReplyDelete
  8. AnonymousNovember 25, 2013 at 6:49 PM

    Thank you! It works for me!!!

    ReplyDelete
  9. AnonymousDecember 3, 2013 at 12:24 AM

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

    ReplyDelete
  10. AnonymousJanuary 16, 2014 at 8:40 AM

    worked

    ReplyDelete
  11. AnonymousJanuary 25, 2014 at 12:52 AM

    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. AnonymousApril 30, 2014 at 10:16 PM

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

      Delete
    2. AnonymousAugust 19, 2014 at 3:43 PM

      This, clearly, is a case of user stupidity. As I mentioned above, no need to go delving into system32 to get CMD to run in administrator mode. Just find it in the start menu, right click, run as admin.....simple. Just about every system tool needs admin privileges, so if something doesn't work properly, try admin mode.

      And the blocking of system functions to normal users is quite a good defence. Without it, users would go changing system files\settings willy nilly, messing up their PC's then making people like me come and fix it; or people could create very simple CMD scripts that would bring a system to it's knees within seconds. The administrative mode is an extra layer of defence to stop unwanted\malicious changes to system files.

      So don't go bashing something without fully knowing what it is your bashing.

      Delete
  12. dj yekoFebruary 26, 2014 at 8:48 AM

    it worked! tnx...

    ReplyDelete
  13. UnknownMarch 8, 2014 at 7:17 PM

    thanks a lot man.......its working

    ReplyDelete
  14. AnonymousMarch 24, 2014 at 6:28 PM

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

    ReplyDelete
  15. UnknownApril 26, 2014 at 10:59 PM

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

    ReplyDelete
  16. AnonymousMay 11, 2014 at 6:13 PM

    This is very very helpful, thanks.

    ReplyDelete
  17. AnonymousMay 18, 2014 at 11:36 PM

    This was quite helpful, thank you.

    ReplyDelete
  18. UnknownJune 6, 2014 at 9:09 PM

    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. UnknownJune 17, 2014 at 6:48 PM

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

      Delete
    2. AnonymousOctober 3, 2014 at 5:59 AM

      I am having the same problem I have 16 hours of work into this PC. At this point I am just trying to prove to myself that I can fix anything, and it's a losing battle.

      Delete
    3. AnonymousOctober 12, 2014 at 1:09 AM

      Same problem, spent hours, taken full ownership of windir but nothings working. Hate to reinstall but im near that point.

      Delete
  19. AnonymousOctober 13, 2014 at 12:28 AM

    worked thanks!

    ReplyDelete
  20. AnonymousJanuary 2, 2016 at 7:18 AM

    Did not work in Windows 10.

    sfc /scannow
    Windows Resource Protection could not start the repair service.

    No matter if WMI is running or not, either manual or automatic.



    PS: (windows 10 is malware, don't go for it)

    ReplyDelete
  21. AnonymousDecember 11, 2016 at 2:06 PM

    sfc /scannow
    Windows Resource Protection could not start the repair service.

    Sending me mad

    ReplyDelete

Subscribe to: Post Comments (Atom)