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
- Fix for Event Log Service Startup Error 1079
- How to Create a System Repair Disk in Windows 7 and Vista
- Fix for Themes Service Startup Problems in Windows 7 and Vista
- Error “the Audio Service Is Not Running” When Opening the Volume Mixer in Vista
- How to Update the Repair Folder in Windows XP Using NTBackup
If you enjoyed this post, make sure you subscribe to our RSS feed! We feature Tips, Troubleshooting information, Scripts and Utilities for Microsoft Windows Operating Systems!
Prefer an E-mail subscription?
I have this exact same problem with scannow and this fix didn’t work for me either. The service was already set to manual.
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.
@David: Check out http://www.winhelponline.com/blog/run-sfc-offline-windows-7-vista/
I need a command prompt fix – windows doesn’t start
Note you have to run the shortcut as Administrator for it to run.
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.
What? My module was already in the “manual” mode setting. Da hell man?
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.