XYplorer Beta Club

What's the exact target that does not work?

C:\<user name>\Downloads

I have returned to v 19.80.0108 and this works flawlessly.

Yep, saw it now. It did not work if Toolbar | Open With | Resolve Shortcuts before Matching was OFF. Fix comes.

Superb! Thanks:)
Glad to help.

Version 19.80.0140 works OK now. Problem fixed. Many thanks:)

Heyy, I don't know if this is related, but since around the start of 2023 I've been unable to resolve .lnk shortcuts when they're pointing to a mapped network share (symlinks to the exact same location work fine however!).
For example:

CoolTutorialVideos.lnk points to (an SMB Mapped Drive) "E:\CoolTutorialVideos"
Double-clicking the link takes me to "TOSHIBA (E:)CoolTutorialVideos\" with the error message 'Location currently not available'.
In the address bar, the drive letter appears to be the literal volume label of the mapped drive (TOSHIBA). So I toggled combinations of "Support volume labels in paths" and "Resolve junctions" but it didn't change anything.

What's weird about this though, if I Right-Click the .lnk and select 'Shortcut Target > Go to Shortcut Target' it resolves to the correct location just fine.
Why would the context menu work, but not the double-click?

Cannot reproduce. How do you create those links?

admin wrote: ↑28 Apr 2023 16:05 Cannot reproduce. How do you create those links?

Just by drag/drop+alt from the mapped (E:\) drive (from either XY or Explorer) to Local and/or Network locations.

I just tried creating a shortcut to the UNC, so "\\NAS\E\CoolTutorialVideos" rather than the mapped "E:\CoolTutorialVideos" and it works with UNC no problem.

Hmmm cloned my XY setup to the NAS pc, and remote .lnk shortcuts (both Mapped and UNC) pointing back to my Desktop seem to be working. So I guess it's something about my Desktop.. registry that's causing XY to fail the resolve? But the shortcuts resolve correctly on both systems when using Explorer.

I guess I'll keep trying things till I can isolate the cause of it. Or give up and convert them all to .lnks to UNC heh

Ookay, it looks like it's something caused by setting the SMB Mapped Drive (E:\) root as my Windows' "Downloads" folder.
Creating different SMB mapped drives (F:\,G:\, etc:\) all seem to work correctly.

Something about that special Shell Folder is making XY not resolve it correctly and calls it by it's volume label (like it would do for a "Downloads" folder I guess)

Can you send me such a link?

I don't think it's the link, as the link will work - as long as it's not pointing to "Downloads"\Foldername\. If I remove the Windows "Downloads" Shell Folder properties by changing the location, eg instead of E:\ I assign a temp folder: then the exact same link that was broken before and resolving to "VolumeLabel(E:\)Foldername\" will now correctly resolve to "E:\Foldername"

It looks like this when broken: I've tried to attach it, wonder if it works

Confusing. Cannot reproduce.

I've managed to reproduce it on the other network PC now with this setup:

PC-A
(map drive from PC-B [T:\]) E:\
set 'Downloads' folder to root of mapped drive 'E:\'
restart/open XY
create Shortcut LNK target to "E:\Example" - this fails
create UNC LNK target to "\\PC-B\T\Example" - this works

PC-B
(local drive) T:\Example\

I'm still confused. I don't see why another PC would be needed to reproduce the problem.

When you say "map drive" how exactly do you map?

The LNK target is shown eg on the Meta tab. Does it look correct?

admin wrote: ↑29 Apr 2023 10:12 I'm still confused. I don't see why another PC would be needed to reproduce the problem.

Ah, when you said you couldn't reproduce it, I wondered if it was my Desktop that might be causing it so I tried it on a different PC to see if I could reproduce it

admin wrote: ↑29 Apr 2023 10:12 When you say "map drive" how exactly do you map?

I create network shares of drives on PC-B with full Admin access: Then on PC-A w/ Explorer or XY I map that from the context menu and set the drive to be the Shell Folder 'Downloads': -

admin wrote: ↑29 Apr 2023 10:12 The LNK target is shown eg on the Meta tab. Does it look correct?

Yes, LNKs targeting the 'Downloads' drive are showing the correct local paths: But for some reason it resolves to VolumeName(VolumeLetter:)FolderName \ -
If I change the 'Downloads' Shell Folder to any other folder/drive, those previously unresolveable 'Location currently not available' LNKs start resolving to the correct local paths