improve MOVE/MOVE conflict with Windows virtual files

The usual way to solve a conflict with MOVE/MOVE is to allow duplication with the client and server names (from the conflicting MOVE requests).
The main issue we want to solve is to find a way to avoid running into user confusion following a MOVE/MOVE conflict when the client is using Windows virtual files.
In such case, the destination folder on the client side will loose any virtual files (i.e. placeholders without data).
In itself, this is no data loss as the files will still exist in the server but can easily lead to user confusion.
The worst would be if the user delete the folder created on the server before realizing that the only existing copy of the files exist in this folder.

We need to warn the user about the MOVE/MOVE conflict and rollback the change on the client side such as not to create empty folders.