Bear

Well-Known Member
Joined
Sep 29, 2016
Messages
128
Not sure whats going on but for some dumb reason windows 10 is not recognizing my
3TB Hitachi UltraStar 7K3000 as a HDD
it insists its a SSD.
My 850 evo has to go back to samsung so they told me to clone the c: onto D: then change boot order.

Perfect sense, same as always so I do so and now not only is the system HORRENDOUSLY slow but when I check system defrag it insists drive "c:" is a ssd.
if I run "defraggler" it does see it as a HDD but not the win 10 defragger.
The bios is set to uefi.
now I realize hdd is slower then SSD but not THIS slow. It takes roughly 4 minutes to fully load windows and stabilize.
 

Attachments

Solution
heheh well, that might make a big diff huh?
It opened another window, ran through some testing closed that screen and viola` issue resolved
idk, does the sysinfo file I gave originally tell you? If not tell me how to tell you.
 
I once met the same problem. The answer I got from the "computer shop on the corner" was the Mobo was too old and missed some functions.
I got around it by simply disable / switching off defragging for that drive...
 
They lied to you. This has nothing to do with the motherboard. It's windows being confused after cloning the system.
 
I don't think so. I did not clone a drive, I removed the old failing HD drive, inserted a new SSD and started a fresh install from scratch.
That make me believe that some functionality from the old MoBo was missing.
 
Shouldn't be the motherboard, I've never heard of that UNLESS the controller was acting up, but if that was the case it wouldn't operate and defraggler wouldn't show it properly like it does.
 
i would've thought it was included in the normal update checks.
well, after doing the update and sadly finding alot of personal settings changed, removing the SSD, changing sata port order, updating all the drivers I can think of, It STILL says its an ssd
 
If you open an admin command prompt and run winsat formal it should then rebort as a hdd after a reboot. If not another thing to try is setting the Optimize Drives Service to start automatically also has been known to fix this issue.
 
heheh well, that might make a big diff huh?
It opened another window, ran through some testing closed that screen and viola` issue resolved
 
Solution
It forces windows as part of it's testing to re-evaluate connected devices. Pleased it's fixed. Knew we'd get there in the end.