XYplorer Beta Club

All of a sudden today, all day, while moving a selection of files, or selection of folders (sometimes just 1 folder), usually across volumes or a network share, often one of the files to be moved results in a failure and the source remains. The failed file in question is moved, or actually copied since the source remains. The error is always "clone filetimes" as follows. Any ideas what may be happening? I'm on version 22.20.0200. Files in question are excluded from anti-virus etc.

Custom Move from 10/16/2021 1:59:01 PM

From: I:\Folder1\
To: T:\Folder2\

Files processed: 14 (13 new, 0 over, 0 skip, 1 fail), 1 dir
Bytes moved: 90.40 MB
Transfer rate: 476.83 MB/sec
Created folders: 1
Remarks: Custom Move completed in 193.2 ms
Warnings: There has been 1 failed file.

------------------------------------------------------------------------

Failed files:

FAIL (clone filetimes) New I:\Folder1\file1.dat -> T:\Folder2\file1.dat |

So far my guess is that is has something to do with my upgrading Everything from 1.4 to 1.5 beta. That was the last system change I made, and I think it seems to happen when I try to move some files right after a quick rename operation, and perhaps one file is locked by Everything. I reverted back to 1.4 to see if the problem goes away. If it does I guess is has something to do with the options in 1.5 I have enabled for indexing, including property indexing.

Sorry but what has Everyting version to do with this error ?
I use Everything version 1.5 all the time and there is no influence of XY move or copy operation
or any other file operations.
It doesn't hook in any way in file operations and never locks files.
It just gets notified about file changes or creations and reads the MFT or file properties and updates its own index.

I agree with "everything" you're saying. It may not have been that. But for whatever reason the problem has gone away so far after reverting back to 1.4. Version 1.5 is in beta and perhaps there is an issue with exclusive reading of meta data, I dont know. I'll post more info if the issue persists.

Which beta version you are using ?
Current version is 1.5.0.1280a