By that reasoning, you might also suggest another arguably paid option – Windows itself, which employs NTFS as the default filesystem.
I’m simply being facetious, excusé moi.
A note on blacklisting ntfs3 in favour of ntfs-3g:
The ntfs3 kernel driver can appear to fail if damage; or, rather, an indicator of damage; to an NTFS formatted drive is found (commonly referred to as a dirty bit).
ntfs-3g, however, ignores this and mounts the NTFS partition, regardless.
Important to note is that the NTFS filesystem may still be damaged, as ntfs-3g allows you to blissfully continue using your drive.
If an error does exist, it should/must be corrected within a Windows environment using chkdsk, which can achieved by launching an administrative command prompt and using the command:
chkdsk /f x:
- x: denotes the drive letter of the disk as it appears in Windows.
If a Windows installation is not available, chkdsk may also be run from a bootable Windows installer, or the downloadable Hiren’s BootCD PE; as one possible example.
I hope this additional information is helpful.
Cheers.