Long story short, I had data loss on a drive mapped by everything.
I'm curious if it's possible to get that most recent file list from the hard drive that has Everything installed, without booting up the machine. Does everything store a file database somewhere that's easy to read or is it in memory? This was a network share mapped, not native NTFS. I'd like to compare the before/after file list.
Where is the everything database stored?
Re: Where is the everything database stored?
You can find your Everything.db in %LOCALAPPDATA%\Everything
This expands to:
If you use the portable version, your Everything.db is stored in the same location as your Everything.exe
Please backup your Everything.db as soon as possible.
Everything will overwrite it on exit.
Use db2efu to convert your Everything.db into an EFU filelist.
An EFU file list can be opened in Everything, Notepad or Excel.
Good luck.
This expands to:
C:\Users\your-username\AppData\Local\Everything
If you use the portable version, your Everything.db is stored in the same location as your Everything.exe
Please backup your Everything.db as soon as possible.
Everything will overwrite it on exit.
Use db2efu to convert your Everything.db into an EFU filelist.
An EFU file list can be opened in Everything, Notepad or Excel.
Good luck.
Re: Where is the everything database stored?
thanks so much for the quick reply! fortunately everything is installed in a powered down VM so i can safely browse the file system and get it
Re: Where is the everything database stored?
Related, Failed hard drive.
Similarly, if you opened a new instance, you could throw a copy of the .db in there
(renamed to the instance name, so if -instance KKK, instead of Everything.db, it would be Everything-KKK.db)
& likewise use the -read-only -no-auto-include switches...
(And always work on backups.)
Similarly, if you opened a new instance, you could throw a copy of the .db in there
(renamed to the instance name, so if -instance KKK, instead of Everything.db, it would be Everything-KKK.db)
& likewise use the -read-only -no-auto-include switches...
(And always work on backups.)