Du for Sources is meant to update the install media, the "ISO:\Sources" folder. Only meant for offline usage, not online, it is NOT meant to be integrated in any wim file.
All updates SSU, CU, DU for SafeOS and DU for Sources are available on UUP, except the Flash and DotnetFX CUs (only DEV channel has DotnetFX CUs available).
I can only find CUs and Windows Insider Preview builds on UUP Dump. Are all updates released on channels called "Preview"? What's DotnetFX and why are Dotnet CUs not released on the other two channels? What's exactly UUP and is it official? I think it's weird for WU to offer Windows builds instead of only updates (although only on the Dev channel). So, which updates should we integrate when creating an updated Windows 10 image (I don't care about Flash Player), CU, SSU, DU for SafeOS and DotnetFX, not DU for Sources?
Didn't we go thru all of this a few times now? Updates are: - Public - Preview on catalog aka the old non security updates, now called Preview. And offered on WU as optional updates. - Release preview - Beta Channel DEV channel is an entirely separated channel for ongoing, not build related, testing.
So, non-Windows Insiders get .NET Framework CUs but Beta/Release Preview channels users don't? Why do you separate the Dev channel from UUP if it appears on it? On UUP Dump there's a more recent EP/Feature Update than the one which appears on the Updates Overview. So, there are non-channel updates called Preview too like at least some Catalog updates? May Catalog updates be more up-to-date than Channel ones?
You're mixing up all the info and concluding all wrong. Non insiders get the official publicly released updates and optional updates on WU. Insiders get the SSU/CU updates which are released at the insider level they enrolled in. On beta/rp channels on 1909 all public updates were offfered on WU + the IP level updates for their IP level. Because that channel has nothing to do with Updates. It still is .479 on the overview as on UUP, last time i checked. Running in circles here. Catalog updates are either public or non security preview updates. In some cases an update goes thru the channels and is moved from RP/Beta channel to Preview Catalog, but not always.
I think there is an issue with the latest downloads of the Dynamic Updates. I tried both .572 and .608 with the proper updates. I restored Windows from three different saved Windows images, even a version that's from a few months ago where W10UI worked perfectly. When it gets W10UI gets to installing the Dynamic Updates on my extracted 19042.1 ISO I get this. It never used to do that on any of my Windows installs. Can someone test it? Only other thing I can do is a clean install of Windows but I don't think that's the issue. It's always worked in the past with any of the images I restored. windows10.0-kb4588844-x64_b990911e041404A014e4a01f0a1086714675290b.cab No Instance(s) Available. No Instance(s) Available. No Instance(s) Available.
UUP offers all updates that the WU service also offers, including the updates for an upgrade scenario. UUP dump ISOs are made from those updates and base files, not an official feature of MSFT but by @whatever127 (website and technics) and @abbodi1406 (conversion + updates integration script). Again, in upgrade scenarios it's downloaded by setup. What has update history to do with this? I didn't use it in my answers. I have the idea that none of my answers stick.
If I integrate the latest DU for Sources on an ISO, use it to install Windows and afterwards do an in-place-upgrade install will it sill be offered by the setup? Why are SSU installed when installing CU via WU but when integrating updates on an ISO we need to integrate both and not only the CU? Why aren't they installed when manually installing the CU too? I meant integrating the DU for Sources when creating a new ISO, not DU for SafeOS.
Yes. Because MSFT made it working that way. On WU, it downloads (if needed) the latest SSU when the latest CU is downloaded and installs the SSU silently (won't show up in "update history" but will show on "Installed Updates". Both are needed for an 100% uptodate ISO. Take a look at the Updates Overview and the W10UI progress i always show before i announce the updated overview: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-546#post-1625365