I have the same issue. Alle drives, that are exFAT formatted with VeraCrypt on a Mac, are mountable. But sometimes folders and files are missing or Error -50 occurs while copying file or creating folders on the mounted drive. With Windows and VeraCrypt everything works fine for the same drives. Played a bit around and found out, that the "no mountable file systems" error occurs, if the drive is formatted with Windows and the allocation unit size for an exFAT drive is greater than 1024kb. Very weird...
Looks like an issue with MacOS Sonoma. https://discussions.apple.com/thread/255173291?sortBy=best and maybe related to this: https://sourceforge.net/p/veracrypt/discussion/technical/thread/f1596c1ad4/
Hmm. Or exFAT on Mac is broken. I will test some more without VeraCrypt encryption. Maybe it leads somewhere
Great idea. Of course I searched for the error, but there is nothing that solves the issue or find the cause. Meanwhile I copied everything to antother USB device of the same size. Also verycrypt encrypted, but with a windows system. On mounting this device on a mac os system, it states, that there is no file system that can be mounted. I begin to belive, that there is a serious problem with verycrypt on mac :-(
Great idea. Of course I searched for the error, but there is nothing that solves the issue or find the cause. Meanwhile I copied everything to antother USB device of the same size. Alos verycrypt encrypted, but with a windows system. On mounting this device on a mac os system, it states, that there is no file system that can be mounted. I begin to belive, that there is a serious problem with verycrypt on mac :-(
Hey, I've got an fully encrypted USB drive (18,2 TiB, ~16TiB used, exFAT in the encrypted part) and the following issue: Mounted in MacOS X (newest stable version of MacOS and VeraCrypt) it is not possible to create new folders and sometimes files, but not everytime. Error -50 is reported. Mounted in Windows 11 (newest stable patchlevel and newest VeraCrypt version) everything works fine. I tried the first aid from the disk utility of MacOS -> no real issues, only a folder with length 0 is detected...