Technical Anshu
Tutorials Blog
🔍 Index Scope

Windows Search Indexing Options Add the Folders You Actually Search

An index is a map, and Windows ships with only half the town drawn in. This guide shows how to put your real work folders on the map — and keep the junk off it — so search is fast exactly where you need it.

✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 6 minute read
🎥 Watch the full video — remove web results first, then fix the map with this guide

Plenty of "slow search" complaints are really wrong-map complaints. The index is healthy, Bing is gone, and search still crawls — because the folder being searched was never indexed in the first place, so Windows walks it live, file by file. Scope tuning is the unglamorous fix: tell the indexer the truth about where your work lives.

Indexing Options — included locations (illustration)
Indexed locations [x] Start Menu [x] Users (Desktop, Documents, Pictures...) [ ] D:\Office Files <- your real work lives here, unindexed [ ] E:\Projects <- searched daily, found never Modify -> tick the folders you actually search
👆 Illustration — search can only find instantly what the index was told to watch
1

The Rule — Search Is Only Fast Where the Index Looks

Windows Search has two gears. Folders inside the index are answered from the database — instantly. Folders outside it are searched by walking the disk live, folder by folder, which is slow and often times out before finishing. Out of the box, Windows indexes your user profile — Desktop, Documents, Pictures, the Start Menu — and little else. The second drive where the office actually keeps its files, the Projects folder on D:, the shared work partition: none of it is indexed until somebody adds it. If your searches feel instant for some things and hopeless for others, this split — not Bing, not a bug — is usually the whole explanation.

2

Add the Folders You Actually Search

  1. Open Indexing Options and click Modify.
  2. In the location tree, tick the folders where your real work lives — the D: drive work folder, the projects partition, the shared documents folder.
  3. Click OK and give Windows time: newly added folders are indexed in the background, and results improve as the count climbs.
  4. Resist the opposite temptation. Do not tick the entire C: drive or the Windows folder "to be safe" — indexing system folders balloons the database, slows the indexer, and fills results with system files you will never search for.

One honest limit: network locations are mostly out of bounds. Windows will not index an ordinary mapped network drive the way it indexes local folders (server-side indexes on Windows Server are the exception), so files on a NAS or file share will stay in the slow, live-walk gear no matter what you tick locally. Know that before promising anyone instant searches across the office share.

3

Prune What You Never Search

Scope tuning cuts both ways. App caches, game libraries, download dumps and backup folders that sit inside your profile get indexed by default and return as noise in results. In the same Modify list, untick locations that produce clutter — a Downloads folder full of installers is the classic example — and the panel gets cleaner while the index gets smaller and quicker to maintain. Review the scope once on every office PC you set up; ten minutes of honest scoping beats every "search booster" utility ever sold.

🎥 Pair This With the Bing Fix From the Video

Local-only search from the video plus an honest index scope from this page is the complete fast-search setup.

▶️ Watch Full Video
❓ Frequently Asked Questions

Can I just index the whole C drive so everything is covered?

You can, but you should not. Indexing the Windows and Program Files folders massively grows the database, keeps the indexer busy, and floods results with system files. Index your data locations — profile folders and your work partitions — and leave the operating system out of it.

Why will Windows not index my mapped network drive?

By design, Windows Search indexes local storage; ordinary mapped drives and NAS shares are searched live instead, which is slow. The exception is folders on a Windows Server with its own indexing, where the server's index can be queried. For a NAS, expect live-walk speeds and plan folder structures accordingly.

I added a folder but search still misses its files. What gives?

New locations are indexed in the background, and Windows throttles indexing while you work. Check the item count in Indexing Options — it should be climbing. If the folder was added hours ago and nothing has been indexed from it, the rebuild guide in this set is the next step.

This guide is based on the Technical Anshu Windows Search video • Stuck on a step? Ask in the video comments — you will get a reply 🙏