you should now be able to mount your filesystem without error (but perhaps with a little dance of joy?).this time open System Preferences / Security and Approve the macFUSE Extension.attempt once more to mount your filesystem, and you will not be surprised to get the error "System Extension Blocked".restart macOS (without enabling System Integrity Protection).
#Macfuse catalina install#
IF you STILL get the error "System Extension Blocked".attempt once more to mount your filesystem.IF you get the error "System Extension Blocked".attempt to mount your filesystem (using whatever software you have that relies on macFUSE).So the prevailing instructions coming from this thread seem to be: Is there a better way to test macfuse independent of sshfs?
I tried running /Library/Filesystems/macfuse.fs/Contents/Resources/load_macfuse echo $?, which returns 1, indicating that the macfuse cannot be loaded, which makes me believe the issue is not related to sshfs. Have you checked in to see if your problem is mentioned there? Or if it's related to the specific command-line that you are calling in sshfs? If this issue only occurs with sshfs, perhaps it might be better to raise it there instead? Is your mac managed by a company who might have locked something down? Are there any side issues mentioned in there that might apply to you?
Everyone else in this thread using macFUSE 4.2.0 on macOS 11.5 seems to find the reboot fixes their issue, so we need to find out what is different in your case.Īlthough no-one here says they are using sshfs, recent comments in issue #705 say that sshfs users got things working with 4.2.0 on Big Sur.