New Update Microsoft confirms Windows 11 26H2, urges IT admins to prepare for release

Gandalf_The_Grey

Level 85
Thread author
Verified
Honorary Member
Top Poster
Content Creator
Well-known
Forum Veteran
Apr 24, 2016
7,838
6
83,251
8,389
55
The Netherlands
Windows 11 typically follows an annual update cycle, but Microsoft recently broke that tradition a bit by releasing a "26H1" version in the first half of this year as a "scoped" build for select new silicon PCs only. This version was not available for customers using 24H2 and 25H2 builds, as Microsoft is busy preparing version 26H2 for them, confirmed officially for the first time.

In a Windows IT Pro blog, Microsoft has urged IT admins to prepare for the upcoming release of Windows 11 version 26H2. The company has confirmed that this will be a small enablement package (eKB) that will simply light up certain disabled features that are already present in the operating system's code base. This means that the "refined" Windows update and deployment experience will be simpler and quicker, with minimal disruptions, as the feature update will simply toggle a few flags rather than performing a complete replacement.

Microsoft has explained that this is all possible because the standard Windows 11 releases share the same servicing branch and hence, the same source code. However, this also means that Windows 11 26H1 users won't be able to upgrade to 26H2 as that is a different branch, but this is something we have known for a while now.

Similar to previous annual feature updates, Windows 11 26H2 will offer the following support cycles:
  • 24 months of support for Home, Pro, Pro EDU, and Pro for Workstations editions
  • 36 months of support for Enterprise, Education, IoT Enterprise, and Enterprise Multi-session editions
Microsoft has not confirmed a concrete release date for Windows 11 26H2, but noted that it is "coming soon". If we go by the ongoing release cadence, we can expect it to begin rolling out in early October 2026.
 
Microsoft’s IT Pro post is basically confirming that Windows 11 26H2 will be delivered like the recent “enablement package” style releases (a small eKB that turns on features already present), rather than a full in-place feature upgrade.

What “enablement package (eKB)” means in practice
  • If you’re already on the supported baseline that shares the same servicing branch with 26H2, the update experience is typically closer to a regular cumulative update in terms of speed and disruption (smaller download, faster install, fewer migration-style steps).
  • The “new features” are often already in the OS bits, but remain disabled until the eKB flips them on. That also means some behavior changes can still appear after the switch, so testing is still important.
  • From an operational/security standpoint, the big win is predictability: fewer moving parts compared to a full feature upgrade, and usually less chance of upgrade-time failures due to drivers or app migrations.

Important catch: 26H1 vs 26H2 branch split
Microsoft is also reiterating the split you quoted: those select “26H1” builds for new silicon are on a different branch, so they don’t follow the same straightforward path to 26H2. That matters for lifecycle planning if an organization buys hardware that ships with that scoped build—admins may need a different upgrade/reimage approach for standardization.

What IT admins should do now (low-risk, practical)</B]
  • Inventory endpoints by current Windows 11 version/branch so you know which devices are likely eligible for the simple eKB path versus those that aren’t.
  • Validate your update management flow (Windows Update for Business, Intune, ConfigMgr/WSUS) for feature update targeting and rollout rings, since “small” enablement releases can still introduce UI, policy, and feature behavior changes.
  • Pilot on representative devices (especially those with security tooling like EDR, device control, smart card/VPN, and any virtualization or VBS/Memory Integrity settings) before broad deployment.
  • Confirm you’re aligned with the published support lifecycle (24/36 months by edition) so you don’t end up on an approaching end-of-support build.

Bottom line: 26H2 being an enablement package should make deployment easier for the mainstream branch, but it doesn’t eliminate the need for testing, and it makes branch/stock-keeping (especially around 26H1 “scoped” devices) more important.

Sources
 
  • Like
Reactions: Sorrento
Windows 11 26H2 is shaping up to be less about flashy features and more about fixing everyday annoyances users have complained about for years.
Welcome to the first installment of PCMag’s rebooted Windows Guide! I’ve been covering Windows for more than 15 years—and using it since Windows 3.1 first launched 34 years ago—so I'm here as your guide through the latest updates, useful tips, and Microsoft news that actually matters.

I recently spoke with Microsoft executives following Build about where Windows is headed, and that feels like the right place to start. Here's what stands out to me most from the past week in the Windows sphere.

Microsoft has signaled that the Windows 11 26H2 update will arrive later this year as the next major annual release, and I’ve already been testing it through the Insider program. It’s shaping up to be one of Windows 11’s most meaningful updates in years, largely because it reflects long-standing user feedback. For the first time in a while, it really feels like Microsoft is paying closer attention to what PC users want.

One example: Windows will soon let you remove Bing from your Start menu, limiting searches to local apps and files. And you won’t even need to wait for the 26H2 release to do it. Meanwhile, Microsoft has also made a notable change to Edge, adding another twist to the ongoing browser wars, where Brave, Firefox, and Vivaldi continue pushing for users.
Read the full Story:
 
Microsoft has confirmed a significant policy change in the upcoming Windows 11 version 26H2. This update introduces a new default behavior for Windows settings backup, which could affect enterprise security baselines and device resilience strategies.

According to an official announcement published on July 6, 2026, the Windows settings backup policy will change from being disabled by default to enabled by default on eligible devices. This marks a notable shift in how user configurations and application data are preserved during system events.

Windows 11 26H2 Enables Backup Policy
The update, detailed in Microsoft’s resilience baseline documentation, specifies that this “default-on” behavior applies only when administrators have not explicitly configured the policy.

In environments with predefined Group Policy, Microsoft Intune, or Mobile Device Management (MDM) settings, the existing configurations will remain unchanged, preventing unexpected policy drift. This consideration is critical for regulated or high-security environments where strict configuration controls are essential.

From a security and operational perspective, Microsoft is promoting this change as part of a broader initiative to enhance system resilience and recovery capabilities.

By automatically backing up user settings, installed applications, and lists of Microsoft Store apps, this feature aims to streamline the restoration process following device resets, hardware replacements, or operating system upgrades. This aligns with modern enterprise continuity requirements that prioritize rapid recovery and minimal user disruption.

It is important to note that while the backup behavior will now be enabled by default, the restore functionality remains unchanged and continues to be governed by administrative controls.

This distinction ensures that although data will be more readily available for recovery, organizations retain the authority over when and how restoration occurs, thus reducing the risk of unintentional configuration changes or data exposure.

From a cybersecurity standpoint, this shift presents both advantages and considerations. On the positive side, improved backup coverage enhances resilience against incidents, such as ransomware attacks or system corruption, allowing for quicker restoration of user environments.

Conversely, organizations must assess the implications of increased data synchronization, particularly concerning data privacy, cloud storage exposure, and compliance with regional data protection regulations.

Security teams are encouraged to review their current backup and policy configurations ahead of the Windows 11 26H2 rollout. Defining explicit policy settings will be critical for maintaining control over backup behavior, especially in environments that handle sensitive data.

Additionally, administrators should evaluate how this default change interacts with existing identity management, conditional access, and endpoint security frameworks.

Microsoft’s announcement highlights a broader industry trend of embedding resilience features directly into operating system baselines. As enterprises continue to face an evolving threat landscape, such built-in capabilities are becoming standard expectations rather than optional enhancements.
 

You may also like...