Your laptop benchmarks like a rocket but feels like it’s wading through mud — but only sometimes. The pattern: it’s fine after a reboot, then gradually gets sluggish as the day wears on. If that sounds familiar, Windows 11’s AI features are prime suspects. They’re designed to be invisible, which makes them the perfect invisible culprit.
Here’s the mechanism: features like Recall, AI search indexing, and Live Captions don’t just use the NPU — they generate constant CPU, memory, and disk activity around it. Snapshot encoding, index merging, model loading — all of that competes with your actual work. The slowdown is real, measurable, and fixable. If battery drain is your bigger complaint than speed, start with AI features draining laptop battery instead — same culprits, different lens.
This guide shows you how to prove AI features are the cause (not just suspect them) and then surgically fix the slowdown. If you’d rather just turn the whole AI stack off, turn off AI features in Windows 11 is the quick path. And if Task Manager shows the NPU itself pinned, NPU usage high at idle digs into that specific symptom.
Why this happens
- Recall’s snapshot pipeline: Capturing, encoding, and AI-analyzing screen snapshots every few seconds creates sustained CPU and disk load.
- Index merging churn: Windows AI search constantly merges new index data in the background, spiking disk I/O for minutes at a time.
- Model loading stalls: When an AI feature first activates, loading its model into memory can freeze the system briefly — then it repeats after updates.
- Memory pressure: AI models and snapshot caches consume gigabytes of RAM, pushing other apps into the pagefile on 16GB machines.
- Competing with foreground apps: Background AI tasks don’t always yield politely; a Recall encoding burst during a game or compile causes visible stutters.
- First-week indexing storm: New laptops and fresh Windows installs index everything at once — the worst slowdowns happen in the first days of ownership.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Prove AI features are the cause
Never “fix” by randomly disabling things. Confirm the diagnosis with Task Manager so your effort lands on the real culprit.
- When the laptop feels slow, open Task Manager (Ctrl + Shift + Esc) > Processes, sorted by CPU.
- Look for AI-related processes: Recall snapshots, Search Indexer, LiveCaptions, Copilot background tasks.
- Check the Memory and Disk columns too — AI features often bottleneck disk, not CPU.
- Note the correlation: does slowness coincide with high usage by these processes? That’s your proof.
- If no AI process is active during slowdowns, stop here — your problem is elsewhere (startup apps, thermals, storage).
Fix 2: Pause Recall during work hours
Recall is the heaviest continuous AI workload. You don’t have to kill it forever — pausing it when you need speed is often enough.
- Open Settings > Privacy & security > Recall & snapshots.
- Toggle “Save snapshots” off during demanding work, back on later if you value the timeline.
- Alternatively, use the system tray Recall icon to pause snapshots for a set period.
- Delete old snapshots to reduce the background processing queue.
- Observe for a day — if responsiveness returns, you’ve found your main offender.
Fix 3: Defer indexing to idle time
Search indexing is necessary but doesn’t need to run while you’re working. Windows lets you schedule its aggression.
- Go to Settings > Privacy & security > Searching Windows.
- Turn off “Enhanced” mode if on — Classic indexes less and churns less.
- Exclude huge folders (media libraries, code repos, game installs) from indexing.
- In Indexing Options (Control Panel) > Advanced, you can rebuild a corrupted index that loops endlessly.
- Let the laptop sit plugged in and idle for a few hours to let indexing finish its backlog.
Fix 4: Close Copilot and Live Captions when not in use
These are the AI apps people leave running out of habit. They’re cheap individually but add up, and closing them is instant relief.
- Fully quit the Copilot app (not just minimize) when you’re not using it — check the system tray.
- Toggle Live Captions off with Win + Ctrl + L the moment a call or video ends.
- Remove Copilot from Startup apps (Task Manager > Startup) so it doesn’t preload.
- Disable Studio Effects in camera settings when not on calls.
- Make “close AI apps after use” a habit for a week and compare the feel.
Fix 5: Free up memory headroom
AI features plus modern apps on 16GB RAM is a tight fit. Memory pressure makes everything — AI or not — feel slow.
- In Task Manager > Performance > Memory, check if you’re consistently above 85% usage.
- Close browser tabs aggressively — browsers are the other great memory hog.
- Disable unnecessary Startup apps to reclaim RAM from boot.
- If you’re perpetually maxed, consider whether your next laptop needs 32GB — AI workloads are only growing.
- As a stopgap, increase the pagefile: System > Advanced > Performance Settings > Advanced > Virtual memory.
Fix 6: Use Game Mode and Focus sessions for demanding work
Rather than permanently disabling AI, let Windows deprioritize background work when it matters.
- Enable Game Mode: Settings > Gaming > Game Mode — it throttles background tasks during games.
- For creative work, close AI apps manually before starting (Game Mode doesn’t cover everything).
- Use Focus sessions (Clock app) to signal “don’t disturb” — some background AI activity pauses.
- Plug in for heavy tasks — Windows is less aggressive about background work on AC power, paradoxically making foreground apps smoother.
- After the demanding session, re-enable whatever AI features you value.
Closing
A laptop that’s slow “only sometimes” is usually a laptop doing invisible work — and on Copilot+ PCs, that work is often AI-related. Diagnose with Task Manager, then target the actual hogs: Recall snapshots, runaway indexing, and always-on Live Captions. You don’t have to choose between AI features and speed — scheduled, selective use gives you both. If the machine is slow even with every AI feature disabled and a clean Task Manager, look at thermals, startup bloat, or storage health next; the AI was a red herring.
