- Fix an issue where large and highly fragmented files might not be readable (#7). - Internal improvements in preparation for changes coming in macOS 27.

- Hash tree directories are now fully supported. In ext3 or ext4 volumes, a file lookup can use the hash tree to make an initial lookup faster, especially in a directory containing many items. - Various other performance improvements. - The `inline_data` feature, where a volume can have small files or directories with its data embedded in the inode, is now supported for reading. - ExtendFS now supports reading files whose name is not encoded in UTF-8. However, note that while ExtendFS may support this, many parts of macOS may not support file names that aren't valid UTF-8. For example, such files might not appear in the Finder or other user-facing programs at all. However, you should be able to read them via terminal commands. - Fix an issue where large files on an ext2 volume might not be readable. - Fix an issue on volumes with the `csum_seed` feature enabled where file reads might fail or directories might incorrectly appear to be empty. - Fix an issue where reads on a sparse file might fail with an input/output error. - ext2, ext3, and ext4 volumes mounted by ExtendFS are now marked as "true" read-only volumes. Among other improvements, this means that options such as creating new folders and deleting files (which did not do anything if selected) no longer appear in the Finder. This fix requires both updating ExtendFS and updating to macOS 26.5 or later.

- Fix an issue where sections of some files might not be readable.

- Fix a crash that could rarely occur in a background process. - Fix an issue where a GUI window might open whenever a disk is mounted.

- The interface that tells you how to enable the file system extension is now translated in additional languages: Spanish, French, and Chinese (Simplified). Feedback is appreciated. - Fix an issue where a disk with an error policy set to "mount as read-only" may not mount at all if it has errors.

- Fix an issue where volumes that have features enabled which are incompatible with ExtendFS might mount and show inconsistent data. - The casefold feature is now supported. Directories which have the casefold flag marked by a Linux machine will use case-insensitive lookups for its contents. - A volume marked as needing recovery can now try to mount, but it may show a warning that the disk needs repair. ExtendFS cannot currently repair disks; if you see this warning, use fsck on a Linux machine to repair the disk. - Checksums are now verified on a few data structures. There are plans to expand this in the future. - Some additional ext4 features are supported. Check the README file in the GitHub repo for the current full supported feature list. - Fix an issue where reviews might be requested sooner than expected.

- Fix an issue where a process might not exit for longer than expected if a disk is unmounted uncleanly. - Fix an issue where a process might exit too soon if an unmount is blocked.

- Fix missing limits for file size and extended attribute values, and fix other minor errors with volume metadata reporting. - The app may now ask for a rating after enabling the extension if your settings allow. If you choose to do so, it is appreciated.

IMPORTANT: In some cases, after performing this update, you might need to restart your computer and re-approve the file system extension in System Settings. Most ExtendFS updates shouldn't require you to do all of this, but unfortunately one of the changes below might need you to re-approve it and/or restart your device. If you encounter problems after updating, try that first. - More types of ext2/3/4 volumes, such as those marked as a /var partition on a Linux install, can be automounted. - Fix an issue where information the last block group on the volume might not be fetched, which can lead to some volumes not mounting, some files not appearing, and other issues. - Try to make it more difficult for the app to be updated or deleted while it is being used to mount a disk, which would have caused the disk to abruptly unmount. In addition, after an App Store update, automatically try to remount disks that were unmounted during this process (this is currently only supported for disk images). Unfortunately the update from 1.0.0 to 1.0.1 won't have these improvements, but this change may make future updates smoother. - Improve performance in cases where file data maps are requested at item lookup time. - Fix potential issues and improve performance when working with sparse files in an ext2 or ext3 volume. - Improve error handling in various areas. - Remove some unnecessary code.