Windows Resource Protection Could Not Start the Repair Service

If you ran sfc /scannow and saw “Windows Resource Protection could not start the repair service”, the System File Checker was blocked before it could scan anything. This guide explains why Windows Resource Protection could not start the repair service and gives seven fixes in the order that works fastest, from restarting one Windows service to a repair install that keeps your files.

Quick answer: open Command Prompt as administrator, set the Windows Modules Installer (TrustedInstaller) service to manual with sc config trustedinstaller start= demand, start it with net start trustedinstaller, and run sfc /scannow again. If that fails, repair the component store with DISM.

What Causes Windows Resource Protection Could Not Start the Repair Service?

The repair service named in the message is the Windows Modules Installer, also called TrustedInstaller. SFC needs it to read and replace protected system files. The error appears when: Problems like this often travel together, so it also helps to know the Windows 11 update stuck at 46% guide, the automatic repair loop guide and the steps to repair Windows 10 from USB.

• The Windows Modules Installer service is disabled or set to a startup type that blocks it.
• Command Prompt was opened without administrator rights.
• The component store (WinSxS) is damaged, so the service cannot start properly.
• A pending update or a half-finished repair is holding the servicing stack.
• Third-party security software blocks changes to protected system files.

How to Fix Windows Resource Protection Could Not Start the Repair Service: Step-by-Step

Step 1: Open Command Prompt as administrator

Search for cmd, right-click Command Prompt, and choose Run as administrator. A standard window is the single most common reason for this message, so reopen it properly before trying anything else and run sfc /scannow once more. If this first step does not solve it, the Windows RE image fix cover related causes.

Step 2: Restart the Windows Modules Installer service

Press Win + R, type services.msc, and find Windows Modules Installer. Double-click it, set Startup type to Manual, click Start, then OK. You can do the same in one step from an elevated prompt:

• sc config trustedinstaller start= demand
• net start trustedinstaller

Also Read: https://axeetech.com/how-to-fix-windows-11-update-stuck-at-46-percent-complete-guide/

Step 3: Run SFC again

With the service running, type sfc /scannow and wait until it reaches 100 percent. The scan can take 15 to 30 minutes. Microsoft documents every switch in its System File Checker reference. If SFC reports that it repaired files, restart the PC and test again.

Step 4: Repair the component store with DISM

If SFC still cannot start, repair the image it depends on. Run these commands in order and let each finish:

• DISM /Online /Cleanup-Image /CheckHealth
• DISM /Online /Cleanup-Image /ScanHealth
• DISM /Online /Cleanup-Image /RestoreHealth

Step 5: Try SFC in Safe Mode

Hold Shift while clicking Restart, choose Troubleshoot, Advanced options, Startup Settings, Restart, then press 4 for Safe Mode. Open an elevated Command Prompt and run sfc /scannow. Fewer drivers and programs run in Safe Mode, which removes most conflicts.

Step 6: Check the disk for errors

Run chkdsk C: /f /r and agree to schedule it for the next restart. Bad sectors can stop Windows from reading its own files. For driver problems that surface alongside this error, read how to update device drivers manually.

Step 7: Do a repair install

If nothing works, download the Windows ISO from Microsoft, run setup.exe from inside Windows, and choose to keep personal files and apps. This replaces damaged system files without wiping your data. The Microsoft DISM guide explains the underlying repair process.

Related SFC Error: “Could Not Perform the Requested Operation”

A close cousin of this problem is the message “Windows Resource Protection could not perform the requested operation”. It normally means SFC was started without administrator rights, or it is running while Windows is still busy with a pending restart. Restart the PC first, reopen an elevated Command Prompt, and run the scan again before moving on to DISM.

Reading the SFC Log After a Scan

When SFC finds files it cannot fix, it writes details to C:\Windows\Logs\CBS\CBS.log. Search that file for the word “corrupt” or “cannot repair” to see which files failed. Copying only the SFC lines with findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfclogs.txt" makes the log much easier to read. If you are also chasing blue screens, see the MEMORY_MANAGEMENT blue screen guide.

Common Mistakes When Fixing Windows Resource Protection Could Not Start the Repair Service

• Running SFC in a normal Command Prompt window instead of an elevated one.
• Skipping DISM, then wondering why SFC still fails because the component store is broken.
• Stopping the scan at 20 or 30 percent because it looks frozen. SFC can pause for several minutes.
• Disabling the Windows Modules Installer permanently instead of leaving it on Manual.

Quick Recap: Windows Resource Protection Could Not Start the Repair Service

Start with an elevated prompt and the TrustedInstaller service, then run SFC. If the message returns, repair the image with DISM, test in Safe Mode, check the disk, and finish with a repair install. Most cases of Windows Resource Protection could not start the repair service are fixed by the second or fourth step. Pair this guide with the general Windows troubleshooter guide if other tools also fail to start.

Windows Resource Protection Could Not Start the Repair Service FAQ

What does Windows Resource Protection could not start the repair service mean?

It means the System File Checker could not start the Windows Modules Installer service it depends on, so no scan was performed.

Is it safe to set TrustedInstaller to Manual?

Yes. Manual is the default startup type on most Windows installs, and Windows starts the service when it needs it.

Will a repair install delete my files?

Not if you choose to keep personal files and apps in the setup screen, but a backup before any repair is always wise.

Can I run SFC without administrator rights?

No. SFC needs elevated rights to read and replace protected system files.