Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsMicrosoft Windows Search Indexer (SearchIndexer.exe) can spike CPU when Windows is crawling new files, repairing an index, or encountering a file/folder that it can’t index cleanly. In 2024, this is most often triggered after Windows updates, storage changes, new external drives, or when the index becomes inconsistent.
This guide walks you through a reliable, step-by-step fix workflow: confirm the real culprit, apply quick remediations, restart Windows Search properly, rebuild the index when needed, and then tune indexing scope to prevent repeat spikes.
As an Amazon Associate I earn from qualifying purchases.
Use the steps in order. If you already know you need a rebuild, you can jump to that section—but even then, do the quick checks first to avoid redoing work unnecessarily.
What causes Search Indexer high CPU usage on Windows
High CPU usage is usually a symptom of one of these scenarios: heavy indexing work, an index that needs repair, an indexing loop caused by changing files, or a problematic data source (e.g., a network share, a failing disk, or a corrupted file).
#1 Best Overall
- Get NVMe solid state performance with up to 1050MB/s read and 1000MB/s write speeds in a portable, high-capacity drive(1) (Based on internal testing; performance may be lower depending on host device & other factors. 1MB=1,000,000 bytes.)
- Up to 3-meter drop protection and IP65 water and dust resistance mean this tough drive can take a beating(3) (Previously rated for 2-meter drop protection and IP55 rating. Now qualified for the higher, stated specs.)
- Use the handy carabiner loop to secure it to your belt loop or backpack for extra peace of mind.
- Help keep private content private with the included password protection featuring 256‐bit AES hardware encryption.(3)
- Easily manage files and automatically free up space with the SanDisk Memory Zone app.(5). Non-Operating Temperature -20°C to 85°C
Common triggers in 2024 Windows builds
- Windows feature or cumulative updates (Search index can revalidate content after upgrades).
- New storage (new SSD/HDD, external USB, SD card, or mapped drives).
- Large file ingestion (photo libraries, mail archives, source code repos, or PST expansion).
- Index corruption (Search Indexer keeps reprocessing items).
- Content changes during indexing (sync tools, databases writing frequently, camera imports).
- Third-party filter/codec issues (often impacts whether files can be indexed efficiently).
Before you change anything: confirm the culprit and capture evidence
Before you rebuild the index, confirm that Search Indexer is truly the top CPU consumer and capture a snapshot. This helps you avoid unnecessary index resets when the real issue is elsewhere.
Step 1: Identify the high-CPU process
- Right-click the taskbar > Task Manager.
- Click the Processes tab.
- Click the CPU column to sort by usage.
Look for SearchIndexer.exe. If another process is higher (e.g., Microsoft Defender, a sync client, a backup agent), address that first.
Step 2: Confirm it’s indexing right now
- Open Resource Monitor: press Win + R, type
resmon, press Enter. - Go to the CPU tab.
- In the associated handles/search fields, identify if SearchIndexer is working on file reads/writes.
If CPU is high but disk reads/writes are low, suspect an indexing loop or an indexing task stuck on specific items.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Step 3: Check Windows Search status
- Press Win + R, type
services.msc, press Enter. - Find Windows Search.
- Confirm Status is Running.
- Confirm Startup type is Automatic.
If Windows Search is stopped, you may see other symptoms later (slow search, repeated CPU spikes when it retries).
Quick fixes that usually work (5–15 minutes)
Start with low-risk changes. These often stop the indexing loop caused by recently changed content.
1) Restart Windows Search service
- Press Win + R, type
services.msc, press Enter. - Right-click Windows Search > Restart.
- Wait 5–10 minutes and re-check Task Manager CPU.
After a restart, indexing may briefly spike while it resumes, but it should eventually settle.
2) Reboot the PC
A full restart clears transient indexing tasks and can stop concurrent operations (sync, backups) from thrashing the search pipeline.
Recommended Free Tools
3) Let indexing run on battery/power-aware systems
If you’re on a laptop, check power mode settings. Some systems behave more aggressively when power is limited or when the device rapidly changes power states.
Rank #2
- Solid state performance with up to 800MB/s read speeds in a portable drive. (Based on internal testing; performance may be lower depending on host device, interface, usage conditions and other factors. 1MB=1,000,000 bytes.)
- Back up your content and memories on a storage solution that fits seamlessly into your mobile lifestyle.
- Take it with you on your adventures—up to two-meter drop protection means this durable drive can take a beating. (Based on internal testing.)
- Secure it to your belt loop or backpack for extra peace of mind thanks to the tough rubber hook.
- From Sandisk, a brand professional photographers trust to take on assignments.
4) Temporarily pause heavy file-changing apps
Pause tools that constantly write to disk (sync clients, large downloads, continuous backup agents, database systems). Watch Task Manager for CPU to drop over 10–30 minutes.
Restart and reset Windows Search components (safe sequence)
If a simple restart didn’t help, perform a controlled restart sequence. This is safer than immediately rebuilding because it resets active indexing tasks without destroying the index data.
Step-by-step: restart core services
- Open Services (
services.msc). - Stop Windows Search.
- Stop Background Intelligent Transfer Service (BITS) only if it’s tied to searching/indexing activity in your environment. If unsure, skip this step.
- Start Windows Search again.
- Wait 10 minutes, then check CPU.
If SearchIndexer spikes immediately and steadily climbs without easing, move to index rebuild.
Verify Windows Search is configured correctly
- In
services.msc, open Windows Search properties. - Set Startup type to Automatic.
- Set Service status to Running.
- Click Apply and OK.
Rebuild the search index (most common durable fix)
Rebuilding forces Windows to recreate the index from scratch using the current indexing locations and settings. This is the most reliable solution when the index is corrupted or stuck in a loop.
Rebuild using Indexing Options
- Press Win + S, type Indexing Options, open it.
- Click Advanced.
- Under Index Settings, find Troubleshooting.
- Click Rebuild.
- Confirm the prompt.
On large libraries (tens or hundreds of thousands of files), a rebuild can take hours. CPU may rise during this time. If you can, start this before you’re away from the PC.
Alternative: Reset search index
Depending on the Windows version, you may see an option to Reset. Reset is effectively a full wipe-and-recreate of index data. Use it if rebuild isn’t available or if you’ve already narrowed the scope and still see persistent CPU loops.
Control what gets indexed to stop future CPU spikes
The best way to prevent repeat high CPU is to reduce what Windows must index and what changes continuously. You can do this without disabling search completely.
Remove locations that don’t need indexing
- Open Indexing Options.
- Click Modify.
- Uncheck folders that you don’t need for search (e.g., large temp folders, game libraries, build output directories).
- Click OK and let it apply changes.
If your CPU spikes are triggered by a specific directory (like a development workspace), unchecking it can help immediately.
Rank #3
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Use folder-level exclusions (more targeted)
Some folders are better excluded directly rather than by broad category. Exclude the path that’s constantly changing or contains huge numbers of similar files.
Common high-churn folders include downloads while actively downloading, node_modules, build caches, and application log folders.
Exclude file types that cause expensive indexing
If Indexer is chewing through media files you don’t query often, excluding file types can reduce CPU. Availability depends on Windows edition and current UI options in Indexing Options.
If you don’t see controls for file types, stick with location exclusions first; it’s the most consistent across Windows setups.
Advanced troubleshooting when rebuild doesn’t fix it
If the CPU problem persists after rebuild, you’re likely dealing with an underlying content source issue (network share, permissions, corrupted files) or a system component interaction problem.
1) Check for indexing errors in Event Viewer
- Press Win + R, type
eventvwr.msc, press Enter. - Go to Windows Logs > Application.
- Filter for sources like Windows Search and events that mention indexing.
Look for repeated errors around SearchIndexer activity. If the same path shows up repeatedly, exclude that location and rebuild.
2) Repair system files (SFC + DISM)
Corrupted system components can break search indexing behavior. Run these from an elevated Command Prompt.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →- Press Win, type cmd, right-click Command Prompt > Run as administrator.
- Run:
sfc /scannow - If needed, run:
DISM /Online /Cleanup-Image /RestoreHealth - Reboot and re-check CPU.
3) Update Windows and indexing-related components
Search behavior has been improved over time via cumulative updates. In 2024, staying current often resolves indexing loops tied to specific builds.
Rank #4
- NEARLY 2X FASTER THAN OUR PREVIOUS GENERATION(8) – move 1,000 high-res photos in under 60 seconds(6) with up to 2000MB/s transfer speeds(2).
- IP65 RATING AND UP TO 3M DROP PROTECTION(3) – protects against spills and drops.
- POCKET-SIZED – fits easily in pockets and small bags.
- SPACE TO OWN YOUR AI CONTENT – speed and capacity to download your high-res clips and photo edits.
- 256-BIT AES ENCRYPTION(4) – helps keep private files secure with password protection.
- Open Settings > Windows Update.
- Click Check for updates.
- Install all available updates, then restart.
4) Check disk health (search can thrash on failing storage)
If storage has read errors, indexing may repeatedly retry. Check drive health and ensure you’re not seeing SMART warnings.
At minimum, run chkdsk for the drive that holds your index locations (be careful and schedule it if needed).
When the problem is actually not indexing: look for misbehaving filters and malware
Search Indexer can spend CPU time indexing because another layer is slowing or interfering with file access—especially third-party add-ons that hook into file processing.
Free tools Windows power users keep installed
One-click scans. No signup required.
Identify third-party interference
- Recent installs: document viewers, preview handlers, OCR tools, media codecs, backup tools.
- Browser/launcher downloads: add-ons that create background extraction folders.
If you installed something right before the issue started, test by temporarily uninstalling it and then rebuilding the index.
Run a full Microsoft Defender scan
- Open Windows Security.
- Go to Virus & threat protection.
- Run Full scan.
If malware is present, indexing can repeatedly process or fail on generated/modified artifacts, creating persistent CPU spikes.
Performance expectations: what is normal after fixes
After a restart or rebuild, Search Indexer commonly shows higher CPU for a period. This can last longer on systems with large local libraries, slow HDDs, or many small files.
- If indexing is progressing, CPU should gradually stabilize after an initial ramp-up.
- If CPU remains high indefinitely without progress, that points to a loop (bad folder, permission errors, or index corruption).
- If you frequently modify indexed folders (sync/downloads), periodic CPU spikes may return even after a successful rebuild.
Common mistakes that make Indexer worse
- Rebuilding repeatedly without giving it time to finish. Most first rebuilds need hours.
- Indexing continuously changing folders (Downloads during active sync/download, build output directories).
- Including network shares without stable availability. If a share is intermittent, indexing retries can get expensive.
- Disabling Windows Search entirely as the first attempt. This often breaks search across Start menu and system apps and may reduce your productivity more than it solves CPU.
Alternatives to full indexing (if you just need faster search)
If your priority is fast search over a limited set of locations, you can keep indexing enabled but narrow it down sharply.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallLimit indexing to core folders
Index typical personal locations (Documents, Pictures, Desktop) and avoid volatile directories. This reduces CPU while preserving search usefulness for everyday files.
Best Value
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Use targeted search results instead of full crawling
Windows Search still benefits from indexing, but with fewer indexed locations you can accept less coverage for greater stability. If you mostly search within one drive (e.g., Projects), index only that drive’s relevant folders.
FAQs
Why is SearchIndexer.exe using 100% CPU even after I rebuild?
If CPU stays pegged, you likely still have a problematic indexed location, permission issue, or continuous file churn. Check Event Viewer for repeated indexing errors and then exclude the offending path. Also verify that indexed locations aren’t on a network share with intermittent access.
Can I disable Windows Search to stop Search Indexer CPU usage?
You can stop or disable the Windows Search service, but it will affect system search features (Start menu and many app searches rely on it). Prefer reducing indexed locations instead of fully disabling if your goal is CPU stability.
How long should indexing take after a rebuild?
It varies heavily based on file count and storage speed. On a moderately sized library, it can be a few hours. On very large collections (especially many small files), it can take most of a day.
Will indexing consume CPU even when I’m actively using the PC?
Often yes. Indexing is designed to run in the background, but it may compete for CPU and disk. If you must keep performance stable, reduce indexed scope, exclude volatile folders, and consider running heavier rebuilds when you’re not downloading or syncing.
Does Windows update fix Search Indexer high CPU issues?
Sometimes. Search and indexing improvements are delivered via cumulative updates. Updating Windows first can help if the issue started right after an OS update.
Bottom Line
When Search Indexer spikes CPU on Windows in 2024, the fix is usually a combination of confirming the culprit, restarting Windows Search, rebuilding the index if corruption is suspected, and then tightening what gets indexed to prevent repeat churn.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →If rebuild doesn’t stabilize CPU, pivot to Event Viewer and storage/permission checks—those are the fastest ways to find the single folder or condition that keeps the indexer in a loop.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
