Other PSA: You probably don't need the TRIM Enabler app.

[Wowfunhappy]

Because I now run a website with a collection of legacy OS X software, people keep sending me emails to tell me about Trim Enabler. I received five separate emails about it in just the past couple of weeks. I do know about Trim Enabler and I appreciate the company's legacy OS X support, but I don't think pretty much anyone should use it.

TRIM is a feature which improves the performance of SSDs. On macOS / OS X, TRIM is disabled by default on non-Apple SSDs, so anyone using a third party SSD on OS X should absolutely enable it manually. I just don't think you need to use the TRIM Enabler app.

As best as I can tell, all the TRIM Enabler app does is either apply a well-documented patch to the IOAHCIBlockStorage kernel extension (on OS X 10.6.8 – 10.9) or run trimforce enable (on OS X 10.10+). In exchange, it costs $10. I completely support developers charging for quality software, including simple software which focuses on one thing and does it well—but this feels like a bit much.

I've attached a script I compiled many years ago which will enable TRIM on non-Apple SSDs on any version of OS X from 10.6.8 onward. Extract and double click.

Note: You should make a time machine backup before running this, and I am not responsible for data loss. That said, this is not my patch; this process has been well-documented in the Mac community for well over a decade now, and if it was causing widespread problems we'd have heard about it.

Secondary PSA: AppleRAID Doesn't Support TRIM.​

AppleRAID—that is, RAID arrays created in Disk Utility—do not support TRIM. You can use an app like TRIM Enabler to make Disk Utility say that TRIM is enabled, and the OS will even attempt to issue TRIM commands, but they won't work. You will see lines like this in the system Console:

8/1/25 5:58:02.000 PM kernel[0]: CoreStoragePhysical::issueUnmap: unmap returned e00002c7

This is the OS attempting to issue TRIM commands, and failing.

My attached script will automatically exit without making any changes if it detects AppleRAID is in use. (By contrast, TRIM Enabler will enable TRIM anyway and proceed to claim that everything is working even though it is obviously not...)

If anyone knows a solution to this, please share. I'm currently using a RAID 0 array of two Samsung Evo SSDs (because no one makes SATA SSDs larger than 4 TB and I needed space) and the lack of TRIM is nagging at me.

Tertiary PSA: This doesn't open any "security holes".​

The Ars Technica article I linked above has a paragraph at the end:

Indeed, if you’re adding a third-party SSD to a Mac, you won’t be able to enable TRIM support without loading some old and insecure kernel extensions—don’t do this, because although TRIM makes a difference in reducing write amplification and extending the life and performance of an SSD, it’s not worth the barn-sized security holes you have to open up in order to get it.

I'm not sure what they're referring to here, but I think they're just confused. There is no version of macOS in which you need to disable a security feature to enable TRIM. The kext patching method which would otherwise invalidate code signatures (and anger SIP) is only used on versions of macOS which don't enforce code signatures for kexts anyway.