A hidden feature in a Windows 11 Insider Experimental build lets you open folders in new File Explorer tabs with a middle-click—and it is raising quiet alarms among IT teams before the feature is even officially acknowledged.

Found in build 26300.8687, which shipped to testers on June 12, 2026, the change extends tab activation to two high-visibility surfaces that most advanced users touch hundreds of times a day: the File Explorer Address Bar and the Home page. Right now, middle-clicking a folder in the main file list already opens it in a new tab; this update brings that same convenience to the breadcrumb trail and the frequently-accessed Home screen.

But the build has not appeared in any publicly-facing Microsoft release notes for June 12. The company’s published record for that date details Release Preview build 28000.2333, which focuses on Magnifier, Task Manager, and shell reliability—no mention of Explorer tabs. That silence is significant: it means the feature exists only as an experimental, controlled rollout inside a dedicated Insider channel, with no promise of reaching general availability.

What actually changed

Build 26300.8687 is an enablement package that activates the feature as part of Windows 11 version 25H2. Once enabled, users can middle-click any folder name inside the Address Bar—at any level of the breadcrumb path—to open that location in a new tab. The same action works on folder entries scattered across the Home page, including pinned locations, recent files, and favorites.

This isn’t a trivial UI tweak. The Address Bar is more than a path string; it is where cloud-storage providers, virtual folders, and namespace shells can insert themselves. A middle-click on a OneDrive or SharePoint breadcrumb segment, for example, must open a new tab that correctly displays the cloud-backed content and its sync state, while retaining the original tab’s context.

Home is arguably more complex. It aggregates links from local drives, libraries, pinned network shares, and third-party sync clients. A middle-click there may try to open a disconnected network folder, trigger an authentication challenge, or launch a provider-managed view that was never designed to be duplicated in a separate tab.

Because the feature is under a Controlled Feature Rollout, not every machine that installs the build will see it immediately—or at all. Your specific hardware, geographic region, or Microsoft account profile might keep it hidden even after the update.

What this means, depending on who you are

For everyday Windows users who depend on File Explorer for daily file management: this is a genuine time-saver. Navigating a deep folder hierarchy currently requires opening a new tab, then drilling down from scratch. With middle-click on the Address Bar, you can fork your workflow at any level. Found a folder you want to keep handy while continuing your main task? Middle-click it. The learning curve is flat, and the action feels natural.

But unpredictability is the trade-off. If a middle-click on a Home folder opens a blank tab, crashes Explorer, or spawns a duplicate authentication window, the convenience evaporates. Users who run sync clients like Dropbox or iCloud alongside OneDrive may see inconsistent behavior because those providers aren’t all tested against this new code path.

For power users who juggle multiple Explorer windows and tabs, the Address Bar shortcut is a small but meaningful upgrade. It reduces the friction of keeping several locations in view while comparing files, moving data, or monitoring cloud sync status. Combined with existing Ctrl+T and Ctrl+W shortcuts, it makes File Explorer behave more like a modern web browser.

However, power users are most likely to have installed shell extensions—archive managers, context-menu tools, advanced search utilities—that hook into Explorer. The middle-click action travels through a different code path than a standard double-click or Enter press. An extension that works perfectly with a single tab might introduce lag, flicker, or incorrect rendering when a new tab springs up from an unexpected trigger. If you rely on third-party Explorer enhancements, test this feature with your extension set before adopting it as muscle memory.

For IT administrators and managed organizations, the implications are more serious. The WindowsForum analysis of this build outlines a pilot-testing approach that treats the feature not as a saved click, but as a potential source of hidden incompatibilities. The dangers are real:

  • Navigation from Home or the Address Bar often reaches cloud-backed, virtual, or redirected folders that are governed by DLP, access control, or auditing software. A new tab must fire those same policy checks; if it doesn’t, data can leak or compliance reporting can be incomplete.
  • Namespace providers—such as the virtual folders used by enterprise document management systems—may lose context when opened in a tab. The tab might show a blank screen, revert to a local view, or drop the custom icon overlay that tells users they’re inside a managed space.
  • Assistive technology workflows can break. Screen readers must correctly announce the new tab’s content, keyboard focus must move to it logically, and high-contrast or scaling settings must still render the tab bar and its controls legibly.
  • If a DLP agent or endpoint security product does not inspect the tab’s initiation as thoroughly as a regular click, a user could bypass a block just by middle-clicking.

