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
Is not a CBS update (it's for updating ISO:\Sources) by extracting the cab and put the extracted files in the sources folder. All is explained here: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-406#post-1526578
I understand the DU as a quick and dirty fix to reduce the chances for a broken installation or update or upgrade. Once that specific installation has gone beyond the breaking point, there is no more reason for the DU. The DU patches should not be in an image.
To be clear, can you integrate updates into the MVS 18362.30 extracted ISO with W10UI 6.5 or is it better to use UUP 18362.1?
Why do you advise that I'm using the .30 iso and no problems so but maybe because I use NTlite for that I believe MSMG toolkit does not support higher integration than 18362.1
It doesn't matter what tool you use, it's always better to use a clean base wim, like msft provided for all windows 10 releases up till 1903, on 1809 they released an updated refresh iso and called it the re-release of 1809. On 1903 they left 18362.1 to the UUP system and released a refresh iso as base iso. It's not about problems, it's about the servicing schemes used thru the years, by msft and homebrewers, to not have traces of other updates in a newly updated iso. With 1903 a lot has changed but when people ask what's better, most will advice to start with a fresh clean base wim.