No: These are the channels: - DEV channel, isolated not related to any build test channel - Beta channel, atm offering the same updates as the next channel - Release Preview channel, offering the same updates as the previous channel - Retail channel, offers public updates And you have Catalog Preview updates, not really preview and previously known as third week non security updates, and catalog only, but as with 7 and 8.1 it got the preview designation in the release name on catalog and now they are offered as optional updates on WU too.
So "online" DUs only work with a clean install? It must be "online" AND "clean install"? AND you must enable it?
I don't know what this means. A clean install doesn't need a DU for sources, you can strip all files down to the bare and it will still install. it is used for upgrades, depending on the files it updated on the ISO. DU for SafeOS is now used by MSFT to update the winre.wim image on the released ISOs, instead of the full LCU.
Clean-install (in this context) means an empty partition. One that does not have any prior version of Windows 10 already installed on it. A partition that does not have any applications or programs installed on that partition concurrent with Windows 10.
Then it doesn't need the du for sources applied to the ISO but it doesn't hurt either if it was applied. For a clean install from boot only these files are needed: Code: | bootmgr | bootmgr.efi | +---boot | | bcd | | boot.sdi | | bootfix.bin | | bootsect.exe | | etfsboot.com | | memtest.exe | | | +---fonts | | chs_boot.ttf | | cht_boot.ttf | | jpn_boot.ttf | | kor_boot.ttf | | malgunn_boot.ttf | | malgun_boot.ttf | | malgun_console.ttf | | meiryon_boot.ttf | | meiryo_boot.ttf | | meiryo_console.ttf | | msjhn_boot.ttf | | msjh_boot.ttf | | msjh_console.ttf | | msyhn_boot.ttf | | msyh_boot.ttf | | msyh_console.ttf | | segmono_boot.ttf | | segoen_slboot.ttf | | segoe_slboot.ttf | | wgl4_boot.ttf | | | +---nl-nl | | bootsect.exe.mui | | | \---resources | bootres.dll | +---efi | +---boot | | bootia32.efi | | bootx64.efi | | | \---microsoft | \---boot | | bcd | | cdboot.efi | | efisys.bin | | memtestx64.efi | | memtestx86.efi | | winsipolicy.p7b | | | +---fonts | | chs_boot.ttf | | cht_boot.ttf | | jpn_boot.ttf | | kor_boot.ttf | | malgunn_boot.ttf | | malgun_boot.ttf | | malgun_console.ttf | | meiryon_boot.ttf | | meiryo_boot.ttf | | meiryo_console.ttf | | msjhn_boot.ttf | | msjh_boot.ttf | | msjh_console.ttf | | msyhn_boot.ttf | | msyh_boot.ttf | | msyh_console.ttf | | segmono_boot.ttf | | segoen_slboot.ttf | | segoe_slboot.ttf | | wgl4_boot.ttf | | | \---resources | bootres.dll | \---sources boot.wim install.wim lang.ini setup.exe If the lang.ini file is needed i haven't tested.
That's why i never let setup download anything for my videos, it takes a long time to run. Pretty logical. You mean Start > Settings > Update & Security > Windows Update > Check for updates. How would you install a DU for ISO:\sources on a running install? How would you install a du for safeOS when it's meant for offline updating winre.wim? That publishment actually talks about all updates.
Do some channel Preview updates stop being called "Preview" when released on Catalog and on WU for all users as well as some Catalog Preview updates when released on WU?
You asked some questions before I morphed into Spock and I wasn't sure if your questions were rhetorical or literal. I think that where you were headed was a discussion about offline media update. In some instances, there might not be an option to obtain Dynamic Updates online. There may not be a connection to an MS endpoint. In those instances one could acquire Dynamic Update packages and apply them to the image prior to starting Setup on the device. Such an endeavor might involve a series of modifications to a number of different targets (image files) in a specific order. Some modifications may be repeated on different targets. The target images would include: WinRE (winre.wim) WinPE (boot.wim) Operating system (install.wim) Note: The main operating system file (install.wim) contains multiple editions of Windows 10. An update to a single edition may only be required to deploy it, based on its index. Possible all editions may need an update. At this point, there are scripts, possibly Power Shell scripts, that could be deployed to apply the appropriate modifications to the image files. My guess is that's where the scripts come-in after a download of UUPDUMP.ML files. It is to apply media based DUs and to assemble the final ISO. It is here where I must end my comments because I am not up to the task of disassembling existing scripts to ascertain their accuracy. I am assuming that everything is performed in the right order and to the right targets. But it has been an issue of concern and I have accepted these scripts in good faith.