A sensible IT policy should treat this experimental feature as a “conditional go” only after a structured pilot. That means maintaining a control device on the same build without the feature enabled, testing against local, network, cloud, and virtual folder types while monitoring for crashes, authentication prompts, and policy violations. The fact that Microsoft is simultaneously shipping shell-extension reliability improvements in the same June 12 Release Preview build—accelerating app launch and core shell experiences—underscores that Explorer’s extensibility layer remains fragile.

How we got here: a slow, careful tab expansion

Microsoft added tabs to File Explorer in Windows 11 version 22H2, but the road since then has been cautious. The first iteration merely allowed you to accumulate tabs manually using a “+” button. Middle-click on a folder in the file pane arrived later, building on the browser paradigm. Now, for the first time, that paradigm is bleeding into the navigation surfaces that surround the file list.

The Address Bar and Home page are logical next steps. Competitors like macOS Finder have long offered tabbed browsing with spring-loaded folder actions, but Microsoft has been deliberate—some would say slow—because Explorer’s architecture is uniquely tangled. It pulls content from the local shell, cloud providers, Quick access, and legacy Control Panel namespaces, all through a plugin model that dates back to Windows 95. Every new entry point for tab creation is a new vector for a misbehaving extension to cause trouble.

The fact that this feature landed in an “Experimental” Insider branch rather than the main Dev or Beta channels tells you Microsoft is still gauging stability. The build is labeled Experimental because it contains changes that might never ship; Microsoft’s own Insider documentation warns that such features “may change, be removed, or never ship outside Insider testing.”

What to do now

If you’re an Insider already on the Experimental channel and the feature has rolled out to your machine, you have a chance to shape its future. Use it in your real workflows and report back via the Feedback Hub. Your bug reports about blank tabs, crashes, or accessibility gaps are the most effective lever to get this polished before a wider release.

For everyone else, there is no rush. These are the concrete steps, depending on your situation:

  1. Insiders on Experimental build 26300.8687: Confirm the feature is actually present—don’t assume the build number alone means you have it. Test middle-click on at least three types of folders: a plain local folder, a folder inside OneDrive or another cloud-sync client, and a folder that appears inside a namespace extension if you use one (like a file archive opened as a folder). Watch for duplicate tabs, authentication loops, or Explorer restarts.
  2. Insiders on other channels: The feature isn’t offered to you yet. Keep your system updated, and watch for announcement posts on the Windows Insider Blog. If you rely on Explorer extensions for daily work, consider setting up a virtual machine on the Experimental channel so you can test without risking your main environment.
  3. IT administrators: Do not greenlight this for production. The build’s Experimental status and Controlled Rollout nature make it unreliable to deploy. Instead, build a reusable compatibility test ring around Explorer—inventory the extensions, cloud providers, and namespace providers your organization uses, and plan to quickly test future Insider builds once the feature appears in a more stable channel (Beta or Release Preview). That preparation will pay off when the feature eventually reaches general availability.
  4. Accessibility and security teams: Prioritize the accessibility pass. A screen reader must announce the new tab’s location and content accurately; keyboard focus must stay predictable. DLP and endpoint security software must treat the middle-click path identically to a standard double-click. Any deviation is a regression that could affect compliance.

The core rule: the new tab must behave exactly like opening the same folder through a traditional route. If it doesn’t, that’s a bug, not an acceptable quirk.

What to watch next

Microsoft has not acknowledged this feature publicly, so the next milestone is not a release date but a signal: a mention in a future Insider build’s release notes, a blog post from the Windows team, or the feature’s migration from Experimental to Dev or Beta. That migration would indicate the company believes it’s stable enough for a wider audience.

In the interim, keep an eye on File Explorer’s reliability patches in regular cumulative updates—the June 12 Release Preview notes show Microsoft is actively hardening the shell. That work will directly benefit whatever form middle-click tabs eventually take. And if you’re an enthusiast who loves to explore, build 26300.8687 offers an early glimpse of an Explorer that behaves a little more like the web browser you already use every day.