locked
BUG: Windows.edb exploding RRS feed

  • General discussion

  • I believe I've come across a bug which causes Windows.edb to grow until the drive is completely filled.

    I have about 500gb of stuff indexed by Windows for a total of what Indexing Options reports as 648,284 index items. The index is currently at 70GB, my free disk space down to 0.

    What makes it somewhat strange is that Indexing Options tells me that indexing is complete, yet the file is still growing.

    For now I'm going to disable indexing and delete the index file.

    If this helps at all:

     Directory of C:\ProgramData\Microsoft\Search\Data\Applications\Windows
    
    08/03/2012  02:13 PM    <DIR>          .
    08/03/2012  02:13 PM    <DIR>          ..
    29/02/2012  06:45 PM    <DIR>          Config
    08/03/2012  02:13 PM             8,192 edb.chk
    08/03/2012  02:13 PM         1,048,576 edb.log
    08/03/2012  02:13 PM         1,048,576 edb166CA.log
    08/03/2012  02:13 PM         1,048,576 edb166CB.log
    08/03/2012  02:13 PM         1,048,576 edb166CC.log
    08/03/2012  02:13 PM         1,048,576 edb166CD.log
    08/03/2012  02:13 PM         1,048,576 edb166CE.log
    08/03/2012  02:13 PM         1,048,576 edb166CF.log
    29/02/2012  06:45 PM         1,048,576 edbres00001.jrs
    29/02/2012  06:45 PM    <DIR>          GatherLogs
    29/02/2012  06:45 PM    <DIR>          Projects
    07/03/2012  09:16 PM         8,454,144 tmp.edb
    08/03/2012  02:06 PM    70,841,860,096 Windows.edb
                  11 File(s) 70,858,711,040 bytes
                   5 Dir(s)         458,752 bytes free


    the cows are here to take me home now...


    Thursday, March 8, 2012 10:18 PM

