FIX: Windows Resource Protection could not start the repair service

Windows Resource Protection could not start the repair service is quite a normal error to receive when attempting to start a System File Checker scan. The problem is caused by trustedinstaller service not running properly.

One or more steps require the use of Administration rights on the system. Please sign-in in with an Administrator before continuing.

Resolving this problem

Method 1: Using Services.msc

1. Press the Windows + R key on your keyboard at the same time and then type services.msc and hit enter.

Run Services FIX: Windows Resource Protection could not start the repair service resource protection

Run Services

2. Then find Windows Modules Installer or TrustedInstaller and doubleclick it.

TrustedInstaller FIX: Windows Resource Protection could not start the repair service resource protection

TrustedInstaller

3. Now click the Start button.

Services Start FIX: Windows Resource Protection could not start the repair service resource protection

Services Start

 

Then try to run SFC again and see if it now works.

Method 2: Using Elevated Command Prompt

1. Start an Elevated Command Prompt (Run as Admin)

2. Enter the following command:

3. Hit enter.

Net Start TrustedInstaller FIX: Windows Resource Protection could not start the repair service resource protection

Net Start TrustedInstaller

 

Now try to run SFC again and see if it now works.

What's your reaction?
Solved it!
6%
Helped me
0%
Didn't work
88%
Inaccurate Information
6%
About The Author
Yuri Pustjens
Yuri Pustjens
2014, 2015 & 2016 Microsoft Most Valuable Professional Windows Yuri specializes in troubleshooting (crash analysis and devices), system resource utilisation and system performance. He is also very interested in Customer Security. Yuri can be found as Windows Community Moderator and Wiki Author on Microsoft Answers and is active on different communities all across the web.

Leave a Response