Separate names with a comma.
Discussion in 'macOS High Sierra (10.13)' started by MIKX, Apr 28, 2018.
Hi, just curious.
Trimforce works well for me.
One costs money, one doesn't!
Every third party app uses trimforce to enable trim, so the result will be the same.
I go with trimforce, as that is Official Apple option.
But, never had issues with Trim Enabler in the past.
I've always just used the terminal command. They do the same thing, one just uses a GUI.
Yea I think trimforce was added in 10.11.4 if memory serves. Before that and without a trim enabler program it was kind of a drawn out fix to enable.
IMO, TE is mainly for proving other functions nowadays. If you only want to enable TRIM, use terminal command make more sense.
Yesterday, as an experiment I turned off Trim in Trim Enabler 4.1.2 shut down my cMP, removed all drives except my SanDisk SDSSDA480G ( Sierra 10.12.6 ) and my Samsung 960 EVO NVMe ( EFI-bootable ) ( Sierra 10.12.6 ).
Shut down again and did a cold start.
After the startup I was surprised to see that both of the above drives showed as Trim = Yes in Sys Info..
Native, built in Trim !
I have never run the Terminal Trimforce command.
EDIT : I wonder if there would be any conflicts in running Trim Enabler with SSDs that have native Trim support ? Anyone have any thoughts on this?
^^^^^AFAIK, neither of those drives are natively TRIM supported by the Mac OS. And, IIRC, Sandisk uses the Sandforce controller, and the Sandforce controller doesn't like TRIM. I believe that TRIM was still enabled when you restarted.