Aller au contenu principal

Trueimage renamed my drive's OEM name/model

Thread needs solution

I used Trueimage 2020 to clone my Samsung SSD from my Seagate ST1000 in my laptop (my laptop has 2 hard drive bays). Anyway, after completing the clone, I swapped out the Seagate and booted from my newly cloned Samsung SSD. To my surprise, during boot, the system showed the SSD as a ST1000LM014  and when I looked at it in Windows, it also shows it as the 1TB Seagate drive. How do I rename it back to the original Samsung 860 EVO SSD? If I look at the properties of the drive, it shows the Seagate name and model number but under Hardware it does show up as Samsung 860 EVO. There's no way to change the drive name in either Properties, etc. I suspect it may be something encoded in the Windows registry perhaps? Thanks for any light anyone can shed on this matter.

0 Users found this helpful

Gary, I was not 100% certain what you were doing. After rereading your post several times, I worked out that the original drive was an Seagate ST1000, and the new drive is an Samsung 860 EVO. 

There is something very odd going on. Initially I thought what you are seeing was not the is not the name of the HDD but the name of the OS partition on the HDD. Windows invariably reports partition names, not disk model names; the only place I am aware where disk model names are reported is in Device Manager. Many disk utilities report both drive and partition information (for example HardDisk Sentinel or MinTool Partition Wizard). Windows Disk Management does not report drive model; it reports drive number and partition information. This information for the PC I am working on at the moment is shown in the screenshot below:

You can rename partitions with Disk Management.

However, the correct drive should be listed during bootup. One possibility is that somehow the UEFI/BIOS became corrupted. I would set the UEFI/BIOS to defaults, save, the renter the UEFI/BIOS to see if the drives are correctly identified.

Before messing with the UEFI/BIOS go in to the UEFI/BIOS and confirm how the SSD is being reported.

You should wait for suggestions from the other MVPs who are is USA, UK and Europe. 

Ian

I have a vague memory of seeing something similar to this reported in the forums previously but not of what caused it??

Again, if I remember correctly, I think that the remedy was to go into the Control Panel > Device Manager while booted into Windows, find the Disk Drive and delete it from there then restart the PC and allow Windows to correctly detect the Samsung EVO SSD as it boots again.

I would definitely recommend making a full disk backup before trying it unless you intend to revert back to the original Seagate drive and start over if anything goes wrong!

Note: I have tried this on a Hyper-V Virtual Machine running Windows 10 and all worked as expected (other than the fact my disk drive remained the same as wasn't incorrect).

The VM restarted and rediscovered the disk drive along with offered me the option to upgrade to Windows 11 which I have declined at the moment!

Thanks both of you for your comments. As strange as it sounds, yes, during POST before the OS actually boots up, the laptop shows the typical memory/RAM checks and then the drives, where it shows the Seagate ST1000 instead of the Samsung 860 EVO. So it's obviously not something within Windows so will try the BIOS stuff. This laptop is an old Toshiba Satellite which doesn't have the UEFI boot protected stuff like the newer PCs. I'll play with the BIOS and see what happens.