[Solved] Windows Resource Protection could not perform the requested operation

By April Cai in Common Errors Tags: Windows

When some Windows functions don’t work or Windows crashes, use System File Checker (SFC) to scan and restore corrupted Windows system files. However, as many users reported, when they perform a “sfc /scannow” command, “Windows Resource Protection could not perform the requested operation” error pops up. 

If you’re annoyed by this problem, don’t worry. You can fix it with our help here:

Solution 1. Run SFC in safe mode

1) Press the Windows logo key  and R key at the same time to invoke the Run box.

2) Type msconfig and press Enter.

2) Tick on Safe boot in Boot and click OK.

3) Click Restart when asked by System Configuration.

Your Windows will then boot into safe mode

4) Run sfc /scannow to see if it works.

Solution 2. Run CHKDSK

If there were errors on your hard drive, SFC would also fail. CHKDSK can check the integrity of your hard disk and fix various file system errors: 

1) Type cmd in the search box from Start. Then right-click on Command Prompt to choose Run as administrator.

2) Click Yes when prompted by User Account Control.

3) Type chkdsk /r in the open Command Prompt window and press Enter. Enter y, When asked to schedule checking disk.

4) Close the Command Prompt window, and restart your PC.
Then it will start checking disk and fix the errors detected automatically.



5) Run sfc /scannow to see if it works.

  • Daniel A

    I did everything and it did take around 20 minutes for the CHKDSK step to finally start going past 33% (took around 30 – 40 minutes in total) but SFC/SCANNOW still gets stuck at 17%… Damn! This looks bad.

  • Suzanne Reynolds Angell

    I have followed the above instructions. It is currently scanning and repairing drive at 25% complete this has been the same for 20mins. Should the repair be completed by now?

    • April Cai

      Hi, Suzanne. It’s not easy to say how long the CHKDSK takes exactly. It’s directly related to the speed of your computer and the size of your hard drive. Also, if there are a lot of issues on your disk, it will take much longer time then. Please take your patience to just wait for it to complete.:)

      • Hapmaplapflapgap

        should i expect the 21%->22% to take approximately the same time as for instance the 15%->16%? it seems to get stuck at 21 but i can’t tell if its actually stuck or if it just takes way longer for some reason.

    • Daniel A

      Did it ever work?

  • Nadia Bernabe

    I typed everything in but my pc say “Windows cannot run disk checking on this volume because it is write protected

    • MeMadMax

      That sounds like a virus.
      Run a antivirus check on ur system.

    • Jennifer

      Change the drive letter from X:/ to C:/

      The X: drive (administrator CMD prompt) is write protected but the C: drive you are trying to check is not.

      And by the way, I’m getting really tired of people giving out bad advice to people about Windows. The person who responded previously had no idea what he was talking about. If you don’t know, then STFU.

      The worst violator of this is Microsoft itself, they don’t even read your questions before responding with some canned answer.

      • Printul DE Brazilia

        i do not understand how to change drive letter?

        • Patrick Andrews

          to change drive letter, type C: and hit enter. Pretty straightforward

  • Cluff Elliott

    So what happens if chkdsk/r doesn’t fix the problem. Sfc gets to 98% and give me the same message?

  • Fares Masry

    nothing of these works for me

  • Constitutional Reconvention

    It should be chkdsk /f –> the /r command is not exactly going to be fun, waiting that long.

    • Daniel A

      But is /f still gonna fix the problems?

      • Constitutional Reconvention

        In general, yes. If you have bad sectors, then the /r is fine. But some hard drives can take 2 to 40 hours to complete this process.