Issue with Proton Drive file renaming and data duplication problems.
Issue with Proton Drive file renaming and data duplication problems.
I rely on Proton Drive for backing up my data, and during a recent attempt to reorganize the folders in my account, I noticed that files—around 860 GB—were not only renamed but also duplicated extensively. I halted the process once it had copied roughly 60 GB, though significant damage remained.
I reached out to Proton Tech Support, who acknowledged my inquiry and mentioned they’d shared details with their developers, but offered no further assistance. I don’t have access to any data from before this incident. I’ve begun manually reviewing each folder and removing duplicates, but the sheer volume makes it impractical.
The core issue, as I understand it, is:
- I must delete the duplicated files (this part is straightforward),
- And rename all files in every directory that had the following appended to their names: (# Name clash "Date of the Incident" "RandomUniqueAlphaNumericString").
Any guidance would be greatly appreciated. I’m not optimistic about finding a more efficient solution. I’ve already explored Proton’s mass renaming tools, which mostly work for single directories and sequential naming.
My system is Windows 10 fully updated as of the time this was written.
Instead of using the Command Prompt, consider PowerShell.
For instance:
https://techcommunity.microsoft.com...e-same-size-on-your-computer-via/ba-p/3787635
At first, you might use Get cmdlets to locate duplicate files.
Subsequently, employ other cmdlets or scripts to handle the next steps.
Example:
https://helpcenter.trendmicro.com/en-us/...tmka-20817
(Reference the PowerShell section).
But it all hinges on your readiness to write some code. Either directly or via scripts created by others. Perhaps with a bit of adjustment on your end.
The key point is to make sure all crucial data—whether duplicated or not—is stored somewhere safe, away from your current machine, and that it can be recovered and understood.
Take some time to research PowerShell further and think about what you’re comfortable trying and the risks involved.
80/20 Rule
It’s likely just a handful of cmdlets will address 80% of the issues caused by Protron. You’ll then need to fix the rest manually.
There could also be alternative ideas or tips from other users who faced similar challenges and found solutions.
After spending the last few days working on it, I finally completed the corrections. Using Windows File Explorer Search, Sort, and Group tools, I managed to remove the duplicate files, and by applying some clever, temporary folder changes, I was able to rename everything correctly. Thanks, BRU dev team!