How to Stop Search Indexer From Maxing Out the Disk on Windows 11

Quick fix: Open Control Panel → Indexing Options → Modify. Untick large folders that generate constant churn (node_modules, build outputs, OneDrive cache). Then Advanced → Rebuild. After rebuild, indexer settles to baseline. For permanent low-CPU: disable Windows Search service entirely if you don’t use Start menu/File Explorer search.

Task Manager shows Microsoft Windows Search Indexer (SearchIndexer.exe) using 30–80% disk for hours. PC slows down. Indexer is scanning thousands of files for full-text indexing. On dev machines with constantly-changing files, this never finishes — it just keeps indexing.

What causes this

Windows Search Indexer scans indexed locations for new/changed files, then extracts metadata (filename, modified date) and content (text within supported formats) into the search database. On stable folder trees, it’s quiet. On folders with constant changes (project builds, sync folders, cache folders), it can’t keep up — new files arrive faster than indexing completes.

Method 1: Exclude high-churn folders

The targeted fix.

1. Open Control Panel → Indexing Options.
2. Note the total indexed items count. If >200,000, indexing is overloaded.
3. Click Modify. Untick:
   • node_modules folders
   • build, dist, target output folders
   • %LocalAppData% subfolders (large caches)
   • %AppData% if not needed (Outlook signatures, etc., may need this)
   • OneDrive cache folders
   • Visual Studio output directories
   • Steam library and game directories
4. Click OK. Indexer trims its database over next minutes/hours.
5. Click Advanced → Rebuild. Forces a fresh start with the smaller scope. Takes 30 min–2 hours.
6. After rebuild, total items should be under 100,000 for typical Office use.
7. Indexer CPU should drop to single-digit percentages when idle.

This is the standard targeted fix.

Method 2: Throttle indexer’s background priority

For when exclusions aren’t enough.

1. Indexer runs at Background priority by default. To verify or change: Settings → Privacy & security → Searching Windows. (Path may vary by build.)
2. Set Find my files to Classic mode — indexes only Documents, Pictures, Music, Videos, Desktop. Less aggressive than Enhanced.
3. In Advanced indexing options: limit indexer to specific times if possible. Some Windows builds let you schedule indexing to off-hours.
4. For PowerShell-based throttling: stop the service during work hours, start at night:

   Stop-Service WSearch
   # work hours pass...
   Start-Service WSearch

   Automate via Task Scheduler.

5. For drives where you don’t want indexing at all: right-click drive in File Explorer → Properties → General tab → untick Allow files on this drive to have contents indexed.

Throttling reduces CPU impact during productive hours.

Method 3: Disable Windows Search service entirely

For power users who use third-party search.

1. Open Services (services.msc). Find Windows Search. Right-click → Properties.
2. Set Startup type to Disabled. Click Stop. Apply.
3. Service is now off. Indexer stops; no CPU/disk overhead.
4. Side effect: Start menu search may be slower (still works via in-memory mini-index). File Explorer search uses live disk scan (slow but accurate).
5. For instant filename search: install Everything from voidtools.com. Uses NTFS MFT for near-instant filename search without indexing daemon.
6. For content search needs: use DocFetcher or per-app search (Outlook, OneNote).
7. To re-enable: set Startup type back to Automatic (Delayed Start).

This is the right path for users who don’t rely on Windows Search.

How to verify the fix worked

• Task Manager → Performance → Disk. SearchIndexer drops below 5% disk usage when idle.
• Indexing Options shows item count reduced — ideally under 100,000.
• If service disabled: Get-Service WSearch shows Stopped.

If none of these work

If indexer still spikes after exclusions and rebuild: Antivirus scanning indexer’s files: AVs may scan files indexer reads — doubling I/O. Add C:\ProgramData\Microsoft\Search\ to AV exclusion list. OneDrive sync conflicts: OneDrive marks files as offline-only, but indexer tries to read content. Cloud-only files cause download attempts. Mark frequently-indexed OneDrive folders as Always keep on this device, or exclude OneDrive folders from indexing. Failing SSD: indexer’s constant reads stress disk. Failing drives respond slowly, making indexer take longer than expected. Run CrystalDiskInfo. For PCs with HDDs not SSDs: indexing on HDD is fundamentally slow. With 500,000+ files, may never settle. Either upgrade to SSD or disable Windows Search. For shared/networked drives indexed: each scan reads over network — slow and continuous. Exclude network locations from indexing.

Bottom line: Indexing Options → Modify → untick high-churn folders. Rebuild for clean baseline. Disable Windows Search service entirely if you don’t use Start menu/File Explorer search.