Open Task Manager on your Lenovo laptop, sort by CPU, and there’s a good chance you’ll find Microsoft Windows Search Indexer — SearchIndexer.exe — sitting near the top, chewing through 20 to 40 percent of your processor for hours. The fans spin up, the battery drains faster, and everything else feels sluggish while the indexer grinds away.

Here’s the important context: the search indexer isn’t malware, and it isn’t broken by default. Its job is to catalog your files so that Start menu and File Explorer searches return results instantly. After a fresh install or a major Windows update, heavy indexing for a few hours is completely normal. But when it never finishes — when SearchIndexer.exe pins the CPU day after day — something is stuck, looping, or misconfigured. Lenovo laptops add their own wrinkles: scheduled Vantage tasks and bundled utilities can feed the indexer a constant stream of changing files.

This guide follows the same diagnostic sequence a repair technician uses: confirm the indexer is the genuine culprit, find what’s keeping it busy, then fix it in order.

Why this happens

  • A corrupted search index: The index database can be damaged by a crash, a power loss, or a failed update. A corrupt index forces SearchIndexer.exe to re-scan endlessly without ever completing, which looks exactly like permanent high CPU usage.
  • Too many indexed locations: By default, Windows indexes your entire user folder plus the Start menu. Folders full of large, frequently changing files — game libraries, video projects, software repositories — multiply the indexer’s workload enormously.
  • Cloud sync churn: OneDrive, Dropbox, and similar tools constantly touch files. Every touch re-triggers indexing, so a large or stuck cloud sync can keep the indexer busy for days on end.
  • A recent Windows update: Major updates, especially the 24H2 feature update, invalidate the existing index. Windows then rebuilds it from scratch, a process that legitimately takes several hours on a large drive.
  • Outlook email indexing: If Outlook is set to index its data file, a large mailbox with tens of thousands of messages can single-handedly keep SearchIndexer.exe at high CPU.
  • Third-party software loops: Some utilities write and rewrite log files, caches, or temp data inside indexed folders. Each rewrite queues another indexing pass, creating an infinite loop that never settles.
  • Disk or file-system problems: A failing drive or a corrupted file system makes every read slow. The indexer crawls, retries, and stays pegged on CPU while it waits on a disk that can’t keep up.

How to fix it

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

Fix 1: Confirm the indexer is the real culprit

Before changing anything, make sure SearchIndexer.exe is actually the problem and not a lookalike process. Open Task Manager with Ctrl + Shift + Esc, switch to the Details tab, and sort by CPU. Look for SearchIndexer.exe specifically — not SearchHost.exe, which handles the search user interface. Watch it for two or three minutes. Genuine indexer trouble shows sustained CPU above 15–20% with no sign of tapering off. If usage spikes and drops in waves, the indexer is working normally and will finish on its own. The same careful identification applies on Dell machines with indexer trouble .

  1. Press Ctrl + Shift + Esc to open Task Manager.
  2. Go to the Details tab and click the CPU column to sort descending.
  3. Find SearchIndexer.exe and note its CPU percentage over 2–3 minutes.
  4. If it holds above 15% continuously, the indexer is your culprit — continue with Fix 2.

Fix 2: Check whether it’s just unfinished work

The indexer’s own status takes thirty seconds to check. Open the Start menu, type Indexing Options, and open it. The top of the window tells the truth: either “Indexing complete” with a count of indexed items, or an active count still climbing. If it’s actively indexing tens of thousands of items, the high CPU may be legitimate — especially within a day or two of a Windows update. In that case the correct fix is patience, not surgery.

  1. Open Start, type Indexing Options, and press Enter.
  2. Read the status line at the top of the window.
  3. If indexing is in progress with a rising item count, plug the laptop in and give it several hours — preferably overnight.
  4. Only continue to Fix 3 if the status says “Indexing complete” yet CPU usage stays high, or if the item count never moves.

Fix 3: Shrink what Windows indexes

This is the most effective fix for chronic indexer CPU usage. Most Lenovo laptops index the entire user profile, including folders that never need searching. Trimming the list cuts the workload at the source.

  1. In Indexing Options, click Modify.
  2. Expand Users → your username and uncheck heavy folders: Downloads, game libraries, video project folders, and virtual machine folders.
  3. If you use OneDrive with a huge synced library, consider unchecking the OneDrive folder — you can still search it through the OneDrive app or website.
  4. Click OK, then Close, and watch Task Manager for 10–15 minutes to see CPU settle.

