Fix Windows Search Indexer High CPU Usage

If your PC’s fans are spinning up and Task Manager shows the Search Indexer (SearchIndexer.exe) eating 50–100% of your CPU, the Windows Search service is likely stuck in a loop or overwhelmed by a large or corrupted index. This guide walks you through the most effective fixes, from simple service restarts to rebuilding the index from scratch, so you can get your CPU usage back to normal and keep Windows search working.

What You’ll Need

Administrator access to the PC (to run commands and change service settings).
A few minutes of patience – the index rebuild can take a while on large drives.
Optional: a backup of your important files before any system changes, though the steps here are generally safe.

Step-by-Step

Confirm the culprit. Press Ctrl+Shift+Esc to open Task Manager. In the Processes tab, look for “Search Indexer” or “SearchApp.exe”. If it’s using high CPU, proceed.
Restart the Windows Search service. Press Win+R, type services.msc, and press Enter. Scroll to “Windows Search”. Right-click it and choose “Restart”. This often clears a temporary glitch. If the service is already stopped, start it.
Check for pending indexer activity. After the restart, open Settings (Win+I) → “Privacy & security” → “Searching Windows”. Look for the indexing status. If it says “Indexing complete”, but CPU is still high, continue. If it says “Indexing in progress”, let it finish for a few hours – it’s normal.
Reduce indexed locations. In the same “Searching Windows” page, click “Customize search locations here”. Uncheck folders you don’t need to search, like large media libraries or backup drives. This shrinks the index and reduces CPU load.
Rebuild the index. Open Control Panel → “Indexing Options”. Click “Advanced” → “Rebuild”. Confirm. This deletes and recreates the entire index. It can take hours, but it fixes corrupted index files that cause high CPU loops.
Run the Search and Indexing troubleshooter. Go to Settings → “System” → “Troubleshoot” → “Other troubleshooters”. Find “Search and Indexing” and run it. Follow the prompts – it may identify and fix issues automatically.
Check for system file corruption. Open Command Prompt as administrator (right-click Start → “Terminal (Admin)”). Run sfc /scannow and wait for it to complete. Then run DISM /Online /Cleanup-Image /RestoreHealth. Restart and check CPU usage.
Disable Windows Search temporarily (last resort). If nothing helps, you can disable the service: in services.msc, double-click “Windows Search”, set “Startup type” to “Disabled”, and stop the service. This kills the CPU usage, but you lose search functionality until re-enabled. Only do this if you rarely use Windows search.

Common Mistakes

Rebuilding too often. Rebuilding the index is heavy on CPU. Doing it repeatedly without addressing the root cause (like a huge indexed folder) just wastes time.
Ignoring third-party antivirus. Some security software can interfere with the indexer, causing it to loop. If you have a third-party AV, temporarily disable its real-time protection to see if CPU drops.
Not waiting long enough. A full index rebuild on a large drive can take 1–3 hours. Don’t assume it’s stuck; check the indexing status in Settings.
Disabling the service permanently. This breaks search in File Explorer, Start menu, and Outlook. It’s a sledgehammer fix – only use if you truly don’t need search.

Tips

Set indexing to “Respect power settings” in Indexing Options → Advanced → Index Settings. This makes the indexer pause on battery power.
Exclude folders that change constantly, like temp folders or large game directories. You can do this in “Customize search locations”.
Keep your Windows updated. Microsoft frequently fixes indexer bugs via updates.
If you have an HDD, consider defragmenting it (Optimize Drives) – a fragmented drive can slow down indexing.

Troubleshooting

If the service restarts but CPU stays high: Check if the indexer is stuck on a specific file. Use Process Monitor (from Microsoft Sysinternals) to see what files SearchIndexer.exe is accessing. If it’s hammering one file, that file might be corrupted – try moving or deleting it (if safe).

If the rebuild fails or never finishes: The index database might be locked. Stop the Windows Search service, then delete the folder C:\ProgramData\Microsoft\Search\Data\Applications\Windows (you’ll need admin rights). Restart the service – it will create a fresh index. This is a more aggressive rebuild.

If the troubleshooter finds nothing: Check Event Viewer for errors from “Windows Search”. Look under “Windows Logs” → “Application” for events with source “Windows Search”. They may point to a specific issue like a corrupt file or a permissions problem.

If CPU is still high after disabling the service: Something else is wrong. Check for malware with a full scan, and verify that no other process is masquerading as SearchIndexer.exe (check the file path – the legitimate one is in C:\Windows\System32).

Frequently Asked Questions

Q: Is it safe to disable Windows Search? Yes, but you lose the ability to search in File Explorer, Start menu, and Outlook. You can always re-enable it later.

Q: How long does a rebuild take? It depends on the amount of data. On a typical 1TB drive with 500GB of files, it can take 1–3 hours. During that time, CPU usage will be high – that’s normal.

Q: Will rebuilding the index affect my files? No, it only rebuilds the search database. Your files remain untouched.

Q: Why does the indexer run at 100% after every Windows update? Windows updates often change the index schema, forcing a full re-index. This is normal and should settle down after a few hours.

Q: Can I limit the indexer’s CPU usage? Not directly. But you can reduce the number of indexed locations, which makes the job smaller. There’s no built-in CPU throttle.

Q: Does the indexer cause high CPU on SSD too? Yes, but it finishes faster on SSDs. If it’s persistent, follow the same steps.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →