Microsoft Plans Windows 11 26H2 Update for Late September to Early October 2026
Microsoft will release Windows 11 26H2 between late September and early October 2026, a modest iteration built on the 24H2 servicing branch. Devices running 24H2 or 25H2 can upgrade via a 174KB enablement package, while older versions require a full feature update of roughly 6.5GB. The shared servicing model reduces compatibility risks and testing burdens, as Microsoft shifts toward smoother, lower-risk feature delivery.
Unlike previous annual feature updates that introduced numerous new features and significant underlying changes, 26H2 will be a relatively modest iteration. Its focus is not a major system overhaul but a continuation of the existing code branch, enabling pre-installed features through a lighter mechanism to reduce compatibility risks and improve system stability. In past years, Windows feature updates typically delivered dozens of new features and improvements at once, accompanied by changes to the underlying system version. After Microsoft released Windows 11 24H2 in October 2024, the system experienced various issues, including hardware compatibility failures, feature regressions, and stability anomalies, some of which took months to resolve. This prompted Microsoft to adjust its strategy to reduce the risks associated with major annual version transitions.
During the Windows 10 era, Microsoft referred to this update approach as "Windows as a Service," continuously pushing new features to the system. However, frequent updates did not fully resolve compatibility issues caused by changes in the underlying code branch. 24H2 is the most recent major feature update built on a new servicing branch, while subsequent 25H2 and the upcoming 26H2 are based on the same underlying branch as 24H2. Microsoft employs a "shared servicing" model, under which Windows versions using the same codebase can share security updates, non-security fixes, compatibility validation, and pre-release regression testing. The core difference between versions lies mainly in which additional features the new version enables.
Upgrading from Windows 11 25H2 to 26H2 is not equivalent to switching to a completely new system branch. 26H2 and 25H2 use the same source code, with the only difference being that the former enables more feature switches. Therefore, if an issue affects 26H2, it typically also affects 25H2; likewise, fixes for that issue will apply to both versions. For enterprise users, this does not mean they can skip pre-deployment testing entirely, but testing can focus on newly enabled features without repeating the full application compatibility, hardware compatibility, and certification processes. This mechanism significantly reduces the testing and maintenance burden of cross-version upgrades.
Shared servicing is not a new concept introduced with Windows 11. Microsoft adopted a similar approach with Windows 10 1909 in 2019, when new code for 1909 was delivered to Windows 10 1903 devices via updates, but the features remained disabled by default until the official release. Windows 11 23H2 also used a similar update logic relative to 22H2; now 24H2, 25H2, and 26H2 form a new shared servicing branch. Because they share the same servicing branch, Microsoft does not need to wait for the official release of 26H2 to begin distributing relevant code to users. Many components required for subsequent versions can be installed on devices in advance through monthly cumulative updates, but remain disabled by default. Microsoft confirmed that within the same servicing branch, monthly cumulative updates will cover different Windows versions, and the next version's new feature payload will be included in the updates in a disabled state.
When users update versions, they primarily receive feature enablement and a new support lifecycle, rather than re-downloading the entire system. This mechanism also offers more flexible choices for users with different needs. Users who prioritize stability can remain on their current version and wait for new features to undergo longer validation; those who wish to maintain support coverage can upgrade when their version approaches end of support. For example, 24H2 support ends in October 2026, so users can first upgrade to 25H2 and then move to 26H2 at an appropriate time.
After 26H2 is officially released, users can install it via three methods depending on their current system version: ISO image, full feature update, or enablement package. The ISO image corresponds to a complete system installation, while a full feature update is typically used for devices that need to switch to a different underlying servicing branch. For devices that already have the required code, Microsoft can provide a smaller enablement package, known as eKB. Microsoft stated that after completing the new version, it will provide both a full feature update and an enablement package to Windows Update. The full feature update is used when the underlying system branch changes; the enablement package allows devices already running Windows 11 25H2 to quickly switch to 26H2.
Conversely, users still on Windows 11 22H2 or 23H2 branches will need to receive a full feature update. For example, upgrading from Windows 11 23H2 to 26H2 requires a large-scale underlying migration because 23H2 is not in the same servicing branch as 24H2, 25H2, and 26H2. Microsoft has not yet announced the final installation package size for a direct upgrade from 23H2 to 26H2, but the previously announced 23H2-to-25H2 case can serve as a reference: the full update includes approximately 5.3GB of the Windows 11 24H2 base image, plus about 887MB of cumulative update packages, totaling nearly 6.5GB.
In contrast, upgrading from Windows 11 24H2 or 25H2 to 26H2 is extremely low-cost. Previous information shows that on devices already running 24H2 or 25H2, the Windows 11 26H2 enablement package is only about 174KB. Microsoft used a similar upgrade scenario to illustrate that this size is roughly three ten-thousandths of the full 6.5GB feature update. The reason is that the vast majority of code required for the next version has already been stored on the computer through previous cumulative updates; the enablement package is mainly responsible for activating new features, restarting the system, and updating Windows' internal build number and support lifecycle. Installing Windows 11 26H2 via the enablement package roughly proceeds in four stages: first, the feature flags for new code are changed from disabled to enabled; then the system restarts; after restart, the corresponding features are officially activated; finally, Windows' internal build number is updated.
Microsoft hopes this approach will reduce compatibility and stability issues caused by major version upgrades, shifting Windows feature evolution from a one-time large-scale switch to a smoother, lower-risk continuous update model.