Rage-free, succinct, and hopefully useful for Joe and his team to sort these issues out with great haste. (EDIT: I don't mean to sound impatient either...I only say it that way because I have had file reversion and risks of data loss throughout this whole week and as we speak.) File change reversion - Sync reverts a file to an older version (If this is not caught and corrected manually by the end user downloading the correct version from the Web Console Change History, permanent data loss is imminent!) File duplication - Sync creates a duplicate entry entitled the same but with an (on XYZcomputer) appended. File is often partially blank or outdated. Renaming leaves both - Sometimes, Sync will leave a renamed file intact, forcing end user to delete the old one Sync delay - Sometimes Sync will not function at all until two default scans are run, presumably due to how WSA communicates with the cloud. Storage space error - Sometimes, Sync will show that only 1GB of storage is the maximum allowed, instead of 25GB More to come as I observe them or can add more details to the existing list... Again, 2014 release definitely made the existing issues worse for me.