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 .
John L.2
Dropbox Staff
Dropbox StaffHi Tom30,
Block level sync should be working for all file types, regardless of file extension. Please let us know if that is not the case.
The issue where changes are not picked up automatically (which is specific to these applications) can be resolved by either turning off the "preserve file modification timestamps" setting in the application or naming the file with a ".tc" or ".hc" extension.
--J
John L.2 wrote:Hi Tom30,
Block level sync should be working for all file types, regardless of file extension. Please let us know if that is not the case.
The issue where changes are not picked up automatically (which is specific to these applications) can be resolved by either turning off the "preserve file modification timestamps" setting in the application or naming the file with a ".tc" or ".hc" extension.
--J
I just tried yesterday to turn on the "preserve file modification timestamps" setting but it caused the changes not to be picked up. The volume has a .tc extension as directed. For me, it appears not to be "either" but rather "both" still.
