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 had the exact same issue yesterday. I have used a Mac for years and recently moved to a Windows 10 environment. I thought using Dropbox as I had successfully for years on the Mac would help in moving my files to the new system. I spent at least 4 hours yesterday when my PC got stuck in a boot loop, trying to solve and restore to an earlier point and received the exact same error with the cache file. I now see this is an issue that a Dropbox just can't resolve, or won't resolve. So that means I am done with Dropbox. And the worst part is, after a year of this issue being discussed here, I see there is still no real solution. I'm screwed. I have to do a clean install. Another day of productivity down the drain. I will be alerting every person I work with in media (and there are many) that they should find another cloud storage solution, be it Google, Apple, Microsoft, or whatever. Because Dropbox can't get a known serious issue resolved in well over a year. It's embarrassing, frankly.
I gave up on Dropbox a week ago and am now using Tresorit. Will be closing my Dropbox account once my testing of the new system is done.
My solution, for now (because even excluding .dropbox.cache from the image doesn't seem to guarantee that Dropbox still doesn't somehow corrupt the restore points), was to acquire a second SSD for my laptop and move the dropbox folder there. Annoying that this was the only solution, but Dropbox is used too much as a part of the workflow (so I can't replace it yet), and I must have the restore points available. :slight_frown:
How do you like Tresorit?
We have a business account and twice now have run into issues with this wasting countless hours. This is ridiculus considering how long this issue has been outstanding.
I had to cancel the Tresorit account too. It did not work reliably. I had three computers synching through Tresorit. It would not reliably synch every file on all three machines. Although I was paying for the business level service Tresorit seemed to not like synching more than 500,000 files. I contacted them within 3-4 days of getting started. By the end of the 30 day trial period they had not come back with any solutions. The customer service person was very polite but did not every have a solution. I have not tried any other service. Currently without real-time off site storage/synching. Please post if You find a workable solution. Thanks, Dan
Sorry to hear :( This is an absolute mess. Neither registry fix below works:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToSnapshot
$UserProfile$\Dropbox\*.dropbox
$UserProfile$\Dropbox\.dropbox.cache\*.*
$UserProfile$\Dropbox\.dropbox.cache\attrs_cache\*.*
$UserProfile$\Dropbox\.dropbox.cache\icons\*.*
$UserProfile$\Dropbox\.dropbox.cache\new_files\*.*
$UserProfile$\Dropbox\.dropbox.cache\old_files\*.*
$UserProfile$\Dropbox\.dropbox.cache\placeholder_cache\*.*
$UserProfile$\Dropbox\.dropbox.cache\prefetch_cache\*.*
$UserProfile$\Dropbox\.dropbox.cache\qebcobkqbgpbzfynfuwbof\*.*
$UserProfile$\Dropbox\.dropbox.cache\qebcobkqbgpbzfynfuwbof\placeholder.*
$UserProfile$\Dropbox\.dropbox.cache\tmp_dirs\*.*FilesNotToSnapshot is what System Restore observes. I can verify that the Dropbox cache files are indeed NOT backed up when the files/folders are excluded in the registry. There is a small app System Restore Explorer where one can view the contents of the snaphot. Not quite sure why it still fails. Perhaps the original cache files contained prior to the snapshot is seen as non-conforming during general file verification before over-writing. All the client machines are set for on-line sync only. Not that it matters though.
Creating an additional partition (drive) on the client machine and have all syncing take place there and disabling system restore for that drive is one workaround. That was mentioned earlier in this thread.
Another workaround was to setup a dedicated server (virtual machine) for Dropbox with local/cloud sync. We then setup a mapped drive on the client machines pointing to the local Dropbox server. Doing this, of course, does not require installing the Dropbox app on the client machines. This may not be ideal in some situations if one needs local Dropbox app notifications/interaction. FYI: If you try to point to a mapped UNC path within the Dropbox client app preferences it will not comply.
If no fix is available soon we will be bailing before our renewal.
My reply keeps getting deleted. Sorry
