When Windows Search pushes your CPU up, the culprit is almost always the indexer, a background service that catalogs your files so searches come back instantly. Most of the time the spike is temporary and ends on its own. When it doesn't, the fixes are small and reversible: let the pass finish, shrink what gets indexed, restart the service, and rebuild the index only as a last step. This guide walks through each one in the order we'd try them on Windows 10 and 11.
TL;DR
- SearchIndexer.exe, SearchProtocolHost.exe and SearchFilterHost.exe are all parts of Windows Search. Short bursts of CPU use after you add many files are normal.
- Confirm the cause in Task Manager before changing anything. Then let indexing finish with the PC on and plugged in.
- If it keeps going, exclude big folders you never search, restart the Windows Search service, and check that your drive has free space.
- Rebuild the index only if Search is missing files or acting broken. A rebuild is itself CPU and disk heavy.
- Disabling indexing outright is a trade-off: search gets slower and results can be incomplete.
Table of Contents
- What the Windows Search processes actually do
- When high CPU from Search is normal
- Step 1: Confirm Windows Search is really the cause
- Step 2: Let one indexing pass finish
- Step 3: Shrink what gets indexed
- Step 4: Check disk space and restart the service
- Step 5: Rebuild the index, but only when you must
- When the cause isn't a normal indexing pass
- Should you just turn indexing off?
- Our perspective
- Where Tempered fits
- A quick checklist to keep it from coming back
- FAQ
- Sources
What the Windows Search processes actually do
Windows Search keeps a database of file names, properties and (for supported file types) contents. When you type in the Start menu or File Explorer, Windows reads that database instead of scanning your drive. The work of building it is split across a few processes you will see in Task Manager:
- SearchIndexer.exe is the main service host. It decides what to index and tracks changes.
- SearchProtocolHost.exe reads items from a location, such as a folder or an email store, on the indexer's behalf.
- SearchFilterHost.exe opens individual files and extracts their text and properties.
The indexer talks to the protocol host constantly while it works. Microsoft's developer documentation notes that if you stop the protocol host, the indexer simply launches a new instance. So ending SearchProtocolHost.exe in Task Manager is not a fix. It comes right back, and you've interrupted work the system was doing for a reason.
The indexer also runs in the LocalSystem account and stays running for all users, even when nobody is logged in. That design lets Windows maintain one shared index with consistent security rules. It also explains why you can see activity right after boot, before you've touched anything.
When high CPU from Search is normal
The indexer is designed to be polite. Microsoft's Windows team has described its "model citizen" approach: it should back off when other programs need resources. In practice, according to Microsoft's troubleshooting guidance, indexing slows while you're actively using the PC and pauses when battery power is low. The same page says indexing new files can take a few hours.
That means these situations are expected, not a bug:
- Right after a Windows upgrade or a fresh install. The index starts from zero.
- After you copy or sync a large batch of files. Think a photo library, a project archive, or a cloud folder that just finished downloading.
- After you add a new drive or folder to the indexed locations.
- After rebuilding the index. More on that below.
In these cases, one or two cores may run hot for a while, fans spin up, and then everything calms down. If it settles within a few hours of leaving the PC idle, you don't have a problem. You have an index being built.
The point where it becomes worth investigating: CPU stays elevated for days, it returns every time you log in, or search itself is slow and unreliable on top of the load.
Step 1: Confirm Windows Search is really the cause
Don't fix the wrong thing. Spend two minutes confirming.
- Press Ctrl + Shift + Esc to open Task Manager.
- On the Processes tab, click the CPU column header to sort highest first.
- Look for Microsoft Windows Search Indexer, SearchProtocolHost, or SearchFilterHost. On the Details tab they appear as searchindexer.exe and so on.
- Watch for a minute. A spike that fades is different from a flat, sustained line.
Microsoft's guidance says Task Manager can confirm whether searchindexer.exe is running, and the Windows Search settings page shows indexing status. Open it here:
- Windows 11: Settings > Privacy & security > Searching Windows
- Windows 10: Settings > Search > Searching Windows
The page shows whether indexing is in progress and roughly how many items are indexed. If it says indexing is running and the count is climbing, patience is the fix. If the status is stuck, or the page is greyed out, skip ahead to the section on persistent problems.
If the indexer isn't the top process at all, you're chasing the wrong thing. Our guide to finding the CPU hog in Windows 11 and the broader walkthrough on high CPU usage in Windows 11 cover the other usual suspects.
Step 2: Let one indexing pass finish
It sounds too simple, but it resolves most cases. Microsoft's advice is to let indexing finish with the computer on and, if applicable, connected to power. Because the indexer yields when you're busy, you get the fastest finish by leaving the PC idle.
Practical version for a laptop:
- Plug it in.
- Change nothing in the indexing settings.
- Leave it on, with the lid open or sleep disabled, for a few hours (an evening works).
- Check the Searching Windows page the next day.
If the status reads that indexing is complete and CPU is back to idle, you're done. Resist the urge to kill the process mid-pass. An interrupted pass just starts again and the cycle repeats.
Step 3: Shrink what gets indexed
The indexer's workload scales with the number of items. Microsoft says performance problems may begin when the indexer handles more than 400,000 items. A developer with node_modules folders, a photographer with a huge archive, or anyone who syncs a big cloud drive can cross that line without noticing.
The documented remedy is to exclude folders to reduce the number of indexed items or the index size.
To do it:
- Open Settings > Privacy & security > Searching Windows (Windows 10: Settings > Search > Searching Windows).
- Under Find My Files, choose Classic if you want the default behavior limited to libraries and the desktop. Enhanced indexes your whole PC and creates more work.
- Scroll to Excluded folders and add the heavy ones you never search by name: build output, virtual machine folders, backup copies, download caches, game libraries.
Or use the older route: search for Indexing Options in the Start menu, click Modify, and uncheck locations.
A good rule: index the places where you actually look for documents, mail and pictures. Skip anywhere that is mostly machine-generated.
What about Outlook and big mailboxes?
Email stores can be large and change constantly, which keeps the indexer busy. If your CPU spikes line up with Outlook being open, check how much mail is being indexed and consider trimming the indexed scope. The same principle applies as for folders: fewer, more relevant items means less work.
Step 4: Check disk space and restart the service
The indexer stalls or struggles when conditions are poor. Microsoft lists a busy device, low battery, insufficient memory or low disk space as reasons it slows or stops. The same page recommends making sure you have more than 1 GB of free disk space. If your system drive is nearly full, fix that first.
Then restart the Windows Search service, which the guidance recommends when indexing is paused or an external application has paused it:
- Press Win + R, type services.msc and press Enter.
- Find Windows Search in the list (the service name is wsearch).
- Right-click it and choose Restart.
- Confirm the Startup type is Automatic (Delayed Start) or Automatic. Don't set it to Disabled unless you've decided to turn search indexing off.
If the service refuses to start, or other services seem broken as well, our walkthrough on resetting Windows services safely shows how to recover without reinstalling Windows.
One warning from Microsoft: some third-party applications disable the Windows Search service, and the company recommends not running them if you want to use Search. If a "cleaner" or tweaker you installed turned the service off, that is probably why search is empty or erratic.
Step 5: Rebuild the index, but only when you must
A rebuild throws away the existing database and crawls everything again. Microsoft's Search platform team describes it as an expensive process for CPU and disk, though an effective fix when search isn't finding files correctly. Microsoft's troubleshooting page likewise says to rebuild when Search isn't working properly or isn't finding files it should.
So rebuild when search is broken, not just because CPU is high. If you do:
- Open Indexing Options from the Start menu.
- Click Advanced, then Rebuild under Troubleshooting.
- Confirm, then leave the PC plugged in and idle. Expect heavy CPU use at first and incomplete results until it finishes.
Do this in the evening, not before a meeting. Before you rebuild, trim your indexed locations (Step 3) so the new index starts smaller.
When the cause isn't a normal indexing pass
If the load never settles even after a rebuild, look at the symptoms.
| What you see | What it likely means | What to do |
|---|---|---|
| Indexer is busy for days, status shows items climbing | Very large or fast-changing set of files | Exclude folders, then let it finish |
| Searching Windows page is greyed out | Corrupted indexer registry keys or database, per Microsoft | Restart the service, then rebuild the index |
| Constant disk activity along with CPU | The indexer may be recovering the database or reacting to a disk write problem | Check the drive's health and free space |
| Search works fine but the PC feels slow anyway | Something else is the real load | Check startup apps and the top CPU process |
The second and third rows come straight from Microsoft's troubleshooting page, which says a greyed-out status page can indicate corrupted indexer registry keys or database and that maintenance activity may be database recovery or a response to a disk-writing problem, so check for disk failures. If a drive is genuinely failing, back up your data before doing anything else. The CPU load is a symptom, not the disease.
Other services can also look like search trouble. If your top process is Explorer, Defender or OneDrive rather than the indexer, see our guides on Explorer.exe high CPU, Antimalware Service Executable and OneDrive high CPU. A synced cloud folder is a common reason the indexer has so much to chew on in the first place.
Should you just turn indexing off?
You can, and some people on slow hard drives or old laptops do. But know what you're giving up. Microsoft notes that when indexing is paused, search results may be incomplete. File Explorer searches fall back to scanning folders live, which is slower and can use CPU in its own way during the search.
A middle path works better for most people:
- Exclude the folders that bloat the index.
- Use Classic rather than Enhanced mode.
- Leave the service on Automatic (Delayed Start).
If you still want to go all the way, our guide to disabling search indexing, tuning it and keeping Search usable lays out the options, including how to undo each one.
Our perspective
We see the same pattern again and again with Windows Search complaints. Someone sees a process at 25 percent CPU, searches for how to kill it, and lands on advice to disable services, edit the registry, or run a one-click cleaner. The indexer then gets switched off, search gets worse, and the original question (why was the PC slow?) never gets answered.
Our view is that a spike is a clue and not a verdict. SearchIndexer.exe is usually doing legitimate work, and the interesting question is why it has so much to do: too many items, a folder that changes constantly, a nearly full drive, or a disk that is struggling. Measure first, change one thing, and keep a way back.
That is how we built Tempered. It reads live CPU, RAM, GPU and disk numbers, explains in plain language what looks like a real constraint, and proposes specific changes that only happen after you approve them. We don't clean the registry or invent problems to look busy, and every change is logged with a one-click undo. For a case like this one, that means seeing whether Search is truly the bottleneck before you touch a service.
— Ian
Where Tempered fits
If you'd rather not step through Task Manager, Services and Indexing Options by hand, Tempered does the diagnosis for you. It looks at live CPU, RAM, disk and uptime, tells you which process is actually responsible, and suggests changes such as trimming startup items or managing background processes. Nothing is applied without your approval, and each change can be reversed.
There is a Free plan with limited AI scans, which is plenty to check whether Search is your real problem. Torque starts at $5.99 per month and Torque Max at $12.99 per month, with higher scan limits and more features. You can compare them on the Tempered pricing page. No AI API key and no technical background are required.
A quick checklist to keep it from coming back
- Keep at least a few gigabytes free on your system drive, and well above Microsoft's 1 GB floor.
- Exclude build folders, VM images and backup copies from indexing.
- After moving or syncing a huge folder, leave the PC idle and plugged in overnight.
- Avoid utilities that disable the Windows Search service unless you've decided to give up indexed search.
- Rebuild the index only when search returns wrong or missing results.
FAQ
Is it safe to end SearchIndexer.exe in Task Manager?
It won't harm Windows, but it rarely helps. The service restarts on its own, and the protocol host that supports it is relaunched as soon as you stop it. If you need a pause, restart the Windows Search service from Services, or fix the underlying cause by excluding folders.
Is SearchIndexer.exe a virus?
The genuine file is part of Windows and runs under the system account. If you want to double-check, right-click the process in Task Manager and choose Open file location. The real one lives in the Windows System32 folder. If it is elsewhere, run a full scan with Windows Security.
How long should indexing take?
Microsoft says indexing new files can take a few hours. A big library or a fresh install can take longer, and it goes faster when the PC is idle and plugged in. If activity continues for days with no growth in the item count, move on to restarting the service and checking disk health.
Does Windows Search indexing wear out an SSD?
Normal indexing is a light, mostly read-heavy workload, and we haven't found official guidance that says it meaningfully shortens an SSD's life. The more practical concern is a rebuild or a failing disk driving constant activity. If you see sustained disk use, check the drive's health first.
Why does the indexer run when I'm not logged in?
It is a system-wide service that runs under the LocalSystem account so everyone on the PC shares one index. That is by design, and it is why activity can show up soon after startup.
Sources
- Troubleshoot Windows Search performance, Microsoft Learn
- Debugging protocol handlers, Microsoft Learn
- Windows Search overview, Microsoft Learn
- Windows Desktop Search, Engineering Windows 7 blog archive
- Configuration and Settings, Windows Search Platform blog