SearchIndexer.exe misbehaving on Windows 11 is one of the most common background-CPU complaints, and it’s frustrating because the process is supposed to be invisible. When it works, you get instant search and never think about it. When it breaks, it’s a permanent 20–60% CPU tax with hot fans and draining battery — for a feature you might not even use daily.

This is the definitive version of the fix. It covers everything: the quick checks, the rebuild, the scope surgery, and the loop-busting forensics for stubborn cases. Work it in order.

Why this happens

  • Corrupt index database — the most common cause of never-ending indexing loops.
  • Overly broad indexing scope — entire drives, cloud folders, and program directories all indexed by default.
  • OneDrive/cloud sync churn — constant file changes generating endless indexing work.
  • A single file crashing the indexer in a loop — corrupt documents or mailbox files retried forever.
  • Post-update full reindex — feature updates invalidate the index and trigger a complete rebuild.
  • Outlook data files — large PST/OST files are extremely expensive to index.
  • Broken “pause while active” behavior — the indexer failing to back off during user activity.

How to fix it

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

Fix 1: Read the indexing status

Windows tells you exactly what the indexer is doing — start there.

Steps:

  1. Go to Settings → Privacy & security → Searching Windows.
  2. Check “Indexing status”: complete vs. in progress, and the item count.
  3. If it shows complete but CPU is high → you have a loop (go to Fix 4).
  4. If it shows hundreds of thousands pending → it’s legitimate catch-up work; give it an idle night plugged in.
  5. Open the classic Indexing Options (search it in Start) for the controls used in the next fixes.

Fix 2: Trim the indexing scope aggressively

The default scope indexes far more than anyone needs. This is the permanent fix for “indexer always busy.”

Steps:

  1. In Indexing Options, click Modify.
  2. Uncheck: entire secondary drives, external drives, OneDrive/cloud folders (unless you search them constantly), Program Files, Windows folder.
  3. Keep checked: Start Menu, your Users folder.
  4. Click OK and let the index rebuild with the smaller scope — future indexing work drops dramatically.
  5. In Advanced → File Types, uncheck extensions you never search inside (e.g., .log, .tmp, executables).

Fix 3: Rebuild the index cleanly

When corruption is suspected — and it should be, if indexing never completes — rebuild from zero.

Steps:

  1. Indexing Options → Advanced → under Troubleshooting, click Rebuild.
  2. Confirm — the old index is deleted immediately.
  3. Plug in the laptop and leave it idle for several hours (overnight is best).
  4. The next day, verify Settings → Searching Windows shows “Indexing complete.”
  5. Check Task Manager — SearchIndexer.exe should sit at 0% when idle.

Fix 4: Hunt down the looping file

If a rebuild didn’t help, a specific file is crashing the indexer repeatedly. Find it in Event Viewer.

Steps:

  1. Open Event Viewer → Windows Logs → Application.
  2. Filter by Source: Windows Search Service, Level: Error/Warning.
  3. Look for the same file path appearing repeatedly — that’s the loop culprit.
  4. Move that file out of indexed locations, repair it, or delete it if it’s corrupt junk.
  5. Rebuild the index (Fix 3) once more to clear the stuck state.

Fix 5: Exclude Outlook and heavy file types

Mailbox files are indexer kryptonite. Exclude them.

Steps:

  1. In Indexing Options → Modify, expand and uncheck Microsoft Outlook (or Outlook-specific locations).
  2. Alternatively: Advanced → File Types → uncheck pst, ost, msg.
  3. Outlook’s own internal search continues to work — it doesn’t depend on the Windows index.
  4. Also uncheck file types for content you never search: archives (.zip, .7z) if you don’t need content search inside them.
  5. Let the index update and observe CPU over the next day.

Fix 6: Tame OneDrive’s indexing churn

OneDrive and the indexer are frequent partners in crime.

Steps:

  1. In Indexing Options → Modify, uncheck your OneDrive folder entirely.
  2. In OneDrive Settings, use Selective sync to sync only folders you actually need locally.
  3. For folders you browse but rarely search, right-click → “Free up space” (online-only) so they generate less local churn.
  4. If you don’t use OneDrive, unlink it completely — it’s pure overhead then.
  5. Monitor SearchIndexer.exe for a day — OneDrive exclusions fix a large share of persistent cases.

Fix 7: Force proper backoff behavior

Make the indexer respect your activity and power state.

Steps:

  1. Win + R → gpedit.msc (Pro) → Computer Configuration → Administrative Templates → Windows Components → Search.
  2. Verify “Disable indexer backoff” is set to Disabled or Not Configured (backoff should be enabled).
  3. Enable “Prevent indexing when running on battery power to save energy” if available.
  4. On Home edition, check HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Search for rogue values and remove them.
  5. Restart and confirm indexing now pauses while you work. For Acer-specific indexer quirks, see our Acer indexer guide ; for the 24H2-specific variant, the 24H2 indexer deep-dive .

Fix 8: Disable Windows Search (last resort)

If you’ve done everything and the indexer still won’t behave, and you rarely use Windows search:

Steps:

  1. Win + R → services.msc → find Windows Search.
  2. Set Startup type to Disabled, click Stop, then OK.
  3. Restart — Start menu search will be slower (live disk scanning) but functional.
  4. Install Everything (voidtools) for instant file search as a replacement.
  5. Revisit this decision after major Windows updates — Microsoft does fix indexer bugs over time.

Closing

A healthy Windows Search indexer is invisible; a broken one is unmistakable. The sequence that fixes nearly all cases: trim the scope (Fix 2), rebuild clean (Fix 3), and exclude the churn sources (Fixes 5–6). Do those three and SearchIndexer.exe goes back to 0% at idle permanently. Disabling search is always available as the escape hatch, but it’s rarely necessary once the scope is sane. For related background-CPU issues, Microsoft’s Windows support hub documents the search service architecture.

Frequently asked questions

How long should Windows 11 indexing take to complete?
Initial indexing on a typical laptop with 100,000–300,000 files takes 2–8 hours of idle plugged-in time. After that, incremental indexing of daily changes should be invisible — seconds of CPU here and there. If indexing hasn’t completed after several days of normal use, or CPU stays high with ‘indexing complete’ showing, something is wrong and needs the fixes in this guide.
Does disabling Windows Search break anything?
Disabling the Windows Search service removes fast indexed search from the Start menu and File Explorer — searches still work but scan the disk live, which is slow on large drives. It doesn’t break Windows itself. Most users are better off fixing the indexer than disabling it, since instant search is genuinely useful once the indexer behaves.
Why does SearchIndexer use CPU when I'm not searching for anything?
The indexer works proactively, not on demand — it catalogs files as they change so searches are instant later. Normal triggers include new downloads, cloud sync activity, email arrival, and software installations. It should pause when you’re actively using the PC and throttle on battery. Constant high CPU means it’s stuck, looping, or indexing far too much.
Can OneDrive cause Search Indexer high CPU?
Yes, very commonly. OneDrive constantly creates, modifies, and syncs placeholder files, and each change queues indexer work. Large OneDrive libraries with Files On-Demand generate a steady stream of indexing events. Excluding OneDrive folders from the index (or limiting what’s synced) is one of the most effective fixes for persistent indexer CPU.