Make Windows 10 realize USB 3.0 connected drive is an SSD, not an HDD.

I have an SSD inside an Inateck FE2006 case, and Windows recognizes it fine. *But* when I look under drive optimization, it says it's an HDD and not an SSD (and will thereby try to defragment it instead of sending TRIM commands). Now, when I run CrystalDiskInfo, it realizes that it is an SSD, which one, that it supports TRIM, etc. - just like if it was connected via SATA 3. So the USB 3.0 to SATA 3 controller doesn't seem to generally block these things.

Now I'm wondering, is there a way to make Windows 10 [Version 10.0.14393] realize that it's talking to an SSD and not to a hard drive/make it send TRIM commands to it?

Well, I tried it (including restart), but that didn't do anything unfortunately.

Code:

winsat disk -n 4
Windows System Assessment Tool
> Running: Feature Enumeration ''
> Run Time 00:00:00.00
> Running: Storage Assessment '-n 4 -ran -read'
> Run Time 00:00:00.16
> Running: Storage Assessment '-n 4 -seq -read'
> Run Time 00:00:01.92
> Running: Storage Assessment '-n 4 -seq -write'
> Run Time 00:00:02.14
> Running: Storage Assessment '-n 4 -flush -seq'
> Run Time 00:00:00.56
> Running: Storage Assessment '-n 4 -flush -ran'
> Run Time 00:00:00.55
> Disk  Random 16.0 Read                       199.25 MB/s          7.7
> Disk  Sequential 64.0 Read                   325.79 MB/s          7.8
> Disk  Sequential 64.0 Write                  320.35 MB/s          7.8
> Average Read Time with Sequential Writes     0.233 ms          8.5
> Latency: 95th Percentile                     0.470 ms          8.7
> Latency: Maximum                             1.058 ms          8.9
> Average Read Time with Random Writes         0.233 ms          8.8
> Total Run Time 00:00:05.38

Hi,

I have an SSD inside an Inateck FE2006 case

If that case uses UAS protocol then that would explain why it doesn't support TRIM and hence treat your drive as if it were a HDD.

While you CAN defrag a SSD like you would a HDD, you really shouldn't as it just doesn't need it because latency is so low you'd hardly notice a difference.

To find out if the case supports UAS open device manager and check for an UAS entry under Storage controllers.

Cheers,

Uhh... you're confusing me a bit. I'm pretty sure UASP supports both UNMAP and direct ATA command passthrough, which could both be used to support TRIM? I mean, as far as I know UASP was pretty much made to do this. Did you mean to ask if it is not using UASP?

Hi,

Did you mean to ask if it is not using UASP?

No, I would like to know if it supports UASP for that would explain what you are experiencing.

Checked it and yes it does use UAS which does not support TRIM so Windows looks at it as if it were a HDD as far as optimization is concerned.
Other then that it should be faster than a USB 3.0 connection though.

Cheers,

What makes you think UASP doesn't support TRIM? UASP supports TRIM fine via two different methods, like I wrote above... and as I wrote in my entry post, CrystalDiskInfo is able to detect that just fine.

Hi,

What makes you think UASP doesn't support TRIM? UASP supports TRIM fine via two different methods, like I wrote above... and as I wrote in my entry post, CrystalDiskInfo is able to detect that just fine.

It does not support it natively, hence the use of the UNMAP hardware command which not all UASP hardware supports.
Windows however will treat your drive as if it were a HDD when you want to optimize it.

Now I'm wondering, is there a way to make Windows 10 [Version 10.0.14393] realize that it's talking to an SSD and not to a hard drive/make it send TRIM commands to it?

Short answer: No.
The main reason being that SCSI devices are unaware of trim command so these need to be translated.

Cheers,