Just heard of SSD Trim recently. but I have what may be conflicting data. Probably not, but I need clarification
When I go to optimize, I get this
It's set for "Weekly", but the OS partition hasn't been trimmed for 14 days, The E:\ partition for 24 days, and the encrypted N:\ partition "optimization not available" (I'd like to change that if possible)
It is normal it is set to weekly and windows will do a trim command when it is necessary and not always every week. You can't do a trim command on the n: partition and it won't do anything, it doesn't need it.
@kitpzyxmsir -
The way that you have it is just fine. Never worked right to begin with. The SSD drive electronics will do it when required, in any case.
You can always force a TRIM manually.
What device is "N", where is it "not possible"?
When Optimise is set for Weekly, Windows retrims SSDs every 30 days.
See my ditty SSD trim, defrag - TenForums
Denis
You are confusing trim with retrim. When trim is enabled, Windows always sends the trim command to the hardware each time when it sees that a block no longer contains valid data. But each time when the hardware receives a trim command, it stores the command in a queue. Once in a while the command gets discarded from this queue so the command never gets executed by the controller chip. Windows solves this problem automatically, by sending the commands again. That's what's called a retrim. Default is after 30 days because, there's no need to do it more frequently, at least not under any normal usage conditions.
Further, a defrag can also be a partial defrag in the particular sense that, besides skipping contiguous blocks of 64MB or larger, a defrag session can be interrupted after a certain period of time, as the SSD optimization task aims to avoid defragging the SSD more heavily than really should be needed (part of why it's called an optimization). Excessively defragging an SSD causes too much wear and tear on the NAND chips of the SSD, but excessive fragmentation on an SSD hurts performance too much, and, in addition, the number of fragments that NTFS can support is still limited (despite that this maximum number is actually pretty large). During the (weekly by default) scheduled optimization task, Windows analyzes how severe the fragmentaion on the SSD is, and doesn't start to defrag the SSD before it sees that the severity level has exceeded a certain threshold.
I don't use encryption. I cannot tell you why your partition cannot have the trim or the defragmentation.
I have an encrypted vhdx virtual disk , I have mounted from the internal SSD and after from a Flash Drive USB. In both cases I can defragment them. I would like to know why I have not trim when it has been mounted from the SSD.
If your partition is on an external HDD/SSD its SATA/USB adapter or the enclosure must support the UASP to have trim.
Last edited by itsme1; 28 Feb 2023 at 04:08.
It depends. With BitLocker on NTFS, that would be yes. See: https://social.technet.microsoft.com...ives-with-trim
Quote