Here is a familiar scene: you open Task Manager because the laptop feels sluggish, and there it is — Cortana, or SearchHost, chewing through 15–25% CPU. You have never intentionally opened Cortana in your life. Microsoft retired the Cortana app itself, yet something wearing its name (or its backend) is busy in the background, and your battery and fans are paying for it.

What you are actually seeing is Windows Search infrastructure doing Cortana’s old job. SearchHost.exe handles taskbar search, indexes your files, and processes cloud search results — and when its index corrupts or its workload spirals, CPU usage climbs and stays there. The good news is that this is one of the more fixable background-CPU problems, because the causes are few and the remedies are well understood.

Below is the full rundown: what is really running, why it spikes, and how to calm it down without breaking search.

Why this happens

  • Corrupted search index looping: A damaged index makes SearchHost re-index the same files endlessly, pinning CPU for hours or days.
  • Cloud search churn: Online search results, Microsoft account sync, and work/school content keep the search backend busy on slow connections.
  • Cortana app remnants active: Leftover Cortana app components and background permissions still trigger activity on some upgraded systems.
  • Large file collections being indexed: New photo libraries, code repositories, or synced OneDrive folders cause days of initial indexing.
  • Search highlights and suggestions: Animated search highlights and suggestion fetching add continuous low-level background work.
  • Conflicting privacy settings: Toggling search permissions repeatedly can leave the indexer in a confused, high-activity state.
  • Outdated Windows builds: Older Windows 11 builds had SearchHost memory and CPU inefficiencies fixed by later cumulative updates.
  • Third-party search enhancers: Utilities that hook into Windows Search can multiply the backend’s workload.

How to fix it

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

Fix 1: Identify exactly which process is busy

  1. Open Task Manager with Ctrl + Shift + Esc and sort by CPU during a spike.
  2. Check whether the busy process is SearchHost.exe, SearchIndexer.exe, or an actual Cortana entry.
  3. Right-click the process, choose Open file location, and verify it lives in C:\Windows\SystemApps (legitimate) rather than somewhere odd.
  4. Note the pattern: constant usage means an index loop; spikes when you type mean query processing issues.

Naming the process correctly decides the fix. SearchHost spikes get the index and cloud fixes below; a genuine Cortana app entry gets disabled in Fix 5. Do not kill these processes as a “fix” — Windows restarts them, and you learn nothing. If SearchHost specifically is the hog, our dedicated SearchHost.exe high CPU guide goes deeper.

Fix 2: Rebuild the search index

  1. Go to Settings, Privacy & security, Searching Windows.
  2. Open Advanced indexing options, click Advanced, then Rebuild under Troubleshooting.
  3. Let it run to completion — expect heavy CPU and disk for one to three hours on large drives.
  4. After it finishes, monitor for a full day: proper behavior is near-zero idle CPU.

A corrupt index is the number one cause of endless SearchHost CPU. Rebuilding is disruptive once — schedule it overnight or during lunch — and then the problem is gone permanently. If you have an enormous file collection, consider switching from Enhanced to Classic indexing in the same settings page to shrink the indexer’s workload.

Fix 3: Turn off cloud and web search features

  1. In Settings, Privacy & security, Search permissions, turn off Cloud content search for both Microsoft account and work/school account.
  2. In the same page, disable search highlights if you do not use them.
  3. Under Searching Windows, review the “Find my files” scope and exclude folders that do not need indexing.
  4. Restart the SearchHost process via Task Manager (right-click, End task — it restarts cleanly) and observe.

Cloud search keeps the backend fetching, parsing, and ranking online results continuously. On a metered or slow connection this is pure waste, and even on fast connections it adds measurable background CPU. Local file search keeps working fine without it — you lose only web results in the taskbar box, which most people never wanted there anyway.

Fix 4: Update Windows and check for known fixes

  1. Go to Settings, Windows Update, and install all pending updates.
  2. Specifically look for cumulative updates — several have included SearchHost performance fixes.
  3. Restart when prompted and monitor SearchHost CPU for a day.
  4. If updates are stuck, clear the update cache or grab the update from the Microsoft Update Catalog .

