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 No 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 No 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 No comments

141 additional answers

Sort by: Newest
  1. Anonymous
    2020-05-27T03:03:46+00:00

    No, the image backup didn't give the option for E:.

    There is a folder called "DESKTOP-6CGVOG7"  in WindowsImageBackup. I guess MY LITTLE AGGRIVATION was my old pc. This one must not be named- I wouldn't have chosen DESKTOP-6CGVOG7. Inside it has folders - Backup 2020-05-26 021321, Catalog, Logs, SPPMetadataCache and a file named Mediald. I just want to make sure that DESKTOP-6CGVOG7-1809 is what I'm suppose to name it? Will try the boot now.

    I was able to get to recovery. Should I do another image back up without the extra partition? I would like not to have to reinstall programs and update again if possible.

    The end is in sight!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-05-27T00:19:39+00:00

    Here are your partitions...

    Local Disk is the name of your 1909 partition. It is C: when you boot to it. Otherwise, it's D:.

    Windows is the name of your 1809 partition. It is C: when you boot to it. Otherwise, it's D:.

    Recovery Image is your old D:. It's been pushed to E:.

    Soon, we want to delete all of your partitions & redo the clean install. Then you will have EFI, MSR, Windows (C:), & Recovery -- all of it belonging to 1909. I'm satisfied your computer can take 1909 because DISM, SFC & Windows system image all worked. Are you satisfied yet that your apps will work in 1909? Then let us proceed to the next step. We have to nuke it all & redo the clean install.

    No wonder the image took so long to make. It included both 1809 (D:) & 1909 (C:). Did it offer E: too & did you select it? Then it's got Win 8.1 too.

    (1) Let's rename the image to keep it separate & distinct from the next one...

    (a) Plug in the external HDD that holds the image.

    (b) Open the WindowsImageBackup folder on it.

          You'll see one folder inside with the name of your computer on it.

    (c) Append "-1909_with_1809" to its name.

    That's the name you'll see, if/when you must restore that image. The next time you make an image, append something to its name too. I delete the oldest one before making a new one, so that I always have three...

    (2) OK, let's practice how to restore it. Boot to any recovery environment. If the computer is completely dysfunctional, you'll still be able to get to the one on your 1909 Installation USB drive.

    (a) Plug in both the Installation USB & the HDD that holds the image, then reboot.

         Or, maybe wait till after (d) to plug in the HDD, in case they can't be told apart.

    (b) Immediately press ESC repeatedly for the Startup Menu.

    (c) Press F9 at that screen for the "Boot Device Options" screen.

    (d) Select the 1909 USB Installation drive to boot to it.

    (e) Click "Repair your computer" instead of to install.

         This will reboot to the recovery environment.

    (f) Then "Troubleshoot > Advanced Options > System Image Recovery" will start the process.

    Do it to see that your image will be offered. But back out as soon as you see it. Don't do a system image recovery until it is necessary. It will restore all the partitions it contains back to where they were at the time the image was made.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-05-26T15:48:15+00:00

    The new 1909 set up changed some of the disk names Here's what file manager says now  D is now some of my old C:\ disk folders the H: is not my usb -it's  not plugged in at the moment; it's another external drive I was getting programs installed from.

    The image back up finished. I think I added this D: because as seen above, here it's not the recovery space any longer. That became E:. Each time I plug in a new drive or USB the identifying Letter all rename themselves except C: instead of just adding the next vacant letter they get rearranged. Naming them didn't help. I don't remember this happening in other, older computers I've had so I thought it was a MS 10 update thing. 

    I am being told that I don't have permission to access most of my folders. Click to continue to permanently get access. Should I do this for every folder?

    .

    Was this answer helpful?

    0 comments No comments