Good morning to you both, I hope you are both well.
May I make a request for the GitHub ticket (GH #1346) to be addressed sometime in 2025, please? 7-Zip has addressed two security vulnerabilities in versions 24.08 and 24.07. I realize VeraCrypt may not be affected by these issues, but it may benefit from the other changes in the updated 7z.dll:
Mounir thank you so much for all that you do! It’s been a productive year. I am delighted to see you are receiving some help from others e.g. for VeraCrypt crash reporting. I’m loving version 1.26.15 of VeraCrypt, it is working perfectly for me.
Mounir, best wishes to you and your family, especially your daughter whom you mentioned to us.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The VeraCrypt homepage was updated yesterday to reflect the 1.26.15 release, so it's strange that you're not seeing it. I think your browser is showing a cached version of the homepage. Try clearing your browser cache.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@enigma2illusion: I try to stay organized to optimize my time and keep track of all necessary tasks but I'm not as efficient or as fast as I was 11 years ago. I've slowed down which explains the various small issues that pop up here and there.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks very much for a lot of hard work and attention to detail!!! You guys make an excellent team! I got my notification a short time ago from the SourceForge update system proclaiming the happy news of your new baby :)
👍
3
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good day, TYVM for all.
I write here only for info.
I'm sure that is a false positive, but my AV 360 TS on exe of v1.26.15 make me error on cloud database, so i'm back to v1.26.14 and this version no problems, is all ok.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Unfortunately, false positives often occur with new releases. This is typically resolved within a few weeks once people report them to the affected vendor.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@userhd: Thanks for providing the details. As I suspected, this appears to be a heuristic-based detection which can sometimes lead to false positives. In my experience, it's not uncommon for less established antivirus engines to report higher rates of false positives when using heuristic analysis compared to major AV solutions. Nonetheless, it's always a good idea to cross-check with other engines for confirmation.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Be sure to reboot your PC after the upgrade as prompted by the VeraCrypt installer which has fixed this error for other forums users.
If the reboot does not resolve the error, check the version of the veracrypt.exe file is using 1.26.15 version since there may have been an issue during the upgrade and the file was not updated.
Disable your AV/Malware software, re-run the 1.26.15 installer software and when completed, reboot PC.
Last edit: Enigma2Illusion 2024-09-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thx for your reply.
Sry, I didn't mention that I use the portable version.
However, it works with the restart.
But there is no Info about restarting the system in the portable version.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is a tricky situation. In portable mode, while there’s technically no installation, VeraCrypt still loads its driver into the Windows kernel using the portable binaries to enable volume mounting. However, in many cases, the driver remains loaded, even after the portable instance is closed. This creates an issue when you try to run a new set of binaries since the system will default to using the already loaded driver which may not be compatible with the new binaries.
Currently, VeraCrypt has a version mismatch detection mechanism for drivers, but it only compares the first two parts of the version number. For example, versions like 1.26.7 and 1.26.15 are seen as identical, which can lead to compatibility issues.
To address this, the ideal solution is to enhance the version check to compare the entire version number, ensuring that all parts are verified. This improvement will be implemented in the next release.
Until then, avoid using different versions of portable mode in the same Windows session. Always reboot your system when switching to a different portable version to prevent conflicts.
👍
2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Mounir,
I never had this kinda issues with former versions.
Maybe you can add a "reboot note" for every source of the portable version.
THX in advance.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have this same issue on a single windows system that has been rebooted multiple times. Using the portable version and verified it is running version 1.26.15 using taskmgr.
I will add I can mount the volume on a different computer without any issue using the same portable files just recopied.
Winver Win 10 22H2 19045.5011 which is the same version as the system that the mount works on.
Last edit: lawson23 2024-11-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
mount option /m noattach is bugged
after mounting volume with this option, volume id can't be seen in mountvol ouput
so we can't start command as :
mountvol c:\data \?\Volume{ff85e292-c1b9-11ee-8c1e-e03f49358a76}\
best regards
Last edit: petitlou60 2024-09-08
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Version 1.26 and newer of VeraCrypt versions has deprecated the following features:
.
See documentation below for remediation procedures.
Conversion Guide for VeraCrypt 1.26 and Later
https://sourceforge.net/projects/veracrypt/files/VeraCrypt%201.26.15/
Changes between 1.26.14 and 1.26.15 (2 September 2024) :
Hello Mounir and Enigma2Illusion,
Good morning to you both, I hope you are both well.
May I make a request for the GitHub ticket (GH #1346) to be addressed sometime in 2025, please? 7-Zip has addressed two security vulnerabilities in versions 24.08 and 24.07. I realize VeraCrypt may not be affected by these issues, but it may benefit from the other changes in the updated 7z.dll:
https://www.7-zip.org/history.txt
Mounir thank you so much for all that you do! It’s been a productive year. I am delighted to see you are receiving some help from others e.g. for VeraCrypt crash reporting. I’m loving version 1.26.15 of VeraCrypt, it is working perfectly for me.
Mounir, best wishes to you and your family, especially your daughter whom you mentioned to us.
Is this official final release? as home page still has no info
The VeraCrypt homepage was updated yesterday to reflect the 1.26.15 release, so it's strange that you're not seeing it. I think your browser is showing a cached version of the homepage. Try clearing your browser cache.
Hey, it's fixed now, i've noticed this thread a second or so after Enigma's post, and I think you updated home page a few mins later or so,
Hi @idrassi
The big green Download button at the link below goes to the Windows 1.26.7 version of VeraCrypt instead of the latest version.
https://sourceforge.net/projects/veracrypt/
Indeed, my bad!
I have just update Sourceforge link to latest release.
Sorry for the misunderstanding.
I think ara's issue is different than the SourceForge green download button.
Thank you for fixing the green download button.
Honestly, I do not know how you are able to manage new source code changes, bug/support tickets and software releases across:
Bitbucket
GitHub
Launchpad
SourceForge
VeraCrypt
Last edit: Enigma2Illusion 2024-09-04
@enigma2illusion: I try to stay organized to optimize my time and keep track of all necessary tasks but I'm not as efficient or as fast as I was 11 years ago. I've slowed down which explains the various small issues that pop up here and there.
Mounir Idrassi & Enigma2Illusion,
Thanks very much for a lot of hard work and attention to detail!!! You guys make an excellent team! I got my notification a short time ago from the SourceForge update system proclaiming the happy news of your new baby :)
Good day, TYVM for all.
I write here only for info.
I'm sure that is a false positive, but my AV 360 TS on exe of v1.26.15 make me error on cloud database, so i'm back to v1.26.14 and this version no problems, is all ok.
Thanks @userhd for the information. Could you please share more details about the error reported by AV 360 TS?
VirusTotal doesn't show any positive detections: https://www.virustotal.com/gui/file/bc569a7876587ee139254ccd058493bed1d8a5efe3cd6b4578a2a4125950ae86
Unfortunately, false positives often occur with new releases. This is typically resolved within a few weeks once people report them to the affected vendor.
My info/error is:
Type:
Win64/Heur.Generic.H8oAy20A
Scan Engine:
Motore 360 Cloud Scan
Error:
Win64/Heur.Generic-H8oAy20A
Dir file:
C:......\VeraCrypt-x64.exe
Dim file:
5.92M (6,204,136 Bytes)
Ver. file:
1.26.15
MD5:
d11879af08997c3c8a0eaada506bc2b9
Digit Firm:
IDRIX SARL
Suggestion:
Quarantined files
TVM for all.
@userhd: Thanks for providing the details. As I suspected, this appears to be a heuristic-based detection which can sometimes lead to false positives. In my experience, it's not uncommon for less established antivirus engines to report higher rates of false positives when using heuristic analysis compared to major AV solutions. Nonetheless, it's always a good idea to cross-check with other engines for confirmation.
Hi,
I can't mount my volume with the new version.
Hope you can help me out here.
Cheers!
Be sure to reboot your PC after the upgrade as prompted by the VeraCrypt installer which has fixed this error for other forums users.
If the reboot does not resolve the error, check the version of the veracrypt.exe file is using 1.26.15 version since there may have been an issue during the upgrade and the file was not updated.
Disable your AV/Malware software, re-run the 1.26.15 installer software and when completed, reboot PC.
Last edit: Enigma2Illusion 2024-09-04
Thx for your reply.
Sry, I didn't mention that I use the portable version.
However, it works with the restart.
But there is no Info about restarting the system in the portable version.
Hi @idrassi
Based on the post above, the Windows portable installer should provide a reboot prompt during upgrades.
@slapshot @enigma2illusion:
This is a tricky situation. In portable mode, while there’s technically no installation, VeraCrypt still loads its driver into the Windows kernel using the portable binaries to enable volume mounting. However, in many cases, the driver remains loaded, even after the portable instance is closed. This creates an issue when you try to run a new set of binaries since the system will default to using the already loaded driver which may not be compatible with the new binaries.
Currently, VeraCrypt has a version mismatch detection mechanism for drivers, but it only compares the first two parts of the version number. For example, versions like 1.26.7 and 1.26.15 are seen as identical, which can lead to compatibility issues.
To address this, the ideal solution is to enhance the version check to compare the entire version number, ensuring that all parts are verified. This improvement will be implemented in the next release.
Until then, avoid using different versions of portable mode in the same Windows session. Always reboot your system when switching to a different portable version to prevent conflicts.
Hi Mounir,
I never had this kinda issues with former versions.
Maybe you can add a "reboot note" for every source of the portable version.
THX in advance.
I have this same issue on a single windows system that has been rebooted multiple times. Using the portable version and verified it is running version 1.26.15 using taskmgr.
I will add I can mount the volume on a different computer without any issue using the same portable files just recopied.
Winver Win 10 22H2 19045.5011 which is the same version as the system that the mount works on.
Last edit: lawson23 2024-11-05
Hello,
mount option /m noattach is bugged
after mounting volume with this option, volume id can't be seen in mountvol ouput
so we can't start command as :
mountvol c:\data \?\Volume{ff85e292-c1b9-11ee-8c1e-e03f49358a76}\
best regards
Last edit: petitlou60 2024-09-08
Hi @petitlou60
Please include the specific version of Windows. You can run "winver" to get the version and build number.
This will help the developer in trying to recreate the problem.
Hello
my windows is Windows 11 23H2 22631.4112
/m noattach problem occurs also with 1.26.7 release
Hi @petitlou60
Do you recall which version of VeraCrypt that the issue did not occur?