Microsoft has quietly fixed multiple SearchHost CPU bugs through cumulative updates. If your laptop has been postponing updates for months, you may be suffering from a bug that was fixed long ago. This is also the moment to confirm you are on a supported Windows 11 build — check Microsoft’s Windows 11 download page for the current version.

Fix 5: Disable the Cortana app and its background activity

  1. Go to Settings, Apps, Installed apps, and search for Cortana — uninstall it if present.
  2. Go to Settings, Apps, and check startup entries for anything Cortana-related; disable them.
  3. In Settings, Privacy & security, Search permissions, review and disable any remaining Cortana-era toggles.
  4. For a thorough job, see our guide on disabling Cortana in Windows 11 24H2 , which covers the Group Policy and registry methods.

On systems upgraded from Windows 10, Cortana remnants often survive with background permissions intact. Removing the app and its startup entries stops the genuine Cortana component; the search-backend fixes above handle the rest. Between the two, background CPU from this whole family should drop to near zero.

Fix 6: Limit what gets indexed

  1. Open Indexing Options (Settings, Privacy & security, Searching Windows, Advanced indexing options).
  2. Click Modify and uncheck folders that do not need fast search: program files, game libraries, temp directories, node_modules-style folders.
  3. Keep indexed locations to your documents, desktop, and start menu.
  4. Click OK and let the index adjust — CPU settles as the scope shrinks.

Most people index far more than they search. Every folder in the index is a folder SearchHost watches for changes, so trimming the scope directly trims background work. Developers should absolutely exclude dependency folders — a single node_modules directory can contain 100,000 files that the indexer dutifully tracks.

Fix 7: Disable Windows Search indexing (last resort)

  1. Press Win + R, type services.msc, and find Windows Search.
  2. Set Startup type to Disabled, click Stop, then OK.
  3. Test taskbar search — file-content search will be slower or limited, but app launching still works.
  4. Re-enable anytime by reversing the steps if you miss full search.

This is the nuclear option, and it works: with the service off, SearchHost and SearchIndexer go quiet permanently. The trade-off is slower file-content searches. Many users find they only ever search for app names — which still works — and happily leave indexing off forever. Try Fixes 1–6 first; this one is for when nothing else sticks.

Closing

Cortana-era CPU usage on Windows 11 is really a search-backend problem wearing an old name, and it yields to methodical fixes: rebuild the index, trim cloud features and indexed scope, remove app remnants, and keep Windows updated. Only disable the search service outright if the gentler fixes fail. Your fans will spin down, your battery will thank you, and taskbar search will keep working for the things you actually search for.

Frequently asked questions

Why is Cortana using CPU when I never open it?
On Windows 11, what shows up as Cortana activity is usually the SearchHost.exe process, which powers both taskbar search and Cortana’s backend. It indexes files, processes search queries, and syncs cloud content in the background. High CPU typically means the search index is rebuilding, the index is corrupted and looping, or cloud search features are churning on a slow connection.
Can I completely remove Cortana from Windows 11?
Cortana as a standalone app was retired by Microsoft, but its search backend (SearchHost.exe) remains part of Windows and cannot be fully removed without breaking taskbar search. You can disable the Cortana app, turn off its background activity, and tame SearchHost’s CPU usage — which achieves the practical result most people want.
Will disabling Cortana break Windows Search?
Disabling the Cortana app itself does not break search. However, aggressively disabling the underlying SearchHost process or the Windows Search service will degrade or disable taskbar search. The fixes in this guide target the CPU waste while keeping search functional, unless you explicitly choose to disable search indexing.
Is SearchHost.exe the same as Cortana?
Not exactly, but they are closely related. SearchHost.exe is the modern Windows Search host process that also serves Cortana’s search backend. In Task Manager, Cortana-related CPU usage usually appears under SearchHost.exe or SearchIndexer.exe rather than a process literally named Cortana.