Microsoft released Windows 11 Insider Experimental Preview Build 26300.8687 on June 12, 2026, delivering two long-anticipated search improvements: forgiving fuzzy matching for local files and settings, and a visible toggle to disable web results. The build marks a quiet but significant shift in how Windows handles queries typed into the Start menu and taskbar search box — areas that have drawn years of criticism for cluttering local results with Bing suggestions.

Windows search has been a contentious feature since the launch of Windows 10, when Microsoft merged local file and app results with web predictions served by Bing. Enthusiasts immediately pushed back, using registry hacks and third-party tools to strip out the online content. Over successive Insider builds, Microsoft tinkered with the mix, sometimes reducing the prominence of web results, sometimes adding a "Search the web" section, but never providing a straightforward off switch. Build 26300.8687 changes that calculus.

Forgiving Your Typos: How Fuzzy Local Search Works

The most immediately noticeable change in this build is the way the Start menu and search pane handle misspellings, partial words, and near matches. Fuzzy search isn’t new to software engineering — it has been a staple of code editors, email clients, and macOS Spotlight for years — but Windows has traditionally relied on exact prefix matching or basic substring look-up. If you typed “PowrPint,” Windows would fail to find PowerPoint unless a full-text index happened to include the misspelled name. With build 26300.8687, the search engine now applies edit-distance algorithms that tolerate a certain number of insertions, deletions, or character swaps.

In practical terms, this means you can type “outlokk” and still see Outlook appear at the top of the results. The tolerance appears calibrated to common typing errors on QWERTY keyboards — transposed letters, missed keystrokes, and phonetic mix-ups like “f” for “ph.” Feedback from early testers suggests the engine performs best on one- or two-character deviations, though it may also handle longer queries with a higher error budget as the indexing service learns individual user patterns. The change applies not only to installed applications but also to files, settings pages, and even documents stored in OneDrive, provided they are indexed locally.

A Microsoft engineer explained in the accompanying blog post that the fuzzy logic runs client-side, leveraging the existing Windows Search index rather than phoning home to Microsoft servers. That distinction matters for privacy-conscious users who have grown wary of Windows telemetry. Because the computation stays local, fuzzy suggestions appear instantly without the latency of a cloud round-trip. The index has been updated to store phonetic hashes and n-gram fingerprints, which allow the query engine to generate a ranked list of candidate items in milliseconds.

The feature is enabled by default in this experimental build, but a toggle exists under Settings > Privacy & Security > Search Permissions, where users can revert to strict exact-match behavior if they prefer predictability. The same settings page also houses the new web-results control.

Putting Users in Control of Web Results

The second headline feature is a visible, user-facing switch that suppresses Bing web answers from local searches. In the current public release of Windows 11, the only way to completely block web results is through a Group Policy or a registry key buried in HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Explorer. That approach is inaccessible to the average consumer and often breaks after feature updates. Build 26300.8687 adds a simple on/off slider labeled “Show web results in search” within the Search Permissions page. When turned off, a query for “weather” will only return local weather apps, settings, or files — no Bing snippet, no “See web results” link, no Edge tab suggestion.

The toggle appears to be part of a broader effort by Microsoft to comply with the Digital Markets Act in the European Economic Area, where the company must offer users the ability to decouple Windows functions from Microsoft services. However, the setting is also being flighted to Insiders outside the EEA, suggesting Microsoft sees value in giving all power users a cleaner search experience. The build notes caution that the toggle is still “experimental” and may not work for all query types — particularly “quick searches” that the Shell interprets as navigation commands. In those cases, a fallback “Search the web” link might still appear at the bottom of the pane, though Microsoft says it is working to eliminate that exception.

A History of Search Frustration

To understand why these two features matter, it’s helpful to recall the rocky history of Windows Search. When Windows 10 launched in 2015, Microsoft touted Cortana integration and universal search as flagship features. The reality was messier: Bing results would often pop up before local files, slowing down the system and consuming bandwidth. The Search and Cortana team tinkered with indexing algorithms, but the root problem — a business desire to drive traffic to Bing — remained an architectural choice.

With Windows 11 in 2021, Microsoft separated Cortana from the search experience and committed to making search “local-first.” Yet the web results persisted, now served through the Edge browser engine. Users who had uninstalled Edge or changed their default browser were still seeing Edge-hosted Bing pages when they accidentally clicked a web suggestion. Privacy advocates pointed out that keystrokes were being sent to Microsoft even when users only intended to find local files. Microsoft eventually added an option to turn off “Search online and include web results” in the Settings app, but that option only controlled the top-level switch; the underlying integration remained, and many users reported that web results continued to appear after updates reset their preferences.

