You open Task Manager, and there it is: SearchIndexer.exe, chewing through 30, 50, 80 percent of your CPU while you are trying to work. The fans spin up, the laptop heats, and the battery drains — all for a background feature you never asked to run right now. Before you kill it in frustration, a short decision process separates the cases where patience is the fix from the cases where intervention is required.

Here is exactly what to do, in the order that resolves the problem fastest.

Why this happens

  • Post-update rebuild: Windows updates invalidate the search index, triggering a full rebuild that legitimately consumes heavy CPU for hours.
  • Large new file additions: Downloading big archives, syncing cloud folders, or connecting a drive full of files queues enormous indexing work.
  • Corrupted index loop: A damaged index database makes the indexer reprocess the same files endlessly, never finishing.
  • Problem files: Corrupt documents or malformed metadata can stall indexing threads, pinning CPU while making no progress.
  • Over-broad index scope: Enhanced indexing mode covers the entire drive, including folders you will never search, multiplying the workload.
  • Cloud sync churn: OneDrive or Dropbox constantly modifying files forces the indexer to re-index the same content repeatedly.
  • Antivirus double-processing: Real-time scanning of every file the indexer touches roughly doubles the CPU cost.
  • Outlook data files: Large email stores contain tens of thousands of items that are slow to index and rarely searched by content.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Confirm it is the indexer and assess the situation

  1. Open Task Manager, sort by CPU, and verify the consumer is SearchIndexer.exe or Microsoft Windows Search Indexer — not SearchHost.exe (the search UI) or another process.
  2. Ask: did this start after a Windows update, after adding many files, or out of nowhere? The first two have innocent explanations; the third needs investigation.
  3. Check Settings → Privacy & security → Searching Windows for the indexing status message — it often tells you a rebuild is in progress.
  4. This triage takes two minutes and prevents “fixing” a legitimate rebuild that would have finished on its own.

Fix 2: Give legitimate indexing a chance to finish

  1. Plug in the laptop and leave it on and idle for an extended period — overnight is ideal. Indexing is designed to yield to your activity, so idle time is when it makes progress.
  2. Do not repeatedly kill the indexer or shut down mid-rebuild; each interruption restarts portions of the work.
  3. Check progress the next morning in Task Manager. Declining CPU usage over successive checks means it is working through the backlog — let it continue.
  4. Only proceed to intervention if usage is unchanged after 48 hours of adequate idle time.

Fix 3: Rebuild the corrupted index

  1. Open Control Panel → Indexing Options → Advanced → Rebuild.
  2. This deletes the existing index and starts fresh — the nuclear option for the corrupted-index loop, and it works.
  3. Leave the laptop plugged in and idle for several hours afterward for the rebuild.
  4. Monitor for a day after completion. A clean rebuild resolves the majority of never-ending indexer CPU cases. For the full rebuild walkthrough with 24H2 specifics, see disabling search indexing in 24H2 .

Fix 4: Shrink what gets indexed

  1. In Indexing Options → Modify, uncheck folders you never search: game libraries, video archives, downloads, and external drives.
  2. In Settings → Privacy & security → Searching Windows, add large personal archives to Excluded folders.
  3. Consider switching from Enhanced to Classic mode so only libraries and the desktop are indexed.
  4. A smaller index means shorter rebuilds, lower ongoing CPU, and searches that still cover everywhere you actually look.

Fix 5: Hunt down the problem file or folder

  1. If CPU spikes correlate with a specific folder’s activity, that folder likely contains the stall-inducing file.
  2. Temporarily exclude the suspect folder in Indexing Options and watch CPU for an hour — a dramatic drop confirms the location.
  3. Within that folder, look for corrupt or bizarre files: zero-byte documents, malformed archives, or files with extremely long paths.
  4. Move suspects out, or exclude their file types in Indexing Options → Advanced → File Types. For the related SearchApp process, see SearchApp.exe high CPU .

Fix 6: Calm the cloud sync churn

  1. If OneDrive or Dropbox is constantly syncing, the indexer re-indexes churned files endlessly — fix the sync first.
  2. Resolve sync conflicts, pause syncing during work hours, or set large folders to online-only so they are not constantly changing locally.
  3. Exclude cloud sync folders from the index if you rarely search their contents.
  4. The indexer is often innocent here — it is faithfully tracking files that will not sit still.

Fix 7: Disable the Windows Search service

  1. Press Win + R, type services.msc, find Windows Search, click Stop, and set Startup type to Disabled.
  2. Restart and confirm SearchIndexer.exe no longer appears in Task Manager.
  3. Test Start menu and File Explorer searches — both work, with slower content searches as the only trade-off.
  4. Fully reversible: set the service back to Automatic any time. This is the right call when you rarely search file contents and value the CPU silence more.

Fix 8: Check for deeper system issues

  1. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in an admin Terminal — system corruption can manifest as indexer loops.
  2. Check drive health (wmic diskdrive get status) — a failing drive makes indexing crawl and stall.
  3. Ensure at least 15 percent free space on indexed drives.
  4. If the indexer misbehaves on a healthy system with a clean index and narrow scope, a Windows repair install from official media is the final step. Microsoft documents search troubleshooting at Windows support .

Closing

High CPU from search indexing is a “what to do” problem with a clear answer: confirm it is the indexer, give legitimate rebuilds their overnight window, rebuild the index if it is corrupt, shrink the indexed scope, and disable the service if the trade-off favors silence. Most cases resolve at step two or three — the indexer was either finishing real work or needed its database rebuilt. Either way, you now know exactly which one it was.

Frequently asked questions

What should I do first when search indexing uses high CPU?
First, confirm the culprit in Task Manager — look for SearchIndexer.exe or Microsoft Windows Search Indexer using sustained high CPU. Then check how long it has been running: if it started after an update or after adding many files, let it finish overnight while plugged in. Only intervene if the high usage persists beyond 48 hours or returns constantly without new files being added.
How long is too long for search indexing to use high CPU?
A full initial index or post-update rebuild legitimately takes several hours on large drives — sometimes up to a day or two on slow hard drives with lots of files. Beyond 48 hours of plugged-in runtime with no progress, or high CPU that never stops even with no file changes, the indexer is stuck or the index is corrupt, and you should rebuild or limit it.
Will my searches break if I turn off indexing?
No. Windows Search still works without the index — File Explorer searches scan files directly, which is slower for content searches but fine for filenames. Start menu app search is unaffected entirely. Most users who disable indexing notice slower searches only when digging through thousands of documents by content, which is rare.
Why does indexing spike every time I start my laptop?
The indexer catches up on changes made while the laptop was off or asleep — new downloads, modified files, synced cloud content. If the spike lasts minutes, that is normal catch-up. If it lasts the entire session every day, the index is likely corrupt, a synced folder is churning (OneDrive conflicts), or a problem file keeps stalling the crawler.