How To Fix Windows Resource Protection could not start the repair service — sfc error

Advertisement

Windows

When Windows system misses a Windows Resource Protection (WRP) file, it will encounter some errors. At this rate, you can use SFC (System File Checker) tool to scan and repair the file on Windows. But, it will be useless if an error occurs again and the sfc cannot help you any more. What to do, then? Read on the methods for sfc errors: Windows Resource Protection could not start the repair service.

RELATED TOPICS:

Advertisement

Why does it happen?

First things first: if we want to solve the problem, we should figure out why it happened.

There is such service called Windows Modules Installer(TrustedInstaller) in your Windows. It has full access to Windows Resource Protection (WRP) files and registry keys. When you want to run sfc tool to restore missing or corrupted WRP resources, if Windows Modules Installer is disabled, then the error Windows Resource Protection could not start the repair service would be showing up.

How can I solve the problem?

Therefore, to enable and start Windows Modules Installer service in your Windows can fix the error for you.

Here’s how to:

Step 1. On your keyboard, press Windows key + R key together to open a Run box. Then type services.msc in the box and click OK.
Windows

Step 2. On the open Services window, find and double-click on Windows Modules Installer.
Windows

Read Also:  Solution Fix OBS Black Screen on Windows 10

Step 3. On General pane, select the Startup type to be Manual. Then click Apply OK to save your settings.
Windows

Step 4. Close Services window. Enter cmd in the search box from Start menu and right-click on Command Prompt from the result. Then select Run as administrator.
Windows

Note: When prompted by User Account Control, click Yes.

Step 5. On the open black window, enter the following commands and press Enter key on your keyboard after each:

sc config trustedinstaller start= demand
net start trustedinstaller

Windows

READ ALSO:

Conclusion

Now try to run sfc.exe on your Windows. The error should be fixed.

For queries and suggestions, don’t hesitate to contact us. Thank you for reading, Folks!

Sharing is caring!