Changes between 1.23 and 1.23-Hotfix-1 (20 September 2018) :
Windows:
Fix low severity vulnerability inherited from TrueCrypt that allowed reading 3 bytes of kernel stack memory (with a rare possibility of 25 additional bytes). Reported by Tim Harrison.
Disable quick format when creating file containers from command line. Add /quick switch to enable it in this case if needed.
Add /nosizecheck switch to disable checking container size against available free space during its creation. This enables to workaround a bug in Microsoft Distributed File System (DFS) that reports wrong free disk space.
Thanks, Mounir. Version 1.23 lets me encrypt my Dell laptop with UEFI/Secure Boot. Following the installation of VeraCrypt last month, the laptop has successfully undergone a few Windows 10 updates (without needing to decrypt), including this week's major release. Donation sent.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Mounir,
I have Asus X75VC with windows 10 1803 64 bits.
If you remember with old poweshell shell script applied i have secure boot failure
i have re tested system encryption with new 1.23 release , now all is right i can encrypt my system
what a good job !
your next challenge now is to solve performances problems
on my system with AES encryption and with AES NI instructions set active
boot time is increased by 2 minutes with long HDD Trashing (I/O queuing over 50)
startup time of big software eg libreoffice is 3 times more long.
Globaly system is less responsive.
Thank you for your implication in this project
Best regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is surely one of the best releases. System encryption on EFI configured HP computers work out of the box (I tried Win7Pro on HP 6200 Pro SSF and Win8.1 on HP dm-1 4300 so far). Before it either didn't work, or stopped working after some reboots, or only worked with awkward workarounds!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried 1.23 Hotfix 1 on two computers. One with Windows 1809 et the other with windows 1803.
I got two reproductible BSOD . One when I tried to start the encryption of the partition drive, and the other at the end of the decipher of the partition drive, which has been ciphered with another veracrypt version. It was something like "page fault in nonpaged area".
In both case, I downgraded to version 1.2.3 and the problem disappeared.
System drive encryption with 1.23 Hotfix 1 worked fine on a third W10 computer ...
Anyway, big THANK YOU for your amazing work!
Frédéric
Last edit: Elfeclair 2018-10-08
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for this report and your analysis, this is much appreciated.
A modification was done to fix a low severity vulnerability in the
driver and from your description it looks like the new code has some
anomaly that is not obvious to see for now. I will try to reproduce on
my side to find more clues.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Another forum user has reported the same issue with 1.23 Hotfix 1 giving error "page fault in nonpaged area" BSOD in the thread below that may aid you in finding the root cause of the problem.
After further investigation, there was indeed a bug introduced in 1.23-Hotfix-1 which was causing a BSOD in many cases.
I have fixed this issue and I have uploaded 1.23-Hotfix-2 to nightly builds folder.
This is was a simple bug that should have been detected before publishing but surprisingly it didn't occur on the test systems I was using. Sorry for the inconvenience.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Since Hotfix-2 applies only to Windows, I was reluctant to perform a
full build on all other operating systems for a 1.23-Hotfix-2 release
and so I didn't update the official download page with 1.23-Hotfix-2 links.
Now I understand the confusion and I have come up with simple solution:
I have updated the official download page
(https://www.veracrypt.fr/en/Downloads.html) with links to 1.23-Hotfix-2
specific to Windows and I indicate that there are two stable versions:
1.23-Hotfix-2 for Windows and 1.23 for the other operating systems.
This is not perfect but at least things are clear.
I have also added the SHA256 checksum as requested.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2018-11-26
@Mounir:
Again, thank You for the continuous contribution to the project. If I may, I am really, really desperate for the following feautures I had asked long before. Is there any chance they would exist in 1.24, especially the first one, Mounir? Thank You so much for Your answer and any effort to make these features real.
I just created a separate folder for 1.23-Hotfix-2 ans I uploaded the same files as the ones that were present in the Nightly Builds folder.
I did this because I want Nightly Builds to contains latest 1.24-Beta builds and since 1.23-Hotfix-2 is stable, it deserves to have its own release folder.
The most important this is the the 1.23-Hotfix-2 files are unchanged and this can be verified.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1.23 Hotfix 2 released October 8, 2018
https://sourceforge.net/projects/veracrypt/files/VeraCrypt%201.23-Hotfix-2/
Changes between 1.23-Hotfix-1 and 1.23-Hotfix-2 (8 October 2018) :
.
1.23 Hotfix 1 released September 20, 2018
https://sourceforge.net/projects/veracrypt/files/VeraCrypt%201.23-Hotfix-2/
Changes between 1.23 and 1.23-Hotfix-1 (20 September 2018) :
.
1.23 released September 12, 2018
https://sourceforge.net/projects/veracrypt/files/VeraCrypt%201.23/
Changes between 1.22 and 1.23 (12 September 2018) :
Last edit: Mounir IDRASSI 2018-12-19
Thanks, Mounir. Version 1.23 lets me encrypt my Dell laptop with UEFI/Secure Boot. Following the installation of VeraCrypt last month, the laptop has successfully undergone a few Windows 10 updates (without needing to decrypt), including this week's major release. Donation sent.
At the download page the only option to verify the file is the PGP signature.
PGP is too complicated for most of the users, and the digital signature (embedded on Windows version) is easy to fake.
Can you publish at the same page the MD5, SHA512 or something similar to check the file?
In the same download page, there is in the bottom links to SHA26 and SHA512 checksums files whch contains the hash value of all published files.
Hello Mounir,
I have Asus X75VC with windows 10 1803 64 bits.
If you remember with old poweshell shell script applied i have secure boot failure
i have re tested system encryption with new 1.23 release , now all is right i can encrypt my system
what a good job !
your next challenge now is to solve performances problems
on my system with AES encryption and with AES NI instructions set active
boot time is increased by 2 minutes with long HDD Trashing (I/O queuing over 50)
startup time of big software eg libreoffice is 3 times more long.
Globaly system is less responsive.
Thank you for your implication in this project
Best regards
Thank you so much! I just sent you my third donation.
Last edit: Sam 2018-09-17
This is surely one of the best releases. System encryption on EFI configured HP computers work out of the box (I tried Win7Pro on HP 6200 Pro SSF and Win8.1 on HP dm-1 4300 so far). Before it either didn't work, or stopped working after some reboots, or only worked with awkward workarounds!
1.23 Hotfix 1 released Septemeber 20, 2018.
https://sourceforge.net/p/veracrypt/discussion/general/thread/6ab45d49/#cfaa
Hello,
I tried 1.23 Hotfix 1 on two computers. One with Windows 1809 et the other with windows 1803.
I got two reproductible BSOD . One when I tried to start the encryption of the partition drive, and the other at the end of the decipher of the partition drive, which has been ciphered with another veracrypt version. It was something like "page fault in nonpaged area".
In both case, I downgraded to version 1.2.3 and the problem disappeared.
System drive encryption with 1.23 Hotfix 1 worked fine on a third W10 computer ...
Anyway, big THANK YOU for your amazing work!
Frédéric
Last edit: Elfeclair 2018-10-08
Hi Frédéric,
Thank you for this report and your analysis, this is much appreciated.
A modification was done to fix a low severity vulnerability in the
driver and from your description it looks like the new code has some
anomaly that is not obvious to see for now. I will try to reproduce on
my side to find more clues.
@Mounir,
Another forum user has reported the same issue with 1.23 Hotfix 1 giving error "page fault in nonpaged area" BSOD in the thread below that may aid you in finding the root cause of the problem.
https://sourceforge.net/p/veracrypt/discussion/technical/thread/72dc3c65fd/
"One when I tried to start the encryption of the partition drive"
also BSOD for Windows 8 64bit UEFI
currently after reinstalling windows encrypt partition drive succeed
After further investigation, there was indeed a bug introduced in 1.23-Hotfix-1 which was causing a BSOD in many cases.
I have fixed this issue and I have uploaded 1.23-Hotfix-2 to nightly builds folder.
This is was a simple bug that should have been detected before publishing but surprisingly it didn't occur on the test systems I was using. Sorry for the inconvenience.
love you <3 thank you !!
Thank you! It's fantastic! I encrypted my intel Celeron 3450 and Win 10. I'm paying for this miracle!
Last edit: Nik 2018-10-20
Nice Work! Its stable now.
Thanks for all the hard work on this. Is an ARM build in the works, due out soon? Thanks again.
I am also interested in an ARM version for my raspberry pi ...
Hello
would it be possible to make the sha256 hash of the "1.23 Hotfix 2" version available here:
https://sourceforge.net/projects/veracrypt/files/VeraCrypt%20Nightly%20Builds/
or update files here:
https://sourceforge.net/projects/veracrypt/files/VeraCrypt%201.23/
EDIT
other things, why the h2 version isn't in the official channel ?
thanks you
Last edit: pidibi952834 2018-11-14
This is a fair question. Why do people have to drill down into the forum to see what is labelled as a hotfix? It should be on the download page.
Since Hotfix-2 applies only to Windows, I was reluctant to perform a
full build on all other operating systems for a 1.23-Hotfix-2 release
and so I didn't update the official download page with 1.23-Hotfix-2 links.
Now I understand the confusion and I have come up with simple solution:
I have updated the official download page
(https://www.veracrypt.fr/en/Downloads.html) with links to 1.23-Hotfix-2
specific to Windows and I indicate that there are two stable versions:
1.23-Hotfix-2 for Windows and 1.23 for the other operating systems.
This is not perfect but at least things are clear.
I have also added the SHA256 checksum as requested.
thanks you for the cleanup and the sha256 ^^
@Mounir:
Again, thank You for the continuous contribution to the project. If I may, I am really, really desperate for the following feautures I had asked long before. Is there any chance they would exist in 1.24, especially the first one, Mounir? Thank You so much for Your answer and any effort to make these features real.
1) Allow custom/textless message for Rescue Disk
2) Option to hide tray icon of the VeraCrypt background task
Hello Mounir,
Any reason why 1.23 Hotfix 2 was re-uploaded Decemeber 19, 2018? The readme does not include any new changes.
Last edit: Enigma2Illusion 2018-12-19
I just created a separate folder for 1.23-Hotfix-2 ans I uploaded the same files as the ones that were present in the Nightly Builds folder.
I did this because I want Nightly Builds to contains latest 1.24-Beta builds and since 1.23-Hotfix-2 is stable, it deserves to have its own release folder.
The most important this is the the 1.23-Hotfix-2 files are unchanged and this can be verified.