Everything "Not Responding" when accessing Windows Explorer

If you are experiencing problems with "Everything", post here for assistance.
Post Reply
tech9
Posts: 7
Joined: Sun Apr 13, 2025 2:48 pm

Everything "Not Responding" when accessing Windows Explorer

Post by tech9 »

I downloaded Everything1.5a (ET) about two weeks ago for Windows running on Parallels Virtual Machine, and it worked flawlessly with my Mac, so I added my external hard drive as a "Folder."

But because
(1) Parallels registers external hard drives as Windows network drives (see http://bit.ly/4jyt3Hi), and
(2) ET was set to "automatically include new mapped network drives," my hard drive got scanned/indexed twice, meaning, when I searched for files on the external drive, every search result was duplicated twice.

So I just removed the external hard drive from the "Folder" list, but ever since I removed it, when I click on certain buttons within ET which open the Windows Explorer Dialog Box (e.g. "Open File List," or "Options>>Exclude>>Add Folder", or "Options>>Folders>>Add..."), ET freezes and displays a "not responding" label.

I've tried reinstalling ET, rebuilding indexes, deleting the .db file, but it still freezes. Any help?

---on Windows Dialog box: https://learn.microsoft.com/en-us/windo ... alog-boxes
---on Parallels and ET: viewtopic.php?p=30007&hilit=parallels#p30007
therube
Posts: 5716
Joined: Thu Sep 03, 2009 6:48 pm

Re: Everything "Not Responding" when accessing Windows Explorer

Post by therube »

If you disable the automatic inclusion - if you don't use (where ever, however, it is that Everything picking it up automatically?) but instead re-enable the Folder index, does the 'not responding' condition persist?
tech9
Posts: 7
Joined: Sun Apr 13, 2025 2:48 pm

Re: Everything "Not Responding" when accessing Windows Explorer

Post by tech9 »

Problem solved: after uninstalling Everything, I searched "Everything" in my AppData folder and found residual Everything files which the uninstaller had not removed. I deleted all those residual files, reinstalled "Everything," and now it works fine again.

I'm not technical enough to know which of those residual files was causing the problem. I'm guessing one of them had some kind of saved log of what (past) drives were connected to my computer, and Everything (including newly installed instances of Everything) kept opening that log and looking for those drives, instead of detecting the drives aren't connected anymore; when it could't find the drives, it would stop responding.
Post Reply