If you cloned your HDD to your SSD, it sounds like you have a system that boots in UEFI mode and the cloning application didn't register the bootloader file on the SSD into the UEFI firmware. The one-time boot menu populates dynamically based on what's actually available on the system, as long as the bootloader files on the attached devices are at the standard \EFI\Boot\Bootx64.efi path defined in the UEFI spec. The boot order list maintained in the firmware used for regular booting does not automatically populate, and bootloader file paths involve uniquely identifying devices and partitions. It's not like the Legacy BIOS days where you just said, "Boot from this device".
In terms of a fix, I don't know what cloning application you used, but clones performed with Macrium Reflect Free usually work fine, but when they don't, Reflect's "Rescue Media" has a routine called "Fix Boot Problems" that can address this issue, among other possible issues.
jphughan
9 Legend
•
14K Posts
0
December 17th, 2018 15:00
If you cloned your HDD to your SSD, it sounds like you have a system that boots in UEFI mode and the cloning application didn't register the bootloader file on the SSD into the UEFI firmware. The one-time boot menu populates dynamically based on what's actually available on the system, as long as the bootloader files on the attached devices are at the standard \EFI\Boot\Bootx64.efi path defined in the UEFI spec. The boot order list maintained in the firmware used for regular booting does not automatically populate, and bootloader file paths involve uniquely identifying devices and partitions. It's not like the Legacy BIOS days where you just said, "Boot from this device".
In terms of a fix, I don't know what cloning application you used, but clones performed with Macrium Reflect Free usually work fine, but when they don't, Reflect's "Rescue Media" has a routine called "Fix Boot Problems" that can address this issue, among other possible issues.