On Windows 11, SearchHost.exe is the face of search — the Start menu box, the taskbar search flyout, the highlights panel. Type a query and it should spike briefly and vanish. Instead, for many users it spikes to 30–60% CPU and stays there, or surges every time the mouse drifts near the search box. The search UI becomes the slowest thing on the machine, which is backwards.

The anatomy is the same as Windows 10’s search problems with Windows 11 twists: every interaction queries both the local index and Microsoft’s online services, and Windows 11 adds the Search highlights content feed into the mix. When any leg of that pipeline hangs — corrupt index, stalled highlights fetch, broken app package — SearchHost burns CPU retrying. Fix the pipeline legs in order and search becomes instant.

Confirm it first: open Task Manager, hover over or click the taskbar search, and watch SearchHost.exe. Spikes tied to the search UI = this guide. For the Windows 10 version, see our SearchHost on Windows 10 guide ; for the condensed best-fixes list, the best SearchHost fixes is a quick companion.

Why this happens

  • Search highlights fetching: The content feed hanging on slow or proxied connections, retrying endlessly.
  • Bing integration stalls: Online query portion timing out per keystroke.
  • Corrupt search index: Every local query becoming expensive instead of instant.
  • Broken SearchHost package: The UI’s AppX package damaged by a feature update.
  • Indexer stuck re-crawling: Post-24H2 re-indexing never completing on a corrupt file.
  • SearchHost memory/cache bloat: Accumulated state degrading over long uptimes.
  • Third-party Start replacements: Start11/ExplorerPatcher hooks conflicting with the search pipeline.

How to fix it

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

Fix 1: Disable Search highlights

The single most effective Windows 11-specific fix.

  1. Right-click the taskbar > Search > uncheck Show search highlights (or set Search to Hide/Search icon only if you never use the box).
  2. Alternatively: Settings > Privacy & security > Search permissions > turn off Show search highlights.
  3. Test immediately: hover over and click the search area, type queries — hover-triggered spikes should be gone.
  4. This kills the content-fetch code path entirely; local search is unaffected and usually faster.
  5. If you liked highlights, you can re-enable later — but confirm the spikes don’t return first.

Fix 2: Disable Bing/web search integration

Stop the per-keystroke network hangs.

  1. Press Win+R, type regedit, navigate to HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Windows\Explorer (create Explorer if missing).
  2. Create DWORD (32-bit) DisableSearchBoxSuggestions = 1.
  3. Go to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Search and set BingSearchEnabled = 0 (DWORD, create if missing).
  4. End SearchHost.exe in Task Manager (it restarts fresh) or reboot.
  5. Type several test queries — results should now be local-only and instant, with no CPU spike. Microsoft documents these policies on the Windows support hub .

Fix 3: Rebuild the search index

Repair the local query leg.

  1. Settings > Privacy & security > Searching Windows > Advanced Search Indexer Settings > Troubleshoot first.
  2. If that doesn’t help, same dialog > Rebuild — full re-crawl takes 30 minutes to hours; keep the laptop plugged in and idle.
  3. Before rebuilding, narrow scope: set Find my files to Classic instead of Enhanced, and add high-churn folders (Downloads, build dirs, sync roots) to Excluded folders.
  4. Wait for “Indexing complete” status before judging — testing mid-rebuild is meaningless.
  5. After completion, search should answer as you type with SearchHost barely registering CPU.

Fix 4: Re-register the SearchHost package

When the UI component itself is corrupt.

  1. Open PowerShell as administrator.
  2. Run: Get-AppxPackage -AllUsers MicrosoftWindows.Client.CBS | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} — SearchHost lives in the CBS (Client Core) package on Windows 11.
  3. If that package name doesn’t resolve on your build, fall back to re-registering all inbox packages: Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} (takes several minutes).
  4. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth from an elevated prompt afterward.
  5. Reboot and test — package corruption from the 24H2 update is a known cause of persistent SearchHost CPU.

Fix 5: Check for third-party conflicts

Start-menu mods hook the same UI.

  1. If you use Start11, ExplorerPatcher, StartAllBack, or similar, disable or uninstall them temporarily and test search.
  2. Check Task Manager > Startup apps for search-adjacent helpers and disable during testing.
  3. Some “Windows 11 tweaker” tools patch the search UI’s registry keys in ways that break it — undo their search-related tweaks.
  4. Test with a clean configuration: if search is calm, re-add customizations one at a time.
  5. Keep your chosen customization updated — most conflicts are fixed in newer versions.

Fix 6: Update Windows and clear the caches

Get Microsoft’s latest search fixes.

  1. Settings > Windows Update — install everything pending; SearchHost fixes ship regularly in cumulative updates. Stuck updates can be fetched manually from the Microsoft Update Catalog .
  2. Clear the search cache: Settings > Privacy & security > Search permissions > Clear device search history.
  3. Run Disk Cleanup > Clean up system files and remove thumbnails, temporary files, and delivery optimization files — stale caches feed search slowness.
  4. Check update history for a failed update coinciding with the problem’s start — uninstall it as a test if suspected.
  5. Re-test after each change; update-delivered search fixes often resolve issues no setting can.

Fix 7: Reduce scope and consider the nuclear option

Permanent lightness for search-heavy complainers.

  1. Settings > Privacy & security > Searching Windows: Classic mode + generous Excluded folders = minimal indexer workload forever.
  2. In Advanced Search Indexer Settings > File Types, uncheck extensions you never search.
  3. The nuclear option: services.msc > Windows Search > Disabled — Start search falls back to slow non-indexed scanning. Only for users who rarely search and value absolute quiet.
  4. Prefer the middle path (Fix 1+2+3 combined) over the nuclear option — you keep fast local search with none of the spike sources.
  5. Document your final configuration — after the next feature update, verify the registry keys and highlights setting survived.

Closing

SearchHost.exe spikes on Windows 11 come from the search UI doing too much online work and querying a broken local index. Disable Search highlights, cut the Bing integration, rebuild the index — three changes, ten minutes, and the search box goes back to answering before you finish typing. That’s all search was ever supposed to do.

Frequently asked questions

What is SearchHost.exe on Windows 11?
SearchHost.exe is the process behind Windows 11’s search interface — the Start menu search box, taskbar search, and the Search highlights panel. Every keystroke you type runs through it as it queries your local search index and Microsoft’s online results. When healthy it idles at zero and spikes briefly per query; sustained high CPU means the query pipeline is stuck — usually a corrupt index, hanging web-search integration, or a broken SearchHost app package.
Why does SearchHost.exe spike when I just hover over the taskbar search?
Windows 11’s Search highlights feature preloads content — news, doodles, trending searches — when the search UI opens or hovers, and that content fetch runs through SearchHost. If the content service is slow or your connection stalls, the fetch hangs and retries, burning CPU. Disabling Search highlights removes this entire code path, which is why it’s one of the most effective single fixes for hover-triggered spikes.
Is it safe to end SearchHost.exe in Task Manager?
Yes. Ending it just closes the search UI process; Windows restarts it automatically next time you search, and nothing else is affected. It’s a useful diagnostic — if CPU stays normal after the restart for a while, the process itself is fine and its data (index, cache) is the problem. But it’s temporary relief only; apply the permanent fixes so the spikes don’t return.
Will turning off web search break anything I need?
No. Disabling search highlights and Bing integration only affects the search UI’s online content — local file, app, and settings search keeps working, and is usually faster without the web queries slowing it down. Your browser and everything else are untouched. Most users find search strictly better after the change: instant local results with no waiting on network fetches.