Greetings all! I've just come across an anomaly that I've never really noticed (wasn't really looking for) before. My check for operational TRIM on an SSD under Windows has always included the FSUTIL directive to make sure it's active (W8 does a good job of that by itself) and a run of the li'l app called TrimCheck. When things were under control, TrimCheck always showed an active TRIM on my OS partition. Just recently I built a 2-partition SSD (for bandwidth testing) and ran the check on both partitions. The OS partition is actively TRIMmed just fine but TRIM is inactive on the 2nd partition according to TrimCheck. Can someone verify this for me, and if it's so, is this the case with W8.1.1 (W7?) and TRIM? Thanks for any help!
I do not have ssd in my windows systems, but I think that your situation is the normal way windows "trims". In windows 8.x it should be taken care by the defrag? scheduler. Or you can create an idle scheduler that sends trim (retrim) commands on your partitions http://technet.microsoft.com/en-us/library/hh848675.aspx Panagiotis
Indeed the reTRIM command trimmed the data just fine, but everywhere I've read talks about Windows SSD TRIM processing on a DISK basis, not a partition basis. I'll see if I can find anywhere that talks about it. Thanks, Panagiotis
Trim is enabled on a disk basis but the trim command(s) are performed on a volume basis. This behavior is reported usually with a second ssd but in all answers everyone responds "Trim is enabled so is working fine". A good example that not everything we read on the net is true. Panagiotis
