You type a filename into Explorer's search box on a mapped NAS drive, the green progress bar starts its slow crawl, and minutes later you're still waiting for a file you could have found by hand. This isn't a misconfiguration you can toggle away — Windows Search refuses to index network drives by design, and the tool everyone recommends (Everything) gets its magic from a local-disk trick that physically cannot work over a network. This article explains the real mechanics, then walks through every fix that actually works in 2026 — including the free ones.
Two facts explain almost every slow NAS search:
1. The Windows Search indexer does not index network locations. UNC paths (\\server\share) and mapped drive letters are excluded by design — you can't add them in Indexing Options, and the various Library workarounds don't change what the indexer actually crawls. This is documented behavior, not a bug (see Microsoft's Windows Search overview).
2. Without an index, Explorer searches by brute force. When you search an unindexed location, Explorer performs a live recursive scan: open a directory over SMB, wait for the server to enumerate it, recurse into every subdirectory, repeat. Each directory costs at least one network round trip. A share with 200,000 folders means hundreds of thousands of round trips, serialized. The time goes to network latency, not disk speed — which is why a faster NAS barely helps.
Microsoft's supported fix is to run the Windows Search service on the file server, so Explorer can hand the query to the server's own index. That works — but the service only exists on Windows Server, requires admin rights on that server, and simply does not exist for a QNAP, Synology, TrueNAS, or any Samba box. For NAS owners, the official path is a dead end.
Everything deserves its reputation, and it's worth understanding exactly where the speed comes from, because that's also where it ends.
On a local NTFS volume, Everything doesn't walk folders at all. It reads the Master File Table (MFT) — NTFS's internal catalog of every file on the volume — in one fast sequential pass, then subscribes to the USN change journal, NTFS's log of every create, rename, and delete. Result: a complete index in seconds and realtime updates with near-zero cost.
Neither of those exists over a network. SMB exposes files and folders, not the server's volume internals — a client can't read the MFT or the USN journal of a remote disk. So for network shares, Everything falls back to "folder indexing": the same slow recursive directory walk Explorer does, run on a schedule or by hand. Between rescans, the index goes stale — there is no realtime change detection over SMB. Voidtools' own answer for realtime network search is to run Everything (or its ETP/HTTP server) on the server itself — which requires the server to be a Windows machine you're allowed to install software on. Fine for a Windows file server you administer; impossible on a NAS. We've covered this gap in more depth in our comparison of Everything alternatives.
| Your situation | Best option | Why |
|---|---|---|
| All files on local NTFS drives | Everything (free) | MFT + USN journal make it instant and realtime locally. Nothing beats it there. |
| QNAP NAS, searching in a browser is fine | Qsirch | Full-text index built on the NAS itself. QNAP devices only. |
| Synology NAS, searching in a browser is fine | Universal Search | Same idea, Synology only. |
| Need to search inside file contents on a share | Agent Ransack / FileLocator Lite | On-demand content scanning. Slow on big shares, but the right tool for the job. |
| Small share you want offline anyway | Windows Offline Files | Syncs the share locally so the local indexer covers it. Costs disk space equal to the data. |
| Any SMB share (NAS, Windows Server, Samba) + instant name search in a Windows app | Malvicsearch | Client-side persistent index with realtime SMB change notifications. Nothing installed on the server. |
The architecturally cleanest place to build an index is on the NAS itself, next to the disks. Both big vendors ship this: QNAP Qsirch and Synology Universal Search. Both go beyond filenames into full-text content indexing.
The honest caveats: each works only on its own vendor's devices, and you search through the NAS's web UI or the vendor's apps — not from an arbitrary Windows workflow. But if you own a QNAP or Synology and a browser tab is an acceptable place to search, try the built-in engine first. It may be all you need.
Offline Files ("Always available offline"). This syncs a share to your local disk; the local copy is on NTFS, so Windows Search indexes it and search becomes fast. The catch is the word copy: you spend local disk space equal to everything you sync, sync conflicts appear when files change on both sides, and for a multi-terabyte share it's simply not practical. Reasonable for a small departmental folder; not a NAS answer.
Mapped-drive indexing tricks. Adding a share to a Library via registry or folder-redirect workarounds changes what Explorer displays, not what the indexer crawls. Searches still fall back to live enumeration.
OneDrive / cloud sync. Only relevant if your data lives in OneDrive or SharePoint. It doesn't make a NAS searchable.
We've written a fuller teardown of these in how to index a network share on Windows — including the cases where Offline Files is genuinely the right call.
Everything above is about finding files by name. If your actual question is "which contract mentions this clause," a name index can't answer it — you need a content search tool.
Agent Ransack / FileLocator Lite are the standouts: they scan inside files on demand, with good filtering, and they work fine over SMB. Because there's no persistent index, every search reads file contents across the wire — on a huge share that's slow, and there's no way around it without a server-side content index (which is exactly what Qsirch and Universal Search are). For content queries, they are the right tool.
UltraSearch / UltraFileSearch are on-demand name searchers. UltraSearch reads the MFT of local NTFS drives (like Everything), but on network shares both fall back to live enumeration with no persistent, realtime index — so they inherit the same NAS slowness this article is about. Listary is a polished launcher-style search focused on local drives and app integration rather than network shares.
Malvicsearch (our product) exists for the specific gap left by everything above: a persistent, realtime filename index of SMB shares, built and kept fresh entirely from the client side — no admin rights on the server, nothing installed on the NAS, works against any SMB server: Windows Server, NAS boxes, Samba on Linux.
How it deals with the mechanics described earlier:
What it does not do: Malvicsearch searches file and folder names and paths only — it does not look inside file contents (use Agent Ransack for that), and it runs on Windows 10/11 (64-bit) only.
When not to use Malvicsearch: if all your files are on local drives, install Everything instead — it's free and excellent at exactly that. If your main need is content search, or you're happy searching your NAS through its own web UI, you don't need us either. Malvicsearch earns its keep when your files live on a NAS or file server and you want instant, always-current name search inside a Windows app.
The trial is 5 days, full-featured, no credit card. A licence is $29 one-time (lifetime, 1 PC) with a 14-day money-back guarantee. Download it here and point it at your slowest share first.
If your shares live on a Windows file server rather than a NAS, the tradeoffs shift slightly — we've covered that scenario separately in fast file search on a file server.
Because the indexer is designed to index only local volumes. UNC paths and mapped drives can't be added in Indexing Options, so Explorer searches them with a live folder-by-folder crawl over SMB. The supported alternative — indexing on the server via the Windows Search service — exists only on Windows Server, not on NAS or Samba systems.
Not over SMB. Everything's realtime updates come from the NTFS USN change journal, which is only readable on local volumes. For network shares it offers folder indexing with scheduled or manual rescans; the index is stale between rescans. Realtime is possible only by running Everything or its ETP/HTTP server on the server itself, which must be a Windows machine you can install software on.
No. Malvicsearch is purely client-side: it builds and updates its index from your Windows PC over standard SMB, so it works with any SMB server — Windows Server, NAS boxes, or Samba on Linux — with no server-side software and no admin rights on the server.
No. It indexes file and folder names and paths only. For searching inside documents, use a content search tool such as Agent Ransack, or a NAS-side engine like QNAP Qsirch or Synology Universal Search, which build full-text indexes on the NAS itself.
Malvicsearch listens for SMB change notifications, which arrived with a median of about 2 seconds in our test suite. As a safety net for notifications a server fails to deliver, it also re-sweeps network locations every 15 minutes by default, and you can trigger a manual refresh from the menu at any time.
Searching a NAS from Windows doesn't have to mean watching Explorer's progress bar. Download the free 5-day Malvicsearch trial and search your shares as you type — or see pricing ($29 one-time, 14-day money-back guarantee).