Repair Windows Resource Protection failed to start repair service: falla sfc / scannow

Contents

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 corrupt system files. Despite this, can get Windows Resource Protection was unable to start the repair service Error trying to run sfc command / scannow. Here, in this post, I will walk you through how to fix Windows resource protection failed to start repair service error in Windows 10/8/7, Vista and Windows Server.

You may receive the following error message when sfc / scannow does not repair system files.

SFC System File Checker cannot repair corrupted member file
O,
Windows Resource Protection found corrupt files but was unable to repair some of them
O,
System File Checker does not work, does not run or cannot be repaired.

Cause:

This error mainly occurs when Windows module installation services do not start. In this post, I'll tell you 2 methods to start this service.

Method 1: using the command line

Steps 1: Open Command prompt as administrator. Ir Start menu, and look for Command and, when the result appears, right click on it and select Execute as an administrator.
run command prompt as administrator

Paso 2: Type the following command and hit enter. When the commands are executed successfully, will return it to a message “SUCCESS”.

sc config trustedinstaller start= auto
sfc scannow falla

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

That's all. Now you can run the sfc command / scannow without getting an error. Yes even then, you get the same error or another error message, You can use the next alternative tool to fix the error Windows Resource Protection could not start repair service.

Subscribe to our Newsletter

We will not send you SPAM mail. We hate it as much as you.