Windows 10: MR clone can show incorrect SSD identification info

I've cloned two old SSDs to Samsung EVOs recently (on two PCs, both 20H2 Pro), and discovered that MR carries some historical identification from the disk you're cloning (DUH!). In both cases, I cloned old SSDs to brand new Samsung 870 EVO 250GB SSDs, and in both cases, on the newly installed SSDs, Windows 10 Device Manager mis-identified the new SSDs. A check into Device Manager\Properties\Events for the new disks revealed historical info from the disks I had cloned from. Everything had been copied to the new disk, including the identification of the old disk in the registry. A search through each registry revealed that the Device Manager info was derived from the Friendly Name subkey info for the disk Windows thought it had on hand. Snooping around revealed that the registry had the info on the source disk just beside (above) the info for the new disk. I backed up the subkey, edited the Friendly Name, and rebooted. Now Device Manager and specs software (Everest) show exactly what they should: a new, Samsung authenticated, 870 EVO 250GB is sitting in the bay. "If you're cloning, if you're cloning, ... the whole world clones with you."

:)

 

MR clone can show incorrect SSD identification info

I've cloned two old SSDs to Samsung EVOs recently (on two PCs, both 20H2 Pro), and discovered that MR carries some historical identification from the disk you're cloning (DUH!). In both cases, I cloned old SSDs to brand new Samsung 870 EVO 250GB SSDs, and in both cases, on the newly installed SSDs, Windows 10 Device Manager mis-identified the new SSDs. A check into Device Manager\Properties\Events for the new disks revealed historical info from the disks I had cloned from. Everything had been copied to the new disk, including the identification of the old disk in the registry.

A search through each registry revealed that the Device Manager info was derived from the Friendly Name subkey info for the disk Windows thought it had on hand. Snooping around revealed that the registry had the info on the source disk just beside (above) the info for the new disk.

I backed up the subkey, edited the Friendly Name, and rebooted. Now Device Manager and specs software (Everest) show exactly what they should: a new, Samsung authenticated, 870 EVO 250GB is sitting in the bay.

"If you're cloning, if you're cloning, ... the whole world clones with you."

 

MR clone can show incorrect SSD identification info

The simple solution is to uninstall the disk in Device Manager and reboot - it will be fixed when Windows reinstalls it after a reboot. I've done it before.

 

MR clone can show incorrect SSD identification info

That's one reason I use imaging and recovery rather than cloning.