Now it is important to note that this will only be of interest to users that have a mix of duplicated and non duplicated within the same mount point.
Because Drive Bender supports file duplication at the folder level, users need to be aware of how Drive Bender handles folder duplication when folders are moved.
The way Windows performs a folder moved will depend on where the folder is being moved to. If the folder move is localized i.e. the source and target locations are on the same drive, Windows will perform a folder rename operation. If the move is not localized, Windows will perform a folder / file copy operation, followed by a delete operation of the original folder.
So what does this mean for file duplication? Well prior to v184.108.40.206, a localized moved would result in the duplication state being retained regardless of the target folder, this be because the folder is renamed. However this is not the case for a non localized moves, because this is a copy / delete operation, the moved folder inherits the duplication state of the target folder.
To make this functionality more consistent, this was changed in v220.127.116.11. If a localized move occurs, the folder being moved will inherit the duplication state of the target folder.
Note it is possible to revert to the pre v18.104.22.168 method by changing a registry entry. One the server, open regedit and navigate to "HKEY_LOCAL_MACHINE\SOFTWARE\Division-M\Drive Bender".
Create a new DWORD value called "Enforce Duplication On Folder Move" and set it to 0, then reboot.