You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Enable NTFS Write support on Mac OS X El Capitan

In Mac OS X Yosemite I could read and write to NTFS partitions starting the following settings:


1. OSXFuse

2. NTFS-3G

3. Fuse-Wait.


After upgrading to the El Capitan I'm not able to write to NTFS. Is there any solution? Because I tried to reinstall the software and NTFS-3G does not install properly.

MacBook Pro with Retina display, OS X El Capitan (10.11)

Posted on Oct 7, 2015 9:54 AM

Reply
Question marked as Top-ranking reply

Posted on Oct 11, 2015 8:31 PM

André Hottër wrote:


I can not understand Apple such a simple function nowadays is to store data in an HD generates so much head and cost of pain for us users!

There is no other puglin free to install?

Apple has its own file system format. Use that and there isn't any pain. If you need to use the drive on a Windows machine, then you have to deal with the cost and pain.

96 replies

Jun 5, 2016 1:47 PM in response to IMJoseAngel

You brought up the fact that OS X is UNIX certified, alluding that supporting NTFS is somehow required by the certification and is therefore safe, effective, without threat of data loss. UNIX does not require support for any specific file system, especially the half-baked, proprietary NTFS.

You even tried to reinforce your false appeal to authority:

This is not an Apple matter. This is Linux/Unix basics

The thing is that Apple gives support just to NTFS (read-only). This doesn't mean you can't to mount it as RW as I do daily and without any issues from one since one year now. Is just a simple recomendation from a humble user. Leave people take their own decissions and do their own tests to find that is a secure way to work with NTFS.

That's great that it works for you. But, you should let people know that the method is unsupported, and being that it is unsupported, others have reported complete data loss.

Jun 5, 2016 2:02 PM in response to Barney-15E

Sorry, but I referred to the Unix kernel supporting NTFS as defined by Apple. For me Unix or Linux is the Kernel and if NTFS is supported, is supported. What is clear for me is that this was the first and the last time I try to help in this forum. Thanks for your way of keeping the knowledge (Good or bad, independently of your criteria).


Good bye guys

Jun 5, 2016 2:25 PM in response to IMJoseAngel

Unix and Linux are not the same thing. Linux was independently written as a Unix clone. They look much alike, and use many of the same commands, but they are not the same.


Just as Microsoft has no support of any kind for Apple's HFS+ (Mac OS Extended), which it can neither write or read, Apple has no official write support for NTFS. Both are proprietary formats that neither has ever licensed to anyone. As such, no one but Apple and Microsoft know exactly how to safely write to their respective formats.


As I wrote earlier in this same topic, both NTFS and Apple's HFS are proprietary. Those solutions that exist were figured out on their own by the companies who make them. Such as Paragon's apps to write NTFS from a Mac, or their sister product that allows Windows users to read from and write to a Mac drive. In other words, neither is 100% compatible with either architecture. What they offer works, but not necessarily perfectly.


But either Paragon's or Tuxera's offerings are a billion times safer to use than an unsupported and undocumented Terminal hack.

Sep 5, 2016 9:47 AM in response to JOFORUP

More reasons not to migrate to Mac OS and more reasons to press regulators to get Apple to start unbundling the hidden muck-ups of their hardware and operating systems.

What hidden muck-ups? That NTFS access came along with the BSD Unix base OS X was built over. Perhaps regulators should go after all of those people who contribute their time for free to the open source BSD Unix code? And hey! Why stop there. They should go after all of that hidden and undocumented stuff in Windows, too. It only takes a few minutes online to find hundreds of things you can do with Windows that aren't officially documented anywhere on Microsoft's site.

Still a great schoolchildren platform though.

I see. Still stuck in the incredibly childish platform war mentality. If a computer does what you need it to do, it's a good computer. But I guess I can still use those grade school apps on my Mac to get work done. You know, useless stuff for kids like the Adobe CC suite, Microsoft Office, Quark XPress, etc.

Sep 5, 2016 3:01 PM in response to Csound1

"You will be better served by using Windows, which never has problems"

Ahhh, reminds me of my former Systems Support Analysts' pasquinade comments about Micro(expletive) products, those numerous, chronic deleterious, nocuous (read: corporate disasters) episodes before finally listening to an in-law and migrating to a more productive, far more stable platform (Apple OS).


Hilarious ... "Windows...(never having) problems"😁😁😁

Sep 5, 2016 6:51 PM in response to DRailroad

I have nothing to do with Windows, nor Microsoft and although I use them at work and occasionally at home I have limited liking for their platform. I love Visual Studio IDE, as it is on par if not better than X-code. Old backup NTSF drives work in Windows, far from seamlessly, but they work and Microsoft support has been helpful to resolve known issues. I am really disappointed that the responses from AAPL are "sorry, you have to live with inconvenience". It is sad that a Unix based platform is restricted not because of incompetence or licensing, but because this way the Apple products are kept intact and customer is reminded to stay away from competitive products. If AAPL products are so great, why are they afraid that competition from an unsupported will encroach on their turf? Makes me question the legendary reliability of Mac OS. Second thing I do not like is the bundling of closed system components and the resulting limited system inter-operability. Excuses that NTSF is unstable and has bugs are lame and of bad taste, and really not in the DNA of Apple. If they are, then too bad, maybe a sign to rethink the value of the company. No this smells like a cheap competition barrier and adds development cost to port older systems. I have a fix, but it entails development costs and weakens my argument to migrate to add Mac OS to enterprise ecosystem.


Now add to this the recent tax blow-up again in the context of unfair competition and prior war with Google and Samsun, I really question what AAPL is doing. This is not a criticism, rather an honest reflection of an observer. AAPL may take it or ignore it, but I would seriously reconsider investment plans.

Sep 28, 2016 8:14 AM in response to viniciusf

Well, NTFS writing support has been removed from El Capitan os and later, to enable that u need a Third-Party Drivers which ve some as free and others r paid, the best among them is :

  1. Paragon NTFS for Mac which costs 19.95$
  2. Tuxera NTFS for Mac which costs 31$


but better formatting ur external drives with exFAT, ensuring they work well on both Windows and Mac OS X without any extra work. if you must write to an NTFS drive, one of the paid, third-party drivers will be the best-performing, least-effort option.

Enable NTFS Write support on Mac OS X El Capitan

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.