v.2004 CU & v.20H2 FU

Not a problem or question, but today, I unpaused WU and let it run updates. The CU KB5001330 for v.2004 took 2 hours to run and complete. No problems, nor errors. I followed this with the FU to v.20H2, also from WU. The FU took 25 minutes. I know 20H2 isn't much of an update, but it sort of surprised me it was so short. I suppose if I had done the FU without the preceding CU, It would have run longer? Anyway, just an observation. Now on to a system image backup and a recovery CD.

jamis said:

...The CU KB5001330 for v.2004 took 2 hours to run and complete.... I followed this with the FU to v.20H2, also from WU. The FU took 25 minutes. I know 20H2 isn't much of an update, but it sort of surprised me it was so short.....

the FU from 2004 to 20H2 is a small enablement package that just turns on dormant features that are already in your 2004 system files. It installs like a CU.

The KB5001330 CU would be expected to take longer than a typical CU. It not only installs the usual patches and security fixes, but this one also is tasked with removing the Legacy Edge from your system. The Chromium Edge update didn't do that, it just hid Legacy Edge. On top of that, KB5001330 also installs the latest service stack update (from now on they will be rolled up into the CUs). There's a lot of work to do and, particularly on an HDD system, will inevitably take a lot of time.

Having said that, 2 hours seems too long for the i5-2320 system in your specs, my System One with a Pentium B950 did it in a little over an hour.

Tekkie Boy said:

From what I've heard, it can take a long time on computers with HDD....

Yes, I can confirm that. My System One has an HDD, it was much faster on my machines with SSDs...

... I don't know whether Norton is also slowing down the update.

I suspect you are correct there.

Thanks for the superb explanations. Norton was indeed active during both updates, but had little activity compared to the Windows Installer program that was using nearly all of the CPU usage and was hitting the hard drive pretty hard. The drive is far from full (280GB out of 916GB), but it's not new technology either. Bree's explanation of what the CU was doing is a lot more than I expected and likely explains why there were several periods where the percentage complete display appeared to "stick" for a long time. Again, no issues from either update, Thanks again for the education!