Agreed, Was originally aiming the question at @abbodi1406, but in the end adapted post to follow on from previous converstion Previously always handled DU's manually, just recently started using the script to test if it indeed works (saves 1 step in operation) AS a rule I always have a virgin distribution target on HDD, to which I would usually extract the DU directly to sources folder, .. all other updates to UPDATES folder, then run prepared script -> updated installation media.
Patch boot.wim #2 will update some du files. But not for all. Some times will be downgrade. Like you put du files in current place, after #2 progress done. DLL build downgrade from 404 to 292(17763 example)
Afaik, the dynamic updates for setup media (iso:\sources) don't go into any other place. Dynamic updates for dism integration are superseded by the CU very fast after release.
W10UI expand DU to iso\sources normal boot.wim\2\sources is updated with CU (cannot be controlled) uup boot.wim\2\sources is updated manually with DU (if any) during creation
I learn to never use DU again for the same reason. Seams CU usually contains newer versions of DU files. Edit: Well, seams not this time. KB4502374 contains newer files. Maybe CU does not contain DU files at all?
Afaik, the CU doesn't update the ISO:\Sources folder. it services the WIM files. The CU normally supersedes the CBS dynamic update when it's released after the CBS DU was released.
The point I was trying to make was......... in my case, (running your script) the DU does not get extracted into the sources folder .... not really an issue for me as I am more than pepared to address the problem manualy. As I always have.....
possibly... but usually the boot.wim, ... not the SOURCES folder (@Enthousiast CU normally supersedes the CBS dynamic update)..but if that was the case, why is it that when I integrate all the latest updates.... nothing changes in the SOURCES folder..... everything remains as build .001 (anal, current release is .145 so as far as I am concerned original buid is .001) EDIT: solved
@Enthousiast ... went back to drawing board after reading this, and yes, at some point (not sure why) I started targeting the .wim instead of the distribution folder. Ran script with revised instruction and all is now as it should be.. problem solved. @abbodi1406, @Enthousiast thanks for input....
cumulative update for media like SD cards or USB devices attached for installation media created with MCT to avoid errors when upgrading the new features