After the 24H2 update, a lot of users meet SearchIndexer.exe the hard way: fans spinning, CPU pinned, Task Manager showing the indexer grinding away for hours — or days. Some of that is legitimate: 24H2 invalidates large parts of the old index and rebuilds it. But when the indexer never settles, or when the update reset your scope to Enhanced mode, you get a background process consuming CPU like it’s rendering video.

This guide is the 24H2-specific playbook: verify the update-related triggers first, then scope, rebuild, and exclude — keeping fast search intact. (For the Lenovo-focused version with brand-specific notes, that’s a separate guide; the mechanics here apply to every 24H2 machine.) For other background CPU consumers, see Antimalware Service Executable high CPU ; for overall speed, speeding up a slow Windows 11 laptop .

Why this happens

  • 24H2 invalidated the old index: Feature updates force large-scale re-indexing — heavy but temporary.
  • Scope reset to Enhanced: The update can flip indexing back to whole-drive Enhanced mode.
  • Search highlights re-enabled: The Bing-driven search-box content adds indexer/UI workload.
  • Corrupt index from the update: Interrupted or partial indexing during the upgrade leaves a damaged database.
  • High-churn folders: Sync folders, build outputs, and download directories force endless re-indexing.
  • Outlook data files: Large OST/PST stores add major indexing load after profile migrations.
  • Defender double-scanning: Real-time protection scanning every file the indexer touches multiplies the cost.

How to fix it

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

Fix 1: Check indexing status and give legitimate work time

Don’t interrupt a valid rebuild.

  1. Open Settings > Privacy & security > Searching Windows and read the Indexing Status — in-progress with a climbing count means real work.
  2. After a 24H2 upgrade, allow one overnight plugged-in session for the rebuild — judging it mid-rebuild leads to wrong conclusions.
  3. Open Task Manager and note whether SearchIndexer.exe CPU is constant or pulsing; constant + frozen item count = stuck.
  4. If status shows complete but CPU stays high, or status is stuck for 48+ hours, it’s not legitimate work — continue.
  5. Also check Update history — a very recent 24H2 install explains everything; patience is the fix.

Fix 2: Reset scope to Classic and trim folders

Undo the update’s scope reset.

  1. In Settings > Privacy & security > Searching Windows, set Find my files to Classic (the update may have set Enhanced).
  2. Click Advanced indexing options > Modify and uncheck: game libraries, media folders, VM directories, build outputs, archives, and cloud-sync folders you rarely search.
  3. Keep: Start Menu, your Documents (selectively), and Outlook if you search mail.
  4. Turn off Show search highlights on the Searching Windows page — it removes the Bing content workload from the search UI.
  5. The indexer should visibly calm within 15–30 minutes as its queue shrinks.

Fix 3: Rebuild the index cleanly

The corruption cure.

  1. Search “Indexing Options” in Start, open it, click Advanced > Rebuild, and confirm.
  2. Run it overnight, plugged in — the rebuild is CPU- and disk-intensive by nature.
  3. The next day, verify status shows complete with a reasonable item count in Settings > Privacy & security > Searching Windows.
  4. Monitor SearchIndexer.exe during normal use for a day — it should be near zero when idle.
  5. If high CPU returns within days of a clean rebuild, an external churn source is the cause (Fix 4), not the index.

Fix 4: Exclude high-churn and heavy locations

Stop the perpetual re-indexing loop.

  1. In Indexing Options > Modify, uncheck: Downloads (heavy downloaders), torrent/completed folders, OneDrive/Dropbox sync roots you rarely search, and developer directories (node_modules, target, .git, package caches).
  2. For Outlook users: in Modify, expand Microsoft Outlook and uncheck archive PSTs; keep only the live mailbox if you search mail.
  3. In Advanced > File Types, set rarely-searched types (installers, archives, binaries) to Index Properties Only instead of full content.
  4. Each exclusion takes effect quickly — watch Task Manager for the drop.
  5. This fix has the highest long-term value: it prevents the problem from recurring as your file churn continues.

