0x80070780 on system restore for inaccessible Win 10

[Mmballew88]

My desktop crashed due to power outage, cannot login, trying system restore ends in attached error 0x80070780, apparently a system restore is not a good idea with dropbox as I've read many issues with syncing corruption, so how can I restore, should I just delete all Dropbox folders and file off partition?  I'm not sure if I can access them on C:?  See attached screenshots

[Mmballew88]

---

@Mmballew88  wrote:

My desktop crashed due to power outage, cannot login, trying system restore ends in attached error 0x80070780, apparently a system restore is not a good idea with dropbox as I've read many issues with syncing corruption, so how can I restore, should I just delete all Dropbox folders and file off partition?  I'm not sure if I can access them on C:?  See attached screenshots

---

Also I'm using smart sync on most folders, I don't mind downloading again, and to make copy of files onto usb.  I don't understand file storage between C drive and H partition

[Jay]

Hi @Mmballew88, thanks for messaging the Community!

Could you try doing a system restore without including the Dropbox folder and cache to see if this helps? 

Regarding the H:\, this might be a method on how Windows restores files, so it's not something we can advise on, unfortunately.

Keep me updated with any progress!

[Mmballew88]

I was finally able to fix a currupted boot file and get back in and let dropbox sync, however, I have noticed smartsync does not seem to maintain it's folder (local/online) status very well, I have tried to set multiple times but it doesn't take and a lot of files are trying to sync again, it may be tech support messing with something as i raised a ticket with support team, thanks for your feedback here.

[barbecue]

Under no circumstances should you use Dropbox on a volume that you need to use System Restore with. If you do, your system restore images will be created successfully, but will be corrupt and cannot be restored. There is no way to recover with System Restore once this happens. The only solution is to either do some half-assed workarounds that might or might not help, or to not use Dropbox with System Restore at all.

Dropbox has known about this problem for years, but has done nothing to fix or mitigate the damage.

Dropbox refuses to acknowledge that the problem exists or warn users about the problem.

Your best bet is to stop using Dropbox, and use a service that does not cause system corruption instead.