Two nearly identical machines running identical software and identical VeraCrypt software. Macs running Catalina. Latest VeraCrypt update v.4. VeraCrypt continues to work normally on one machine, while on the other, the encrypted file will open using the volume window but will no longer close using the volume window. Have to restart the machine to close the encrypted file. Getting the following message in a pop up window after opening the encrypted file:
Operation not permitted
78ym6lsmrlf5yc 0000gn/T
//.veracrypt_aux_mnt1/control
Reloaded the update twice; made no difference. Even completely erased the original copy before downloading and opening a new copy. Have noticed no other differences. What's going on?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Things have been going from bad to worse on one of two macs on my network - nearly identical except for the screen size. The machine with Veracrypt issues, internet connectivity issues had stopped logging into the History Channel website today after struggling yesterday. The other mac seems to be working flawlessly with Veracrypt, History Channel, internet connectivity and everything as far as I can tell. Have run all utilities, reinstall of the current OS - have done everything except erase the HD and completely start over again. Any ideas?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When I mount the encrypted volume it creates the temporary folders just fine, but it adds an extra forward slash before .veracrypt (just like in Joe's screenshot) when it trys to open the control file. I assume that's the file that keeps track of the mounted volumes in VeraCrypt because after it mounts the volume, VeraCrypt doesn't know it did successfully.
I'm able to unmount the volume via Finder but not via VeraCrypt.
Running Mac OS Big Sur 11.0 Beta (20A5323l)
VeraCrypt 1.24-Update4
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Tim: I ended up erasing the entire HD and cloning a fresh ,good copy from a similar machine running similar software. The infected maching began acting all weird with all sorts of error codes, on top of the veracrypt malfunction. Everything is fine at the moment. Joe
Two nearly identical machines running identical software and identical VeraCrypt software. Macs running Catalina. Latest VeraCrypt update v.4. VeraCrypt continues to work normally on one machine, while on the other, the encrypted file will open using the volume window but will no longer close using the volume window. Have to restart the machine to close the encrypted file. Getting the following message in a pop up window after opening the encrypted file:
Operation not permitted
78ym6lsmrlf5yc 0000gn/T
//.veracrypt_aux_mnt1/control
Reloaded the update twice; made no difference. Even completely erased the original copy before downloading and opening a new copy. Have noticed no other differences. What's going on?
I just realized that I left out part of the error message. Posting a screen capture:
Things have been going from bad to worse on one of two macs on my network - nearly identical except for the screen size. The machine with Veracrypt issues, internet connectivity issues had stopped logging into the History Channel website today after struggling yesterday. The other mac seems to be working flawlessly with Veracrypt, History Channel, internet connectivity and everything as far as I can tell. Have run all utilities, reinstall of the current OS - have done everything except erase the HD and completely start over again. Any ideas?
I'm getting the same error message as Joe.
When I mount the encrypted volume it creates the temporary folders just fine, but it adds an extra forward slash before .veracrypt (just like in Joe's screenshot) when it trys to open the control file. I assume that's the file that keeps track of the mounted volumes in VeraCrypt because after it mounts the volume, VeraCrypt doesn't know it did successfully.
I'm able to unmount the volume via Finder but not via VeraCrypt.
Running Mac OS Big Sur 11.0 Beta (20A5323l)
VeraCrypt 1.24-Update4
Just submitted a ticket on it here. I assume an upvote will help it get attention?
https://sourceforge.net/p/veracrypt/tickets/365/
Tim: I ended up erasing the entire HD and cloning a fresh ,good copy from a similar machine running similar software. The infected maching began acting all weird with all sorts of error codes, on top of the veracrypt malfunction. Everything is fine at the moment. Joe