When you run the System File Checker using the /Scannow parameter from an elevated Command Prompt, the following error may occur. Additionally, you may experience problems running Windows Installer Setup files and installing fixes from Windows Update.

Windows Resource Protection could not start the repair service

This happens if the TrustedInstaller (Windows Modules Installer) service is disabled. Use these steps to reset the service startup type.

1. Click Start, type Services.msc

2. Double-click Windows Modules Installer

3. Set its Startup type to Manual

4. Click OK.

The TrustedInstaller service has full access to Windows Resource Protection (WRP) files and registry keys, and this services needs to be running in order to restore missing or corrupted WRP resources. The TrustedInstaller service starts on-demand when running the System File Checker.

Related Posts


Email SubscriptionPrefer an E-mail subscription?

Enter your email address:

Delivered by FeedBurner

8 Comments

  1. Harmil2
    said this on Wednesday, September 1st 2010 12:11 pm

    I have this exact same problem with scannow and this fix didn’t work for me either. The service was already set to manual.

  2. Kiachu Shen Ku
    said this on Monday, August 23rd 2010 5:50 pm

    Just a Note:
    I am troubleshootng out Vista failing to update with error 8070002.
    My Vista at this point has:
    TrustedInstaller description says “
    Status: is blank; Startup Type: is blank.

    When attempting to start the TrustedInstaller, it gives error Error 2: The system cannot find the file specifiied.

  3. said this on Monday, August 16th 2010 11:06 am

    @David: Check out http://www.winhelponline.com/blog/run-sfc-offline-windows-7-vista/

  4. David
    said this on Sunday, August 15th 2010 9:18 pm

    I need a command prompt fix – windows doesn’t start

  5. said this on Sunday, April 25th 2010 7:31 am

    Note you have to run the shortcut as Administrator for it to run.

  6. said this on Sunday, April 25th 2010 7:30 am

    what I did was browse to C:\Windows\System32\sfc.exe made a shortcut on the desktop and added the /scannow to the target of the shortcut.

  7. N/A
    said this on Wednesday, March 31st 2010 6:06 am

    What? My module was already in the “manual” mode setting. Da hell man?

  8. Aron J
    said this on Wednesday, February 24th 2010 3:46 pm

    This doesn’t work (or atleast the problem can be caused by other things as well.

    The times I have experienced this (always in conjunction with a WU 80080005 error) the problem wasn’t solved by setting the service to manual or it was already at manual.

Leave a Reply