The standard script delivered with the downloader always throws errors for me. I have to use aria2c command lines that are much more conservative. Much slower, but they always work for me, on first attempt.
well , after a long time , once again download windows 10 source files via aria2c script , and ran the uup converter script from aboodi to generate iso. all went ok and iso is ready... now testing iso by making a virtul machine of 21H2 windows 10 pro , it is asking for a key .. is aboodi windows 10 activator working for latest windows 10 builds?
whats this ? i just made an iso from UUP , but its saying version 2004 ? although build is 19041.1 ? it is not 21H1?
It is correct. MS used the year/month scheme before the second half of 2020. Just like 1809 or 1507. So 2020/April =2004 They started using the year/half form since 20H2.
how to add updates? ( ok , i ran UUP script again , and in configurations, toggled add updates to 1 ) now it is making iso again, will it make 22h2 iso now?
You can download 19044.2075, set autostart to 0, start the download cmd, put in the 22H2 EP (kb5015684) manually (you can remove the 21H2 EP (KB5003791)) and start the conversion script. Better would be to only use UUP dump for creating a pristine 19041.1 ISO and next use W10UI + updates to update a copy of the 19041.1 ISO.
Why would be better? What is the advantage to that method? To be honest, you mentioned W10UI method in the Windows 10 Enterprise forum, however, I wasn't sure what exactly to download, only the latest cab files or every single one building up to the latest update? It is confusing to me.
With this method, when frequently integrating updates you don't need to download and convert the UUP files to ISO everytime, with creating a pristine 19041.1 ISO once you only have to download and integrate the updates. this is enough:
And you create base 19041.1 with AddUpdates = 0? Thank you so much for the answers, I'll get out of your hair (for now).
I have an old ISO 19044.1147_amd64. Can I download and integrate all the Windows KB of 19044.2075 to keep it up to date?