4/28/2021 Disk name in Device Manager shows old disk name after cloning and replacement

Macrium Support Forum

Disk name in Device Manager shows old disk name after cloning and
replacement
https://forum.macrium.com/Topic23810.aspx

 By debumitra - 10 June 2018 8:47 PM

Hello,

My DELL Optiplex Micro desktop PC originally had a LITEON 128GB M.2 SATA SSD. I used Macrium to clone the LITEON SSD into a Samsung EVO

850 M.2 256GB  SATA SSD as I needed additional disk space.

After cloning, the Samsung EVO 256GB SSD booted fine and everything is working.

But in Windows Device Manager, the new Samsung Disk shows up with the old LITEON name.  That is instead of being called "Samsung EVO

256GB", it's called "LITEON 128GB", the name used by the old SSD. This is confusing.

Please could anybody provide some explanation why this happened?

Also, is there away the new (installed) disk could be called by its correct name in the Windows Device Manager?

OS: Windows 10

Thanks,

Debabrata Mitra

 By jphughan - 10 June 2018 9:05 PM

To my knowledge, that isn't possible. The reason is that the name shown in Device Manager is based on the drivers that are loaded to support
that device, or from the device itself in the case of generic drivers for things like hard drives, optical drives, USB controllers, etc. Are you saying
you've physically removed the LiteOn SSD and you're still seeing a LiteOn SSD shown in Device Manager, with the Samsung SSD nowhere to
be found? Try opening the Disk Management application, and in the lower half of the main area where your disks are listed, right-click the "tile"
toward the left corresponding to your Samsung SSD and choose Properties -- make sure you're actually selecting your Samsung SSD based on
the capacity of the drive. What name is shown in the Device Manager properties page that appears?

 By debumitra - 10 June 2018 9:46 PM

 jphughan - 10 June 2018 9:05 PM

The LiteOn SSD was physically removed and replaced by the Samsung SSD. Before replacement, the LiteOn SSD was cloned into the Samsung

SSD using Macrium. In Device Manager, under Disk Drives, I see the Samsung SSD, but it's called LiteOn (i.e., the name was not changed to

reflect the make/model of the Samsung SSD). I know it's the Samsung SSD, although it's called LiteON, because the Hardware ID shows

Samsung. Also, under events, it says that the LiteOn device was migrated to Samsung.

All that is good and makes sense. It's just that the label used to identify the Samsung SSD in Device Manager still shows LiteOn.

I would like to know if there is a safe way to change the label.

 By jphughan - 10 June 2018 10:18 PM

I've never seen that happen despite having cloned multiple PCs using multiple products and multiple versions of Windows. But I also don't know

https://forum.macrium.com/PrintTopic23810.aspx 1/4
4/28/2021 Disk name in Device Manager shows old disk name after cloning and replacement

of a way to change the device "display name" shown in Device Manager. Just out of curiosity, can you post a screenshot (or more if needed)
that shows Device Manager labeling the SSD as a LiteOn while also showing Samsung as the hardware ID ?

 By debumitra - 11 June 2018 10:03 AM

 jphughan - 10 June 2018 10:18 PM

I have collected together several screen shots in the attached PDF showing that the Samsung SSD (i.e., hardware ID Samsung) shows up with
LiteOn label. Also, the events indicate the same.
Thanks.

 By Seekforever - 11 June 2018 12:22 PM

Don't know if this would provide any clue but what is displayed in the BIOS?

 By DanDanz - 11 June 2018 1:07 PM

I've got a hunch that this has something to do with fast boot remembering a boot path across a shutdown/reboot. Try turning it off for a reboot
cycle.

 By jphughan - 11 June 2018 1:28 PM

I think the fact that it's identified as a SCSI device is a clue. Check your Storage Controllers category in Device Manager. Do you see some
sort of SATA/RAID storage controller, likely Intel Rapid Storage? If so, that storage controller may somehow still be retaining the LiteOn SSD
identifier, although I can't imagine why and have never seen this before. Depending on your system there may be a way to disable that
controller entirely and run your storage controller in native AHCI mode, but that's typically a setting that's only changed before a clean Windows
installation rather than changed for existing Windows installations, although I believe there's a way to accomplish the latter if you jump through
some hoops like a trip through Safe Mode.

 By debumitra - 11 June 2018 11:16 PM

 jphughan - 11 June 2018 1:28 PM

First of all, thank you all for your interest in the problem and suggestions. Here are all the things I have tried (with no
result):
(a) Checked BIOS setting. BIOS->DRIVES->SATA-4, Type = 250GB SSD, Device ID = Samsung SSD 850 EVO M.2 250GB.
So the BIOS recognizes the SSD correctly. Doesn't think that the SSD is LiteOn.
(b) Switched off fast boot and rebooted. Didn't change anything.
(c) The machine uses Intel Rapid Storage (RST) controller. I did not try to change it. But the GUI attached to the Intel RST
Controller shows everything correctly. It says Model = Samsung SSD 850 EVO M.2 250GB and Firmware = EMT21B6Q.
No sign of LiteOn SSD there.
(d) Safe mode:  I did this too. But again, it didn't change anything. Windows Device Manager still says LiteOn.

