Windows Resource Protection could not start the repair service.

Question

Sfc /Scannow Windows Resource Protection could not start the repair service.

Answer 1

1

Run this command in Command Prompt first:

DISM.exe /Online /Cleanup-image /Restorehealth

Then run the SFC command again to test if it then succeeds.

2

If that does not resolve the problem, open the Settings App.

Go to System - Recovery.

Click the Reinstall Now' button in the 'Fix problems with Windows Udpates' section, and wait for that process to complete.

This process will not affect your files, settings or installed apps and should resolve any problems with the Windows system files.

Answer 2

Run System File Checker only from an elevated Command Prompt and ensure the required services and folders are available.

1. Open an elevated Command Prompt
   1. Select Start.
   2. Type command.
   3. Right‑click Command Prompt and select Run as administrator.
   4. Approve the UAC prompt.
2. Start the TrustedInstaller (Windows Modules Installer) service
   1. In the elevated Command Prompt, run:

            sc config trustedinstaller start= demand
            net start trustedinstaller
      

   2. If this service is stopped or disabled, Windows Resource Protection cannot start the repair service and sfc /scannow fails.
3. Verify WinSxS temp folders exist System File Checker needs the WinSxS temp structure:
   • Open File Explorer and go to: C:\Windows\WinSxS\Temp
   • Confirm both PendingDeletes and PendingRenames folders exist.
   • If either is missing, create the folder with the exact name (no spaces, correct capitalization).
4. Run SFC again In the same elevated Command Prompt, run:

      sfc /scannow
   

   Do not close the window until verification reaches 100%.
5. If SFC still fails, run DISM first (Windows 8.1/10/11) In the elevated Command Prompt, run:

      DISM.exe /Online /Cleanup-image /Restorehealth
   

   After it completes successfully, run:

      sfc /scannow
   

6. If SFC completes but reports repairs
   • When the result is “Windows Resource Protection found corrupt files and successfully repaired them.”, the operation succeeded.
   • To review details, filter the CBS log for SFC entries:

          findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >sfcdetails.txt
     

     Then open sfcdetails.txt to see what was repaired.

If the error persists after these steps, collect logs (CBS.log, DISM logs, Event Viewer) and consider using the Windows troubleshooters or contacting support, as there may be deeper servicing or component store corruption.

---

References:

• Use the System File Checker tool to repair missing or corrupted system files
• Description of System File Checker (Sfc.exe)
• Windows 10 upgrade quick fixes
• Error: Windows Explorer has stopped working
• "Error 1053: The service did not respond to the start or control request in a timely fashion"
• The CBS.log file contains entries that some files aren't repaired even after you successfully run the SFC utility on a Windows Server based computer