Everything 1.50.1415b crashing via network drives

[Xavierarmand]

my Everything 1.50.1415b keeps crashing\freezing when I'm removing drive from the network drives tab in Options.

I'm new to having a NAS and thus network drives to play with. added some, then changed my mound about them so disconnected them via dopus or `net use` in cmd.

have this in on the options page.

Everything_MAIN10_2026-06-23_06-34-51PM_1080x987.png

every time i removed one, with either apply or ok. the option window and then the main would freeze becoming up responsive to any input. needed to kill them via a task manager and re-run EV. this has been consitant for a couple days and across reboots. its happened about 4 or 5 times now.

i think by the time i got to manually removing these network drives they were all "Offline"\grayed out.

I'm on win 10 Version 21H2 (OS Build 19044.7184). i haven't test it on my win11 install.


Is this happening to anyone else? or has my tinkering come back to bite me? LOL

- Xaiver

[void]

Thank you for the issue report Xaiver,

I haven't had any luck reproducing the issue my end.

Could you please send a mini crash dump:

• Wait for Everything to hang.
• Download Process Explorer from Microsoft:
  https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer
• In Process Explorer, select Everything.exe (If there is two, select the one using the most memory)
• Right click Everything.exe and under Create Dump, select Create Mini Dump.
• Choose a filename and click Save.
• Please upload this file in bug report

[Xavierarmand]

well would you believe it... its not happening now. haha!.

at least not through my nas right now, just tired adding, then removing a couple shares and EV didn't freeze.

and come to think of i was playing with using ssh to mount my linux based steam deck as a drive could i could back it up to the nas via.

i don't know if it was the ssh or that linux uses many millions of files and confusing about of symlink throught the os files.


so i guess we can call this not an issue, for now. the next i ssh into my steam deck from my pc ill check if it happens again and chime back.

[void]

Thank you for your reply Xavierarmand,

I suspect the Everything database was busy and an action was performed that caused Everything to block until the reindex completed.

Normally, a reindex is added to a queue and Everything shouldn't block.

I would have to see a mini crash dump to determine the issue.
Please let me know if you see the issue again.

[Herkules97]

None of this may apply, as I've never used NAS connections. But removing devices would cause a rebuild. I don't know how long you've waited for these, but if there are a few million or tens of million of files it might take a few minutes. However if you haven't had this issue before, maybe it's a one-off issue related to something else. I noted a situation I had a day or 3 ago below where I suspect Windows doing something caused freezing when it normally doesn't.

I've had freezing too, frozen window is not equal to a broken process.
Yesterday it happened while several EBV instances were all saving to the OS device, this hasn't happened before but I think maybe Windows was itself doing something which caused it to crap itself for a moment. Not frozen processes, still chugging along. Just couldn't do anything with the windows.
A minute or 3 later and the window I wanted to use unfroze.

But typically it happens when applying settings that may cause a rebuild. IIRC it still works in the background, but I think most of the time I do this it's a mistake so I force-exit and do it right the next time. For example one time I wanted to purge the index journal but I also ended up changing one of the fast sort options to enabled. Sometimes I spasm, or lose control otherwise, my way to mistakes.
If a window is frozen, basic check is the CPU/GPU/disk usage. Often frozen windows become unfrozen when the process has done what it wanted on my end.

This includes when you click on them. Maybe there are instances where clicking on a frozen window could cause it to break the process entirely, Idk.
I don't think I've had anything in the last few years break because I click. It's just a vanity thing and comes with that not responding pop-up.

Old video games that are black screens after alt-tabbing due to exclusive fullscreen may just be entirely broken. Idk, never known how to get it up and displaying. Not that I've looked it up. Need For Speed 2 was one such.

Oh yeah, also when I reach max commit and windows stop updating their contents. But I can still click inside the programs. Maybe there are ways to make them update again. Restarting the programs work and typically they also exit without issue. I think programs like EBV do not suffer from this issue as each window gets closed. So if a window isn't displaying correctly I think you could just exit the window and open a new one..I don't think any EBV windows broke from the most recent max commit some day ago.

[Xavierarmand]

Thank you for your reply Xavierarmand,

I suspect the Everything database was busy and an action was performed that caused Everything to block until the reindex completed.

Normally, a reindex is added to a queue and Everything shouldn't block.

I would have to see a mini crash dump to determine the issue.
Please let me know if you see the issue again.

i sent a bug report with a .dmp (via a dropbox link because it was too large upload).

it froze up on me again. on my 2nd pc. i let it sit a long while. it wouldn't comeback.
killed it. restarted instantly frozen, a few times. to get it back i had to delete my ini.

haven't yet tired to import a back up of settings.

[void]

Thank you for the crash dump.

Everything has hung while trying to read volume information for: \\main10\x

What is the hardware for this network share?



If you import your settings back, please make sure Tools -> Options -> Network drives -> Automatically include new mapped network drives is unchecked.
Avoid adding your \\main10\x as a network drive.
Instead add it as a folder index under Tools -> Options -> Folders.

[Xavierarmand]

sorry for my late reply, been too busy a week.

I've don't much networking as qeek rule. i have to now thou.

the hardware is to "Main10" desktop pc, from a mini11 in the other room.

I'm also new to having a NAS that has about 7ish shares on it.

its not just everything that had crashes, doups has as well and it can be slow.

I'm not surprised by that. more so it seems the oddities of how windows shares SMB. its good, as in fine most of time. thou with massive shares it hangs in the middle of all of it.


and thanks, using folders seems more stable will use this.

one of these shares is mapped to ` A: ` via Dopus\Explorer. EV is automatically seeing it. its also added a folder ` \\server\a `.

which do you suggest to keep index?

[void]

A: is probably easier to use than \\server\a

Either will work (both are treated the same) as a folder index under Tools -> Options -> Folders.