-
Notifications
You must be signed in to change notification settings - Fork 515
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
macFUSE 4.5.0 doesn't seem to work on MacOS Sonoma 14.2 #992
Comments
macFUSE 4.5.0 works fine for me on macOS 14.2. This not a general issue. The button to allow macFUSE to load should be in the section located above "Sécurité". |
Not working for me too. |
@nikolafamit I assume you are talking about an NTFS volume. Is that correct? |
Yes. |
@nikolafamit Then this is a completely different issue. macFUSE is a building block for developing file systems. You won't be able to read from or write to your NTFS volume using macFUSE alone. What you might be looking for is NTFS-3G. NTFS-3G is an implementation of the NTFS file system and it relies on macFUSE. Please know that NTFS-3G and macFUSE are independent projects. Setting up NTFS-3G to replace Apple's read-only NTFS implementation is not an easy task, especially for recent versions of macOS. If you want to try, look for a recent how-to. |
Oh, I see now. Tnx for clarification |
I just upgraded to MacOS 14.2 (14.2.1) and MacFUSE keeps working as expected. I'm using it with latest version of Cryptomator. |
Upgraded to 14.2.1 (Intel), still says that the system extension is blocked. |
I have exactly the same issue that @mably describes. |
I have exactly the same issue as well |
I have the same issue. |
Faced with the same issue when run command: mac osx Ventura 13.4.1 I try any command from this discussion and then restart mac os and then try running again: then faced with issue: but resolve it such way: |
I'm using Intel Mac with Sonoma 14.2.1. The last time I reinstalled MacFuse and restarted. After the restart, I can mount the volume. However, today I had the same problem again. I guess maybe I trusted the developer before, so I don't see the button (or whatever) to add the developer. Anyway, the fix for me is to reinstall MaFuse 4.5 AGAIN and RESTART. After that, I can mount, e.g.,
Replace |
All you guys on here seem to be computer experts. I am not. I have PCloud as my cloud back up and now it does not work correctly because of this problem with macFuse. Why can the makers of macFuse not organise a fix for this problem which a Tech idiot like myself can install with one click? I have a Mac mini M1 running Sonoma 14.2.1 Can anyone including the authors of macFuse tell me a simple way to get my iCloud working again? |
@denericdeneric pCloud uses a custom version of macFUSE. Please make sure to use the latest version of pCloud. If this does not resolve your issue, I recommend raising the issue with the pCloud team. @mably (and other with the same issue) Try running the following command in Terminal. It attempts to load the macFUSE kernel extension manually. You need administrator privileges to run the command and you will need to enter your password.
Then open the "Privacy & Security" system preferences. Is there an "Allow" button as shown on the screenshot below? |
Hi @bfleischer, I can confirm that running the command above fixed the problem on my side, thanks 👍 But I can also confirm that I don't have that "Allow" button in the "Privacy & Security" system preferences as can be seen in my original screenshot. |
I'm running macOS 14.2 as well. macfuse was installed on a previous version with brew. Brew just upgraded all packages. But there was no directory named 14... only 13 and below. And I also get this "macFUSE too old" message on mounting. After running |
If anyone else is running into this issue, I was able to fix it by disabling System Integrity Protection(SIP) on the mac.
It should prompt you to allow the extensions now. I will try enabling SIP and verify the extension still works but I'm now able to load MacFuse and NTFS drives successfully. |
I haven't tried this, but discovered a kext-less implementation (doesn't require a kernel extension) of FUSE here, that currently has 678 stars: https://github.com/macos-fuse-t/fuse-t I made a workaround myself, using Docker via OrbStack on Mac: https://github.com/jzombie/sshfs-mac-docker. Though it's a bit tricky to set up the first time, it doesn't require messing around w/ FUSE, and you can still access remote mounts via Finder / apps. |
Huge instability for me in Sonoma, so much that I have decided to remove MacFuse. Reading old HFS+Extended Macintosh CD-ROMs. Maybe I will try the above alternative. |
@bfleischer Thanks, running the terminal command (On latest Sonoma with 4.6.0) made it show up under "Details" in the Privacy settings on the Mac. It showed up as enabled, but "saving" it prompted for password and then noted a reboot was necessary. After that, MacFuse and software relying on it (such as VC) started working again :) |
Hi - So, no issues with installing 4.6 on Sonoma 14.3 however, nothing has changed for me. I was always able to read my NTFS drive from macOS and I'm still only able to read the drive after installing macfuse. I'm confused to why installing this is useful if it only enables reading (not writing) which is something I thought macOS was already capable of doing. Please let me know if I'm wrong.. my goal here is to read & write to my external NTFS drive. |
Be careful (i.e., don't use it) if you're using fuse-t on Sonoma on Apple silicon. macos-fuse-t/fuse-t#45 |
Hi @bfleischer , I have done all of this above, and I still don't have that "Allow" button in the "Privacy & Security" system preferences.
I have followed your instructions, wihout much luck |
@benoitballester if you installed via homebrew (especially on an earlier version of macOS), did you try reinstalling (which helped @TheChatty)?
|
Yes I have also tried this method, via brew, without any luck |
I'm going to close this issue since the op's problem and all non-NTFS related problems have been resolved as far as I can tell. Please open a new issue in case you are still running into problems on macOS Sonoma. |
I encounter the same error with a M1 macOS Trying to write on a FAT32 thumbstick
|
@fpaupier macOS supports FAT32 natively. No need to use macFUSE for writing on a FAT32 volume. And ...
|
Password: |
Keep getting this message:
But when I check the system preferences there is no reference to "Benjamin Fleischer":
The text was updated successfully, but these errors were encountered: