• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Windows 11 26H2

GotNoRice

GotNoRice

[H]F Junkie
2FA
Joined
Jul 11, 2001
Messages
12,818
As of today, the enablement package for 26H2 no longer has insider restrictions attached to it. That means you can now use it to update a regular 25H2 install to 26H2, even if you are not enrolled in any of the insider/preview channels. Risk is minimal since 24H2, 25H2, and 26H2 all share the same underlying code.

I would recommend updating to 26200.9278 first, which is the "preview" version of 25H2 that was released today, available to anyone who toggles the "Get the latest updates as soon as they're available" option in Windows Update. Installing the enablement package will convert your 26200 (25H2) install to 26300 (26H2) after a quick reboot.

https://gotnorice.com/Windows11.0-KB5121794-x64.zip
 

Attachments

  • Windows11.0-KB5121794-x64.zip
    170.5 KB · Views: 0
I thought 26H2 was primarily for ARM systems and some other special cases, or was that only when it first came out, cause MS had it plastered all over not to use it on normal systems or something..
 
MrGuvernment said:
I thought 26H2 was primarily for ARM systems and some other special cases, or was that only when it first came out, cause MS had it plastered all over not to use it on normal systems or something..
Click to expand...

"26H2" is the same codebase as "24H2" and "25H2"; with the shared code known internally at Microsoft as "Germanium". 26H1 is actually based on a newer version of the Windows code, called "Bromine". 26H1 was an early release of Bromine that was targeted at ARM systems, because it contains a lot of ARM-specific improvements. But Bromine is not an "ARM version of Windows" or anything like that. There is even an x86 version of "26H1" on the insider channels right now. We will most likely see the official x86 version of Bromine released either as 27H2 or potentially even "Windows 12", at which point the branches will be merged once again.
 
Is this the version that lets you tinker with the new Start menu's size and scope?
 
Installed the update to 26200.9278 yesterday which took quite a long time. Installed the update to 26300.9278 today which went quickly. Don't notice any changes and everything works just as it did--thankfully! Figure it will be pushed as an update later so might as well take the medicine now.

Am running the O'Connell Desktop Restore so maybe that breaks the update. Fine with me. Setup is just as I like it. Was waiting to see if things broke, moved or changed. All the pieces made it through the transporter unscathed. Checkmate.
 
Last edited:
tordogs said:
Installed the update to 26200.9278 yesterday which took quite a long time. Installed the update to 26300.9278 today which went quickly. Don't notice any changes and everything works just as it did--thankfully!
Click to expand...
That's really the point. Feature rollouts are gradual across versions that share the same codebase. Moving to 26H2 is more just for them end of life older branches. But it makes me wonder if 24h2,25h2,26h2 are all the same why bother having different end of life dates.

It's almost like Windows is preparing to go back to having a single version that last several years with incremental service packs.
 
Last edited:
You must log in or register to reply here.
Back
Top