Windows 10 Windows Resource Protection Could Not Start the Repair Service: Getting SFC to Run
You open Command Prompt as administrator and type sfc /scannow to repair system files. Instead of a scan, you get “Windows Resource Protection could not start the repair service.” When Windows 10 Windows PAGODA127 SLOT Resource Protection could not start the repair service appears, the tool that SFC depends on is not running, so no scan can begin.
SFC, the System File Checker, relies on the Windows Modules Installer service, also known as TrustedInstaller. This service is normally set to start when needed. If it is disabled, stuck, or damaged, SFC cannot request repairs and stops immediately.
Optimisation tools often disable TrustedInstaller because it uses resources during updates, and malware sometimes disables it to prevent repairs.
Starting the service, or running SFC from recovery, usually lets the scan proceed.
What Might Be Causing It
SFC fails to start for these reasons:
- The Windows Modules Installer service is disabled.
- The service is stuck from a previous update or repair.
- The command was run without administrator rights.
- System components needed for the service are damaged.
Windows Update problems often appear at the same time, because updates use the same service.
A pending restart from Windows Update can also keep the service busy. Restarting the PC before running SFC often clears this without further changes.
First Steps to Try
Start the service.
- Make sure Command Prompt was opened with “Run as administrator.”
- Press Windows + R, type services.msc, and press Enter.
- Double-click Windows Modules Installer, choose Manual as the Startup type, and start the service.
- Return to the administrator Command Prompt and run sfc /scannow again.
- If Startup type is greyed out, continue with the next steps.
You can also start the service from Command Prompt with sc config trustedinstaller start= demand, followed by net start trustedinstaller.
If the Problem Continues
Run repairs another way.
- Run DISM /Online /Cleanup-Image /RestoreHealth, which repairs the component store SFC needs.
- Restart and try sfc /scannow again.
- If it still fails, restart into Advanced options and open Command Prompt from recovery.
- Run sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows, adjusting the letter if needed.
- Run a Full scan and an offline scan with Microsoft Defender in case malware disabled the service.
Uninstall optimisation tools that disable services to stop this happening again.
Protect Your Data First
Do not delete or replace TrustedInstaller files manually. Create a restore point before running repairs, and let DISM and SFC finish without interruption.
The Bottom Line
SFC cannot start when the Windows Modules Installer service is disabled or stuck. Set the service to Manual and start it, repair the component store with DISM, and run SFC offline from recovery if needed.