Flamingo Raises $4.5M Seed Round · Led by Vertex Ventures, bringing total funding to $6.7M to build the open, AI-native layer for IT and security.
"Fae" Grace Meadows
SearchIndexer.exe at the top of Task Manager is usually doing what it was told. What the Windows Search Indexer does, the four causes of a spike, how to rebuild and trim the index, and the narrow set of machines where turning it off is the right call.
A user reports a fan that never stops, Task Manager shows Microsoft Windows Search Indexer near the top, and the first forum answer says to switch it off. That fix trades a busy hour for a slow Start menu, a slow File Explorer and a broken Outlook search. This guide covers what the Windows Search Indexer does, why it spikes, how to rebuild or trim it, and when disabling it is the right call.
The indexer is a catalog. It reads the files and mail in the locations you tell it to watch, pulls out names, properties and text, and writes all of it into one database. When someone types into Start, File Explorer or classic Outlook, Windows reads the catalog instead of opening every file on the disk.
Three processes do the work. The Windows Search service, short name WSearch, runs SearchIndexer.exe, which owns the database and decides what gets read next. SearchProtocolHost.exe opens each location, whether a folder, a mailbox or a synced library. SearchFilterHost.exe runs the filters that turn a PDF or a Word file into plain text. When Task Manager shows the indexer busy, one of those three is doing the reading.
The catalog lives in C:\ProgramData\Microsoft\Search\Data\Applications\Windows. On Windows 10 the file is Windows.edb; on Windows 11 it is Windows.db, a SQLite database that replaced the old ESE format. Microsoft's search performance guide, updated February 2026, says to judge its size by Size on disk in the file's properties, because Explorer's size column misreads the sparse file.
The indexer is built to get out of the way. When disk or CPU use is high, it stops so the foreground work wins, and it pauses on low battery. That backoff is why a healthy indexer shows "Indexing speed is reduced because of user activity" rather than pinning a core all day.
A busy indexer is usually doing something it was told to do. Microsoft's own numbers draw the line between normal and too much. A typical user's machine indexes fewer than 30,000 items, a power user's up to 300,000, and performance problems start above 400,000. The hard limit is about 1 million, and past it the indexer "may fail or cause resource problems". A single Outlook mailbox above 6 million items degrades it too.
Check the count before anything else. On Windows 11 it is under Settings, Privacy & security, Searching Windows, in the Indexed line. A number in the hundreds of thousands tells you the ticket is about scope, not a bug.
Four causes cover nearly every spike.
The first index after a change. A feature update, a new profile or a migration to a new laptop means the catalog starts from zero. Expect hours of work, and Microsoft's guidance is to let a full rebuild run for up to 24 hours before judging it.
Outlook data files. Classic Outlook hands its OST and PST files to Windows Search, and a big cached mailbox is the single largest thing on most office PCs. The r/sysadmin thread below is the extreme version: a 37 GB IMAP OST, more than 400,000 items, and full rebuilds that came back after a clean Windows install. One reply suggested checking the Search operational log for SYSTEM permissions, and another pointed at the cache window, which that admin keeps at 30 days.
Huge or fast-changing folders. A synced SharePoint or Teams library, a developer's build folder or a log directory that rewrites itself every minute gives the indexer work that never ends. In the second thread below, the pending count kept climbing past 60,000, and one reply named the usual culprit: a large synced site that the indexer chases forever until the folder is excluded.
A damaged catalog. If the service sits on "starting", the count resets on its own, or the Indexing Options page is greyed out, the database or its registry keys are broken. Microsoft's table says a greyed-out page with no status means exactly that, and the fix is to clear C:\ProgramData\Microsoft\Search\Data and let it rebuild.
A rebuild deletes the catalog and reads everything again. It fixes a damaged database and it makes any exclusions you just set take effect, so it is the step that follows every change below.
Open Settings, Privacy & security, Searching Windows, select Advanced indexing options, then Advanced, then Rebuild. The same dialog opens from Control Panel as Indexing Options. Run it at the end of the day, keep the machine on power, and give it the full 24 hours before you decide it failed. The walkthrough below shows the clicks on Windows 11.
Two notes for Windows 11. The defragment step in older guides, esentutl /d against Windows.edb, only works on the Windows 10 format; on Windows.db a rebuild does that job. And the Search and Indexing troubleshooter is on Microsoft's MSDT retirement list, so on current builds the manual steps here are the troubleshooter.
The ticket every help desk has seen at least once:
A rebuild on the same scope rebuilds the same problem. Shrinking the scope is the fix that lasts.
Exclude folders first. Under Searching Windows, Add an excluded folder takes whole trees out, and Indexing Options, Modify, gives finer control. The candidates are synced libraries nobody searches locally, build and log folders, VM disks and backup targets. Under Advanced, File Types, you can tell the indexer to read only the properties of a file type rather than its contents, which helps on folders full of large text logs or CAD files.
Then check the mode. Windows 11 offers Classic, which indexes Documents, Pictures, Music and the desktop, and Enhanced, which indexes the whole PC. Microsoft's indexing page notes that Enhanced gives fuller results but may use more system resources. On a machine that was set to Enhanced and has a second data drive, switching to Classic is often the whole fix.
For Outlook, shorten the cached mail window. A one-year default on a busy mailbox puts every message in the index, and a shorter window keeps the OST and the catalog smaller at the same time.
Turning it off is two commands from an elevated prompt:
codesc config WSearch start= disabled net stop WSearch
The space after start= is required. To undo it, set start= delayed-auto and start the service again, which is the startup type Microsoft documents as correct.
The cost lands on three places. Start menu file results and File Explorer search stop using the catalog and crawl the disk instead, which on a full profile means long waits and the Save As search box returning nothing useful. Classic Outlook's Instant Search depends on the service, and as one reply in the first thread put it, without it Outlook falls back to a slow, incomplete search for IMAP mailboxes.
So disabling fits a narrow set of machines: a kiosk, a single-app VDI image, a server role that never searches, or a PC where the user searches with a third-party tool by choice. For everyone else, trim and rebuild. If CPU stays high after the indexer is fixed, the culprit is elsewhere, and our guide to diagnosing high CPU usage reads the symptom before picking a fix.
Group Policy and Intune expose the same switches under Computer Configuration, Administrative Templates, Windows Components, Search, all writing to HKLM\SOFTWARE\Policies\Microsoft\Windows\Windows Search. Microsoft's Search policy CSP lists them for Intune.
Three settings earn their place. Stop indexing in the event of limited hard drive space keeps the catalog from filling a small SSD. Do not allow locations on removable drives to be added to libraries keeps USB drives out. Allow indexing of encrypted files stays off unless the index location is itself encrypted, because the policy text warns that metadata for those files is stored unencrypted. One setting deserves a warning label: Disable indexer backoff makes the indexer run at full speed even when the machine is busy, which is the opposite of what a user on a call wants.
The other half is visibility. A script that reads the indexed count and the Size on disk of Windows.db across every machine finds the ones carrying a 400,000-item catalog before their users file a ticket. On OpenFrame that is a script run across a client's devices with the output collected in one place.
The Windows Search Indexer is a catalog that makes Start, File Explorer and Outlook search fast. It spikes after updates and migrations, on big Outlook files, on synced libraries and on a damaged database. Check the indexed count, trim the scope, rebuild, and give it a day. Disable it only on machines where nobody searches.
If the disk is the busy part rather than the CPU, the next suspect is the service next door, covered in our guide to Superfetch (SysMain).
For the other names that show up near the top of Task Manager, our guide to svchost.exe explains which service lives in which host.
Lead AI Fairy
Some things defy easy explanation: magic dust, the northern lights… and Flamingo’s AI Angels. Think Charlie’s Angels, reimagined with automation brains and serious RMM (Remote Monitoring & Management) chops. Weird? A little. Effective? Absolutely. That’s the job.
Still deciding?
Ask Mingo answers from our docs and customer stories.
Still deciding?
Ask Mingo answers from our docs and customer stories.