If the Windows Resource Protection (WRP) is missing or corrupted, then System File Checker (SFC) can help to scan and repair corruptions in Windows system files using /scannow parameter.
sfc /scannow will scan all the protected system files and replace the corrupted file with a cached copy. But if there is an error, the SFC tool cannot work. One of the SFC errors is: Windows Resource Protection could not start the repair service.
This article covers information of this error, how to solve the “Windows Resource Protection could not start the repair service” error.
SFC is a utility in Windows. It allows the user to scan for and restore corrupt Windows system files.
But sometimes while running this tool you can also receive one of the following errors:
- System File Checker SFC cannot repair corrupted member file.
- Windows Resource Protection found corrupt files but was unable to fix some of them.
- System File Checker not working, will not run or could not repair.
If these error occurs; you can try running System File Checker in Safe Mode or at Boot Time or repair the Windows Component Store using DISM.
Why “Windows Resource Protection Could Not Start the Repair Service” error occurs?
There is a device called Windows Modules Installer (TrustedInstaller.exe) in your Windows. This device:
- Has full access to the WRP files and registry keys.
- Enables installation, modification, and removal of Windows updates.
TrustedInstaller.exe is a process of Windows Modules Installer service in Windows 10/8/7/Vista, which is located in C:\Windows\servicing\. The permission for full access to modify WRP-protected resources is restricted to processes using the Windows Modules Installer.
If your Windows Modules Installer is disabled and you are trying to run the sfc
Tool then the error of Windows Resource Protection could not start the repair service will occur.
How to fix “ Windows Resource Protection Could Not Start the Repair Service ” ?
So how to fix the error “Windows Resource Protection Could Not Start the Repair Service”. By enabling and starting the Windows Modules Installer service in Windows can fix this error. Here are the few simple steps:
- On keyboard press Windows+R key together, to open a Run box.
- Type services.msc and Click OK.
A Service Window will be opened. Find and double-click on Windows Modules Installer.
- In General pane (adjacent to Log On), select Startup type as Manual.
- Click Apply then OK.
To accomplish the same task using command-line following steps should be followed:
Enter cmd in search box
Right click and select Run as administrator.
On opening the Command-prompt, type the following commands and hit Enter after each command.
sc config trustedinstaller start= demand net start trustedinstaller
Now try running the sfc.exe, the error of “Windows Resource Protection Could Not Start the Repair Service” should get eliminated.