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-23T19:32:28+00:00

(1)Without the usb plugged in

BCDEdit /Set description "Win 1809"

BCDEdit /Set {default} description "Win 1909"

(I put then im at the same time)

This is what I get:

Microsoft Windows [Version 10.0.17763.557]

(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>BCDEdit /Set description "Win 1809"

The operation completed successfully.

C:\WINDOWS\system32>

C:\WINDOWS\system32>BCDEdit /Set {default} description "Win 1909"

The operation completed successfully.

C:\WINDOWS\system32>

When I was still originally in 1909 (USB still plugged in from install) I did set up email (I forwarded something to myself to see that it worked okay) and I could use some of the internet but it wouldn't let me send a reply here. Everything was really, really slow to respond. it didn't ask for router passwords but WWW was up and running though again really slow and timed out several times.

Question - Am I suppose to be running off the USB to get into1909? Because when starting i'm given a choice as I said, one is Windows 10 and the other is Win 1909, though they both say that they're 1809 in System >About. even after doing

BCDEdit /Set description "Win 1809"

BCDEdit /Set {default} description "Win 1909"

I thought to click the above change product key or upgrade your edition of windows but I don't know if that was going to mess something up. So I didn't.

.
Was this answer helpful?

0 comments No comments
Anonymous

2020-05-23T20:23:45+00:00

(1) While in 1809...

(a) Enter: BCDEdit /Set description "Win 1809" (forget the other one)

(b) Let me see a BCDEdit & an MSConfg again.

(2) Are you still seeing volume 4 & 5 at boot now?

(3) And 5 is on top, & it leads to 1909?

(4) And this is the boot option screen -- or does it look different?

Too bad I still don't quite really recall that, & I can't easily find mention of it on the NET. Too bad I suggested the second one would probably be 1909, but it was the first -- volume 5. I'm thinking we should undo this dual boot & try it again. I'm thinking -- by booting into 1809 (volume 4) before the process was done -- things got messed up & may still be incomplete.

This time, we'll stick with the top one (volume 5) all the way through the complete install process. Let me see those items, then I'll post how to undo it.
Was this answer helpful?

0 comments No comments
Anonymous

2020-05-23T20:53:58+00:00

1a) resultsBCDEdit /Set  description "Win 1809"

Microsoft Windows [Version 10.0.17763.557]

(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>BCDEdit /Set description "Win 1809"

The operation completed successfully.

1b) result BCDEdit

C:\WINDOWS\system32> BCDEdit

Windows Boot Manager

identifier              {bootmgr}

device                  partition=\Device\HarddiskVolume2

path                    \EFI\Microsoft\Boot\bootmgfw.efi

description             Windows Boot Manager

locale                  en-US

inherit                 {globalsettings}

default                 {default}

resumeobject            {d9e3b86e-78e0-11e9-84e8-a4ddf41949bd}

displayorder            {default}

                        {current}

toolsdisplayorder       {memdiag}

timeout                 300

Windows Boot Loader

identifier              {default}

device                  partition=F:

path                    \Windows\system32\winload.efi

description             Win 1909

locale                  en-US

inherit                 {bootloadersettings}

recoverysequence        {d5a66151-9c6d-11ea-b841-881b5a4be9d0}

displaymessageoverride Recovery

recoveryenabled         Yes

isolatedcontext         Yes

allowedinmemorysettings 0x15000075

osdevice                partition=F:

systemroot              \Windows

resumeobject            {d5a6614f-9c6d-11ea-b841-881b5a4be9d0}

nx                      OptIn

bootmenupolicy          Standard

Windows Boot Loader

identifier              {current}

device                  partition=C:

path                    \WINDOWS\system32\winload.efi

description             Win 1809

locale                  en-US

inherit                 {bootloadersettings}

recoverysequence        {96cdf572-78bf-11e9-a9d7-e86d93e6c8ae}

displaymessageoverride CommandPrompt

recoveryenabled         Yes

isolatedcontext         Yes

allowedinmemorysettings 0x15000075

osdevice                partition=C:

systemroot              \WINDOWS

resumeobject            {d9e3b86e-78e0-11e9-84e8-a4ddf41949bd}

nx                      OptIn

bootmenupolicy          Standard

C:\WINDOWS\system32>

1b) MSConfig

not sure if this is what you wanted

I haven't rebooted from the USB again yet, I wasn't sure what it would mess up if anything but I'll give it a try and let you know the rest.

.
Was this answer helpful?

0 comments No comments