Microsoft has given Experimental Channel Insiders their first official taste of Windows 11 version 26H2 with the rollout of build 26300.8697 on June 19, 2026. Simultaneously, Beta Channel testers received build 26220.8690, which delivers a slate of reliability improvements for File Explorer and other core components. The dual release marks a significant milestone as the 26H2 flag surfaces publicly for the first time, signaling the ramp-up toward the next major Windows 11 feature update.

For weeks, eagle-eyed Insiders have speculated that the 26H2 designation was imminent after references appeared in internal telemetry and SDK headers. Now, with Experimental build 26300.8697, the version string is displayed prominently in winver and system settings, confirming that 26H2 has graduated from reference to reality. The Experimental Channel, known for testing cutting-edge features months ahead of wider deployment, typically serves as the first proving ground for new version forks. This release aligns with Microsoft’s established cadence of a single annual feature update, suggesting that 26H2 is on track for a second-half 2026 public launch.

What’s New in Build 26300.8697 (Experimental)

Beyond the version branding, Experimental build 26300.8697 does not introduce sweeping new features that are immediately visible. Instead, it lays foundational changes under the hood. According to the official changelog, the build activates several dormant flags related to the upcoming Windows Copilot Runtime 2.0, enhanced NPU scheduling for on-device AI tasks, and a redesigned taskbar animation system that had been partially leaked earlier this year. Most of these are locked behind feature gates, meaning only a subset of Insiders will see them.

One notable enablement is a new “Smart Snap” grouping feature that automatically suggests window layouts based on frequently used app combos. Early testers report that the implementation feels smoother than the existing Snap Assist, with haptic feedback support on precision touchpads. However, the feature is currently limited to devices with haptic-capable hardware.

The build also updates the Windows Kernel with a new memory compression algorithm codenamed “Zephyr.” Microsoft’s release notes claim up to 18% better memory utilization on systems with 8 GB RAM or less, which could significantly improve multitasking on budget notebooks and older hardware. That alone has sparked excitement among Windows enthusiasts who have long criticized the operating system’s growing RAM footprint.

Known Issues in 26300.8697

As expected in an Experimental branch, build 26300.8697 ships with its share of rough edges. Microsoft’s list of known issues includes:

  • File Explorer may crash when using the new “tab groups” feature with more than 15 tabs open.
  • Quick Settings toggles can become unresponsive after waking from modern standby.
  • Some Arm64 devices experience a black screen for up to 90 seconds after login if Windows Hello is enabled.
  • The Print Screen key occasionally fails to capture the full desktop when Dynamic Refresh Rate is active.

Insiders are advised to back up their data before installing, as the Experimental Channel carries heightened risk of instability. Despite the bugs, reactions on Reddit and the Insider Feedback Hub lean positive, with many praising the memory improvements and the smoother taskbar animations even in this early state.

Beta Build 26220.8690: Reliability Takes Center Stage

For Beta Channel Insiders, build 26220.8690 is a more cautious affair. The primary focus is reliability, particularly for File Explorer, which has been a source of constant complaints since the Windows 11 launch. Microsoft’s engineers have reworked the Explorer’s address bar logic, eliminating a race condition that could cause the bar to reset unexpectedly when navigating between network shares. Another long‑standing bug where the context menu would sometimes render with blank icons after right‑clicking a OneDrive file has been squashed.

Perhaps the most welcome fix addresses a memory leak in the Input Method Editor (IME) that affected users of Japanese, Chinese, and Korean language packs. The leak could gradually chew through hundreds of megabytes over a single session, leading to sluggish performance. With the patch, the IME process releases resources correctly, restoring snappy text input even after hours of use.

Beta testers also gain a backported version of the new battery usage insights page originally developed for the 26H2 branch. This dashboard now breaks down energy consumption by app, network activity, and display brightness, offering a more granular view than the current Settings page. It still carries a “beta” badge, but Microsoft is soliciting feedback to refine the UI before it reaches general availability.

Additional Fixes and Enhancements

  • Windows Update: Resolved an issue where the “Check for updates” button would remain disabled after a failed cumulative update installation.
  • Task Manager: Fixed a scenario where the process list would flicker and reorder itself when sorted by power usage.
  • Networking: Addressed a DHCP client bug that could cause a “No Internet, secured” status on Wi‑Fi networks after resuming from hibernation.
  • Accessibility: Narrator now correctly announces the state of toggle switches in the Wi‑Fi flyout, a small but important fix for visually impaired users.

