We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
Block-level sync for VeraCrypt not working post 83.4.152 update
Greetings all,
After DB auto-updated to 83.4.152, I noticed that the block-level syncing doesn't seem to be detecting changes anymore for my VeraCrypt container.
Before the update, everytime I di...
Hi all, we've brought this to our team and wanted to follow up.
While we've presented a workaround: either by turning off the "preserve file modification timestamps" setting in the application or naming the file with a ".tc" or ".hc" extension, we want to be transparent about our current priorities and unfortunately, this means that we won't be able to delve deeply into this in the near future.
We're still tracking these reports, and will make sure to inform you right away of any changes.
Thanks for understanding .
Walter
Dropbox Staff
Dropbox StaffHello there JhonyWalker - thanks for the report!
As your inquiry echoes the OP's description and some similar reports we had from other users, I moved your post under this thread to keep things neat around our Community.
As John L.2 mentioned above, our team is looking into this matter while we speak while, in the meantime, you can try disabling the "Preserve modification timestamp" in VeraCrypt and/or TrueCrypt's preferences or (quoting John here) "touching" the files to force them to sync up.
(https://superuser.com/questions/10426/windows-equivalent-of-the-linux-command-touch/764721#764721)
Thanks for your patience while we look into this matter and let us know if you come up with any additional questions.
Hey Guys,
for those who have still problems. If your changes to a file or a container are done, just try to pause the sync in dropbox. Wait some seconds and then resume.
If I do so, dropbox recognises a change and is syncing. And it is using block level sync.
Just a work around. I will try to automate this for my needs.
Maybe it helps.
Greetings
FatCharlie
Pausing syncing doesn't seem to work for me. I just opened a ticket but since this has apparently been going on for about a month, I'm not very hopeful. pCloud looks like a good alternative. Has anyone use that service?
Hope dropbox team will expedite resolving the issue.
I have also been experiencing this issue after using Dropbox for years and years with Truecrypt and Veracrypt without issue. Even when I uncheck the preserve modification times option I still have problems on Windows 10. Dropbox will sometimes claim the file is locked and then refuse to sync even though Veracrypt is closed and has no handles open. I suspect there is a race condition where Dropbox detects its own lock on the file and then refuses to upload it. The only way I have been able to force a sync is to open the container in a hex editor and modify one byte, save the file, restore the byte, and save again. This triggers Dropbox to sync the container.
Something definitely changed from all previous versions of Dropbox.
