What the search index does and how it breaks
Windows Search runs a background service, SearchIndexer.exe, that crawls the folders you chose and builds a database of file names, contents and metadata. The index lives under %PROGRAMDATA%\Microsoft\Search\Data and typically grows to 1–10 GB depending on how much text it is asked to remember. Search feels instant because results come from this database, not from scanning the disk live.
Trouble shows up in two flavors. The index goes stale or corrupt — files you can see in Explorer do not show up, or search returns nothing at all. Or the indexer churns: SearchIndexer.exe pins a core, keeps the disk at 100% and never settles, usually after a big update or when an index build was interrupted mid-way. Both cases end the same way: delete the index, let Windows build a fresh one.
- Files visible in Explorer never appear in search results
- Search finds nothing for file names you know exist
- SearchIndexer.exe holds the CPU or disk at a high level for hours
- The folder %PROGRAMDATA%\Microsoft\Search\Data grows past several GB
- Outlook search shows no results — it rides on the same index
Rebuilding the index the official way
Press Win+R, type control and press Enter, then open Indexing Options (switch the view to icons if you land in categories). Click Advanced, and on the Index Settings tab press Rebuild and confirm. Windows wipes the existing index and starts over — during the rebuild the search box returns incomplete results, and on large libraries the process quietly runs for a few hours in the background.
The manual route does the same with more control. In an elevated prompt run net stop "Windows Search" (the service's short name is WSearch), then delete the contents of %PROGRAMDATA%\Microsoft\Search\Data — some subfolders refuse access because of SYSTEM-level permissions, so take ownership or simply use the Indexing Options dialog instead of forcing it. Then run net start "Windows Search" and indexing resumes from scratch. Whatever route you take, the locations list in Indexing Options survives: your settings are not lost, only the database.
Keeping the index lean
A rebuilt index is only as good as its scope. In Windows 11, Settings → Privacy & security → Searching Windows decides between Classic mode (documents, e-mail and the default library folders) and Enhanced mode (your whole drive) — Enhanced is the usual reason an indexer runs hot on a big disk. Review the list in Indexing Options → Modify and uncheck heavy folders with games, videos, node_modules-style project trees and virtual machine disks.
Outlook users should know that rebuilding also wipes the mail index, so the first search-heavy day afterwards will re-crawl mailboxes. To see whether the index is even worth shrinking, measure first: the before/after storage report in Kleaner PRO shows how much %PROGRAMDATA%\Microsoft\Search\Data actually holds relative to the rest of the drive. With that number in hand, you rebuild with evidence instead of a guess.
Questions and Answers
How long does a Windows Search index rebuild take?
From a few minutes on a small document library to several hours on a large one. It runs in the background at low priority; search stays usable but incomplete until it finishes.
Is it safe to delete the files in %PROGRAMDATA%\Microsoft\Search\Data?
Yes, once the Windows Search service is stopped — you lose only the index database, never your files, and Windows rebuilds it automatically from the locations configured in Indexing Options.
Why is SearchIndexer.exe using so much CPU or disk?
Usually a fresh rebuild in progress, Enhanced indexing mode on a big drive, or a stuck index after an interrupted update. Pause indexing, narrow the indexed locations, or rebuild to clear the jam.
Know what is included before you buy.
The one-time 30-minute trial covers core tools. PRO-labelled features stay locked until a paid license is activated.
Read next
Write to us: [email protected]