Jump to content

Speccy Incorrectly Identifies USB3.0 Hard Drives as SSD Drives in Windows 10 1511_2


helakejr

Recommended Posts

Machine Summary: Intel Core I7-6700K, 32 GB DDR4, NVIDIA, C:-LITEON IT L8T-256L9G-HP 256GB SATA3 SSD (in M.2 slot), D: Hitachi HUA723020ALA641 2TB SATA3 Hard Drive, K: 4TB SATA3 Hard Drive, L: 4TB SATA3 Hard Drive, M: 4TB SATA3 Hard Drive, N: 4TB SATA3 Hard Drive, [KLMN are four Seagate ST4000DM 000-1F2168 USB Device (as shown in Win10 device manager. Drives are physically in a SANS Digital four drive tower connected by a USB3.0 interface, the SANS Digital controller is operating in RAID0 (e.g. no RAID)]. 

 

Motherboard: ASROCK Z170 Pro4S

LGA1151/ Intel Z170/ DDR4/ 3-Way CrossFireX & 2-Way SLI/ SATA3&USB3.1/ M.2&SATA Express/ A&GbE/ ATX Motherboard

 

NOTE#1: This machine was recently "upgraded(down-graded)" from Windows 8.1 PRO x64, under this OS your software worked. After the upgrade: same issue, after doing a Clean Win10PRO install: same issue.

 

Software: Windows 10 PRO Build 1511_2 (64-bit) OS updated to all updates and patches, CCLeaner v5.17.5590 (64-bit)

 

Problem: CCLeaner (Speccy) identify the KLMN hard drives as SSD Drives even though they are SATA3 4TB Seagate Hard Drives.

 

As such the CCleaner tool Drive Wiper->Wipe Free Space only allows 1 pass because it incorrectly thinks that my seagate drives are Solid State Device's.

 

I suspect that the Win10 algorithm for drive identification has changed from Win8.1 and the "newer way" needs to be understood.

 

NOTE#2: Issue also occurs with: Speccy v1.29.714 (64-bit)

post-76628-0-42138800-1468695701_thumb.jpg

post-76628-0-29364100-1468695702_thumb.jpg

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.