Can't boot Windows following restore to new NVMe, drive not in boot options
My existing Window's 10 system NVMe drive failed (Samsung 960), and I am trying to restore to a new (larger) NVMe drive (Samsung 970). I have tried an image backup restore using ATI 2019 to the new drive, which completed successfully - but the system will not boot to Windows. The NVMe drive is not listed anywhere by my BIOS in the boot options it presents to me during boot.
I am not entirely sure if the Windows boot used GPT or legacy mode - it is a UEFI Gigabyte BIOS - but I believe it used legacy mode since the .tib backup file properties as shown by the Acronis restore did show that the backup file partition as MBR. (I also tried the UEFI/GPT mode backup as well, and that failed to boot with the Window's "inaccessible boot drive" error message, but at least the BIOS found the GPT boot option and offered it. But given the backup file showed MBR partition I suspect legacy mode is the right path.)
I had verified the backup file was valid, and did select the option "Recover Disk Signature" when I did the restore.
I have tried repeated times with a couple of different backups - with the same results.
I believe I originally created the failed NMVe drive by cloning from a SATA SSD using Samsung's software, if that matters. One idea I had is to try a restore to that original SSD first, and then reclone using Samsung's stuff -- but thought to look for other ideas here first.
In the Gigabyte BIOS settings, "other OS" is selected rather than "Windows 8/10" option, which hides the "CSM compatibility" option. This seems suspect, but I am pretty sure it is the same setting as before when the system was working - so I haven't tried changing that. (I assume I should not need to change any of the prior BIOS settings to get the system to boot after a successful restore, but perhaps this is a bad assumption.)
Finally, I had Bitlocker enabled on the system, but from my readings I understand that ATI2019 is compatible with that and should restore fine (afterwhich I might need to re-enable Bitlocker).
Any help/suggestions would be greatly appreciated!