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-27T22:39:49+00:00

    (1) If you are happy with 1909, the best thing to do is a new clean installto get all the partitions right. Currently, you've got...

    (a) An empty leftover Win 8.1 recovery partition.

    (b) An EFI partition shared by 1809 & 1909.

    (c) An MSR partition probably used by 1809 only.

    (d) An 1809 Windows partition that is highly dysfunctional.

    (e) A 1909 Windows partition (named Local Disk) that has its recovery environment in a folder.

    (f) An 1809 recovery partition.

    (g) A Win 8.1 factory reinstall partition.

    That's a big mess & waste of space. We could probably clean it up dangerously with AOMEI -- but a clean install really is best. You've got that first system image to get you back in shape, if something goes really wrong -- but I doubt it will. We know 1909 can clean install well for you.

    Remember, version 2004 is coming soon. We don't know what it will think of that big mess or the smaller one AOMEI is likely to leave.

    (2) Let me see what Windows system image offers to you...

     

    Mine are all pre-selected & cannot be checked/unchecked. You will want EFI (it's shared). MSR doesn't show up there. The WinRE it offers or pre-selects belongs to 1809, but at least it's tiny & won't hurt 1909. Yeah, may as well make one without the 1809 partition (D:). Then name it "Messy_1909".

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-05-27T21:54:09+00:00

    I renamed the old back up "image_1909_with_1809" should I make a new one without the 1809?

    I did another dry run and it looks like it went correctly. I should the above file.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-05-27T03:21:54+00:00

    (1) OK. E: is a partition Non Grata anyway. We want to kill it soon.

    (2) "DESKTOP-6CGVOG7" is the name 1909 gave to your computer. So, the image put that name on the folder.

    (a) Rename it in WindowsImageBackup to "Image_1909_with_1809". Don't append, just rename. Then see whether that name is offered by the restore process. But then back out.

    (b) You may rename your computer in 1909 at "right-click START, System, Rename this PC". After that, Windows system image backup will put the new name on that folder (the first one inside WindowsImageBackup) .

    (3) "I would like not to have to reinstall programs and update again if possible."

    I guess you can keep your current 1909, & we can clean off the extraneous partitions with AOMEI Partition Assistant. But I have a misgiving or two about it.

    Was this answer helpful?

    0 comments