Microsoft shipped a targeted reliability update on March 10, 2026, that directly tackles a stubborn Windows 11 File Explorer flaw: searching across multiple drives from “This PC” often returned incomplete or inconsistent results. KB5079473, now rolling out to Windows 11 24H2 and 25H2, makes that experience dependable again – though it’s not a speed fix, and administrators should measure actual gains before changing any indexing policies.

The Fix: What Changed in Builds 26100.8037 and 26200.8037

KB5079473 is a cumulative update that advances Windows 11 24H2 to build 26100.8037 and Windows 11 25H2 to build 26200.8037. Microsoft’s official release notes state simply that it “improves File Explorer search reliability across multiple drives and ‘This PC.’” There is no mention of performance boosts, no published benchmarks, and no promise of a faster search experience. That’s by design: the update addresses a specific bug where queries spanning several local drives could miss files, show partial results, or behave erratically.

Some early testers have reported searches feeling snappier. While that’s plausible – a search that no longer hangs or times out may return results sooner – the improvement is rooted in correctness, not raw speed. Microsoft has not altered indexing algorithms, disk I/O patterns, or the search indexing engine itself. Instead, the patch fixes a logic problem in how File Explorer aggregates results from different volumes when you search from the top-level “This PC” node. For anyone who abandoned native search because “it never finds my files on the D: drive,” this is a welcome course correction. But it does not turn File Explorer into a real-time, whole-drive indexer.

Reliability vs. Speed: Why the Distinction Matters

A search tool that reliably returns the right files is a prerequisite for any further speed improvements. Before KB5079473, many users and IT departments wrote off File Explorer search as simply broken for multi-drive setups. They turned to third-party utilities like Everything, Listary, or WizFile, or trained users to search only within specific folders. That frustration was legitimate: opening “This PC,” typing a filename you know exists on a secondary SSD, and seeing no results after several seconds undermines confidence in the entire operating system.

Now that reliability is restored, the conversation shifts from “should I use File Explorer search at all?” to “is it fast enough for my workflow?” The answer depends entirely on your indexing configuration, storage layout, and query patterns. Classic indexing – the default – only indexes a limited set of locations (typically user folders and the Start menu). When you search from “This PC,” Windows uses the index for those locations but must fall back to a slower, brute-force scan for anything outside those boundaries. On a system with tens of thousands of files spread across multiple drives, that fallback scan can still take several seconds or even minutes, especially on mechanical hard drives.

Enhanced indexing widens the net significantly, covering almost every local file. That makes “This PC” searches much faster because nearly every result comes straight from the index. But the trade-off is higher CPU and disk activity, particularly after file changes or reboots, as the indexer works to keep up. On older or busier machines, that can lead to perceptible system slowdowns. KB5079473 doesn’t alter these fundamentals. It simply removes the buggy behavior that further degraded the experience, leaving the underlying indexing architecture to do its normal job.

Who Should Re-Evaluate Native Search Now?

The fix opens the door for three distinct audiences to reconsider File Explorer search, but the bar for “good enough” varies.

Casual home users who occasionally need to find a misplaced document across drives now have a reliable built-in tool. If your workflow involves clicking “This PC” and searching for a file a few times a week, and you don’t mind waiting a few seconds if the file isn’t indexed, KB5079473 may be all you need. You can stop remembering which third-party tool you installed and just use what’s in front of you.

Power users with multiple local drives are the prime candidates. If you keep a structured folder hierarchy but sometimes cannot recall whether a report went on drive C, D, or E, this update makes the native fallback viable. You can stay on Classic indexing for its lighter footprint, confident that when you do fire off a full-system search, it will actually find the file – even if it takes a little longer. That’s a meaningful shift from needing to open a separate application for every cross-drive query.

IT administrators managing fleets face a more complicated calculus. Many organizations licensed or deployed third-party search tools precisely because users complained about File Explorer’s unreliability. Now that the reliability bug is fixed, you can run a controlled experiment on representative hardware. Don’t immediately push Enhanced indexing or rip out existing tools. Instead, test the patched File Explorer against your current solution using real-world queries that your staff actually perform. Measure whether results are complete, and define an acceptable response time threshold – ideally by surveying the people who will live with the choice, not by an arbitrary desktop benchmark.

