You open Task Manager on your Lenovo and something called Cortana — or SearchHost.exe wearing Cortana’s old clothes — is burning 15-30% CPU while you do nothing. Microsoft officially retired the Cortana app, yet its ghost still haunts Windows 11 background processes, and on Lenovo laptops with busy preloads it misbehaves more visibly than most.

Here’s the honest technical picture: the Cortana consumer app is gone, but Windows Search still runs on infrastructure Cortana built. When SearchHost.exe (the search UI) or its indexing backend gets stuck — corrupted index, a looping background task, contention with Lenovo’s own utilities — Task Manager shows CPU usage that users understandably still call ‘Cortana high CPU.’ The label doesn’t matter; the stuck search pipeline does. On Lenovo laptops the symptom stands out more because Vantage’s own background tasks compete for the same CPU windows during the post-boot indexing rush.

This guide identifies which process is actually misbehaving on your ThinkPad, IdeaPad, or Legion, calms it down, and — if you want — silences Cortana’s remnants properly without breaking Windows Search. For broader Lenovo sluggishness, pair this with disabling background apps on Windows 11 .

Why this happens

  • SearchHost.exe stuck on a corrupted index — The search UI process loops retrying queries against a damaged index database — constant CPU, no results improvement, the classic ‘Cortana’ symptom.
  • Legacy Cortana background tasks still scheduled — Retired-but-present Cortana maintenance tasks in Task Scheduler can fire and fail repeatedly, each attempt costing CPU.
  • Lenovo Vantage + search contention at boot — Vantage’s hardware polls and update checks collide with search indexing in the post-boot window, amplifying spikes on 8 GB RAM systems.
  • Bing/online search integration hanging — SearchHost waiting on network responses for cloud search results can spin while connectivity is poor — CPU burn for zero benefit.
  • Corrupted Cortana app package — The deprecated Cortana AppX package sometimes corrupts during feature updates and its background host crashes and restarts in a loop.
  • Lenovo Smart Performance or similar utilities polling — Older Lenovo utility versions poll system state aggressively, and their queries route through the same search/indexing APIs.
  • Windows 11 24H2 search regression — Feature updates occasionally reintroduce search CPU bugs fixed in earlier builds — fixed again in subsequent cumulative updates.

How to fix it

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

Fix 1: Identify the real process

Name it precisely before touching anything.

  1. Open Task Manager, sort by CPU, and find the offender — note whether it’s SearchHost.exe, SearchIndexer.exe, or an actual Cortana entry.
  2. Right-click > Open file location: legitimate SearchHost lives in SystemApps; anything elsewhere is suspicious.
  3. If it’s SearchIndexer.exe, skip to Fix 4. If it’s SearchHost.exe, continue here.
  4. End the SearchHost task once as a test — it restarts automatically; if CPU stays low for hours after, it was a transient stuck state.

Fix 2: Kill Cortana’s scheduled tasks

Stop the retired tasks from firing.

  1. Open Task Scheduler and navigate to Task Scheduler Library > Microsoft > Windows > Windows Search and > … > Cortana (if present).
  2. Disable any Cortana-named tasks — right-click > Disable. These serve the retired assistant, not search.
  3. Also check Microsoft > Windows > Management > Provisioning for Cortana-related logon tasks on Lenovo preloads.
  4. Restart and watch Task Manager for 15 minutes — looping-task CPU vanishes immediately when this is the cause.
  5. Note: on Lenovo preloads these tasks sometimes reappear after Lenovo Vantage updates — if CPU returns weeks later, re-check the Task Scheduler locations before assuming a new problem.

Fix 3: Disable cloud/Bing search integration

Cuts the network-wait spinning that inflates SearchHost CPU.

  1. Open Settings > Privacy & security > Search permissions.
  2. Turn off Cloud content search (Microsoft account and Work/School account).
  3. Under More settings, disable Search highlights — it triggers background content fetches.
  4. SearchHost CPU typically drops within minutes; local file search is unaffected.

Fix 4: Rebuild the search index

