Could be anything, even something to do with running as admin. You may have to uninstall your current version before installing v6. You can stop the prompt etc from:
Settings > Advanced > Automatically check for updates
I’d be inclined to wait a bit before trying to update to v6 as it has bugs that are still being ironed out.
Thanks, I thought that might be possible but will hold on for now if it is still in Beta,
Is there somewhere I can post suggestions for enhancements? For example it seems a real omission that when syncing two folders with 278GB of files already in place there is no option to “Skip” if they are identical. Only Replace, which is crazy.
If this is about Qsync, from my own observations, Qsync Client only replaces / overwrites files that are NOT IDENTICAL. It scans files and stores the data in C:\Users\USERNAME\AppData\Local\QNAP\Qsync
It “watches” any folder pairs for changes and compares them with the stored data, then replaces using the file attributes. Windows changes these attributes if a file is, say, copied, which can result in an overwrite of an apparently identical file. In any case Qsync still has to at least scan the folder pairs to build the databases stored in the above mentioned folder. So if you’ve copied files to the NAS from Windows, the initial Qsync scan still has to take place.
It can take a while to sync 278GB of data, but as it runs in the background I tend to ignore it.
If you want more flexibility you may want to look at HBS3 (Hybrid Backup Sync) where you can set up a sync job with schedules and rules / filters to suit yourself.
Note that in Qsync Client you may be able to speed up the process, or at least ensure a more stable connection, by enabling “LAN Sync”
Thank you for your report. We have confirmed internally that this issue occurs when installing via the .msi file. Therefore, we recommend using the .exe file to complete the installation instead.
We apologize for any inconvenience this may have caused. Our team is already working on a fix, and this issue will be resolved in the next release. Thank you for your patience and cooperation!