VeraCrypt on MacOS 15 Sequoia

Open source disk encryption with strong security for the Paranoid

Brought to you by: idrassi

VeraCrypt on MacOS 15 Sequoia

Forum: General Discussion

Creator: Sergei Zuyev

Created: 2024-09-19

Updated: 2024-09-30

Sergei Zuyev - 2024-09-19

Has anyone tested if VeraCrypt works on the latest MacOS Sequoia 15.0?
Thanks!

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ted Poe - 2024-09-21

i just tried it and it reports an issue using MacFUSE. More later if i find anything.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Ted Poe - 2024-09-21
  
  MacFUSE - unsupported operating system.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Mounir IDRASSI - 2024-09-21

I have just installed macOS Sequoia on an Apple M1 machine and VeraCrypt 1.26.14 works correctly with FUSE-T. (FUSE-T is recommended for Apple Silicon due to issues affecting the installation of macFUSE on these machines.)

@tedpoe: macFUSE 4.8.0, which was released in June, added support for macOS Sequoia, so it looks like you are using an old version. As I mentioned above, if you are using an Apple Silicon machine (M1/M2/M3), a better alternative is to use FUSE-T and install the FUSE-T version of VeraCrypt.

👍
1

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Peter R - 2024-09-22

This is not working on macos sequoia for me with Fuse-T and veracrypt 1.2614. I have two macs - one with macos 14 and one wiht macos 15. I can open my file on macos 14 but not on macos 15. The error is the old hdiutils error. My file is not corrupted and have run the diskutils check.
I would appreciate any support in getting this working. It is a hassle to role back my macos software to be able to get veracrypt to work.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Peter R - 2024-09-22

I have tried restoring volume header but makes no difference to the error. Still no problem mounting the file on sonoma

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ted Poe - 2024-09-22

Excellent. Thank you. My apologies. I should have included that i was running VeraCrypt 1.26.14 and macFUSE 4.8.0, but both from brew. I've now installed the recommended fuse-t (https://github.com/macos-fuse-t/fuse-t) as i'm running an M2 machine. The brew package for VC 1.26.14 relies on and installs the macFUSE 4.8.0 nonetheless. I went to the VC website (https://www.veracrypt.fr/en/Downloads.html) and installed the fuse-t-compatible version of VC and everything works properly again. Thank you very much for the guidance.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

La Chica10 - 2024-09-23

Both macFUSE 4.8 and Fuse-T with veracrypt 1.2614 has the mounting error "hdutil: attach failed - no mountable file systems" on a M1 machine with OS 15 Sequoia

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Mounir IDRASSI - 2024-09-23

@dvorak123: The error message indicates that the filesystem of your volume is not supported by macOS. What filesystem do you use for this volume?
If you upgraded to Sequoia from a previous macOS version, ensure that any third-party product for non-native filesystems is also upgraded to ensure that it is working properly.
Another possibility is that the volume has been corrupted somehow, but this cannot be caused by the upgrade to Sequoia.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- La Chica10 - 2024-09-23
  
  The filesystem of the volume still works in both macOS 14 and windows, so it's not corrupted.
  
  For some reason it is not recognized in OS 15. I know a fix is to create a new volume in OS 15 and copy the contents from the old one, but this doesn't seem like a sustainable fix when having too many old volumes.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Peter R - 2024-09-23

Thanks for the assistance.
There must be something about sequoia reading the old encrypted container file.
I went back to my macos sonoma computer and created a new encrypted container and mounted the old container that sequoia won't read.
I then copied the data from the old container to the new container.
Sequoia will open the new container but not the old one which will open on sonoma.
Not sure what it about sequoia and my old container but it is fixed.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Sergei Zuyev - 2024-09-23
  
  You can hardly call this a fix. I think it is supposed to be read by all systems where VC is intalled...
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Peter R - 2024-09-24

I am not sure what the issue was with old container. It was originally created on a windows machine about five years ago. Perhaps something has changed over that period. It is a fix for me to recreate another container through macos which will work in this situation and work also across windows and mac computers.
I appreciate all the work the maintainers of this software must put in to keep it going across a number of platforms.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Sergei Zuyev - 2024-09-24
  
  Of course, we all do!
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Mounir IDRASSI - 2024-09-30

For the record, there is indeed a bug in macOS Sequoia regarding exFAT volumes and disks and it is not specific to VeraCrypt. It has been reported to Apple since last year but no fix has been released: https://discussions.apple.com/thread/255188289?sortBy=rank.

So, Apple officially doesn't seem to care about this and the only solution is to create new exFAT volumes on macOS Sequoia.

Additionally, this article provides more details on the issue: https://appleinsider.com/articles/24/04/03/external-drive-support-in-macos-sonoma-is-partially-broken-and-its-probably-apples-fault . It mentions:

The implementations of the exFAT and MSDOS file systems on macOS have changed; these file systems are now provided by services running in user space instead of by kernel extensions. If an application has explicit checks or support for either the exFAT or MSDOS file systems, validate the application with those file systems and report any issues. (110421802)

So, the new exFAT implementation in macOS Sequoia is indeed buggy.

Last edit: Mounir IDRASSI 2024-11-24

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Sergei Zuyev - 2024-09-30

Just for records, I have upgraded to Sequoia and veracrypt worked fine. An exFAT disk created in the precious MacOS10.14 was mounted fine. Thanks a lot for your efforts!

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.