sfc /scannow WILL NOT function

Anonymous
2020-04-22T21:30:43+00:00

Cmd Prompt > sfc /scannow says Windows Resource Protection could not start the repair service every time I try to use it. What I have tried to do to fix this through reading this site and many others but no luck. This is what I remember trying:

safe mode start

Windows Modules Installer is at manual

DISM /Online /Cleanup-Image /RestoreHealth > operation successfully completed

net start trustedinstaller>successful

chkdsk /r > typed y but it didn't work either

ICACLS C:\Windows\winsxs and restart

all have failed

administrator cmd prompt says C:\WINDOWS\system32 (I have  a 64 though some programs run on 32)

I tried reinstalling 10 with keeping my programs, but the internet is too slow to get it to work even after several days of trying. I can't fresh install even if I had my disk with me. Many of my programs can't be replaced well not by me.

Have  windows 10 but updates always fail many, many, many times if they going through at all. 

I need my pc working properly and something is definitely wrong with it. I need the scan and repair to work.

If someone can help me I would really appreciate the kindness.

Windows for home | Windows 10 | Performance and system failures

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
2020-05-13T07:55:26+00:00

(1) You don't seem to use the Downloads folder. I guess your way is OK.

(2) I don't like that bugcheck. Do you get a lot of them? Those are blue screen errors. There are many threads on bugchecks that are really sad to look at. They end up checking various hardware components one after the other, swapping RAM chips, installing fans & blowing out dust bunnies. But it could just be software as well.

(3) OS Build 17763.557 was 25 quality updates ago. That's pretty far back...!...

https://support.microsoft.com/en-us/help/4503327

June 11, 2019—KB4503327 (OS Build 17763.557)

Not sure what to suggest. Need to hit the sack.

Was this answer helpful?

1 person found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2020-05-20T04:08:09+00:00

Affinity Designer & Affinity Photo have the same hardware specs...

  • Windows-based PC (64 bit) with mouse or equivalent input device
  • DirectX 10-compatible Graphics Cards and above
  • 2GB RAM minimum (4GB RAM recommended)
  • 670MB of available space; more during installation
  • 1280x768 display size or better

And your HP Pavilion 21-h013w can handle that. And you said one of them did work fine a while. (You got the other only after problems surfaced). I think specs isn't the problem.

(1) It could be worth a shot to deal with KB4023057 as in that article I posted earlier. It could be the real troublemaker with the services it has given you. Either uninstall or fully disable it. However, other threads indicate it's a monster to deal with. It will come back & never quit trying to upgrade your computer. And it can thwart WUShowHide.

(2) Or do the dual-install I also mentioned earlier & see what happens in that. You'll have a clean 1909 (as well as that buggy 1809). Want fuller instructions?

Was this answer helpful?

0 comments

141 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-05-05T00:35:58+00:00

    (1)

    (a) "Did it a couple times through administrator."

    I don't understand that. Did you reboot to the recovery environment? You don't need to "run as administrator" there -- it automatically is an administrator & doesn't ask. So I'm thinking you tried to do an offline scan while booted to Windows. I doubt that can possibly work.

    (b) "I tried it through my user account and got the same."

         "oh and I used D:"

    Those do make it sound as if you did boot to the internal recovery environment. Anyway, try it from your Win 10 Installation USB drive which is a 1909 environment.

    (c) If C:\ is changing to D:\ in the recovery environment, I think I have a cure for that. Want to try it?

    (2) I saw your post before the editing where you said you forgot your password. You really need to rectify that. However, you can avoid the need for a password by booting to the Win 10 Installation USB drive for its external recovery environment. Everything will be the same as above -- except, at step (3), it will not ask for the password. Here is how to boot it...

    (a) Plug in your Win 10 1909 Installation USB drive.

    (b) Hold Shift & click Restart to get to the internal recovery environment, which is 1809.

    (c) At the Choose an Option screen, click "Use a Device".

    (d) Click the Installation USB drive (named by the drive model).

    (e) When that boots, choose "Repair your computer" at lower left (instead of to install).

         This reboots again to its external recovery environment. It will be a 1909 environment. Might make a difference.

    Now try that offline SFC. What happens?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-05-04T21:26:32+00:00

    Did it a couple times through administrator. First time it said a lot why each on of those commands were important and were used to repair windows but no scan started; the second time I got this message.

    Windows Resource Protection could not start the repair service.

    I tried it through my user account and got the same.

    oh and I used D:

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-05-04T04:02:08+00:00

    Let's try an offline SFC in the recovery environment...

    (1) Unplug the external USB drives to keep drive letters at a minimum in the recovery environment.

         Letter assignments may get jumbled there.

    (2) Hold Shift as you click Restart.

         This will reboot to the Recovery partition (that we fattened up).

    (3) At the Choose an Option screen, click "Troubleshoot > Advanced Options > Command Prompt".

         This reboots again & will ask for your Microsoft account password.

    (4) As you've still got multiple letters, enter these commands...

    *DIR  C:*

    *DIR  D:* <<< Normally, the DVD-ROM

    *DIR  E:*

    The one that shows a Windows & a Users folder is the Windows partition.

    (5) If it's C:, enter the following (otherwise use D: or E:)...

    SFC  /ScanNow  /OffBootDir=C:\  /OffWinDir=C:\Windows

    (6) Close the Command Prompt with its "X" or type "Exit".

    (7) Click "Continue" to exit the recovery environment back to Windows.

    Did it run that way? If so, try it in Windows now. Here's what it looked like for me...

    X:\windows\system32>SFC /scannow /offbootdir=C:\ /offwindir=C:\Windows

    Beginning system scan.  This process will take some time.

    Windows Resource Protection did not find any integrity violations.

    Was this answer helpful?

    0 comments