We are seeing strange behavior when Writable volumes are enabled and how it handles deleted files. Here is the scenario:
-User copies from from Directory A to Directory B
-User deletes file from Directory A
-User then attempts to copy file from Directory B to Directory A
-Windows clams the file already exists and asks if users should copy and replace or not copy at all
Why would windows think the file exists when it has been deleted. We've also notice that deleted files do not go to the Windows recycle bin.
Maybe this behavior is by design and if so is there a way to prevent it?
We are running AppVolumes 2.12.1.103