x64 crashes when network drive not connected

[highend]

That's not a tweak but a normal gui config option

Configuration | General | Refresh, Icons, History | Auto-Refresh | Refresh during file operations

[daniel_m]

Oh, I see. I hunted down this setting by copying parts of my XYplorer.ini into a fresh ini, and mistakenly associated "WatchDuringFileOp" with the adjacent "WatchIt" ("; Tweak: |-separated list of locations to watch ...").

In that case, fixing deleted folders not getting removed from the view might be a real issue. I remember that we discussed this over a year ago in viewtopic.php?t=27337&hilit=Refresh+dur ... s&start=70. File system notifications cause XYplorer to become unresponsive on network drives for a short while. Donald introduced a tweak "SHChangeNotifyExcludeNetwork" to exclude network drives from file system notifications. It turns out that an unexpected side effect is that XYplorer doesn't realise that it deleted the currently viewed folder.

[admin]

Cannot reproduce (with a fresh installation). The deleted folder is correctly removed from the tree and XY jumps to the parent as new current location.

[daniel_m]

Did you do a "shift + del"? I tried it again and I got the result shown in "shift-delete.gif".

1) Make a new folder on a mapped network drive in XYplorer (fresh v27.90.0012 with default settings).
2) Enter the folder.
3) Shift-delete the folder in Windows Explorer.

=> The folder remains visible in XYplorer

When I right-click the (deleted) folder in the tree, I get no context menu.
When I click on the (deleted) folder in the breadcrumb bar, XYplorer becomes unresponsive for a few seconds.
When I navigate to the root, the (deleted) folder is not shown in the file pane. But it is still there in the tree, and I can navigate back to it (via the tree view or the breadcrumb bar). Doing so, the file pane shows error "The system cannot find the path specified".

[admin]

Tried it in Win8.1 and Win11. Maybe it's a Win10 thing.

[daniel_m]

Tested on Windows 10 and 11.

[admin]

The Windows notification system is known to be somewhat erratic. Tried a reboot already?