Hi Michael,
Thanks for this. The actual hardware isn’t likely to be the issue, but more likely its how those files are managed by the system. DropSync doesn’t actually change properties of files itself, but it can copy various extended attributes of files which make them hidden. What is surprising here is that the files are not hidden in your source but are hidden in the destination. My only guess for this is that somehow the folder containing those files (on the destination) got set to hide contents or that there is some other mechanism (eg a file creation mask) on the destination that will make the files hidden at the time they are created. This might depend on the directory. For example files created inside your Library folder might be set to hidden automatically. These are mechanisms that would apply to your system and aren’t really in DropSync’s control.
If you want to investigate further you might want to check flags on your hidden files. You can do this in Terminal with
ls -lO filepath
where filepath is the path to the file you want to inspect. It may have an attribute “hidden” which you can change using
chflags nohidden