Device manager not correct - showing old disconnected hard drive

[speccy]

I have an odd issue where a Samsung SSD that is no longer in my system is still showing. The weird thing is if I bring up the properties, and then populate the fields of the drive (by pressing the populate button), it shows the capacity of the newer drive which is double the size. This drive is not a Samsung drive though. So I'm not sure what's going on here - see picture where it clearly states (at the top) that I'm looking at the properties of a 250GB Samsung drive, but the populated fields show it to be a 480GB drive.

 

[mjperry51]

Have you tried uninstalling from Device Manager and rebooting??

 

[speccy]

This is the drive with the OS on it, I'm not keen to try and remove it from device manager in this way. I can live with it the way it is, but it's yet another oddity with Windows 10. This product was so not ready for release. The only reason I was looking was because I had a USB Blu-Ray drive which kept disappearing after a few minutes of playing a movie, was driving me nuts. I wasn't able to solve that, so I've sent it back, but it's weird that DM is showing attributes of a drive that's no longer connected and mashing up the details with the newer one that is connected...

 

[TechFreak1]

This is the drive with the OS on it, I'm not keen to try and remove it from device manager in this way. I can live with it the way it is, but it's yet another oddity with Windows 10. This product was so not ready for release. The only reason I was looking was because I had a USB Blu-Ray drive which kept disappearing after a few minutes of playing a movie, was driving me nuts. I wasn't able to solve that, so I've sent it back, but it's weird that DM is showing attributes of a drive that's no longer connected and mashing up the details with the newer one that is connected...

Install the samsung magician application, this should rectify your issue.

Plus you will most likely install the similar application that came with your replacement SSD.

 

[speccy]

Thanks for your suggestions, but this is not how device manager has worked in any version of Windows ever. It should pick up the device and populate the fields with the info found, the old values should not persist. Scanning for new hardware within device manaher doesn't make any difference either. I'm not installing any Samsung software to try and rectify this, the drivers for the SSD's are part of the OS and are provided by Microsoft. The ATA/ATAPI drivers are from Intel as it's an Intel chipset on my mainboard. I do appreciate that you've taken the time to post, but in this instance I seriously doubt installing anything from Samsung will make any difference.

If i drill down further into the properties of the drive, it would seem that it is correctly recognised for what it is, but Windows has not updated the description in the top level of the device manager. See picture below which shows Samsung at the top but the hardware id's clearly show it to be a Sandisk drive of a much larger capacity.

 

[TechFreak1]

Thanks for your suggestions, but this is not how device manager has worked in any version of Windows ever. It should pick up the device and populate the fields with the info found, the old values should not persist. Scanning for new hardware within device manaher doesn't make any difference either. I'm not installing any Samsung software to try and rectify this, the drivers for the SSD's are part of the OS and are provided by Microsoft. The ATA/ATAPI drivers are from Intel as it's an Intel chipset on my mainboard. I do appreciate that you've taken the time to post, but in this instance I seriously doubt installing anything from Samsung will make any difference.

If i drill down further into the properties of the drive, it would seem that it is correctly recognised for what it is, but Windows has not updated the description in the top level of the device manager. See picture below which shows Samsung at the top but the hardware id's clearly show it to be a Sandisk drive of a much larger capacity.

View attachment 121502

I know how device manager works .

It was a random out of the box solution, because if there are any sort of conflicts in the registry for instance then installing these two applications should rectify them. Just because they are OEM software it doesn't mean they do not come bundled with the correct drivers .

The fix I see is relatively simple, is to uninstall the driver via right click and it should re-install correctly.

Or simply try system restore and see how that goes?

Also I would recommend installing the application that comes with any SSD as they generally helps with you advanced features such as over provisioning. Which of course you should tinker with if you know what you're doing.

Not to mention keeping a tab of how much data has been written to your drive, although with SSD's now it is highly unlikely they will die any time soon for the average consumer or prosumer.

 

[speccy]

I'm reluctant to uninstall the drivers for my Windows/boot drive. It's not really causing me any issues, just an oddity really, and typical of my experience with Windows 10 on the desktop, it's a bit of a mishmash and not really finished. Win10Mobile on the other hand, despite a few quirks is actually very good (for me at least).

 

[halflifecrysis]

Go to device manager, do an advanced view of your IDE and USB controllers (show all show hidden). Some will show up ghosted out or grayed out. Delete the ghost entries and reboot.

 

[TechFreak1]

I'm reluctant to uninstall the drivers for my Windows/boot drive. It's not really causing me any issues, just an oddity really, and typical of my experience with Windows 10 on the desktop, it's a bit of a mishmash and not really finished. Win10Mobile on the other hand, despite a few quirks is actually very good (for me at least).

Fair enough, try halflifecrysis suggestion haven't seen any ghost entries myself so didn't think to suggest it .

Go to device manager, do an advanced view of your IDE and USB controllers (show all show hidden). Some will show up ghosted out or grayed out. Delete the ghost entries and reboot.

 

[speccy]

Removed all hidden entries under all sections and rebooted, but the larger Sandisk drive is still identified as a 250GB Samsung device...

 

[TechFreak1]