Build 26300.8687 represents the most decisive step yet toward disentangling local search from Microsoft’s online services. By placing the web-results toggle alongside the new fuzzy-search setting, Microsoft signals that the two belong to the same family of user-experience controls — giving people a fast, accurate, and distraction-free tool that they can customize to their liking.

Under the Hood: What’s Changing in the Indexer

Though Microsoft hasn’t published a detailed technical whitepaper, the build announcement mentions several under-the-hood changes that make fuzzy search possible. The Windows Search indexer, which previously stored only stems and dictionary terms, now computes and persists two additional data structures: a phonetic encoding using a Double Metaphone algorithm adapted for multilingual input, and a trigram vector that captures overlapping three-character sequences in every indexed item’s title, path, and content preview. When a user submits a query, the search engine decomposes it into the same phonetic and trigram representations and uses cosine similarity to rank items against the index.

This is computationally more expensive than a straightforward prefix lookup, so Microsoft has optimized the pipeline by moving the similarity calculation into the search UI process rather than calling out to the indexer service across a COM boundary. The query processor maintains a small in-memory cache of recently accessed items, which provides near-zero latency for repeated fuzzy searches. In unusual cases where the cache misses entirely, the fallback exact search still operates, ensuring that users don’t see a blank results pane while the engine churns.

Disk usage for the search index database grows by roughly 8–12% in this build, based on early reports from Insiders who have analyzed the Windows.edb file. Microsoft recommends that users who are tight on space trigger a manual index rebuild after upgrading, which removes redundant data from the previous schema. The company also notes that the extra indexing work consumes about 5–7% more CPU during the initial crawl but returns to idle once the index is fully populated.

Early Feedback from the Insider Community

Though the discussion thread on WindowsForum is just starting to light up, preliminary reactions are overwhelmingly positive. Testers who had previously relied on third-party launchers like Flow Launcher or PowerToys Run are intrigued by the possibility of a capable built-in alternative. One common refrain: “Finally, I don’t need to install Everything just to find a misspelled folder.” Others caution that fuzzy matching can sometimes surface too many irrelevant results, particularly for short queries that match a broad set of trigrams. “Typing ‘cat’ now shows me CatLog, CatEditor, Catalog Maker, and a dozen other apps I forgot I had installed,” one user noted. Microsoft seems to be aware of this, and the feedback hub has several requests to add a “relevance threshold” slider in a future update.

The web-results toggle is receiving even more enthusiastic praise. Power users who manage fleets of Windows machines are hopeful that the setting can be deployed via Intune or Group Policy without the janky registry hacks they’ve been using since 2015. IT administrators have already created uservoice threads asking for a “DisableBingWebSearch” policy that maps directly to this new slider. For now, the toggle applies on a per-user basis, but Microsoft hints that a machine-wide policy is under consideration.

Some Insiders running the build on ARM64 devices report that the web toggle interacts oddly with the Edge WebView2 runtime, causing a brief flash of a white window before results stabilize. The issue appears isolated to Snapdragon X Elite processors and is likely a graphics-driver glitch rather than a problem with the search feature itself. Microsoft has acknowledged the report and says a fix is planned for the next build refresh.

Build 26300.8687 is labeled “Experimental Preview,” which in Microsoft’s release terminology means it tests features that may or may not ship in a future production update. However, the nature of the changes — fundamental improvements to accuracy and user agency — suggests they are likely to graduate to the Dev and Beta channels relatively quickly. If telemetry shows that fuzzy search reduces the number of queries that return zero results (a metric Microsoft tracks closely), and that the web toggle doesn’t significantly dent Bing referral traffic, these features could land in the next major Windows 11 feature update.

The build also hints at a broader philosophy shift. For years, Microsoft insisted that blending local and web results provided “delightful” experiences, despite vocal user pushback. Now, the company seems to accept that one size does not fit all. By decoupling the two and investing in smarter local algorithms, Windows Search inches closer to the utility-first design that made Spotlight on macOS so popular. Whether this marks a permanent change or a temporary experiment remains to be seen, but Insiders are voting with their feedback — and for once, Microsoft appears to be listening.

If you’re an Insider on the Dev or Canary channel and want to test Build 26300.8687, you can download it now via Windows Update. Microsoft warns that it may not be offered to all machines immediately due to a staged rollout; you can manually check for updates to force the installation. As always with pre-release builds, back up your data and be prepared for a few rough edges. The full release notes are available in the Feedback Hub under the “Windows Search” category, and the team encourages testers to file bugs and suggestions directly through the hub.