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

141 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-05-22T17:11:13+00:00

    No tears. Okay got thru the install. Nothing seems to have exploded, in fact it all looks the same. I chose the second Windows 10 (descending) version 4; the first one was 5. I'm still in 1809 from start up.

    Oh I got this message when choosing the 150 space.  I clicked continue anyway.

    Windows Setup

    The partitions on this disk selected for installation are not in the recommended order. For additional information about the installing to GPT disks go to the Microsoft website (www.microsoft.com) and search GPT.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-05-22T21:57:38+00:00

    (1) That's great that no calamity has occurred as yet. I'm overjoyed.

    (2) I did mine a few years ago. I don't recall that error message, but my existing installation didn't have extra partitions. I had already deleted Dell's factory recovery partition & my own leftover Win 8.1 recovery environment partition. Seems like you made the right choice to click through it.

    (3) I don't recall version numbers on the boot choices. Both of mine said "Windows 10" until I renamed one. Boot to 1909, then...

    (a) Let's see a BCDEdit from an Administrator Command Prompt...

    Microsoft Windows [Version 10.0.18363.836]

    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>BCDEdit

    Windows Boot Manager

    identifier                {bootmgr}

    device                    partition=\Device\HarddiskVolume1

    path                       \EFI\Microsoft\Boot\bootmgfw.efi

    description            Windows Boot Manager

    locale                     en-US

    inherit                    {globalsettings}

    badmemoryaccess     Yes

    default                   {current}

    resumeobject         {7f582e76-a2f7-11e9-86db-c6c7375e4034}

    displayorder           {current}                           <<< You'll have two items under displayorder

    toolsdisplayorder   {memdiag}

    timeout                  30                                     <<< The boot screen lasts this long till the default loads

    Windows Boot Loader                                    <<< You'll have two Boot Loaders

    identifier                         {current}

    device                             partition=C:

    path                                \WINDOWS\system32\winload.efi

    description                     Windows 10            <<< This shows up on the boot screen & in MSConfg

    locale                              en-US

    inherit                             {bootloadersettings}

    recoverysequence           {7f582e78-a2f7-11e9-86db-c6c7375e4034}

    displaymessageoverride  CommandPrompt

    recoveryenabled             Yes

    badmemoryaccess          Yes

    isolatedcontext               Yes

    allowedinmemorysettings    0x15000075

    osdevice                         partition=C:

    systemroot                     \WINDOWS

    resumeobject                 {7f582e76-a2f7-11e9-86db-c6c7375e4034}

    nx                                   OptIn

    bootmenupolicy            Standard

    C:\WINDOWS\system32>

    (b) Type MSConfg into Search, & show a picture of the Boot tab...

    (4)

    (a) How do you like 1909?

    (b) Have all the drivers seem to have installed?

    (c) Can you do an SFC?

    (d) Can you make a Windows system image backup?

    (e) Do your programs seem to install & run well in it?

    If your answers are mostly yes -- especially to (d) -- we should redo the clean install, this time wiping all the partitions at the "choose where to install" screen. You'll select them one by one & click "delete". Then select the huge unallocated space (which will be all that's left), & click next.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-05-22T23:41:44+00:00

    3a)This is the BCDEdit

    Microsoft Windows [Version 10.0.17763.557]

    (c) 2018 Microsoft Corporation. All rights reserved.

    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             Windows 10

    locale                  en-us

    inherit                 {bootloadersettings}

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

    recoveryenabled         Yes

    isolatedcontext         Yes

    allowedinmemorysettings 0x15000075

    osdevice                partition=F:

    systemroot              \Windows

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

    nx                      OptIn

    bootmenupolicy          Standard

    Windows Boot Loader

    identifier              {current}

    device                  partition=C:

    path                    \WINDOWS\system32\winload.efi

    description             Windows 10

    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>

    3b) MSCONFIG

    4)It still says I have 1809

    a) Maybe I should have picked 5 instead of 4?

    .

    Was this answer helpful?

    0 comments