We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.

Forum Discussion

bph2019's avatar
bph2019
Helpful | Level 6
6 years ago

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...
Desktop
Sync
Third Party Integrations
  • Walter's avatar
    Walter
    2 years ago

    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 .

nei a.'s avatar
nei a.
Experienced | Level 11

I have the same issue, but I think it started with version 82.
The ugly "workaround" I use, is to copy the "file" daily to "file_yyyymmdd", this syncs, and the immediately delete the file. While the orginal file is not synced, doing this I have a daily history, I can get if needed.

I think drobox either wants to save resources or has introduced a bug, it seems that a file is no longer checked on close alone, but only on close and the file date has changed. (I use the mode to not change the timestampo of the file)

 

  • nei a.'s avatar
    nei a.
    Experienced | Level 11
    6 years ago

    I do not think so, windows 10 with ntfs here, that should work or do I miss something?

    And it used to work until 2019-10-04 (last sync in my history), so something else must have changed. 

    • bph2019's avatar
      bph2019
      Helpful | Level 6
      6 years ago

      Yes, my experience is the same with nei a., as I was able to utilize block-level sync functionality with VeraCrypt container (*.hc) and TrueCrypt (*.tc) before the 152 update.  The last time that my container showed it was modified and synced before the manual workarounds (re-uploading the entire container) was October 13th.

      In terms of next steps, what would you all advise?  Is there an approach to submit this bug and escalate the issue to DB's support?

      Thanks in advance, all.

About Create, upload, and share

Find help to solve issues with creating, uploading, and sharing files and folders in Dropbox. Get support and advice from the Dropbox Community.

Need more support

If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X or Facebook.

For more info on available support options for your Dropbox plan, see this article.

If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!