Several users have managed to resolve this particular issue by using a different SATA cable or SATA port. Faulty SATA cable / SATA port – We have seen several reports in which the SSD drive was refusing to boot due to a problem with the SATA cable used for the connection.In this case, removing/wiping the original drive will resolve the issue. Cloned SSD and source drive have the same unique ID – There are a lot of cloning software products (including Samsung Magician) that will mistakenly copy the unique ID during the cloning process.This means that you’ll need to access your BIOS/UEFI settings and instruct your computer to boot from the new SSD drive. The drive is not set to boot – During the process of cloning the source disk and connecting the SSD to the new computer, the drive will not preserve its boot priority.In this particular scenario, there is no repair strategy other than using a recovery tool to fetch the data from the old HDD and clean installing Windows on the SSD. Naturally, those we’re migrated to the new drive and might have messed up the boot data. Source disk can’t boot – This typically happens in those scenarios where the source disk that was cloned had contained bad sectors.

Macrium reflect clone disk id