History · Apr 9 2026 · 8 min
Thirty years
of good intentions.
The thing built into the Start menu of every Windows machine in the world, designed by the people who wrote the operating system, takes sixty-seven seconds to find a file that an indexed engine finds in eight milliseconds. This is not a bug. It is three decades of architecture.
Indexed search
Interlinked Files · 4.47M file corpus
Windows Search
Same machine · same drive · same query
Thirty years of Windows file search
From a walker to an indexed walker.
The history of Windows file search is the history of Microsoft noticing the previous version was slow, rebuilding it, and ending up with something only marginally faster.
| Year | Milestone | What changed | Result |
|---|---|---|---|
| 1995 | Start > Find > Files or Folders | No index. Full directory walk every query. | Minutes |
| 2005 | Windows Desktop Search (XP add-on) | First indexer attempt. Ran as a service. Slow to populate. | Faster for indexed paths |
| 2007 | Windows Vista: Instant Search | Built-in indexer. Consumes RAM. Users complain. | 10 to 30s for unindexed |
| 2010 | Windows 7: scope narrowed | Microsoft restricts default index to user folders only. | Less coverage |
| 2015 | Windows 10: Cortana era | Local search merged with Bing web results. | Added latency |
| 2021 | Windows 11: Enhanced mode | Optional full-drive indexing. Still throttled. | Not instant on 4M files |
| 2026 | Windows Search today | Partial index + web merge + throttled service. | 67.1 seconds |
Three compounding decisions
None of them wrong. All of them fatal.
Windows Search is slow because three architectural decisions, each rational in isolation, compound into the most polished bad file search in computing.
Partial index
Not indexing everything by default
Windows Search indexes a small subset of paths by default: your user folders, the Start menu, and not much else. Rational in 2007 when drives were slow and RAM was scarce. Twenty years later, any query for a file outside your profile either returns nothing or falls back to a slow walk. On a 4.47 million-file drive where most files live outside the default scope, this is the same as not having an index at all.
Web merge
Mixing local search with Bing
Since Windows 10, the Start menu search box is also the web search box. Every query contacts a remote service, waits for (or times out) web results, merges them with local results, and ranks them together. The user waits for the slower of the two before seeing anything. Even if the local index were fast, the web-merging layer on top keeps end-to-end time floating around several seconds.
Throttled service
Playing nice with everything
The indexer tiptoes: it yields to foreground programs, throttles its own IO, sleeps on battery. On a slow drive with an active user, the indexer never reaches steady state. Files you created this morning may not be indexed. Files deleted last week may still appear. Users notice, stop trusting it, and fall back to File Explorer search, which is a recursive walk. Even slower.
A partial index + a web merge + a throttled service = the most polished bad file search in computing.
The structural asymmetry
Every constraint Microsoft has, a third party doesn't.
Microsoft ships to a billion users who want everything for free, and a noticeable fraction of them don't want an indexer at all. They cannot index every file by default. They cannot consume 400 MB of RAM during a build. They cannot pin a core for ten minutes on first launch.
We can. Users who install Interlinked Files expect it. They opt into the aggressive side of the trade. File search goes from a minute to a microsecond. Everything else stays the same.
Microsoft
Serves 1B users who didn't ask for this
Interlinked Files
Serves users who chose speed
The cost of legacy
Where the time goes on every query.
| Stage | Windows Search | Interlinked Files | Why |
|---|---|---|---|
| Index scope | User folders only | Every file | Default coverage determines hit rate |
| Fallback on miss | Full directory walk | No fallback needed | Indexed engines don’t walk |
| Web merge overhead | ~2 to 4s per query | 0s | Local-only means no network wait |
| Index freshness | Hours behind | Real-time (USN journal) | Throttled vs. unrestricted IO |
| End-to-end query time | 67.1 seconds | 8 ms | 8,387× faster |
The bottom row is the only row most users ever see. But the bottom row is the product of every row above it. Each architectural constraint adds latency. They compound multiplicatively, not additively.
Where the 67 seconds go
Anatomy of one Windows Search query.
You type a filename into the Start menu. Behind the scenes, Windows Search checks its partial index, finds nothing, falls back to a directory walk, simultaneously fires off a Bing request, waits for both, merges the results, and finally shows you the file. Here is where the time actually goes.
If you remove the directory walk
Windows Search
82% is the walk. 18% is overhead.
Indexed engine
No walk. Direct lookup. Done.
The directory walk is 82% of the total time. Eliminate it and the query moves six orders of magnitude.
The numbers
What happens when you remove every constraint.
Filename search
Best query on 4.47M files
Content search
446K code files, sparse ngram
Memory at idle
vs 800 MB (Outlook) / unknown (WS)
Index build
4.47M filenames, cold start
Live updates
Real-time via NTFS change journal
Coverage
Every file on every NTFS volume
The speed difference between Windows Search and Interlinked Files on the same machine, the same drive, the same query. Not a synthetic benchmark. A real 4.47 million-file developer workstation. Every constraint removed. Every path indexed.
The lesson
Windows Search isn't broken. It's trapped.
Windows Search cannot index aggressively because it ships to a billion people who didn't ask for it. It cannot skip web results because that would break the Start menu UX model. It cannot consume real CPU because someone on a Surface Go would notice.
Third-party file search has always been faster than Windows Search and always will be. Not because the engineering is smarter. Because the permission model is different. Install Interlinked Files and you opt into the aggressive side of the trade. The constraints that cripple Windows Search do not exist here.
File search goes from a minute to a microsecond. Everything else stays the same.