XYplorer Beta Club

Well, that sounds like a mere theoretical approach. Note that XY provides working portable devices support for years now for all Windows versions apart from Win10 Creators Update. It's Win10 Creators Update that broke it, not XY. I will need to find a way around it, and it will take to get my hands dirty in the guts of Win10. Theory won't help much here.

What language are you working in?

I actual do this with a nodejs application which uses a VStudio C# command line application for dir and file data (for win).

One full year is gone ... But this XY BigBug is still alive.

Hope it can be fixed in XYplorer 19.xx.xxxx

IT'S ON MY LIST.

Come, does anybody of you really think that this constant nagging does any good?

I close this topic now.

FYI: I'm now began tackling this issue. This is probably a longer way to walk. Each of the coming releases will have a couple of silent changes under the hood, all related to Portable Devices but not mentioned in the change log (it's just deep down technical stuff).

So, please test the handling of Portable Devices from time to time and let me know if anything stopped working alright.

And those of you on Win10 Creators Update and later, please let me know if Portable Devices finally started working again. Then we have reached the end of that way. And can open a .

Could anybody on Windows 10 version 1703 (or later) feedback whether Portable Devices work now with v19.00.0104?

1804 RS4 Build 17134.1

Doesn't work, "Internal storage" has no content (while Windows Explorer displays it just fine)

v19.00.0105 any better?

I'd say: worse

Clicking on the + sign in front of the entry for that device (it's called "AOSP on Hammerhead" -> Custom Rom on my old Nexus 5)
leads to a spinning mouse cursor and a XY instance that doesn't react on mouse clicks any more (but it is NOT in a "non responding state").

Specifically: The tree and tabs are blocked completely, other areas (items in a list pane, the menu, etc.) are clickable

Damn.

OK, time to setup my own Win10 system.

Sure ! I can't understand how is it possible now to fix a bug without having a dev AND a test environment W10/x64.
I missed something ?

Well, the important thing here is that *I* can understand it. But thanks for sharing your personal deficiencies.

As you can see in my new signature I got Win10 up and running. And -- that was the harder part -- got my VB6 environment installed and kicking. Yup. Tomorrow the bug fixing can begin...

PS: And congrats to Senegal! First team that was actually pleasing to watch. Hey, it's a game, it's played.