Gary Marks

Happy to be of service!

Hi Paul, I wrote this as an example when I was auditioning scripting languages to replace the soon-to-be deprecated VBScript. PowerShell won out. Anyway, just copy the entire block of code and paste it into a text file with the .ps1 extension. Run it to make sure this dialog is acceptable, and then add your own code at the end to execute VeraCrypt from the command line using the $Password variable along with your other chosen options (quick link). Function GetPassword { $Form = New-Object System.Windows.Forms.Form...

I'm not aware of any means to coerce the VeraCrypt GUI into limiting the options that unfamiliar users sometimes find daunting. An alternative would be to create a script that automatically includes all of the desired mounting options except the password, collecting the password instead via a single item dialog to the user, and then passing all of these items to VeraCrypt in a command line. That avoids including the cleartext password in the script, and you won't have to instruct users in VeraCrypt...

There was a discussion of this very topic back in 2020, showing that both Elcomsoft tools and Tails "identify" a VeraCrypt volume by finding apparently random data where VeraCrypt might have placed it. Sometimes it is a false positive, as Keyszer Soze demonstrates in the last post of that thread. Read it here in case you need to mount a defense denying the charges when you are being beaten with a rubber hose to reveal the VeraCrypt password. If you test it yourself with different results, be sure...

Your post is a little unclear to me, but what I understand you to be saying is that you installed VeraCrypt on your E: drive (not your system drive) and then you encrypted the E: drive, which doesn't automatically mount at boot time. Now you can't run VeraCrypt properly because the E: drive isn't yet mounted and the program files are unreachable. If I haven't totally misunderstood your dilemma, try using the portable version of VeraCrypt to mount your encrypted drive using the E: drive letter. As...

As your own successful results with Enigma2Illusion's direct links suggest, downloading from the source instead of an intermediary like Launchpad.net is often a go-to fix. I asked my dear friend Google, "What are some of the problems encountered when downloading files from launchpad.net?" (edited to use larger image)

As your own successful results with Enigma2Illusion's direct links suggest, downloading from the source instead of an intermediary like Launchpad.net is often a go-to fix. I asked my dear friend Google, "What are some of the problems encountered when downloading files from launchpad.net?"

There's an old saying that the squeaky wheel gets the grease. Here's an example of some loud squeaking with high levels of readership... https://www.neowin.net/news/microsoft-pulls-developer-accounts-of-wireguard-and-veracrypt/ It's great to see the support that the developer of this program receives!