Mis Support

That was for a totally different issue: The data area passed to a system call is too small Source: MountVolume:8887

Thank you Mounir as well ! You were totally right. The issue was indeed somehow the installer failing to update the veracrypt binaries properly, even after a reboot. I uninstalled VC 1.26.7, rebooted, installed VC 1.26.14, rebooted, and everything is working fine now. Much appreciate the help.

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.

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 ?

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: 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. I am able to Any idea ?

I use the VC UI, not command line

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 I feel it is a filter driver compatibility / communication problem.

I have the exact same regression issue with 1.26.14, with all my VC volume. So it is not an isolated incident. Reverting to 1.26.7 resolves the issue. Veracrypt 2.6.14 OS: Windows 10 22H2 Build: 19045.4780 The data area passed to a system call is too small Source: MountVolume:8887