We are talking about how MS deploys new Feature Updates (not MCI or MSI upgrades like security ones on Patch Thursday) to PCs. Then, using those UUP files on could create his\her own ISOs for future installation etc.
UUP dump uses the windows update servers for downloading all needed files for the creation of an ISO, very good way to get clean ISOs, without any pre-integrated updates, for projects. Or with IP builds for those who need to do a clean install.
There even seems to be one person who uses the UUP files directly to apply a new Insider Preview, without creating the ISO first.
Is it me or if I want to download the .1 Build and don't want to integrate updates, I should type "0" in the ConvertConfig.ini's "AddUpdates" section because if I don't it will integrate updates even if I downloaded the .1 Build and so it will stop being the .1 Build, which is weird?
Not sure I get it still. Is there any reason for me to switch from just getting latest ISO and integrating updates classically?
I know but if I download that build but keep "1" typed in the ConvertConfig.ini's "AddUpdates" section won't it integrate updates and so it will stop being the .1 build but a build which was released afterwards?
No, if you download a build not containing any updates, like 19041.1, it won't integrate any updates, whether addupdates is set to 0 or 1.
Thanks. Another question, after running Windows 10's Setup.exe, I'm asked if I want to install updates (some installs failed after choosing to do it). If I choose to do it will it install the most recent ones even if I have the .1 Build?
I'm the one who wrote (more "rephrased" but still) this FAQ entry and I probably should've made this clear enough - It's not impossible, it's almost impossible and completely useless. But I know better than to overwhelm mostly non-technical users with such useless technicalities. To create a working image you need the metadata ESD. (Not available for Windows Server through the Unified Update Platform or, in fact, anywhere else) This particular ESD has an index which contains metadata, the registry and check sums. To create an image you need to export the metadata ESD and have all the files it references available in (preferably, in the standard procedure) separate ESDs (which we derive from available UUP files). Only then you have a complete installation image with a complete registry and all files with correct metadata. This image can be later glued together with available WinPE files and you have an almost perfect replica of a normal installation media, which you can put into an ISO image. Some questions one might have: "Why not get the registry hive files from an already created ISO?" That would be an ISO->ISO converter. Completely useless. Not to mention you still lack the metadata and the files cannot be acquired through UUP (or anywhere else except maybe VHDs which are not a good option), which defeats the purpose of the project and you don't gain anything in the process. "Why not gather all ESDs, apply them and capture the metadata?" ESDs available through UUP dump are client-only. No relevant server-specific files are available. In such an image you would be missing almost everything. Even if you were to glue this together at all costs you would need some sort of base install.wim to build upon taken from a complete Windows Server image, which again defeats the purpose and is effectively useless. I hope this answers all questions regarding Windows Server. (If I missed/messed up something I expect @abbodi1406 to correct me ) --- Short PSA: I'm currently hosting UUP dump (both managing and paying for the server) and until @whatever127 comes back you can direct all questions and problems regarding the website and/or related things to me. I'll help with anything and everything and try to keep everything operational until the owner comes online again. If you have any questions that you'd like answered ASAP you can reach me a lot faster at the UUP dump Discord.
The Edge updates can only be browsed for files they contain (and all of them can be downloaded, only manually) similar to how it is with Windows Server updates. Some people really want to integrate the new Edge installer .cabs, and that's where you'd get them. It's not a Windows 10 build and that's why you cannot create a Windows 10 image from it. (Which is effectively what "There are no languages available for this build." means)
There is a problem with the Name. I get this 19041.330.200610-1131.VB_RELEASE_SVC_IM_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO BUT, this is 1st Build from 19042 & not sure about VB_RELEASE either ???