Ubuntu 26.04 package

Mounir IDRASSI — Sun, 26 Apr 2026 03:20:37 -0000

Thank you for the report.
I have just built Ubuntu 26.04 packages for version 1.26.24 and they are now available on the download page and also here on Sourceforge

Ubuntu 26.04 package

Jack Omen — Sat, 25 Apr 2026 17:07:15 -0000

Hi, I noticed last Ubuntu package is 25.04, though Ubuntu 26.04 is out now. Could you please make the package for the latest release available in the download section?
Many thanks

VeraCrypt 1.26.24 GUI won't close after auto dismount

Mounir IDRASSI — Sat, 25 Apr 2026 06:35:29 -0000

There was no behavior change in VeraCrypt 1.26.24 related to this. The option "VeraCrypt Background Task -> Exit when there are no mounted volumes" applies only to the background task, i.e. after the main VeraCrypt window has been closed/hidden to the tray.

If the main VeraCrypt window is left open, auto-unmount will unmount the volume, but it will not automatically close the visible GUI.

What you are describing is a new feature: making the whole VeraCrypt process exit after auto-unmount if no volumes remain, with no UI and no system tray icon. This is new behavior and it would require a new explicit option.

For example, we could add an option such as "Close VeraCrypt window after auto-unmount if no volumes remain". If this is combined with "VeraCrypt Background Task -> Exit when there are no mounted volumes", then the whole VeraCrypt process would terminate after auto-unmount when no volumes remain.

Concerning the path of the last selected container file, it is indeed not cleared automatically after auto-unmount, but this is also not part of the current auto-unmount functionality. There is already the "Never save history" setting, which helps, but we could also consider adding an option to clear the volume field after auto-unmount.

VeraCrypt tries to be as customizable as possible, but at the same time, adding more and more options makes usage more complex.

For your use case, I would advise always closing the UI after mounting is done, or preferably using the command line for mounting. Many power users on this forum use VeraCrypt from batch files or PowerShell scripts, since this avoids exposing information through the UI.

win 11 preview impossible for Veracrypt drive files

Bert Cuzeau — Thu, 23 Apr 2026 06:11:19 -0000

Miracle !
I guess the latest win 11 update solved it ! (:fingers-crossed:)
I don't have to restart Explorer any more : all the files from the encrypted drive have a normal ("not unsafe") status, pdfs are previewed etc ...
Hopinge next update won't regress.

Project Update

Thomas Navara — Thu, 23 Apr 2026 00:10:28 -0000

Are you able to share the reason so many accounts were disabled without appeal?

Remote reboot of encrypted system

Shane Taylor — Wed, 22 Apr 2026 19:47:45 -0000

I have a question I'm hoping someone can answer for me. I have a primary workstation at home that I access remotely while away from home. I have refrained from encrypting my system drive since I cannot enter the password when I am away to complete the Windows startup in the case of a power failure, or manual remote restart. My workstation has a second physical Ethernet port, which is designed for network/remote support use, but I'm not sure if it could be set up to access the machine in such a way as to facilitate entering the pre-boot Veracrypt password? Does anyone know, or does anyone who needs remote access (over possible reboots) utilize system encryption? Thank you in advance for any insight and/or advice.

1.26.27 BETA Released 2025/9/20

Enigma2Illusion — Tue, 21 Apr 2026 04:02:35 -0000

@idrassi

Issues with custom PIM values when changing KDF in:

Tools > Password Change or Keyfiles
Tools > Set Header Key Derivation Algorithm

VeraCrypt should reset the PIM to default value when a change to the KDF is made to prevent accidental large or small PIM values being used against the new KDF PIM value.

Using a test file container set to KDF => Whirlpool using custom PIM 490 and change it to Argon2 automatically uses PIM 490 for Argon2.

Users may not know PIM value of 490 using Argon2 is extremely too large.
Conversely using a custom PIM 8 for Argon2 is extremely too small for the other KDFs.

Attached are two examples of using 490 PIM with KDF Whirlpool to Argon2.

Proposed Solution

Whenever the new KDF is different from the current KDF, the PIM value should default to the correct PIM value of the new KDF with a warning message to the user that the PIM of new KDF has been set to default and to refer to the appropriate section of the manual for PIM default values.

https://veracrypt.jp/en/Header%20Key%20Derivation.html

Project Update

Enigma2Illusion — Mon, 20 Apr 2026 10:09:48 -0000

Thanks for explaining this!

Project Update

Enigma2Illusion — Sun, 19 Apr 2026 23:32:37 -0000

Regarding Argon2id:

1.26.27

Currently in the 1.26.27 Beta and the near future 1.26.27 production release, you can use Argon2id only on Windows OS 10/11 for non-system encryption drives/devices and file containers.

1.26.28 Windows Only Update

Windows UEFI systems with Secure Boot enabled updated to add the newer Microsoft UEFI CA 2023.

Windows users with system encryption must create a new VeraCrypt Rescue Disk after updating to 1.26.28 or later version.

Detailed technical explanation on GitHub here:

https://github.com/veracrypt/VeraCrypt/issues/1655#issuecomment-4276186649

1.27.x

Argon2id support for Windows UEFI system encryption.

Unsure which version Mounir was referencing for Argon2Id for Linux non-system drives/partitions and file containers

Mounir wrote:

Argon2id support for Linux non-system volumes/containers is much more feasible. This is planned and I will work on it.

Argon2id support for Linux non-system drives/partitions and file containers.

Project Update

Marcos Morar — Sun, 19 Apr 2026 22:04:09 -0000

Oh, my bad! I got confused between 1.26.27 and 1.27.

So, version 1.26.28 will add Argon2id support for containers and non-system drives, but only on Windows. If I understand correctly, it will also include Argon2id support for non-UEFI system drives. However, Argon2id support for UEFI system drives and for Linux will only be available in version 1.27. Is that right?

Recent posts to General Discussion

Ubuntu 26.04 package

Ubuntu 26.04 package

VeraCrypt 1.26.24 GUI won't close after auto dismount

win 11 preview impossible for Veracrypt drive files

Project Update

Remote reboot of encrypted system

1.26.27 BETA Released 2025/9/20

Project Update

Project Update

Project Update