You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Windows: Windows 10 Pro
Explorer++ Version: Explorer++ version 1.4.0.2293 (64-bit build); Build date: Jan 28 2024 14:58:43
open a VPN
Connect to a machine using a network address like \\my.machine.whatever... in a couple of tabs.
Disconnect from the VPN without closing the tabs to the network locations. I think it might be important to have one of the tabs selected.
Doing the above causes Explorer++ freezes up. After killing it, trying to open it up never displays the program. You have to go into Task Manager and kill the instances. The only way I found to fix it is to remove the registry entry under HKEY_CURRENT_USER\Software\Explorer++ (source)
I expected the program open up as normal, and then give an error message stating unable to open location (with the network/file location in the error message). Finally, close the tabs that to which it could not connect, and then run as normal.
Since it didn't officially crash, there is no dump file to attach.
The text was updated successfully, but these errors were encountered:
Windows: Windows 10 Pro
Explorer++ Version: Explorer++ version 1.4.0.2293 (64-bit build); Build date: Jan 28 2024 14:58:43
Doing the above causes Explorer++ freezes up. After killing it, trying to open it up never displays the program. You have to go into Task Manager and kill the instances. The only way I found to fix it is to remove the registry entry under HKEY_CURRENT_USER\Software\Explorer++ (source)
I expected the program open up as normal, and then give an error message stating unable to open location (with the network/file location in the error message). Finally, close the tabs that to which it could not connect, and then run as normal.
Since it didn't officially crash, there is no dump file to attach.
The text was updated successfully, but these errors were encountered: