Windows Resource Protection Service Cannot Start During SFC Scan — How to Fix?

If you're encountering the error where the Windows Resource Protection (WRP) service fails to start during an sfc /scannow scan, there could be several underlying causes. However, don't worry—there are multiple methods available to help resolve this issue and restore the normal functionality of the system repair service.

Why Does This Error Occur?

The "Cannot start the repair service" error typically arises from one of the following reasons:

  • Corrupted or missing system files;
  • Conflicts with antivirus or third-party software;
  • Registry errors or misconfigured system settings;
  • Issues with Windows services, including the SFC service itself;
  • Third-party software blocking access to system resources (e.g., optimization utilities).

Methods to Fix the Error

1. Run SFC in Safe Mode

One of the easiest ways to bypass this error is to run the sfc /scannow command in Safe Mode. This will load Windows with only essential drivers and services, increasing the chances of a successful file integrity check.

  1. Restart your computer.
  2. During the boot process, press the F8 or Shift + F8 key to open the Advanced Boot Options menu.
  3. Select Safe Mode with Command Prompt.
  4. In the Command Prompt, type sfc /scannow and wait for the process to complete.

2. Check and Repair the Windows Modules Installer Service

Sometimes, this error can occur due to an issue with the Windows Modules Installer (TrustedInstaller) service, which is responsible for system updates and modifications. To check its status, follow these steps:

  1. Open Command Prompt as Administrator (right-click the Start menu > Command Prompt (Admin)).
  2. Enter the following command: net start trustedinstaller and press Enter. This will start the service if it's been stopped.

If the service fails to start, you may need to repair or further diagnose the system.

3. Use the DISM Tool to Repair System Files

If the standard SFC tool doesn't resolve the problem, try using the DISM (Deployment Imaging Service and Management Tool), which can repair damaged system components that SFC may not be able to fix.

  1. Open Command Prompt as Administrator.
  2. Type the following command and press Enter: 
    DISM /Online /Cleanup-Image /RestoreHealth
  3. Wait for the process to complete, and then run sfc /scannow again.

4. Disable Third-Party Antivirus Software

In some cases, third-party antivirus or optimization programs may block the repair service from functioning properly. Try temporarily disabling your antivirus and then rerun the SFC scan.

5. Check System Services

The issue could also be related to problems with specific system services. To check their status, use the Windows Services Manager:

  1. Press Win + R, type services.msc, and press Enter.
  2. Look for the Windows Modules Installer and Windows Management Instrumentation services and make sure they are running. If they're stopped, start them manually.