Announcement: 1.24 Update 8 Released 11/28/2020

[Enigma2Illusion]

1.24 Update 8 for macOS released November 28, 2020

https://sourceforge.net/projects/veracrypt/files/VeraCrypt%201.24-Update8/

• MacOSX:
  • Fix compatibility issues with macOS Big Sur, especially on Apple Silicon M1 with macFUSE 4.0.x..

---

1.24 Update 7 released August 7, 2020

https://sourceforge.net/projects/veracrypt/files/VeraCrypt%201.24-Update7/

• All OSes:
  • Don't allow Hidden volume to have the same password, PIM and keyfiles as Outer volume.
  • Fix random crash in 32-bit builds when using Streebog.
  • Enable FIPS mode in JitterEntropy random generator.
  • Update Beginner's Tutorial in documentation to use "MyVolume.hc" instead of "My Volume" for file container name in order to avoid confusion about nature of file nature.
  • Minor code cleanup.
• Windows:
  • Fix wrong results in benchmark of encryption algorithms when RAM encryption is enabled.
  • Fix issue when RAM encryption used, AES selected and AES-NI not supported by CPU that caused the free space of newly created volumes not filled with random data even if "quick format" is not selected.
  • Fix UI for blocking TRIM in system encryption not working in MBR boot mode.
  • Support password drag-n-drop from external applications (e.g. KeePass) to password UI fields which is more secure than using clipboard.
  • Implements compatibility with Windows 10 Modern Standby and Windows 8.1 Connected Standby power model. This makes detection of entring power saving mode more reliable.
  • Avoid displaying waiting dialog when /silent specified for "VeraCrypt Format" during creating of file container using /create switch and a filesystem other than FAT.
  • Use native Windows format program to perform formatting of volume since it is more reliable and only fallback to FormatEx function from fmifs.dll in case of issue.
  • Don't use API for Processor Groups support if there is only 1 CPU group in the system. This can fix slowness issue observed on some PCs with AMD CPUs.
  • Don't allow to encrypt the system drive if it is already encrypted by BitLocker.
  • Implement detection of Hibernate and Fast Startup and disable them if RAM encryption is activated.
  • Warn about Fast Startup if it is enabled during VeraCrypt installation/upgrade, when starting system encryption or when creating a volume, and propose to disable it.
  • Add UI options to control the behavior of automatic bootloader fixing when System Encryption used.
  • Don't allow a directory path to be entered for the file container to be created in Format wizard.
  • Don't try to use fix for CVE-2019-19501 if Windows Shell has been modified or is not running since there is no reliable way to fix it in such non standard configuation.
  • MBR bootloader: fix incorrect compressed data size passed to decompressor in boot sector.
  • Add warning message when typed password reaches maximum length during the system encryption wizard.
  • Fix wrong error message when UTF-8 encoding of entered password exceeds the maximum supported length.
  • Update libzip to latest version 1.7.3.
  • Update translations.
• Linux/MacOSX:
  • Force reading of at least 32 bytes from /dev/random before allowing it to fail gracefully.
  • Allow choosing a filesystem other than FAT for Outer volume but display warning about risks of such choice. Implement an estimation of maximum possible size of hidden volume in this case.
  • Erase sensitive memory explicitly instead of relying on the compiler not optimizing calls to method Memory::Erase.
  • Add support for Btrfs filesystem when creating volumes (Linux Only).
  • Update wxWidgets for static builds to version 3.0.5.

---

1.24 Update 6 released March 10, 2020

https://sourceforge.net/projects/veracrypt/files/VeraCrypt%201.24-Update6/

• Windows:
  • Fix PIM label text truncation in password dialog.
  • Fix wrong language used in installer if user selects a language other than English and then selects English before clicking OK on language selection dialog.

---

1.24 Update 5 released March 9, 2020

https://sourceforge.net/projects/veracrypt/files/VeraCrypt%201.24-Update5/

• Windows:
  • Optimize performance for CPUs that have more than 64 logical processors (contributed by Sachin Keswani from AMD).
  • Support specifying keyfiles (both in tokens and in filesystem) when creating file containers using command line (switches /keyfile, /tokenlib and /tokenpin supported in VeraCrypt Format).
  • Fix leak of keyfiles path and name after VeraCrypt process exits.
  • Add CLI switch /secureDesktop to VeraCrypt Format.
  • Update libzip to version 1.6.1.
  • Minor UI fixes.

---

1.24 Update 4 released January 23, 2020

https://sourceforge.net/projects/veracrypt/files/VeraCrypt%201.24-Update4/

