How to Fix ‘Windows Resource Protection Could Not Start the Repair Service’

When running the System File Checker command (sfc /scannow) inside an administrative Command Prompt or PowerShell terminal in Windows 11 or Windows 10, the scanning process may terminate immediately with an error: Windows Resource Protection could not start the repair service. Without the SFC utility functional, users are unable to verify protected operating system files or replace corrupted Windows binaries. This blockage occurs when the background service responsible for system component servicing is disabled, stopped, or corrupted.

Fixing this error requires verifying the operational status of the Windows Modules Installer service, resolving registry permissions, and leveraging DISM servicing commands.

What Causes the Windows Resource Protection SFC Failure?

The System File Checker utility does not repair operating system files on its own; it relies on the Windows Modules Installer service (TrustedInstaller.exe) to gain exclusive write permissions to protected system directories (such as System32 and WinSxS). The error occurs due to:

  • Windows Modules Installer Service Disabled: The TrustedInstaller service is stopped or its startup type has been set to Disabled.
  • Corrupted Component-Based Servicing (CBS) Manifests: Damaged system store packages prevent TrustedInstaller from resolving installed component versions.
  • Safe Mode Without Minimal Services: Attempting to run SFC in Safe Mode when the TrustedInstaller service has not been added to Safe Mode service registries.
  • Third-Party Antivirus or Optimizer Interference: Registry optimisers disabling essential Windows maintenance services to reduce background CPU usage.
  • Damaged Service Binary or Permissions: File corruption affecting TrustedInstaller.exe or invalid access control lists (ACLs) on the C:\Windows\Servicing folder.

Step 1: Start and Configure Windows Modules Installer Service

Ensuring that the TrustedInstaller service is enabled and running resolves the vast majority of SFC launch failures:

  1. Press Windows Key + R, type services.msc, and press Enter.
  2. Scroll down through the alphabetical list and locate Windows Modules Installer.
  3. Double-click the service to open its Properties window.
  4. Check the Startup type. If it is set to Disabled, change it to Manual.
  5. If the Service status is Stopped, click the Start button.
  6. Click Apply and then OK.
  7. Open an elevated Command Prompt and rerun sfc /scannow to verify that the scan begins normally.

Step 2: Start TrustedInstaller via Command Prompt

If the Services graphical console fails to open, configure the service directly using administrative command lines:

  1. Press Windows Key + X and select Terminal (Admin) or Command Prompt (Admin).
  2. Set the startup configuration of TrustedInstaller to manual:
    sc.exe config trustedinstaller start= demand
    (Note: There must be a space after start=.)
  3. Start the service immediately:
    net start trustedinstaller
    Confirm that the output reads: The Windows Modules Installer service was started successfully.
  4. Initiate your system scan:
    sfc /scannow

Step 3: Enable TrustedInstaller in Safe Mode (If Applicable)

If you are troubleshooting Windows inside Safe Mode, TrustedInstaller is disabled by default unless registry keys are added:

  1. Open an administrative Command Prompt while in Safe Mode.
  2. Execute the following commands to permit TrustedInstaller execution:
    REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\TrustedInstaller" /VE /T REG_SZ /F /D "Service"
    REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\TrustedInstaller" /VE /T REG_SZ /F /D "Service"
  3. Start the service:
    net start trustedinstaller
  4. Proceed with running sfc /scannow.

Step 4: Repair the Component Store with DISM

If TrustedInstaller fails to start due to corrupted servicing manifests, use the Deployment Image Servicing and Management (DISM) tool to restore the system image:

  1. Open an elevated Command Prompt.
  2. Execute the health check command:
    DISM /Online /Cleanup-Image /CheckHealth
  3. Scan the component store for corruption:
    DISM /Online /Cleanup-Image /ScanHealth
  4. Repair the store using Windows Update servers:
    DISM /Online /Cleanup-Image /RestoreHealth
  5. Allow the command to complete to 100%. Once finished, restart your PC and execute sfc /scannow.

Step 5: Inspect CBS Log Files for Underlying Faults

If the repair service continues to throw errors, inspect the Component-Based Servicing log:

  1. Press Windows Key + R, type C:\Windows\Logs\CBS, and press Enter.
  2. Open the file named CBS.log with Notepad.
  3. Scroll to the bottom of the log to review recent failure entries marked [SR] or Failed to initialize TrustedInstaller.
  4. If severe corruption exists that DISM cannot resolve, consider performing an in-place Windows 11 upgrade installation to rebuild the component store without losing files.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.