You open Task Manager and there it is: SearchApp.exe — or on newer builds, SearchHost.exe — chewing through 20, 40, even 70% CPU while you are doing nothing at all. Typing in the Start menu becomes laggy, the search box stutters, and the laptop’s fans spin up for a feature you barely use.

Windows Search is genuinely useful, but its indexer is fragile. When the index database corrupts, when a folder it watches changes constantly (hello, Downloads and cloud sync folders), or when a buggy update leaves the search service in a bad state, the process enters a re-scan loop: it indexes, hits the corruption, restarts, and indexes again. Each cycle costs CPU, and the cycle never ends.

The fix is methodical: confirm the search service is the problem, restart it cleanly, then rebuild or constrain what it indexes. Killing the process only buys minutes, so the steps below go after the root causes in order. For the broader indexer picture, see Windows Search indexer high CPU .

Why this happens

  • Corrupted search index database: a damaged index forces the service to re-scan endlessly without ever finishing.
  • High-churn watched folders: Downloads, cloud sync, and developer folders change constantly, triggering endless re-indexing.
  • Stuck search service state: the service gets wedged after an update and loops instead of idling.
  • Enhanced search mode: indexing the entire PC instead of default locations multiplies the workload enormously.
  • Corrupted search app package: the SearchHost app package itself can break, causing crash-restart cycles.
  • Third-party shell handlers: bad preview or property handlers make the indexer hang on specific files.
  • Cloud content search: searching OneDrive and cloud content adds network waits that keep the process busy.

How to fix it

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

Fix 1: Confirm SearchHost is the culprit

Verify the CPU is really coming from search before changing search settings. Constant CPU with no typing points to the indexer; spikes only while typing point to the search UI.

  1. Open Task Manager, sort by CPU, and confirm SearchApp.exe or SearchHost.exe is the top consumer.
  2. In the Details tab, right-click it and choose Open file location to verify it is a genuine Windows file.
  3. Note whether the spike is constant or tied to typing in search — both point to the indexer.

Fix 2: Restart the Windows Search service

A clean restart clears wedged in-memory state and is the fastest possible relief. If the spike returns after every reboot, the service is not the problem — the index is.

  1. Press Windows key + R, type services.msc, and press Enter.
  2. Find Windows Search, right-click it, and choose Restart.
  3. Watch Task Manager for five minutes; if CPU drops and stays down, a stuck service was the whole story.

Fix 3: Rebuild the search index

The definitive fix for a corrupted index database. Slow once, fast forever after. Do not interrupt the rebuild; a half-built index performs worse than a corrupted one.

  1. Open Settings > Privacy & security > Searching Windows.
  2. Click Advanced indexing options, then Advanced, then Rebuild under Troubleshooting.
  3. Leave the laptop plugged in and idle until indexing completes — check progress in the same dialog.

Enhanced mode indexes your entire PC. Classic indexes only default locations and is dramatically lighter. Enhanced mode made sense on fast desktops; on laptops Classic is almost always the better trade.

  1. In Settings > Privacy & security > Searching Windows, find Find my files.
  2. Select Classic instead of Enhanced.
  3. Click Advanced indexing options > Modify and remove any huge custom folders you added.

Fix 5: Exclude high-churn folders

Folders that change constantly should never be indexed. Excluding them stops the re-scan loop at its source. Revisit these exclusions after installing dev tools, which love adding watched folders.

  1. In Advanced indexing options, click Modify.
  2. Untick Downloads, OneDrive sync folders, code repositories, and game library folders.
  3. Click OK and let the indexer settle; CPU should drop within the hour.

Fix 6: Repair the Search app package

If the process crash-loops, its own package may be damaged. Re-registering it fixes the container. Run PowerShell as administrator or the re-registration will fail silently.

  1. Open an admin PowerShell and run: Get-AppxPackage -AllUsers Search | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}.
  2. Restart the laptop after the command completes.
  3. Open Start and type a test query to confirm search works and CPU stays low. See Microsoft’s Windows help for more search troubleshooting.

Fix 7: Disable cloud content in search

If local search is fast but CPU spikes with network activity, cloud search integration is the amplifier. Local file search is unaffected; you only lose searching inside cloud-only files.

  1. In Settings > Privacy & security > Searching Windows, scroll to Cloud content search.
  2. Turn off both Microsoft account and Work or School account options.
  3. Restart the search service from services.msc and verify idle CPU.

Fix 8: Limit which file types get indexed

The indexer’s Advanced options let you control exactly which file extensions are indexed and whether it indexes contents or just properties. Excluding developer artifacts, virtual machine disks, and other heavy file types you never search by content dramatically shrinks the indexer’s workload without affecting everyday file search.

  1. Open Advanced indexing options, click the Advanced button, then the File Types tab.
  2. Untick extensions you never need content search for, such as virtual disk and database files.
  3. For remaining types, choose Index Properties Only where full content search is unnecessary.
  4. Click OK and let the indexer rebuild; future indexing passes will be much lighter.

Closing

SearchApp.exe high CPU is almost always an indexer problem: a corrupted database, too-broad indexing scope, or a high-churn folder it cannot keep up with. Restart the service for instant relief, rebuild the index for a permanent fix, and narrow what gets indexed so the problem never returns. If the search indexer is also pinning your disk at the same time, work through the high disk usage on startup guide alongside this one.

Frequently asked questions

What is the difference between SearchApp.exe and SearchHost.exe?
They are the same feature under different names. SearchApp.exe was the process name in earlier Windows 11 builds; Microsoft renamed it to SearchHost.exe in later builds (around 22H2/23H2). Both power the Start menu search box and the search indexer UI. Fixes for one apply to the other, so do not worry about which name your Task Manager shows.
Can I disable Windows Search entirely?
You can set the Windows Search service to Disabled in services.msc, which stops all indexing and the search UI. Start menu search will still show apps but become much slower at finding files. For most people, constraining the index (Fixes 4 and 5) is the better trade — you keep fast search without the CPU cost, instead of losing the feature completely.
Why does search use CPU right after I install Windows?
A fresh install or feature update triggers a full initial index of the entire drive, which legitimately uses significant CPU for hours. This is expected and self-resolving. The problem is only when high CPU persists for days after installation. Give a new system 24–48 hours of plugged-in idle time before concluding the indexer is stuck.
Does rebuilding the index delete my files?
No. Rebuilding only deletes and recreates the search database — the catalog Windows uses to find files quickly. Your actual files, folders, and documents are completely untouched. After the rebuild, file search may be slower for a few hours while the index repopulates, then returns to full speed with the corruption gone.