Windows Search keeps an index of your files so Start-menu searches return instantly — but building and maintaining that index costs CPU. When SearchIndexer.exe sits at 20–60% for hours, or spikes every time you create files, the index is either corrupted, far too broad, or fighting with another process over the same files. The laptop gets hot, loud, and slow while search itself barely works.

There is a clear best-practice order for fixing this: first shrink what gets indexed (the biggest lever), then rebuild the index cleanly, then schedule indexing politely. Done in that order, most systems go from constant indexing churn to near-silence within a day.

Why this happens

  • Index scope too broad: Indexing entire drives, program folders, and archives multiplies work enormously.
  • Corrupted index database: Damage causes endless re-crawling instead of incremental updates.
  • Huge file collections: 100k+ files (photo libraries, code repos, VMs) keep the indexer permanently busy.
  • Files changing constantly: Developer builds, downloads, and sync tools trigger re-indexing in loops.
  • Indexing encrypted or offline files: The indexer struggles with content it cannot read, retrying wastefully.
  • Conflicting antivirus scanning: Defender scanning every file the indexer touches doubles the CPU cost.
  • Post-update re-indexing backlog: Feature updates invalidate the index, triggering a full rebuild.

How to fix it

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

This is the highest-leverage change. Most users search documents, not program files — yet default indexing often covers far more. Narrowing the scope can cut indexing CPU by 80% or more permanently.

  1. Go to Settings > Privacy & security > Searching Windows > Advanced indexing options > Modify.
  2. Untick entire-drive entries and program/data folders you never search.
  3. Keep only your user folders with real documents (Documents, specific project folders).
  4. Click OK; the indexer will trim its workload over the next hour.

Fix 2: Exclude high-churn folders explicitly

Folders whose contents change constantly — build outputs, downloads in progress, VM disks, sync folders — force endless re-indexing. Excluding them breaks the loop while keeping search working for everything else.

  1. In the same Modify dialog, expand your user folders.
  2. Untick Downloads subfolders with constant activity, code build-output folders, and VM directories.
  3. Also exclude cloud-sync working folders if a sync tool churns them.
  4. Verify search still finds your documents afterward — it will.

Fix 3: Rebuild the index cleanly

After scoping, rebuild so the database matches the new scope without carrying forward corruption. Expect one heavy crawl, then quiet — the heavy period is normal and finite.

  1. In Advanced indexing options, click Advanced > Rebuild and confirm.
  2. Let it run: 1–3 hours depending on file count; CPU will be high during this one pass.
  3. Do not interrupt it — interruptions are what corrupt indexes.
  4. After completion, SearchIndexer.exe should idle near 0% between file changes.

Fix 4: Respect the post-update rebuild window

After Windows feature updates, the indexer legitimately rebuilds because file versions changed. This looks identical to a broken indexer but resolves itself — the mistake is ‘fixing’ it mid-rebuild and corrupting the new index.

  1. Check Settings > Searching Windows for indexing status after any feature update.
  2. If it shows active indexing with file counts climbing, leave it alone for a few hours.
  3. Plug in AC power and let it finish uninterrupted overnight if needed.
  4. Only apply Fixes 1–3 if heavy indexing persists days after the update.

Fix 5: Calm antivirus interference

Defender’s real-time scanner inspecting every file the indexer reads is a CPU multiplier. You do not disable protection — you just stop the two from amplifying each other on folders that do not need both.

  1. Ensure excluded-from-index folders with trusted content also have Defender folder exclusions (Windows Security > Exclusions).
  2. Never exclude your indexed Documents from Defender — only unindexed, trusted bulk folders.
  3. After adding exclusions, restart the Windows Search service.
  4. Compare SearchIndexer CPU during a manual re-crawl.

Fix 6: Schedule indexing for idle hours

Windows lets indexing run whenever it wants by default. Constraining it to idle time keeps it from competing with your work — especially valuable on laptops where every CPU cycle affects battery and heat.

  1. In Indexing Options > Advanced, check your power settings for the indexer service.
  2. Use Task Scheduler (Microsoft > Windows > Windows Search) to add idle conditions if needed.
  3. In Settings > System > Power & battery, keep the laptop from sleeping during the first rebuild.
  4. Pair with startup trimming so boot-time file churn does not trigger indexing storms.

Fix 7: Let Storage Sense reduce indexer churn

A cluttered drive gives the indexer more to chew on: temp files, stale downloads, and gigabytes of installer debris that change constantly. Storage Sense automatically clears this debris on a schedule, which quietly reduces the indexer’s ongoing workload. Combined with freeing up disk space manually once, it keeps the file set the indexer watches lean and stable.

  1. Go to Settings > System > Storage > Storage Sense and turn it on.
  2. Configure it to run monthly: clean temp files, Recycle Bin contents older than 30 days, and Downloads you opt in.
  3. Run it once manually with ‘Clean now’ to clear the existing backlog.
  4. Over the following week, watch SearchIndexer CPU trend downward as churn decreases.
  5. Keep at least 15% of C: free permanently — full drives make every indexer pass harder.

Closing

Search indexing high CPU is a scope problem first and a corruption problem second: index only what you search, exclude churn-heavy folders, rebuild once cleanly, and let post-update rebuilds finish undisturbed. That sequence takes Windows Search from a constant background burden to what it should be — an invisible service that answers instantly and otherwise stays silent. Revisit your indexed locations every few months — software installs love to add themselves back into the index scope, and a quick quarterly check keeps the workload lean permanently.

Frequently asked questions

How long should initial indexing take?
For a typical laptop with 50k–100k indexed files, the first full crawl takes 1–3 hours of elevated CPU, ideally run overnight on AC power. It becomes a problem only when heavy indexing persists for days with the file count never stabilizing — that signals corruption or a churn loop, not normal first-time indexing.
Will narrowing the index break Start menu app search?
No. Start menu app and settings search does not depend on the file index locations you configure — apps are found through a separate mechanism. Narrowing file indexing only affects file-content search results. Your programs, settings, and Store apps keep appearing in search exactly as before.
Should I just disable Windows Search entirely?
You can, but you lose instant file search and Start-menu file results degrade badly. The scoped-index approach in this guide gives you 90% of the CPU savings while keeping search fully functional. Full disable is only worth considering on very old hardware where even a minimal index causes pain — and even then, try scoping first.
Why does indexing restart every time I boot?
Usually because something is churning files at startup — cloud sync tools, updaters, or apps writing to indexed folders — so the indexer always has ‘new’ work at boot. Trimming startup programs and excluding churn-heavy folders from the index breaks this cycle. If indexing restarts with zero file changes, the index database itself is likely corrupt and needs the Fix 3 rebuild.