Prototype

Its because the drive is a SMR (Shingled Magnetic Recording) type of drive and they use the same TRIM command as SSDs do use for a different purpose. Defraggler and a few other programs incorrectly see this as an SSD, when it is in fact used (on SMR drives such as yours) for "prompting" the drive to reclaim the non SMR parts of the drive that act as a faster cache area before they are written to the SMR area that make up most of the drive. So don't worry, you can defragment it just fine with Defraggler or a better defragmenter.

So why isn't there any support? Older defrag programs from years ago such as UltraDefrag do appear to support such drives years ago (I have not extensively tested this but it appeared to work fine) and programmatically I would of thought it would be relatively simple to implement. Atleast if for some strange reason you chose not to support such drives the program should fail gracefully and bring up a prompt informing the user that it can't defrag such drives instead of just falling over or hanging?

When analysing any NTFS drive formatted with cluster sizes of 128KB or larger defraggler either crashes or the analysis gets stuck on starting. Other file systems with large clusters of 128K such as ExFAT do work as expected. I know its unusual to have clusters this large but I need them for a particular backup program that when creating huge backup files has a tendency to have massive fragmentation issues and huge clusters greatly reduces this problem.