Open cyrus104 opened 1 year ago
Any thoughts on how to fix / get around this?
After upgrading and rebooting [...]
Upgrading what and rebooting what? Assuming it's about VC, what was the VC version before the upgrade? What happens if you copy the container file locally and mount it using the new version?
I went to another version of veracrypt on my laptop running windows 10 and was able to mount the same file without issues
Which version of VC was that? Can you install the same version on the system with Windows 11 21H2 you see the problem on, and try there?
Yes, I did a routine upgrade of VC to ensure I had the latest version (1.25.9).
I am am not sure what version I installed over as I didn't take a note and cause this issue. Yes, when I copy the file locally, I can open it with the current version of VC.
I will get the laptop with the older VC from my office tomorrow and update this post. As of Thursday, that Windows 10 laptop with an older version of VC (will check) was able to open the volume while it was still on the NAS.
I have used veracrypt numerous times to open/modify containers on a NAS via SMB from a Windows 10/11 machine. After upgrading and rebooting my share will no longer open and I get an error related to compression on the file. I have verified that compression is off on the NAS itself and when I right click on windows explorer and go to advanced compression is also off. I'm not sure how to solve this.
Expected behavior
I get the error below when I try to mount it using this version. I went to another version of veracrypt on my laptop running windows 10 and was able to mount the same file without issues.
Observed behavior
I get the following error when I try to mount the volume.
Steps to reproduce
Screenshots
Your Environment
Please tell us more about your environment
VeraCrypt version: 1.25.9
Operating system and version: Windows 11 21H2
System type: 64bit Intel