Windows 11 25H2 vs 26H1: 2026 Admin Comparison and Upgrade Guidance

This comparison is for Windows endpoint admins planning feature update policy in Intune, Windows Update for Business, Autopatch, WSUS, or Configuration Manager. It explains when Windows 11 25H2 is the right target for a managed fleet and when Windows 11 26H1 matters, which is only for specific new hardware.

The key point is scope. Microsoft's Windows 11, version 26H1 page describes it as a specialised release, available only preinstalled on select new devices, with the first devices using Qualcomm Snapdragon X2 Series processors. It is not offered through Windows Update and cannot be installed as an in-place update on existing devices.

What changed since June: Windows 11, version 26H2 reached general availability on 29 September 2026. For existing 25H2 and 24H2 devices, the next step is now 26H2 through a small enablement package, not 26H1. Devices on 26H1 cannot take 26H2 at all. If you are deciding whether to move 25H2 devices forward, read Windows 11 26H2 vs 25H2.

Quick Comparison: Windows 11 25H2 vs 26H1

Dates and builds come from Microsoft's Windows 11 release information, checked on 18 October 2026. The processor list comes from Windows 11, version 26H1 supported processors.

What Microsoft Says About 26H1

For admin planning, the most important Microsoft statements are about scope and servicing, not features:

• It is not a feature update. Unlike 24H2 and 25H2, 26H1 is not offered through Windows Update, so it cannot be installed in place on existing devices.
• It is not for broad deployment. Microsoft says 24H2 and 25H2 remain the recommended releases for enterprise deployment, and organisations can adopt 26H1 selectively for new hardware without changing existing plans.
• It cannot take the second-half 2026 feature update. 26H1 is based on a different Windows core from 24H2, 25H2 and 26H2. Microsoft says these devices "will have a path to update in a future Windows release", without a date.
• It is serviced normally. 26H1 receives monthly security and non-security preview updates, with 24 months of servicing for Pro and 36 months for Enterprise from its 10 February 2026 release.

That changes the decision:

• Do not build any Windows Update for Business or Intune feature update plan around moving existing devices to 26H1.
• Do review 26H1 when buying new hardware that ships with it.
• Do keep reporting logic aware of three build families now (26200, 26300 and 28000), so 26H1 and 26H2 devices are not misclassified as outliers.

Key Differences for Admins

Servicing and Upgrade Path

Windows 11 25H2 is still a normal target for existing enterprise endpoints, and it now has a straightforward next step: the 26H2 enablement package, which installs like a monthly update with a single restart in most scenarios. See the 26H2 enablement package pilot gate for that rollout.

Windows 11 26H1 needs a different handling model. Treat it as a supported release for specific new devices, with its own servicing track. It will not join your annual feature update cycle until Microsoft publishes a future path, so plan to service 26H1 devices with monthly updates only for now.

Intune and Update Rings

For Intune-managed fleets, keep feature update policies explicit. If a policy should hold existing devices on 25H2, target 25H2 directly. If it should move them to 26H2, target 26H2 directly. Never rely on a vague "latest" approach.

For 26H1 devices, use a separate dynamic group or a hardware-specific assignment. Do not assign them to a 26H2 feature update policy and expect the enablement package to install; it does not apply to 26H1. Track build family, OEM model, Autopilot profile, update ring and compliance policy separately until the device class is proven stable.

Hotpatch and Autopatch

Microsoft's release information states that hotpatching is not available on Windows 11, version 26H1. If you use Windows Autopatch hotpatch updates for 25H2 or 26H2, exclude 26H1 devices from those rings and service them with the standard monthly cumulative update.

Reporting and Compliance

Update reporting should not flag 26H1 devices as unmanaged simply because they are outside the 25H2 build family. At the same time, do not treat 26H1 as a target for devices that Microsoft does not offer it to.

Useful checks include:

• OS build family: 26200 for 25H2, 26300 for 26H2 and 28000 for 26H1.
• Device model and processor family.
• Whether the device shipped with 26H1.
• Whether the device is assigned to a 25H2 or 26H2 feature update policy, a 26H1-specific ring, or a hold group.
• Whether compliance policies use minimum build logic that accidentally excludes 28000, or treats it as "newer than 26H2".

This read-only check reports the version and build family on a device:

