SearchIndexer.exe is one of those processes you never notice until it ruins your day. On HP laptops it has a habit of pinning the CPU at 40, 60, even 90 percent for hours — fans blaring, battery melting — all in the name of making your file searches a fraction of a second faster. The tradeoff is not worth it when the indexer never finishes.

The indexer is supposed to do one big initial pass and then quietly track changes. When it loops forever, the cause is almost always a corrupted index database or a folder it should never have been asked to index — a network drive, a massive code repository, or a constantly changing sync folder. HP’s bundled software adds thousands of extra files to the pile.

Here is how to find out what the indexer is choking on, rebuild the database cleanly, and shrink its workload so it stays quiet.

Why this happens

  • Corrupted index database: The most common cause of endless indexing — the database is damaged, so the indexer restarts its pass forever.

  • Huge or unsuitable folders indexed: Network drives, developer repos with hundreds of thousands of files, and VM folders overwhelm the indexer.

  • Constantly changing sync folders: OneDrive or Dropbox folders that change every few minutes force perpetual re-indexing.

  • Outlook PST/OST files: Large mail archives are expensive to index and re-index on every mail sync.

  • Post-update re-index: Major Windows updates invalidate the index and trigger a full rebuild that can take hours.

  • HP preinstalled software bloat: Recovery partitions and bundled suites add tens of thousands of files the indexer dutifully catalogs. Trimming startup and background load generally helps too — see how to disable startup programs in Windows 11 .

  • Disk errors interrupting the index: Bad sectors in indexed areas cause the indexer to retry and restart its scan repeatedly.

How to fix it

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

Fix 1: Check what the indexer is actually doing

Before rebuilding anything, confirm the indexer is the problem and see whether it is making progress or stuck.

  1. Open Settings, Privacy and security, Searching Windows.
  2. Look at the indexing status line — it shows whether indexing is in progress and how many items are indexed.
  3. Note the item count, wait 15 minutes, and check again — a rising count means progress; a frozen count means stuck.
  4. Click ‘Advanced indexing options’ (or open Indexing Options from Control Panel) to see exactly which folders are included.
  5. Open Task Manager and confirm SearchIndexer.exe matches the CPU spike.

Fix 2: Exclude folders the indexer should never touch

Shrinking the indexer’s workload is the highest-leverage fix. Every folder you exclude is thousands of files it never has to scan again.

  1. Open Indexing Options from Control Panel.
  2. Click Modify and expand the folder tree.
  3. Uncheck network drives, external drives, and any developer or VM folders.
  4. Uncheck OneDrive or Dropbox folders if they change constantly — or pause sync during the fix.
  5. Uncheck HP recovery partitions and program folders you never search.
  6. Click OK and give the indexer 30 minutes to settle — CPU should start dropping.

Fix 3: Rebuild the index from scratch

When the database is corrupted, no amount of excluding folders helps. A rebuild creates a clean database and ends the loop.

  1. Open Indexing Options and click Advanced.
  2. On the Index Settings tab, click Rebuild under Troubleshooting.
  3. Confirm the prompt — the current index is deleted and rebuilt.
  4. Plug the laptop into AC power and let the rebuild run for several hours, ideally overnight.
  5. Expect high CPU during the rebuild; this is normal and temporary.
  6. When the status shows ‘Indexing complete’, verify SearchIndexer.exe idles near zero.

Fix 4: Limit Outlook and file-type indexing

Email archives and exotic file types are the most expensive things the indexer processes. Trimming them cuts rebuild time dramatically.

  1. In Indexing Options, click Advanced, then the File Types tab.
  2. Uncheck file extensions you never search — old archives, disk images, obscure formats.
  3. In Outlook, go to File, Options, Search, Indexing Options, and consider excluding the OST if mail search speed is acceptable.
  4. Alternatively, in Outlook’s Search options, reduce the indexed mail range.
  5. Restart the Windows Search service: Win plus R, services.msc, restart ‘Windows Search’.
  6. Monitor CPU over the next hour to confirm the improvement.

Fix 5: Restart and repair the Windows Search service

Sometimes the service itself is wedged rather than the database. A clean restart with repaired system files fixes the wedge.

  1. Press Win plus R, type services.msc, and press Enter.
  2. Find Windows Search, right-click, and choose Restart.
  3. If it will not restart cleanly, set Startup type to Automatic (Delayed Start) to reduce boot competition.
  4. Run sfc /scannow in an admin Command Prompt to repair underlying system files.
  5. Check HP Support for your model’s latest chipset and storage drivers, which affect indexer I/O.
  6. Restart the laptop and recheck indexer behavior.

Fix 6: As a last resort, disable indexing selectively

If you genuinely never use Windows search, disabling the service ends the CPU drain permanently — but understand the tradeoff first.

  1. In services.msc, double-click Windows Search.
  2. Change Startup type to Disabled and click Stop.
  3. Test Start menu and File Explorer search — they will be noticeably slower.
  4. If the tradeoff is unacceptable, re-enable the service and return to the exclusion strategy in Fix 2.
  5. A middle path: keep the service on but index only the Start Menu and Users folders.
  6. For the indexer variant that hits hardest after updates, see SearchIndexer high CPU in Windows 11 24H2 .

Closing

A healthy search indexer is invisible — it finishes its pass and goes quiet. If yours never stops on your HP laptop, the index is almost certainly corrupted or pointed at folders it cannot handle. Rebuild it, shrink its territory, and searches stay fast while your CPU finally gets some peace.

Frequently asked questions

Why is Windows Search Indexer using so much CPU?
The indexer is re-scanning your files to build the search database. High CPU is normal for a few hours after a fresh install or major update, but if it never stops, the index is usually corrupted — or it is indexing a huge folder like a network drive or developer repo.
Can I just disable Windows Search indexing?
You can, but Start menu and File Explorer searches become slow. A better middle ground: keep indexing on but exclude huge folders, so the indexer finishes quickly and stays quiet. Only disable the service entirely if you never use Windows search.
How long does rebuilding the search index take?
Typically 30 minutes to several hours, depending on how many files you have — large photo libraries and mail archives extend it. Let it run overnight with the laptop plugged in and the lid open. CPU will be high during the rebuild, which is expected and temporary. When Settings reports ‘Indexing complete’, usage should drop to near zero.
Does HP software make indexing worse?
Not deliberately, but HP laptops ship with big recovery partitions and bundled suites containing tens of thousands of files, all of which the indexer dutifully catalogs. Excluding the HP recovery partition and program folders you never search trims the index substantially. It is a one-time change in Indexing Options that pays off permanently.