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-06T04:26:37+00:00

    (1) Yeah, sounds like SFC is not the solution. DISM & SFC do often disappoint. Even when they do run successfully (even "fixing" something), the problem they were run for doesn't go away. That sounds like a sin, but I guess it means the problem is something other than a bad system file. But does it work in Windows too now? We want it to work there.

    (2) That clarification makes me think the Built-In Administrator is turned ON. What is the reason for that? Careful, though, don't turn it off unless there is at least one other Administrator account. That would be a bundle of trouble fixed only with a clean install or a system image restore. Is that the password you have forgotten, the one for the Built-In Administrator?

    (3) "A lot of type came up which I thought you'd like to see"

    You can copy text at any Command Prompt by selecting it with the mouse (or use Ctrl-A to select all of it), then press Ctrl-C. After that, type "Notepad" at the Command Prompt, & paste it (Ctrl-V) into a text file. The file will be there after you boot back to Windows. Practice it while booted to Windows to see what you've got to click & type into the name box. Be sure to give it a name you can remember, in case it ends up in a folder you didn't intend. And be sure to keep the file type ".txt" but not the asterisk.

    (4) "And the D drive had the Windows and user folders not C so I used D:"

    Very good. Here is how to fix that. Manually switch the letters once. This presumes, of course, that List Vol shows C:\ & D:\ get switched as before...

    (a) Shift+Restart for the recovery environment.

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

    (c) Enter...

    DiskPart

    List  Vol <<< This shows the volumes with their drive letters.

                                                I will use "x" & "y", you must use the actual numbers.

    Select  Vol  x              <<<  Select the one that has the letter "C".

    Remove  Letter=C      <<< Removes the letter "C".

    List  Vol  <<< You should see "C" is gone.

    Select  Vol  y              <<<  Select the one that has the letter "D".

    Remove  Letter=D     <<< Removes the letter "D".

    List  Vol  <<< You should see "D" is gone.

    Assign  Letter=C        <<< What was "D" is now "C".

    List  Vol  <<< You should see "C" is added.

    Select  Vol  x               <<< Goes back to "x".

    Assign  Letter=D         <<< What was "C" is now "D".

    List  Vol                        <<< You should see the letters have switched.

    Exit

    (d) Exit the Command Prompt with its "X" or type "Exit".

    (e) Click "Continue" to get back to Windows.

    After doing that once, the next time you go into the recovery environment, you should see they won't have switched again. At least, they haven't switched back for me. It is strange -- when I boot to my internal 1909 recovery environment -- a letter is added to my Recovery drive. It doesn't show up in Windows. And it doesn't show up in the external 1909 environment. But it was getting the letter "C" & Windows was changed to "E". But I switched them to normal, & they've stayed switched.

    Edit:  Yep -- it's still holding...

    Microsoft Windows [Version 10.0.18362.175]

    (c) 2019 Microsoft Corporation. All rights reserved.

    X:\windows\system32>diskpart

    Microsoft DiskPart version 10.0.18362.1

    Copyright (C) Microsoft Corporation.

    On computer: MININT-ORVBH16

    DISKPART> list vol

      Volume ###  Ltr  Label               Fs         Type             Size        Status      Info

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

      Volume 0       E                                        DVD-ROM         0 B   No Media

      Volume 1       C   PCR Hard        NTFS     Partition      930 GB   Healthy

      Volume 2       F   WinRE 1909     NTFS     Partition      847 MB  Healthy

      Volume 3            ESP                  FAT32    Partition        99 MB  Healthy    Hidden

      Volume 4      D   ESD-USB1909  FAT32    Removable    14 GB   Healthy

    DISKPART>

    Windows (C:) still has its C: in the internal recovery environment. WinRE 1909 got bumped to F: because my 1909 Installation USB (ESD-USB 1909) was plugged in. When I then booted to the USB's external environment, WinRE 1909 had no letter, the USB was D: -- & C: still was C:.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-05-06T01:29:32+00:00

    OK. That's something to work with. But...

    One thing: Your prior post sounds like you've got the Built-In Administrator account turned ON. That's really for temporary use in an emergency. It isn't full-functioning. Are you doing these update attempts while signed into that? You should sign into your user account instead, which preferably should also be an Administrator account.

    Don't turn**off the Built-In Administrator, though, unless you've got at least one normal Administrator account. Either make the existing user account an Administrator or create a new one. Then, turn off the Built-In one. Need instructions?

    Edit:  I'm having trouble understanding that SetupDiag report. Some of what I find on it is scary to suggest. I think we should fix the drive letter problem & resolve the Administrator account issue. Ensure we have a normal Administrator account, then run the upgrade again. But run it from the USB drive instead of through Windows Update. To do that...

    Plug it in, open it in File Explorer, & click "Setup.exe". Run this way, it will ask whether to keep files & apps. Be sure to say yes. If it fails, post the new SetupDiagResults.log.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-05-06T01:10:09+00:00

    Here's what Setup Diag result's log.

    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

    Was this answer helpful?

    0 comments No comments