Windows 10: Difficulty integrating Cumulative Update into 20H2 image

I realize that there is probably an extremely small audience that actually does this, but has anyone been able to successfully integrate the latest Windows 10 20H2 updates into their ISO images?

For some reason, when I do so, if I try to install Windows from that media I get the following error:

A media driver your computer needs is missing. This could be a DVD, USB, or Hard disk driver. If you have a CD, DVD, or USB flash drive with the driver on it, please insert it now.

What I am Doing

I am taking the released ISO image of Windows 10 20H2 and applying the following updates:

WinRE (the WinRE.wim file): Servicing Stack Update (SSU) and Safe OS Dynamic Update.

WinPE (boot.wim file - both Index 1 and 2): SSU and Latest Cumulative Update (LCU)

Main OS (install.wim file - any or all indices): SSU, LCU, Flash Player security updates, and .NET updates.

Windows Media: Setup Dynamic Update

Through a process of elimination I've determined that the problem is with the LCU (Latest Cumulative Update).

I've tested my updated ISO images by trying to install to both VMware workstation and Hyper-V with the same failure as noted above in both instances.

Note that I've been doing these updates for at least a year now, and I do it at least least once a month, more frequently when Microsoft releases C and/or D patches in addition to the normal monthly B patches. My process is fully automated so it's not human error *Smile and has been 100% reliable up until now. I follow precisely the procedures that Microsoft prescribes.

There are only 2 LCUs for 20H2 so far: The usual monthly update for October 2020 and the preview release which was made available on Oct. 28. I'm having the same problem with both of them.

Has anyone else tried this?

:)

 

Integrating cumulative updates into the image

Ha, I managed to figure it out - purely accidentally.
It turned out there IS a prerequisite to integrating this - it's called "servicing stack" and these KBs are released more or less along with the cumulative updates (sometimes like once per two CUs).
Of course, this is not explained anywhere (the connection and dependency).

The another catch is that when you try to integrate all this, you have to do it twice. WTF.
So you have to mount the image, do whatever customizations you have prepared, then integrate the servicing stack, THEN unmount and save the image, AND THEN mount it again and finally integrate the large update.

This is almost as annoying as booting into safe mode in Windows 10 compared to Windows 7.
just-pure-WTF

 

windows 20h2 update issue

Hi, I'm Israel M., I'm an independent consultant and I'm happy to help you.

The update of Windows 20h2 is carried out cumulatively, correcting errors the focus was to correct problems seen until then, being made available by Microsoft an extensive list (almost 50 items cited by the company), thus showing that this update promises to
regularize a good part of the image that reaches users of the distribution. Therefore, these constant updates are corrections.

I hope I helped, I await your return.

Best regards,

Israel M.

Outside consultant

 

Update History is not showing v.20H2

Hi Dominic

I am Dave, an Independent Advisor, I will help you with this . . .

This is normal behavior in Windows 10, typically when you install a Feature Update like 20h2, the update history is wiped, this is to prevent the user from trying to uninstall an update that was prior to the Feature Update, which would de-stabilize Windows
10, the list should start building again, when some updates are applied to version 20h2 . . .