Preview 1.26.12 Released

[Enigma2Illusion]

Version 1.26 has removed support for TrueCrypt Mode, the RIPEMD-160 hash algorithm and the GOST89 encryption algorithm. See documentation below for remediation procedures.

Conversion Guide for VeraCrypt 1.26 and Later

---

https://sourceforge.net/projects/veracrypt/files/VeraCrypt%20Nightly%20Builds/

Changes between 1.26.7 and1.26.12 (6 July 2024) :

• All OSes:
  • Update translations and documentation
  • Implement language selection settings in non-Windows versions.
  • Make codebase compatible with wxWidgets 3.3 in non-Windows versions.
• Windows:
  • Better fix for Secure Desktop issues under Windows 11 22H2
  • VeraCrypt Expander: Fix expansion of volumes on disks with a sector size different from 512 (by skl0n6)
  • Fix writing wrong EFI System Encryption Advanced Options to registry
  • Don't close Setup when exiting VeraCrypt process through system tray Exit menu
  • Fix failure to format some disks (e.g. VHDX) caused by virtual partition offset not 4K aligned
  • Fallback to absolute positioning when accessing disks if relative positioning fails
  • Update zlib to version 1.3.1
• Linux:
  • Focus PIM field when selected (GH #1239)
  • Fix generic installation script on Konsole in Wayland (GH #1244)
  • Added the ability to build using wolfCrypt as the cryptographic backend. Disabled by default. (Contributed by wolfSSL, GH PR #1227)
  • Allows GUI to launch in a Wayland-only environment (GH #1264)
  • CLI: Don't initially re-ask PIM if it was already specified (GH #1288)
  • CLI: Fix incorrect max hidden volume size for file containers (GH #1338))
  • Enhance ASLR security of generic installer binaries by adding linked flag for old GCC version (reported by @morton-f on Sourceforge).
• macOS:
  • Fix corrupted disk icon in main UI (GH #1218)
  • Fix near zero width PIM input box and simplify wxTextValidator logic (GH #1274)
  • Use correct Disk Utility location when "check filesystem" is ran (GH #1273)
  • Add support for FUSE-T as an alternative to MacFUSE (GH #1055)
• FreeBSD:
  • Fix privilege escalation prompts not showing up (GH #1349)
  • Support automatic detection and mounting of ext2/3/4, exFAT, NTFS filesystems (GH #1350)
  • Use correct Disk Utility location when "check filesystem" is ran (GH #1273)

[Sr Lopez]

Thanks for all your Hard Work!

[风之暇想]

Refs still formatted incorrectly
https://sourceforge.net/p/veracrypt/discussion/general/thread/6d0c0dfdc8/#8274

[Michael Cowell]

I'm kinda new to this type of software but I have successfully created a VeraCrypt partition using 1.26.7 and I just installed the new version 1.26.12. Do new versions need to recreate the partition to apply any new features to the encrypted partition or .hc files? It will take a long time to copy everything out, remove the partition and rebuild it using 1.26.12 and copy everything back in.

[Enigma2Illusion]

In short, no.

For future reference, the release notes will tell you if you need to recreate the encryption or hash which is rarely needed for the software update/upgrade.

Therefore, it is advisable to review the release notes before performing the update/upgrade.

For users upgrading from pre-1.26.x version, see the following documentation below.

Conversion Guide for VeraCrypt 1.26 and Later

[John Navarro]

Running your beta 12 release on Ubuntu 24.04 Desktop. Seems to work really well. Did discover one oddity - when I click the dismount button on a usb connected hard drive I get the following message:

Directory not empty:
/media/veracrypt3

VeraCrypt::FilesystemPath::Delete:26

If I click the dismount button again it dismounts as expected without the message. I have 3 other similar drives and they produce the same message, but not all the time.

I am basically mounting a NTFS encrypted drive, copying a bunch of files, then clicking dismount. There is no disk activity when I attempt to dismount.

Thank you

[Mounir IDRASSI]

@John Navarro: The Linux error code 26 corresponds to EBUSY (Device or resource busy). This indicates that the volume cannot be dismounted because there are still pending I/O operations. This situation typically occurs when the I/O buffer hasn’t been flushed to disk quickly enough before you attempt to dismount the volume.

It's important to note that VeraCrypt doesn't control the speed at which I/O buffers are flushed; this is managed by the system based on various factors.