$cv = Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion'
$family = switch ($cv.CurrentBuild) {
  '26100' { '24H2' }
  '26200' { '25H2' }
  '26300' { '26H2' }
  '28000' { '26H1' }
  default { 'Other or older' }
}
[pscustomobject]@{
  DisplayVersion = $cv.DisplayVersion
  Build          = "$($cv.CurrentBuild).$($cv.UBR)"
  Family         = $family
}

Expected output on a 26H1 device with the October 2026 update is DisplayVersion 26H1, Build 28000.3231 or later, and Family 26H1.

Known Issues Are Shared

The open items on the 26H1 release health page also list 25H2 and 26H2 as affected. As of the 13 October 2026 updates, two remain only mitigated on all of them:

• Remote Desktop fails for non-admin users with error 0xC000000D when the host has Administrator protection enabled. The Windows security baselines for 24H2, 25H2 and 26H2 enable Administrator protection by default.
• USB Audio Class 1.0 devices fail to start or produce no sound.

The AVD and FSLogix black-screen issue is resolved on 26H1 by KB5127646 and on 25H2 by KB5127648. None of these is a reason to choose one release over the other. They are reasons to keep both on the latest monthly update.

Recommended Approach in October 2026

Final Recommendation

As of October 2026:

• Use Windows 11 25H2 or 26H2 as the feature update target for existing managed fleets. For 25H2 devices, moving to 26H2 is a scheduling decision, not an emergency.
• Treat Windows 11 26H1 as a separate path for supported new hardware only. It cannot replace 25H2, and it cannot move to 26H2.
• Keep Intune update rings, Autopatch assignments and compliance policies explicit, so 25H2, 26H2 and 26H1 devices are each measured correctly.

Most organisations should only run 26H1 where hardware or procurement creates a real need, and should accept that those devices sit outside the annual feature update cycle until Microsoft publishes their next step.

Operational Decision Framework For Endpoint Teams

Use this sequence before changing broad feature update policy:

1. Confirm the servicing path for each hardware class: 25H2 staying put, 25H2 or 24H2 moving to 26H2, or 26H1 preinstalled with monthly servicing only.
2. Separate rings by build family, not by department alone. A finance pilot ring that mixes 26200, 26300 and 28000 devices will create false compliance noise.
3. Exclude 26H1 devices from hotpatch rings and from any 26H2 feature update policy.
4. Update Autopilot and ESP expectations for any model that boots into a different build family than your documentation assumes.
5. Recheck security baselines after the first 26H1 pilot wave: Defender platform version, Secure Boot state, BitLocker protectors, Administrator protection, and any CIS or custom hardening packs.
6. Train the helpdesk on which build strings are expected, so "wrong OS version" tickets are triaged correctly.

When Not To Broaden 26H1

Do not expand 26H1 beyond required hardware when:

• Application certification is still tied to the 25H2 or 26H2 build family
• Your feature update policy says "latest" without an explicit target release version
• Compliance policies use minimum build logic that cannot express several supported families cleanly
• The estate depends on hotpatch or on IoT Enterprise devices
• You need every device on the same annual feature update cadence
• Driver or firmware quality for the new silicon class is still failing pilot machines

In those cases, keep 25H2 or 26H2 as the standard and isolate 26H1 to procurement-driven exceptions with named owners.

Validation Evidence To Collect

Procurement And Lifecycle Note

Hardware buyers and endpoint engineers need a shared rule:

• The default corporate catalogue stays on models and images aligned to the broad 25H2 or 26H2 target where possible
• Snapdragon X2 SKUs that ship with 26H1 are ordered only into a labelled exception catalogue
• Exception devices get a distinct Autopilot profile, update ring and support article from day one, plus a note that they will not take the annual feature update until Microsoft publishes a path

Without that rule, procurement creates an unmanaged second fleet, and the update team discovers it through compliance failures.

Primary Sources

• Windows 11 release information
• Windows 11, version 26H1
• Windows 11, version 26H1 supported processors
• Windows 11, version 26H1 known issues and notifications
• Windows Update for Business feature updates
• Intune feature update policies
• Windows Autopilot overview

Related Reading

• Windows 11 26H2 vs 25H2
• Windows 11 26H2 enablement package pilot gate
• Secure Boot CA 2023 Rollout Readiness
• Windows Update for Business Deferral Not Respected
• Hardening Windows 11 with CIS Benchmark Level 1
• Patch Management hub