Removed all hidden entries under all sections and rebooted, but the larger Sandisk drive is still identified as a 250GB Samsung device...

Have a look at the .inf or use aida64, it may very well turn out to be a rebranded Samsung drive :grin:.

How did you migrate your install btw?

 

[speccy]

It's not a Samsung drive, and it's not 250GB, it's 480GB - see earlier screenshot showing the hardware id's which show that it is a Sandisk 480GB drive, but the title of the properties box containing this info still says Samsung 250GB at the top - so weird!

To move my data from one drive to the other I used Clonezilla which allowed me to copy the data and also resize the partition to fill the new drive at the same time. It was the first time I'd used Clonezilla actually (I normally use Symantec Ghost for such tasks), but it seemed to work well enough.

 

[TechFreak1]

It's not a Samsung drive, and it's not 250GB

It was a joke hence the emoticon lol.

it's 480GB - see earlier screenshot showing the hardware id's which show that it is a Sandisk 480GB drive, but the title of the properties box containing this info still says Samsung 250GB at the top - so weird!

I saw, somewhere something weird has happened.

have a look at the events tab, there maybe a clue there about what happened.





Also what does this window say for you?

To move my data from one drive to the other I used Clonezilla which allowed me to copy the data and also resize the partition to fill the new drive at the same time. It was the first time I'd used Clonezilla actually (I normally use Symantec Ghost for such tasks), but it seemed to work well enough.

That maybe the culprit, only way to check would be clone data from USB to another (different OEMs and sizes).

 

[speccy]

I think I'm gonna leave it, it works, and I think if I do anything drastic, I may end up with more issues than I started with. It was more of an observation really, and typical of Windows 10 (desktop). Win10M on my phone I love

 

[TechFreak1]

I think I'm gonna leave it, it works, and I think if I do anything drastic, I may end up with more issues than I started with. It was more of an observation really, and typical of Windows 10 (desktop). Win10M on my phone I love

Probably best, as the saying goes "if it ain't broke don't fix it ".

 

[speccy]

Or another way, if it's just a bit broke, don't make it worse

 

[TechFreak1]

Or another way, if it's just a bit broke, don't make it worse

lol, yup.

Though I doubt some would be able to refrain from doing so.

 

[speccy]

I've tried fixing minor things like this for myself and for customers in the past and ended up in a much bigger hole. We live and learn, and over the years, I've learned that it's sometimes ok to accept less than total perfection to avoid a whole lot of pain/expense.

 

[ikjadoon]

I've tried fixing minor things like this for myself and for customers in the past and ended up in a much bigger hole. We live and learn, and over the years, I've learned that it's sometimes ok to accept less than total perfection to avoid a whole lot of pain/expense.

I apologize for the necropost, but I thought I'd post the solution as this is the first result in Google.

I had the same problem: Samsung 840 EVO 250GB (old) -> Samsung 850 EVO 500GB (new). I'd used Macrium Reflect instead of Clonezilla, but exactly the same symptoms.

But, I'd made an image the night before, so I was adventurous. :grin: The fix is what was suggested earlier by mjperry51: uninstall the hard drive from Device Manager. Then the new hard drive is recognized and the driver installs itself, from Microsoft as expected. :excited:

Reinstalling Samsung Magician didn't do anything (nor enabling/disabling RAPID mode) nor did removing any hidden devices (even a hidden device that was the old SSD), FWIW, which I'd tried first. Only uninstalling the enabled, active SSD from Device Manager fixed it (right-click the phantom old drive in Device Manager, click 'Uninstall Device', and reboot).

Before:


After:

 

[BigSweeney]

I apologize for the necropost, but I thought I'd post the solution as this is the first result in Google.

I had the same problem: Samsung 840 EVO 250GB (old) -> Samsung 850 EVO 500GB (new). I'd used Macrium Reflect instead of Clonezilla, but exactly the same symptoms.

But, I'd made an image the night before, so I was adventurous. :grin: The fix is what was suggested earlier by mjperry51: uninstall the hard drive from Device Manager. Then the new hard drive is recognized and the driver installs itself, from Microsoft as expected. :excited:

Reinstalling Samsung Magician didn't do anything (nor enabling/disabling RAPID mode) nor did removing any hidden devices (even a hidden device that was the old SSD), FWIW, which I'd tried first. Only uninstalling the enabled, active SSD from Device Manager fixed it (right-click the phantom old drive in Device Manager, click 'Uninstall Device', and reboot).

Before:
View attachment 137330

After:
View attachment 137331
View attachment 137332

ikjadoon, I'm in the same exact situation. I used Samsung Data Migration to migrate from a 250G 960 Evo to a 1 TB 960 Evo. Everything seemed to work fine until I tried to run a benchmark on my build and received an error about the SSD. I looked into what was causing issue and noticed the exact same scenario above. The drive is booting/functioning fine, showing up in Windows explorer and Disk Management but in Device Manager it's still showing up as the old drive. Like OP I'm nervous about uninstalling the Boot drive with my OS on it.

After you right clicked and uninstalled the device and did a system restart, BIOS was still able to detect the boot drive after it was uninstalled? Just want to make sure before I make this move because it seems pretty risky.