Win11 26H2 Preview Officially Launched: Build 26300 Now Rolling Out

On June 19, Microsoft officially released the Win11 26H2 Experimental Preview (Build 26300.8697) on the Windows Insider Blog. This isn't "coming soon"—it's already here. My machine received the update and I've upgraded directly.

This comes after the IT Pro blog confirmed 26H2's existence on June 20, with Microsoft now putting the version into action. Official confirmation + downloadable preview, a two-pronged approach.

At the same time, Microsoft is calling on IT admins: Start testing now, don't wait for the final release.

01. What Exactly Is 26H2?

Let's get straight to the point: Win11 26H2 won't be one of those "big updates" that makes you reinstall your system.

It's delivered via something called an Enablement Package (eKB). Simply put, it's a tiny switch—your system's underlying code has been ready for a while; the enablement package just flips that switch to the "open" position.

How big is the package? About 200KB, less than 500KB. For context, a 480p image is 10 times that size.

How fast does it install? About 2 minutes, one reboot, and you're done. You'll barely notice any interface changes throughout the process.

This approach is the same as last year's 25H2. In fact, starting from 24H2, Microsoft has abandoned the traditional "major feature update" for three consecutive annual releases. All real new features are gradually rolled out through cumulative updates. The annual version number mainly serves to reset the lifecycle countdown.

It's worth noting that 26H2 and 25H2 share the same servicing branch—meaning the underlying platform hasn't changed, and the upgrade experience is just a single reboot.

02. Experimental Channel Is Live, Upgrade Now

This year's pace is different from previous years. Previously, annual updates followed a "confirm → test → release" three-step process, with months in between. But this time, Microsoft released the Experimental preview in the same month as confirming 26H2.

Who can upgrade now?

• Insiders already in the Experimental Channel—just check for updates in Windows Update, and you'll receive Build 26300.8697. After upgrading, Settings > System > About and winver will show the version as 26H2.
• Insiders in the Beta Channel—you can switch directly to Experimental without reinstalling the system. Go to Settings > Windows Update > Windows Insider Program to make the switch.
• Those not yet registered as Insiders—select the Dev Channel during registration (Dev is transitioning to Experimental; once the transition is complete, the channel name will automatically change to Experimental).

Key info for the two versions:

Will the October final release still happen? Yes. The final version will likely still roll out to the Stable Channel this fall. But if you want to try it early, you don't have to wait until October—the Experimental Channel is your early-access pass.

03. Special Note: Not Compatible with 26H1 Users

If you're using 26H1, pay attention.

26H1 is a "special edition" tailored for next-gen ARM chip devices like the Snapdragon X2, based on a different Windows core. The servicing branches for 26H1 and 26H2 are separate. Microsoft specifically emphasized in the blog:

26H1 devices cannot upgrade to 26H2; they will have a dedicated path to a future version.

It's not just the main branch—even the Insider channels are separate. Beta and Experimental channels each have their own independent builds for 26H1 (28020.2308 and 28120.2315). So if you're on 26H1, don't pick the wrong channel.

04. What's New in This Experimental Version?

As the first 26H2 preview, Build 26300.8697 doesn't have many changes, but a few are worth noting:

File Explorer - Improved visual consistency and reliability of the copy dialog in dark mode, including startup experience and expanded progress view.

Taskbar - When using the new "small taskbar" option, the system tray is no longer cut off or pushed off-screen.

Start Menu - After adding or removing apps, the Start menu reflects changes instantly without needing to sign out or restart—a solid quality-of-life improvement.

Settings - Improved reliability of the Apps > Startup page.

Virtualization Fixes - Fixed HYPERVISOR_ERROR (0x20001) and KMODE_EXCEPTION_NOT_HANDLED (0x1E) blue screens that occurred on some devices after installing the latest preview, during system restarts, virtual machine operations, or running certain games.

Most features are still rolled out in batches via Controlled Feature Rollout (CFR) —not everyone will see all new features at once. If you want early access, go to Settings > Windows Update > Windows Insider Program and manually enable features under the Feature flags page.

05. What's Microsoft Urging IT Admins to Prepare For?

The most unique aspect of this announcement is that Microsoft simultaneously released an IT Pro readiness guide (aka.ms/GetReadyFor26H2) and directly urged IT admins to act now:

Switch your environment to the Experimental Channel to verify compatibility

Don't wait for the Beta version—Experimental is available now. Register as an Insider, select Dev (which will transition to Experimental), deploy a verification environment, and run your enterprise software, drivers, and management tools. Start now.

Plan phased rollout rings

Start with a small pilot, then gradually expand. Note: 26H2 and 25H2 share the same servicing branch, so most of your 25H2 compatibility test results can be reused directly, but 26H1 is not compatible.

Evaluate existing deployment tool compatibility

MDT, SCCM, Windows Autopilot—can these tools handle version upgrades in the form of eKB? Microsoft provides a dedicated document explaining the enablement package mechanism (aka.ms/eKB-Explain). Reading it in advance is infinitely better than scrambling later.

Pay special attention to channel structure

This year's Insider channels are more complex than before—Experimental has three lines: 26H2/25H2 version, 26H1 version, and future platform version (Canary 29600 series). IT admins need to ensure test devices are on the correct channel and don't get mixed up.

06. Personal Take: Has Microsoft's "Servicing" Strategy Reached Its End?

For three consecutive years (24H2 → 25H2 → 26H2), version numbers have been pushed via enablement packages, with the underlying code barely changing.

But this year, 26H1 splitting off to run on an independent core sends a signal: Microsoft has quietly opened a branch off the main "servicing" track for annual updates.

26H1 is based on a different Windows core, tailored for next-gen ARM chips. This suggests Microsoft might be walking two paths simultaneously—mainstream x86/existing ARM devices continue on the "servicing" route (eKB + cumulative updates), while new hardware platforms follow an independent version line.

The impact on the Insider ecosystem is the most direct. The Experimental Channel now has to maintain three different build lines simultaneously (26H2 main branch, 26H1 branch, Canary future platform branch), making channel selection much more complicated for users.

Back to 26H2 itself:

For regular users, this is genuinely good news. No pain of major version migration, no worries about software incompatibility, and an upgrade experience with near-zero friction. Features gradually grow in through monthly updates, much like progressive upgrades on phones. And with the Experimental Channel now directly available, early adopters don't have to wait.

But for IT operations, the benefits aren't as significant as they seem. The version number jumps from 24H2 to 26H2, but the underlying platform is still the same servicing branch. Your compatibility testing workload hasn't decreased—it's just changed form, from "one big exam per year" to "monthly quizzes." Add in the variable of the independent 26H1 branch, and this year's testing scope is actually broader.

As for what new features 26H2 will bring down the line? File Explorer with built-in Copilot, search upgraded to "Ask Copilot," a WinUI-rewritten Run dialog, native WebP wallpaper support—they're all on the way. They'll be activated in batches through this year's monthly cumulative updates. The Feature flags page in the Experimental Channel already allows manual activation of some experimental features.

07. Let's Discuss in the Comments

Are you currently on Beta or Experimental in the Insider program? I've already switched and upgraded to 26300. The most immediate impression? It's fast—one reboot, the version number changes, but the interface feels almost identical. In short, that's what eKB is all about.

Have you upgraded yet? Or are you waiting for the final release?