I get an error message that Windows System Restore failed?

Are you kidding? Have you read this thread? I did a very comprehensive test.

There is no solution other than uninstalling your software.

You had me believe that you were working on this issue.  I see now that you were just trying to pat us on the head and say "there, there".

I'm out.

Sorry to hear you feel this way DeeRoche - I wish I could help more. Unfortunately, without any additional information, I won't be able to.

Should you need to look further into this, please go ahead and log a ticket with our team providing the specifics of the affected device through the following page:

https://www.dropbox.com/support

If there's anything I can help with in the meantime, do let me know. 

Thanks for nudging me here coxlegal.

Would it be OK if I reached out to your Dropbox associated email address to work on this together?

Hi Walter - this continues to be a problem - I have contacted dropbox support as you suggested previously with the details and received no reply

The error message I get is still the same as before

I only continue to use Dropbox as work uses it - and at work we have had the same issue of restore not working on other computers using Win 7 where dropbox is installed

The error message I get is on a Win 8.1 system is

System Restore failed to replace the file (D:\Users\*****\Dropbox\.dropbox.cache\qebcobkqbgpbzfynfuwbof\placeholder.bat) with its original copy from the restore point. An unspecified error occurred during System Restore. (0x80070780)

I have like other people on here deleted dropbox and all files and system restore works fine - so please dont ask us to contact Microsoft

Drive D has been disabled in system restore - and that made no difference. For information Drive D is a recovery drive partition

I have had to resort to making system images as a work around but this really isnt satisfactory

Why arent Dropbox developers looking at sorting this? My Dropbox contract renews in September - I will be looking elsewhere for the company if it isnt resolved

Richard

Walter, I am a software developer. When our clients say there is a problem, and provide step-by-step instructions on recreating the issue, as I did a few months ago, we don't say "I can't fix it because I can't see your results"  we follow the steps given, recreate and fix the issue. 

The only bug that can't be fixed is one that can't be recreated.  This is a surprisingly easy bug to recreate.  It would take less than 20 minutes to produce on any Windows 10 machine.

Dropbox is far superior to anything else out there doing what you are doing.  But this issue could be a product-killer for you if it becomes common knowledge.

Same issue here. Can't believe it's gone on this long without a resolution. I'm working on a user's computer, I have wasted hours on it because I can't do a simple restore to before their issue happened. The error is the exact same as the others are getting. Stop blaming Microsoft for a clear issue with your software. I have been in IT for over 15 years, and have not seen an issue like this with System Restore. It's quite clearly something with your software causing this. You said back in March you were passing the info on to the dev team but obviously that hasn't happened. 

I will be speaking with all of my business customers (approx 500 seats) and letting them know that Dropbox effectively kills System Restore and encouraging them to migrate to another provider unless a solution is reached quickly. 

Same issue here, has this been addressed yet or is there an accepted workaround yet?

I've unlinked my account on this machine and deleted the dropbox folder but am still getting the placeholder.bat error message. I had a bsod fail during a vpn install and this bug means I'm now basically screwed if I can't do a system restore.

Have been a happy customer for many years now but this is a BIG problem for me especially given the premium price I pay for the smart sync stuff over onedrive.

Hey there people - thank you all for your constructive feedback and patience on this one. 

Apologies for the tardy response but I was checking back on this internally and I just found out that our team are aware and working towards a fix as we speak.

In the meantime, a potential workaround is to exclude the .dropbox.cache from the system restore which can be done via the FilesNotToBackup registry -  note that this is not something we support, and should only be completed by advanced users.

We'll make sure to keep you posted on our team's progress on this via this thread so make sure you're subscribed to it so you can receive email notifications (you can do this by clicking on the upper ellipsis button on any thread and then click on 'Subscribe').

I hope this helps to some extent! 

Have added the .dropbox.cache folder location and the same folder location with a *.* wildcard to the FilesNotToBackUp registry key as suggested by Walter above.

Though I suspect this might help people moving forward when creating and subsequently restoring from a *new* restore point created *after* making the suggested registry changes, it does nothing to rescue the poor victims, including myself, that are trying to restore from an *existing* snapshot. It looks like the process restores the registry first which effectively wipes the new key entries and then just goes ahead as before trying (and failing) to restore that **bleep** placeholder.bat file, with the same fail outcome.

A complete wipe and rebuild is looking increasingly likely at this point which, frankly, is a disaster. 

Please can someone at dropbox give us a step by step to get us out of this? Have you guys reached out to microsoft to request a best practice way of excluding a file or folder already contained in a snapshot? If it turns out this is not possible due to a 'microsoft thing' rather than a 'dropbox thing' and out of your control then it would be great to know sooner rather than later so I can bite the bullet and get on with a rebuild. 

yes having the same issue here . . . windows system restore broken by dropbox . . 

I had to do a complete reset of my machine, and I am disappointed this hasn't been resolved yet. Its good that there is a possible workaround. It would be better if it were verified, and it would be of course better if it were fixed completely.

