A reminder that modern SSDs are rated for literally Petabytes of write operations; a couple extra defrags will shorten their lifetime, but not by enough to actually matter.
EDIT to add: while true, beware if you are running an SSD without DRAM cache or otherwise a cheap knock-off no-name brand SSD. Those shouldn't be trusted anyways, and under increased load... it's better off just not using them at all to be honest. Look up reviews for the brand if you're not sure.)
This bug is basically down to Win 10 mis-reading the SSD as a regular drive (normally it will run TRIM on an SSD if you select it for "Optimization" which is what the Defrag util is now classified as - it will defrag spinny disks, and run TRIM on SSDs, at least when they are detected correctly).
To fix this bug, get Windows to reassess what type of drive you have (apparently Windows detects SSDs by running a benchmark (!!) on them).
Launch an elevated Command Prompt (Hold Win + X then press A; or alternatively, search cmd or powershell, right-click > run as admin) then:
(formal should run all assessments, diskformal runs all for the disk, but hey, Windows gotta Windows, I'd just run both to be sure).
However note winsat assessment supposedly may not work with drives having multiple partitions (?? - Pressing X to doubt here).
Someone also mentioned using
fsutil behavior set DisableDeleteNotify 0
which should be set this way (to 0 instead of 1) for SSDs to enable TRIM, so make sure that's set correctly (set 0). To check, run
fsutil behavior query DisableDeleteNotify
(info on disabledeletenotify 0 / TRIM here)https://computingondemand.com/fix-windows-recognizing-ssd-as-hard-disk-drive/
(goes into the details of what winsat and its arguments and switches do)