• Windows:
  • Fix regression in Expander and Format when RAM encryption is enable that was causing volume headers to be corrupted.
  • Fix failure of Screen Readers (Accessibility support) to read UI by disabling newly introduced memory protection by default and adding a CLI switch (/protectMemory) to enable it when needed.
  • Fix side effects related to the fix for CVE-2019-19501 which caused links in UI not to open.
  • Add switch /signalExit to support notifying WAITFOR Windows command when VeraCrypt.exe exits if /q was specified in CLI (cf documentation for usage).
  • Don't display mount/dismount examples in help dialog for command line in Format and Expander.
  • Documentation and translation updates.
• Linux:
  • Fix regression that limited the size available for hidden volumes created on disk or partition.
• MacOSX:
  • Fix regression that limited the size available for hidden volumes created on disk or partition.

---

1.24 Update 3 released December 21, 2019

https://sourceforge.net/projects/veracrypt/files/VeraCrypt%201.24-Update3/

• Linux:
  • Fix console-only build to remove dependency on GTK that is not wanted on headless servers.

---

1.24 Update 2 released December 12, 2019

https://sourceforge.net/projects/veracrypt/files/VeraCrypt%201.24-Update2/

• All OSes:
  • clear AES key from stack memory when using non-optimized implementation. Doesn't apply to VeraCrypt official build (Reported and fixed by Hanno Böck)
  • Update Jitterentropy RNG Library to version 2.2.0
  • Start following IEEE 1541 agreed naming of bytes (KiB, MiB, GiB, TiB, PiB).
  • Various documentation enhancements.
• Windows:
  • Fix possible local privilege escalation vulnerability during execution of VeraCrypt Expander (CVE-2019-19501)
  • MBR bootloader:
    • workaround for SSD disks that don't allow write operations in BIOS mode with buffers less than 4096 bytes.
    • Don't restore MBR to VeraCrypt value if it is coming from a loader different from us or different from Microsoft one.
  • EFI bootloader:
    • Fix "ActionFailed" not working and add "ActionCancelled" to customize handling of user hitting ESC on password prompt
    • Fix F5 showing previous password after failed authentication attempt. Ensure that even wrong password value are cleared from memory.
  • Fix multi-OS boot compatibility by only setting VeraCrypt as first bootloader of the system if the current first bootloader is Windows one.
  • Add new registry flags for SystemFavoritesService to control updating of EFI BIOS boot menu on shutdown.
  • Allow system encrypted drive to be mounted in WindowsPE even if changing keyboard layout fails (reported and fixed by Sven Strickroth)
  • Enhancements to the mechanism preserving file timestamps, especially for keyfiles.
  • Fix RDRAND instruction not detected on AMD CPUs.
  • Detect cases where RDRAND is flawed (e.g. AMD Ryzen) to avoid using it if enabled by user.
  • Don't write extra 0x00 byte at the end of DcsProp file when modifying it through UI
  • Reduce memory usage of IOCTL_DISK_VERIFY handler used in disk verification by Windows.
  • Add switch /FastCreateFile for VeraCrypt Format.exe to speedup creation of large file container if quick format is selected.
  • Fix the checkbox for skipping verification of Rescue Disk not reflecting the value of /noisocheck switch specified in VeraCrypt Format command line.
  • check "TrueCrypt Mode" in password dialog when mounting a file container with .tc extension
  • Update XML languages files.
• Linux:
  • Fix regression causing admin password to be requested too many times in some cases
  • Fix off by one buffer overflow in function Process::Execute (Reported and fixed by Hanno Böck)
  • Make sure password gets deleted in case of internal error when mounting volume (Reported and fixed by Hanno Böck)
  • Fix passwords using Unicode characters not recognized in text mode.
  • Fix failure to run VeraCrypt binary built for console mode on headless machines.
  • Add switch to force the use of legacy maximum password length (64 UTF8 bytes)
  • Add CLI switch (--use-dummy-sudo-password) to force use of old sudo behavior of sending a dummy password
  • During uninstall, output error message to STDERR instead of STDOUT for better compatibility with package managers.
  • Make sector size mismatch error when mounting disks more verbose.
  • Speedup SHA256 in 64-bit mode by using assembly code.
• MacOSX:
  • Add switch to force the use of legacy maximum password length (64 UTF8 bytes)
  • Fix off by one buffer overflow in function Process::Execute (Reported and fixed by Hanno Böck)
  • Fix passwords using Unicode characters not recognized in text mode.
  • Make sector size mismatch error when mounting disks more verbose.
  • Speedup SHA256 in 64-bit mode by using assembly code.
  • Link against latest wxWidgets version 3.1.3

[Unit 193]

Howdy,

