Microsoft issued Windows 11 Insider Preview Build 26300.8687 to the Dev Channel on June 12, 2026, and shipped a single, transformative feature: typo-tolerant app search results. The operating system can finally surface the correct application even when you fat-finger a name, skip letters, or transpose characters. If you have ever typed “Chome” instead of “Chrome,” “Outlok” for “Outlook,” or “pint” when you meant “Paint,” this experimental update aims to banish the empty result list that has plagued users for decades.
The feature, dubbed “Approximate App Matching,” works inside the Start menu, the taskbar search box, and the full search home experience. Microsoft says it relies on fuzzy string comparison algorithms that run entirely on-device, preserving privacy and working without an internet connection. In internal tests, the company found that roughly one in five app searches contains a typo—a rate that spikes on touch and virtual keyboards. With the new engine, Windows quietly computes the distance between your input and the names of every installed application, then surfaces the closest matches above a configurable confidence threshold.
How Approximate Matching Works
At its core, the matching engine uses a tuned implementation of the Damerau-Levenshtein algorithm—a method that counts the number of single-character edits required to turn one string into another. Edits include insertions, deletions, substitutions, and transpositions of adjacent characters. When you initiate a search, Windows compares your query against a pre-built index of app names, shortcuts, and alternative titles (like “MS Word” for “Microsoft Word”). If the edit distance is small enough—typically one or two operations for short names, and up to three for longer ones—the app appears in the results with a slightly lower ranking so that exact matches still take priority.
Microsoft has layered a custom dictionary on top of the algorithm. This dictionary includes common misspellings, phonetic variations, and localized aliases. For example, “Edg” correctly resolves to “Microsoft Edge,” “PowerPont” finds “PowerPoint,” and “VisualCode” brings up “Visual Studio Code.” The system even handles omitted spaces and punctuation: “StickyNotes” matches “Sticky Notes” and “diskmgmt” launches Disk Management just as “diskmgmt.msc” does. Phonetic matching is also language-aware; in English, “calender” points to Calendar, while similar mechanisms work in Spanish, German, Japanese, and other supported interface languages.
Crucially, all processing happens locally. The search indexer already knows the names of every installed app from the Start menu layout, and the fuzzy logic simply adds a lightweight computation on top of that. No data is sent to Microsoft, and the feature respects the existing search privacy settings.
Real-World Testing and Early Reactions
The Windows Insider community has flooded feedback channels with praise and minor gripes. On the Feedback Hub and social networks like X, testers describe the feature as “long overdue” and “a total game‑changer for productivity.” One user wrote, “I can never remember if it’s ‘Snipping Tool’ or ‘Snip & Sketch’ or just ‘SnippingTool.’ Now I just type ‘snip’ and it shows up instantly.” Another tester, who frequently mistypes “PowerShell” as “Powershel,” confirmed that the misspelling now yields the correct app without the need for a second attempt.
Accessibility advocates have also cheered the update. Users with motor disabilities find that reducing the need for exact typing makes the Start menu far more usable. Touch-screen users on tablets and 2-in-1s—where virtual keyboards naturally produce more errors—stand to benefit the most.
Not everyone is completely satisfied, however. Some Dev Channel participants have noticed that very short queries, such as “ms,” can return too many results. For instance, “ms” might show Microsoft Store, MS Paint, MS Teams, and MS Word simultaneously, making it harder to select the intended app with just another tap or click. Microsoft is aware of the issue and says it may introduce a “did you mean?” prompt or intelligent ranking adjustments in future builds.
Performance impact appears minimal. On mid-range hardware, the fuzzy computation adds less than 50 milliseconds to a typical search. Older machines might see a slight increase in CPU usage during the first index rebuild after the update, but Microsoft recommends waiting for the indexer to settle before judging performance.
A Glimpse at the Build’s Other Changes
Build 26300.8687 is relatively lean outside of the search improvement. The official release notes mention three notable bug fixes:
- An issue where the taskbar could flash or show incorrect accent colors when switching between virtual desktops has been resolved.
- A memory leak in File Explorer that occurred when browsing folders with a large number of media files (particularly .mp4 and .mkv formats) has been plugged.
- A reliability problem with the Widgets board that caused it to fail loading after waking from sleep is fixed.
The build carries KB number KB5035214 and is offered both as a cumulative update and a full ISO download. It remains part of the 24H2 development semester, but since Dev Channel features can be delayed, reworked, or cancelled, there is no guarantee when typed-tolerant search will hit the Beta or stable channels.
How to Enable or Disable the Feature
Insiders who install the update will have approximate matching enabled by default. A new toggle appears under Settings > Privacy & security > Search permissions, labelled “Use approximate matching when searching for apps.” Flipping it off reverts to the traditional exact-match-only behaviour. Microsoft uses this experimental toggle to collect usage telemetry that will inform the final implementation.
You can test the feature by intentionally mangling app names. Try “wordpad” for WordPad, “movie maker” for the legacy Movie Maker, or “calc” for Calculator. Even wildly wrong queries such as “netflex” (which finds Netflix) or “photso” (for Photos) should work. If an app you expect isn’t found, use the Feedback Hub to report the misspelling; Microsoft engineers use those reports to expand the fuzzy dictionary.
The Long Road to Better Windows Search
Windows Search has a checkered past. Windows 8’s search was slow and divided by category. Windows 10 improved speed but still demanded precise typing—a mismatch for a modern operating system. Third-party utilities like Everything, Listary, and PowerToys Run rushed in to fill the fuzzy-search gap. Even Microsoft’s own PowerToys Run module offers excellent fuzzy matching for apps, files, and system commands, but many users—especially in enterprise—are unable or unwilling to install unsanctioned tools. The native feature closes that hole.
In 2021, Microsoft upgraded the search indexer to include more metadata, but the matching logic remained rigid. The 2022 “Search Highlights” feature added fresh content to the search pane, but the fundamental input problem persisted. Approximate app matching marks the first deep change to the matching engine itself. Insiders have spotted references to a broader “ApproximateEverything” flag in internal builds, hinting that Microsoft may eventually extend fuzzy matching to files, settings, and web results.
Comparisons with Other Platforms
Fuzzy search for apps is standard elsewhere:
| Platform | Native Fuzzy Search | Notes |
|---|---|---|
| macOS (Spotlight) | Yes | Handles minor typos and phonetic errors since macOS Sierra. |
| Android (app drawer) | Yes | The device keyboard’s autocorrect often masks the search, but fuzzy logic also exists natively. |
| KDE Plasma (KRunner) | Yes | Long offered approximate matching for apps, files, and system actions. |
| GNOME (Shell search) | Yes | Basic approximate matching for apps and settings. |
| Windows 11 (Build 26300.8687) | Yes (experimental) | Currently limited to installed apps; may expand later. |
Thus, Windows 11 is finally catching up, and for many productivity‑minded users it’s the single most impactful usability improvement of the year.
Known Issues and Caveats
As with any Dev Channel build, rough edges remain. Microsoft’s official known-issues list for build 26300.8687 includes:
- Some Insiders may experience explorer.exe crashes when right-clicking on the taskbar.
- The new Search might momentarily show a “No results found” message before populating with fuzzy matches—a timing quirk that should resolve as the indexer warms up.
- On devices with an exceptionally large number of installed apps (several hundred), the fuzzy matching process can add a slight, sub-second delay to search responsiveness.
- The Widgets board may still fail to load for a subset of users, though the build includes a mitigation.
Because the feature is experimental, Microsoft may adjust the edit-distance threshold or dictionary in subsequent updates without notice. Testers are advised to share constructive feedback via the Feedback Hub under “Desktop Environment > Search.”
What’s Next?
Microsoft has not provided a public timeline for shipping typo-tolerant search to general availability. Historically, features that debut in the Dev Channel take anywhere from three months to a year to reach the Release Preview ring, and some—like the controversial taskbar changes in 2023—never make it out. The overwhelming positive reception, however, suggests that approximate matching has a strong chance of landing in the Windows 11 24H2 feature update or a subsequent Moment release later in 2026.
In the meantime, users not on Insider builds can achieve similar functionality via PowerToys Run, Flow Launcher, or the classic Everything search tool. Each offers fuzzy filtering across files and folders as well, though none integrates as tightly with the Start menu as the native feature does.
Verdict: A Welcome Productivity Boost
Windows 11 Insider Preview Build 26300.8687 demonstrates that Microsoft is listening to one of the oldest complaints about its desktop experience. Typo-tolerant app search might seem like a small change, but it eliminates a daily frustration for millions of people. By combining established fuzzy algorithms with local processing, the feature manages to be both smart and private. Early testers clearly love it, and the surrounding build appears stable enough for daily driving—provided you accept the usual Dev Channel risks.
For Windows enthusiasts, this is a build worth installing. For everyone else, keep an eye on the Beta channel; if the feature continues to garner positive feedback, it could arrive on your PC sooner than you think. Until then, every mistyped “Chrome” can finally rest easy—Windows is learning to forgive.