Fix Windows Resource Protection Could Not Start the Repair Service – sfc /scannow fails

Windows-Resource-Protection-could-not-start-repair-service

sfc /scannow is the great command line tool that works great when your PC needs to repair damaged or corrupted system files. However, you may get Windows Resource Protection Could Not Start the Repair Service error when trying to run sfc /scannow command. Here, in this article, I will guide you How to fix Windows Resource Protection Could Not Start the Repair Service Error in Windows 10/8/7, Vista and Windows Server.

You may get following error message when sfc /scannow fails to repair system files.

System File Checker SFC cannot repair corrupted member file
Or,
Windows Resource Protection found corrupt files but was unable to fix some of them
Or,
System File Checker not working, will not run or could not repair.

Cause:

This error mostly caused when Windows Modules Installer Services is not started. In this article, I will tell you 2 methods to start this service.

Method 1: Using Command Line

Steps 1: Open Command Prompt as Administrator. Go to Start menu, and search for Command and as the result appears, Right-click on it and select Run as Administrator.
run-command-prompt-as-administrator

Step 2: Type following command and press enter. When commands get executed successfully, it will return you to a message “SUCCESS”.

sc config trustedinstaller start= auto
sfc scannow fail

Step 3: Now, type following command and press Enter.
net start trustedinstaller

That’s all. Now you can run sfc /scannow command without getting an error. If still, you are getting the same error or another error message, then you can use following alternate tool to fix Windows Resource Protection Could Not Start the Repair Service error.

Leave a Reply

Your email address will not be published. Required fields are marked *