[Bug?] Container file timestamp is not updated when opening via command line

[Thomas]

Hi,

Within the preferences I unchecked the setting "Preserve modification timestamp of file containers" to ensure that the changed date (timestamp) of my container is updated.

If I use the UI to manually open/close the container the date of the container is correctly updated.

But I am normally using a small batch script to open and close the container. If I now use this batch script the date is not updated.

Script for opening the container file:

"C:\Program Files\VeraCrypt\VeraCrypt.exe" /v data_container.tc /l s /a /q /m rm

Script to close the container file:

"C:\Program Files\VeraCrypt\VeraCrypt.exe" /q /d

Is this a bug or is my script incorrect?

Why is it important for me to change the date of the container?
-> I am using Nextcloud and the client does only sync changed files back to the server

This is a real issue for me because it has massive impact on my backup solution. Any hint is welcome.

Thanks and regards
Thomas

[Adrian Kentleton]

If you want to use the command line to mount a volume using the preferences as set in the GUI Settings > Preferences, then specify '/q preferences'.

If you do not specify '/q preferences', then you will have to explicitly specify every parameter you wish to use to mount the volume; and in the case of timestamps, you need to use '/m ts' to update timestamps.

Note that '/a' is redundant (since it's implicit) if you have specified '/q' and '/v'.

[Thomas]

Hi Adrian,

perfect, thanks a lot for this tip. This is exactly what I was looking for. Changing the parameters solved my issue.

New command:

"C:\Program Files\VeraCrypt\VeraCrypt.exe" /v data_container /l s /m ts /q /m rm