All replies

  • I would say that's a problem! I checked mine, and with 33,946 index items, the file is 400MB, which I guess is OK.

    However, this did allow me to find what appears to be a bug in this area: changing the location of the index doesn't survive restarting the Windows Search service!  Which means that relocating the index doesn't work. Hmmm. Edit: Workaround is to stop the Windows Search service before moving the index in the UI. The service will then restart and the configuration change will stick.


    • Edited by rseiler Friday, March 9, 2012 7:46 AM
    Friday, March 9, 2012 7:36 AM
  • same issue here. out of space and Windows.edb file is 270gb. can you delete this file?

    Tuesday, March 20, 2012 11:22 AM
  • run the indexing options control panel and click rebuild index.

    "A programmer is just a tool which converts caffeine into code"

    Tuesday, March 20, 2012 11:12 PM
    Answerer
  • Nitro, how many indexed items do you have?  If it's in the hundreds of thousands, like OP's, I wonder if that could be the trigger. Mine's quite a bit lower, and the EDB is still only a half gig.
    Tuesday, March 20, 2012 11:25 PM
  • Not a 100% sure as a reset the index. but i think it was about 300,000. one thing i did have set in my search options was to include subfolders. I change this to see if it makes a difference. 

    ps. is this the best forum to report bugs and feedback?

    Wednesday, March 21, 2012 12:32 AM
  • run the indexing options control panel and click rebuild index.

    "A programmer is just a tool which converts caffeine into code"

    Andre, does rebuilding prevent the problem the second time?

    the cows are here to take me home now...

    Wednesday, March 21, 2012 2:40 AM
  • Try it out. I have no idea. I use 3rd party search tools. Windows search sucks.

    "A programmer is just a tool which converts caffeine into code"

    Thursday, March 22, 2012 11:29 PM
    Answerer
  • run the indexing options control panel and click rebuild index.


    "A programmer is just a tool which converts caffeine into code"

    Andre, does rebuilding prevent the problem the second time?

    the cows are here to take me home now...

    I had same issue.  Rebuilding the index made the problem go away for just over a week but then I noticed my free space start declining again so rebuilt.  Seems like this will be a regular task until the bug is fixed.  Hope it will have been in the release preview
    Tuesday, May 29, 2012 7:00 AM
  • Yeah, it seems to explode again after a few days or so.


    the cows are here to take me home now...

    Tuesday, May 29, 2012 7:02 AM
  • Reduce the indexed folders and only index the name not the content.

    "A programmer is just a tool which converts caffeine into code"

    Sunday, June 3, 2012 7:55 PM
    Answerer
  • I've run into this as well... My Win8 upgrade from Win7 has a 184GB (and growing) Windows.edb file.  I free up disk space, it consumes what I free, then warns I'm out of disk space again.  Rinse, repeat.  Aside from killing the index service, has anyone found a solution?

    Mark


    • Edited by mpietras Tuesday, September 18, 2012 7:05 PM
    Tuesday, September 18, 2012 6:52 PM
  • Windows Search sucks. Disable the indexer and increase your Windows performance. Use Classic Shell whose search box will still work even if you disable Windows Search. For file search, use "Everything" product. It won't index contents. If you MUST search contents, use FileLocator Pro.
    Thursday, September 20, 2012 1:41 PM
  • Hello mpietras

    Are you using the RTm version of Windows 8 or the Release Preview version of Windows 8?


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

    Monday, September 24, 2012 4:19 PM
  • Yes, RTM.  FYI I have disabled Windows Search and the issue has gone away (except I no longer have fast searches)

    Mark

    Monday, September 24, 2012 4:42 PM
  • I also have this exact same issue.  My Windows.edb file is 98GB.

    Windows 8 RTM.

    Saturday, September 29, 2012 9:40 AM
  • 184GB, 98GB, 270GB, yikes!

    Maybe it's THAT bad because you enabled the option to index content rather than just file names?  If not, are you maybe indexing more than you should?  For example, once I noticed that Windows had somehow included my entire Users directory for indexing--not good. This is a definite problem, but reigning in what's indexed, and how it's indexed, should prevent it from getting this out of hand.

    Failing that, I think scheduling a rebuilding of the index on a regular basis, say once a week early in the morning, would be a good idea, though a quick search didn't turn up any way to actually do that. No doubt a third-party macro tool could handle it. Best I could find with what's built in is calling up the Indexing UI, but nothing beyond that:

    rundll32.exe shell32.dll,Control_RunDLL srchadmin.dll

    Saturday, September 29, 2012 4:13 PM
  • 184GB, 98GB, 270GB, yikes!

    Maybe it's THAT bad because you enabled the option to index content rather than just file names?  If not, are you maybe indexing more than you should?  For example, once I noticed that Windows had somehow included my entire Users directory for indexing--not good. This is a definite problem, but reigning in what's indexed, and how it's indexed, should prevent it from getting this out of hand.

    Failing that, I think scheduling a rebuilding of the index on a regular basis, say once a week early in the morning, would be a good idea, though a quick search didn't turn up any way to actually do that. No doubt a third-party macro tool could handle it. Best I could find with what's built in is calling up the Indexing UI, but nothing beyond that:

    rundll32.exe shell32.dll,Control_RunDLL srchadmin.dll

    How much did you have in your Users folder that it'd be a bad idea to index it? I'm pretty sure that's how it's been by default in Windows 7 anyway.

    the cows are here to take me home now...

    Saturday, September 29, 2012 4:43 PM
  • Hello,

    If you are seeing this issue:

    Could you go to Control Panel, choose Indexing options

    Take a screenshot of that and make it available.

    This shows the number of items and what folders and drives are being searched


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

    Monday, October 1, 2012 5:21 PM
  • had the same problem today on my windows 8 enterprise with ssd drive...

    Windows.edb had 70GB

    index settings where just default, so user profile, outlook and onenote nothing special!!

    have disabled all except outlook now.. 

    Size of Windows.edb file is now 73792KB just waiting and watching what happens now... 

    what i also recognized before with the 70GB EDB File... LogFiles gettings created/merged/deleted about every second... (couldn't be good for a SSD Drive though)

    ....

    as i'm writing this my File size increased allready to 139MB... in a few Minutes... :(

    although indexing is running now (2700 items indexed) so i hope the file didn't increase to much...


    edit: lol... 3100 items; siz allready 172....
    Thursday, November 15, 2012 10:27 AM
  • @DjFutureShock, if your system doesn't also have a spinning drive in order to relocate the index to, I'd disable indexing and use a 3rd-party alternative. At the very least, you might deselect some of the things being indexed in your profile.

    Each time someone posts here, I'm reminded to look at the stats: 57K items indexed, 904MB, which happened in under two months. Not bad, relatively speaking, but it's hard to believe that it's right.

    Thursday, November 15, 2012 4:15 PM
  • I too just noticed this problem. Have been an avid user of Windows' search functionality since it was a third-party product (Lookout). But only since upgrading to Windows 8 Pro (x64) have I seen the index balloon out of proportion, filling all available disk space. I have 2x256 SSDs (RAID-0) in my notebook. I basically index two types of items: my e-mails (1.1M in 33 PST files, ~57G), and about 150K files (DOC, PDF, XLS, etc.; ~56G). How can the windows.edb file have expanded to 94G (almost as big as the 113G of data)? Sure seems like a bug. Of course telling the indexer to rebuild "solves" the problem, but at a cost: it takes ~4 days for my computer to index everything, during which my search results are incomplete ...

    Slightly relatedly, I can't find where in Win8 would show the results of a search on all the data on my computer. It seems the Win8 "search files" (flag-f) no longer includes local e-mails in its searches, and the search box in Outlook includes *only* e-mails. So I have to do two searches-- a move backward away from Mac OS's convenient Spotlight, which includes in its search results not only all local files but also Google ...

    Tuesday, December 4, 2012 5:20 AM
  • Same here, Windows 8 Pro with Media Center, standard indexing options (including libraries).

    A week ago Windows.edb had grown to about 90 GB, thus filling up my entire SSD drive. Stopped the service, deleted the file, and restarted. This is how it has progressed since then:

    December 1: 5 GB, 825 883 elements indexed
    December 2: 6.2 GB, 830 697 elements indexed (finished)
    December 6: 70.9 GB, 852 023 elements indexed (finished)

    I've completely disabled the Windows search Service now, but hoping for a fix to this awful bug...

    Thursday, December 6, 2012 9:52 PM
  • Same problem, during the last 2 days, it has grown to 129 gb. The "Microsoft Windows Search Indexer" is working overtime in the Task Manager. Is there some kind of recursion, that it indexes it self?
    • Edited by TNesser Friday, December 7, 2012 7:57 AM
    Friday, December 7, 2012 7:45 AM
  • Same here.  It grows at the rate of 0.5GB/hour on my computer.  The only way  that I know to deal with it is to reboot the computer.

    Hong

    Monday, December 10, 2012 12:39 PM
  • I'm getting this problem as well. Very frustrating waking up to a drive with 0KB free. Anyone have experience with good third party search tools?
    Tuesday, December 18, 2012 5:51 PM
  • Same problem here, 105 gb..... 
    Friday, December 21, 2012 10:10 PM
  • I also have this problem. I changed the location and shut down all selected indexing locations. I have now diskspace again and it seems to work. But hoping to find a structural solution?
    Saturday, January 12, 2013 9:22 AM
  • I'm really, really, really disappointed by this. I recently had this problem and I didn't find the culprit immediately for my space issue, so I uninstalled my Steam games, one of which was a 200+ hours saved game of Skyrim

    today I used a better disk space analyser and found that the EDB file was 120Gb on a 200Gb drive. So I immediately disabled search indexing and deleted the file

    there were more than 300.000 files indexed

    Sunday, February 10, 2013 11:09 AM
  • Disclaimer: I don't "own" this file or any of the indexing stuff.

    I too have seen this @ home.  This is a known issue that is being investigated.

    It is "safe" to delete windows.edb if it gets to be a crazy size.  The downside is that it will take a while for the search indexer to re-index, and in that time desktop search isn't going to work.  I have been periodically deleting mine if it explodes in size. 

    Of course if you have a gigantic number of things being indexed, then the size may be normal.  For me, ~400,000 items being indexed takes 6-7GB.  I've heard that 1-2GB/100K items is typical.  If you have too many things for a small SSD or something, you may have to remove things from your index, or move it to a different drive.  You can see how many items are being indexed in Indexing Options.

    I've discovered that I need to take manually delete windows.edb, and to do so, I have to stop the SearchIndexer process in taskmgr.  Usually it stays a sane size then for a few weeks before exploding again.

    Hope that helps,

    Shawn


    Shawn

    Thursday, May 2, 2013 1:25 AM
  • Install the May 2013 Update to fix the issue:

    Windows 8 and Windows Server 2012 update rollup: May 2013

    http://support.microsoft.com/kb/2836988/en-us

    This update package also fixes the issues that are documented in the following articles in the Microsoft Knowledge Base:


    2838018    The Windows.ebd file grows very large in Windows 8 or Windows Server 2012


    "A programmer is just a tool which converts caffeine into code"

    Tuesday, May 14, 2013 7:58 PM
    Answerer