XYcopy does not handle copy/move to Network Drive

[stphn17]

Hello,

I have background processing activated for all file operations, but unfortunately the copy to a network drive opens up the windwos copy/move dialog instead of being handled by XYcopy in the background.
Strangely, the copy from the network drive back to my local drive is being handlded by XYcopy in the background.

Reason why I am writing this, is that it is quite bothersome due to the fact that XYplorer/Windows keeps "lagging" when XYplorer copys using the normal Windows Dialog. No idea why this happens.
But, if the copy/move would be in background, XYplorer is unfrozen and can be used to queue further copy jobs.

Hope there's a fix for that.

[admin]

Hi,

XYcopy has no problem with copying to network locations. There must be some other reason for your issue. Are you talking about a mapped drive?

[stphn17]

Yes, the network share is mapped as the letter "Y" in Windows.

[admin]

Tested that. No problems. Hard to say what's causing your issue.

[stphn17]

Maybe try it with a bigger file? I use e.g. 300 MB files right now.

I tested it now with a complete fresh install (portable version) of XYplorer, but the same behavior comes up.

Actually, I just checked Task Manager and indeed XYcopy.exe is shown in the Task Manager, but still, the Windows Copy Dialog pops up, when moving from local drive to network drive.
If I chose the other way, from network drive to local drive, no Windows Copy Dialog pops up.

In both cases, XYplorer says that background jobs are scheduled and enqueued.
Which might be right, becasue copy operations are happening one after the other, but still, for each operation the Windows Dialog pops up.

[admin]

Check your settings in Configuration | File Operations | File Operations | Background Processing | Apply to...

[stphn17]

"Apply to" is set to "Copy", "Move Cross-Volume" and "Backup".

I just tested it on a different Computer, with older XYplorer Version (20.80.0300) and there I have the expected behavior: Copy/Move to Network Drive is completely in the background. No windows copy dialog.

I noticed that even the log is different:
Computer B (correct behavior, XYplorer 20.80.0300, XYcopy 2.10.0155): Custom Move/Custom Copy
Computer A (incorrect behavior, XYplorer 22.60.0100, XYcopy 2.10.0184): Move/Copy

Update:
I updated the older XYplorer version on Computer B, but it is still showing the expected behavior.
It's very strange.. I cannot explain the issue.

[admin]

So the same XY version is behaving differently on two computers.

1) Is the XY configuration same of different?

2) Is the Windows version same of different?

[stphn17]

Both Configuration Files are differnt.
I even tested it with a new, portable Download of XYplorer on Computer A, and it's the same behavior.
So I think the config file is not the culprit. The essential settings, are all the same.

Regarding Windows Version:
Computer A has Windows Professional Version 10.0.19044 Build 19044
Computer B has Windows Enterprise Version 10.0.19042 Build 19042

I just noticed another behavior: Custom Copy operations seem to completely fail on Computer A.
I just wanted to use XYplorer to copy from one folder to another on the same local drive, with background processing but instead the Windows Copy Dialog came up.
The XYplorer log also states that a normal "Copy" was executed, instead of "Custom Copy".

All, although "Use Custom Copy" is enabled.

EDIT:
OK, I think we're getting somewhere.
The entire time, I was copying from a OneDrive Folder on Computer A, whereas on Computer B, I was using a "normal" Folder.
I just tested the following on Computer A:
Copy/Move from "Downloads" (not in OneDrive) to Network Drive: Custom Copy works.
Copy/Move from "OneDrive" Folder to Network Drive: Custom Copy doesn't work.

I could recreate the same behavior on Computer B.
As soon as I chose a Folder in OneDrive as the "Copy From"-Location, custom copy doesn't work anymore.

EDIT 2:
FYI: Same behavior I could not recreate with the Dropbox Folder. So it must be something specific to OneDrive integration.

EDIT 3:
So, I just thought that maybe it's a problem of Windows that "no external copy handler" can be used with OneDrive and I tried out TeraCopy.
Using it in Windows Explorer, it's absolutely not a problem. TeraCopy handles the copy/move operations.

So I tried the TeraCopy integration with XYplorer, but it shows the same incorrect behavior! TeraCopy will not be chosen to handle the file operation when copying/moving from a OneDrive folder, instead the standard Windows Dialog is used.

[admin]

Yeah, good analysis.

What is the full path of that OneDrive folder?

[stphn17]

steph\OneDrive or resp. C:\Users\steph\OneDrive

It's basically the default installation folder.

[admin]

Okay, what you see goes back to this (I will check later whether this is still true today):

Code: Select all

v18.50.0118 - 2017-10-30 12:40
    ! OneDrive in Windows 10 Creators Update: Could not copy/move items anywhere 
      from OneDrive location using Custom Copy. Fixed. Now shell copy is used 
      for the job.

But shell copy will still run in the background, so it should not be a big problem. XYplorer should NOT be frozen.

[admin]

In the next beta everything will work as expected. The OneDrive folder now behaves like any other folder.

[stphn17]

great news! thanks for fixing it!

EDIT:
I installed the latest BETA and, can confirm that it is working now. Thank you!