Windows 11 Versions Explained: 24H2, 25H2, 26H1, and What’s Next

Windows 11 now ships on two separate codebases, and that changes which version your PC can run. 24H2, 25H2 and 26H2 share one platform (Germanium) and update through tiny enablement packages. 26H1 runs on a newer platform (Bromine) and ships only on select new Arm hardware such as Snapdragon X2 laptops. Microsoft released 26H2 on September 29, 2026, and 24H2 Home and Pro stop receiving updates on October 13, 2026.

Quick Takeaways

• 24H2, 25H2 and 26H2 share the Germanium platform (builds 26100, 26200, 26300). Moving between them takes one restart and a small download.
• 26H1 (build 28000, platform Bromine) is hardware-bound. It is not offered to existing PCs, and it cannot upgrade to 26H2.
• 26H2 resets the support clock to 24 months (Home/Pro) and 36 months (Enterprise/Education).
• 27H2 (2027) is widely reported as the release that merges both branches. Microsoft has not confirmed the version name.

Windows 11 Version Comparison Table

Prerequisites: Identify Your Current Windows 11 Version

Check your version before you decide anything. The build number tells you which branch you are on.

Method 1: winver

Press Win + R, type winver, and press Enter. The dialog shows the version (for example, 25H2) and the OS build (for example, 26200.xxxx).

Method 2: PowerShell

Open Windows Terminal or PowerShell and run:

(Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion') | Select-Object DisplayVersion, CurrentBuild, UBR

• DisplayVersion returns the marketing version (24H2, 25H2, 26H2).
• CurrentBuild returns the build family (26100, 26200, 26300, 28000).
• UBR is the Update Build Revision, the number after the dot. It increments with each cumulative update.

Method 3: Command Prompt

systeminfo | findstr /B /C:"OS Name" /C:"OS Version"

This prints the edition and full build string. Use it in remote sessions where a GUI is unavailable.

Read the Build Number

Conceptual Overview: Why Versions Behave Differently

The Enablement Package Model

Microsoft stopped shipping full OS reinstalls for every annual release on the Germanium branch. Monthly cumulative updates deliver the code for new features in advance, and those features sit dormant. An enablement package (eKB) then flips a switch that changes the version string and turns the features on. The result is a restart and a download similar in size to a monthly patch.

This is why 24H2, 25H2 and 26H2 share one servicing branch. Compatibility with apps and drivers stays identical across them.

The Platform Split: Germanium vs. Bromine

Windows has one codebase per “platform release.” Germanium launched with 24H2 in 2024. Bromine is a newer platform with core changes, including support for ARMv9 hardware. Microsoft shipped it as 26H1 on specific new silicon only.

Because Bromine is further along the development chain, its build number (28000) is higher than Germanium’s 26300. Windows upgrades only move to a higher build number, so a 26H1 device cannot take 26H2. Going from 28000 to 26300 would count as a downgrade, which requires a clean reinstall.

Version-by-Version Breakdown

Windows 11 24H2 (Build 26100)

24H2 is the Germanium baseline, released October 1, 2024. It introduced the platform that three later versions would reuse. Home and Pro editions reach end of updates on October 13, 2026. After that date, these PCs stop receiving security patches.

Enterprise and Education editions on 24H2 keep updates until October 2027.

Windows 11 25H2 (Build 26200)

25H2 arrived September 30, 2025 as an enablement package on top of 24H2. It added no new hardware requirements and few headline features. Its main value was resetting the support lifecycle. Home and Pro are supported until October 12, 2027.

Windows 11 26H1 (Build 28000)

26H1 is not a feature update for 25H2. Microsoft built it for new Arm silicon, starting with Qualcomm Snapdragon X2 PCs, with NVIDIA-based Arm devices also reported as targets. Key facts:

• It is preinstalled only. Microsoft does not offer it through Windows Update to existing PCs.
• Sideloading an ISO onto an existing PC is not a supported upgrade path.
• Its support ends March 14, 2028 (Home/Pro) and March 13, 2029 (Enterprise/Education).
• Microsoft states that 26H1 devices will get an upgrade path in a future Windows release, with no date or version number published.

Windows 11 26H2 (Build 26300)

26H2 is the 2026 annual feature update, released September 29, 2026. Key facts:

• Delivered as an enablement package to PCs on 24H2 or 25H2. It needs one restart.
• Adds no separate exclusive feature set. It enables features from the past year that shipped turned off by default in 25H2. Microsoft lists point-in-time restore as one recovery addition.
• Resets support to 24 months (Home/Pro) and 36 months (Enterprise/Education).
• Enables the Machine Identity Isolation feature behavior, which matters for domain-joined devices (see Troubleshooting).
• Microsoft’s first monthly security update that carries 26H2 release notes is slated for October 13, 2026.
• Microsoft has announced the end of Snapdragon 850 support after 26H2.

Step-by-Step: Install Windows 11 26H2

Step 1: Confirm Eligibility

Your PC must run 24H2 or 25H2 (builds 26100 or 26200). A device on build 28000 cannot take this update.

Step 2: Install Pending Updates

Go to Settings > Windows Update and install all pending cumulative updates. The enablement package needs the latest servicing stack.

Step 3: Opt In to Early Availability

Switch on “Get the latest updates as soon as they’re available.” Once your device qualifies, Windows Update shows a Download and install option for version 26H2.

Step 4: Restart and Verify

After the restart, run winver. You should see version 26H2 and build 26300.x.

(Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion').DisplayVersion

The output should read 26H2.

Step-by-Step: Pin Your PC to a Specific Version

Pro, Enterprise and Education editions can hold a device on a target version through Group Policy. This works well for pilot rings.

Via Registry (PowerShell, run as Administrator)

$path = 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'TargetReleaseVersion' -Value 1 -Type DWord
Set-ItemProperty -Path $path -Name 'ProductVersion' -Value 'Windows 11' -Type String
Set-ItemProperty -Path $path -Name 'TargetReleaseVersionInfo' -Value '25H2' -Type String

• TargetReleaseVersion = 1 enables the version pin.
• ProductVersion names the product line the pin applies to.
• TargetReleaseVersionInfo sets the version to hold. Change it to 26H2 to move forward.

Pinning delays feature updates but does not extend support. A pinned PC still falls out of support when its version reaches end of updates.

Which Version Should You Run?

Troubleshooting and Real-World Scenarios

Scenario 1: The 26H2 Option Does Not Appear

1. Confirm the build with winver. Build 28000 means 26H1, which is never offered 26H2.
2. Turn on “Get the latest updates as soon as they’re available.”
3. Install all pending cumulative updates and restart.
4. Check for update blocks from policy or a compatibility hold in Settings > Windows Update.

Scenario 2: Update Fails With 0x80070002 or 0x800f0922

Error 0x80070002 means a required file is missing. Error 0x800f0922 often points to a full System Reserved partition or a servicing failure. Repair the component store first:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

• DISM /Online /Cleanup-Image /RestoreHealth repairs the Windows component store from Windows Update.
• sfc /scannow verifies protected system files and replaces corrupted ones.

Restart, then retry the update. If it still fails, reset the update cache:

net stop wuauserv
net stop bits
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
net start bits
net start wuauserv

• net stop wuauserv stops the Windows Update service so the cache folder can be renamed.
• ren ... SoftwareDistribution.old forces Windows to rebuild the update cache.

Scenario 3: Domain Machine Loses Secure Channel After 26H2

Microsoft documents that some Credential Guard-protected machine accounts can lose their secure channel with an on-premises Active Directory domain after 26H2. The cause: 26H2 begins honoring existing or policy-provisioned Machine Identity Isolation enforcement settings.

Before deployment:

1. Audit Group Policy and MDM for any Machine Identity Isolation setting.
2. Pilot on a small ring of domain-joined devices.
3. Review Microsoft’s release health page for the current mitigation.

Scenario 4: Audio Breaks After Updating

Microsoft’s release health page lists two audio-related issues: some apps that decode AC-3 (Dolby Digital) audio might close unexpectedly after the September 22, 2026 update (KB5124010) or later, and some USB Audio Class 1.0 devices might fail to start after 26H2. A Known Issue Rollback is available for the first. Check the release health page for current status before you troubleshoot drivers.

Scenario 5: Rolling Back

Windows keeps the previous version’s recovery data for a limited window. Go to Settings > System > Recovery to see whether Go back is available. For enablement packages, you can also remove the package with DISM:

DISM /Online /Get-Packages | findstr /i "Enablement"

This lists installed packages that contain the enablement entry. Removal rules depend on the package, so test in a lab first.

What’s Next: Windows 11 27H2 and the Platform Merge

Microsoft has not announced 27H2, but credible reporting points to the following:

Treat these as reported expectations, not commitments. Microsoft’s only firm statement is that 26H1 devices will get a path to a future Windows release.

Plan for a larger servicing event in 2027. A full upgrade takes longer than an enablement package and carries more driver and app compatibility risk. The Snapdragon 850 support cutoff after 26H2 hints that the next platform raises hardware baselines.

FAQ

Is Windows 11 26H2 a big update?

No. 26H2 installs as an enablement package with one restart. It switches on features already delivered through monthly updates to 25H2 and turns on some that were off by default.

Can Windows 11 26H1 upgrade to 26H2?

No. 26H1 (build 28000) uses a newer Windows core than 26H2 (build 26300). Those devices stay on 26H1 and receive monthly updates until Microsoft delivers the promised upgrade path in a future release.

When does Windows 11 24H2 reach end of support?

October 13, 2026 for Home and Pro editions. Enterprise and Education editions continue until October 2027. Installing 26H2 resets the lifecycle.

Do I need to upgrade from 25H2 to 26H2 right away?

No. 25H2 Home and Pro remain supported until October 12, 2027. Upgrade when you have validated your apps and drivers, or if you need the 24-month lifecycle reset.