Block-level sync for VeraCrypt not working post 83.4.152 update

[bph2019]

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 dismount my VC encrypted container, DB will index the file and compare the deltas at the block-level -- syncing the block-level changes.  However, after the 152 update, I've noticed that even with lots of changes in the VC container, after I dismount, DB detects no changes to the encrypted file.  I end up having a bunch of conflicts when trying to sync between machines via the "rename the file and rename it back" approach.

Could someone share resolution or your similar experiences if you're also using encrypted containers with DB?

Thanks,

BPH

[nei a.]

really? " account-specific information that may be necessary to troubleshoot"

it seems to me that dropbox has not or is not willing to understand the problem

there is nothing account specifc here, just install veracrypt, create a dummy container, set the flag not to update the file timestamp

and observe that it does not sync

[Olivier32]

Thank you @MSDDROP, your workaround works fine : 

Within Veracrypt -> Preferences -> Untick Preserve modification timestamp of conntainers.

Now each time I close a Mounted Volumn I can see it Sync up (changes only as only takes a second).

---

[Pups Ivan]

Hi all! I have 113.4.507 version and same problems. And nothing new so far?

[Jay]

Hi @Pups Ivan, have you tried the info provided here to see if this helps?

[Tom30]

The "workaround" is not an option. 

What's the current status on implementation?

I mean seriously this ticket is 2 years old!

[Tom30]

@Jay ?

[nei a.]

@dropbox, is now fixed or not? a simple yes or no  would help .....

[nei a.]

anyone home?

[Hannah]

Hey @nei a., thanks for the nudge here.

I've opened up a ticket for you so we can look into this further through our support channel. 

If anyone else is having trouble with this, please reach out to our support team and let me know your ticket numbers.

[nei a.]

thanks for this, but somehow I cannot access the ticket. but nevertheless I do not really need this ticket, all information is in this thread.
I need the question answered, which I asked above, i.e.  has this bug been fixed?

2 years ago I lost data due to this, and this is something that should never happen, the first few times dropbox stated it fixed "something", it still did not work based on my tests, others also confirmed this in this thread.
the latest answer we got from Dropbox regarding this  is from 2020  ... " I'm afraid we don't have a concrete ETA to share with you. "