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-04-30T03:24:40+00:00

Microsoft Windows [Version 10.0.17763.557]

(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>ReagentC /Info

Windows Recovery Environment (Windows RE) and system reset configuration

Information:

    Windows RE status:         Enabled

    Windows RE location:       \?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE

    Boot Configuration Data (BCD) identifier: 96cdf572-78bf-11e9-a9d7-e86d93e6c8ae

    Recovery image location:   \?\GLOBALROOT\device\harddisk0\partition6\RecoveryImage

    Recovery image index:      2

    Custom image location:

    Custom image index:        0

REAGENTC.EXE: Operation Successful.

C:\WINDOWS\system32>DiskPart

Microsoft DiskPart version 10.0.17763.1

Copyright (C) Microsoft Corporation.

On computer: MYPC

DISKPART> Select Disk 0

Disk 0 is now the selected disk.

DISKPART> List Part

Partition ### Type              Size     Offset

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

Partition 1    Recovery          1023 MB 1024 KB

Partition 2    System             360 MB 1024 MB

Partition 3    Reserved           128 MB 1384 MB

Partition 4    Primary            919 GB 1512 MB

Partition 5    Recovery           450 MB   921 GB

Partition 6    Primary             10 GB   921 GB

DISKPART> Select Part 5

Partition 5 is now the selected partition.

DISKPART> Detail Part

Partition 5

Type    : de94bba4-06d1-4d40-a16a-bfd50179d6ac

Hidden : No

Required: Yes

Attrib : 0X8000000000000001

Offset in Bytes: 988986474496

Volume ### Ltr Label        Fs     Type        Size     Status     Info

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

* Volume 7                      NTFS   Partition    450 MB Healthy    Hidden

DISKPART> Exit

Leaving DiskPart...

C:\WINDOWS\system32>
Was this answer helpful?

0 comments No comments
Anonymous

2020-04-30T04:35:48+00:00

Those attributes & type look good to me. I thought at least one would be bad to explain why Disk Management calls it OEM. I'll have to research another reason why it is called OEM & whether that is a problem to either the upgrade to 1909 or to the failure of the image backup.

But size seems to matter, going by that article I posted. Would you like to add 10/so MB to the size of that Recovery Tools partition? You'll have to choose a 3rd-party app to do it. I use AOMEI Partition Assistant, but when I go to its site for the free version, it asks for my email address...

https://www.aomeitech.com/pa/standard-edition.html

AOMEI Partition Assistant Standard 8.7

I'm pretty sure I wasn't asked back when I took it. I certainly don't get emails from them. But my version is 6.3, & I may decide to go for the new one. Mine did cause a problem once when I did a delete & shift in one "easy" step. It's how I got EFI to be first on my drive. Hopefully the new one has a cure.
Was this answer helpful?

0 comments No comments
Anonymous

2020-04-30T05:46:00+00:00

I installed AOMEI Partition Assistant Standard 8.7 But Im not sure what I need to do. I don't want to mess it up. Yes they wanted an email for customer support they said.

Could any of this partition issues be why scannow won't work either? I figured there was something wrong somewhere in my OS since downloads, repairs and troubleshooter kept failing. I discovered sfc /scannow no longer worked either when i tried to find out what was going wrong.
Was this answer helpful?

0 comments No comments