Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Solved
I get an error message that Windows System Restore failed?
Hi
When I run Windows System Restore it fails with this error message
System Restore failed to replace the file (D:\Users\*******\Dropbox\.dropbox.cache\qebcobkqbgbzfynfuwbof\placeholder.bat) wit...
Hi everyone,
We're testing out some changes in v182 (currently in beta) that should hopefully help with this. Let us know if you continue to run into problems.
Thanks
I received a "quasi-tip" from someone at Carbonite that pointed me in a strange direction. Because I am in the middle of an incredibly critical and time-sensitive project, I cannot test it now. But, just in case someone has the ability to try it, here it is. Now, if the keys "FilesNotToBackup" or "FilesNotToSnapShot" do not exist, simply create them.
1. Start "Regedit"
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup
3. Add a Multi-string value with the Dropbox directory
a. Right-Click in the window on right-side
b. Select New
c. Select Multi-string value
3. Give the value a descriptive name, like "Dropbox"
4. Double-click the value to open the value editor
5. Enter the following string: %UserProfile%\Dropbox\*.* /s
(NOTE: This means to ignore all files inside the "C:\Users\{yourusername}\Dropbox" directory and Subdirectories.)
6. Click OK to close.
7. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToSnapshot
8. Follow the above steps 2 thru 6 for this key.
9. Close Regedit
10. Create a System Restore Point
11. Try to System Restore to the point you just created.
Please let us know if you were able to test this.
Good Luck & Best regards,
Jacob
Sorry all, bad news: This problem will not be solved. For Windows 10 users who care about their system integrity it's time to move on to alternatives. Personally I'll be initiating a migration to OneDrive both personally and for my company. A colleague has been trialing it for some time and it has certainly changed and improved a lot since I first tested it back in the day.
Longer explanation:
Having experienced a laptop crash firsthand which was not recoverable due to this issue I raised a support request with Dropbox on Sept 4th. It took a long time but eventually it was escalated twice to a specialist at their Advanced Support Team. On Sept 25th I was told "This issue has been logged with our engineering team in the past who are still actively working towards a solution."
After repeatedly asking for a progress update / ETA I eventually received a surprising answer on Oct 14th: "At this time, we are no longer actively working on a solution for this problem."
For six weeks after that I've been pushing to clarify their reasoning behind this as it does not make sense at all to me. Especially not when I see how many in here that sadly have been struck by the same issue. I can just imagine how many more have been affected which are not finding this information here. Unfortunately for every reply back to Dropbox support they have re-iterated their decision, their team is no longer actively working on a solution for this problem.
I've been a happy paying Dropbox customer since September 2009 so I'm not really wishing to leave voluntarily. Unfortunately I cannot really trust a company with my data that does not care about an issue as serious as this.
Just thought I'd let you all know to not have any false hopes about the future.
I too am now experiencing this problem. Like many people here, I found this thread and possible solutions to not contaminate the restore point AFTER it was already contaminated. All I can do now is vent here. I cannot believe that this has been going on for two-plus years with no clear fix. Instead, Dropbox finds it appropriate to stuff a jankey solution deep in some thread and call it a day? Wow. I've always enjoyed using Dropbox, and I think I've been using it for almost a decade now. Seems it is time to look for alternative solutions to Dropbox, and I'll make sure to mention this issue and Dropbox's lack of action for the past two years to anyone who is considering using the service or already is. Simply ridiculous and negligent.
Wow this is awful Dropbox. My system is also failing to restore because of your program.
I hope your devs can figure this out -- this is absolute amateur hour for a multi-billion dollar company.
I'm in the same boat as everyone else. Truly astonishing that they would allow this level of extreme dysfunction to continue for so long. I wish they would at minimum provide a warning to help avoid it, but clearly, THEY JUST DON'T CARE.
