Windows 11 - 22H2 (Moment 2) & 22H2 (Moment 1) %fetchdetect% All ReleasePreview Mainline 22623 1 %fetchdetect% All ReleasePreview Mainline 22622 1
@inTerActionVRI keep in mind 22622 is now discontinued. And check the post above, i forgot about the channel By default these (base) builds are made available by running the included "uupdump-get-fileinfo+packs.cmd": Code: %fetchdetect% All Retail Mainline 17763 1 125 %fetchdetect% All Retail Mainline 17763 3770 125 %fetchdetect% All Retail Mainline 19044 1 %fetchdetect% All Retail Mainline 19045 1 %fetchdetect% All Retail Mainline 22000 1 %fetchdetect% All Retail Mainline 22621 1 %fetchdetect% All ReleasePreview Mainline 19044 1 %fetchdetect% All ReleasePreview Mainline 19045 1 %fetchdetect% All ReleasePreview Mainline 22000 1 %fetchdetect% All ReleasePreview Mainline 22621 1 %fetchdetect% All Beta Mainline 22000 1 %fetchdetect% All Beta Mainline 22621 1 %fetchdetect% All Beta Mainline 22622 1 %fetchdetect% All Beta Mainline 22623 1 %fetchdetect% All Dev Mainline 25267 1000
These didn't work for me. %fetchdetect% All Beta Mainline 22622 1 %fetchdetect% All Beta Mainline 22623 1
Yes, this build was the friend Ace who mentioned it. But the 18362 and 18363 even discontinued, are for my taste, the best option for retrogaming.
(+) New build 18363.418 = Cumulative Update for Windows 10 Version 1909 (18363.418) amd64 18363.592 = Cumulative Update for Windows 10 Version 1909 (18363.592) amd64 18363.657 = Cumulative Update for Windows 10 Version 1909 (18363.657) amd64 Failed = Metadata for this update is not generated. Edit: 18363 1 with "fetch_sync_current_only=true" = Failed
But you didn't use uupdump-download-archive.cmd before uupdump-get-fileinfo+packs.cmd, did you? I got the 18363.2274. Spoiler 18363 22622 252xx
I attached the file that @abbodi1406 made the pull request. https://forums.mydigitallife.net/attachments/autodl_files-zip.61955/ Just replace depends_win.ps1 inside the \uup\autodl_files folder.
It is necessary to download this data. Only one time. You download an ISO but not download 1.67 gb, heheheh
why you need that? UUP converter should be the latest one already edit: it's not latest, I'm gonna update it someday edit: done
Code: 18363 1 works with these settings: uupdump-get-fileinfo+packs.cmd [set "serverPort=50747" + fetch_sync_current_only=true] Gets: Cumulative Update for Windows 10 Version 1909 (18363.657) amd64 Cumulative Update for Windows 10 Version 1909 (18363.657) arm64 Cumulative Update for Windows 10 Version 1909 (18363.657) x86 Cumulative Update for Windows 10 Version 1909 (18363.592) amd64 Cumulative Update for Windows 10 Version 1909 (18363.592) arm64 Cumulative Update for Windows 10 Version 1909 (18363.592) x86 Cumulative Update for Windows 10 Version 1909 (18363.418) amd64 Cumulative Update for Windows 10 Version 1909 (18363.418) arm64 Cumulative Update for Windows 10 Version 1909 (18363.418) x86 18363.592_amd64_en-us_core_99c9fe2f_convert.zip 18363.592_amd64_en-us_professional_99c9fe2f_convert.zip 18363.657_amd64_en-us_core_b1cf67e1_convert.zip 18363.657_amd64_en-us_professional_b1cf67e1_convert.zip 18363.418_amd64_en-us_core_4526605b_convert.zip
No. It is downloading the uup-converter-wimlib-85.7z, not the latest one uup-converter-wimlib-86.7z. This happens when the package is generated by the website. For example: 22621.963_amd64_en-us_multi_997706be_convert.zip Inside it is stored depends_win.ps1. When we run uup_download_windows.cmd, depends_win.ps1 will be called and will download 7zip, aria2c, uup-converter-wimlib.7z to the file folder and will download the entire bin folder. But it is pointing to old version link. So it is necessary to update. abbodi made the pull request but it was never committed. I said this above.
I'll try to explain how uupdump-get-fileinfo+packs.cmd and "new build" on the website works By default we are trying to get latest builds from Windows Update from the base builds in the uupdump-get-fileinfo+packs.cmd it will work that way only for available products, outdated builds should lead you to the latest available upgrade from the outdated build, so there's no point to adding outdated base builds here's the list Code: Client All Retail Mainline 17763 1 125 All Retail Mainline 17763 3770 125 All Retail Mainline 19044 1 All Retail Mainline 19045 1 All Retail Mainline 22000 1 All Retail Mainline 22621 1 All ReleasePreview Mainline 19044 1 All ReleasePreview Mainline 19045 1 All ReleasePreview Mainline 22000 1 All ReleasePreview Mainline 22621 1 All Beta Mainline 22000 1 All Beta Mainline 22621 1 All Beta Mainline 22622 1 All Beta Mainline 22623 1 All Dev Mainline 25267 1000 Server All Retail Mainline 20348 1 8 All Retail Mainline 20348 1 406 All Retail Mainline 20349 1 406 All ReleasePreview Mainline 20348 1 8 All ReleasePreview Mainline 20348 1 406 All ReleasePreview Mainline 20349 1 406 All Dev Mainline 25267 1000 8 something is out of logic here: All Retail Mainline 17763 3770 125: 17763 is EOL now and sometimes you need to ask for the CU build for non security updates, check that in January and you'll see All Beta Mainline 22000 1: there's no Beta builds for 22000 build, but it was needed for upgrade to 22621.1 for some reason due to A/B testing (some users get 22621, some 22623) All Dev Mainline 25267 1000: just use any Dev build and you always get the latest one All Dev Mainline 25267 1000 8: for 8 SKU (server) you can get only CU updates right now, so you need to change this line to the existed released Dev Server build if new CU is available if you need to download EOL build then change config.ini to fetch_sync_current_only=true and use "New build" feature on the website, then generate packs using uupdump-get-packs.cmd overkill solution: run uupdump-download-archive.cmd and download builds archive, it's 1.5 Gb. of data there's no point in adding Retail 22622.1 22623.1 because it doesn't exists, that builds are for Beta channel only