I haven't been able to reproduce this so far.
Would it be possible to provide some extra information:
-
A Process Monitor log of what happens. (Let us know the name of the file that has the error, too.)
-
File size in bytes, of the file that had the error.
-
From a Command Prompt, the output of:
fsutil sparse queryRange "C:\abc\xyz.ext"
Where
C:\abc\xyz.ext
is the path to the source file that had the error. -
Same again on the output file, to check if the ranges were set on retry, or if it simply skipped that stage after the failure.