Microsoft put Windows 11 26H2 into the Release Preview Channel on August 27 as a small enablement package. How the mechanism works, which features switch on for managed devices, the KB numbers in circulation, and the October 13 deadline for 24H2 Home and Pro.
Windows 11 26H2 reached the Release Preview Channel on Thursday, August 27, as build 26300.9278, and it arrives the way recent Windows 11 releases have: as a small enablement package, not a full operating-system upgrade. Devices already on 24H2 or 25H2 share a servicing branch with it, which changes what “upgrading” means in practice and what an administrator needs to test.
This guide covers the mechanism, the features that switch on for managed devices, the update identifiers circulating in community trackers, and the date that matters most for Home and Pro machines. It leans on BetaNews, Pureinfotech and a Windows 11 Forum thread that reproduces Microsoft’s announcement. Microsoft’s own pages were not reachable for this article, so identifiers are flagged where they rest on secondary sources.
- Released: build 26300.9278 to the Release Preview Channel on August 27, 2026. General availability is planned for later this year with no exact date given.
- Mechanism: an enablement package (eKB) that switches on features already present on the device, rather than replacing core components.
- Servicing: 24H2, 25H2 and 26H2 share one servicing branch and receive identical monthly security and quality updates.
- Deadline: Windows 11 24H2 Home and Pro stop receiving updates on October 13, 2026. Enterprise and Education editions continue until October 12, 2027.
What an enablement package actually does
A traditional feature update downloads a new operating-system image, rebuilds the system in place and restarts several times. An enablement package does almost none of that. The code for the new features has already arrived through earlier monthly cumulative updates, sitting dormant, and the package flips the switch that activates it. That is why the packages listed in the Windows 11 Forum thread weigh in at roughly 173 to 174 KB.
BetaNews quotes Microsoft describing 26H2 as “the same source code with only the additional features turned on.” In other words, there is no second codebase to maintain or to test separately. A device that moves from 25H2 to 26H2 keeps its drivers, its apps and its servicing path. After the move it returns to the standard monthly update cadence.
BetaNews also reports this is the first time Microsoft has delivered a new Windows 11 version to Insiders before general availability. That is a secondary claim, and it fits the logic of the change: a version that is mostly a switch can be tested early because most of its code already shipped.
One servicing branch, three versions
Per the same coverage, Windows 11 24H2, 25H2 and 26H2 sit on a shared servicing branch. Practically, they get the same monthly security and quality updates. A patch deployed in September lands the same way on all three, so the version number on a device stops predicting which fixes it has.
Pureinfotech adds that the cumulative update behind build 26300.9278, KB5120998, is an optional install for 24H2 and 25H2 on the stable channel and is offered to 26H2 on Release Preview. For anyone maintaining a mixed fleet, that overlap is the useful part. Patch compliance reporting does not need three separate tracks, though feature behavior still differs once the switch is on.
What turns on for managed devices
For commercial customers, 26H2 enables three experiences that were built into earlier releases but off by default: Windows settings backup, app-specific taskbar actions, and some File Explorer improvements. Pureinfotech notes that many other 26H2 features had already reached devices gradually through monthly updates, and it does not itemize them.
The distinction matters for change management. Features that arrive through a monthly update appear on a schedule you can see in release notes. Features unlocked by the package appear when the package installs, so the version change itself becomes the moment user-visible behavior shifts. Settings backup, in particular, touches user data flows and deserves a policy review before it is on for everyone.
How to get the build as of August 28
Enrolled Release Preview Insiders can open Settings, go to Windows Update and select 26H2 for download and install. BetaNews says it does not install automatically, and Pureinfotech points to the “Get the latest updates as soon as they’re available” setting. Clean-install ISOs were not available yet; both outlets say they are coming soon.
Administrators in the Windows Insider Program for Business can deploy it using Windows Update client policies or WSUS. BetaNews says Azure Marketplace access opened on August 27 as well. The Windows 11 Forum thread lists the enablement package for the retail 26H2 release and a separate one for the experimental Insider Refresh build, so the right package depends on the channel and current build of the device.
| Identifier | What it is | Reported by |
|---|---|---|
| Build 26300.9278 | Release Preview build of Windows 11 26H2, released August 27 | BetaNews, Pureinfotech, Windows 11 Forum |
| KB5120998 | Cumulative update; optional on stable 24H2 and 25H2, offered to 26H2 on Release Preview | Pureinfotech |
| KB5121794 | Enablement package for the retail 26H2 release, about 174 KB | Windows 11 Forum thread |
| KB5122776 | Enablement package for the Insider Refresh build 26340 (experimental), about 173 KB | Windows 11 Forum thread |
The KB numbers above come from a community forum and a news site, not from Microsoft’s release-health pages. Confirm them against Microsoft’s documentation before building deployment rules around them.
The October 13 deadline for 24H2 Home and Pro
The date with a hard consequence is October 13, 2026. BetaNews and Pureinfotech both report that Windows 11 24H2 Home and Pro stop receiving updates then, while Enterprise and Education editions stay supported until October 12, 2027. General availability of 26H2 is still undated, so anyone on 24H2 Home or Pro has to plan around the calendar, not the release.
Because 24H2 and 25H2 share the servicing branch with 26H2, moving a machine to 25H2 or 26H2 is a small step in terms of code. The practical risk is administrative: devices that nobody inventoried until the deadline passes.
A test plan for IT teams
This section is advice, not reporting. A sensible order is below.
- Inventory the fleet by version using winver or your management console, and flag every 24H2 Home and Pro device.
- Confirm the latest cumulative update is installed on pilot machines before adding the enablement package.
- Pilot 26H2 on a small ring through Windows Update client policies or WSUS, and watch the three newly enabled features for policy conflicts.
- Review settings backup against your data-handling rules before it is on by default.
- Keep a clean-install ISO plan ready for when Microsoft publishes the media.
What is not known yet
Microsoft has not given a general availability date beyond “later this year.” The sources do not list new hardware requirements, saying only that devices must meet the existing Windows 11 requirements. Neither report lists known issues for this build, which is not the same as there being none. Release Preview is a validation channel, and the first weeks of any build tend to surface edge cases that release notes miss.
Questions readers ask
Is Windows 11 26H2 a full upgrade?
No. It is delivered as an enablement package that activates features already on the device, and 24H2, 25H2 and 26H2 share one servicing branch.
When is general availability?
Microsoft has said only that it will arrive later in 2026. No exact date had been announced as of August 28.
Do I need new hardware?
The sources mention only the existing Windows 11 hardware requirements. No new requirement is reported.
What happens to 24H2 on October 13?
Home and Pro editions stop receiving updates that day, per BetaNews and Pureinfotech. Enterprise and Education editions are supported until October 12, 2027.
Sources