I want to point out that the new SSD was installed exactly at the same M.2 port where the old SSD was installed. It has
the same interface and used the same drivers as the old one. The only difference between the old and the new is the
model and the capacity. Also, the new one is a clone of the old one - cloned using Macrium.

https://forum.macrium.com/PrintTopic23810.aspx 2/4
4/28/2021 Disk name in Device Manager shows old disk name after cloning and replacement

Please let me know what else I should try.

 By jphughan - 11 June 2018 11:33 PM

I've worked in IT for 15 years and have cloned multiple drives on multiple systems using multiple applications across multiple versions of
Windows, and I have never once seen Device Manager have a "sticky" display name like that on a hard drive or anything else. The fact that
you're reusing the same port shouldn't matter. You can change the device connected to a particular USB port without causing this, after all, and
the same goes for hard drives at least in every experience I've had or know of, except this one.

I have one last suggestion, which I freely admit is a "Hail Mary" in that I have no idea whether it will work because I have no idea what's causing
this problem in the first place. I would suggest making a backup of your system before you try this, although I doubt you'll actually need it. Here
goes: In Device Manager, delete the LiteOn SSD device. When I tried this in a VM, I was prompted to restart (no lockup/BSOD or anything),
and after doing so, the device was back. So maybe that will cause this device to return properly in your case.

 By debumitra - 13 June 2018 12:12 AM

 jphughan - 11 June 2018 11:33 PM

Thanks for your suggestion. It seems that I shall have to try your "Hail Mary" suggestion as no other more conservative
ideas are coming alone. But I may nt be able to get to it before Friday. In the meantime, here is some more information
(with a hope that this triggers some other ideas, from 'jphugan' or anybody else):

I have checked various other places and tools to see if any other application reads the Samsung Disk as a LiteOn Disk
the way Device Manager does. But none did. They all returned the same label/string: Samsung SSD 850 EVO M.2 250GB

Here is the list of things I tried.

BIOS -> DeviceID = Samsung SSD 850 EVO M.2 250GB

Only Device Manager shows the wrong label.

Key Name:         
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SCSI\Disk&Ven_Samsung&Prod_SSD\4&19a2fccc&0&000400
Value 0
  Name:          DeviceDesc
  Type:            REG_SZ
  Data:            @disk.inf,%disk_devdesc%;Disk drive
........
........

https://forum.macrium.com/PrintTopic23810.aspx 3/4
4/28/2021 Disk name in Device Manager shows old disk name after cloning and replacement

Value 9
  Name:          FriendlyName
  Type:            REG_SZ
  Data:            LITEON L8H-128V2G-11 M. SCSI Disk Device

 By jphughan - 13 June 2018 12:30 AM

If that's the only place you're seeing this, and based on your finding in the registry, I'm getting more confident that deleting that device in Device
Manager and allowing it to be recreated will resolve this. And I wouldn't characterize that suggestion as aggressive. Again, I tried it in a VM and
was simply prompted to restart, at which point the device came back. And even in the very unlikely event that your whole system falls apart, if
you captured a backup immediately prior to making this change, thanks to Rapid Delta Restore, the restore process itself will proceed extremely
quickly because there will be so few changes to roll back since the time of the backup. Good luck, and please report back! (On a side note,
even fixing this wouldn't explain what caused it in the first place. I wish that could be established just out of general curiosity. Such a strange
issue....)

 By debumitra - 13 June 2018 10:23 PM

 jphughan - 13 June 2018 12:30 AM

Thank you, jphughan, for all the encouragement. I took a Macrium backup, uninstalled the device from device manager,
rebooted the PC. Guess what? The problem corrected itself. Now it shows up as "Samsung SSD 850 EVO M.2 250GB" in
Device Manager too. as expected. Thank you!

By the way, I found this link by web search where somebody else faced the exact same problem and the only thing that
worked was uninstalling the device from device manager, as you suggested. Check out this url
"https://forums.windowscentral.com/windows-10/407272-device-manager-not-correct-showing-old-disconnected-
hard-drive.html", go all the way down to the last but one post by "ikjadoon", and you will see the exact same problem
and solution.

 By jphughan - 13 June 2018 10:50 PM

Glad it worked! And hey, apparently you’re not alone on this issue. I’d still love to know what the underlying cause is, but based on the last few
Win10 releases and especially considering this new age of Win10 releases planned for every March and September, it seems Microsoft just
exchanges one set of bugs for another. Ever since Win10 1607, I’ve noticed that bugs I found in the previous release get fixed, but stuff that
worked just fine in previous releases is broken, even stuff that has nothing to with any of the new features. Sigh....

https://forum.macrium.com/PrintTopic23810.aspx 4/4