Windows Search
Also called wsearch, windows search service, searchindexer
The Windows service that builds and queries the file and Start search index.
What you need to know
This is the search index, not a random leftover.
Windows Search crawls files so Start and File Explorer can answer quickly. High disk after an upgrade or a new folder is often a rebuild.
- Important?
- Yes, for fast Start and File search
- High disk normal?
- During a rebuild, yes
- Safe to disable?
- Only if you will wait on every search
What does this service do?
Display name: Windows Search. Service name: WSearch.
WSearch maintains the index used by Start, File Explorer search, and some apps. SearchHost.exe is the box. This service is the catalog.
History on Windows
Still present
Windows Desktop Search shipped as an add-on in the Windows XP era. Windows Search became a built-in service on Windows Vista and has stayed on Windows 7, 8, 10, and 11. The service name WSearch is still the contract on current Windows.
| First built-in as this service | Windows Vista (2007) |
|---|---|
| Earlier form | Windows Desktop Search add-on on Windows XP |
| Still present | Yes, including Windows 10 and Windows 11 |
| Discontinued | No |
Why does Windows need it?
Without an index, every search walks the disk. That is slow on a large drive and worse on a spinning disk.
When does it run?
It runs when Windows is building or updating the index, and when a search query needs it. It can look idle between those jobs.
Should it always be running?
Always running is not required. A working trigger or automatic start that wakes for indexing is enough. Disabled means every search is a live crawl.
Can I disable it?
Only if you accept slower search
You can stop WSearch to test whether the indexer is the disk load. Leaving it off makes Start and folder search slower. That is a trade, not a cleanup win.
What happens if I disable it?
Start and File Explorer search fall back to slower unindexed queries. Some apps that rely on the index return fewer results.
Process host
The indexer is usually SearchIndexer.exe. SearchHost.exe is the search box. Ending svchost.exe is the wrong first move. See SearchIndexer.exe / SearchHost.exe.
Dependencies
| Depends on | RPC and core Windows services |
|---|---|
| Used by | Start, File Explorer, and some Microsoft 365 search surfaces |
Resource behavior
- CPU
- Can rise while crawling
- Disk
- High during a rebuild
- Memory
- Moderate
- Network
- Low unless a location is remote
Common problems
High disk after an upgrade
Windows may rebuild the index. That can last hours on a large HDD. Check Indexing Options before you disable the service forever.
Search misses new files
The folder may be excluded, or the index may still be processing. Open Indexing Options and look at status.
Troubleshooting
Safe steps first.
See if the index is rebuilding
Indexing Options shows status. A rebuild is a reason for disk use.
Pause locations, do not delete System32
Remove a huge folder from the index as a test. Do not delete SearchIndexer.exe.
Rebuild only after you know the scope
A rebuild is a real job. Use it after a broken index, not as a weekly habit.
Technical details
Technical details
| Display name | Windows Search |
|---|---|
| Service name | WSearch |
| Common host | SearchIndexer.exe |
Sources and verification
Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. How we research.
- Microsoft Learn: Windows Search · Windows Search overview
Was this article useful?
A yes or no is enough. Pick a reason if you want, or add a short note.
Thanks. That helps us improve this page.