XYplorer Beta Club

Works fine here with all my three devices. In Win8.1 and Win10.

BTW, you can run a script by click through the Address Bar: right-click the "Script" icon in the Address Bar and click "Run Script" in the popup menu.

The context menu on Windows Server 2012 R2 is fine as well, even the 64 bit one
but not on W10...

The bug with the greyed out items exists as well and double clicking an .mp4 file
leads to nothing (while on a local drive WMP is started)

The bug with the greyed out items is fixed in the next beta.

Double-clicking issues seem to be related to bitness AND the opening app. I can open some files only via the 64-bit context menu. The double-click (or ENTER) only supports opening with 32-bit apps.
So there might be workarounds here by patching the registry.

The bug with the greyed out items is fixed in the next beta

Confirmed fixed in v19.00.0116

Well, I'd say this 15-month old bug is fixed now! XYplorer is back in business in Windows 10!

The rest are the usual MTP glitches. This protocol did not stop to suck.

BTW, I really like Win10! Looking forward to modernize the interface a bit, and especially go for that dark theme...

admin wrote:Double-clicking issues seem to be related to bitness AND the opening app. I can open some files only via the 64-bit context menu. The double-click (or ENTER) only supports opening with 32-bit apps.

I don't know if this info may help nail it down. In my case I normally use Image Eye x64 as my default image viewer and I too can open the images from the 64-bit context menu. However, I don't think it has anything to so with the bitness of the application itself. I say that because I installed the x86 version of Image Eye and verified Windows and XY were now using that version. I even did a reboot and checked again. The result was the same as I previously reported (i.e., double clicking on the image gives the error message, "The directory name is invalid"). Yet the image files open properly from the 64 bit context menu. So it must be something about the way the image is opened via the 64-bit context menu, the fact that it's a 64-bit operating system and the associated registry entries versus the fact that the program itself is x64 since the result is the same using the x86 version.

You cannot open it via the 32-bit context menu, right?

admin wrote:You cannot open it via the 32-bit context menu, right?

Sorry yes, I neglected to mention that but I did try. Correct, I can't open the image via the normal 32 bit context menu or from the "Open with..." menu.

I see this here as well with some file types (e.g. TXT, but not with JPG). Cannot explain it at the moment. The error message does not make any sesne. Might be just another Win10 bug...

OT What a shot!

GOSH, I'm still breathless. 10/10 drama points.

admin wrote: Well, I'd say this 15-month old bug is fixed now! XYplorer is back in business in Windows 10!

Thanks a lot for fixing this !

admin wrote:BTW, I really like Win10! Looking forward to modernize the interface a bit, and especially go for that dark theme...

I cannot wait for that dark theme.

Thanks, this is great, I did notice this doesn't call XYcopy ? or is that a setting I've missed ?

Twisten wrote:Thanks, this is great, I did notice this doesn't call XYcopy ? or is that a setting I've missed ?

Right, XYcopy cannot handle this crazy MTP protocol.

XY is the best file manager in so many ways...That said, others like "Total Commander" and two instances of "Windows File Manager" running at the same time have no problem dealing with my Note 8 files. Is this fixed in this shiny new beta?