"Windows could not move the file. Trying alternate method." Why?

[emarkay]

Using JKD 3.32 with JkDefragGUI 1.01.
 
Occasionally I see the message: "Windows could not move the file. Trying alternate method."

There does not seem to be a problem, and it dies seem to move the data OK, but I am just curious as to the reason.

BTW, you all should be praised by the community for your fantastic work!

MRK

[jeroen]

JkDefrag is based on the Windows defragmentation API. It does not move files by itself, but sends instructions to the API to move files. Sometimes the API refuses to move a file, or moves only a part, thereby fragmenting the file. JkDefrag therefore checks if a file has been moved properly, and if not then tries again (by calling the API slightly differently). I don't know why the API sometimes refuses to move a file, or moves only a part of a file. It seems to happen most frequently (but not only) when a file is moved to a gap that was vacated just before, even though the same API has finished the previous move and reports the area now to be totally empty.

[WHRoeder]

This gap delay is what DIRMS.com posts as his major feature.
I suggest that when this happends, switch to the next zone now and retry later.

[jeroen]

I suggest that when this happends, switch to the next zone now and retry later.

I have tried many things, and have finally settled on the "alternative method". The normal JkDefrag method is faster and works fine in most cases, the alternative method is slower and takes care of the rest.