v2.5

UEFI:NTFS v2.5

This version fixes unloading of the native file system driver for some platforms/media [eed6de8c9d23ac34925014586e2b55258aaf3e3c].
This is needed because on some platforms (e.g. Intel NUCs) MBR based media may present more than one disk instance for the disk where the target bootloader resides, including some driverless disk instances, whereas we previously assumed that there could only ever be one disk instance.
We also ensure that, if UEFI:NTFS is being chainloaded, SetPathCase() will be able to perform its job regardless of whether the directory has already been opened [ee57bd9187ccacc6c85c97677774a811c2814eb8].
This release was build from GitHub Actions on Linux/Ubuntu using gcc and the latest EDK2 (https://github.com/pbatard/uefi-ntfs/actions/runs/8557379470).
The _signed binaries are the Secure Boot signed versions (In a Secure Boot enabled environment, these should be used with the _signed versions of the NTFS drivers found here)
Note that the 32-bit ARM version is not Secure Boot signed, as Microsoft's current policies require additional validation for the signing of 32-bit ARM UEFI binaries.

UEFI:NTFS v2.5

This version fixes unloading of the native file system driver for some platforms/media [eed6de8c9d23ac34925014586e2b55258aaf3e3c].
This is needed because on some platforms (e.g. Intel NUCs) MBR based media may present more than one disk instance for the disk where the target bootloader resides, including some driverless disk instances, whereas we previously assumed that there could only ever be one disk instance.
We also ensure that, if UEFI:NTFS is being chainloaded, SetPathCase() will be able to perform its job regardless of whether the directory has already been opened [ee57bd9187ccacc6c85c97677774a811c2814eb8].
This release was build from GitHub Actions on Linux/Ubuntu using gcc and the latest EDK2 (https://github.com/pbatard/uefi-ntfs/actions/runs/8557379470).
The _signed binaries are the Secure Boot signed versions (In a Secure Boot enabled environment, these should be used with the _signed versions of the NTFS drivers found here)
Note that the 32-bit ARM version is not Secure Boot signed, as Microsoft's current policies require additional validation for the signing of 32-bit ARM UEFI binaries.

uefi-ntfs