Resource Protection could not start the repair service

Question

Resource Protection could not start the repair service

Fe-0859 0

After following the instructions for Storage Test Failure on computer - Options for Resolution. I got the above error message after run: sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

0 comments

2 answers

Your answer

Answer 1

Hendrix-V 14,680 Microsoft External Staff Moderator

Hi Fe-0859,

Welcome to the Microsoft Q&A forum.

The message “Windows Resource Protection could not start the repair service” indicates that Windows was unable to start the service needed to repair system files. This can happen when system files, disk structures, or startup components are affected, often following storage or disk‑related errors.

Here are some possible troubleshooting steps that you can consider trying:

Recommended solutions (short and effective)

1, Run Startup Repair

Boot into Windows Recovery Environment
Select Troubleshoot > Advanced options > Startup Repair
Let the process complete and restart the PC

2, Repair the Windows image using DISM

In Advanced options, open Command Prompt
Run DISM /Image:C:\ /Cleanup-Image /RestoreHealth
After it completes, retry sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

3, Check the disk for errors

From Command Prompt in Recovery, run chkdsk C: /r
Allow the scan to complete and restart

If repairs don’t complete successfully, this option reinstalls Windows while preserving personal data.

Troubleshoot > Reset this PC
Choose Keep my files

If disk checks continue to report storage‑related issues, it may be helpful to consult your device manufacturer for further hardware diagnostics. Persistent storage errors can impact system recovery tools.

Let me know if you need further assistance, feel free to ask me by clicking "Add Comment" or "Add Answer" if you cannot add comment so your response will be visible. Thanks for your effort.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Fe-0859 0 Reputation points

2026-03-01T02:51:01.7733333+00:00

Thank you for the information. I followed the instructions. First chkdsk C: /f /r It stated Unable to obtain a handle to the event log

Tried sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows... The status - Ok

Tried DISM /Image:C\ /Cleanupp-Image /RestoreHealth Windows has scanned the file system and found no problems.
Hendrix-V 14,680 Reputation points Microsoft External Staff Moderator

2026-03-01T02:57:25.6+00:00

Hi Fe-0859,

Thank you for completing the recommended checks.

These results indicate that Windows and its core components are functioning normally. At this point, no further repair actions are required. We recommend restarting the device and continuing to use it as normal.

I hope the insights shared in the forum help address your concerns effectively. If there is anything else I can assist you with, please feel free to let me know in the Comments section.

In addition, if you found the answer helpful, we’d really appreciate it if you could click "Accept Answer" and kindly give it an upvote. Your acknowledgment helps others facing similar situations find useful references and contributes to building a stronger community.
Hendrix-V 14,680 Reputation points Microsoft External Staff Moderator

2026-03-03T10:28:20.9233333+00:00

Hi,

I just wanted to follow up and check if the information I provided was helpful. If you have any further questions or updates regarding this issue, please feel free to let me know in the Comments section. I'd be happy to assist you.

Answer 2

AI answer

"Windows Resource Protection could not start the repair service" indicates that the servicing components SFC depends on (primarily the Windows Modules Installer/TrustedInstaller and the component store) aren’t available or working in the environment where the offline SFC command is being run.

From the provided material, the supported way to address SFC issues is to repair the Windows image first with DISM, then rerun SFC, and if that still fails, move to support.

Use this sequence:

Boot into a Windows environment where the OS image is accessible (for example, normal Windows, WinRE, or a troubleshooting VM if this is a disk from another machine).
Run DISM to repair the image, then SFC:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

If the image files are not available or DISM reports file-not-found errors, explicitly point DISM to a known-good WIM source:

DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:C:\install.wim:1 /LimitAccess
sfc /scannow

If the OS disk is being repaired from another system (for example, Azure VM or offline disk repair), run DISM against the mounted image, then SFC with the offline parameters, ensuring the paths are correct and the servicing stack is intact:

Dism /image:<DriveLetterOfOfflineWindows>:\ /cleanup-image /restorehealth /source:wim:<DriveLetterOfOfflineWindows>:\recovery\windowsRE\winre.wim:1

sfc /scannow /offbootdir=<DriveLetterOfOfflineWindows>:\ /offwindir=<DriveLetterOfOfflineWindows>:\Windows

If, after DISM completes successfully, SFC still reports that it cannot start the repair service or that corruption remains, the guidance is to contact technical support, as this indicates deeper corruption of the servicing stack or system files that SFC/DISM cannot repair.

References:

AI-generated content may be incorrect. Read our transparency notes for more information.

Share via

Resource Protection could not start the repair service

2 answers

Your answer