Windows Resource Protection could not 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 Defender updates failed, service won't start in AntiVirus, Firewalls and System Security The last few days, Defender has been trying and failing to update its definitions. A manual update from Defender fails.
- Windows Resource Could Not Start The Repair Service Program
- Windows Resource Protection Could Not Start The Repair Service Win10
Windows Resource Protection could not start the repair service is quite a normal error to receive when attempting to start a System File Checker scan. The problem is caused by trustedinstaller service not running properly.
Method 1: Using Services.msc
1. Press the Windows + R key on your keyboard at the same time and then type services.msc and hit enter.
2. Then find Windows Modules Installer or TrustedInstaller and doubleclick it.
TrustedInstaller
3. Now click the Start button.
Windows Resource Could Not Start The Repair Service Program
Bab i akuntansi pajak waluyo edisi 6 ebook. Then try to run SFC again and see if it now works.
Method 2: Using Elevated Command Prompt
1. Start an Elevated Command Prompt (Run as Admin)
2. Enter the following command:
3. Hit enter.
Net Start TrustedInstaller
Now try to run SFC again and see if it now works.
I cannot run SFC. How do I fix it?
dism.logI have not tried running it in Safe Mode yet.
ChloeChloe1 Answer
Wow I never would have expected this. I found the answer in a comment.
I was using a 32 bit console called console2, and running as an administrator – was frustrating as hell as nothing worked. For me, this was the missing link in the chain. Really grateful man, as this has been bugging me for months. Microsoft really should have caught this one with a more meaningful error message… I wonder how many human years have been wasted from misleading error messages!
I was using Console2 also. When I ran it from the shitty Microsoft cmd shell (Command Prompt run as Administrator), then it worked.