Hi Munir,
I know this is not very helpful, but macFUSE 4.2.0 and 4.2.1 are running fine for me on macOS 11 and macOS 12. Apple completely re-wrote the kernel extension manager in macOS 11. This has caused some issues before, but as far as I know those issues have been resolved in the 11.3 update.
There are a few users that are still reporting issues loading the kernel extension. I recommend raising these issues with Apple. The macFUSE kernel extension is signed correctly and notarized. In all remaining cases (after the macOS 11.3 update) the loading issues were caused by something local and affected other third-party kernel extensions as well.
For example, there is an old version of the OpenZFS kernel extension (spl.kext) that will prevent all other third-party kernel extension from loading. I've seen cases where permissions of macOS system folders were incorrect and prevented third-party kernel extensions from loading. In one or two cases the database used by macOS to store user consent was damaged.
The first thing to try is triggering the built-in panic-medic. To do this run
kmutil trigger-panic-medic --volume-root /Volumes/<YourVolumeName>
in the recovery environment.
Did you try loading the macFUSE kernel extension on a clean install of macOS 11 and/or macOS 12?
Please also check the logs in Console.app when trying to load the macFUSE kernel extension. The logs usually contains a lot more useful information than just the error code.
Best regards,
Benjamin
I tried 4.2.0 on Big Sur 11.5.1. Now I'm stuck in a loop where macFuse mount will bring up popup that I need to approve macfuse kernel extension<Screenshot 2021-09-30 at 23.47.19.png>