Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Solved
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 .
I have found a solution that works for Truecrypt and prob Veracrypt. On Truecrypt go to Settings\Preferences deselect "Preserve modification timestamp of file containers" and do this on all your machines. Now the whole folder will sync and the time stamp of the folder will update. It takes much longer however as it doesnt appear to be using the block level sync.
Hope it works for you as well.
Thanks GH74!
After disabling this preference in VeraCrypt (which is really used as a security feature to preserve the privacy of the encrypted container), it triggered DB to sync after dismounting the container. Consider my entire container is several GBs, DB seemed to sync it fairly quickly, so it looks like the block-level sync is still working, but only if the DB service detected that the file had change.
Hope this works for all users that find this thread. Please let us know if there's is an alternate solution that preserves the intended VeraCrypt / TrueCrypt privacy functionality of not modifying the timestamp during dismount.
