Fix: Windows Resource Protection Could Not Start the Repair Service

The System File Checker (SFC) is a built-in Windows tool that scans and repairs corrupted or missing system files. It’s commonly used when the system becomes slow, crashes frequently, or displays unexpected errors. However, sometimes when you try to run the sfc /scannow command, you may encounter an error message saying “Windows Resource Protection could not start the repair service“. Several users report similar error: sfc scannow not working. Every time I type it into the admin command prompt, it tells me that Windows Resource Protection could not perform the requested operation, even when I’m in safe mode. This error usually occurs if the Windows Modules Installer service, also known as TrustedInstaller, is disabled or not running. Since this service is responsible for managing, protecting, and repairing core system files, SFC cannot function without it.

What is Windows Resource Protection?

It’s a security feature in Windows designed to protect important system files, folders, and registry entries from being modified, deleted, or replaced by unauthorized programs or users. It uses Access Control Lists (ACLs) to control permissions and restricts changes to a special system account called TrustedInstaller.

When these protected resources become corrupted, SFC (System File Checker) works with TrustedInstaller (Windows Modules Installer) to verify file signatures and restore originals from the WinSxS store.

If, for some reason, TrustedInstaller is not started or disabled, SFC cannot start and display the error: “Windows Resource Protection could not start the repair service.”

• Windows Modules Installer service not started: This is the most frequent cause, as the service is crucial for the System File Checker (SFC) tool.
• Corrupted system files: The SFC tool relies on other system files to function. If these files are corrupt, the SFC scan will fail.
• Malware or virus infection: Malware can corrupt or interfere with essential system files and services, including those needed for SFC.
• Third-party software interference: Some security software or other applications can block the SFC scan from running correctly.
• Problems with the component store: The Component Based Servicing (CBS) component store, which the SFC tool uses, can become damaged.

Start the Windows Modules Installer (TrustedInstaller) Service

SFC depends on the Windows Modules Installer (TrustedInstaller) Service to access and repair protected system files. If this service is disabled or not running, SFC cannot perform repairs, which leads to the error.

1. Press Win + R on your keyboard to open the Run dialog.
2. In the run command box, type services.msc and press Enter.
3. Scroll down the list and locate Windows Modules Installer, right-click and select Restart,
4. If the service not started, Double-click the service to open its properties.
5. Set Startup type to Automatic, click Start to run the service.
6. Click Apply → OK to save changes.
7. Now open Command Prompt (Run as Administrator) and run:

Start Windows Modules Installer (Using Command Prompt)

If the service is missing or fails to start from the Services console, use the command line to force-enable it.

1. Select Start, type CMD, Right-click Command Prompt, then choose Run as administrator.
2. Type command sc config trustedinstaller start= demand then press Enter,
3. Next, run the command net start trustedinstaller to start the service manually
4. Try the sfc /scannow command again.

Check and Repair Windows Image with DISM

If core Windows system files or the component store (WinSxS folder) are damaged, the SFC tool may not have a clean source to repair files from. In this case, SFC will fail repeatedly even if TrustedInstaller is running.

• Open Command Prompt as Administrator.
• Run command: DISM /Online /Cleanup-Image /RestoreHealth

The Deployment Imaging and Servicing Management (DISM) tool repairs the Windows system image and restores missing or corrupted files in the component store.

• It may take 10–30 minutes, depending on the system condition. Once the DISM process is complete, restart your computer.
• After the restart, run the System File Checker again: sfc /scannow

Note: If DISM cannot Download Repair Files

Run SFC in Safe Mode

Safe Mode starts Windows with minimal services and drivers, which prevents third-party software from interfering with system processes such as TrustedInstaller.

• Press Windows + I → System → Recovery.
• Under Advanced startup, click Restart now.
• After reboot, go to Troubleshoot → Advanced options → Startup Settings → Restart.
  Choose 4) Enable Safe Mode.
• Once in Safe Mode, open Command Prompt (Admin) and run: sfc /scannow
• Restart your PC normally after the scan completes.

Verify and Repair Windows Service Dependencies

The TrustedInstaller service relies on other services such as Windows Update and the Background Intelligent Transfer Service (BITS). If these are stopped or misconfigured, SFC may sometimes fail.

• Press Windows key + R, type services.msc and click ok
• Scroll down to locate Windows Update, make sure it’s set to Automatic and running.
• Do check the Background Intelligent Transfer Service as well.
• If these services are not running, right-click → Properties → set Startup type → Automatic → click Start.
• Now open the command prompt as administrator and try running SFC again.

If the previous steps don’t work, temporarily disable your third-party antivirus to check if it’s causing a conflict.

Video: fix Windows Resource Protection could not start the repair service

FAQ: Windows Resource Protection Could Not Start the Repair Service

Q1. What is Windows Resource Protection (WRP)?
WRP protects critical Windows files and registry keys to prevent unauthorized changes. The sfc /scannow command is part of WRP and checks for system file integrity.

Q2. Why does “Windows Resource Protection could not start the repair service” appear?
This error usually appears when the TrustedInstaller service is disabled, missing, or cannot start due to corrupted configurations or system files.

Q3. Can I repair this without reinstalling Windows?
Yes. Most users fix it by manually starting the TrustedInstaller service, running DISM, or performing an SFC scan in Safe Mode.

Q4. Does this issue affect system performance?
Not directly, but since SFC can’t run, you might not be able to repair other corrupted files, which could eventually affect performance or cause crashes.

Q5. Should I use a third-party repair tool?
It’s not recommended. Windows built-in tools like SFC, DISM, and System Restore are reliable and safer to use.

•  Fix Automatic repair couldn’t repair your pc On Windows 10
• Fix Microsoft Edge not responding, keeps freezing on Windows 10
• Windows PC Freezes frequently while playing Games
• Solved: error code: inet_e_resource_not_found in Microsoft Edge