What the new era of Windows Insider means for us

[rpodric]

Hi. You are probably well aware of the seismic changes in the WI program, the first wave of which arrived today:
https://blogs.windows.com/windows-insider/2026/04/24/were-moving-to-experimental-and-beta-announcing-new-builds

It wasn't a great surprise that an offlineinsiderenroll'd Dev build was turned into this after 26300.8289 (the second image is what others would see). Will doing a "Stop receiving" followed by a re-enroll in Dev (even though it's no longer called that) get things back on track? If not, is a v2.65 still possible? I hope MS hasn't cutoff this avenue.

When otherwise it would have been this:

Thanks

[abbodi1406]

"Stop receiving" will remove any enrollment, even the new one
re-enroll or new enroll via the script would not work properly

can you export and share these registry keys?

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SLS\Programs

[rpodric]

That's what I figured, so I didn't try Stop Receiving.

Here are the exports, zipped up.

Reg_items.zip

[rpodric]

Might be worth pointing out that on an extremely similar unsupported machine, also enrolled the same way, and also upgraded to the current build from the last Dev build, instead of seeing the screen that I saw (my first screenshot above), he shows no change from before. I doubt that will help with the next build, but it is curious.

[Ulti-P-Uszer]

I am also hoping for a new version of OLIE so that I can upgrade my Canary VM to Experimental channel.

[rpodric]

Today's 28300.8346 showed up in Windows Update anyway, and there was a further surprise on reboot: the new screen. Most importantly, Unenroll Device was toggled ON, and it said that it was "scheduled." So, I quickly changed that. Also, neither radio button was selected (that can be seen below).

[akuropka]

I installed 26300.8346 as well but didn't see any changes, still as shown in #29 (comment).

[rpodric]

@akuropka That's interesting. The user I mentioned above who was on that screen before this build, now has a screen identical to mine (shown in my last post). So, which screen shows up isn't following any logic that I can see. Regardless of screen, I'm guessing the builds will continue to come.

[akuropka]

Roughly going through registry I found the following differences between @rpodric and mine noteworthy.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\ClientState]
-"UICapabilities"=dword:00000001
+"UICapabilities"=dword:00000002
-"LastTransactionDuration"=dword:00000002
+"LastTransactionDuration"=dword:00000003
-"WNSServiceUriExpirationBinaryRegName"=hex:00,03,02,60,7c,ef,dc,01
+"WNSServiceUriExpirationBinaryRegName"=hex:00,28,4a,aa,42,ea,dc,01
-"WNSServiceUriExpirationInDaysRegName"=dword:0000001e
+"WNSServiceUriExpirationInDaysRegName"=dword:0000001d
-"CurrentCallsPerDayCount"=dword:00000007
+"CurrentCallsPerDayCount"=dword:00000003
-"FirstCallOfTheDayTime"=hex:dc,50,33,66,1a,da,dc,01
+"FirstCallOfTheDayTime"=hex:3b,e0,c1,4a,f5,d3,dc,01

[rpodric]

If it helps, this is what it is now here:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\ClientState]
"ValidateOnlineHr"=dword:80070002
"AllowFSSCommunications"=dword:00000000
"UICapabilities"=dword:00000002
"IgnoreConsolidation"=dword:00000001
"MsaUserTicketHr"=dword:00000000
"MsaDeviceTicketHr"=dword:00000000
"LastHR"=dword:00000000
"ErrorState"=dword:00000000
"PilotInfoRing"=dword:00000003
"RegistryAllowlistVersion"=dword:00000004
"FileAllowlistVersion"=dword:00000001
"LastTransactionDuration"=dword:00000007
"WNSRegistered"=dword:00000001
"WNSServiceUriExpirationBinaryRegName"=hex:00,28,4a,aa,42,ea,dc,01
"WNSServiceUriExpirationInDaysRegName"=dword:0000001d
"CurrentCallsPerDayCount"=dword:00000001
"FirstCallOfTheDayTime"=hex:08,95,d0,0b,7e,da,dc,01

[akuropka]

Btw I noticed I do not have the new Feature Flags menu in insider settings. Don't know if this is related...

[rpodric]

Right, that makes sense since you're not on the new screen (it's all or nothing). Fortunately, if you're marooned on that screen, it's not that bad since Vivetool has everything there (which is only five things currently, shown below) and dozens more. It's not as user-friendly though.

[rpodric]

I installed 26300.8346 as well but didn't see any changes, still as shown in #29 (comment).

If you still didn't pick it up, even with today's build, try (then reboot):

Windows Registry Editor Version 5.00

# New Windows Insider Program experience, including Advanced Options to choose version and Feature Platforms releases. ViVetool ID: 61157505 (CFR RKey: 34583695)
# Updates the Windows Insider Program settings experience with clearer channel definitions and improved navigation. Provides more transparency into available preview features and simplifies build selection.
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\14\34583695]
"EnabledState"=dword:00000002
"EnabledStateOptions"=dword:00000000