My internet is not that slow. All of the other updates from Microsoft loaded in a couple of minutes today.
This update 20H2, is taking hours to install on all of my 10PRO computers. Why?
Win 10 PRO 10.018363 Build-18363
Your build 18363 is Windows 10 version 1909. To upgrade from that to 20H2 is a full Feature Update that downloads a complete new version of the OS (about 3.8GB), then performs an in-place upgrade. It also creates a windows.old folder and puts your previous Window in it, should you need to go back. This inevitably take a long time. Exactly how long depends on how powerful a CPU your PC has, and whether you have an HDD or an SSD, With an HDD and a modest CPU 'hours' is not unreasonable.
I looked at the timing of this here for the 2004 Feature Update, 20H2 (19042) is basically using the same system files as 2004 (19041) plus a few updates and a small enablement package to bump it up to 20H2, so the timings are comparable.
How long does the 2004 upgrade take using Windows Update?
64 Bit OS
AMD Ryzen 3 3200
4GB memory
1TB digital HD
- - - Updated - - -
It just finished loading and re-booted to normal .....3:20 minutes.
Forgive me, but I am curious: Why would you be upgrading to 20H2 which is no longer supported by Microsoft rather than upgrading to a version that is actually supported?
I don't think the OP had any choice in the matter.
I have found that this is the route typically taken by Windows Update when performing the feature update from 1903/1909.
It seems to be a prerequisite to upgrade first to 20H2 before it is then capable of the feature update by enablement package to 21H2. I'm not sure why, it may be that there's a servicing stack that Windows Update needs before it can go any higher, and that can only be installed after upgrading to 20H2. The feature update from 20H2 to 21H2 is usually offered almost straight away.
@Rapidrob will be pleased to know that going from 20H2 to 21H2 is swift and painless. The small enablement package that performs the feature update installs like a cumulative update, and just as quickly.
LOL. That's a really good call, Bree. I forgot to take that into consideration. For those updates that are simply enablement packages, all the features are already present in the previous version once the latest updates are applied, they simply need to be switched on by use of the enablement package.
Never thought about that because I always update to the latest version right away. For example, most of my machines are already on 22H2.
Again, good call and you educated me with something I had never considered.
I had not considered it until recently either, I had assumed that if you stuck with an unsupported version until Windows Update forced the upgrade on you it would go straight to 21H2.
But I had deliberately left a VM on 1909 and left it to see if/when MS would force it to upgrade. That was not until a few months ago, MS seem to have been really slow/cautious at forcing upgrades this time round. Windows Update took mine to 20H2 first, only then did it offer 21H2. Others who have stuck with 1909 for as long as they could get away with have reported the same.
Quote