lurkios

You can drop a batch script/other in their startup folder using the command line: https://www.veracrypt.fr/en/Command%20Line%20Usage.html Encrypt the volume using a keyfile and either put it in a location accessible to all employees systems at start, or dsitribute it to each.

First off, thank you for Veracrypt. I've relied heavily on it since Truecrypt was murdered and it's served very well - the work of the devs is very much appreciated. I do seem to be having an issue since installing 1.22, which may be coincidental or may not be: Occasionally, maybe one time in 10, the bootloader for Veracrypt fails to recognize my USB keyboard. The keyboard functions okay outside of the bootloader (bios, raid firmware, etc.) and once Windows boots. The keyboard is powered/lit during...

Right, that's a better way of putting it.

First off, thank you for Veracrypt. I've relied heavily on it since Truecrypt was murdered and it's served very well - the work of the devs is very much appreciated. I do seem to be having an issue since installing 1.22, which may be coincidental or may not be: Occasionally, maybe one time in 10, the bootloader for Truecrypt fails to recognize my USB keyboard. The keyboard functions okay outside of the bootloader (bios, raid firmware, etc.) and once Windows boots. The keyboard is powered/lit during...

That'll work - much appreciated.

In a case where a KeePass database's master key is a Windows user account is there a way to have KeePass automatically login to that database when the user logs in? I have it starting with Windows, but not logging in automatically. (System's already encrypted, so no concern there.)

Despite the oddly strong objections of a single party, the verification continues to fail.

For any wondering, the signature continues to show invalid. Additionally, I see project leaders have replied to several posts both before and after this - but no word here.