Feature update to Windows 10, version 20H2 not downloading.  

Ghot said:

After you grab any outstanding updates, open a command prompt as admin, and run sfc /scannow

Matthew Wai said:

Or more specifically, right-click on the Start button --> Windows PowerShell (Admin).
Run SFC /ScanNow

Well, I've run into some big problems. Windows Update was saying that I needed to restart to finish installing some update, so I decided to do that before anything else. The computer got stuck on the restarting screen, and after about two hours, I realized it was never going to get unstuck. I pushed the button on the computer to shut it down manually.

Both before and after the reboot, the computer has been behaving sluggishly. Something seems wrong with Windows now. I think I should restore my system to its pre-update state using the most recent Macrium backup from before the in-place update, then try the update again differently (possibly without checking for updates first). Should I proceed?

Ghot said:

Yes.
Restore to backup before the in-place upgrade.
Then, do the in-place upgrade again... following the directions exactly, in the tutorial.
Then, after that's done... make another backup.
Then do the updates.

I'm currently holding off on doing the in-place upgrade, as Windows Update automatically started downloading Version 20H2, and so far seems to be downloading it successfully. It's up to 7% now. I intend to try updating normally, and proceeding with the in-place upgrade only if that doesn't work.

- - - Updated - - -

The update finished downloading and prompted me to restart. After I restarted, it installed successfully. Everything seems to be working well so far.

Matthew Wai said:

Or more specifically, right-click on the Start button --> Windows PowerShell (Admin).
Run SFC /ScanNow

Every now and then, I run the system file checker to make sure there's nothing wrong with Windows, but I usually do it through the Command Prompt. Is there any benefit to using Powershell instead?

hbenthow said:

I usually do it through the Command Prompt. Is there any benefit to using Powershell instead?

Both work. I suggest PowerShell just because it is on the right-click Start menu, while Command Prompt is not. It is convenient to open a PowerShell window.

Matthew Wai said:

Both work. I suggest PowerShell just because it is on the right-click Start menu, while Command Prompt is not. It is convenient to open a PowerShell window.

Ah, I see.

Thank you for all of the help. Everything seems to be working correctly, so I'll mark the thread as solved.