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-25T01:38:29+00:00

    (1) The NET should be working well in 1909. KB4556799 is currently the latest cumulative update. It installed well for me, but maybe is doing more for you. How far back is your OS Build at System>About compared to the list of cumulative here...?...

    https://support.microsoft.com/en-us/help/4556799/windows-10-update-kb4556799

    May 12, 2020—KB4556799 (OS Builds 18362.836 and 18363.836)

    Maybe it just has too much to do. It can be blocked with WUShowHide, but, especially if the computer is far back, you really ultimately want it in. I guess the fact it constantly fails & retries could be slowing the NET. Normally, when I take in a cumulative, I just sit & watch it till it's done. Also, at boot, I put an eye on "right-click Taskbar, Task Manager". If anything is at or near 100%, I let it subside before doing anything of my own.

    (2) I think 1909 hadn't completed its install before you pulled the USB drive & booted into 1809 (volume 4). Finally it does sound like it has completed (except for updates), but I fear having interrupted it with all those boots to 1809 might have had an untoward effect, though I don't really know.

    I like that the "volume" stuff has gone & you get a normal boot menu. If you undo the dual boot & try again & see volumes again, you will know which to pick (volume 5). When you get to the normal boot menu, it will have "Windows 10" on top probably, & "Win 1809" will still be there anyway. I would continue to boot & reboot into 1909 until it has completed its updates.

    My suggestion is to undo it & retry for a better result.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-05-25T00:19:15+00:00

    I got into 1909, but had to go back into 1809 to send this. Tried multiple times yesterday and today to read and reply from within 1909 but it just won't work. Defender may be set wrong because it says this is a malicious site.

    (I got into 1909 but this is what I ended doing - tried again without the USB as you said, no go, same thing happened still said 1809 even though I chose 1909 and that was the choices. So I rebooted with the USB in (before you said not to) and it gave me a new choice Win 1909 or Win 1809 Change defaults or choose other options. Clicked 1909; it worked. Restarted again without the USB and got the new options again, it probably had to restart a couple times to wake it up. )

    System>About says 1909 YEAH! I hope.

    That Volume window didn't show up this time either. So yes, the first one must have bee 1909. Good to know. The choices now are Win 1909 (on top) Win 1809 (on bottom). File manager has Local Disk (C:) Windows (D:); D has my old folders plus a bunch I don't recognize.

    I forgot to write that yes I've been downloading since I got into it before, they're just really slow-lousy internet again which seems to be much worse I hope that's not 1909 . Troubleshooter says it can't identify the problem with the internet as usual, been through this a thousand times and have done the unplug, replug, stopped almost all the background apps and so on.

    Just got have all the updates but one installed - left the computer on all day all night but 2020-05 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4556799) has yet to complete an install keeps saying to retry which I have tried several times. Is it really important?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-05-23T21:12:31+00:00

    (1) There's no need to boot to the USB except to reinstall or to get into its recovery environment.

    (2) That /Set command is only changing the descriptionshown for the partitions in the boot selection screen & in MSConfg.

    (3) To boot to 1909, choose that one from the boot screen. Check "START, Settings, System, About" to know for real it is 1909. If it doesn't say so there, something is wrong. Are you sure both choices say 1809? It sure sounded like 1909 installed somewhere. And it looks it too in BCDEdit & MSConfg.

    (4) What about those questions I asked about "volume"?

    (5) Have you gone into 1909 & done the things I suggested -- Windows Update, etc.? And -- if you are in 1909 & asked to reboot -- make sure the reboot is back to 1909. Same for 1809.

    Edit:  Well, here is how to undo the dual boot, if you have determined the 1909 installation cannot be improved...

    (1) Boot to 1809.

         (Check you are there at About.)

    (2) Open MSConfg, Boot tab.

         It should look just as in your picture.

    (3) Select the Win 1909 boot entry, & click Delete.

         Follow whatever instructions, then close MSConfg with the OK button. Reboot, if asked.

         BCDEdit should now show only the Windows Boot Loader named Win 1809 remains.

    (4) Open Disk Management.

    (5) Right-click the 1909 partition (between C: & D:), & select Delete Volume.

         It should return to unallocated space. Reboot, if asked.

    That's about it. If you haven't been asked to reboot by the end, do one now anyway. Then I think we should try the dual boot once more.

    Was this answer helpful?

    0 comments No comments