sfc /scannow WILL NOT function

Anonymous

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.

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

(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.

0 comments

Answer accepted by question author

Anonymous

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?

0 comments

141 additional answers

Anonymous

2020-05-12T10:05:46+00:00

(1) Those DiskPart's look OK to me. The 1809 & 1909 environments are getting the same letters. C & D remain as in Windows, & the empty Win 8.1 Recovery partition (Windows RE) gets no letter. Though the 1809 environment is adding an extra letter (H) to the 1809 Recovery partition (492 MB), at least it doesn't muss any of the other letters. I'm pretty sure it didn't happen to me when mine was 1809. But it happens to me now that it is 1909. It appears to afflict our internal environments, but not the external ones.

I guess the letters are not the problem. But it sure looked like it might have been before.

(2) "I thought BT was supposed to clean itself up"

(a) The one from your upgrade to 1809 probably disappeared long ago. This one likely is getting started during the 1909 upgrade attempts but isn't getting cleared after the failures. What shows up at "START, Settings, System, Storage, Temporary Files"? Everything there is expendable -- exceptfor Downloads. If there is a "Previous Windows Installation(s)" item, select it to delete $Windows_~BT. Also, there may be a "Windows update cleanup" item (or something like that) that should be selected & deleted. It might be a good idea to do this after each failed upgrade attempt.

(b) I don't like seeing that $AV_AVG folder. Have you installed the AVG anti-virus? Your SetupDiag reports are showing Windows Defender to be the active anti-virus app, which is good & all one needs. If it is just turned off, I would fully uninstall AVG. But, if you never made it the Real-Time scanner, I guess it would be OK to keep it to run On-Demand as a secondary.

(3) Yeah, Reliability History looks pretty bad. Copy/paste the details of those 3 red X's.

(4) There is too much going on at Windows Update. It could be why your internet is slow. We should have checked that before trying the upgrade. I'm sorry I didn't think of it. Download WUShowHide...

https://support.microsoft.com/en-us/help/3183922/how-to-temporarily-prevent-a-windows-update-from-reinstalling-in-windo

WUShowHide

It looks like 1909 has started coming in at Windows Update again. See whether you can block it with WUShowHide. If it has come too far, you might have to let it complete & fail. Then catch it when it starts to download again.

(a) We want to stop the upgrade attempts until after 1809 is fully updated with those NET Framework updates & any others that may be coming.

(b) Maybe even block 2 NET framework updates so that one at a time comes in.

To block them, click Hide Updates, put a check into it, then click next. To unblock them, click Show Hidden Updates.

============

It looks like I'm soon to get KB4497165. It hasn't shown up at Windows Update yet.
Was this answer helpful?

0 comments No comments
Anonymous

2020-05-12T04:59:56+00:00

Yes I compared the setupDiag with the ones I've sent and they appear to be the same except near the bottom with a different date.

Command prompt - signed under my account on both reciveries

1809

Microsoft Windows [Version 10.0.17763.1]

(c) 2018 Microsoft Corporation. All rights reserved.

X:\windows\system32>Diskpart

Microsoft DiskPart version 10.0.17763.1

Copyright (C) Microsoft Corporation.

On computer: MININT-40BVC8O

DISKPART> list vol

Volume ### Ltr Label        Fs     Type        Size     Status     Info

---------- --- ----------- ----- ---------- ------- --------- --------

Volume 0     G                       DVD-ROM         0 B No Media

Volume 1         Windows RE   NTFS   Partition   1023 MB Healthy

Volume 2     C   Windows      NTFS   Partition    919 GB Healthy

Volume 3     H                NTFS   Partition    492 MB Healthy

Volume 4     D   Recovery Im NTFS   Partition     10 GB Healthy

Volume 5         SYSTEM       FAT32 Partition    360 MB Healthy    Hidden

Volume 7     F   ESD-USB      FAT32 Removable     32 GB Healthy

DISKPART> exit

Leaving DiskPart...

X:\windows\system32>notepad

X:\windows\system32>

1909

Microsoft Windows [Version 10.0.18362.592]

(c) 2019 Microsoft Corporation. All rights reserved.

X:\Sources>Diskpart

Microsoft DiskPart version 10.0.18362.1

Copyright (C) Microsoft Corporation.

On computer: MININT-3VHFEEK

DISKPART> list vol

Volume ### Ltr Label        Fs     Type        Size     Status     Info

---------- --- ----------- ----- ---------- ------- --------- --------

Volume 0     G                       DVD-ROM         0 B No Media

Volume 1         Windows RE   NTFS   Partition   1023 MB Healthy

Volume 2     C   Windows      NTFS   Partition    919 GB Healthy

Volume 3                      NTFS   Partition    492 MB Healthy

Volume 4     D   Recovery Im NTFS   Partition     10 GB Healthy

Volume 5         SYSTEM       FAT32 Partition    360 MB Healthy    Hidden

Volume 6     F   ESD-USB      FAT32 Removable     32 GB Healthy

DISKPART> exit

Leaving DiskPart...

X:\Sources>notepad

X:\Sources>

This is what File Explorer says (minus my seagate)![](https://learn-attachment.microsoft.com/api/attachments/97533efa-6241-48ed-87d1-b7fb7bc61ec0?platform=QnA

I was wonder is this something amiss ![](https://learn-attachment.microsoft.com/api/attachments/60302815-6946-4661-910b-2925cce1855d?platform=QnA

I thought BT was supposed to clean itself up after installs or near installs. Maybe I got it mixed up with something else.

Reliability looks bad.

The shutdown was because everything froze.

Don't know if you want to see every tech error.

.
Was this answer helpful?

0 comments No comments
Anonymous

2020-05-12T04:05:35+00:00

It appears SetupDiag appended its new report (dated 5/11/2020) to the one made on 5/5/2020. And this new one looks a lot like the one you showed on page 2 of this thread dated 4/27/2020. They say: "SetupDiag was unable to match to any known failure signatures". So -- we're on our own.

(1) Did it mess up the drive letters again?

(a) Plug in the 1909 Installation USB drive.

(b) Shift+Restart to the 1809 environment.

(c) "Troubleshoot > Advanced Options > Command Prompt"

(d) Show a DiskPart, List Vol, from its Command Prompt.

(e) Exit back to its Choose an Option screen.

(f) Click "Use a Device" to boot to the 1909 USB.

(g) Click "Repair your computer" for the 1909 recovery environment.

(h) Let's see the List Vol there too.

(2) How do things look at "START, Settings, Update & Security, Windows Update"? Is there any message there? Anything waiting to come in?

(3) Let's see any message in Reliability History (type into Search). Click the day (5/11/2020), then click "View technical details" for any item with a red X...

(4) They say, by the end of this month, Win 10, version 2004, will be out. But I think we should pursue the installation of 1909 & face that one when it comes.
Was this answer helpful?

0 comments No comments