OSX: Golden Gate 27.0.1 -- fully updated VeraCrypt: Latest release from 06/2026 MacFuse: 5.40 -- latest release
I try to mount the drive, but this pops up before I can (attached screenshot):
"objc[1301]: +[NSNumber initialize] may have been in progress in another thread when fork) was called.
objc[1301]: +[NSNumber initialize] may have been in progress in another thread when fork) was called.
We cannot safely call it or ignore it in the fork() child process.
Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug."
If anyone is experiencing this issue, how did you fix it?
OSX: Golden Gate 27.0.1 -- fully updated
VeraCrypt: Latest release from 06/2026
MacFuse: 5.40 -- latest release
I try to mount the drive, but this pops up before I can (attached screenshot):
"objc[1301]: +[NSNumber initialize] may have been in progress in another thread when fork) was called.
objc[1301]: +[NSNumber initialize] may have been in progress in another thread when fork) was called.
We cannot safely call it or ignore it in the fork() child process.
Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug."
If anyone is experiencing this issue, how did you fix it?
Update: Downloading Fuse-T, then downloading the Fuse-T version of VeraCrypt solved my issue and I'm able to load my drives again.