Guides · for everyone · updated August 2026
Windows Search can't find a file you know exists?
Your file is fine: the index never saw it. Windows Search only covers its “indexed locations” (a small slice of the disk) and often skips file contents. A whole-machine index like Interlinked Files covers every drive and folder, so the file can't hide.
The three reasons it happens
1 · The file lives outside the indexed locations
By default Windows Search indexes your user libraries and little else. Downloads that got moved, project folders on the root of C:, anything on a second drive: outside the fence, invisible to search, no matter how precisely you type the name.
2 · You searched for words inside the file
Content search only works where content indexing is on and only for types Windows has a filter for. A phrase inside a PDF in a non-indexed folder fails twice at once. It looks like the search is broken; really it never read the file.
3 · The index is behind
Windows rebuilds and catches up on its own schedule. A file saved a minute ago, or thousands of files copied yesterday, may simply not be in the index yet, and there's no honest progress bar telling you that.
The fix, in one move
All three causes are the same disease: a partial index. Interlinked Files replaces it with a complete one: every file on every NTFS drive, names and contents (PDFs, text, code), kept current within about a second of a save. Name lookups answer in under a millisecond; whole-machine content searches in about 8 ms. On the same machine, 20 typical Windows Search queries took a median of 67 seconds. That's the gap an index closes.
Common questions
Why does Windows Search miss files that definitely exist?
Three usual reasons: the file sits outside Windows Search's indexed locations (most of the disk is), you searched for words inside the file but content indexing was off or unsupported for that type, or the index simply hadn't caught up yet. The file is fine: the index never saw it.
How do I make Windows search the whole computer?
You can switch Windows Search to 'Enhanced' mode in Settings, but it stays slow to build, skips many content types, and drops behind on changes. The practical fix most people land on is a dedicated indexed search tool. Interlinked Files indexes every file on every drive by default and answers in milliseconds.
How fast should file search actually be?
On an indexed machine, a name search answers in well under a millisecond and a whole-machine content search in about 8 milliseconds, measured across millions of files. Across 20 typical queries, Windows Search took a median of 67 seconds on the same machine. Waiting is not a law of nature; it's a missing index.
Is there a search that includes external and second drives?
Yes. Interlinked Files indexes every NTFS drive attached to the machine (second SSDs, big archive drives) as one searchable whole, so a single query covers all of them.
Free forever, no card. Download for Windows · deeper comparison: Interlinked vs Windows Search.