SearchHost.exe is supposed to be a lightweight process — the friendly face of the Start menu search box. So when Task Manager shows it chewing 30, 40, even 50 percent CPU on your ASUS laptop, something has clearly gone wrong behind that innocent little search field. Fans spin, the machine lags, and typing in the Start menu feels like wading through mud.

On ASUS laptops this usually traces to one of two things: the Windows Search index itself is corrupted or stuck rebuilding, or an ASUS utility is interfering with search components. The fixes below go in diagnostic order — quick resets first, index surgery second, ASUS-specific cleanup last.

Why this happens

  • Corrupted search index: A damaged index database makes SearchHost loop on unreadable entries instead of serving results.
  • Stuck re-indexing: After updates or location changes, the indexer restarts from scratch and SearchHost stays busy for days.
  • Too many indexed locations: Whole drives, network shares, or external disks added to the index multiply the workload.
  • ASUS utility interference: MyASUS and ASUS update tools can lock or corrupt search database files during their own operations.
  • Corrupted search app package: The SearchHost UWP package itself can be damaged, causing constant crash-restart cycles.
  • Cloud search and history features: Search Highlights and cloud content retrieval add ongoing background queries.
  • Third-party shell extensions: Context menu handlers from installed software can hook into search and hang it.

How to fix it

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

Fix 1: Restart SearchHost and check the pattern

Open Task Manager, find SearchHost.exe under Background processes (you may need to expand), and choose End task — Windows restarts it immediately. This is a diagnostic reset: if CPU stays low afterward, it was a transient stuck state. Also run the dedicated troubleshooter: Settings → System → Troubleshoot → Other troubleshooters → Search and Indexing. It detects index corruption and permission problems automatically and is surprisingly effective. The general SearchHost fix guide covers the non-ASUS variant of this same sequence.

  1. End the SearchHost.exe task in Task Manager.
  2. Run the Search and Indexing troubleshooter.
  3. Apply any repairs it suggests and reboot.
  4. Monitor SearchHost CPU for 30 minutes.

Fix 2: Rebuild the search index cleanly

If the troubleshooter found index problems — or SearchHost is still hot — rebuild the database from scratch. Open Control Panel → Indexing Options → Advanced → Rebuild. This deletes the corrupted index and rebuilds it cleanly, which takes a few hours of plugged-in idle time. Crucially, while rebuilding, first open Indexing Options → Modify and uncheck locations you don’t need indexed: external drives, game folders, downloads archives. A smaller, cleaner index finishes faster and stays healthy. Microsoft documents the indexing options in the Windows support hub .

  1. Open Control Panel → Indexing Options.
  2. Click Modify and uncheck unnecessary locations.
  3. Click Advanced → Rebuild and confirm.
  4. Leave the laptop plugged in and idle for several hours.

Search Highlights (the decorative content in the search box) and cloud-backed search keep SearchHost making ongoing queries. Go to Settings → Privacy & security → Search permissions and turn off Show search highlights. In the same area, disable cloud content search and search history if you don’t use them. These features are pure overhead for most users — disabling them cuts SearchHost’s background workload dramatically without affecting local app and file search at all.

  1. Open Settings → Privacy & security → Search permissions.
  2. Turn off Show search highlights.
  3. Disable cloud content search and search history.
  4. Restart and verify SearchHost stays quiet.

Fix 4: Re-register the SearchHost app package

A damaged SearchHost package causes crash-restart loops that look like constant CPU. Open PowerShell as administrator and re-register the Windows Search app package for all users. This reinstalls the manifest without touching your data or index. After the command completes, reboot and check Task Manager — a package that was crash-looping will now sit at near-zero. If PowerShell reports the package healthy but CPU persists, the problem is data-side (the index), not package-side, and Fix 2’s rebuild is the answer.

  1. Open PowerShell as administrator.
  2. Re-register the Microsoft Windows Search package.
  3. Reboot the laptop.
  4. Check SearchHost.exe CPU at idle for 15 minutes.

Fix 5: Update or reset ASUS utilities

On ASUS machines, don’t skip this. Update MyASUS and Armoury Crate via the Microsoft Store, since outdated versions are known to interfere with search components. If SearchHost spikes specifically when an ASUS utility runs, reset that utility: Settings → Apps → Installed apps → Advanced options → Repair, then Reset if needed. Also check Task Manager’s Startup tab and disable ASUS updaters you don’t need — fewer ASUS background processes means fewer chances of search interference. The startup programs guide shows how to audit these safely.

  1. Update all ASUS apps via the Microsoft Store.
  2. Repair, then reset, any ASUS utility tied to the spikes.
  3. Disable unneeded ASUS startup entries.
  4. Reboot and monitor for a full day.

Fix 6: Limit indexing scope or switch to classic mode

For a permanent lightweight setup, shrink what gets indexed. In Indexing Options → Modify, index only your user folder essentials (Documents, Pictures) — exclude videos, downloads, and program folders. Alternatively, go to Settings → Privacy & security → Searching Windows and switch from Enhanced to Classic indexing, which limits the index to libraries and desktop. Classic mode dramatically reduces SearchHost and indexer workload on machines where you rarely search file contents. Start menu app search keeps working normally either way.

  1. Open Indexing Options → Modify and trim locations.
  2. Or switch to Classic indexing in Search settings.
  3. Rebuild the index after changing scope.
  4. Confirm CPU stays low across several days.

Closing

SearchHost.exe goes rogue for fixable reasons — a corrupted index, noisy cloud features, or an ASUS utility getting in the way. Work from the troubleshooter through the rebuild to the ASUS cleanup, and the process returns to the invisible background role it was designed for. Your Start menu stays fast, and your CPU stays yours.

Frequently asked questions

What is SearchHost.exe and can I delete it?
SearchHost.exe is the Windows Search interface process that powers the Start menu search box and search flyout. You cannot and should not delete it — it’s a protected system component. Disabling it breaks Start menu search entirely. The correct fix is addressing whatever is making it work overtime: usually a corrupted index, a stuck search process, or a conflicting ASUS utility.
Why does SearchHost.exe use high CPU only on my ASUS laptop?
It doesn’t only happen on ASUS, but ASUS machines have extra triggers: MyASUS and Armoury Crate integrate with search, ASUS preinstalled apps add indexed locations, and ASUS update utilities can corrupt the search database during their own updates. The base Windows Search causes are the same everywhere; the ASUS-specific steps below handle the extras.
Will disabling Windows Search indexing break anything?
Disabling the indexer only makes file searches slower — it doesn’t break Windows or the Start menu’s app search. Start menu search for installed apps still works; searching file contents becomes slow because there’s no index. Most users keep indexing on for the Start menu and just fix or limit it rather than disabling it entirely.
How do I know if the search index is corrupted?
Classic signs: SearchHost.exe or SearchIndexer.exe holding sustained high CPU for days, Start menu search returning no results or freezing, and Event Viewer showing search-related errors under Windows Logs → Application. The Search and Indexing troubleshooter will also typically report that it found and repaired index problems when corruption is present.