Fix Windows Resource Protection Could not Start Repair Service

You need to run the SFC scan in Safe Mode to get past this issue

Reading time icon 3 min. read


Readers help support Windows Report. When you make a purchase using links on our site, we may earn an affiliate commission. Tooltip Icon

Read the affiliate disclosure page to find out how can you help Windows Report effortlessly and without spending any money. Read more

Key notes

  • If you are getting the windows resource protection could not start the repair service error, it might be due to a third-party app.
  • A quick and effective way to get past this issue is to run the SFC scan in Safe Mode.
  • You can also solve this problem by running the CHKDSK command to repair bad disk sectors.
windows resource protection could not start the repair service

windows resource protection could not start the repair service is an error message displayed while SFC is running on your Windows 10 computer. Since SFC is a tool for repairing and restoring system files, finding a quick fix for this system bug is imperative.

In this guide, we will show you quick ways to fix this issue and restore normalcy on your PC.

How to fix the Windows resource protection SFC error?

1. Run SFC in Safe Mode

  1. Press the Windows key + I to open the Settings app and select the Update & Security option.
    update and windows resource protection could not start the repair service
  2. Select the Recovery option in the left pane and click the Restart now button under Advanced startup.
    restart now
  3. When your PC restarts, choose Troubleshoot > Advanced options.
    advanced options
  4. Now, select the Startup Settings option.
    startup settings windows resource protection could not start the repair service
  5. Click the Restart button.
    restart
  6. Once your PC restarts, press the corresponding key to Enable Safe Mode or Safe Mode with Networking.
    enable safe
  7. Next, when your PC boots up, press the Windows key, type cmd, and select Run as administrator under Command Prompt.
    cmd admin windows resource protection could not start the repair service
  8. Finally, copy and paste the SFC command below and hit Enter to run it: sfc/scannowsfc scannow

If you are getting the Windows resource protection could not start the repair service error while trying to run the SFC scan on normal boot, you might need to run the scan in Safe Mode.

If the scan works normally, the problem could be due to a third-party app or process.

2. Make some security changes

  1. Press the Windows key + S, type cmd, and click Run as administrator under Command Prompt.
    cmd admin windows resource protection could not start the repair service
  2. Type the command below and hit Enter: ICACLS C:Windowswinsxsicalcs
  3. Finally, wait for the command to finish running and restart your PC.

SFC might be interrupted if the winsxs folder cannot be accessed for some reason. The might be why you are getting the Windows resource protection could not start the repair service error.

You can fix this by modifying security descriptors for that folder.

3. Run CHKDSK from Command Prompt

  1. Launch Command Prompt as an administrator.
  2. Type the command below and hit Enter: chkdsk c: /rchkdsk windows resource protection could not start the repair service
  3. Now, press Y when you are prompted.
  4. Finally, restart your PC and the scan will begin automatically when your PC boots up.

Another reason for the Windows resource protection could not start the repair service is related to hard disk errors. The easiest way to fix this is to run the CHKDSK command.

The three methods detailed in this tutorial should help you solve the Windows resource protection could not start the repair service error on Windows 10. It means that now you can run the SFC scan without any sort of problems.

If the SFC scan is still not working on your PC, check our detailed guide to fix it quickly.

Let us know which of the methods worked best for you by leaving us a message in the comments below.

More about the topics: windows 10 fix