Problem with MacOS Ventura (13.0) and Veracrypt Container Files

Configuration:

Encrypted "Masterfile" on Time Capsule. Access via Ethernet.

Encrypted "Slavefile" stored directly on MacBook Pro.

Problem:

It is no longer possible to open both files at the same time to perform a synchronization.

When I open the second file it is shown as open in Veracrypt, but not on the MacBook (Finder). It is also displayed in the disk utility.

However, access to it via "Finder" is impossible, because the access rights are restricted, although they have been assigned.

Up to and with MacOS Monterey, this was never a problem and worked flawlessly for years.

I am grateful for any advice.

MacBook Pro 15″, macOS 13.0

Posted on Nov 15, 2022 10:28 PM

Reply

Similar questions

6 replies

Nov 18, 2022 7:32 PM in response to viktorfromschaffhausen

Is this just an encrypted folder or a container which includes a file system? What file system is being used on the encrypted container? I'm thinking the file system may be corrupted. I've seen this happen to Filevaulted drives with the APFS file system. Can you run First Aid on the unlocked volume? Even if First Aid says everything is "ok" click "Show Details" and scroll through the report to see if there are any unfixed errors listed since the First Aid summary report will lie about the results.



Nov 19, 2022 7:59 AM in response to HWTech

Thanks for your feedback. I used Veracryt 1.25.9 and the latest version of "MacFuse" to encrypt the file containers by means of FAT. This ensures that I can access the decrypted files with MacOS as well as with Windows. In the meantime I installed the application "Parallels" and can synchronize all three file containers and edit each of the files under Windows 10. So no files are corrupt or damaged.

Cheers

Nov 19, 2022 4:01 AM in response to viktorfromschaffhausen

Thanks for the feedback. To encrypt the file containers by means of FAT I used Veracrypt 1.25.9 and the latest version of "MacFuse". This ensures that I can access the decrypted files with MacOS as well as with Windows 10. As I already explained, with MacOS Monterey I was even able to open three file containers in parallel and synchronize them without any problems. In the meantime I installed the application "Parallels" and I can synchronize and edit all three file containers in parallel under Windows 10. So no files are corrupt or damaged. I tried this with my Mac Mini (Macmini 8,1) and MacBook Pro (2019) (both with Intel chip).

Unfortunately I can't try in safe mode because the following error message appears: kext load failed: -603946990, mount_macfuse: the file system is not available (255).

Cheers


Nov 17, 2022 5:18 PM in response to viktorfromschaffhausen

Hello viktorfromschaffhausen,


Thanks for that info and for choosing the Apple Support Communities. If we understand correctly, you are having an issue with accessing some encrypted info on your Mac. First, did you use Disk Utility to encrypt this info: Encrypt and protect a storage device with a password in Disk Utility on Mac - Apple Support? We ask this so we know if this was done with an Apple tool, or a 3rd party.


Can you test this in safe mode How to use safe mode on your Mac - Apple Support and test for the same issue? This will help isolate further.


If you are still having this issue, please provide more details about your situation so we can determine next steps.


Cheers!



Nov 19, 2022 12:03 PM in response to viktorfromschaffhausen

I realize it is a long shot, but you should never overlook something simple. I find that Windows is able to overlook and get past things which may not be 100%, but macOS tends to get hung up with anything unexpected. It still may provide a clue to what is going on with macOS if Disk Utility is able to scan the volume, but not mount it. I have seen macOS not be able to read HFS+ volumes before, yet sometimes running another app (file scanner, data recovery, etc.) will suddenly allow macOS to mount the volume, yet AFAIK the app did not make any modifications to the volume.


Most likely this is a bug with Ventura, but good luck getting Apple to do something about an odd issue with third party software. You are probably better off trying to contact the Veracrypt developers and checking their support forums. I have not seen VeraCrypt mentioned much on these forums over the years...in fact those few times I'm the one who has brought it up as an option for users.


This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Problem with MacOS Ventura (13.0) and Veracrypt Container Files

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.