Activity for Enigma2Illusion
-
Enigma2Illusion posted a comment on discussion General Discussion
You never provided a properties screenshot of the volume when mounted using the 1.25.4 of the volume showing the TrueCrypt Mode value. This will help diagnosis if your volume is actually mounting in the older version because it is using TrueCrypt Mode which does not exist in 1.26.x version.
-
Read the following post and the links within the post: https://sourceforge.net/p/veracrypt/discussion/general/thread/3903ea9e97/#8cc3/cc1a
-
The line numbers do change between versions if new code and/or deleted code is made to that module that results in a different line number for the error message. The text of the error message tells you cause(s) and/or the remediation of the error. EDIT: Here is the developer explaining the line number being different between versions. https://sourceforge.net/p/veracrypt/discussion/technical/thread/c263c33ffe/?limit=25#e987
-
The line numbers do change between versions if new code and/or deleted code is made to that module that results in a different line number for the error message. The text of the error message tells you cause(s) of the error. EDIT: Here is the developer explaining the line number being different between versions. https://sourceforge.net/p/veracrypt/discussion/technical/thread/c263c33ffe/?limit=25#e987
-
The line numbers do change between versions if new code and/or deleted code is made to that module that results in a different line number for the error message. The text of the error message tells you cause(s) of the error.
-
My understanding is John is not using system encryption as he stated in the second paragraph. Only file containers to store financial information. Hence there is no need to clone the drive to upgrade VeraCrypt. John can downgrade by uninstalling the latest version and reinstall 1.22 version.
-
It is not an error code. It is a source of the error and the line number in the code for that specific version of VeraCrypt for the developer to know which module and line number issued the error for troubleshooting a possible bug in the code.
-
User solved problem by shrinking using Windows Disk Management instead of gparted. https://github.com/veracrypt/VeraCrypt/issues/1423#issuecomment-2380051670
-
I know you are using Linux. My point is the 1.24.4 version volume properties should show the TrueCrypt Mode which is not shown in your screenshot. BTW: The title says you upgraded from 1.25.4 and your posts say 1.24.4 which should be 1.24-Update4 version. Which version is the working version? 1.25.4?
-
I know you are using Linux. My point is the 1.24.4 version volume properties should show the TrueCrypt Mode which is not shown in your screenshot. BTW: The title says you upgraded from 1.25.4 and your posts say 1.24.4 which should be 1.24-Update4 version. Which version is the working version?
-
I know you are using Linux. My point is the 1.24.4 version volume properties should show the TrueCrypt Mode which is not shown in your screenshot.
-
@lowender Hi John, See the documentation below to determine if you need to remediate your volumes before upgrading to Windows VeraCrypt to the current 1.26.15 version as of this date. https://www.veracrypt.fr/en/Conversion_Guide_VeraCrypt_1.26_and_Later.html In short, you need to upgrade your VeraCrypt software since there are newer internal libraries for more secure VeraCrypt software and hence your volumes.
-
@andyrozman Hi Andy, On Windows platforms pre-1.26.x versions show in the volume properties a line item called TrueCrypt Mode with value of either Yes or No. I noticed the TrueCrypt Mode line item is missing from your screenshot when you reverted back to 1.24..4 version. Can you confirm that you are currently using 1.24.4 version and the volume properties of the "normal" VeraCrypt volume does not show the TrueCrypt Mode line item?
-
@ andyrozman Hi Andy, On Windows platforms pre-1.26.x versions show in the volume properties a line item called TrueCrypt Mode with value of either Yes or No. I noticed the TrueCrypt Mode line item is missing from your screenshot when you reverted back to 1.24..4 version. Can you confirm that you are currently using 1.24.4 version and the volume properties of the "normal" VeraCrypt volume does not show the TrueCrypt Mode line item?
-
In order for someone to replicate your issue, what are the specific versions of Windows OSes and Ubuntu OS along with the specific versions of VeraCrypt on the OSes? Also, are you using on Windows the VeraCrypt portable or installed versions?
-
In order for someone to replicate your issue, what are the specific versions of Windows OSes and Ubuntu OS along with the specific versions of VeraCrypt on the OSes?
-
In order for someone to replicate your issue, what are the specific versions Windows OSes and Ubuntu OS along with the specific versions of VeraCrypt on the OSes?
-
In order for someone to replicate your issue, what are the versions of the specific versions Windows OSes and Ubuntu OS along with the specific versions of VeraCrypt on the OSes?
-
In order for someone to replicate your issue, what are the versions of the specific versions Windows OS and Ubuntu OS along with the specific versions of VeraCrypt on the OSes?
-
@daweiliuli Post a screenshot of your Settings > Preferences. As stated in my post below, Fast Start creates this issue and may not be consistent depending on your Preference settings. https://sourceforge.net/p/veracrypt/discussion/general/thread/8bc6adf664/?limit=25#f113 BTW: 1.26.15 is available for Windows.
-
@davedodo Another important detail is how you are imaging/backing-up your VeraCrypt system encryption using Macrium Reflect. You perform the Reflect imaging while the OS is running. You perform the Reflect imaging using the Reflect Rescue Disk in this case the OS is not running. The Reflect output image files are still encrypted by VeraCrypt but cannot be mounted by Reflect to explore the files in the image. . Reflect imaging or cloning while the OS is running Reflect imaging/cloning while the OS...
-
@davedodo My understanding is you merely have VeraCrypt system encryption which is a different scenario than petitlou60. Do you have a VeraCrypt encrypted partition in front of all the Windows partitions like petitlou60 has as shown in the screenshot attachment in his post below? https://sourceforge.net/p/veracrypt/discussion/general/thread/8d9f4f9c84/?limit=25#1ebc
-
@davedodo I use Macrium Reflect to backup my encrypted Windows system partition After reading this, I am reluctant to upgrade. Will this offset issue interfere with the backup? Hi David, As I recommended to petitlou60, I would ask your question on the Macrium Reflect forum as stated in my post above using the developer's explanation to get an answer and/or resolution from Macrium.
-
@wanderer51 Well, that's why i attached the config file... :) I never download or execute files from unknown sources. :)
-
@wanderer51 Well, that's why i attached the config file... :) I never download files from unknown sources. :)
-
Did the VeraCrypt GUI show the Wipe Cache button enabled? If yes, you cached the password. Did you check if Fast Startup was enabled? If yes, disable Fast Startup and reboot your PC. https://sourceforge.net/p/veracrypt/discussion/general/thread/8bc6adf664/?limit=25#f113
-
I am getting this when trying to verify the .deb package: gpg --verify veracrypt-1.26.14-Ubuntu-24.04-amd64.deb.sig veracrypt-1.26.14-Ubuntu-24.04-amd64.deb gpg: Signature made Mon 26 Aug 2024 02:41:33 PM PDT gpg: using RSA key 5069A233D55A0EEB174A5FC3821ACD02680D16DE gpg: Good signature from "VeraCrypt Team (2018 - Supersedes Key ID=0x54DDD393) veracrypt@idrix.fr" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to...
-
Sorry for the long delay and thank you for the link. I was aware of the file format differences just not how they might matter in VeraCrypt. It looks like since all my volumes were created with FAT and are working fine, there is no particular advantage to converting them at this time. I guess the one issue would be data recovery. As I said was that I had mistakenly opened VeraCryptExpander, which I had forgotten was also installed when I installed VeraCrypt. Thanx much. Elliott ...
-
I found on GitHub that the noattach switch was added in 1.24-Hotfix 1 released on October 27, 2019. There has been no modifications to the code for the CLI noattach in Mount.c since the release in 1.24-Hotfix 1. https://github.com/veracrypt/VeraCrypt/commit/28b8bf522219339d4264fe9af8ab0055f8c74aad https://github.com/veracrypt/VeraCrypt/commit/2117490500cb21fc49871bf80964ffbdf11925bd
-
Hi @petitlou60 Do you recall which version of VeraCrypt that the issue did not occur?
-
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.
-
why does Fast Format need 2 minute to complete the format? I don't remember this wait when I used TrueCrypt for my old disks... VeraCrypt by default performs more iterations for the hash than TrueCrypt. Why installing 1.26.15 over 1.25.9 makes VC say "Updated VeraCrypt Bootblock"? What is changed? If you have not seen this message when upgrading previous VeraCrypt system encryption, I do not know why this message was displayed or the technical reason for the message.
-
Hi Jonathan, Per the private message exchange, the issue is likely a device problem that caused the read-only to be set on the device. Per our exchange, please provide the user community with the specific OS version and VeraCrypt version. VeraCrypt is user community supported for assisting other users. Hence, you may not get answers to your questions or issues. Can you mount the VeraCrypt volume using the Options button and enabling "Mount volume as read-only"? This should allow you to copy your...
-
Hi Jonathan, Per the private message exchange, the issue is likely a device problem that caused the read-only to be set on the device. Per our exchange, please provide the user community with the specific OS version and VeraCrypt version. VeraCrypt is user community supported for assisting other users. Hence, you may not get answers to your questions or issues. Can you mount the VeraCrypt volume using the Options button and enabling "Mount volume as read-only"? This should allow you to copy your...
-
Version 1.26 and newer of VeraCrypt versions has deprecated the following features: TrueCrypt Mode HMAC-RIPEMD-160 Hash Algorithm GOST89 Encryption Algorithm . See documentation below for remediation procedures. Conversion Guide for VeraCrypt 1.26 and Later
-
Windows Portable Prompt for Reboot During Upgrade
-
Hi @idrassi Based on the post above, the Windows portable installer should provide a reboot prompt during upgrades.
-
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.
-
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 that you are using is 1.26.15 version since there may have been an issue during the upgrade and the file was not updated.
-
Be sure to reboot your PC after the upgrade as prompted by the VeraCrypt installer has fixed this error for other forums users. If the reboot does not resolve the error, check the version of the VeraCrypt.exe file that you are using is 1.26.15 version since there may have been an issue during the upgrade and the file was not updated.
-
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
-
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 and software releases across: Bitbucket GitHub Launchpad SourceForge VeraCrypt
-
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/
-
Version 1.26 and newer of VeraCrypt versions has deprecated the following features: TrueCrypt Mode HMAC-RIPEMD-160 Hash Algorithm GOST89 Encryption Algorithm . 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) : Windows: Fix MSI install/uninstall issues: Fixed error 1603 returned by MSI silent install when REBOOT=ReallySuppress...
-
First, did you reboot after you upgraded to 1.26.14? https://sourceforge.net/p/veracrypt/discussion/general/thread/8d9f4f9c84/#bb17/373a Depending how you link or use another copy of the veracrypt.exe could be the problem. See the thread below. https://sourceforge.net/p/veracrypt/discussion/technical/thread/c263c33ffe/#7b76 Does directly using the upgraded 1.26.14 GUI work correctly mounting your volumes but not your batch script? Please post the batch script.
-
The Fast Create was added to the GUI starting with 1.26.7 version. The latest version is 1.26.14 and I would recommend all users upgrade to the latest version. Pay attention to my note at the top before upgrading to 1.26 or newer versions. https://sourceforge.net/p/veracrypt/discussion/general/thread/8d9f4f9c84/ Mounir has written a utility that will allow you to migrate from TrueCrypt to VeraCrypt that is in the documentation.
-
In the case of successful system decryption of the OS drive/partition but the VeraCrypt bootloader remains, try the following procedures. Do not use the VeraCrypt Rescue Disk for the following procedures. On the VeraCrypt bootloader screen, press the ESC key to bypass the VeraCrypt bootloader to continue booting into Windows OS since the OS partition is decrypted. Run as administrator the Windows VeraCrypt application by right clicking on the VeraCrypt icon and selecting "Run as administrator". In...
-
Read my post at the link below to get a better understanding of Quick Format. Quick Format for File Container via the GUI checkbox will skip filling the entire space with random data which has security risks. However, Windows OS will fill the space with zeros which is encrypted causing very time consuming creation for large file containers. . Hence, it is going to take a long time. https://sourceforge.net/p/veracrypt/discussion/general/thread/8bf650d8ce/?limit=25#c3c9 Something for your consideration...
-
Is your Windows account on your PC in the Administrator group? If not, that may explain why the first system decryption was not able to replace the VeraCrypt bootloader with the original Windows bootloader when it successfully completed the data decryption.
-
What size is the encrypted disk and what did you select for the filesystem? What size is the file container you are creating within the encrypted disk and the filesystem? Which format did you select for file container? (Full, Quick, Fast) Are you using a custom PIM value for either or both disk and file container? You understand that when you are encrypting within an encrypted volume, you are doubling the CPU workload and doubling the disk read/write processing.
-
What size is the encrypted disk and what did you select for the filesystem? What size is the file container you are creating within the encrypted disk and the filesystem? Which format did you select for file container? (Full, Quick, Fast) Are you using a custom PIM value for either or both disk and file container? You understand that when you are encrypting within an encrypted volume, you are quadrupling the CPU workload and quadrupling the disk read/write processing.
-
In the case of successful system decryption of the OS drive/partition but the VeraCrypt bootloader remains, try the following procedures. Do not use the VeraCrypt Rescue disk for the following procedures. On the VeraCrypt bootloader screen, press the ESC key to bypass the VeraCrypt bootloader to continue booting into Windows OS since the OS partition is decrypted. Run as administrator the Windows VeraCrypt application by right clicking on the VeraCrypt icon and selecting "Run as administrator". In...
-
@anakunda Did you install the previous 1.26.7 version using the Windows 1.26.7 MSI installer?
-
It depends on your threat model. You can read the link below to understand if someone can get access to copy your file container at various points in time. https://www.veracrypt.fr/en/How%20to%20Back%20Up%20Securely.html Otherwise, yes you can copy from the pen drive to your PC.
-
You mean the VeraCrypt_Setup_x64_1.26.14.msi file? Are you using the MSI which is meant for Windows silent deployment for installing on other user PCs? The MSI should have the languages directory. @idrassi The documentation for Language Packs still references the 1.26.7 version and links to the Languages zip file of the 1.26.7 version. Is there a reason for having the Languages pack zip file since the Windows installers should already create the languages directory?
-
@anakunda Which OS platform and the file installer are you using that does not include the languages directory after running the installer? https://www.veracrypt.fr/en/Language%20Packs.html
-
@anakunda Which OS platform and the file installer are you using that does not include the languages directory after running the installer?
-
@petitlou60 I have the paid version, however I am out of technical support. However, even using the unsupported free version, which you should include in your post, you can report the issue you encountered and link back to Mounir's post to get help from some of the forum members on the Reflect product. You can ask if this problem would be resolved in the current paid version of Reflect. Macrium support monitors the user forum and if they think this issue impacts the current paid version which is...
-
@csysmis See solution from the developer at the link below. Could you please check the version of the VeraCrypt.exe file that you are using? It’s possible there was an issue during the upgrade, and the file was not updated correctly. https://sourceforge.net/p/veracrypt/discussion/technical/thread/c263c33ffe/#e987 I will add to Mounir's statement to be sure to perform the required reboot after you upgrade when the VeraCrypt installer prompts you in order to use the newer version.
-
I will add to Mounir's statement to be sure to perform the required reboot after you upgrade when the VeraCrypt installer prompts you in order to use the newer version.
-
I will add to Mounir's statement to be sure to perform the required reboot after you upgrade when the VeraCrypt installer prompts you to perform in order to use the newer version.
-
@csysmis See solution from the developer at the link below. Could you please check the version of the VeraCrypt.exe file that you are using? It’s possible there was an issue during the upgrade, and the file was not updated correctly. https://sourceforge.net/p/veracrypt/discussion/technical/thread/c263c33ffe/#e987 I will add to Mounir's statement to be sure to perform the required reboot after you upgrade when the VeraCrypt installer prompts you to perform in order to use the newer version.
-
OS: Windows 10 22H2 Build: 19045.4780 After upgrading from Veracrypt 1.26.7 to 1.26.14, I am getting the following error on all my VC volumes (4), hc containers and partitions alike: The data area passed to a system call is too small Source: MountVolume:8887 I am using the VC UI. Reverting back to 1.26.7 resolves it for me. Any idea ? MOD EDIT: Including Mis Support's volume detail from the other thread shown below. Yes, I am using the VC GUI, those volumes are native veracrypt volumes. Example:...
-
@idrassi Another person is reporting the same problem using CLI in the thread below in addition to Mis Support's post above using the GUI getting the same error. https://sourceforge.net/p/veracrypt/discussion/technical/thread/c263c33ffe/
-
@erasmo52 @csysmis Please post your command scripts to help the developer troubleshoot the problem. If necessary, you can replace any sensitive information in your command script with dummy information.
-
Hi John, Thank you for running the three tests and providing the VeraCrypt community with your results. On occasion, determine how you can copy/restore the Google Drive file container to a different location on your PC while leaving your original file container untouched by the copy/restore. Then on your PC, attempt to mount the Google Drive's copy/restore file container and see if you are able to access your files. In addition to occasionally testing your Google Drive restore, you can search the...
-
Hi John, I would perform the three tests in my previous post to determine the results of each test of when the file container's timestamp is modified.
-
In production release 1.26.7 version release notes: All OSes: Security: Ensure that XTS primary key is different from the secondary key when creating volumes Issue unlikely to happen thanks to random generator properties but this check must be added to prevent attacks Reference: CCSS,NSA comment at page 3: https://csrc.nist.gov/csrc/media/Projects/crypto-publication-review-project/documents/initial-comments/sp800-38e-initial-public-comments-2021.pdf . The 1.26.14 version now includes the check when...
-
In production release 1.26.7 version release notes: All OSes: Security: Ensure that XTS primary key is different from the secondary key when creating volumes Issue unlikely to happen thanks to random generator properties but this check must be added to prevent attacks Reference: CCSS,NSA comment at page 3: https://csrc.nist.gov/csrc/media/Projects/crypto-publication-review-project/documents/initial-comments/sp800-38e-initial-public-comments-2021.pdf . The 1.26.14 version now includes the check when...
-
Version 1.26 and newer of VeraCrypt versions has deprecated the following features: TrueCrypt Mode HMAC-RIPEMD-160 Hash Algorithm GOST89 Encryption Algorithm . See documentation below for remediation procedures. Conversion Guide for VeraCrypt 1.26 and Later https://sourceforge.net/projects/veracrypt/files/VeraCrypt%201.26.14/ Changes between 1.26.7 and1.26.14 (25 August 2024) : All OSes: Update translations and documentation Implement language selection settings in non-Windows versions. Make codebase...
-
Preserve Accessed Timestamp of File Containers
-
Indeed your file system is damaged and depending on the damage will require data recovery software. The procedures I would perform to attempt to regain access to the filesystem and/or data: With the VeraCrypt dismounted, clone the disk or partition to another drive. Use only the clone for data recovery so you can use multiple data recovery tools by re-cloning from the source disk/partition. The following is done only on the clone using an account with Administrator privilege. In the VeraCrypt application,...
-
Hi @idrassi Excellent work as usual Mounir. Thank you for adding this information to the documentation which came to my attention while helping another user to convert TC to VC.
-
PS: Perform the Settings -> Preferences -> uncheck the box "Preserve modification timestamp of file containers". Create a small test file container and use a simple Notepad file to change within the mounted file container. Use Windows Explorer and the refresh (F5 button) to monitor what happens to the file container's timestamp when you: Mount and dismount without changes. Does the dismount change the timestamp? Mount and change the Notepad file but leave the volume mounted. Does this change the...
-
Indeed your file system is damaged and depending on the damage will require data recovery software. The procedures I would perform to attempt to regain access to the filesystem and/or data: With the VeraCrypt dismounted, clone the disk or partition to another drive. Use only the clone for data recovery so you can use multiple data recovery tools by re-cloning from the source disk/partition. The following is done only on the clone using an account with Administrator privilege. In the VeraCrypt application,...
-
Does the timestamp only change once you dismount the file container regardless of file changes in the file container?
-
Here is an article that you can read about the differences of FAT, exFAT and NTFS file system formats. https://www.pcmag.com/how-to/fat32-vs-exfat-vs-ntfs-which-format-is-best-for-your-storage-drive My preference is to use NTFS since I am not trying to copy the file container to use on other OS platforms like Linux that can support NTFS starting with Linux 5.15 kernel or Mac using third party drivers which can read and write to NTFS. To change file system formats, you will need to create a new file...
-
Here is an article that you can read about the differences oif FAT, exFAT and NTFS file system formats. https://www.pcmag.com/how-to/fat32-vs-exfat-vs-ntfs-which-format-is-best-for-your-storage-drive My preference is to use NTFS since I am not trying to copy the file container to use on other OS platforms like Linux that can support NTFS starting with Linux 5.15 kernel or Mac using third party drivers which can read and write to NTFS. To change file system formats, you will need to create a new file...
-
The file container will not synchronize to the cloud. You want to synchronize to the cloud by the changing of the modification timestamp on the file container and only synchronize when the file container is closed/dismounted. Otherwise, the file container will be corrupted on the cloud. Be aware that each time you dismount the file container, the entire size of the file container has to synchronize to the cloud. To allow the file containers to allow updating the modification timestamp after you dismount...
-
In order to answer you questions regarding your file container(s), I need more information from you. Do you use your file container on Linux and/or Mac OS?
-
You can download the Windows 1.26.7 installer VeraCrypt Setup 1.26.7.exe for your PC found on SourceForge in the Files -> VeraCrypt 1.26.7 -> Windows. I have direct linked the file for you.
-
On the problem PC, press the ESC key on the password screen.
-
Are you wanting to reinstall Windows 10 by formatting the OS disk and reinstall Windows which will require an Windows 10 install disk? Or do you just want to remove all of your personal files, apps, and settings from Windows 10 via the Reset PC -> Remove everything which does not reinstall the OS? The Reset PC option is going to require you to decrypt your PC since your disk/OS is encrypted. Decryption only decrypts the files that exist and takes less time than encrypting since the entire disk/partition...
-
Were you still in the System Encryption Pretest phase? If yes, just press the ESC key on the VeraCrypt bootloader screen to load Windows. Nothing has been encrypted during the System Encryption Pretest phase.
-
Hi @idrassi Correctly, the documentation for TrueCrypt Support no longer exists in the 1.26 version. I would like to request the following information be included to the Converting TrueCrypt volumes and partitions documentation to help users determine proactively if their TrueCrypt volumes would be eligible to be converted to VeraCrypt volumes. Three options for location and wording in the documentation shown below. I like the options that tell the user when TC v6.0 was released so they do not have...
-
Regardless of TC or VC, you should already have backups of your data on another disk drive. If you value your data, always have frequent backups of your data due to possible hardware failure, software issues or user error which can cause loss of data and/or access to either the unencrypted drive or an encrypted disk, partition or file container. Which version of TrueCrypt did you create your file containers? VeraCrypt conversion only supports TrueCrypt volumes created with TrueCrypt 6.x or newer...
-
@idrassi Thank you for your understanding. I retested the Volume Tools using wrong password, PIM, hash or wrong keyfiles where appropriate and I did not encounter any crashes. One anomaly I noticed is that the shortcut keys for the various Volume Tools only work for the PIM. The following shortcut keys are not working: ALT-d or ALT-D for Display password ALT-s or ALT-S for Use keyfiles ALT-k or ALT-K for Keyfiles button ALT-o or ALT-O for Mount Options button
-
Version 1.26 and newer of VeraCrypt versions has deprecated the following features: TrueCrypt Mode HMAC-RIPEMD-160 Hash Algorithm 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.14 (25 August 2024) : All OSes: Update translations and documentation Implement language selection settings in non-Windows versions....
-
@idrassi I just noticed in 1.26.13 that none of the CTRL key shortcuts work. For example, when mounting a volume, the previously available CRTL keys worked: CTRL-i for PIM CTRL-e for Cache Password and Keyfiles CTRL-d for Display Password CTRL-s for Use Keyfiles This occurs in all screens. Password Dialog, Mount Options, Volume Tools, etc.
-
@idrassi Also in the password dialog box CTRL key shortcuts are not working: CTRL-k for Keyfiles button CTRL-o for Mount Options button
-
@idrassi Disregard my posts about the shortcut keys not working. I should be using ALT key instead of CTRL key for VeraCrypt. I confused VeraCrypt with another application that uses the CTRL keys. I am sorry Mounir for the false report.
-
@idrassi Also in the password dialog box CTRL key shortcuts are not working: CTRL-k for Keyfiles button CTRL-o for Mount Options button
-
@idrassi I just noticed in 1.26.13 that none of the CTRL key shortcuts work. For example, when mounting a volume, the previously available CRTL keys worked: CTRL-i for PIM CTRL-e for Cache Password and Keyfiles CTRL-d for Display Password CTRL-s for Use Keyfiles This occurs in all screens. Password Dialog, Mount Options, Volume Tools, etc.
-
@idrassi Does the code change Fix regression causing crash when a wrong password is used when changing password of volumes also fix the crash for wrong: Set Header Key Derivation Algorithm Add/Remove key files Remove all key files
-
Something to be mindful of is the xz utils backdoor a few months ago. I suspect Veracrypt would be a target for something similar, so any new contributors should be vetted carefully, and pressure on Mounir to "be faster" should be ignored, which so far has been which is good! The developer of xz faced pressure similar to Mounir to be faster with updates. MOD EDIT: Here is a great write-up on Wikipedia. https://en.wikipedia.org/wiki/XZ_Utils_backdoor
-
Windows associates the .hc file extension to the VeraCrypt application when you install VeraCrypt on the PC for file containers. In the password dialog box, you have to enable the box TrueCrypt Mode in order to mount a TrueCrypt volume in 1.25.9 or older versions. The best solution is to convert the TrueCrypt file container to VeraCrypt using the documentation below. To be upgrade compatible with 1.26 and newer versions, if your TrueCrypt is using HMAC-RIPEMD-160 hash (the PKCS-5 PRF), select a different...
-
@hiddengod Mounir posted that his availability to work on VeraCrypt is going to be extremely limited due to personal family obligations requiring more of his time. https://sourceforge.net/p/veracrypt/discussion/general/thread/6d0c0dfdc8/?page=1&limit=25#ab89 Hence, I would say to all VeraCrypt users that have been wanting or waiting for a certain feature are not likely going to see them implemented anytime soon unless Mounir gets coding, testing and maintenance help from other people. Kudos to @jertzukka...
-
@idrassi I noticed in the Source Code the change item: "Windows: Only load valid XML language files (Language.xx.xml or Language.xx-yy.xml format)". I looked in my C:\Program Files\VeraCrypt\Languages directory and found an old XML file with an install date of 7/25/2023 from the 1.26.4 version called "for_use_veracrypt_languagexml_pt_BR.xml". Snippet of the contents of the XML file in Notepad: VeraCrypt> <localization prog-version= "1.26.4"> <language langid="pt-br" name="Português-Brasil" en-name="Portuguese...
-
EDIT: Move discussion out of the 1.26.13 thread to the feature request thread since this thread should be about any issues with 1.26.13 version.
1 >