Bugs - long paths, files without extensions

[eriks]

1: Duplicate Cleaner doesn't handle files without extensions properly, adding a dot to the filename in some cases. Moving fails with an error message indicating the directory containing a file failed to move, not the file itself.

2: The destination path too long failure is completely unneeded. A mechanism to support up to 32k chars fully qualified names have been in place in Windows for at least a decade, please use it.

[DigitalVolcano]

Sorry you had trouble. Have you an example of a filename/structure that failed to move? What type of drive was it?

For long paths, you can turn on long path support in the Options Window (advanced tab). It's off by default as not all Windows operations support long paths (e.g. hard links, recycle bin).