Community Pulse: Early Adopters Weigh In

Though the Experimental build’s limited availability means only a handful of dedicated Insiders have tested it, early feedback is coalescing around a few themes. On the Windows Insider subreddit, user “TechyTom85” wrote, “Haven’t seen 26H2 in person before. The memory compression actually makes my old ThinkPad usable again. But Explorer crashes are real — lost three tabs twice this morning.” Another user, “PixelPusher_, said, “Smart Snap is a game changer for my workflow, but it’s buggy when undocking my laptop. I trust MS will polish it.”

Beta Channel testers are notably more satisfied. The File Explorer fixes have drawn praise from users like “SysAdminInTraining,” who commented, “Finally no more address bar jumping! That alone is worth the update.” The battery dashboard has also sparked discussion, with several users hoping the company will add historical graphs in a future revision.

Not all feedback is glowing. Some Insiders express frustration that new features remain locked behind feature gates even in the Experimental Channel. “Why give us the 26H2 label if we can’t test half the cool stuff?” asked a user on the official Feedback Hub. Microsoft’s engineering team has responded that gradual enablement is necessary to isolate regressions before a wider rollout, but the policy continues to rankle the most enthusiastic testers.

What the 26H2 Flag Means for Windows 11

The arrival of a 26H2 build in the Experimental Channel signals that the feature set for the next update is largely frozen and the focus is shifting to stabilization. Historically, Microsoft uses the second half of the year to deliver platform improvements, while reserving major user-facing features for the first-half update (if one is released). Given that 24H2 brought a modest refresh, expectations are higher for 26H2.

Sources familiar with the development roadmap say that 26H2 will include deeper integration of AI across the shell, including a context-sensitive Copilot panel that can suggest actions based on selected text or files. The memory compression and scheduler changes in build 26300.8697 are foundational for that AI push, as they aim to keep the system responsive even when running multiple machine learning models on device.

Another significant aspect is the apparent re‑architecture of the taskbar. Code references in the build point to a unified tray area that can host both traditional notification icons and modern widgets, potentially reducing the clutter of two separate flyouts. If this materializes, it would address a long‑standing design criticism that the Windows 11 taskbar feels disjointed.

The Path to General Availability

Microsoft has not publicly committed to a release date for 26H2. However, past release patterns suggest a September or October 2026 rollout, following a traditional Insider ramp through the Dev and Beta Channels over the summer. The Experimental build gives the first glimpse of the version string, but feature complete builds usually arrive in the Dev Channel within 4–6 weeks. From there, a Release Preview candidate typically drops a month before public availability.

For enterprise customers, the 26H2 branding is also a reminder that the 24H2 support lifecycle will eventually end. Organizations still running 24H2 will have 18 months after the initial release of 26H2 to plan their upgrades before that version reaches end of service. The new memory management improvements could ease the transition for older hardware fleets, making 26H2 a more attractive target than previous updates.

The Bigger Picture: Windows Insiders and the Road Ahead

These two builds underscore the growing divergence between the Experimental and Beta Channels. Experimental insiders are expected to tolerate significant instability in exchange for early access to foundational code changes, while Beta testers receive a more polished experience that still catches regressions before broad deployment. This tiered approach has helped Microsoft catch critical bugs — like the IME memory leak — before they affect hundreds of millions of users.

Looking forward, the 26H2 cycle will be a test of Microsoft’s ability to deliver meaningful innovation without repeating the pitfalls of past updates. Users are weary of half‑baked features that ship and then get pulled, as happened with certain widgets and the initial Copilot integration. The steady cadence of reliability fixes in the Beta build suggests the company is listening to feedback, but the true measure will be the quality of the final release.

For now, Insiders have plenty to dig into. Experimental build 26300.8697 offers a tantalizing preview of the 26H2 foundation, while Beta build 26220.8690 makes the current branch more solid. Whether you choose to live on the bleeding edge or prefer a more stable ride, both builds are available today through Windows Update for enrolled devices.

To join the Experimental Channel, Insiders must be running a supported Windows 11 Insiders build and opt in through Settings > Windows Update > Windows Insider Program. Be warned: once you switch to the Experimental Channel, a clean installation is required to return to the Dev or Beta channels. As always, back up your important files before taking the plunge.