So it seems the last two updates didn't have release tarballs (and associated detacted signatures) on either here or launchpad.net. Is this the plan moving forward or were they (hopefully) mistakenly missed? Currently I watch for [Vv]era[Cc]rypt_([\d\w\._-]+)_[Ss]ource\.tar\.(?:gz|bz2|xz) but I could repack a zipfile, it just wouldn't be as easily verifiable by the detached signature.

~Unit 193

[Mounir IDRASSI]

@unit193: the last two updates affect only Windows and so other operating systems are not affected. That's why I didn't publish source code tarballs for these two versions.

[Unit 193]

Ah! Thank you, that makes sense. I see my error, I scolled too far down on https://sourceforge.net/projects/veracrypt/files/VeraCrypt%201.24-Update5/ it seems. Thanks for the quick reply.

~Unit 193

[Enigma2Illusion]

@idrassi

The MacOSX release notes show using latest wxWidgets version 3.1.3 however the software history shows reverting back to 3.1.2 due to unexplained crash.

You may need to update the release notes to remove the 3.1.3 for MacOSX.

Many thanks to you Mounir for your very hard work on VeraCrypt!

EDIT: Also the Readme file.

[Dave]

Speedup SHA256 in 64-bit mode by using assembly code

Does this also apply to Windows?

[Enigma2Illusion]

According to the change commit comment, Windows already has the improvements.

https://sourceforge.net/p/veracrypt/code/ci/54b97f848bc2bb5b24e42bb0c4144e8c72376b47/

[Dave]

Thanks for replying. Good to see more assembly code in VeraCrypt to reduce the performance overhead of encryption.

[karnin]

1.24Update2 is same as 1.24Hotfix2?
New naming? Is it a release version?

[Enigma2Illusion]

The 1.24 Hotfix 2 never existed. Are you meaning 1.24 Update2 RC?

If yes, look at the software history by clicking on Source Code, then History.

There appear to be some changes since 1.24 Update2 RC (release candidate, aka Beta before release).

1.24 Update 2 is a production release.

[karnin]

1.24 Update 2 is a production release.

Thanks for this clarification.

[DDD]

With Update2, on my older win 7 machine, so the MBR version of Veracrypt 1.24 update 2, it does not shut off my machine after 3 minutes or however long, and also it still takes as long after entering my password to verify, as in 1.23. One thing I'm pleased about is that it still says the veracrypt # with the solid line underneat, and the F5 and all that, but it doesn't say that in the EFI version. I wish it would. Also, I don't know where the option is to change the poweroff timeout value, or is it just hardcoded as being 3 minutes? I would have liked an option to keep the MBR version of Veracrypt, with all those messages like pressing F5 and all that, as an option to keep in the EFI version. Also, while using Update 2, I tried upgrading Win 7 to Win10 v 1909, and I got error 0xC1900101 - 0x20017 and the message "The installation failed in the SAFE_OS phase with an error during boot operation", so I was hoping that I wouldn't have to decrypt my drive.

[Nick]

Two things are broke for me with this new 1.24 update 2 version under Windows 7 spk1.

• I can't double click to open drives from the mount window now
• And none of the links in VC 's help menu work, inclucing the homepage link on the front interface.

I've never had an issue with the program in the 7 years I've been using TC, and VC.
Q Was the double click option removed for security reasons, but the menues remain? Not even the right click to open my drive works, even though the drive is mounting ok and I 'can' open the drive from windows explorer. I just can't do it from the mount window anymore.

EDIT
I've downgraded from 1.24 update 2 back to 1.24 hotfix 1 and everyting is working again

[Philip Smith]

I just installed 1.24 update 3
All the help sections links work, have same as you Win 7 sp1.

(( NOTE the downloaded file still says 1.24 update 2 size 34.5MB it is dated December 16 2019 )) I think this needs to be corrected to update 3.

The download link says VeraCrypt 1.24-Update3 BUT the download box in green still has wrong info it still says 1.24 update 2 - 36.2MB.
https://sourceforge.net/projects/veracrypt/files/VeraCrypt%201.24-Update3/

[Nick]

Interesting.
I got mine from the main download site by the way.
https://www.veracrypt.fr/en/Downloads.html

So you're thinking update 2 is really version 3 (at source forge's download directory? They just forgot to rename the files, and they never uploaded verson 3 to the veracrypt.fr link I posted above. So I'm really running version 2.
On a side note: Update 2 might have been updated (last minute) to ver 3 because of these issues I mentioned.

[Philip Smith]

I think they updated the file but possible incorrectly named the downloaded file as 1.24 update 2

What is the date of your file? mine is December 16 2019

