Open Task Manager on a Copilot+ PC and you’ll see them: processes with names hinting at AI work, sipping CPU and memory while you do nothing. Recall snapshot handlers. Search indexers with AI ranking. Copilot helpers. Windows ML maintenance. None of them asked permission in any memorable way, and together they form a constant background hum that costs battery, speed, and occasionally sanity.

Here’s the thing most guides miss: these processes aren’t malware and aren’t (usually) bugs. They’re Windows 11’s AI platform doing its job — indexing, snapshotting, transcribing, predicting. The problem is purely one of consent and proportion: you never chose this workload, and on some machines it’s disproportionate. This guide inventories what’s actually running, explains what each piece does, and gives you two control levels — the polite Settings toggles and the thorough service-level shutdown. For the service-level deep clean specifically, see disable Windows AI services ; for the noise-and-heat angle, laptop fan loud during AI tasks covers that symptom.

If you’re here because the machine is slow rather than just busy, laptop slow when AI features are on is the performance-focused companion. Let’s map the background first.

Why this happens

  • AI is a platform, not an app: Windows 11 runs AI as system infrastructure — services and scheduled tasks that start at boot, independent of any app you opened.
  • Recall needs constant feeding: Snapshot capture, encoding, and AI analysis run as background tasks around the clock when enabled.
  • Search indexing never truly sleeps: The indexer watches for file changes and reprocesses continuously, with AI ranking adding extra passes.
  • Models need maintenance: Windows periodically downloads, verifies, and optimizes AI models in the background.
  • Features phone home to services: Copilot, Live Captions, and Studio Effects each leave helper processes running after use.
  • Updates re-seed the stack: Feature updates reinstall and re-enable background AI components, which is why “I already turned this off” happens.

How to fix it

Work through these in order — inventory first, then act at the level you’re comfortable with.

Fix 1: Inventory your AI background processes

You can’t manage what you can’t see. Build the full picture before touching anything.

  1. Open Task Manager (Ctrl + Shift + Esc) > Processes tab, sorted by CPU.
  2. Look for: Recall/snapshot processes, Search Indexer, Copilot, LiveCaptions, AI-related Windows ML entries.
  3. Switch to the Services tab and note any AI/ML/Recall/Copilot services and their status.
  4. Open Task Scheduler (taskschd.msc) and browse Microsoft > Windows for AI-related tasks (search, maintenance, ML).
  5. Write down the complete list — this is your map for the fixes below.

Fix 2: Turn off the parent features in Settings

Killing processes is temporary; disabling the feature that spawns them is durable. Start with the polite switches.

  1. Recall: Settings > Privacy & security > Recall & snapshots > “Save snapshots” off, then delete snapshots.
  2. Search: Settings > Privacy & security > Searching Windows > Classic mode, exclude big folders.
  3. Copilot: uninstall it or disable autostart in its settings and Task Manager > Startup.
  4. Live Captions: Win + Ctrl + L off, plus disable autostart in Accessibility settings.
  5. Reboot and re-inventory — most AI processes should be gone or dormant.

Fix 3: Disable the scheduled tasks

Some AI work is driven by Task Scheduler entries that survive Settings toggles. Disabling them stops the relaunches.

  1. Open Task Scheduler (Win + R > taskschd.msc).
  2. Navigate to Task Scheduler Library > Microsoft > Windows and look for AI/search/maintenance folders.
  3. For tasks clearly tied to disabled features, right-click > Disable (don’t delete — disabling is reversible).
  4. Focus on snapshot, indexing, and model-maintenance tasks matching your Fix-1 inventory.
  5. Reboot and confirm the processes no longer respawn.

Fix 4: Set AI services to Manual or Disabled

Services are the deepest user-accessible control. Be careful here — only touch services you identified as AI-specific.

  1. Open services.msc (Win + R, as administrator ideally).
  2. Find the AI-related services from your inventory (Recall, AI platform, Copilot services).
  3. Double-click each > change Startup type: “Manual” is the safe choice; “Disabled” is the thorough one.
  4. Stop any currently running ones after changing the startup type.
  5. Document what you changed (screenshot or notes) so you can reverse it. The full service reference is in disable Windows AI services .

Fix 5: Verify with a clean-boot comparison

Prove your changes worked — and catch anything you missed — with a before/after measurement.

  1. Note current idle CPU/memory in Task Manager > Performance (2-minute average).
  2. After your changes and a reboot, measure again at the same idle state.
  3. The delta is your reclaimed headroom — typically 3–8% CPU and several hundred MB RAM.
  4. If a mystery process remains, research its exact name before touching it.
  5. For a truly clean baseline, compare against Safe Mode idle usage.

Fix 6: Maintain the quiet (updates will try to undo it)

Microsoft re-seeds AI background components with feature updates. A light maintenance habit keeps your system quiet.

  1. After each feature update, re-run your Fix-1 inventory (takes two minutes once you know the list).
  2. Re-disable anything the update re-enabled — it’s usually Recall and Enhanced indexing.
  3. Keep your “changed services” notes so re-applying takes seconds.
  4. Consider deferring feature updates a week or two to let others find the re-enable surprises first.
  5. Check this guide’s service list annually — Windows renames things, and new AI services appear.

Closing

Windows 11’s AI background processes aren’t sinister — they’re just uninvited. Inventory them with Task Manager, Services, and Task Scheduler; disable the parent features in Settings for the polite fix; and go to services and scheduled tasks for the thorough one. Measure the before/after so you know it worked, and keep a two-minute post-update audit habit because Microsoft will keep re-seeding the stack. A quiet Copilot+ PC is entirely achievable — it just doesn’t stay quiet on its own.

Frequently asked questions

What AI processes normally run in Windows 11 background?
Typical residents include Recall snapshot processing, Windows Search indexing (with AI ranking), Copilot background tasks, Live Captions services, and Windows ML model maintenance. The exact set depends on your hardware (Copilot+ PCs run more) and which features you’ve enabled.
How do I see all AI background processes?
Task Manager’s Processes tab shows most of them — sort by CPU or Memory and look for Recall, Search, Copilot, and AI-related entries. For services, open services.msc and filter for AI/ML/Recall/Copilot names. There’s no single “AI” category, so you check a few places.
Is it safe to end AI background tasks in Task Manager?
Ending a user-mode AI task is safe — worst case, the feature restarts it or misbehaves until reboot. Don’t disable random services you can’t identify, though; use this guide’s list to target only AI-specific ones. When in doubt, set a service to Manual rather than Disabled.
Why do AI processes restart after I end them?
Windows services and scheduled tasks relaunch them by design — ending the task treats the symptom for minutes. For lasting effect, disable the underlying service or scheduled task, or turn off the parent feature in Settings. This guide shows both levels.