Group: Forum Members
You shouldn't have to change any BIOS settings to switch from one SATA-based drive to another, regardless of the fact that you're moving from an HDD to an SSD. The only exception I can think of would be if you had a very old system that still allowed you to set the SATA ports to IDE Compatibility mode rather than AHCI mode. But if your system supports UEFI booting, I doubt that's it. And Secure Boot isn't going to be an issue here. That just makes sure that the bootloader was properly signed by a trusted authority, so if you were able to use Secure Boot when booting from the old disk, you should be able to use it when booting from the new one containing the same data. Windows has supported Secure Boot since Win8, so as long as you're not trying to use a custom bootloader (or one that's been maliciously altered), that won't be a factor. And fyi, when Secure Boot is the issue, your system immediately shows a warning specifically saying that Secure Boot blocked the boot process. Clearing the keys is generally not a good idea since that can break even a Secure Boot setup that currently works. That's primarily intended for cases where you may have manually loaded some other signer's certificate, such as to use Secure Boot with a Linux distro. (This is all just for future reference, I guess.)
Can you post screenshots of the partition layouts of both the source and destination disks as shown in the Reflect Rescue environment?
The fact that it seems to boot for a while makes me wonder if there's some sort of driver issue here. Did you have any drivers or utilities specific to the old drive installed? Did you try ReDeploy, even though that isn't typically necessary in this scenario?