Windows Resource Protection could not start the repair service (Solved)

Windows Resource Protection could not start the repair service is an error which may occur in a Windows 10, 8, or 7 based computer while you are trying to run the System File Checker tool (SFC /SCANNOW) to scan and repair Windows system files. 

Windows Resource Protection could not start the repair service

The Windows Resource Protection could not start the repair service error is caused because the Windows Modules Installer (aka "TrustedInstaller") is disabled on the system.

This tutorial contains instructions on how to resolve the SFC /SCANNOW "Windows Resource Protection could not start the repair service" error.

How to fix "Windows Resource Protection could not start the repair service" problem.

1. Simultaneously press the Windows + R keys to open run command box.
2. In run command box, type: services.msc and press Enter.

services.msc

 

3. In the list of services double click at "Windows Modules Installer" service.

image

 

4.Set the startup type to Auto and click OK

Windows Modules Installer

 

5. Restart your computer.
6. After the restart, you 'll be able to run the "sfc /scannow" command without any problems. *

* Note: If the "Windows Resource Protection could not start the repair service" appears again, then:
1. Navigate to Windows services management and make sure that the "Windows Modules Installer" is started.
2. Check your system for virus and malware infections by using this guide: Quick Malware Scan and Removal Guide for PC's.

That's it! Let me know if this guide has helped you by leaving your comment about your experience. Please like and share this guide to help others.

If this article was useful for you, please consider supporting us by making a donation. Even $1 can a make a huge difference for us in our effort to continue to help others while keeping this site free: