I think there are some die-hards that refuse to try it. I stopped using the website when I discovered Paul's local server, as the website was constantly down for weeks at the time. I have never looked back since, and for the record, I do not mean any disrespect to those that maintain the website.
From what I experienced, the local server does not include Teams (1910x builds) and maybe some more of the very exotic stuff. There are no further differences. The local server also correctly implements 23H2 Betas.
you can add it manually as any other build if you need it in my script then I can add it I think, but I need working UUP dump website as a reference or actual builds archive I'll try to download actual builds db from the website first tomorrow
Well, I have to admit I haven't fully understood fetchdetect.php yet. Why does the Dev channel use 22621 as build number, for example? I guess some black magic and trickery to make it work (and working well it does). So, I didn't try adding any custom builds, yet, to not mess up the build database. If you plan add it, do add it with a REM in the cmd scripts, as most people don't ever want it. Another thing that bugs me is that fetching information from MS server can randomly fail. The fetching build will then skip and continue with the next entry. No idea if such errors can be trapped and that failed section repeated. Probably it would have been done already if it was that easy.
there's two principally different ways to get builds from Windows Update and fetch_sync_current_only option controlls it in config.ini: 1. with fetch_sync_current_only option we should fetch exact known build number, and it's useful for old known builds, that's it generating a list of builds and brute force checking it is not an option, that's why it's disabled by default 2. without fetch_sync_current_only option we are telling Windows Update on what build we are now, including arch, channel and SKU. Then WU just sends us whatever the latest build is suitable for our case that's why there's only base builds in my scripts (for example I'm on 19044.1 build with 125 SKU, Retail channel and I want to get the latest update - WU sends us build 19044.3324) so for Dev channel - 22621.1 is the latest client base build on Retail channel and it has direct upgrade path to the RP, Beta, Dev and Canary channels and for Canary we are using "latest" as a build instead of a number - it checks the latest build in the database, and it obviously works only on the Canary channel if the database isn't empty part of the problem is a PHP performance on any Windows platform, it's x2 more times faster on my Linux VPS with a single CPU core and failure rate is much much lower (I'm saving results in the log file so I can see any errors on the go) other than that I don't know how to rerun each failed attempt, maybe @abbodi1406 can help with that if fetchdetect.php reports any errors in the output (standard-error stream I guess) in the meantime I downloaded latest builds data from the Website, hope luzea wouldn't hit me for that now I should merge everything and upload the latest archive let me know if I missed something here: Windows 10 Insider Preview 19101.1140 (vb_release_svc_team_flight) Feature update to Windows 10 Team (19045.2130) Code: %fetchdetect% All Dev Mainline 19100 1 119 %fetchdetect% All Retail Mainline 19042 1 119