I get an error message that Windows System Restore failed?

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

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 :(