There is no retail 26H2 ISO yet, you can integrate the 26H2 EKP in any existing retail ISO or install it manually afterwards. ps, he meant to say that you are asking 26H2 questions in the 26H1 thread, 26H2 is not related to 26H1, this is the correct thread: [DISCUSSION] Windows 11 Build 26x00 (PC) [24/25/26H2 Retail- GE-release]
26H2 info and downloads will be in the following thread (when released for public) [DISCUSSION] Windows 11 Build 26x00 (PC) [24/25/26H2 Retail- GE-release]
Thanks, this worked, I used the MVS ISO and ran and in-place upgrade with setup.exe and now Windows Update works again. How is it so that 28020 has a different base build? I switched to the Canary channel when the builds were still 27xxx and upgraded through to 28000 and later 28020? And if so, how come MS allows switching to the Release Preview channel from Beta if the base builds are different?
they have been doing this for about a year now if you want to know what the base build is, just download the corresponding LCU and check the update.mum file, for retail and RP builds it's 28000.1 msft will eventually publish full builds in the WU (in-place upgrade style updates), it's not a hard block or anything just use ISO as in-place upgrade if it's not possible to switch your build correctly using WU at that particular moment
There is no precise data on any fundamental structural differences, apart from separate development branches and update channels. Support for newer processors does not rule out backward compatibility or proper operation on older processors. Ultimately, all negative recommendations from users are based only on Microsoft’s general description of the intended use for newer devices, while almost no one can point to any actual issues when running it on x86-64 processors.