.
The 1.26.14 version now includes the check when you mount the volume or backup/restore the header of the volume. This was added due to volumes being created pre-1.26.7 version.
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.
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.
Last edit: Enigma2Illusion 2024-08-29
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The issue was indeed somehow the installer failing to update veracrypt binaries properly, even after the reboot. I uninstalled VC, rebooted, installed VC, rebooted, and everything is working fine with 1.26.14. Many thanks for the follow up, much appreciated.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.
Hello
I have windows 11 23H2 system not encrypted one veracrypt partition container mounted after
winlogon on letter A
with 1.26.14 all things are ok except one strange dispaly of partition layout on
macrium reflect (which is my backup tool)
EFI partition is displayed as Data (A:) with good size 512Mo but with free space of 188Go which is size of A: freespace
hopely when i start backup saved EFI is good
I think that new release change recognition of veracrypt mounted volumes by Windows
with 1.26.7 macrium dont'see veracrypt volumes, it see only raw partitions containers
Best regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
after new tests i can see mounted veracrypt overlap first partition on macrium lay out
when attempt to save this partition , macrium attempt to save A:
so now i must dismount veracrypt before using macrium
Best regards
@petitlou60: It looks like Macrium is encountering an issue with the offset of the VeraCrypt volume, which results in it using a negative value for the free space. I suspect that the following change in version 1.26.14 may have caused this:
Fixed failure to format some disks (e.g., VHDX) caused by virtual partition offset not being 4K aligned.
In this change, the start offset of VeraCrypt volumes' virtual partition was adjusted from 512 bytes to 1 MiB to align more closely with real disk offsets and to resolve an issue with Windows formatting that expected the offset to be a multiple of 4096.
I think Macrium might be hardcoding the offset of the VeraCrypt volume instead of querying it dynamically. However, there could be another explanation. It would be helpful to report this to Macrium to get their feedback on the incorrect free space value, which I believe is due to a negative value in their calculations.
Thank you Mounir for your work and this explanation.
i use free version of macrium reflect which is now discarded from january first 2024
so there is no support nor ability to ask macrium team.
Fortunately i have a workaround: dismount veracrypt volume before use macrium for backup
this change in partition alignement seems good if i good understand now logical 4K clusters are aligned with physicals4096 sectors starting performance increase.
last question :
for existant veracrypt volumes virtual partition remain unaligned ?
is volume rebuild needed ?
Thank you for your great work
best regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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 currently 8.1.8110, they will engage since this may impact their paying retail and commercial customers.
I would recommend posting the Disk Imaging forum for v8.
@petitlou60: This change is only on the virtual device; it is independent of the physical volume. All volumes, both old and new, will benefit from this change.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@anakunda: Each version of VeraCrypt comes with updated language files. If you want to use language files from an older version, you can manually edit the file and change the prog-version value in the 3rd line to "1.26.14."
However, I strongly recommend using the language files included in the 1.26.14 installers (EXE or MSI).
Used VeraCrypt_Setup_x64_1.26.14.msi to update, but the main UI complained about obsolete language file. Now I see in the installer the language files have new timestamp but were not updated in installation folder so the issue is fixed by manual copy, the installer however failed to update the languages by itself.
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.14/
Changes between 1.26.7 and1.26.14 (25 August 2024) :
Can someone explain or link to a page explaining the XTS master key vulnerability?
In production release 1.26.7 version release notes:
All OSes:
.
The 1.26.14 version now includes the check when you mount the volume or backup/restore the header of the volume. This was added due to volumes being created pre-1.26.7 version.
https://sourceforge.net/p/veracrypt/code/ci/0388885669a4eafd640919098bd5acf0adc48218/
You can read the developers explanation at the link below.
https://sourceforge.net/p/veracrypt/discussion/general/thread/7b3f0cc3f7/#a73a
Last edit: Enigma2Illusion 2024-08-28
Thank you for your hard work and sacrifices
Merci beaucoup pour cette nouvelle 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:
Type: Normal
Encryption Algorithm: AES
Primary key size: 256 bits
Secondary key size (XTS mode): 256 bits
Block size: 128 bits
Mode of operation: XTS
PKCS-5 PRF: HMAC-SHA-512 (Dynamic)
Volme format version: 2
Embedded backup header: Yes
Last edit: Enigma2Illusion 2024-08-29
@csysmis
See solution from the developer at the link below.
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.
Last edit: Enigma2Illusion 2024-08-29
The issue was indeed somehow the installer failing to update veracrypt binaries properly, even after the reboot. I uninstalled VC, rebooted, installed VC, rebooted, and everything is working fine with 1.26.14. Many thanks for the follow up, much appreciated.
@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/
Hello
I have windows 11 23H2 system not encrypted one veracrypt partition container mounted after
winlogon on letter A
with 1.26.14 all things are ok except one strange dispaly of partition layout on
macrium reflect (which is my backup tool)
EFI partition is displayed as Data (A:) with good size 512Mo but with free space of 188Go which is size of A: freespace
hopely when i start backup saved EFI is good
I think that new release change recognition of veracrypt mounted volumes by Windows
with 1.26.7 macrium dont'see veracrypt volumes, it see only raw partitions containers
Best regards
Hello,
after new tests i can see mounted veracrypt overlap first partition on macrium lay out
when attempt to save this partition , macrium attempt to save A:
so now i must dismount veracrypt before using macrium
Best regards
Last edit: petitlou60 2024-08-29
Hello,
In attachement properties of veracrypt.exe , it seems OK
@petitlou60: It looks like Macrium is encountering an issue with the offset of the VeraCrypt volume, which results in it using a negative value for the free space. I suspect that the following change in version 1.26.14 may have caused this:
In this change, the start offset of VeraCrypt volumes' virtual partition was adjusted from 512 bytes to 1 MiB to align more closely with real disk offsets and to resolve an issue with Windows formatting that expected the offset to be a multiple of 4096.
I think Macrium might be hardcoding the offset of the VeraCrypt volume instead of querying it dynamically. However, there could be another explanation. It would be helpful to report this to Macrium to get their feedback on the incorrect free space value, which I believe is due to a negative value in their calculations.
For reference, here is the commit that introduced this change:
https://sourceforge.net/p/veracrypt/code/ci/c7deadb6bad28913798ea741ef36d0c849e2acc2/
Thank you Mounir for your work and this explanation.
i use free version of macrium reflect which is now discarded from january first 2024
so there is no support nor ability to ask macrium team.
Fortunately i have a workaround: dismount veracrypt volume before use macrium for backup
this change in partition alignement seems good if i good understand now logical 4K clusters are aligned with physicals4096 sectors starting performance increase.
last question :
for existant veracrypt volumes virtual partition remain unaligned ?
is volume rebuild needed ?
Thank you for your great work
best regards
@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 currently 8.1.8110, they will engage since this may impact their paying retail and commercial customers.
I would recommend posting the Disk Imaging forum for v8.
https://forum.macrium.com/Reflect-v8/Disk-Imaging
@petitlou60: This change is only on the virtual device; it is independent of the physical volume. All volumes, both old and new, will benefit from this change.
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?
Hello
i follow sugest of csysmis:
uninstall VC
reboot
re install VC
reboot
there is absolutly no change
Thank you to all for help
best regards
Last edit: petitlou60 2024-08-30
That was for a totally different issue:
The data area passed to a system call is too small
Source: MountVolume:8887
Hello, the non-english languages from previous version are not accepted and cause error messages. Can it be fixed?
Last edit: Anakunda 2024-08-31
@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
Last edit: Enigma2Illusion 2024-08-31
VeraCrypt_Setup_x64_1.26.14
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: Each version of VeraCrypt comes with updated language files. If you want to use language files from an older version, you can manually edit the file and change the prog-version value in the 3rd line to "1.26.14."
However, I strongly recommend using the language files included in the 1.26.14 installers (EXE or MSI).
@enigma2illusion: I have updated Language Packs page to point to the ZIP file containing the 1.26.14 language files. Thanks.
Used VeraCrypt_Setup_x64_1.26.14.msi to update, but the main UI complained about obsolete language file. Now I see in the installer the language files have new timestamp but were not updated in installation folder so the issue is fixed by manual copy, the installer however failed to update the languages by itself.