Concerning 19045 ESU, I have to adapt search strings again. Currently, I have Code: call :dAll Retail "19045 6466" which does only detect "Cumulative Update for Windows 10 Version 22H2 (19045.6575)". This is a limited UUP set. Is there a better search string that will detect the "Feature update to Windows 10, version 22H2 (19045.6575)" full UUP sets?
I'm talking about specially uupdump-aio.cmd (the fetch part). There is no thisonly flag here? The 19044 1 125 (LTSC) and the 22631 4 (Enterprise) have already been figured out by myself.
as I said, uupdump-aio.cmd uses \sta\fetchupd.php, but \sta\fetchupd.php doesn't support branch, so it's impossible to fetch full "Feature update" build without migrating to uupFetchUpd2 (add new build on the website already uses uupFetchUpd2) but migrating to uupFetchUpd2 will break MSIT part of the script because it was "build+flag" and with the new function it would be "build minor sku type branch flag"
Hmh, thanks for the hints. Not yet decided what I'll do, however, the official uupdump site has mastered it already (it seems). Already running on API 5000b4c4b9
security update = cumulative update on patch tuesday everything works as expected, they stopped publishing full builds a year ago, the latest full builds are 26100.2314 (server editions) and 26100.1 for HCI nothing new here, just a new name for WU things
Hi @abbodi1406 , Whenever I made iso images of 25H2 for both x64 and arm64 ( via uupdump.net ) for my CoPilot+PCs All AI components are missing but when I install stock iso or factory images I see all AI components present. Furthermore, sometimes I see just 3 of AI components but not all of them. Is there any option to include those AI components for eligible CoPilot+PCs ? I guess none mentions this issue as far as I know. Probably I miss something somewhere but what and how to solve this problem. Thanks in advance. Erdal
@Erdal2 You must install LCU msu on live Copilot+PC to get the AI components they can't be added for offline integration
I tried to use uupdump to build a 26200.7309 iso for amd64 and clicked the right link for it on the site, and after building it, I somehow ended up with 26100.7309. Did I do something worng ?
- What link on UUP dump did you use? - What options did you set, show the convertconfig.ini content - Show us the full conversion progress. Without this information we can't assess what happened.
The 26200 link for Engilish Great Britain language, convert to iso, windows pro, unchecked home, include updates, nothing else checked. Went to an earlier version and it came out as 26200 fine.