The Windows Search Index Explained: What Those edb Files Really Do

What the index is, mechanically

The search index is a real database built on the Extensible Storage Engine (ESE) — the same engine that runs Exchange mail stores and Active Directory — and it lives in C:\ProgramData\Microsoft\Search\Data\Applications\Windows. On NTFS volumes the indexer subscribes to the USN change journal, so a newly saved file is picked up within seconds instead of after a full crawl. Text gets extracted by iFilters and property handlers, which is why a folder of PDFs indexes differently than a folder of plain text files. Everything lands in one file set that most people have never opened.

• Windows.edb — the main database holding paths, properties and extracted content
• Windows.db — the newer property store that joined the family in recent builds
• edbXXXXX.log — transaction logs that make writes crash-safe before they reach the database
• edb.chk — the checkpoint file marking which transactions are already flushed
• tmp.edb — scratch space the engine reserves for maintenance passes

Why the edb set grows — and when it is a problem

On a healthy Classic-mode install the whole set sits somewhere between 50 MB and 1 GB, scaled to the number of documents, and there is nothing to fix. Enhanced mode, which indexes the entire PC by default, pushes the database into multiple gigabytes once game libraries, project trees and virtual machine folders get crawled. Outlook is the classic multiplier: PST and OST data files are content-indexed too, and a mail archive can turn a 300 MB index into a 4 GB one overnight.

Real trouble announces itself as a Windows.edb that keeps growing while search gets slower or returns nothing — usually a corrupted database the indexer keeps rewriting after a dirty shutdown or a full system drive. In that state rebuilding is the standard first move, not a gamble. Log files by themselves are not a leak: Windows keeps a rotating set of them and trims the old ones automatically.

Rebuilding the index without breaking anything

The supported path is Control Panel → Indexing Options → Advanced → Rebuild; the Searching Windows page in Settings is where you switch Classic or Enhanced mode and prune folders. A rebuild deletes the database and re-crawls from scratch, so search stays degraded for an hour or two on a large library — that is the repair working, not a failure. The manual route — stop the Windows Search service, delete Windows.edb and its logs, start the service again — achieves the same thing, because Windows regenerates the whole set on next start.

What you should not do is put the Search folder on a weekly cleaning schedule. The index exists to make search instant, and deleting it every seven days just trades a gigabyte of disk for a permanently half-warm index and endless re-crawling. Rebuild once when there is an actual symptom, and leave it alone between.

Questions and Answers

Read next