Announcing macFUSE 5.3.1

Announcing macFUSE 5.3.1 Posted on 13 Jun 2026

Download macFUSE 5.3.1 macOS 12 or later Apple Silicon or Intel SHA-256: 84ca737f175ad451f4fb988f5e2bb37b839ea5fc3d676c58f6f670e1bffbf3ee

Use the node identifier and generation as the authoritative handle for file system items instead of the inode number. Perform FUSE_LOOKUP to get authoritative handle of directory entries returned by FUSE_READDIR

Previous releases assumed that the node identifier and inode number were identical, as is the case when using the high level libfuse API without use_ino. This change removes that shortcut and resolves macfuse/macfuse#1166 and macfuse/macfuse#1167.
Improve stability by fixing a bug in open file handle management
Improve performance when preparing messages sent to the file system server
Improve performance when enumerating directories by using FUSE_BATCH_FORGET

Update the kernel extension version to 5.3.1
Remove the file system item from the name cache when handling FUSE_NOTIFY_INVAL_ENTRY

This ensures that the next lookup triggers a FUSE_LOOKUP request and resolves macfuse/macfuse#1160.
Address an incompatibility with the macOS 27 SDK included in Xcode 27 beta 1

Turn MFChannelCreateWithDeviceFileDescriptor() into a weak import

This function will be removed once MFMount() supports mounting volumes using the kernel backend. Check that the symbol is available before calling it.
Please note that parts of the MFMount.framework API may still change in future releases.

Fix a path deadlock in the high level API when using VNOP_MONITOR. This adds the missing free_path() call in fuse_lib_monitor() and resolves macfuse/macfuse#1168.

Fix a path deadlock in the high level API when using VNOP_MONITOR. This adds the missing free_path() call in fuse_lib_monitor() and resolves macfuse/macfuse#1168.