Hi Tony359,
Thanks for your message and question.
The fsutil method just shows if the operating system _in general_ uses the TRIM function or not.
The result of this is completely useless - as it returns 0 even if there is no SSD present in the system (!)
If the result is 0, it means that the operating system would send the TRIM command for the proper device (an SSD with TRIM function supported).
The question is: does the hard disk controller (and its driver) pass this command to the SSD(s) used in the system or block it?
The problem is that some hard disk controllers (and their drivers) may block the TRIM command, does not pass it to the SSD, even if it is supported.
For example, if you'd have two or more SSDs (supporting TRIM) in your system, it may be possible that TRIM may be transferred properly to one of them - but not for the other(s) if the SSDs are connected to different hard disk controllers, exactly as you can see now.
Hard Disk Sentinel checks the real usage of TRIM for each appropriate devices (one-by-one). If it displays "disabled", it means there is a problem with the hard disk controller. Usually updating the hard disk controller driver from the "Driver Zone"
(
http://www.hdsentinel.com/driverzone.php ) may help. For Marvell controllers, it is better to use "Standard AHCI Compatible controller" driver supplied with Windows - as that would really support TRIM.
If you prefer, please use Report -> Send test report to developer option now as I can check the disk controller, the current driver and may advise on the proper driver used.
Ps. the F.A.Q. page (
www.hdsentinel.com/faq.php#trim ) describes the above, as it is a very common question