Trying to run sfc/scannow and response is "Windows Resource Protection could not start the repair service"

Anonymous
2010-01-23T17:14:37+00:00

Originally, this started when I was trying to install some statistical software (JMP8) that should be supported by Windows 7.  I kept getting "the application could not start because its side by side configuration is incorrect"

While researching that for Windows 7, I ran across a suggestion to run sfc/scannow in the command prompt.  When I try to do that, I get the error listed above:  Windows Resource Protection could not start the repair service.

Any suggestions?

Windows for home | Windows 10 | Microsoft Store

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2012-05-20T11:30:12+00:00

I  had  this issue and all the steps described in this and other internet posts led me  to a dead end of errors. 

However, I then discovered that somehow almost all my services had  gotten reset to "disabled". This was causing my original problems (network connectivity among them) and this problems.

Changing the services settings fixed my problems

To get to services type services in the search programs box on the start menu, then right click to run it as administrator.

Was this answer helpful?

300+ people found this answer helpful.
0 comments

72 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2015-09-30T05:17:28+00:00

    How do you know if the sfc.exe is 64 bit or 32 bit?

    I don't think it matters at all.

    I successfully fixed issues with dism that said "could not download source files" or "source files not found" by using the /source command to point it to a .wim.

    For example:

    dism /online /cleanup-image /restorehealth /source:wim:d:\sources\install.wim:1 /limitaccess

    *Where "d" is the drive letter of the mounted image.

    By the way, if you still get those errors after using the source file to point to a .wim, then copy the .wim from the source and paste it into your downloads for example and point the source to the downloads location.

    If that doesn't work, then change the extension from .wim to .esd, download esd decrypter and then convert it from the .esd to .wim again.  This will ensure you have a proper .wim.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-09-30T05:07:49+00:00

    Wow.  Thank you.  

    Why in the world, on a 64-bit system, would the 32-bit version of this utility be loaded before the proper 64-bit version is beyond me.    Mind-boggling.

    But this is the trick.  

    Thanks again.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-09-19T18:51:35+00:00

    That's probably because Windows tries to run the 32bit version of SFC.exe in a 64bit Windows installation.

    I went through the same frustrating error on Win10 x64.

    To make a long story short just use this command line from an Admin prompt (please notice the "sysnative" path...):

    C:\windows\sysnative\sfc /scannow

    Solved.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments