XYplorer Beta Club

I'm not sure if this should be a feature request or a bug.

I've enabled Support overlong filenames but when XYplorer opens a file it passes the filepath without prefixing \\?\ to it so long path files fail to open.
I remember reading some time ago that thumbnails or hover box won't work for these files and that's fine but opening the file should work provided the associated program supports it, right?

I've noticed when I double click a video file in M$ File Explorer the program is launched like "C:\Programs\Video Software\video-player.exe" "\\?\D:\someveryveryveryveryverylongpath.mkv" whereas XYplorer launches it like "C:\Programs\Video Software\video-player.exe" "D:\someveryveryveryveryverylongpath.mkv".

That applies to normal and custom file associations. I'm using 32-bit.

Ah yes. You know, when I added support for overlong filenames they weren't hardly any apps that could deal with overlong files, prefixed with \\?\ or not. So now I made some tests on Win11 and yes, things changed. The next beta should work better.

Tried 0301 but it's still not working for me. Either normal or custom association.

I have a 262 char filepath and when double clicking the video player won't play the file and I still see XYplorer opens the file without the prefix.

Can't explain. The prefix is definitely applied and it fixed it for me.

I have a problem that seems related to this discussion.

I have a series of toolbar buttons that run bash scripts which are failing because XY is adding a prefix "\\?\" to paths where it is not expected.

Consider this script (it builds a command that will be run with "openwith" on selected files):
Note the final command is being run through a temporary batch file so I could see what was being run. The batch file looks like this:
When executing the script, the echo command gives:
However what is being run is: We can see there is "\\?\" being added erroneously.

Strangely, I have other similar scripts where this does not happen.

Cheers
John

Edit: rolling back to v28.00.567 resolves this issue for me.

JohnM wrote: ↑12 Nov 2025 23:24 Edit: rolling back to v28.00.567 resolves this issue for me.

The next beta should resolve it too.

So it does. Thanks