Windows 10: Setting up Windows boot manager to boot from SSD as secondary drive

Hi, my situation is such that I had an internal mechanical HDD as the only booting drive. After adding a SSD inplace of optical drive it appears in system as 2nd hard drive without chance to change the order in UEFI BIOS. So it's internal drive #2. I used Paragon Hard Disk Manager to migrate my Windows OS from the old drive to the SSD. Everything went fine and the partitions structure seems mirrored 1:1 to the SSD. During the migration process I instructed HDM to updqate boot entries to reflect the new state.
On reboot however I'm still getting only one entry in boot menu and that's the Windows instance on old drive, ie. the clone on SSD is invisible.
I need to know what can I do so the bootmgr offers me bot instances on both drives, where the SSD clone will be primary (default). I wouldn't make my PC unbootable so wanting experimenting.

:)

 

SSD as Boot and Raid as secondary

I've just bought a vertex 2 and have installed windows on it, but am having difficulties setting up a RAID0 with my 2 HDD's that i want to use as my backup/seconday drives. If i set my Sata config to raid it wont let me boot with my SSD. Any suggestions?

 

SSD as Boot and Raid as secondary

you should set it to RAID, you may have to delay drive detection in your BIOS. I normally set it to zero, but had to change it to 5 seconds (even though there is no delay what so ever) otherwise it would randomly (1 in 3) fail to boot/detect the SSD

i have the same setup, single SSD as boot/windows drive. RAID-0 as game/backup.

 

New Secondary Drive Causes Boot Failure Windows 10

For the second time now, Windows 10 failed to boot after initializing and formatting a spare drive (using Windows Disk Management). After the boot fail, UEFI boot settings were still set to boot from Windows Boot Manager, but it still wouldn't boot, just goes into diagnostic mode, fails to repair boot problem, and goes to the repair menu. In advanced options I can then load a recent image (made with Windows 7 Backup and Recovery in control panel), and everything goes back to normal. My question is what causes this problem, and how do I repair it without re-imaging Windows? I don't recall ever having this problem in other Windows versions, only in Windows 10. Anyone else notice this problem?