Copy in error after successive searches

Hello,

I'm experiencing the following problem when copying files:

I've plugged a USB hard disk into my PC (Windows 11).

In one panel, I'm searching for a file on my internal hard disk.
In the other panel (corresponding to the connected drive), I copy the file I've found.
While copying, I carry out another search on my internal disk and launch another copy to the connected disk.
The copy job is then put on hold.
I launch a new search on my internal disk.

When the first copy is complete, the second copy, which was on hold, triggers an error of the type (the file cannot be found (2)) (I have it in French, so it's not the English version).
Do you have an explanation?

The topic Error when moving multiple files from search folder - #7 by Meridian
seems to match the same problem, but there is no change since then.

Are you really copying, or moving files?

Does the file, and where it's being copied to, still exist at the time it's trying to be copied?

Does Retry have any effect?

I confirm i'm copying.
Yes it still exists on the source.
No, retry give the same error.

Can you give detailed steps on how to reproduce what you're seeing?

E.g. How are you performing the file copies? (Drag & drop? Copy Files button? Copy & Paste?) What is being copied from where to where at each stage? What are the searches and when are they performed vs the other steps?

Hello, my first post detailed the procedure, but I try to reformulate it.

Source = Interal disk on right pannel
Destination = USB Disk on left panel

1- Seach a big file (=file 1) on Source.
2 - Copy it by drag and drop to Destination
3 - Seach a big file (=file 2) on Source.
4 - Copy it by drag and drop to Destination. It is placed on queue as first copy is till progressing
5 - Seach a file on Source.
When it's time for file 2 to be copied, i have the error.

It's as if the queued task made a reference not to the actual path of file 2 but to a path relative to the search.

Many thanks, I've reproduced it now.

1 Like

This will be fixed in the next update.

1 Like

Excellent. Thanks !