SearchHost.exe is Windows 11’s search process, and it has inherited the family trait: burning CPU for no apparent reason. You will find it in Task Manager consuming 10–25% CPU while the laptop idles, the search box closed, nobody typing anything. It is the successor to Windows 10’s SearchApp.exe, and like its predecessor, its CPU spikes come overwhelmingly from the web-connected half of its job — highlights, suggestions, cloud content — rather than from finding your files.

The distinction matters because it defines the fix strategy. You do not need to break search to fix SearchHost; you need to cut the background web churn and repair the index when it loops. Every fix below preserves local file and app search while targeting a specific CPU trigger, in the order that resolves most cases fastest.

Why this happens

  • Search highlights refreshing: The rotating content in the search box wakes the process on a schedule to fetch new material.
  • Cloud content search churn: Syncing Microsoft account and work/school results keeps background queries running.
  • Corrupted search index: A damaged index floods SearchHost with re-indexing events it must process continuously.
  • Stuck suggestion pre-fetch: The suggestion pipeline occasionally wedges, retrying fetches in a tight loop.
  • Excessive indexed locations: Enhanced indexing over huge folders generates a constant event stream for SearchHost.
  • Microsoft account sync issues: Broken sync states cause repeated authentication and content refresh attempts.
  • Outdated Windows 11 builds: Known SearchHost CPU bugs fixed in later cumulative updates.
  • Third-party shell modifications: Start menu replacements and taskbar tweaks can fight the search host process.

How to fix it

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

Fix 1: Verify the process and observe the pattern

  1. In Task Manager, find SearchHost.exe, right-click, Open file location — confirm C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy.
  2. Watch CPU for five minutes without touching the search box; note whether usage is constant or pulsing.
  3. Open the search box, hover without typing, and watch for spikes — hover-triggered spikes implicate highlights and suggestions.
  4. End the task once as a test: if CPU stays low for hours after restart, the spike was transient and you may be done.

The file-location check rules out impostors in seconds. Pattern observation directs the fix: constant load means index or sync problems (Fixes 4–5), while hover/pulse patterns mean highlights and suggestions (Fixes 2–3). Write down what you see before changing settings.

Fix 2: Disable search highlights

  1. Right-click the taskbar, hover over Search, and uncheck Show search highlights.
  2. Alternatively: Settings, Privacy & security, Search permissions, and turn off highlights there.
  3. Close and reopen the search box to confirm the highlights area is gone.
  4. Monitor SearchHost CPU for an hour — the periodic pulse should disappear.

Search highlights are the single most common cause of the “SearchHost spikes every few minutes while idle” pattern. Each content rotation wakes the process to fetch, render, and cache new material. Nobody’s productivity depends on illustrations in the search box; disabling them removes a recurring workload with zero functional loss.

Fix 3: Turn off cloud content search and suggestions

  1. Go to Settings, Privacy & security, Search permissions.
  2. Turn off Cloud content search for both Microsoft account and work/school account.
  3. Disable search history on the device if you do not rely on it.
  4. Restart SearchHost via Task Manager (End task) and observe idle CPU.

Cloud search keeps the backend issuing queries, ranking results, and syncing state continuously — even when you never type. Local search is unaffected: your apps, files, and settings still appear instantly. For users who never wanted web results in the taskbar box, this also makes search results cleaner and faster.

Fix 4: Rebuild the search index

  1. Go to Settings, Privacy & security, Searching Windows, Advanced indexing options.
  2. Click Advanced, then Rebuild under Troubleshooting.
  3. Let it complete — expect heavy CPU and disk for one to three hours.
  4. Afterward, monitor SearchHost for a full day to confirm the constant load is gone.

A corrupted index is the top cause of constant (non-pulsing) SearchHost CPU: the indexer generates endless change events, and SearchHost dutifully processes each one. Rebuilding is disruptive once and curative permanently. If your file collection is enormous, also consider switching Enhanced indexing to Classic to permanently reduce the event stream.

Fix 5: Shrink indexed locations

  1. In Advanced indexing options, click Modify.
  2. Uncheck folders that do not need content search: game libraries, program files, temp dirs, dependency folders like node_modules.
  3. Keep Documents, Desktop, and Start Menu — the places you actually search.
  4. Click OK and let the index trim itself; CPU settles as the scope shrinks.

Every indexed folder is a folder whose changes generate events for SearchHost to process. Developers and creators often index hundreds of thousands of files they never search by content. Trimming the scope is a structural fix: less to watch means less background work, permanently. This pairs well with our Cortana high CPU guide , since the two share backend behavior.

Fix 6: Install Windows updates

  1. Go to Settings, Windows Update, and install all pending updates.
  2. Restart when prompted and monitor SearchHost for a day.
  3. Check Microsoft’s Windows 11 download page to confirm you are on a current build.
  4. If updates are stuck, clear the SoftwareDistribution cache or use the Microsoft Update Catalog .

Microsoft has fixed multiple SearchHost CPU bugs through cumulative updates. A machine months behind may be running a known-bad search build, and no settings toggle fully compensates for a genuine bug. Keep the system current as a matter of routine — it is the cheapest fix on this list.

Fix 7: Reset the search app components (advanced)

  1. Open PowerShell as administrator.
  2. Run Get-AppxPackage MicrosoftWindows.Client.CBS | Reset-AppxPackage (on builds where Reset-AppxPackage is available).
  3. If the cmdlet is unavailable, rebuild the index (Fix 4) and re-apply Fixes 2–3 instead.
  4. Restart and verify SearchHost idles near zero with search fully functional.

When settings and index rebuilds both fail, the search host package’s own stored state may be corrupt. Resetting the package clears it without affecting your files or other apps. This is the deepest non-destructive fix; beyond it lies only the nuclear option of disabling Windows Search entirely via services.msc, which our 100% disk guide mentions for indexer-related disk issues. Microsoft documents search troubleshooting in Windows support .

Closing

SearchHost.exe CPU spikes are the web-content machinery of taskbar search misbehaving: highlights, cloud queries, and suggestion pipelines churning in the background, occasionally amplified by a corrupt index. Disable highlights, cut cloud search, rebuild the index when the load is constant, and keep Windows updated. Local search survives all of it — faster and quieter than before.

Frequently asked questions

What is SearchHost.exe on Windows 11?
SearchHost.exe is the Windows 11 process that hosts the taskbar search experience — the search box UI, query processing, and results rendering. It replaced Windows 10’s SearchApp.exe. It lives in C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy. It is a legitimate Microsoft component, and high CPU from it signals a workload problem, not an infection.
Why does SearchHost.exe use CPU when I'm not searching?
SearchHost does background work even with the box closed: refreshing search highlights, pre-fetching suggestions, syncing cloud content, and reacting to indexer events. A corrupted index, aggressive cloud features, or a stuck background task can keep it busy indefinitely. The fixes in this guide target each of these triggers.
Can I end SearchHost.exe in Task Manager?
Yes, safely — right-click and End task. Windows restarts it automatically within seconds. Ending it is a useful diagnostic (if CPU stays low after restart, the spike was transient) and a temporary relief, but it does not fix a persistent trigger. Use it for testing, then apply the lasting fixes below.
Will disabling SearchHost break the Start menu?
SearchHost specifically powers the taskbar search box, not the Start menu’s app list — though they share backend services. Aggressively disabling search components can degrade search-as-you-type in Start. The fixes here preserve full search functionality while eliminating the CPU waste.