SearchIndexer.exe is one of those processes you never notice until it goes wrong. When it behaves, it quietly catalogs your files in the background and makes Start menu search instant. When it breaks, it sits at 40–70% CPU for hours, the fans never stop, and your Acer laptop feels like it’s running a marathon while you’re just trying to open a document.

The good news is that indexer problems are almost always fixable without sacrificing search. The indexer is doing something legitimate most of the time — it’s just doing too much of it, or doing it in a loop. Identify which, apply the matching fix, and CPU usage drops back to near zero within a day.

Why this happens

  • The index database is corrupt — a crash or bad shutdown damages the catalog, and the indexer loops trying to rebuild it forever.
  • A problematic file keeps crashing the indexer — a corrupt PDF, PST, or media file can make the indexer retry the same file indefinitely.
  • Too many locations are indexed — indexing entire drives including cloud-synced folders and program directories multiplies the workload.
  • A huge number of files changed recently — a Windows update, a restored backup, or a new cloud sync can dump hundreds of thousands of files into the queue.
  • Indexing runs while you’re working — the “respect power settings” logic fails on some Acer models, so indexing doesn’t pause during active use.
  • Outlook PST/OST files are indexed — large mailbox files are among the heaviest items the indexer processes.
  • The index is simply being built for the first time — after a fresh install or major update, initial indexing legitimately takes hours.

How to fix it

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

Fix 1: Check indexing status first

Don’t change anything until you know what the indexer thinks it’s doing. Windows tells you directly.

Steps:

  1. Go to Settings → Privacy & security → Searching Windows.
  2. Look at the “Indexing status” — it shows whether indexing is complete, in progress, and how many items are indexed.
  3. If it says indexing is complete but CPU is still high, the problem is a loop, not legitimate work — skip to Fix 3.
  4. If it shows hundreds of thousands of items pending, let it run overnight plugged in before judging.
  5. Click “Advanced Search Indexer Settings” to open the classic Indexing Options panel for deeper control.

Fix 2: Reduce indexed locations

Most people index far more than they need. Trimming the list is the single most effective long-term fix.

Steps:

  1. Open Indexing Options (search “Indexing Options” in the Start menu).
  2. Click Modify and review the checked locations.
  3. Uncheck entire drives you don’t search — especially secondary data drives and external drives.
  4. Uncheck cloud sync folders (OneDrive, Dropbox) if you search those through their own apps.
  5. Keep indexed: Start Menu, Users folder (or just your user folder), and Offline Files.
  6. Click OK — the indexer will trim the database, which may take a while but reduces all future work.

Fix 3: Rebuild the index from scratch

When the database is corrupt, no amount of tweaking helps — you need a clean rebuild. This is the fix that resolves most “indexing never finishes” cases.

Steps:

  1. Open Indexing Options → click Advanced.
  2. Under Troubleshooting, click Rebuild.
  3. Confirm the warning — the existing index will be deleted and rebuilt.
  4. Plug in the laptop and leave it alone for several hours (overnight is ideal).
  5. Check Settings → Searching Windows the next day — status should show “Indexing complete.”
  6. Monitor SearchIndexer.exe in Task Manager — it should now sit at 0% when idle.

Fix 4: Exclude Outlook data files

PST and OST files are indexing hogs. If you use Outlook with a large mailbox, this fix alone can halve indexer CPU.

Steps:

  1. Open Indexing Options → Modify.
  2. Expand Outlook in the location tree and uncheck it, or
  3. Go to Advanced → File Types tab and uncheck msg, pst, and ost extensions.
  4. Click OK and let the index update.
  5. You’ll still be able to search email inside Outlook itself — Outlook maintains its own search.

Fix 5: Fix the “indexing while active” problem

On some Acer models, the indexer ignores the “don’t index when I’m busy” logic. Force the issue with a policy setting.

Steps:

  1. Press Win + R, type gpedit.msc (Pro) — or use the registry method below for Home.
  2. Navigate to Computer Configuration → Administrative Templates → Windows Components → Search.
  3. Enable “Disable indexer backoff” — set it to Disabled (counterintuitively, this policy being disabled means backoff stays enabled, which is what throttles indexing during use).
  4. For Home edition: in Registry, go to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Search and ensure no DisableBackoff value is forcing it on.
  5. Restart and observe — indexing should now pause when you’re actively using the laptop.

Fix 6: Find and remove the file that’s crashing the indexer

A single corrupt file can trap the indexer in a retry loop. Event Viewer reveals the culprit.

Steps:

  1. Open Event Viewer → Windows Logs → Application.
  2. Filter for Source “Windows Search Service” errors.
  3. Look for repeated errors naming the same file path — that’s your loop culprit.
  4. Move that file out of an indexed location (or delete it if it’s corrupt and unneeded).
  5. Rebuild the index (Fix 3) to clear the stuck state.

Fix 7: Update Acer drivers and Windows

Acer releases chipset and storage driver updates that fix indexer-adjacent performance issues, and Windows updates regularly patch the search service itself. Check your manufacturer’s support site and Windows Update for the latest.

Steps:

  1. Run Windows Update and install all pending updates, then restart — cumulative updates from the Update Catalog regularly include search-service fixes.
  2. Visit your laptop manufacturer’s support site for your exact model and install the latest chipset and storage drivers.
  3. After updating, check indexing status again — some updates trigger a one-time reindex that resolves corruption.
  4. If CPU is still high after 24 hours of idle plugged-in time, consider the nuclear option below.

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

Only do this if you’ve tried everything else and rarely use Windows search. You’ll lose fast Start menu and Explorer search.

Steps:

  1. Press Win + R, type services.msc, and press Enter.
  2. Find Windows Search in the list and double-click it.
  3. Set Startup type to Disabled and click Stop.
  4. Click OK and restart.
  5. Install a lightweight alternative like Everything (voidtools) for file search if you still need fast searching.

Closing

Windows Search Indexer high CPU on an Acer laptop almost always comes down to a corrupt index, too many indexed locations, or a looping file — and Fixes 2, 3, and 6 cover the vast majority of cases. Once the index is healthy and trimmed, SearchIndexer.exe should be invisible in Task Manager. If you’re seeing similar background-CPU problems from other Windows services, our system interrupts guide covers the next most common culprit, and the 24H2 search indexer deep-dive has version-specific tweaks.

Frequently asked questions

What is Windows Search Indexer and why does it use so much CPU?
Windows Search Indexer (SearchIndexer.exe) builds and maintains the database that powers instant file and Start menu search. It uses CPU when first building the index, after major file changes, or when the index database becomes corrupt and it re-indexes endlessly. On a healthy system, indexing pauses when you are actively using the laptop and resumes when idle.
Can I just disable Windows Search Indexer?
You can, but you will lose fast file search — the Start menu and File Explorer search box become painfully slow because every search scans the disk live. A better approach is to reduce what gets indexed or fix the underlying problem. Only disable the service entirely if you rarely use Windows search and prefer a third-party tool.
Why does indexing never seem to finish on my laptop?
An index that never completes usually means the database is corrupt, a specific file is crashing the indexer in a loop, or new files are being added faster than indexing can process them (common with cloud sync folders). Rebuilding the index from scratch clears corruption, and excluding volatile folders stops the endless catch-up cycle.
Does Search Indexer drain battery?
Yes, sustained high CPU from indexing noticeably increases power draw and heat, which drains the battery faster and spins up the fans. Windows is supposed to throttle indexing on battery power, but a stuck or corrupt index can ignore those limits. Fixing the indexer is one of the most effective battery-life improvements on affected laptops.