New NVME SSD - Windows Boot Manager

Hi all - I'm looking for a little bit of guidance.

I have a custom PC (Windows 10 (1909), Gigabyte Z370 HD3 motherboard) and I have just upgraded from a WD 1TB HDD to a 2TB Samsung 970 EVO PLUS NVME.

I used the Samsung Data Migration software to migrate from the HDD to the SSD - all went well. I then restarted the PC and re-ordered the Bios to boot from the SSD first, then HDD, then CDRW. However, when I did this and exited the BIOS, the PC then gave an error message "Reboot and Select proper Boot device". To troubleshoot, I disconnected the HDD and retried - hey presto the PC booted from the SSD no problem!

What I have noticed is that with the HDD connected, the BIOS lists the HDD as "Windows Boot Manager (WD etc.)" but the SSD just as the Samsung 970. i.e. the BIOS does not recognise it as a bootable device. However, with the HDD disconnected, the BIOS lists the SSD as "Windows Boot Manager (Samsung 970 etc)". What I would like is for both to appear as Windows Boot Manager and then set the order as SSD first.

I could just completely disconnect the HDD but I wanted to have it as a back-up just in case the SSD failed.

Can anyone shed some light on why I can't have both recognised as bootable devices?

Thanks,

Ian

- - - Updated - - -

I kept on troubleshooting - cleared the CMOS on the motherboard and no difference. Tried switching off CSM support on BIOS, no difference.

I then booted the machine from the HDD (but with the SSD plugged in) and once in Windows, opened Disk Management and noted that the SSD was disabled - with a Disk Signature Collision error. When I cleared that and restarted the PC, the BIOS then had Windows Boot Manager for both the SSD and HDD, so was able to successfully prioritise boot from the SSD and still have the HDD connected.

So, I seem to have resolved the issue, but can anyone explain how/why?

@fantata1 hello and welcome to TF,
I would try making a bootable MiniTool USB and mark the active partition on the HDD as inactive if no other better suggestions come along; An Easy Way to Set Partition as Active or Inactive with MiniTool

When you cloned the old drive to the new drive, you also cloned its signature - GUID. Windows uses the disk GUID to determine where to load Windows from. Since there were two disks with the same GUID, Windows had to disable one of the drives.

NavyLCDR said:

When you cloned the old drive to the new drive, you also cloned its signature - GUID. Windows uses the disk GUID to determine where to load Windows from. Since there were two disks with the same GUID, Windows had to disable one of the drives.

Solution: Generate Globally Unique Identifier (GUID) in Windows

@fantata1 had already fixed the problem.

Thanks everyone - that all makes sense now. So I accidentally created a new GUID in Disk Management - I got there in the end.

I will create a partition on the old HDD, save all data I want and then remove the OS from it

Please run: DiskParInfo.bat - Click here to go to the BSOD batch repository to download and run this batch file.

can you edit the boot manager

EddieB1106 said:

can you edit the boot manager

3 months late after the issue is solved ?