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-12T03:08:33+00:00

Well it was shorter than some other fails.

Matching Profile found: FindAbruptDownlevelFailure - 55882B1A-DA3E-408A-9076-23B22A0472BD

SetupDiag version: 1.6.0.0

System Information:

    Machine Name = MYPC

    Manufacturer = Hewlett-Packard

    Model = 21-h013w

    HostOSArchitecture = x64

    FirmwareType = UEFI

    BiosReleaseDate = 20140616000000.000000+000

    BiosVendor = 80.10

    BiosVersion = 80.10

    HostOSVersion = 10.0.17763

    HostOSBuildString = 17763.1.amd64fre.rs5_release.180914-1434

    TargetOSBuildString = 10.0.18362.770 (19h1_release_svc_prod1.200309-1836)

    HostOSLanguageId =

    HostOSEdition = Core

    RegisteredAV = Windows Defender

    FilterDrivers = FileInfo

    UpgradeStartTime = 5/5/2020 3:31:35 PM

    UpgradeEndTime = 5/5/2020 4:43:01 PM

    UpgradeElapsedTime = 01:11:26

    CV = tFmz9P/b8E2yPqUB

    ReportId = F0D3CCB9-6371-48A0-AE2E-8679485A4EE3

Error: SetupDiag reports abrupt down-level failure.

Last Operation: Finalize

Error: 0x8007007E - 0x50015

LogEntry: 2020-05-05 16:41:26, Error                 DISM   DISM Driver Manager: PID=18924 TID=20744 Failed trying to load drvstore.dll - CDmiApi::InternalInitialize(hr:0x8007007e)

Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information.

Last Setup Phase:

Phase Name: Pre-Finalize

    Phase Started: 5/5/2020 4:39:25 PM

    Phase Ended: 1/1/0001 12:00:00 AM

    Phase Time Delta: 00:00:00

    Completed Successfully? False

Last Setup Operation:

Operation Name: Process Drivers for Migration

    Operation Started: 5/5/2020 4:41:18 PM

    Operation Ended: 1/1/0001 12:00:00 AM

    Operation Time Delta: 0:00:00:00.0000000

    Completed Successfully? False

SetupDiag was unable to match to any known failure signatures.

System Information:

    Machine Name = MYPC

    Manufacturer = Hewlett-Packard

    Model = 21-h013w

    HostOSArchitecture = x64

    FirmwareType = UEFI

    BiosReleaseDate = 20140616000000.000000+000

    BiosVendor = 80.10

    BiosVersion = 80.10

    HostOSVersion = 10.0.17763

    HostOSBuildString = 17763.1.amd64fre.rs5_release.180914-1434

    TargetOSBuildString = 10.0.18362.770 (19h1_release_svc_prod1.200309-1836)

    HostOSLanguageId =

    HostOSEdition = Core

    RegisteredAV = Windows Defender

    FilterDrivers =

    UpgradeStartTime = 5/11/2020 8:11:14 PM

    UpgradeEndTime = 5/11/2020 8:14:59 PM

    UpgradeElapsedTime = 00:03:45

    CV = tFmz9P/b8E2yPqUB

    ReportId = F0D3CCB9-6371-48A0-AE2E-8679485A4EE3

SetupDiag was unable to match to any known failure signatures.

System Information:

    Machine Name = MYPC

    Manufacturer = Hewlett-Packard

    Model = 21-h013w

    HostOSArchitecture = 1033

    FirmwareType = UEFI

    BiosReleaseDate = 20140616000000.000000+000

    BiosVendor = 80.10

    BiosVersion = 80.10

    HostOSVersion = 10.0.17763

    HostOSBuildString = 17763.1.amd64fre.rs5_release.180914-1434

    TargetOSBuildString = 10.0.18362.770 (19h1_release_svc_prod1.200309-1836)

    HostOSLanguageId =

    HostOSEdition = Core

    RegisteredAV = Windows Defender

    FilterDrivers =

    UpgradeStartTime = 5/11/2020 8:11:14 PM

    UpgradeEndTime = 5/11/2020 8:14:59 PM

    UpgradeElapsedTime = 00:03:45

    CV = tFmz9P/b8E2yPqUB

    ReportId = F0D3CCB9-6371-48A0-AE2E-8679485A4EE3
Was this answer helpful?

0 comments No comments
Anonymous

2020-05-12T01:43:09+00:00

At least it came in a pretty little box & asked for your approval. Was it quick? Let's see SetupDiagResults.log.
Was this answer helpful?

0 comments No comments
Anonymous

2020-05-11T23:53:35+00:00

This is what I got. Ugh!!
Was this answer helpful?

0 comments No comments