XYplorer Beta Club

Hi,
I'm new to XYplorer, in my trial period and so far I'm liking except for one issue. I have menu structure broadly of shortcuts, it is stored on my D Drive as is my Desktop.

The other day I went to run one of my UltraVnc shortcuts and it advised not found. Tried a couple of others all the same error. Strange as I had used them in the last few weeks. When I opened them up the 'start in' path was fine but the Target was pointing to "C:\Program Files (x86)\uvnc bvba\UltraVnc\vncviewer.exe" i.e. x86 not "C:\Program Files\uvnc bvba\UltraVnc\vncviewer.exe". Strange but I edited it, clicked Apply and Ok. Tried run it and same error! Went back in to edit it and it was back as x86.

Recreated the shortcuts on my Desktop, they worked fine, copied to my menu folder and they changed to x86 again and wldn't run

Both my Desktop and Menu folders are on Drv D and if I access the menu folder using File Explorer [Win 11] they work but the same shortcut fails in XYplorer. View the properties in File Explorer it's correct, do the same thing in XY and it shows x86 version.

What is going on? I hope it can sorted else it will be a very disappointing end to what had been a good trial period

Regards
Mark

What did you use to create/edit those shortcuts?

Hi
Right click VncViewer.exe, create shortcut to Desktop then edit properties adding the IP address to the target then move it into the appropriate menu folder. I've done it like for years thru Win 7, 10 & 11 if not earlier having used 2.1 onwards excluding Vista and 8

I haven't come across any other shortcuts with this issue. All very strange but hopefully fixable

Just tried copying the working version on my Desktop and removing the IP address. Moved it to my menu folder and the target path changed to the x86 version

BTW I'm running Win 11 Pro 64bit

Thanks
Mark

Thank Windows for the weirdness. XYplorer is a 32-bit process, and Windows smartly resolves certain shortcuts so that the target is in the 32-bit world.

Can you attach one of those LNK file (wrapped in a ZIP), so I can look into it?

Well we all know Microsoft knows best

2 Zips, Desktop copy which works and Menu copy that doesn't

And both copies reside on my D Drv

FYI I copied the menu zip to my desktop, opened zip, clicked on shortcut and it works so not to sure these are going to help resolve it

The attachments have come from where the shortcut is located i.e. desktop and menu folder

This path is correct (does exist)?
C:\Program Files\uvnc bvba\UltraVnc\vncviewer.exe

Hi
Yes that is the correct target path. Are you saying they both have the same path? If so then I'm not surprised. If I copy the shortcut from my Menu folder to my Desktop using XY, the shortcut changes to this path even though the one in the menu folder shows the x86 path.

If I look at the properties of the same shortcut in the menu folder using File Explorer they show correctly i.e. without the x86 added in

I've had a quick look thru some of my other shortcuts and I wld say the issue relates to those pgms that are 64bit i.e. in the Program Files folder rather than the 32bit in the PF x86 folder.

But why do the shortcuts work from my Desktop folder and not my menu folder when both are on Drv D? The path is correct when on my Desktop but changes when copied to my menu folder

In other words it seems like an issue between XY and Win 11

This mechanism is in place since 2022-01-20 and it should work in your case as well: I'm amazed that's not the case.

Anyway, the correct bitness-safe way to create such a shortcut is to use the environment variable %ProgramW6432% for the path. Many LNK-creating apps don't know this.

Change the target to this:
"%ProgramW6432%\uvnc bvba\UltraVnc\vncviewer.exe" 192.168.1.125

Ok, not sure how to implement %ProgramW6432% into my shortcuts, I'll look at this later after work.

Still very odd that my Desktop shortcut works fine when both are on the same drive D and both work if I use MS File Explorer [FS]. Is the later to do with FS is 64bit and XY 32bit?

Thanks, I'll let you know how it goes

Right-click the LNK file, then choose Properties, and enter the variable into the Target field:

Hi
What a STAR It works, fantastic. In all the years I've used Windows this is a first using this solution
Many thanks for your help Trial period back on track, looking good
Mark