After integrating KB4556803 and installing the image on a VM, same CU still gets offered when I check for updates. Along with 2020-02 adobe flash update. Code: ============================================================ Running W10UI v8.1 ============================================================ ============================================================ Extracting .cab files from .msu files ============================================================ 1/2: 3-netfx-windows10.0-kb4552925-x64.msu 2/2: 4-flash-windows10.0-kb4537759-x64.msu ============================================================ Extracting files from update cabinets (.cab) *** This will require some disk space, please be patient *** ============================================================ 1/5: 0-ssu-windows10.0-kb4557968-x64.cab 2/5: 1-cu-windows10.0-kb4556803-x64.cab 3/5: 2-winpe-windows10.0-kb4557964-x64.cab 4/5: Windows10.0-KB4537759-x64.cab 5/5: Windows10.0-KB4552925-x64.cab ============================================================ Mounting install.wim - index 1/8 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17763.771 Mounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17763.771 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_KB4557968~31bf3856ad364e35~amd64~~19041.262.1.1 [==========================100.0%==========================] The operation completed successfully. ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17763.771 Image Version: 10.0.19041.1 Processing 1 of 2 - Adding package Package_for_KB4537759~31bf3856ad364e35~amd64~~10.0.1.0 [==========================100.0%==========================] Processing 2 of 2 - Adding package Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.1.3176 [==========================100.0%==========================] Error: 0x800f081e The specified package is not applicable to this image. The command completed with errors. For more information, refer to the log file. The DISM log file can be found at C:\Windows\Logs\DISM\DismUpdt.log Deployment Image Servicing and Management tool Version: 10.0.17763.771 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.264.1.6 [==========================100.0%==========================] The operation completed successfully. ============================================================ Resetting OS image base ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17763.771 Image Version: 10.0.19041.264 [===== 10.0% ] [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.17763.771 Image Version: 10.0.19041.264 [==========================100.0%==========================] The operation completed successfully. ============================================================ Adding .NET Framework 3.5 feature ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17763.771 Image Version: 10.0.19041.264 Enabling feature(s) [==========================100.0%==========================] The operation completed successfully. ============================================================ Reinstalling cumulative update(s)... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17763.771 Image Version: 10.0.19041.264 Processing 1 of 2 - Adding package Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.1.3176 [==========================100.0%==========================] Processing 2 of 2 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.264.1.6 [==========================100.0%==========================] The operation completed successfully. ============================================================ Updating winre.wim ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17763.771 Mounting image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.17763.771 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_KB4557968~31bf3856ad364e35~amd64~~19041.262.1.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.17763.771 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_KB4557964~31bf3856ad364e35~amd64~~10.0.1.0 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.17763.771 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.264.1.6 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.17763.771 Image Version: 10.0.19041.264 [===========================99.5%========================= ] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.17763.771 Image Version: 10.0.19041.264 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.17763.771 Image File : D:\win10\intupd\x64\2004\winre.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.17763.771 Exporting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Adding updated winre.wim ============================================================ 1 file(s) copied. ============================================================ Unmounting install.wim - index 1/8 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17763.771 Image File : D:\win10\intupd\x64\2004\install.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully.
I imagine it was just the .netfx update, since after enabling .net 3.5 this same update integrates without errors. On the VM, winver shows .264(don't know how relevant this is, may as well be only cosmetic if there's truly a problem with the integrated updates). The updates themselves i downloaded from your overview post.
https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-498#post-1595972 install was uptodate
That's my experience as well with W10UI-integrated updates. The only downside is windows might pointlessly download the latest CU, but upon restart will detect it's already installed and continue booting without any time-consuming install process. It's the old 4537759 from February, it's the same package for all windows 10 versions, MS just did not bother labeling it for 2004 as well.
I guess I'll try again tomorrow(no flash update this time). See what happens. Also, seemingly != seamlessly .
I know, right? WU does it's own thing, there are region-specific updates, features, some updates get assigned multiple kb's and for a while coexist like that, MS sometimes quietly fix stuff in the backend and a known hard url can point to modified package and so forth. I don't see a problem with W10UI, but with the way Windows have sort-of broken update integration ever since the move to these lame monolithic CUs - if I were to randomly take 100 systems I worked on, at least 30 can't apply the latest CU every couple months, it's pathetic. Not sure if worth investigating if there's some registry flags difference between a uupdump build and the equivalent W10UI. I've seen it a couple times but since it did not actually reinstall those updates, it did not bother me.
Updated the 2004/19041.xxx Updates Overview with SSU/CU MSU links from catalog https://forums.mydigitallife.net/th...pc-20h1-vb_release.80763/page-16#post-1571109
Regarding why W10UI name the iso as 19042 CU KB4556803 contain registry values and manifest for 20H2, but it will need Enablement Package to activate them meaning, the next W10 version 2009 will be small feature update, just like version 1909