The update naming convention for Windows 11 has followed a consistent pattern over the past few years. With versions like 22H2, 23H2, 24H2, and 25H2 released under Microsoft’s strategy of issuing a major update annually—most often in the latter half of the year—news of Windows 11 26H1 has sparked curiosity. The H1 designations previously signified something distinct during the Windows 10 era.
Microsoft has confirmed that Windows 11 26H1 is a legitimate release; however, it is important to note that it is not a feature update for existing PCs. Rather, this version is specifically intended for new ARM devices set to launch in 2026, primarily the Snapdragon X2 series, and potentially the forthcoming NVIDIA N1X. Therefore, if your system operates on Intel or AMD hardware, you won’t see 26H1 in the Windows Update section.

This indicates that 26H1 will not replace the existing versions like 24H2 and 25H2, nor will it serve as the next level in the upgrade cycle. Microsoft remains committed to its annual update approach for current PCs, with the next anticipated update, Windows 11 26H2, expected in late 2026.
In essence, 26H1 resembles the custom builds previously preloaded by OEMs for new hardware generations, but now carries an official version marker from Microsoft to support emerging silicon technologies.
Key Features of Windows 11 26H1: An Inside Look
So, what distinguishes Windows 11 26H1 if it does not introduce visible changes? Windows Latest conducted tests with 26H1 on a virtual machine to uncover the differences, leading to an exploration of the core platform component that Microsoft refers to as the platform core.
This release operates on a distinct core designed for ARM silicon, initiating with Qualcomm’s Snapdragon X2 series, which is currently the only officially supported processor. Microsoft has labeled 26H1 as a “hardware-optimized release, ” developed in collaboration with silicon manufacturers.

“26H1 is based on a different Windows core than versions 24H2, 25H2, and the upcoming feature update.” – Microsoft
Understanding the Windows Platform Core
The “platform core”encompasses the critical underlying code that supports the operation of Windows. This includes components such as the kernel, driver model, scheduling mechanisms, hardware abstraction layers, and security frameworks. Historically, these platform bases had codenames—Cobalt (21H2), Nickel (23H2), and Germanium (24H2 and 25H2). There’s speculation that the new platform for 26H1 may bear the code name Bromine.
Each platform release not only replaces the existing foundation but also significantly enhances it. Enablement packages, such as 23H2 and 25H2, unlock features that are already embedded within the base system.
Rationale Behind the New Platform for 26H1
Versions 24H2 and 25H2 are based on the Germanium platform. In contrast, the upcoming 26H2 update for existing PCs will utilize the same base via the enablement package approach.
Windows 11 26H1 was developed using a newer internal branch tailored for next-generation ARM processors, including Snapdragon X2 and other anticipated architectures. These new processors employ heterogeneous architectures, necessitating revisions in scheduling logic, power management systems, and the way Windows optimizes performance alongside battery life.
Projected Differences for ARM SoCs in 26H1

- Heterogeneous Thread Scheduler: The new core is likely optimized for “Big. LITTLE” architectures (such as Snapdragon X2), resulting in more efficient task allocation between performance and efficiency cores.
- Deep NPU Integration: This core may enable improved routing of AI tasks through the system’s NPU layer, enhancing local AI operations with reduced latency and power consumption.
- Power & Thermal Governors: The core could incorporate new ACPI (Advanced Configuration and Power Interface) states, providing the OS with finer control over energy consumption, ultimately contributing to Microsoft’s claims of “exceptional battery life.”
While these insights are not yet comprehensively documented, it is essential to note that Microsoft cannot provide an in-place upgrade pathway from 25H2 to 26H1 due to the differing hardware requirements.
A Temporary Divergence in Development Tracks
Currently, Windows 11 development operates on two parallel paths. The Germanium line serves existing Intel and AMD systems and proceeds towards 26H2, while the 26H1 will be maintained for new ARM architectures until March 2028. Microsoft has indicated plans for both paths to merge again around the timeframe of Windows 27H2.
Experience with Windows 11 26H1
While Windows 11 26H1 is unavailable for standard PCs, users can download the ISO and test it on virtual machines. However, those who do so may find it largely similar to 25H2, with no additional features introduced as of late.
Noteworthy Improvements in Windows 11 26H1
The first observable change upon booting into Windows 11 26H1 is the OS Build number, which jumps to 28020.1611, marking the differentiation from the Germanium-based builds of 24H2 and 25H2.

Natural Language Search Enhancement: One notable feature is the robust availability of semantic, natural-language search within the Settings menu, which contrasts with the gradual implementation seen in previous versions.
The search functionality operates more intuitively; for example, typing “my mouse pointer is too small” yields direct access to the “Mouse pointer size” adjustment slider in the search results without additional navigation.

Additionally, a new feature enabling control over search indexing of online files in OneDrive under Privacy & Security > Search allows users to choose whether to include content from cloud-based storage.

Increased FAT32 Format Limit: Windows 11 26H1 finally removes the longstanding FAT32 formatting limitation imposed by previous versions, now allowing for partitions up to 2 TB without error. This enhancement greatly simplifies the process of formatting larger SD cards and drives without needing third-party software.

User Interface Enhancements: The update brings additional polish to aspects of the legacy UI that were previously neglected:
- Modernized Storage Interface: In Settings > System > Storage > Disks & volumes, the buttons for “Create a virtual hard disk (VHD)” and “Attach VHD” have been improved with better padding. Likewise, the “Create volume” button has been updated to match Windows 11’s design language, featuring rounded corners and an animated chevron.
-

Source: Phantomofearth via YouTube - Setup Dialog Refinements: The Windows 11 Setup experience includes added safeguards like confirmation dialogs when clicking “Delete Partition” or “Format Partition.” This enhancement serves as a critical addition that was not present in 24H2.
-

Source: Phantomofearth via YouTube
Deprecations and New Safeguards
Alongside these improvements, Windows 11 26H1 represents a shift in certain features:
- Removal of. NET Framework 3.5: The legacy. NET Framework 3.5 is no longer available as an optional feature. Users are encouraged to transition to modern versions, though a standalone installer remains accessible for those who require it.
-

.NET Framework 3.5 is unavailable in Windows 11 26H1 - New Safeguard on Sysprep: Users are now blocked from running the System Preparation Tool (Sysprep) while in Safe Mode. Attempting to do so leads to an error message, ensuring that the tool is only used appropriately in Normal or Audit modes.
Windows 11 26H1 is not an update to pursue unless you are considering a new device powered by Snapdragon X2 silicon. This release is fundamentally a hardware-optimized version aimed at leveraging the capabilities of next-gen ARM platforms, while existing PCs will continue to receive the established monthly updates and the forthcoming Windows 11 26H2 feature update later in 2026.
In the short term, users and businesses need not be concerned, as their current Windows 11 installations will continue to receive full support, including security patches, feature updates, and lifecycle commitments.
The divergence between 26H1 and the mainstream branch is expected to be temporary, as Microsoft intends to integrate both paths in future release cycles.
Special thanks to Windows enthusiast Phantomofearth for contributing screenshots.
Leave a Reply