How to fix “Windows resource protection could not start the repair service” in Windows

How to fix “Windows resource protection could not start the repair service” in Windows – When you use the /scannow parameter to run the system file checker (Sfc.exe) to restore the missing or damaged system files, the following error may occur.

fix “Windows resource protection could not start the repair service”

In addition, you may encounter problems when running Windows Installer files and installing patches from Windows Update.

This can happen if the TrustedInstaller (Windows Module Installer) service is disabled. The TrustedInstaller service has full access to Windows Resource Protection (WRP) files and registry keys, and the service needs to be running to recover lost or damaged WRP resources. When running the system file checker, the TrustedInstaller service will start on demand.

Fix “Windows resource protection could not start the repair service” in Windows

The above error is usually caused by not starting the Windows module installer service. Start with the following steps.

  • Select “Start” and type “CMD“.
  • Right-click Command Prompt then choose “Run as administrator“.
  • If prompted, enter a username and password that grants admin rights to the computer.
  • Type “sc config trustedinstaller start= auto“, then press “Enter“. You should get a “SUCCESS” message.
  • Type “net start trustedinstaller“, then press “Enter“. You should receive a message that the service was started.

That should solve the problem. Another option is to run Sfc /scannow in offline mode (Windows Recovery Environment).

Hope to help you !

More: Did you get error code 800F0922 when updating windows 10? Please refer to the article on how to fix the error “Update Error 800F0922 in Windows 10“.

How useful was this post?

Click on a star to rate it!

Average rating / 5. Vote count:

No votes so far! Be the first to rate this post.