A few months ago I installed Proton Drive on my new PC. It started having issues so I sent it back in for repair. I uninstalled Proton Drive then deleted my files for privacy.
Last week I installed Proton Drive again. To my surprise, it scrambled all of my files locally and remote. All my root folders were deleted and my root is now filled with “Delete conflict” files and folders.
I reported this to Proton immediately. After giving them my logs and details support told me…
- This is expected: “Proton Drive is designed to synchronize ALL changes, even after long periods of not syncing”
- No rollback is possible: “Please note that we are unable to revert this behavior. You will have to restore the files manually”
- They plan to address this: “Regardless, we will absolutely be making improvements to avoid such problems in the future.”
For me I have about 100 files to address, which is manageable, but for others I’m sure this would be a showstopper. The delete conflicts don’t have version history either, so I have to figure out how to weave everything back together.
@Dark_Arc @bl4kers
I can understand the confusion. But it kinda makes sense… if my hypothesis is correct.
Proton Drive has the concepts of “My Files” and “Computers”. Files stored under “Computer” (where you can have synced files for up to 10 computers, according to docs) tracks the files for each computer individually.
So when you uninstall Drive and delete the files, they are only stored in the cloud. But after reinstalling it again, it sees the files locally for that computer is gone … so it gets removed in the cloud.
Had these files been moved to “My Files” in before the reinstall, this should not have happened.
At least, that’s my theory.
Still, I would expect a sync program to ask “hey, do you want these files restored, to merge the local state, or replace the remote state?” before doing anything else.