Symptoms
- Searchindexer.exe or Search shows high CPU/disk in Task Manager
- Usage spikes after adding many new files or after a Windows update
- Usage eventually settles down on its own after a while
- Search itself feels slow while indexing is active
Likely causes
- CommonIndex rebuilding after a Windows update or large file changeBig changes can trigger a full or partial reindex that takes time.
- CommonIndexing locations set too broadly, including large drives or foldersMore content to index means more sustained CPU/disk use.
- PossibleA corrupted index databaseCorruption can cause repeated, unproductive reindexing attempts.
- PossibleIndexing a network drive or external driveThis can be slower and more resource-intensive than local indexing.
- PossibleIndexing running alongside other heavy tasksCombined with an antivirus scan or update, the impact feels worse.
What to do
- Let indexing run uninterrupted after a large update or file change; it typically settles within a few hours.
- Search 'Indexing Options' in the Start menu to see and adjust which locations are indexed.
- Remove folders you don't need to search quickly (like large media libraries) from the indexed locations list.
- If usage stays high for many days, try rebuilding the index: Indexing Options > Advanced > Rebuild.
- Check Task Manager to confirm indexing isn't running at the same time as a scheduled antivirus scan; stagger them if so.
- Make sure indexed external or network drives are actually connected, since a missing one can cause repeated retry attempts.
- Update Windows fully, since search-related bugs are sometimes fixed in updates.
- As a last resort, you can turn off indexing for specific drives entirely if search speed there isn't important to you.
Tools and parts
- None required
When to call a pro
This is a background service issue you can manage yourself; it rarely requires professional repair.
Safety
Generally low risk
Generally low risk for a careful person. Stop if anything looks different from what this guide describes.