For SearchIndexer-driven CPU, rebuild the database it’s choking on.

  1. Open Control Panel > Indexing Options > Advanced > Rebuild.
  2. Leave the Lenovo plugged in for a few hours — the rebuild itself uses CPU, which is normal and temporary.
  3. If you barely use file search, our guide to disabling search indexing on Windows 10 gives steps that work on Windows 11 too.
  4. Verify afterward: idle SearchIndexer should sit near 0%.

Fix 5: Remove the Cortana AppX package (safe method)

Removes the deprecated app without touching search infrastructure.

  1. Open PowerShell as administrator.
  2. Run: Get-AppxPackage -allusers Microsoft.549981C5F5F10 | Remove-AppxPackage — this targets the Cortana package specifically.
  3. Do NOT remove the Search or StartMenuExperienceHost packages — those break search and Start.
  4. Restart. The Cortana entry disappears from Task Manager permanently; search keeps working.

Fix 6: Update Lenovo Vantage and system drivers

Reduces the contention that makes search spikes worse on Lenovos.

  1. Update Lenovo Vantage from the Microsoft Store — old versions poll far more aggressively.
  2. Run Vantage’s System Update or visit Lenovo’s support page for chipset and storage drivers for your exact model.
  3. In Vantage, turn off background features you don’t use (battery thresholds you never set, network boost, etc.). Also disable Vantage’s continuous sensor polling if your model offers it — on some IdeaPads it queries hardware state every few seconds around the clock.
  4. Install pending Windows cumulative updates too — 24H2-era search regressions were fixed in later cumulative releases; check Microsoft’s Windows support hub for the latest.

Fix 7: Create a fresh user profile (persistent corruption)

When search corruption lives in the user profile, no system-wide fix reaches it.

  1. Create a new local admin account: Settings > Accounts > Other users > Add account.
  2. Log into it and use search normally for a day — if CPU stays flat, the old profile’s search database is corrupt.
  3. Migrate your files to the new account rather than fighting the old one’s database.
  4. This is the definitive fix for ’tried everything, still spikes’ cases.

Closing

‘Cortana high CPU’ on Lenovo laptops is really a stuck Windows Search pipeline wearing an old name — kill the legacy tasks, rebuild the index, and remove the dead AppX package, and it goes quiet. Your Start menu search survives; only the ghost leaves. And if the spikes ever return after a Lenovo utility update, you now know exactly where to look first.

Frequently asked questions

What is Cortana doing on Windows 11 if it's discontinued?
Microsoft retired the Cortana consumer app, but its remnants — background services, search integration hooks, and scheduled tasks — still ship with Windows 11 and can malfunction. What Task Manager often labels as Cortana-related CPU usage is actually SearchHost.exe (the search UI process) or the legacy Cortana background task stuck in a loop. The fixes below address the real processes, whatever name they wear.
Is SearchHost.exe the same as Cortana?
Not exactly, but they’re related. SearchHost.exe is the modern Windows Search interface process that powers the Start menu search flyout — it inherited much of Cortana’s old search infrastructure. When people report ‘Cortana high CPU’ on Windows 11, the actual process burning cycles is usually SearchHost.exe or SearchIndexer.exe. Fixing search fixes the symptom regardless of the label.
Will disabling Cortana break Windows Search?
If done correctly, no. The safe methods below disable Cortana’s background tasks and consumer features while leaving the SearchHost.exe interface and file indexing intact — Start menu search keeps working. Aggressive registry hacks that gut the entire search package can break search, which is why this guide uses targeted disables and tells you exactly which ones are safe.
Why does this happen more on Lenovo laptops?
Lenovo’s preload (particularly older McAfee trials and Lenovo Vantage background tasks) competes with Windows Search for disk and CPU during the same post-boot window when search is indexing. On ThinkPads and IdeaPads with mechanical drives or 8 GB RAM, that contention makes SearchHost spikes far more visible than on a clean install. Updating Lenovo drivers and calming the preload reduces the collisions.