Tree of mapped network drive disappears

[jupe]

Yes the label is shown there,

2025-02-07_074611.png (7.29 KiB) Viewed 4233 times

[admin]

Looks like a "Disconnected Network Drive" (red X icon) is not seen as a mapped drive in Win10 and later, whereas in Win8.1 it is. ATM, I cannot do anything (within reason) about it. Might get an inspiration later.

[admin]

I have now checked it in Windows 11 and still can't reproduce it. I'll leave it alone for now.

[daniel_m]

It looks like we are not quite there yet with folders not appearing in the tree

Apparently, this bug doesn't only affect folders created with XYplorer, but other programs as well. E.g. folders created by 7zip appear in the list view, but not the tree view (and refreshing the tree view does nothing). I tried extracting archives containing a folder, as well as the context menu option "Extract to 'archive name'".
This was tested on v26.80.0404 on Windows 10. I am not sure if 7zip itself is the culprit, or if the bug occurs because 7zip was invoked from the XYplorer context menu.

Edit: Forgot to mention that this is with CustomDnDMenu=0 and NetworkDrivesAssumeAvailable=1

[admin]

Just uncheck Configuration | General | Safety Belts, Network | Network | Assume that mapped network drives are available

[daniel_m]

Will do.
Does it affect network performance? Or was the option supposed to fix something Windows messes up but can't ... because Windows excels at messing up?

The point of reporting this was more that there is no obvious connection between NetworkDrivesAssumeAvailable=1 and folders not appearing in the tree. Users who are not aware of this thread won't know what's happening and that it can be fixed easily.

[admin]

"Assume that mapped network drives are available" was added for users that frequently have unavailable mapped drives, which makes everything slow (not only XYplorer). If checked, the speed is back, but auto-refresh is gone. It's a trade off. If your mapped drives are alive, you don't need it at all and should uncheck it.

[daniel_m]

I see. I guess you are talking about the 60 seconds freeze of any program that tries to access the file system when a network drive is unavailable? Even though one might be aware of the missing network drive and only intends to e.g. save a file on a local drive. I tried to find a way to lower that timeout in Windows, but apparently there is none...
Anyways, thanks for the clarification. I will happily accept some network freezing shenanigans once a year for having auto-refresh every day

[admin]

Yep, the damn 60 seconds freeze.