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?

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?

Project Update

Enigma2Illusion — Sun, 19 Apr 2026 20:42:07 -0000

I think you are confusing the 1.26.27 with the future release of 1.27.x version which will be released after the 1.26.28 version.

VeraCrypt 1.26.27 release:

https://sourceforge.net/p/veracrypt/discussion/general/thread/bbfb10089a/#350a

VeraCrypt 1.26.28 release:

https://sourceforge.net/p/veracrypt/discussion/general/thread/9620d7a4b3/?page=1&limit=25#e4ed/9e8d

I have decided to prepare a VeraCrypt 1.26.28 maintenance release whose purpose will be to provide newly Microsoft-signed EFI bootloader components for current 1.26.x users, so people do not have to wait for VeraCrypt 1.27.

.
Planned changes for future 1.27.x :

https://sourceforge.net/p/veracrypt/discussion/general/thread/bbfb10089a/#6401

Project Update

Marcos Morar — Sun, 19 Apr 2026 19:20:54 -0000

Does releasing the 1.26.28 emergency release mean that the stable 1.27 version might be released after June 27, 2026? It's been in beta for a long time, is the stable version really that far away?"

Project Update

Marconius — Sun, 19 Apr 2026 15:39:19 -0000

Great, thanks for the explanation!

Project Update

Mounir IDRASSI — Sun, 19 Apr 2026 15:20:13 -0000

@marconius:
No, VeraCrypt 1.27 will not be required specifically because of this Secure Boot certificate transition.

I posted a detailed technical explanation on GitHub here:
https://github.com/veracrypt/VeraCrypt/issues/1655#issuecomment-4276186649

The short version is that, after investigating Microsoft's guidance and how other Secure Boot projects are handling this, I have decided to prepare a VeraCrypt 1.26.28 maintenance release whose purpose will be to provide newly Microsoft-signed EFI bootloader components for current 1.26.x users, so people do not have to wait for VeraCrypt 1.27.

The old VeraCrypt bootloader is not expected to suddenly stop working on the expiration date just because the Microsoft 2011 UEFI CA expires. Microsoft’s guidance says that already signed 2011 UEFI binaries remain trusted on devices that still have the 2011 CA in their Secure Boot database. So, if a system already boots VeraCrypt today and its firmware still trusts Microsoft Corporation UEFI CA 2011, it should not become unbootable solely because that CA reaches its expiration date.

That said, users with system encryption on UEFI systems with Secure Boot enabled should install the upcoming 1.26.28 maintenance release once it is available. This is strongly recommended because the ecosystem is moving to the new 2023 Microsoft UEFI CA, and future firmware/Windows/Secure Boot configurations may require bootloaders signed with the new CA. It is also important for rescue disk media.

So the practical answer is:

non-system encrypted volumes and containers are not affected by this bootloader signing issue
system encryption on legacy BIOS systems is not affected by UEFI Secure Boot signing
system encryption on UEFI systems with Secure Boot enabled is the case concerned here
users in that situation should update to the upcoming 1.26.28 emergency release when it is published

For update notifications, @enigma2illusion shared the answer.

Project Update

Enigma2Illusion — Sat, 18 Apr 2026 22:57:06 -0000

Please excuse my ignorance, but does the new signed bootloader and all that mean that 1.27 will be a required update?

.
Required update for those users that are using VeraCrypt system encryption.

https://sourceforge.net/p/veracrypt/discussion/general/thread/9620d7a4b3/#3470/56c8/81e5

What happens if someone with all their system drives encrypted doesn't update to 1.27 before the old bootloader expires?

.
I don't know. @idrassi will have to provide answer.

If the update is required, does VeraCrypt do this automatically; or is there some way to alert users that there is an important update? I tried looking, but I couldn't find an automatic update option, no mailing list, etc. so not sure how people who don't follow tech news or these forums would know to update.

.
There are reasons that the update/notification of software update is not built into the VeraCrypt application at the link below.

https://sourceforge.net/p/veracrypt/discussion/general/thread/0cc5a5acc6/?page=3&limit=25#9fcf/3217

Notifications Solutions

Gary Marks solution is to get notifications from SourceForge whenever new software files are available.

https://sourceforge.net/p/veracrypt/discussion/general/thread/0cc5a5acc6/?page=3&limit=25#9fcf/5393

Heribert Slama uses RSS feeds whenever new software files are available.

https://sourceforge.net/p/veracrypt/discussion/general/thread/0cc5a5acc6/?page=4&limit=25#8510

Project Update

Marconius — Sat, 18 Apr 2026 22:15:41 -0000

Please excuse my ignorance, but does the new signed bootloader and all that mean that 1.27 will be a required update? What happens if someone with all their system drives encrypted doesn't update to 1.27 before the old bootloader expires?

If the update is required, does VeraCrypt do this automatically; or is there some way alert users that there is an important update? I tried looking but I couldn't find an automatic update option, no mailing list, etc. so not sure how people who don't follow tech news or these forums would know to update.

Recent posts to Project Update

Project Update

Project Update

Project Update

Project Update

Project Update

Project Update

Project Update

Project Update

Project Update

Project Update