How We Got Here: A History of Windows 11 Search Gripes

File Explorer search dissatisfaction didn’t start with KB5079473, and it won’t end with it either. Since Windows 11’s launch, search has been one of the most complained-about features. Early builds suffered from sluggish performance, even within indexed folders, and the decision to integrate web results from Bing into the local search interface annoyed many power users. Updates like KB5044285 in late 2025 actually worsened search speeds for some, prompting Microsoft forum threads full of workaround suggestions – including the radical step of uninstalling the update entirely.

Behind the scenes, Microsoft has been working on a more ambitious overhaul. Windows Central reported on plans to declutter the search experience, remove web ads, and prioritize local files over online suggestions. PCWorld noted a quiet speed boost in File Explorer from a June optional update, but none of those improvements addressed the specific multi-drive reliability bug. KB5079473 is the targeted fix that makes the broader vision plausible. You cannot ask users to trust a new, simplified search UI if the underlying engine still fails to find files on a second hard drive.

This iterative pattern – incremental fixes layered on top of a creaky architecture – is typical of Windows development. The indexing engine itself dates back to Windows Vista, evolved through Windows 7 and 10, and still relies on a combination of the Windows Search service and legacy NTFS attributes. Rewriting it from scratch would be a monumental task, so Microsoft opts for pinpoint repairs. KB5079473 is exactly that: a scalpel, not a sledgehammer.

Your Action Plan: How to Test KB5079473’s Impact

If you manage Windows 11 machines, or simply want to know whether this update changes anything for you personally, run a structured test before drawing conclusions. The goal is to separate the update’s effect from other variables like indexing mode, hardware differences, or placebo perception.

  1. Confirm the update installed. Go to Settings > System > About and check the OS build. For 24H2, you should see 26100.8037; for 25H2, 26200.8037. If not, check Windows Update for pending restarts.
  2. Document your current indexing mode. Open Settings > Privacy & security > Searching Windows. Note whether “Find my files” is set to Classic or Enhanced. Do not change it yet – you need a baseline.
  3. Craft a test query set. Use files you know exist on different local drives. Include complete filenames, partial names, and terms that appear in file contents (if content search matters to you). Avoid relying solely on recently accessed files; create or move some test files to ensure they aren’t already cached.
  4. Run searches from “This PC.” Open File Explorer, click “This PC,” and type each query. Observe not just how quickly the first result appears, but whether the final result set is complete and correct. A fast empty result is still a failure.
  5. Compare folder-level searches. If a file doesn’t appear from “This PC,” go directly to the folder where it lives and search there. If the folder search works but “This PC” does not, the issue is specific to multi-drive aggregation.
  6. Reboot and repeat. Restarting flushes system caches and recently used file lists, giving you a cleaner measurement of cold-search performance.
  7. If reliability is perfect but speed is lacking, test Enhanced indexing. Before switching, record your current mode so you can revert. Then enable Enhanced via Settings, allow time for the index to rebuild (your drive will be busy), and rerun your queries. Note any improvement in search speed, but also monitor system responsiveness during normal work.
  8. Make a data-driven decision. For IT: set a quantitative bar. For example, “a search that takes over 10 seconds for a known filename on a secondary drive is unacceptable.” If native search meets the bar under Classic indexing, keep your configuration simple. If it requires Enhanced indexing, weigh the resource cost. If even Enhanced isn’t fast enough, retain your third-party tool and hold off until Microsoft delivers further speed optimizations.

Avoid the temptation to change indexing and re-test in the same session – you won’t know which variable helped. Test one change at a time, and always document the conditions.

KB5079473 is not the endpoint. Microsoft’s public roadmap, as reported by TechRadar and PC Gamer, includes a polished search interface that removes web results by default and emphasizes local files. That redesign will only succeed if the underlying engine is trustworthy. This update lays that foundation. Future patches may improve indexing performance, reduce the resource impact of Enhanced mode, or introduce smarter hybrid approaches that combine fast index lookups with targeted fallback scans.

For now, the practical takeaway is simple: File Explorer search for multi-drive systems is no longer broken. It may not be the fastest tool in your kit, but it can be the most convenient. Test it under your own conditions, decide whether it meets your needs, and keep an eye on upcoming builds. The search experience you’ve been waiting for is inching closer – one KB article at a time.