Extend native file handling in OS X (was OSXFUSE)

FUSE for macOS

FUSE 3.8.0

  -  6.6 MB  -  Open Source

Sometimes latest versions of the software can cause issues when installed on older devices or devices running an older version of the operating system.

Software makers usually fix these issues but it can take them some time. What you can do in the meantime is to download and install an older version of FUSE 3.8.0.


For those interested in downloading the most recent release of FUSE for macOS or reading our review, simply click here.


All old versions distributed on our website are completely virus-free and available for download at no cost.


We would love to hear from you

If you have any questions or ideas that you want to share with us - head over to our Contact page and let us know. We value your feedback!

  • FUSE 3.8.0 Screenshots

    The images below have been resized. Click on them to view the screenshots in full size.

    FUSE 3.8.0 Screenshot 1
  • FUSE 3.8.0 Screenshot 2

What's new in this version:

- Add support for DEBUG and DEVELOPMENT kernels. Previous versions of the FUSE kernel extension did only support RELEASE kernels
- Add support for O_APPEND flag of open(2) when running in direct_io mode
- Add high-level support for invalidating files
- Fix file handle bug in exchangedata(2). Relying on vnode_update_identity() resulted in open file handles pointing to the wrong file after calling exchangedata(2)
- Fix "vnode reclaim in progress" kernel panic
- Purge vnode from namecache when a FUSE_NOTIFY_DELETE notification is received by the kernel extension and the file has been deleted and re-created in the meantime
- Always use standard system font for about text in FUSE preference pane

To invalidate caches for a specific path and posting a file system event notifying subscribed processes, e.g. Finder, of remote file changes, call one of the following functions:
- fuse_invalidate_path() for high-level FUSE file systems
- [GMUserFileSystem invalidateItemAtPath:error:] for Objective-C or Swift file systems

Do not post unnecessary file system events because they might trigger file system operations. Especially expensive readdir(3) calls should be avoided:
- Do not post automatic file system events if we already know that we will not be able to detect remote changes reliably. Invalidating a vnode's cached attributes essentially means that we expect the attributes to have changed in user space
- Fix readdir(3) loop when using the high level volicon module. Addresses osxfuse/osxfuse#434