Let me complain for a moment. I am also a software developer. This isn't the type of issue that the companies I have worked for would let "sit". We would work on it until it was fixed; at most of couple of days.

For a company like dropbox, when your system is not only just not working, but your service prevents the host operating system from functioning properly - that's terrible. Your service is harmful, at best negligent.

We are also having the same issue with system restore failing on Windows 10 Pro (Build 1903) systems with Dropbox installed. We had a faulty driver installed on one device which caused a BSOD loop and so the device needed a simple system restore, however, that failed with the same error mentioned previously in this thread. We eventually had to restore the device from a disk image after all else failed.

This issue has caused us to lose about 3 days worth of work on that device, as well as almost 2 days attempting to troubleshoot the issue and finally restoring from a backup disk image after reading this thread. We are still attempting to locate/restore newer documents, work, and program files that were not included in the latest disk image.

For the moment, we have modified registry values on all devices to exclude the Dropbox cache folder from system restore points, however, this obviously can not be a permanent fix for this issue! Please update your software to resolve this issue, or we will begin looking elsewhere for cloud backup services (OneDrive is now syncing for the first time as I write this post), and we will be advising our business partners to do the same.

This is a very serious issue that should not be taken lightly, as anyone who has created, or is about to create, a system backup while this issue remains unresolved will be unable to restore their system if it fails at any point in the future. Your team should at least make an announcement on the app so that users are aware of this issue, and can create regular disk images until the issue is resolved, or at the very least they can be cautious and temporarily avoid unnecessary software/driver installs or any other risky activity that could result in a system failure.

Please consult your dev team and let us know in the thread when this issue is expected to be resolved. I've just realized that the initial post is from October 2018, and so the issue has been around since at least then. This is completely ridiculous. It has been almost a year now. This is something that should be a quick, simple fix on your end for a very serious issue that could affect any of your Windows users at any point in time and cause them to lose their system builds and program files. Please keep us updated.

Thanks for the extensive report sprgroup!

I have already relayed all the details of your problem to our engineering team.At this point, they’ll evaluate the problem and work toward a solution.

Apologies for any inconvenience this might have caused and while I can’t say exactly how long this is going to take, I’ll make sure to keep an eye on the team’s progress and let you know as soon as I have an update.

In the meantime (as you mentioned) the best way to tackle this is to keep excluding .dropbox.cache from the System Restore (see my previous reply for more info). 

So I ask for an update or a step by step or just a simple "we don't anticipate having a fix for this issue soon" over a week ago and am ignored completely. sprgroup asks much the same thing and gets a response in a few hours. Thanks dropbox, way to treat the little guy.

Sorry about this MartyBook - that was an oversight from my end to be honest, as I'm not in the position to advise on a 3rd party service (the FilesNotToBackup registry to be exact) and/or provide a step by step guide on how to remedy this. 

As you know, the team are aware and working on this. I'll make sure to update this thread once I have a more concrete solution for this - thank you all for your patience. 

Hello !! Sorry for my broken English . . . 

Same proble here, as a result we had made 2 times format our laptop, we lost days of work searching what cause the problem. Now we cannot trust to download and to work again with DropBox. It is very hard to understand that at 2019, a pioneer to the sector DropBox, cannot solve a problem which DropBox itself cause to its clients with subscriptions.

And not only that, the problem is not to its software but damage the Operating System.

Microsoft give a restore point option in order to feel safe in any hard situation and Dropbox not only canceling this option but have you to run, to search and to spend time, money and thoughts for NOTHING !!!!

DropBox in this situation, help you with a lot of SILENCE !!!!!

At least GIVE US A FIX BUT A REAL FIX (When our pc stuck at the point that windows restore point give us a message that cannot perform due to DropBox cache file xxxxxxxx.bat

I dont know what more i can say !!!!!       

Has any one made progress on this issue?  I discovered that I had a problem 7 days ago - but it took me 5 days to find this discussion and understand what is wrong (mostly understand).  I did start to tinker with the registry modification but I don't know enough and haven't seen any change from the one attempt to modify the registry (syntax probably wrong)

At this point, whenever Windows updates and trys to make a restoration point, my files go to the earlier version of the last good restoration point.  Then I wait until Dropbox downloads the latest version of my files.  The first time 7 days ago I had to wait 2-1/2 days to get the correct files in place (660,000 files had to index).  I have since removed a big cashe of files from my DropBox so these re-sets don't take so long.

I can command Windows to make a restoration point but I can't restore to that new point.  Dropbox has really gummed up the works here!!!

So I'm really suprised that Dropbox has gone 11 months with no resolution on this issue.  I'm sure it is affecting WAY more customers than know about it.  Dropbox is actually lucky that Windows is pretty stable these days.

You guys that have left DropBox, what did you go to? (I'm sure they are no longer listening in).

Thanks all

So, have you created this registry entry to exclude .dropbox.cache as part of a future version of Dropbox?

I am also having this problem. When will a solution be provided?

Dropbox have known about this issue for years. Solution should be fairly easy to implement but nothing has happened, so I wouldn't expect DP to do anything about it :(