The Windows Search indexer is supposed to be invisible: it quietly catalogs your files in the background so searches return instantly. On many laptops, though, it’s anything but invisible — SearchIndexer.exe chewing CPU, the disk light never resting, the fan spinning during what should be idle time. After Windows updates, the indexer often decides to rebuild its entire catalog, turning your laptop into a space heater for hours. And when the index corrupts, the process can loop forever.

Disabling search indexing is a legitimate performance trade-off, not a hack. You give up instant file-content search across your whole drive; in exchange, the indexer never consumes another CPU cycle. For users who rarely search file contents — who find apps via the Start menu and navigate to files manually — it’s pure win. And there’s a middle path: keep indexing but restrict it to the folders you actually search, cutting 90% of the workload while keeping fast search where it matters.

This guide covers all three options — full disable, location limiting, and the nuclear service-level disable — so you can pick the level that fits how you actually use your laptop.

Why this happens

  • Post-update full rebuilds: Feature updates invalidate the index, triggering hours-long rebuilds that saturate CPU and disk.
  • Too many indexed locations: Default indexing includes broad locations; huge folders (game libraries, photo archives, code repos) multiply the work enormously.
  • Corrupted index loops: Damaged index data causes the indexer to retry failed operations indefinitely.
  • Constant file churn: Folders with frequently-changing files (downloads, sync folders, development directories) keep the indexer perpetually busy.
  • Slow HDD amplifies everything: On spinning hard drives, indexing I/O competes directly with everything else you do.
  • SearchUI coupling: The indexer feeds the search UI process, so indexer problems often manifest as SearchHost/Cortana high CPU too.
  • OneDrive synced folders: Cloud-synced folders with constant changes generate endless re-indexing.

How to fix it

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

Fix 1: Confirm the indexer is your problem

Verify before disabling — the fix should match the diagnosis.

  1. Open Task Manager (Ctrl + Shift + Esc) and check for Microsoft Windows Search Indexer (SearchIndexer.exe) with sustained CPU or disk usage.
  2. Open Control Panel > Indexing Options and check the status — if it says “Indexing in progress” with tens of thousands of items, it’s mid-rebuild.
  3. If it’s a one-time rebuild after an update, consider letting it finish (a few hours on AC power) rather than disabling.
  4. If it’s constant with no end in sight, or recurs frequently, proceed.

Fix 2: Limit indexed locations (the smart middle ground)

Keep fast search where you need it; stop indexing everything else.

  1. Open Control Panel > Indexing Options and click Modify.
  2. Uncheck locations you never search: game libraries, photo/video archives, program files, cloud sync folders you don’t search.
  3. Keep checked only what you actually search — typically Users > your Documents and Start Menu.
  4. Click OK. The indexer trims its workload immediately.
  5. This preserves instant search for your real files while eliminating most of the background cost.

Further reduce the indexer’s workload by file type.

  1. In Indexing Options, click Advanced, then the File Types tab.
  2. Uncheck extensions you never need to search by content: video formats, archives, executables, disk images.
  3. For types you search by name only, select the extension and choose Index Properties Only instead of content indexing.
  4. Click OK and let the index update.

Fix 4: Pause indexing during heavy work

A temporary measure for when you need every resource right now.

  1. Open services.msc, find Windows Search.
  2. Right-click and choose Stop — indexing halts immediately, and searches fall back to slow live scanning.
  3. When your heavy work is done, right-click and Start it again.
  4. This is a good diagnostic too: if stopping the service fixes your CPU/disk problem, you’ve confirmed the indexer as the cause.

Fix 5: Disable the Windows Search service (full disable)

The complete off switch. Searches still work, just slower.

  1. Open services.msc and double-click Windows Search.
  2. Set Startup type to Disabled and click Stop.
  3. Click OK. The indexer will never run again until you re-enable it.
  4. Test Start menu and Explorer search — they work, but file searches take longer.
  5. To re-enable later: set Startup type back to Automatic (Delayed Start) and start the service.

Note: some Microsoft Store app searches rely on the index — if a Store app’s internal search breaks, that’s why. Desktop search is unaffected.

Fix 6: Fix a corrupted index before giving up

If you want indexing but it’s misbehaving, rebuild rather than disable.

  1. Open Control Panel > Indexing Options > Advanced > Rebuild.
  2. Let the rebuild complete fully on AC power — interrupting it just restarts the pain.
  3. If corruption recurs, check disk health (chkdsk C: /f) — recurring index corruption can signal drive problems.
  4. After a clean rebuild with limited locations (Fix 2), most indexer problems stay fixed.

Related: if SearchHost.exe (not the indexer) is your CPU hog, see our Cortana high CPU step-by-step fix .

Fix 7: Reduce file churn in indexed folders

Stop the indexer from re-indexing the same files endlessly.

  1. Move constantly-changing folders (downloads, temp files, active sync folders) out of indexed locations.
  2. In OneDrive/Dropbox settings, consider whether synced folders need indexing — usually they don’t.
  3. Exclude development directories and build outputs, which churn thousands of files.
  4. Fewer changes means a quieter indexer even if you keep it enabled.

Our guide on disabling background apps covers other background resource consumers. Microsoft’s Windows support page documents the indexing options for your Windows version.

Closing

Search indexing is a background luxury, not a necessity — and on laptops where it’s misbehaving, disabling it (or just limiting its scope) is a rational trade. Start with location limiting; go full disable if the indexer proves incorrigible. Either way it’s reversible in seconds, so there’s no risk in trying.

Frequently asked questions

What happens if I disable Windows Search indexing?
Start menu and File Explorer searches still work, but they become slower because Windows scans files live instead of consulting a pre-built index. Searches of large drives can take significantly longer. Everything else — apps, booting, browsing — is unaffected, and many users never notice the difference in daily use.
Will disabling indexing break Cortana or the search box?
No. The search box keeps working for apps, settings, and files — it just searches without the index, which is slower for file content searches. If you’ve already tamed Cortana’s CPU usage with our other guides, disabling indexing is a separate, independent change.
Is it better to disable indexing or just limit indexed locations?
Limiting locations is the smarter middle ground for most users: keep the index but restrict it to folders you actually search (like Documents), excluding huge folders like game libraries or archives. Full disabling is best when the indexer itself is corrupted or when every CPU cycle matters, like on very old hardware.
Can I re-enable indexing later?
Yes, instantly and without consequences. Re-enabling the Windows Search service restores indexing, and Windows rebuilds the index automatically in the background over the next few hours. Nothing is lost in the meantime — disabling is fully reversible, which makes it a safe experiment to try.