Windows 11’s newest annual update is a quick install for many PCs, but some of Microsoft’s newest Windows machines cannot move to it at all. That split makes version number alone a poor guide to how easy the upgrade will be.
Microsoft began rolling out Windows 11 version 26H2, also called the Windows 11 2026 Update, on Sept. 29. PCs on 24H2 or 25H2 can move to it through a lightweight enablement package and a single restart, while select 26H1 devices are excluded because they use a different Windows core.
The timing is especially important for Windows 11 24H2 Home and Pro, which reach end of support on Oct. 13. Microsoft is also releasing 26H2 gradually, so eligible PCs may not receive it immediately.
The fast route is limited to 24H2 and 25H2
PCs running Windows 11 24H2 or 25H2 get the streamlined route. Microsoft says those releases and 26H2 use the same underlying operating-system files, allowing the company to activate 26H2 with a small enablement package rather than a conventional feature upgrade.
Much of the required code is already present on updated 24H2 and 25H2 systems but remains inactive until the package turns it on. The process requires one restart, while eligible managed PCs can also reduce scheduled reboot frequency through Windows 11 hotpatching.
The enablement package has a prerequisite: systems must already have the Sept. 22 KB5124010 preview update or a later cumulative update installed. On consumer and unmanaged PCs, Microsoft says the earliest offers go to eligible 24H2 and 25H2 systems with “Get the latest updates as soon as they’re available” enabled in Windows Update.
Earlier Windows releases do not qualify for this route. Select new PCs running Windows 11 26H1 are also excluded because that release uses a different Windows core; Microsoft says those devices will get a path to a future Windows release instead.
Eligibility still does not guarantee immediate delivery. Microsoft may place safeguard holds on systems with known compatibility problems, while organizations can deploy 26H2 through Windows Autopatch and the Microsoft 365 admin center and validate it on a limited group before expanding deployment.
Safeguard holds can still slow deployment
Administrators should first verify the installed Windows version under Settings > System > About or by running winver. Systems on 26H1 or releases earlier than 24H2 need separate handling because they do not qualify for the enablement-package path.
As of Oct. 3, Microsoft’s Windows release health dashboard lists three mitigated 26H2 issues. They involve some USB Audio Class 1.0 devices, some domain-joined systems protected by Credential Guard and desktop-loading problems reported mainly in virtual desktop environments.
A separate September out-of-band Windows update also addressed Remote Desktop, Hyper-V and USB audio problems caused by an earlier patch. That recent disruption reinforces the case for staged deployment even when a feature update itself is designed to install quickly.
Organizations using custom or legacy drivers should test before broad deployment. Windows 11 26H2 removes default trust for cross-signed drivers after Windows audits compatibility for at least 100 hours and three restarts.
For most 24H2 and 25H2 fleets, 26H2 should behave more like routine servicing than a traditional Windows migration. Administrators still need to separate the devices that qualify for the fast path from systems that require a different upgrade plan.
Read more: Microsoft has already been delivering fixes and feature changes across both releases; a recent Windows 11 preview update for 24H2 and 25H2 shows how closely their servicing remains aligned ahead of the 26H2 switch.