when pulling get progress but nothing copyies from phone

[KolodyazhnyyI]

i got this behaviour yesterday, when tried to pull from phone torrented music collection, which is large enough to not MTP got progress bar, like something is copied, and when finished-nothing appeared on destination drive

[Alex4SSB]

• Do you get progress when pulling single files?
• Did you enable the setting "Deploy AdbProgressRedirection.exe"?
• Is there actual progress in % or at least in total bytes?

[herrblitzkrieg]

Happens to me too here when I try pulling files from my phone to my connected external SSD. So it does pull the files but not to the external drive but instead the files go to '%USERPROFILE%\AppData\Local\VirtualStore\Windows\SysWOW64'.

[Alex4SSB]

@herrblitzkrieg Weird. Does this happen only with external drives?

I searched for the path you provided and got this: https://answers.microsoft.com/en-us/windows/forum/all/please-explain-virtualstore-for-non-experts/d8912f80-b275-48d7-9ff3-9e9878954227#:~:text=For%20a%20program,a%20hidden%20folder.

So with the suggestions from this link:

• Are you using the Microsoft Store version of the app?
• Did you try running it as admin?

[herrblitzkrieg]

• Yes, I am using the MS version of the App.
• I tried running ADB Explorer as Admin and this time it copies the files to '%SystemRoot%\SysWOW64'.

Again, this issue happens only when trying to pull a file/folder from my phone to any external drive like a connected SSD or conventional Flash Drive.

[Alex4SSB]

Are you pulling directly to the external drive root, or into a subfolder? There was an issue with that previously.

[NLSNPNT]

Same happens to me, it can only pull as Admin and it copies the file in the root directory of the partition that it's installed in this case C:\

[herrblitzkrieg]

It happens when pulling to external drive root. When pulling to a subfolder like 'E:\level1', the files land in 'E:'. When pulling to any sub-subfolder like 'E:\level1\level2' or 'E:\level1\level2\level3' it works as planned.

[Alex4SSB]

Okay, thank you @herrblitzkrieg I finally managed to reproduce the issue. I refactored the pull target path mechanism in the last version, and apparently didn't test your case.

The Store version is the cause for the weird paths - I wrote on this issue on the main page.

As a temporary fix, you can enable and use the experimental Drag & Drop support by adding the following line to App.txt: DragDropMethod:4; The current implementation requires building a full hierarchy tree of the current folder, which might take some time depending on the amount of sub-files of a folder.