My C: drive was full when I logged in. Search Everything (SE) crashed and its window disappeared. Even though I have cleared about 20 GB of space on my system drive, SE still crashes:
Start SE
SE displays "Loading database", then "Updating dabatase".
It then populates its default file list and shows the number of files in the status bar.
Then crashes without user intervention.
If I activate the debug mode console, it unfortunately disappears when the main window does the same.
Your database (Everything.db) might be corrupted. Delete it and start Everything again. That will build a fresh database.
1. Make sure Everything isn't running:
- right-click the Everything icon in the system tray (if available) and choose Exit.
2. Delete Everything.db.
Depending on your settings, most likely places are either in the folder where Everything.exe is located or in your profile (c:\users\blaq\AppData\Local\Everything\everything.db)
If that doesn't fix the issue: The files on your harddisk might be corrupted.
To anayze/fix this:
- right-click C:\ in File Explorer
- Choose properties
- Activate the Tools tab
- Click Check
Thanks. I've uninstalled the 64-bit version and installed the 32-bit version. I'll report back if I have any problems, or if I run without crashes for a month.
The 0xc0000409 exception is a buffer overrun in SageThumbs.dll.
Please try enabling shell_max_path in Everything:
In Everything, type in the following search and press ENTER:
/shell_max_path=1
If successful, you should see shell_max_path=1 in the status bar for a few seconds.
Restart Everything: type in the following search and press ENTER:
/restart
Enabling shell_max_path will prevent Everything from passing paths longer than (259 characters in length) to the shell.
I have tested a few different file types with SageThumbs with Everything 1.4.1.1005 x86 on Windows 10 1903 x64 without issue, is there a certain type of file that triggers this crash more often?
To disable thumbnails in Everything (and only show large icons):
In Everything, type in the following search and press ENTER:
/thumbnails=0
If successful, you should see thumbnails=0 in the status bar for a few seconds.
Both 1.4.1.1005 and the nightly build crash when shell_max_path=0.
Both of them work correctly when shell_max_path=1.
I have no idea what type of file might trigger the crash; Everything crashes when presenting its initial view of all files on the system. I would love to help you debug this vital utility.
Does this mean anything? Explorer is using the 64-bit version of the SageThumbs (and associated) DLLs, but Everything is using the 32-bit version. (I'm using 32-bit Everything on a 64-bit machine.)
The crash is most likely occurring when the path is too long (over 259 characters).
When shell_max_path is enabled (set to 1), Everything will avoid loading thumbnails for files with long paths.
To find files with paths over 259 characters, please try the following search:
path:len:>259
Please try opening these files in Windows Explorer and see if it crashes.
You can open Windows Explorer to the file location with Ctrl + ENTER in Everything.
The x86 (32-bit) version of Everything will use the x86 (32-bit) version of SageThumbs.dll
The x64 (64-bit) version of Everything will use the x64 (64-bit) version of SageThumbs.dll
Great suggestion! Opening Windows Explorer at the location of a PNG file whose path is over 259 characters long instantly crashes Explorer. Event Viewer reports:
This is amazing! I'd been getting random Explorer crashes for quite a while and my love for Everything led me to the cause. Thanks! I will download 1.4.1.1006 and follow up with SageThumbs.