(offer) windows 10 19h1 update builds, 18277.1006, 18305.1003 and 18312.1007

[Windows Thunderstruck]

hi. i am gonna offer some kb insider update builds of windows 10 version 1903. are these ok to upload to the ftp?
the builds are 18277.1006, 18305.1003 and 18312.1007.
the x86 and x64 versions came off rg-adguard.net, while the arm versions came off uup dump (because i couldnt unselect the n skus on rg-adguard)
i had to use dism to insert the kb updates of the three builds into the install.wim of arm versions myself, and then use dism++ to get rid of a "[DELETED]" folder that dism left behind. this was done by converting it to an esd and back into a install.wim, and it removed the folder. the reason why i did this is because on cumulative update builds, the uup dump script misnames the pro sku
if you are somehow interested in any of this, you can download them off my mega cloud in the mean time
links:
18277.1006 x86:
https://mega.nz/file/Iw8GyAwC#taufb2oJl ... Jjt95gfYt4
18305.1003 x86:
https://mega.nz/file/05kiEaoD#xj7PNEcZe ... PVUY2yi0Rs
18312.1007 x86:
https://mega.nz/file/B49AjYbZ#hALbV1emR ... M2uYhRMI5g
18277.1006 x64:
https://mega.nz/file/w5t0iIwL#YQFFM4Llk ... rSCG7QPrUA
18305.1003 x64:
https://mega.nz/file/g9lSVKST#jBaiLXjax ... H4Pm59WSiw
18312.1007 x64:
https://mega.nz/file/Ehk0jSJQ#Ub5i6tkz2 ... beaf6OijSE
18277.1006 arm64:
https://mega.nz/file/8tlGnaAL#NHfwOd0Ie ... Zr1ygdG4V0
18305.1003 arm64:
https://mega.nz/file/BklCWAYJ#THuZ5yXqt ... 1MuGXztpI8
18312.1007 arm64:
https://mega.nz/file/Ul9iwY7Q#zMnIai4gu ... YyPmtJ_DlU

[mrpijey]

Is there really any point uploading any of these KB updated versions? The only thing that differs basically is a single or two KB files in the UUP set. These KB files can also be applied to an installed version of the insider version. So no need really do keep full ISOs of these is there?

[Windows Thunderstruck]

I think we should keep these kb update builds. We do have such builds like 18342.8, 18351.7, 18351.8, and such other builds in other windows 10 versions like 19025.1051 and 19025.1052 of 20h1.

We also have 19613.1005 as well

I think these kb update versions should be kept, just like the normal builds

I think these should be on the ftp, just in case if microsoft deletes the files.

[mrpijey]

Well we already have the UUP sets archived, and we can put the KB updates alone on the server (as we already have a small KB repo on the FTP). Then they can simply be applied on an installed system to update it.

[Windows Thunderstruck]

And what is gonna be done with my uploads? I would much perfer them to be kept as isos (for consistency)

[mrpijey]

I will have to think about it, but I think I would prefer we keep the non-updated ISOs and keep any updates as separate KBs. I will still download UUP sets for the updated builds, but these sets are already identical to their release counterparts with additional KBs, so it not an issue to keep the UUPs.

[Windows Thunderstruck]

I have finished the upload of all three builds.

[Windows Thunderstruck]

What happened to my 19h1 uploads? Are they being processed? I suppose thats what happens when my upload folder disappears
I would much perfer them to be kept as isos, not uup sets. After all, such other kb update builds are on the ftp such as 19025.1051 and 19025.1052 and these are in iso format
I am helping to complete your windows 10 build library and therefore, i think these builds mentioned above should be included

Thank you for uploading my rs5 builds (17713.1002, 17744.1003, 17744.1004 and 17758.4) mrpijey

[mrpijey]

I am considering keeping only the KB files as they are the only difference between the base ISOs and these updated ones. I still keep the UUP sets (which do contain the KB files) but I don't see why we should need to keep a full set of ISOs for a few megabytes update which can easily be applied post-install instead.

If I decide to keep only the KB files I will go through my UUP sets and extract these KBs, add them to the FTP and remove the corresponding updated ISOs. I will need to figure out a way to label these so people will understand, or we just make a thread listing each base build and their KB update files.

I much appreciate you're trying to help, but I also need to factor in effective space usage on the FTP. Since these are mere betas I don't see much point in keeping updated ones as full ISOs as this adds a lot of storage overhead and time to compile and process for no real benefits when we can just as well keep the associated KB update files and let members update themselves. Something which is done during install of these ISOs anyway. The ISOs don't even identify themselves as the newer build but the base build so it's not like MS re-compiled the entire build with the updated build number, but rather just added the tiny KB update...

If the decision is made you may still be of very much help by perhaps maintaining the update thread by listing each KB update with their corresponding base ISO build etc. aiding members if they want to install a build with their updates. We'll see the format of this once we get there.

[Windows Thunderstruck]

Where is this "update thread" you speak of?
And the reason why i put these update builds as isos is because of consistency. Several update builds such as 17744.1004, 17758.4, 18342.8, 18970.1005, 19613.1005 etc are in iso format.

The installer stays the same as the base build, some of the files in install.wim are of the updated version, and the version identifiers (winver, command prompt, system information and ntoskrnl.exe identify themselves as the update builds)

[mrpijey]

It's not been created yet, the idea is to create it and use it to keep track of what updates goes where.

And yes, I know prior updated ISOs are on the FTP, but the idea is to remove them and replace them with the KB update files and document it in the thread mentioned above saving both space and resources, and time for the users as they need only to bother adding the KB update.

[Windows Thunderstruck]

If you gonna do that, you may wanna write a tutorial on how to teach users to put the updates in the build.
I dont think everyone knows how to manually install an update using dism.

[mrpijey]

Yeah that won't be an issue since it's a simple command.