Drive Health tells you the truth most "optimizers" get wrong. It reports your drives' real media type, capacity, TRIM status and the SMART data they actually expose — and it does the correct maintenance for each: ReTrim for SSDs, defragment only for confirmed spinning HDDs. It will never defragment flash, never overwrite-erase it, and never invent a fake "health %". This honesty is the whole point of the feature.
Defragmentation rearranges files into contiguous blocks so a mechanical read head doesn't have to seek across a spinning platter. An SSD has no head and no seek penalty — fragmentation simply doesn't slow it down. "Defragging" an SSD does nothing useful and does burn through a slice of the drive's finite write endurance for zero benefit. The real maintenance for flash is TRIM: telling the drive which blocks are now free so it can manage wear and keep writes fast. BRUTAL exposes that as ReTrim, never defrag.
Behind the scenes, each drive is classified from Windows' own storage data: MSFT_PhysicalDisk for media type and bus, MSFT_Partition to map a drive letter to its physical disk. BRUTAL will only defragment a drive that is provably an internal spinning HDD — confirmed HDD media, on an internal bus (SATA/ATA/SAS/SCSI), not removable, not a RAID or Storage Spaces virtual volume, with a real disk mapping. Anything ambiguous — USB enclosures, NVMe, persistent memory, unknown media — fails safe to do not defrag. Even the underlying optimize routine refuses a defrag request on non-HDD media, as defense in depth beyond the disabled button.
fsutil behavior query DisableDeleteNotify), shown on flash drives.Get-StorageReliabilityCounter and only the fields your drive actually reports are shown. Many consumer drives expose only a subset; BRUTAL displays what's there and never synthesizes a number.fsutil, defrag.exe) — no kernel driver, no firmware tampering, no custom move-file engine. An HDD defrag can take a long time; you can navigate away to cancel it.The page includes a standing "SSD Health & Truth" panel listing the bad advice common optimizers still push — and that BRUTAL will not do:
To actually reclaim space rather than maintain the drive's mechanics, see the Disk Cleaner and Disk Analyzer.
Why won't BRUTAL let me defragment my SSD?
Because it would be pointless and harmful. SSDs have no read head, so fragmentation doesn't slow them down, and rewriting blocks just consumes write endurance. The correct SSD maintenance is TRIM, which BRUTAL offers as ReTrim. Defragment is enabled only for confirmed spinning HDDs.
How does it know my drive is an SSD or an HDD?
It reads Windows' own storage data (MSFT_PhysicalDisk media type and bus, MSFT_Partition for the disk mapping). It only defragments a drive proven to be an internal HDD on a SATA/ATA/SAS/SCSI bus; anything ambiguous — NVMe, USB, RAID, Storage Spaces, unknown media — fails safe to no-defrag.
What is ReTrim and is it safe to run?
ReTrim re-issues the TRIM command, telling your SSD which blocks are free so it can keep writes fast and manage wear. It's the proper flash maintenance, runs quickly via the in-box Windows defrag.exe /L, and is safe — it runs without a confirmation prompt.
Why doesn't it show a single 'drive health percentage'?
Because no honest source for one exists on most consumer drives. BRUTAL displays only the SMART fields your drive actually reports (temperature, wear %, power-on hours, error counts) and refuses to synthesize a made-up health score.