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-01T01:51:36+00:00

    I was able to download v8.7 without their asking for my email address from their Changelogs page...

    https://www.diskpart.com/changelog.html

    AOMEI Partition Assistant Changelogs

    They fixed the issue I suffered long ago acc. to those logs. So now my guilt is doubled I never sent them any money. Anyway...

    It's easier to get MBs off C: using Disk Management because it requests MBs (not GBs)...

    (1) Right click START, & select Disk Management.

    (2) Right-click C:partition, & select "Shrink Volume".

    (3) Put 49 into the "amount of space to shrink" box.

    (4) Click the Shrink button, & reboot if/when requested.

    Now you will have 49 MB of unallocated space to give to the 450 MB Win 10 Recovery partition. It will lift it to 499 MB. I don't want to go past that because that same article I quoted above says, "If the partition is 500 MB or larger, it must have at least 320 MB of free space" -- sheesh.

    After that, AOMEI Partition Assistant can expand your Win 10 Recovery partition leftward...

    (1) Ensure Disk 1 is showing in the top, right pane by clicking it in the bottom, right pane.

         Yep, AOMEI calls it Disk 1 where Disk Management says Disk 0.

    (2) Right-click your 450 MB Win 10 Recovery drive, & select "Resize/Move Partition".

         It will be just to the right of the Windows (C:) partition.

    (3) Drag the circle at left of the partition all the way leftward.

         Ensure the whole partition doesn't reposition. You just want the left boarder going left.

    (4) Click the "OK" button.

         Note: There is no Cancel button, but the Close (X) button serves as Cancel.

    (5) After that, the instructions say, "By clicking OK a partition resizing or moving operation will be added to pending operations list, and the new partition structure will be graphically represented in the Partition Assistant main window". I recall it was like that in v.6.3 too. There'll be a button to click to execute the "pending operations". If you don't click it, nothing will actually get done.

    (6) Finally, let us see the attributes & type of the Recovery partition as you did before. Also, show us a ReagentC /Info. If anything has gone amiss with those, we can set it right.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-05-01T03:02:12+00:00

    Was with you til "Finally" LOL Do you mean  Window RE tools - 1023 MB? No 1909. Do you want me to add 49 MB to Windows RE tools?

    ReagentC /Info

    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>

    Glad you know what all this means.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-05-01T03:21:51+00:00

    The one with the label (Window RE tools) is an empty Win 8.1 recovery partition. Forget that. The 450 MB OEM partition is your 1809 Recovery partition (SetupDiagResults.log says 10.0.17763 = 1809). That's the one we are concerned with. We'll see what happens after you successfully upgrade to 1909. I never got a 3rd one, but others have reported it.

    But hold off. I just did the whole process, myself, & will post the result with a ton of pictures. As the old v.6.3, v.8.7 messed with the GPT Attributes. They are easily set right. I haven't done a reboot yet -- was never asked. Let me do it now, & I'll write up the whole thing.

    Was this answer helpful?

    0 comments