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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-05-09T22:00:44+00:00

    1809

    1909

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-05-08T22:51:56+00:00

    Photos never hurt. But...

    "

    Choose an option> device                       <<< I presume this was just after Shift+Restart, meaning you

                                                                              started in the 1809 internal recovery environment.

                                                                              That's what the Recovery partition is.

    use a device >usb scandisk                      <<< This boots to the 1909 Installation USB which has the 1909

                                                                              external recovery environment (among other things).

    windows country/language screen> next

    windows install or repair> repair              <<< This reboots to the 1909 external recovery environment.

    Hp logo screen

    then back to choose an option> device     <<< Now it is in the 1909 external recovery environment.

                                                                                 You should go for the Command Prompt instead of

                                                                                  booting the USB device again.

    use a device >usb scandisk

    windows country/language screen> next

    windows install or repair> repair

    Hp screen

    "

    So - first do a DiskPart in 1809 recovery environment. Then do it in 1909. Verify that C: & D: look good in both. See whether you can get it into a file, & post the contents of the file after you reboot to Windows. You would create the file with Notepad in the 1809 environment. Then open that same file with Notepad in the 1909 environment, & add the 1909 DiskPart results to the bottom. Or just make pictures.

    Edit:  Come to think of it, all of the letters should show up in Notepad the same as in DiskPart, I think. But look at the DiskPart's too.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-05-08T22:15:01+00:00

    This is what happens when I try the usb 1909 in recovery environment

    Choose an option> device

    use a device >usb scandisk

    windows country/language screen> next

    windows install or repair> repair

    Hp logo screen

    then back to choose an option> device

    use a device >usb scandisk

    windows country/language screen> next

    windows install or repair> repair

    Hp screen

    I tried other windows but none starts the usb running. Even advanced options doesn't have a repair except for startup repair which doesn't have the options to repair other than start up. I took photos if you need them.

    So what am I messing up?

    Was this answer helpful?

    0 comments