Fix 5: Run the Search and Indexing troubleshooter

Catch permission and service issues.

  1. Settings > System > Troubleshoot > Other troubleshooters > Search and Indexing > Run.
  2. Answer its prompts (slow search, missing results) — it checks service state, permissions, and index integrity.
  3. Apply recommended fixes and reboot.
  4. Permission problems are sneaky: the indexer retrying an unreadable folder looks identical to corruption in Task Manager.
  5. If it can’t fix the issue, continue — the remaining steps are structural. Further indexer recovery guidance is available on Microsoft Support .

Fix 6: Calm SearchHost.exe (the UI side)

When the front-end, not the indexer, is the hog.

  1. If SearchHost.exe (not SearchIndexer) is the CPU consumer, the problem is the search UI: turn off Search highlights (Settings > Privacy & security > Search permissions).
  2. In Search permissions, also review SafeSearch and cloud-search toggles — disabling Microsoft account and Work/school account cloud search reduces UI workload if you don’t use them.
  3. Test the search box after each change — UI-side fixes show results immediately.
  4. A corrupted search UI cache can also cause this: rebuild the index (Fix 3) covers that too.
  5. Don’t confuse the two processes — fixing the indexer won’t help a SearchHost problem and vice versa.

Fix 7: Disable the Windows Search service (last resort)

Only after proving scope/rebuild can’t fix it.

  1. Press Win + R, type services.msc, find Windows Search, set Startup type to Disabled, click Stop.
  2. Accept the tradeoff: searches become slow full-disk crawls.
  3. Prefer the middle ground first: Classic + minimal folders (Fix 2) + disabled highlights gives near-zero background CPU with fast Start-menu search intact.
  4. To re-enable: set to Automatic (Delayed Start) and reboot, then rebuild once.
  5. Revisit after the next cumulative update — Microsoft occasionally ships indexer fixes worth re-testing.

Closing

In 24H2, search-indexer CPU spikes are usually the update’s doing: a forced rebuild, a scope reset to Enhanced, or a corrupted index from the upgrade. Give the legitimate rebuild one night, then reset to Classic scope, trim high-churn folders, and rebuild cleanly. That restores the indexer to its proper state — invisible — while keeping the instant search that makes Windows usable. Full disable is the last resort, not the starting point.

Frequently asked questions

Why is the search indexer using high CPU in Windows 11 24H2 specifically?
The 24H2 update invalidates much of the existing search index, forcing a full rebuild — legitimately CPU-heavy for hours afterward. 24H2 also reset some users’ indexing scope back to Enhanced mode and re-enabled search highlights, both of which increase indexer workload. Beyond the update window, the usual causes apply: corrupt index databases, over-broad folder scope, and high-churn directories keeping the indexer perpetually busy.
What's the difference between SearchIndexer.exe and SearchHost.exe?
SearchIndexer.exe is the background service that builds and maintains the file index — it’s the one that runs for hours. SearchHost.exe is the front-end process powering the search UI (the search box and results window); it spikes briefly when you actually search. High CPU complaints are almost always about SearchIndexer.exe. If SearchHost.exe itself is the hog, the issue is usually the search UI (highlights, web integration) rather than the index.
How do I know if my search index is corrupt?
Telltale signs: indexing status stuck ‘in progress’ for days with the item count frozen, SearchIndexer.exe at constant high CPU despite status showing ‘complete’, or searches returning no results for files that clearly exist. The definitive test is rebuilding the index — if CPU normalizes after a clean rebuild completes, corruption was the cause. The Settings page (Privacy & security > Searching Windows) shows the current indexing status.
Will disabling the search indexer break Windows search?
It degrades it rather than breaking it. With the Windows Search service disabled, Start-menu and File Explorer searches still work but become slow, unindexed crawls of the disk. Most users find that unacceptable for daily use. The better path — scoping to Classic mode with sensible folders, then rebuilding — keeps instant search while eliminating the CPU problem. Disable only as a last resort.