Hi Bert,
At this point to get off of a 28xxx build
you need to do a clean install of 26300
using MCT.
Then rejoin Insiders on the Dev Channel
if you wish to stay in Insiders.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
With all the talk about 26H2 being rolled out to everyone now, I see no way to do this from the Beta 26H1. With today's 28020.3262 update, I fully expected that under settings > windows update > windows insider program > advanced options, there would have been a 26H2 button available.
No such luck.
Hi Bert,
At this point to get off of a 28xxx build
you need to do a clean install of 26300
using MCT.
Then rejoin Insiders on the Dev Channel
if you wish to stay in Insiders.
If users are being provided with an option to move from Windows 11 25H2 to 26H1, there should ideally also be a clear and supported migration path from 26H1 to the subsequent Windows release, such as 26H2.
Currently, the guidance in this discussion suggests that once a device moves to 26H1, there is no in-place migration path to 26H2 through the Windows Insider channel selector, and moving to 26H2 may require a clean installation.
This creates an important consideration for users choosing 26H1. Someone opting into 26H1 from 25H2 could reasonably expect that they will eventually be able to move forward to the latest Windows release through Windows Update rather than effectively becoming locked into a release path that requires an OS reinstall to change branches.
**If 26H1 is intentionally on a separate servicing or development path, I think this limitation should be communicated very clearly before users are given the option to move from 25H2 to 26H1. Ideally, Microsoft should also provide a supported forward migration path that allows 26H1 systems to transition to a later Windows release without requiring a clean **installation.
Otherwise, users may select 26H1 expecting a normal forward upgrade experience, only to discover later that moving to the latest release requires significantly more effort.
If the AI answer is correct, that there is no path from Beta 26H1 to Beta 26H2, then I think the Windows Insider announcements on 26H2 should make that clear.
For example, before installing 28020.3262, I had the option of moving back to Release Preview, at which point I would have had a path to 26H2. Today, having installed this latest Quality Update, that Release Preview option was greyed out.
No big deal. Just the kind of annoyance that risks happening with the complications created by the new Windows Insider arrangement. In my head, any Beta channel choices should be ahead of Release Preview choices?
AI answer
There is no in-place migration path from Beta 26H1 to 26H2 through the Insider channel selector.
26H1 is on a different Windows core than 24H2, 25H2, and 26H2. Because of that:
That is why no 26H2 option appears under Settings > Windows Update > Windows Insider Program > Advanced options on Beta 26H1.
What is supported:
Also, 26H2 general availability applies to eligible Windows 11 version 24H2 and 25H2 devices with Get the latest updates as soon as they’re available turned on. That rollout does not mean 26H1 devices can switch over directly.
References:
Hello Bert,
One has never been able to go to a lower build # without doing a total clean install. You can upgrade for example but you cannot downgrade from 28xxx to 26xxx . These 2 builds you are referring to are based on different base installs. It's been always like this since day 1 of Windows back in 1985.
eg:
26100.1.240331-1435.GE_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US (Germanium)
28000.1.251103-1709.BR_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US (Bromine)
Regards,