Now Lets start quick guide For Fixing “Windows resource protection could not start the repair service” –
Method 1 : Follow these steps to attempt to fix the problem.
- The error above is normally caused by the Windows Modules Installer service not being started. Start it with these steps.
- Select “Start” and type “CMD“.
- Right-click “Command Prompt” then choose “Run as administrator“.
- If prompted, enter a username and password that grants admin rights to the computer.
- Type “sc config trustedinstaller start=auto“, then press “Enter“. You should get a “SUCCESS” message.
- Type “net start trustedinstaller“, then press “Enter“. You should receive a message that the service was started.
- TrustedInstaller started
Now try the “sfc /scannow” command. It should work without issue now.
That how “Windows resource protection could not start the repair service” will fix.
Methot 2 :Windows Resource Protection could not start the repair service – SFC Error
When you run the System File Checker (Sfc.exe) using the /scannow parameter to restore missing or corrupt system files, the following error may occur.
Windows Resource Protection could not start the repair service
Windows Resource Protection could not start
Additionally, you may experience problems running Windows Installer Setup files and installing fixes from Windows Update.
This happens if the TrustedInstaller (Windows Modules Installer) service is disabled. 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.
Use these steps to reset the service startup type of Windows Modules Installer service.
1. Press Win key + R to launch the Run dialog, type Services.msc, and press ENTER
2. Double-click Windows Modules Installer
3. Set its Startup type to Manual
4. Click OK.
To accomplish the same using command-line, open Command Prompt as administrator. Run the following commands and press ENTER after each line.
sc config trustedinstaller start= demand
net start trustedinstaller
That should fix the problem. Another option would be to run Sfc /scannow in offline mode (Windows Recovery Environment).
This article was originally written for Windows Vista and 7, but very much applies to Windows 8 and Windows 10 as well.
I hope this article is useful to you for resolving the Windows resource protection could not start the repair service error! If you like it then you can share it with your friends. Use below sharing option and share it on your favorite social media sites. Bookmark this website to get more tricks and tips on windows.