How to Fix High NPU Usage by Windows Search on Your AI PC

You open Task Manager and the NPU graph is pinned high — not by a game or an AI app you launched, but by Windows Search, quietly working in the background. The laptop feels warm, the fan spins up for no visible reason, and battery life drops. You did not ask Search to do anything, yet it is consuming the AI chip as if it were rendering video.

On Copilot+ PCs, Windows Search does more than match filenames. It uses the NPU for semantic indexing: reading your documents, emails, and photos so you can later search by meaning — “invoices from March” or “beach photos” — rather than exact words. That is useful, but when the indexer gets stuck, corrupted, or overwhelmed, it turns into a permanent background load.

This guide shows you how to tell normal indexing from a stuck indexer, then stop the runaway usage without breaking search. Work through the fixes in order, and check Task Manager’s NPU graph after each step.

Why this happens

• Semantic indexing backlog: After a feature update, a large file import, or a fresh setup, Search has thousands of files to analyse with the NPU, and that backlog can look like runaway usage for hours.
• Stuck or looping indexer: A single corrupted file, a locked mailbox, or a damaged index entry can make the indexer retry the same item forever, pinning the NPU.
• Corrupted search index: If the index database itself is damaged, Search reprocesses files it already indexed, creating a cycle of repeated NPU work that never finishes.
• Too many indexed locations: Indexing entire drives, network folders, or cloud-synced folders multiplies the NPU workload far beyond the default Documents and Desktop scope.
• Semantic search enabled on a huge library: A large photo or document library gives the NPU’s semantic models far more content to embed, and that work continues long after filename indexing is done.
• Conflicting third-party search tools: Another indexer or desktop search app competing for the same files can force Windows Search to re-index constantly as files appear to change.

How to fix it

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

Fix 1: Confirm Search is the culprit and let a healthy backlog finish

Do not disable features for a backlog that would finish on its own. First prove that Search — not another process — is using the NPU, and give a legitimate backlog a bounded chance to complete. This diagnosis takes five minutes and prevents unnecessary surgery on a healthy system.

1. Open Task Manager > Performance > NPU and note the utilisation, then open Processes and sort by NPU to find the top consumer.
2. Confirm the top process is SearchIndexer, SearchHost, or Microsoft Windows Search — if it is another app, that app is your problem, not Search.
3. Note the time and leave the laptop plugged in and awake for 30 minutes without opening new files.
4. Recheck the NPU graph: if usage falls steadily, the indexer was working through a backlog — let it finish and skip to the prevention advice in Fix 5.
5. If usage stays pinned high with no decline after 30 minutes, the indexer is stuck — move to Fix 2.

Fix 2: Restart the Windows Search service cleanly

A stuck indexer often clears with a clean service restart, which drops its in-memory state without touching your index or settings. It is the fastest fix for a loop that started after sleep, an update, or a crashed app. A similar service-restart logic helps other background hogs, and the same careful process check applies when a Copilot key stops working after a BIOS update — confirm the process before changing settings.

1. Press Windows + R, type services.msc, and press Enter.
2. Find Windows Search in the list, right-click it, and choose Restart.
3. Wait 60 seconds, then check Task Manager’s NPU graph to see whether Search usage drops to near zero.
4. Try a test search from the taskbar to confirm search still returns results after the restart.
5. If usage spikes again within minutes and stays high, the index itself is likely damaged — continue to Fix 3.

Fix 3: Rebuild the search index from scratch

When restarting the service does not help, the index database is the prime suspect. Rebuilding it deletes the corrupted database and creates a clean one, which ends retry loops and duplicate processing. The rebuild takes time, but it is the definitive cure for a damaged index — just schedule it when you do not need instant search.

1. Open Settings > Privacy & security > Searching Windows and scroll to Advanced indexing options (or open Control Panel’s Indexing Options directly).
2. Click Advanced, then under Troubleshooting click Rebuild and confirm.
3. Plug in the charger and leave the laptop awake; the rebuild re-indexes your files and will use the NPU heavily while it runs — that temporary load is normal.
4. Check progress in Indexing Options: wait until it reports indexing complete, which can take several hours on a large library.
5. After completion, monitor Task Manager for a full day; a healthy rebuilt index should leave Search NPU usage near zero when you are not actively searching.

Fix 4: Narrow the indexed locations and exclude problem folders

An index that covers everything will always work harder than one that covers what you actually search. Network drives, cloud-synced folders, and huge media libraries are the biggest multipliers, and excluding them cuts NPU work dramatically without affecting everyday search. This is also where a runaway library behaves like a misbehaving app — compare the pattern with Battle.net issues on ARM Windows , where scope and compatibility, not raw power, decide the outcome.

1. Open Indexing Options and click Modify to see every location currently indexed.
2. Untick network locations, external drives that are not always attached, and cloud folders you rarely search by content.
3. Keep the defaults — user folders such as Documents, Pictures, and Desktop — and add back only folders you genuinely search often.
4. In Settings > Privacy & security > Searching Windows, review Excluded folders and add any huge folder that repeatedly triggers re-indexing, such as a photo archive or a development folder.
5. Click OK, restart the Windows Search service as in Fix 2, and watch NPU usage over the next hour for a clear drop.

Fix 5: Update drivers and prevent the next indexer loop

A healthy index can still be dragged down by a stale NPU or chipset driver that mishandles the AI workload, or by a third-party tool fighting Search for the same files. Closing those two gaps prevents the problem from returning after the next feature update. If AI camera features are also misbehaving, a related symptom is covered in Copilot app widget problems — keep the diagnoses separate so one fix does not mask another.

1. Download the latest NPU and chipset drivers for your exact model from Dell , HP , or Lenovo support, install them, and restart.
2. Open Settings > Windows Update and install pending updates, since Search and NPU fixes often ship together in cumulative updates.
3. Uninstall or pause any third-party desktop search tool, then watch Search NPU usage for a day to see if the conflict was the trigger.
4. Keep indexed locations narrow (Fix 4) and avoid indexing removable drives that vanish and reappear, which forces repeated re-indexing.
5. If high usage ever returns, start again at Fix 1 — a five-minute check will tell you whether it is a fresh backlog or another stuck loop.

Closing

Windows Search using the NPU is normal — it is how semantic search works — but pinned, endless usage is not. Prove it is Search, restart the service, rebuild a damaged index, narrow what gets indexed, and turn off semantic search if you do not use it, and the NPU should return to near-idle when you are not searching.

Frequently asked questions