Fix 4: Restart the Windows Search service

Sometimes the indexer process itself is wedged rather than the index being wrong. A clean restart of the underlying service clears stuck threads without touching your data or settings. This is safe, takes a minute, and resolves many “indexer won’t calm down” cases.

  1. Press Win + R, type services.msc, and press Enter.
  2. Scroll to Windows Search, right-click it, and choose Restart.
  3. Double-click the service and confirm Startup type is set to Automatic.
  4. Wait five minutes, then check Task Manager again.

Fix 5: Run the Search and Indexing troubleshooter

Windows includes a dedicated troubleshooter that checks index permissions, service state, and common misconfigurations. It’s not magic, but it catches the simple stuff — wrong permissions on the index folder, a stopped dependency service — that manual inspection misses.

  1. Open Settings → System → Troubleshoot → Other troubleshooters.
  2. Find Search and Indexing and click Run.
  3. Check the boxes that match your symptoms (files not appearing, slow search) and follow the prompts.
  4. Apply any fixes it recommends, then restart the laptop.

Fix 6: Rebuild the index from scratch

When the index database itself is corrupted, no amount of restarting or trimming helps — the catalog must be thrown away and rebuilt. This is the heavy hammer, and it works. The rebuild re-catalogs everything in your indexed locations, which takes hours, but afterward the indexer returns to its normal near-zero idle footprint. This is also the standard remedy when indexer trouble appears right after a Windows 11 update .

  1. Open Indexing Options and click Advanced.
  2. Under Troubleshooting, click Rebuild and confirm.
  3. Keep the laptop plugged in and powered on — sleep interrupts the rebuild.
  4. Let it run for several hours or overnight. Check back in Indexing Options; “Indexing complete” with a stable item count means success.
  5. For Microsoft’s own guidance on index settings, see Windows search help .

Fix 7: Rule out disk and file-system damage

If a rebuild doesn’t stick and the indexer spirals again within days, suspect the storage underneath. A failing SSD or corrupted file system makes indexing crawl and retry forever. Run a file-system check first, then Lenovo’s hardware diagnostics to test the drive.

  1. Open Command Prompt as administrator and run chkdsk C: /f. Type Y when asked, then restart to let the scan run.
  2. After rebooting, run sfc /scannow in an elevated Command Prompt to repair protected system files.
  3. Open Lenovo Vantage (or Lenovo Support ) and run the storage hardware scan.
  4. If the drive reports errors or bad health, back up immediately — no indexer fix survives a dying disk.

Closing

SearchIndexer.exe earning high CPU for a few hours after an update is normal; holding your Lenovo laptop’s processor hostage for days is not. In the vast majority of cases, the fix is one of three things: trimming over-broad indexed locations, restarting a wedged service, or rebuilding a corrupted index. Work through them in order, give the rebuild the uninterrupted time it needs, and your fans — and your battery — will thank you.

Frequently asked questions

Why is SearchIndexer.exe using so much CPU on my Lenovo laptop?
The indexer catalogs files so Start menu searches return instantly. It spikes after updates, large file changes, or cloud syncs. If it never settles, the index is usually corrupted, the indexed locations include huge churning folders, or a program keeps rewriting files. Rebuilding the index and trimming indexed locations resolves most persistent cases within a few hours.
Is it safe to disable Windows Search to stop the high CPU usage?
Disabling the Windows Search service stops indexing but also breaks Start menu search, File Explorer search, and Outlook search. It is a valid last resort, but rebuilding the index or shrinking indexed locations usually fixes the CPU problem while keeping search working. Only disable the service if every repair attempt fails and you rarely use Windows search.
How long does rebuilding the search index take?
On a typical Lenovo laptop with a 512GB SSD and a normal document library, a rebuild takes one to four hours. Large photo collections, game libraries, or multi-terabyte drives can push it to eight hours or more. Keep the laptop plugged in, avoid heavy file operations during the rebuild, and let it run overnight if the drive is nearly full.
Will limiting indexed locations break Start menu search?
No. The Start menu and core system locations stay indexed no matter what you exclude. Removing folders like Downloads, game libraries, or cloud-synced archives only stops those specific folders from appearing in search results. Most users never notice the difference, but the indexer does — its workload drops dramatically once the churn-heavy folders are excluded.