"Operation not permitted: /var/folders/w6/d2xssyzx.../T/.veracrypt_aux_mnt1/control VeraCrypt::File::Open:232"

[Ant]

Is anyone else getting this too in macOS Big Sur v11.1 when mounting containers? I don't see numbers even though my containers get mounted. (Dismount/Eject)ing leaves left over in my /var... in a brand new 13" MacBook Pro (Intel i7, 2 TB SSD, 32 GB of RAM, no data migrations yet, etc.). :(

Thank you for reading and hopefully answering soon. :)

[Ant]

I also posted this issue in https://github.com/veracrypt/VeraCrypt/issues/795.

[Ant]

I still see this issue after upgrading mac OS Big Sur to v11.2 and macFUSE to v4.0.5. I noticed the long /var/ path has my exposed mounted .dmg in it. It doesn't goes away when I log out and relogin into my macOS account. Is no one else having this problem? :(

[Ant]

Still there in Big Sur v11.4 and macFUSE v4.1.2. :(

[Enigma2Illusion]

Are you using VeraCrypt 1.24 Update 8?

[Ant]

Yep! I even redownloaded and reinstalled https://launchpad.net/veracrypt/trunk/1.24-update8/+download/VeraCrypt_Legacy_1.24-Update8.dmg

[Ant]

https://www.reddit.com/r/VeraCrypt/comments/knkcje/operation_not_permitted/gstb9wv/ is having this issue too. Is anyone else having this problem too like us?

[gefion777]

I am having this problem too!

I did a brand new installation of macOS 11.3 Big Sur on my iMac 27" from 2019, then installed macFUSE 4.1.0, gave access to the system Extension by Benjamin Fleischer and at last installed VeraCrypt 1.24update8.

The error message says "Operation not permitted: /var/folders/ym/…T//.veracrypt_aux_mnt3/control VeraCrypt::File::Open::232", where "mnt1" or" mnt2" or "mnt4" may replace the "mnt3" part depending on the slot used to mount the container volume.

This error does not occur every time I try to mount a veracrypt container volume, but it occurs quite often. Usually I do the mounting from within a script app, where the main.scpt file contains the following:

tell current application
run
do shell script "/Applications/VeraCrypt.app/Contents/MacOS/VeraCrypt --slot=1 <path>/<filename>.hc"
quit
end tell</filename></path>

If I open that file main.scpt with the Script Editor and execute it there (by klicking the trianglular button), it works better than when Script Editor is closed and the script app itself is executed by beeing double clicked. Also, mounting and dismounting using the VeraCrypt app itself works better than using the script.

The same Script App was running without problems under Catalina and Mojave.

[Ant]

Quite often? Mine is 100%. I even tried a brand new 1 MB container file. :(

[Ant]

OMG! "Another recommendation, add Veracrypt to "Full Disk Access" under Settings > Security & Privacy > Full Disk Access.", from https://github.com/veracrypt/VeraCrypt/issues/795#issuecomment-856525764, worked!

[Fernando]

I can also confirm the following worked for me: "Add Veracrypt to "Full Disk Access" under Settings > Security & Privacy > Full Disk Access." also worked for me. on macOS Big Sur and latest macFUSE