Search Indexing High CPU on a Lenovo Laptop? Fix It in Windows 11

You open Task Manager and SearchIndexer.exe — or SearchHost.exe — is sitting at 30%, 60%, even 90% CPU, fans roaring, battery draining. Windows Search is supposed to be a quiet background librarian, building its catalog when you’re idle. When it instead becomes the loudest thing on your Lenovo laptop for hours or days, the index is either corrupt, vastly over-scoped, or stuck in a rebuild loop.

The fix is rarely to nuke the whole service. A properly scoped, freshly rebuilt index uses almost no CPU day-to-day — and you keep instant search. Work through these in order: check what it’s actually doing, scope it down, rebuild it, and only then consider disabling it. For other background CPU hogs, see Antimalware Service Executable high CPU ; for the full speed-up playbook, how to speed up Windows 11 .

Why this happens

• Initial index build: First run (or after a feature update) indexes everything — legitimately CPU-heavy for hours.
• Corrupt index database: A damaged index causes endless retry loops that never complete.
• Over-broad indexing scope: Enhanced mode or added folders make the indexer chew through game libraries, VMs, and archives.
• High-churn folders: Developer build outputs, downloads, or sync folders change constantly, forcing perpetual re-indexing.
• Post-update re-indexing: Feature updates invalidate large parts of the index, triggering a full rebuild.
• Outlook/email indexing: Large PST/OST mail stores add significant indexing load.
• Antivirus fighting the indexer: Real-time scanning of every file the indexer touches doubles the work.

How to fix it

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

Fix 1: Check what the indexer is actually doing

Don’t kill it mid-legitimate-work.

1. Open Task Manager > Processes, find Windows Search / SearchIndexer.exe, and note CPU and disk over several minutes — is it constant or pulsing?
2. Open Settings > Privacy & security > Searching Windows and look at the Indexing Status — it tells you if indexing is “in progress” and how many items are indexed.
3. If status shows indexing in progress with the count climbing, it’s working legitimately — give it idle time (plugged in, overnight) to finish.
4. If the item count is stuck, or status says complete but CPU stays high, the index is likely corrupt — continue to Fix 3.
5. Note the total indexed items: hundreds of thousands on a normal laptop is fine; millions suggests over-scoping (Fix 2).

Fix 2: Scope the index down to what you actually search

The highest-value configuration change.

1. In Settings > Privacy & security > Searching Windows, ensure Find my files is set to Classic, not Enhanced.
2. Click Advanced indexing options (or search “Indexing Options” in Start) > Modify.
3. Uncheck everything you never search: game libraries (Steam, Epic), video/media folders, VM directories, code build outputs (node_modules, bin, obj), cloud-sync archives.
4. Keep checked: Start Menu, Users folders (selectively), and Outlook if you search email.
5. Click OK — the indexer will trim the catalog, and CPU should drop within minutes as the workload shrinks.

Fix 3: Rebuild the index

The cure for corruption.

1. Open Indexing Options (search it in Start) > Advanced > Rebuild.
2. Confirm — Windows deletes the index database and starts over. This is disk- and CPU-heavy for a while: run it overnight with the laptop plugged in.
3. Don’t judge CPU during the rebuild itself — it’s supposed to be busy. Judge the day after it completes.
4. After rebuilding, verify in Settings > Privacy & security > Searching Windows that status shows complete with a sane item count.
5. If CPU is still high post-rebuild with a clean status, something external is churning files (Fix 4) — the index itself is fine.

Fix 4: Exclude high-churn folders

Stop the indexer from re-indexing constantly changing files.

1. In Indexing Options > Modify, uncheck folders with constant writes: Downloads (if you download a lot), build/output directories, log folders, torrent/completed-download folders.
2. If you use OneDrive/Dropbox with large sync sets, consider unchecking the local sync folder if you search it rarely — sync churn is a classic indexer tormentor.
3. For developers: exclude repository target/, build/, .git/ (the .git folder especially — thousands of tiny files), and package caches.
4. Each exclusion reduces the perpetual re-indexing workload immediately.
5. Recheck Task Manager after 10–15 minutes — high-churn exclusions often produce the most dramatic drops.

Fix 5: Troubleshoot with the Search troubleshooter

Let Windows diagnose its own indexer.

1. Open Settings > System > Troubleshoot > Other troubleshooters > run Search and Indexing.
2. Work through its questions honestly (files not appearing, slow search, etc.) — it checks permissions, index integrity, and service state.
3. Apply whatever fixes it recommends and reboot.
4. This catches permission problems (indexer can’t read a folder, retries forever) that manual scoping misses.
5. If the troubleshooter reports it couldn’t fix the issue, continue — the remaining fixes are structural. Additional indexer recovery steps are documented on Microsoft Support .

Fix 6: Limit Outlook and file-type indexing

Trim the two heaviest index contributors.

1. If you use classic Outlook with a huge mailbox: in Indexing Options > Modify, expand Microsoft Outlook and uncheck archive PSTs you never search.
2. In Indexing Options > Advanced > File Types, review the list — uncheck exotic file types you’ll never search by content (or set them to “Index Properties Only” instead of content).
3. For most users, content-indexing documents, email, and text files is enough; indexing the contents of installers, archives, and binaries is pure waste.
4. Also exclude encrypted or compressed archives if listed — the indexer burns CPU trying to peek inside.
5. Apply, then monitor for an hour of normal use.

Fix 7: Disable Windows Search (last resort)

When you’ve proven the indexer is the problem and don’t need fast search.

1. Press Win + R, type services.msc, find Windows Search, double-click it.
2. Set Startup type to Disabled and click Stop.
3. Searches will still work but become slow full-disk crawls — acceptable if you navigate by folder anyway.
4. Alternatively, keep the service but neuter it: Classic mode + minimal folders (Fix 2) gives you fast Start-menu search with near-zero background cost — try this before full disable.
5. To re-enable later, set it back to Automatic (Delayed Start) and reboot.

Closing

SearchIndexer high CPU on a Lenovo laptop is almost always a scoping or corruption problem, not a reason to live without search. Check the indexing status, cut the scope to Classic with sensible folder exclusions, rebuild once cleanly, and exclude high-churn directories. That sequence restores the indexer to what it should be: invisible. Only disable the service if you’ve proven you don’t miss instant search.

Frequently asked questions