windows resource could not start the repair service

If you would like to update the Windows machine, then abide by the given steps.

Finally, click on the Apply option to store the changes.

You have to select Manual as the Startup type when it is not prepared for the default settings.

Go to the services and right-click on it then go for the Properties option.

You should go via the whole services menu and find Windows Modules Installer (or TrustedInstaller).

Thereafter, input the ‘service.msc’ into the Run dialog box and select OK.

Press the Win + R keys at once on your keyboard.

In case you intend to activate Windows Modules Installer service (TrustedInstaller), then go through the below-mentioned steps.

Finally, reboot the system and check when the error still continues.Īctivating Windows Modules Installer Service (TrustedInstaller).

Now, hit the Enter key and wait to finish the process.

You have to continuously enter ‘DISM/Online/Cleanup-Image/RestoreHealth.’.

Administration rights should be provided to Command Prompt.

Thereafter, enter ‘cmd’ into the Run dialog box.

You should press the Win + R keys at once on your keyboard.

If you would like to run a DISM checkup, then abide by the given steps.

Now, press the Enter key, and you have to wait to complete the command.

You should enter ‘sfc /scannow’ once the cursor blink.

Then select to ‘Run as an Administrator.’.

You have to enter ‘cmd’ into it and open the Command Prompt.

Thereafter, the Run dialog box will appear.

Press Win + R keys at once on your keyboard.

In case you intend to perform an SFC scan using Command Prompt, then go through the below-mentioned steps. Source:- How to Fix “Windows Resource Protection could not Start the Repair Service?” The blog contains easy fixes for the issue, so make sure to read it thoroughly.

The service offers smooth functionality however, there is a chance of you encountering “Windows Resource Protection could not start the repair service” error while using it. Windows Resource Protection has been around for a while, making its debut way back in Windows Vista.

Windows resource could not start the repair service