Windows Search Slow? Every Fix, From Gentle to Drastic

The short version: restart the Windows Search service first — it fixes a stalled search more often than any other step. If results are still slow, switch from Enhanced to Classic indexing, untick locations you never search in Indexing Options, and only then rebuild the index (budget several hours). If SearchIndexer.exe is eating CPU, exclude your Outlook data file and any code folders. And if you fix it monthly, stop: Everything for filenames and Agent Ransack for contents replace Windows Search outright.

1. Restart the Windows Search service (2 minutes)

When search suddenly returns nothing — or the search box won't accept typing at all — the indexing service has usually hung. Restarting it is free and instant:

1. Press Win+R, type services.msc, press Enter.
2. Scroll to Windows Search in the list.
3. Right-click it → Restart. If the option reads Start, the service was stopped — start it.
4. While you're there, double-click the service and confirm Startup type is set to Automatic (Delayed Start), the default. If something set it to Disabled, that's your whole problem.

Give it 30 seconds, then search again. In our experience this alone resolves the "search stopped working after an update" complaint most of the time.

2. Switch from Enhanced to Classic indexing (5 minutes)

Windows 10 and 11 offer two indexing modes under Settings → Privacy & security → Searching Windows (on Windows 10: Settings → Search → Searching Windows):

• Classic indexes your libraries and desktop — Documents, Pictures, Music, Videos.
• Enhanced indexes the entire PC, every drive, every folder.

Enhanced sounds better but it's the setting most likely to make a machine feel slow: the indexer crawls hundreds of thousands of files you'll never search for, and keeps re-crawling them every time they change. Switch to Classic unless you genuinely search system-wide. If you keep Enhanced, use Exclude folders from enhanced search on the same settings page to skip heavy directories — game libraries, virtual machine images, code checkouts.

This page also shows Indexing status ("X items indexed") — note that number; you'll use it in step 5.

3. Trim indexed locations in Indexing Options (5 minutes)

The classic control panel gives finer control than Settings does:

1. Press Win+R, type control srchadmin.dll, press Enter. The Indexing Options window opens.
2. Click Modify.
3. Untick every location you never search: old archive folders, browser caches, secondary drives full of media you find by browsing, and especially developer folders (see step 7).
4. Click OK.

A smaller index is faster to query, faster to update, and far less likely to corrupt. The Outlook entry in this list controls email indexing — leave it ticked unless Outlook search isn't something you use (more on this in step 7).

4. Rebuild the index — the nuclear option (hours)

If search returns wrong or missing results even after a restart, the index database is likely corrupt. Rebuilding deletes it and starts over:

1. Open Indexing Options again (Win+R → control srchadmin.dll).
2. Click Advanced (needs administrator rights).
3. On the Index Settings tab, under Troubleshooting, click Rebuild, then OK on the warning.

Be honest with yourself about the cost before you click: a rebuild can take several hours, and search results are incomplete the entire time. On our 1.2-million-file test library it ran for the better part of a workday. Kick it off overnight, leave the PC plugged in, and don't panic when searches look broken the next morning if it hasn't finished.

5. Check indexer status — sometimes the fix is patience

The top of the Indexing Options window tells you what's happening: "Indexing complete." means the index is healthy; "3,419 items remaining" means it's still working. After a rebuild, a big file dump, or on a brand-new PC, slow search is often just an unfinished index.

Two things to know while it churns:

• Indexing deliberately backs off while you're actively using the machine, so it finishes fastest when the PC sits idle and plugged in.
• If indexing is hammering the disk at the worst moment (a video call, a deadline), you can pause it from the Indexing Options window with the Pause button — it stays paused for up to 15 minutes at a time.

6. Run the Windows Search troubleshooter (5 minutes)

Microsoft ships a dedicated fixer that resets permissions and restarts stuck components:

1. Open Settings → System → Troubleshoot → Other troubleshooters.
2. Find Search and Indexing and click Run. (On the newest Windows 11 builds this opens the Get Help app and walks you through the same checks.)
3. Tick the problem that matches yours — usually "Files don't appear in search results" — and apply the suggested fixes.

It's not magic, but it catches the boring causes: a stopped service, broken index permissions, or a search database that needs resetting.

7. SearchIndexer.exe eating CPU or RAM? Find the feeder

Open Task Manager (Ctrl+Shift+Esc) and look for Microsoft Windows Search Indexer (SearchIndexer.exe). Brief spikes after file changes are normal. Sustained high CPU or multi-gigabyte RAM use means something keeps feeding it. The two usual suspects:

• A large Outlook data file. A 20–50 GB OST gives the indexer endless work, because every synced mailbox change triggers re-indexing. If you can live without Windows-side Outlook search, untick Microsoft Outlook under Indexing Options → Modify.
• Code folders. A single JavaScript project's node_modules can hold 100,000+ tiny files that change on every install; .git folders and build output are nearly as bad. Exclude your entire projects directory from the index — proper code search tools don't need the Windows index anyway, as we cover in our guide to searching file contents on Windows.

A note on registry and Group Policy: you can throttle or disable the indexer via Group Policy (Computer Configuration → Administrative Templates → Windows Components → Search) or registry edits, but for a personal machine the steps above achieve the same result without the risk. We don't recommend registry surgery as a speed fix.

8. The hardware truth: no fix outruns a spinning disk

If Windows is installed on a mechanical hard drive, every step above is treating symptoms. Indexing is a brutal random-I/O workload, and an HDD handles it hundreds of times slower than an SSD — which is why search on an older laptop crawls no matter how clean the index is. Moving Windows to even a budget NVMe drive like the Crucial P3 Plus is the single biggest search-speed upgrade available, and it speeds up everything else too. Our SSD upgrade guide covers which drive fits which machine and what the migration involves.

9. When to stop fixing Windows Search and replace it

Here's the honest part. If you've done the steps above more than once, the problem isn't your settings — it's that Windows Search is an indexed, everything-by-default system that trades speed for breadth. Power users get better results by replacing it:

• For filenames: Everything (voidtools) reads the NTFS master file table directly and finds any filename on your drives in milliseconds, with no background indexer grinding away. It's free. Our Everything vs Windows Search comparison shows the speed gap in detail.
• For file contents: Agent Ransack searches inside documents on demand — boolean queries, regex, Office and PDF support — with no index to corrupt in the first place.

Replacing beats endlessly fixing. Keep Windows Search for the Start menu and Settings lookups it's actually good at, and hand file finding to tools built for it. Our Windows file search hub maps out the full ecosystem.

Troubleshooting

• Search box won't accept typing or shows a blank panel. That's the search UI, not the index. In Task Manager, find Windows Explorer and click Restart; if that fails, end the Search (SearchHost.exe) process — it relaunches on next use.
• The index keeps rebuilding itself. Usually disk trouble. Run chkdsk C: /scan from an administrator terminal. Also check the index database size at C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb — if it's grown past 30–40 GB, trim locations (step 3) and rebuild once more.
• Outlook search broke after trimming the index. You unticked Microsoft Outlook in step 3 or 7. Re-tick it in Indexing Options → Modify and let it re-index the mailbox (this takes a while for big OSTs).
• Results miss a folder you definitely indexed. Check the folder isn't in the Exclude list from step 2, and that its files aren't marked with the "not content indexed" attribute (file Properties → Advanced).

FAQ