BOTH Speccy v1.32 AND Defraggler v2.22 Incorrectly Report HDD as an SSD in Speccy Bug Reporting Posted June 22, 2018 The HDD I refer to in my original post has a highly fragmented C: drive (42%), and needs the robust defrag accorded to HDDs. ADDITIONAL INFO: Defraggler incorrectly reports all 3 NTFS partitions on this HDD as SSD - "HOWEVER", it correctly reports the FAT32 OEM Tools partition as HDD. (That's right, 1 drive with 4 partitions, with 3 being reported incorrectly as SSD, and 1 partition - the FAT32 one - reported correctly as HDD). - Maybe this info may help Piriform devs get some insight into the bug. With 42% fragmentation, I need the robust defrag accorded to HDDs. But I don't trust Defraggler to do the job right after misidentifying the drive as SSD. Why dismiss a Warning about SSD defragging, take the time to defrag/optimize/whatever, and NOT get a proper HDD defrag? I (and other users) can't trust Defraggler due to this this bug. Please, Piriform, reply with accurately researched answers to these questions (not mere suppositions): Can I use Defraggler v2.22 to robustly defrag an improperly ID'd "SSD"? Is there some Registry hack, Defraggler .ini file, or other way to change the incorrect SSD flag to HDD? If not, is there an older version of Defraggler that omits the HDD/SSD detection (i.e. no offer of Optimize vs Defrag)? I cannot be the only user of Defraggler who wants answers to these questions. My suggestion - as an engineer - is this: If the bug cannot be banished to the point that Defraggler can, with a VERY high degree of precision and consistency, differentiate between HDDs and SSDs, automatic drive detection determination of defrag algorithms MUST be removed. Present the user with a prominent WARNING regarding SSD defragging; give the user info as to how to determine how to ID their drive type; and make the user MANUALLY select "Optimize SSD" or "Defrag HDD" before proceeding - with a restatement of the danger of defragging an SSD. Do NOT take away user choice when your software relies on faulty drive detection algorithms. I'll have to use another Defrag program if this issue isn't responded to - in fact I'm looking at others RIGHT NOW, because I have a 42% fragmentation C: drive that needs attention. I loved Defraggler for years (I particularly appreciate the SETTINGS -> OPTIONS -> ADVANCED checkbox to "Stop VSS when defragmenting NTFS volume"). That "Turn Off VSS" made your product superior to 2 other defraggers I used that caused MASSIVE numbers of Restore Point creations during defrag (once exceeding 30GB), that actually made the drive highly fragmented with the new Restore Points being written as the drive was being defragged. I came for the "Turn Off VSS", and stayed for the excellent performance of Defraggler otherwise - but I may now be forced to leave. What a pity, if Piriform can't fix this. My drive's health is more important than my love of Piriform software. (And remember, Speccy is ALSO misidentifying this HDD as an SSD). Sorry if this is considered a TL;DR rant. I'm not Ranting - I'm Pleading: Piriform, please fix this Really Bad bug.