bcdedit and BIOS disk order, how do I setup multibooting?

I have 4 SSDs in the UEFI machine, 2 of them have are bootable with Win10 on them and 1 has bootable Linux.


The primary boots just fine. I cloned the primary onto the clone SSD with Macrium and created a bcdedit entry for it. When the machine boots and I select the clone Win10 drive, it does not boot.


I have to go into the BIOS and change the drive order under BIOS/Boot. Not of the multiple devices like CDROM, flash but of the disks themselves. Then the clone Windows 10 boots just fine. But the primary Win10 no longer boots. I have to rearrange the disk order under BIOS again to get my primary disk to boot again. Then the clone stops booting.


and under BIOS/boot/disks I have 2 entries per each disk. I think it has retained some of my previous BCD entries maybe.


To confuse this further, the primary and clone Win10 disks are the same model, so here are 4 entries that look exactly the same and I have to select one until I find the one that works. I usually get it on the 1st try.



I run EasyBCD and it shows no redundant entries.


I can run bcdedit /enum all but cannot figure out which entries are false. This multiboot scheme used to work and recently broke down and I cannot figure where the disconnect it.

I am not really an expert on this, but I do have two SSD's, both containing W10 pro, in a dual boot. My disks are mbr.
I set EasyBCD in each Windows (donot know whether that is necessary) and unchecked "use Metro bootloader". When the Bios screen starts up, it presents the selection option which Windows to start up. What happens in your case of non-booting? Nothing or error message?

The problem may be that windows writes a disk signature to every hard drive if you clone it you have 2 with the same signature so windows can't tell which disk is which

this is the error I get until I change the boot order in BIOS.

It used to work then stopped.
I have to change the boot order in BIOS, as if bcdedit is pointing to the wrong disk. But it's not and disk IDs are unique.

Try the bcdboot command

this is what bcdedit looks like:

Windows Boot Manager--------------------identifier {bootmgr}description Windows Boot Manager
locale en-USinherit {globalsettings}default {current}resumeobject {34222f3b-2d98-11e9-9e5a-d8cb8aefea8e}displayorder {2e2e25a7-b0e8-11e9-9f42-806e6f6e6963} {5bca99d5-b0ef-11e9-9f45-806e6f6e6963} {5bca99d7-b0ef-11e9-9f45-806e6f6e6963} {2c4a7087-b01b-11e9-9f39-806e6f6e6963} {56bfddc0-af31-11e9-9f30-806e6f6e6963} {2e2e25a9-b0e8-11e9-9f42-806e6f6e6963} {current} {34222f4c-2d98-11e9-9e5a-d8cb8aefea8e}toolsdisplayorder {memdiag}timeout 9displaybootmenu YesWindows Boot Loader-------------------identifier {current}device partition=Cath \WINDOWS\system32\winload.efidescription Windows 10locale en-USinherit {bootloadersettings}recoverysequence {34222f3e-2d98-11e9-9e5a-d8cb8aefea8e}displaymessageoverride Recoveryrecoveryenabled Yesisolatedcontext Yesallowedinmemorysettings 0x15000075osdevice partition=C:systemroot \WINDOWSresumeobject {34222f3b-2d98-11e9-9e5a-d8cb8aefea8e}nx OptInbootmenupolicy StandardWindows Boot Loader-------------------identifier {34222f4c-2d98-11e9-9e5a-d8cb8aefea8e}device partition=Gath \Windows\system32\winload.efidescription Windows 10 - August 6, 2019locale en-USosdevice partition=G:systemroot \Windowsresumeobject {f2098f89-b9fa-11e9-9f79-806e6f6e6963}

not sure how to get forum to not format it and eat end of line characters.

dictum said:

not sure how to get forum to not format it and eat end of line characters.

Put code tags around it.