Does one have to integrate the DU when already integrating the SSU, LCU, dotnetCU and FU? What does it do?
I thought "DU" stood for Dynamic Updates and so they wouldn't be needed since I'm integrating the LCU. Anyway, could you tell me what do you exactly mean by saying it updates the source folder and is it integrated the same way the other updates are if I use NTLite (I use it to integrate the other updates) since I don't use DISM to integrate updates?
You put the file into the sources folder, right click it, unpack and allow all duplicate files to be overwritten.
While the other updates update the Windows IMage (the OS being applied to the target), the DU updates the Setup files. Thus, it needs to be applied to the sources directory, outside of the install.wim/esd. DUs correct errors in Setup, and teach Setup how to handle edge cases. It could very well be that Setup failing on a PC will suddenly work after the DU has been applied to it.
MSMG ToolKit has a folder called "Dynamic" so does that mean I can integrate the update the way I integrate the other ones (I can't integrate it with NTLite the way I integrate the other ones) instead of extracting it to the sources folder after all?
I think the folder: Code: WHD\w10\x64\SetupMedia\ is the folder to put in the dynamic update for Sources. For updates integration it's best to use W10UI, it knows how to properly handle all the updates.
I don't know but MSMG ToolKit's README states: "Copy Windows Dynamic Update files to <WHD\w10\<Architecture>\Dynamic> folder (E.g. <WHD\w10\x64\Dynamic>).". I've been using NTLite to integrate updates but since I have an error when I try to integrate this update the "normal way" (unlike with MSMG ToolKit) I simply extract the update's content to the sources folder before loading the image.
For someone who always claims to do clean untouched installs when reporting 100rds of problems, you seem to use 2 windows chopping/modifying tools and even the worst of all of them, ntlite. The dynamic update folder in MSMG toolkit is for the dynamic update for cbs, like the du for safeOS. The setupmedia folder is for the cab containing the files for updating the ISO:\Sources folder, MSMG wants all updates separately in their own folder, W10UI intuitively knows what the update is meant for and automatically applies it in the correct way.
I didn't say I always do that. I was doing untouched installs and I still had (the same) errors. It looks like they weren't caused by MSMG ToolKit/NTLite after all. I even tried the en-us build and I didn't have these errors. Anyway, lately I've only been using NTLite. Now what do you have to say? I thought the dynamic updates for cbs (I don't know what safeOS is) were the same as the dynamic update I'm talking about.
Still the same, considering i have read ALL of them DU for sources is only distributed as a cab, just a container like rar or zip, extract and copy files to ISO:\sources Du for safeOS is cbs and is for integration into wim by dism.
I didn't mention all the issues I've been having but some were fixed by Microsoft and I even had some of them on the en-us builds. I even have a translation problem, duplicated components and other weird things (even after doing an untouched clean install). This DU thing is realy confusing. Anyway, do I need both DU or just the one regarding the sources folder (for instance)?