SearchIndexer.exe Is Eating Disk and CPU: The Windows.edb Guide
The Sneakiest Background Slowdown
Short answer: `SearchIndexer.exe` is the Windows service that scans file names and contents ahead of time and writes them into a database called `Windows.edb`. If it constantly uses high CPU or disk, it is usually one of two things: the "Enhanced" indexing mode in Windows 11 is on and indexing your entire drive, or the index is corrupted and rebuilding endlessly. `Windows.edb` lives under `C:\ProgramData\Microsoft\Search\Data\Applications\Windows\` and can pass 5-10 GB when large mailboxes or hundreds of thousands of files are indexed. The right fix is not to disable the service blindly but to narrow the scope in Indexing Options; that lowers CPU load and shrinks the database. Note that the file does not shrink on its own after narrowing the scope — the index has to be rebuilt.
This is one of the rare topics that answers both "my fan spins even when the computer is idle" and "there is an 8 GB file on my C drive and I have no idea what it is" at the same time.
Key Takeaways
- `SearchIndexer.exe` is the Windows Search service; it writes file names and contents into the `Windows.edb` database.
- In Windows 11, the "Enhanced" mode under Settings > Privacy & security > Searching Windows indexes the ENTIRE drive and is the most common cause of high load.
- `Windows.edb` sits under `C:\ProgramData\Microsoft\Search\Data\Applications\Windows\` and can exceed 5-10 GB.
- Narrowing the scope does not shrink the file immediately; it only shrinks once the index is rebuilt.
- The "Index Properties Only" option keeps file-name search working while dropping content scanning — usually the best balance.
- Disabling the service entirely gives the biggest win but breaks file search in the Start menu and Outlook's instant search.
Windows Search options: gain and cost
| Setting | System load | Effect on search | Suited to |
|---|---|---|---|
| Enhanced mode (entire PC) | High — index can reach 5-10 GB | Most complete, content search everywhere | Powerful machines, heavy searchers |
| Classic mode (libraries + desktop) | Low | Documents found, whole disk not scanned | The default, most users |
| Index properties only | Moderate drop, database shrinks | File names found, contents not searched | People with a full disk |
| Rebuild the index | Very high temporarily | Repairs a corrupted index | When search returns nothing |
| Disable the service entirely | Biggest win | Start menu file search stops working | People using a separate search tool |
What Is the Windows Search Index and Why Does It Grow?
When you type a word in the Start menu, Windows does not scan the disk at that moment; it looks at a database prepared in advance. That database is the `Windows.edb` file, kept continuously up to date in the background by the `SearchIndexer.exe` service. The upside is that search returns instantly; the cost is that the preparation consumes CPU, disk and storage.
The size of the database depends on two things: how many files are indexed, and whether their contents are scanned as well. If only file names are indexed, the file stays at a few hundred megabytes. With content indexing on and a broad scope, the text of every document, email and PDF goes into the database — that is where 5-10 GB `Windows.edb` files come from.
In Windows 11 one more factor made this worse: the "Enhanced" indexing mode in Settings indexes the entire drive rather than just Documents and Desktop as classic mode does. With that option on, projects, virtual machine disks, game folders and backups are all scanned — both the load and the database multiply.
What Does It Mean When SearchIndexer Runs Constantly?
If `Microsoft Windows Search Indexer` shows sustained high disk or CPU in Task Manager, there are three possibilities. The first is normal: after a fresh install, or after copying a lot of files, the index is being built for the first time. That takes a few hours and then stops on its own.
The second is a scope problem. The index covers enormous folders you will never actually search: a virtual machine directory, a few hundred gigabytes of project files, or a backup drive. The indexer watches those continuously and rescans on every change. This is one of the common reasons a fan keeps spinning on an idle machine.
The third is corruption. When `Windows.edb` is damaged, the indexer keeps trying to rebuild, never finishes and loops forever. The symptom is telling: search returns nothing or incomplete results while the indexer is permanently busy. In that case the fix is not narrowing the scope but rebuilding the index by hand.
Narrow the Scope, or Turn It Off?
The first move should always be narrowing the scope, because it removes most of the load without losing the benefit of search. Press Windows + R, run `control srchadmin.dll` and click Modify. You see every indexed location; remove backup folders, virtual machine directories and large media archives from the list.
The second setting, and the most effective one for most people, is in the same window under Advanced > File Types. For each extension you can pick "Index Properties Only" or "Index Properties and File Contents". Turning content indexing off keeps name-based search working while the database shrinks dramatically and the indexer works far less.
Disabling the service outright (`services.msc` > Windows Search > Disabled) gives the biggest win but the cost is real: file search in the Start menu stops working, Outlook's instant search breaks, and searches in Explorer scan the disk from scratch every time, which is slow. Only do this if you have a separate search tool taking its place.
When Is Rebuilding the Index the Right Move?
Rebuilding is the right move in two situations. First, when search itself is broken: no results, incomplete results, or deleted files still showing up. That means the index is inconsistent. Second, after narrowing the scope: `Windows.edb` does not shrink on its own, and a rebuild is what discards the old data.
Start it with the Rebuild button under Indexing Options > Advanced > Troubleshooting. Depending on file count it takes anywhere from half an hour to several hours, and CPU and disk are heavily used throughout. On a laptop it makes sense to start it while plugged in.
Search results will be incomplete during the rebuild; that is normal and resolves when it finishes. You can tell it is done from the "Indexing complete" line at the top of the Indexing Options window.
Frequently Asked Questions
Can I just delete Windows.edb?
Technically yes once the service is stopped, and Windows will recreate it — but that is the same outcome as the Rebuild button by a riskier route. Use Indexing Options > Advanced > Rebuild instead.
What do I lose if I turn Windows Search off?
Finding files by typing in the Start menu stops working, Outlook's instant search breaks, and Explorer searches become noticeably slower because they scan the disk from scratch each time. Settings and app search are unaffected.
I use an SSD — does indexing still hurt?
In performance terms the difference is much smaller on an SSD. But the indexer writes constantly and `Windows.edb` occupies gigabytes; on an SSD that is close to full, those two effects combine into a slowdown you can feel.
Why does indexing seem never to finish?
Windows indexes while the machine is idle and pauses while you use it, and it slows down on battery power on laptops. That is usually why it appears to take days, and it is not a fault — but taking weeks does suggest a corrupted index.
Verdict
`SearchIndexer.exe` is one of the rare items that keeps an idle computer busy and occupies gigabytes of disk at the same time. The correct order is: turn off Enhanced mode in Windows 11, remove large never-searched folders from the index scope, reduce content indexing if needed, and rebuild the index last.
To see the other hidden items using space on the same machine, Disk Mop's Disk Analysis module sorts the drive by size including hidden folders like `ProgramData`, while the Startup Manager and Service Manager modules show on one screen what else is running in the background and taxing the machine.
See what runs in the background and what piles up on disk
One-time payment for lifetime access to all features. No subscription, no hidden fees.
Download Disk Mop Now