The System File Checker or sfc.exe is a utility in Microsoft Windows located in C:\Windows\System32 folder. This utility allows users to scan for and restore corrupt Windows system files. But sometimes while running this tool, you may receive one of the following errors – and the tool will not be able to run or complete its job successfully.

How do I fix Windows Resource Protection cannot start the repair service?

If this happens, you may try to Run System File Checker in Safe Mode or at Boot-Time or repair the Windows Component Store using DISM and see if it works, or you may troubleshoot the errors individually, by following the individual links.

Windows Resource Protection could not start the repair service

If you receive this error message, try this: Run services.msc to open the Services Manager. Look for Windows Modules Installer or the TrustedInstaller service. Double-click on it and ensure that the Service is Started. If not press the Start button. Its startup type has to be set to Manual, by the way. Alternatively, you could open an elevated Command Prompt, type the following and hit Enter.

Once the service is started, run System File Checker and see if it works. If it still does not work, you may need to analyze its logs.

How do I fix corrupted files in Windows Resource Protection?

To fix corrupted files in Windows Resource Protection, you need to run the DISM Tool or use the Reset This PC option. That is sure to help you. This post will show you how to how to Run sfc /scannow System File Checker on External Drives. See this post if you receive a There is a system repair pending which requires a reboot to complete error message.

Windows Resource Protection could not start the repair service - 57Windows Resource Protection could not start the repair service - 68