Search indexing high CPU is one of those problems where the fix you need depends entirely on why it’s happening — and there are at least six different whys. That’s why this guide is deliberately sequential: each step either fixes the issue or rules out a cause, so you never waste time on repairs that don’t apply to your machine. No registry hacks, no sketchy “optimizer” tools — just the built-in controls, used in the right order.

Set aside about half an hour for the diagnostic steps. The rebuild at the end needs hours of unattended time, but everything before it is quick. Let’s go.

Why this happens

  • A corrupted index catalog: The search database gets damaged by crashes or failed updates, and the indexer re-scans forever without finishing.
  • Too much indexed territory: Default settings index the whole user profile, including folders whose constant churn buries the indexer.
  • Cloud sync churn: Every file touched by OneDrive or Dropbox gets re-indexed; a big sync means days of indexer labor.
  • Legitimate post-update rebuilds: Feature updates invalidate the index, triggering hours of genuine catch-up work.
  • Application write loops: Backup tools, utilities, or games rewriting files in indexed folders create infinite re-index queues.
  • Outlook mailbox indexing: Very large mail archives can dominate the indexer’s time single-handedly.
  • Failing or full storage: Slow or nearly-full drives stretch indexing from hours into permanence.

How to fix it

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

Fix 1: Identify the exact process

Precision matters. Press Ctrl + Shift + Esc, open the Details tab, sort by CPU, and find SearchIndexer.exe. Note its sustained percentage over 3–5 minutes. While you’re there, rule out lookalikes: SearchHost.exe is the search interface (different fixes), and TiWorker.exe is Windows Update servicing (different problem entirely). Write down the number — you’ll compare against it after each fix.

  1. Open Task Manager → Details → sort by CPU.
  2. Locate SearchIndexer.exe; record its sustained percentage over several minutes.
  3. Confirm it’s not SearchHost.exe or a servicing process.
  4. Sustained 15%+ = proceed; brief spikes = normal, stop here.

Fix 2: Read the indexer’s status

Open Indexing Options (type it in Start). The top line is the indexer’s own report card: “Indexing complete” with an item count, or an active count still climbing. A climbing count within 48 hours of an update means legitimate work — plug in, wait, done. A stuck count (same number for hours) or “complete” alongside high CPU means the catalog is lying, and you’re headed for a rebuild.

  1. Start → Indexing Options → Enter.
  2. Read the status line and item count; note the count.
  3. Wait 30 minutes; check whether the count advanced.
  4. Advancing = working; stuck or “complete”-but-busy = continue.

Fix 3: Narrow the indexed locations

In Indexing Options, click Modify and uncheck every high-churn folder you don’t search: Downloads, game folders, video projects, VMs, and big cloud-synced folders. This is the step that fixes the most machines, because it attacks the workload rather than the worker. Click OK and give Task Manager 10–15 minutes to show the difference.

  1. Indexing Options → Modify.
  2. Uncheck Downloads, games, videos, VMs, cloud-synced folders.
  3. Keep Documents, Start menu, email checked.
  4. OK → Close; observe CPU for 10–15 minutes. Brand-specific churn (HP utilities, for instance) is covered in the HP indexing guide .

Fix 4: Restart the Windows Search service

A wedged process sometimes only needs restarting. Win + R, type services.msc, find Windows Search, right-click → Restart, and verify Startup type is Automatic. Wait five minutes and compare against the number you recorded in Fix 1. If CPU dropped and stays down, you were dealing with stuck threads, not a broken index.

  1. Win + R → services.msc.
  2. Right-click Windows Search → Restart.
  3. Confirm Startup type: Automatic.
  4. Re-observe for 5+ minutes; compare with your Fix 1 baseline.

Fix 5: Run the Search and Indexing troubleshooter

Settings → System → Troubleshoot → Other troubleshooters → Search and Indexing → Run. It checks service state, index permissions, and common misconfigurations, and it catches things manual inspection misses — like the index folder having wrong permissions after a restore or migration. Apply whatever it recommends.

  1. Settings → System → Troubleshoot → Other troubleshooters.
  2. Run Search and Indexing; describe your symptoms when asked.
  3. Apply recommended fixes.
  4. Restart the laptop afterward.

Fix 6: Rebuild the index from scratch

If the catalog is corrupt, nothing short of rebuilding fixes it. Indexing Options → Advanced → Rebuild, confirm, and let it run — plugged in, sleep disabled — for several hours or overnight. When Indexing Options reports “Indexing complete” with a stable count and Task Manager shows the indexer idle, you’ve won. The post-update indexer guide covers this same rebuild in the update-triggered scenario.

  1. Indexing Options → Advanced → Rebuild → confirm.
  2. Plug in; set Settings → Power to prevent sleep.
  3. Wait hours/overnight; don’t run heavy file operations meanwhile.
  4. Confirm “Indexing complete,” stable count, calm CPU. Reference: Windows support .

Fix 7: Investigate recurrence

A rebuild that doesn’t stick means the environment is hostile: run chkdsk C: /f (reboot to complete) and sfc /scannow elevated to check the file system, hunt for applications rewriting files in indexed locations (backup tools and game launchers are usual suspects), and run your manufacturer’s drive diagnostics. Fix the underlying cause — storage or software — and the indexer stays calm.

  1. Elevated prompt: chkdsk C: /f → reboot; then sfc /scannow.
  2. Look for apps with constant disk writes in Task Manager during idle.
  3. Run manufacturer drive diagnostics.
  4. Address what you find; re-trim indexed locations afterward.

Closing

Search indexing high CPU surrenders to method: identify the process, read its status, shrink its territory, restart its service, run the troubleshooter, rebuild the catalog, and investigate recurrence. Each step is small; together they’re the complete repair. Follow them in order and you’ll spend your time on the step that actually fixes your machine instead of all of them at random.

Frequently asked questions

How do I know the high CPU is really from search indexing?
Open Task Manager’s Details tab and sort by CPU. The culprit process is SearchIndexer.exe, described as Microsoft Windows Search Indexer. Watch it for several minutes: genuine indexer trouble shows sustained usage, typically above 15 percent, that doesn’t taper off. Brief spikes during file copies are normal. Confirm the exact process name before changing anything, since SearchHost.exe is a different component.
What is the very first thing I should try?
Check Indexing Options from the Start menu and read the status line. If it shows indexing actively in progress with a climbing item count — especially within a day or two of a Windows update — the correct action is patience, not repair. Plug in and give it several hours. Only start the repair steps if the status says complete while CPU stays high, or if the count never advances.
Which folders should I remove from indexing?
Remove folders that change constantly but that you never search: Downloads, game installation folders, video project directories, virtual machine folders, and large cloud-synced folders like OneDrive. Keep Documents, the Start menu, and your email indexed. This single change eliminates most chronic indexer CPU problems because it removes the churn the indexer was drowning in.
Rebuilding didn't help — what now?
If a full rebuild completes and CPU spikes return within days, the problem is underneath the index: either something keeps corrupting it or the disk can’t keep up. Run chkdsk and SFC to check file-system health, look for software that constantly rewrites files in indexed locations, and test the drive with your manufacturer’s diagnostics. Persistent recurrence after a clean rebuild always points to storage or a looping application.