v.2004 CU & v.20H2 FU


  1. Posts : 509
    Windows10 Home 64 bit v. 21H1 bld. 19043.1620
       #1

    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.
      My Computer


  2. Posts : 2,772
    Windows 11 Pro, 21H2
       #2

    I'm not surprised that the FU went fairly quickly. The last couple have been fairly minor updates. Likewise, the 21H1 update hitting any time now should be a very minor and fast update. It's the 21H2 update that is supposed to be rather major.

    The part that surprised me is how long the CU took for you. That cumulative update took under 5 minutes for and that includes all the pre-boot activity including the actual download. That wasn't on just machine. So far I've allowed about 4 machines to get that update, all very quickly.
      My Computers


  3. Posts : 821
    Win 10
       #3

    jamis said:
    I suppose if I had done the FU without the preceding CU, It would have run longer?
    Hello @jamis,

    No, that wouldn't have taken any longer anyway.

    The FU simply explains a switch to make the features of the 20h2 visible and changes the build number from 19041 to 19042.

    In order for the 20h2 FU to be able to install, at least build number 19041.153 must be installed.

    This means that the basis data was already included from this build for 20h2.

    The same applies to the upcoming 21h1.


    Friendly greetings
      My Computer


  4. Posts : 821
    Win 10
       #4

    hsehestedt said:
    The part that surprised me is how long the CU took for you.
    From what I've heard, it can take a long time on computers with HDD.

    And if it is the same computer as specified under its computer info, I don't know whether Norton is also slowing down the update.
      My Computer


  5. Posts : 24,619
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       #5

    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.
      My Computers


  6. Posts : 509
    Windows10 Home 64 bit v. 21H1 bld. 19043.1620
    Thread Starter
       #6

    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!
      My Computer


  7. Posts : 821
    Win 10
       #7

    @Bree and @jamis

    Thanks for the information and feedback.

    Take care and stay safe.


    Friendly greetings
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 21:31.
Find Us




Windows 10 Forums