Also if you put the mouse on the file mine shows a version of 1.24.10.0
** when you click HELP -> ABOUT it still shows it as update 2 ** not 3

I also have 1.24 update 2 size 34.2MB Dated 14-12-2019 file version 1.24.9.0

I think someone forgot to put update 3 on the file left it as 2.
Check your and tell me what you have

[Nick]

The file I have looks to be the same:
----Details Tab----
File Version: 1.24.10.0
Product version: 1.24-Update2
Size: 34.5 MB (36,228,656 bytes)
Digital Sig tab: Monday, Dec 16, 2019 5:05:30 AM

Like I said, I ran the upgrade option with the previous 1.24 hotfix 1 over the top of this to down grade back to hotfix1. This 1.24-Update2, or Update 3 (as you mentioned it might be) has the issues I mentioned a few posts back.

[Philip Smith]

Does it downgrade the version?
I would suggest uninstalling completely then reinstalling Update3 that is what I do.
Also before doing that try a portable version of update 2 if available have not seen one for 3. Worth a try.

[Nick]

Trying the portable version first is a good idea.

It did seem to downgrade ok. I mean everytfhing seems to be working great as was the case for the last 7 years. I think because it was not a major update, downgrading just replaced the (few) files that were updated in these hotfixes. I'm sure the On-the-fly-driver is the same in most of these versions. To uninstall I would have to decrypt my entire OS drive first. I have to set time aside for that. But It seems to be working.

[Philip Smith]

Does it downgrade the version?
I would suggest uninstalling completely then reinstalling Update3 that is what I do.
Also before doing that try a portable version of update 2 if available have not seen one for 3. Worth a try.

UPDATED
Take it back re uninstalling if it was just a volume or encrypted partition okay, but with the C drive encrypted not worth the risk.

I think you can try the portable version to see if the help works and experiment with other problem
I can't double click to open drives from the mount window now

[Nick]

As mentioned above, yes it downgraded fine. It's showing the previous version in the about tab now.
I'm sure the installer just deleted the newer files and replaced them with the old. And there might not been that many files updated.
Keep in mind, if the (On-the-fly) driver has not changed between versions (That is the driver that decrypts and encrypts , then why would the drive need to be decrypted. These updates are for the 'application', not the encrypted file system I'm pretty sure.

[DDD]

So with my Windows 1903 system, trying to upgrade to 1909, when the computer booted, I entered my Veracrypt password, and then the Windows recovery screen popped up, then I selected "Continue to Windows on volume 3" and then it reboots, I enter the Veracrypt password again, and then it ends up reverting me back to my original system with an error 0xC1900101 - 0x20017 The installation failed in the SAFE_OS phase with an error during BOOT operation.

Also, on my Windows 7 system, when I select "yes" to review the release notes after upgrading to 1.24 Update 2, it opens Opera and tries to access it on the web, whereas on my Win 10 v1903 machine, it opens up a local copy of the changelog, which I much prefer. So is it a difference between the MBR/BIOS version on my Win7 machine vs the GPT/EFI version on my win 10 machine?

Also, on my windows 10 machine, no restore points were created when upgrading to 1.24 Update 2, but yet Revo Uninstaller made 2 within 2 hours of each other when uninstalling some programs, just 2 days prior. So, I don't think it's a low disk space issue. Windows 7 made the restore point successfully.

[Marian Kechlibar]

https://www.reddit.com/r/VeraCrypt/comments/ejk39a/windows_10_no_longer_booting_after_updating/

My colleague has exactly the same problem, only on Windows 7. After updating VeraCrypt. Any ideas?

[DDD]

On my system, only SHA-256 and RIPEMD-160 are showing as possible options for the hash values - are there supposed to be others like Whirlpool?

[xyzs101]

Hi, I'm experiencing a problem with the newest version of veracrypt. Let's start at the beginning:

• I had a working windows 10 1909 computer with veracrypt 1.24 hotfix 1 with a encrypted system disk using also secure boot with the keys loaded manually
• Last week the installation of the Microsoft patch KB4524244 (UEFI related) failed after reboting once. More attempts to install the patch failed even without reboot. By now the patch has been revoked by MS.
• Today I tried to update veracrypt to the current version 1.24 Update 4. After installing and rebooting I could enter my password, got the success message, but nothing more happened. Choosing the repair option, which gets active after some boot attempts, has the same effect: You get a message like "preparing to recover", but nothing more happens.
• I tried to boot using the loader from the rescue disk, but it also didn't work, so I'm currently decrypting the disk using the rescue disk (takes ages ...). Let's see if thatleads somewhere. If not, I have to set up windows anew and copy the data back from my backup.
• Any ideas or hints?