Disconnected UNC paths still causing freezing/crashing.

[dgdomtar]

I had originally posted about disconnected UNC paths spawning an infinity of error messages and then crashdumping here (#504). A fixed was subsequently put in and the recent dev builds don't suffer from that exactly anymore, however I am still getting problems of the program not elegantly handling disconnected/unreachable UNC paths.

It will not throw a network error like the below and freeze up for 30 seconds after hitting Cancel. Sometimes it will free up and allow me to click something else to get away from it or close the tab. Other times it will simply re-freeze when I try to do something and get in a network error popup/cancel freeze loop until I have to End Task it.

To eliminate this, is it possible if it encounters this error in the future, it will disconnect from that path and make no further reconnection attempts unless the user manually tries to reconnect with it? Or at the very least a timeout limit or something?

Explorer++ version 1.5.0.2565 dev (64-bit build)
Build date: Jan 28 2025 04:31:35
OS: Win 11 Ent 26100.3194