Though I don’t know what the best BIOS settings for my system are, they are the same for the original which worked, as they were for the clone. So, what I am saying is that no changes have been made to the system from cloning and then testing the clone. The system would then boot and when everything seemed fine, I cloned the OS, but that would not boot.

The file rescue was successful but for some reason the system wouldn’t boot after that so I eventually re-flashed the BIOS. I had trouble booting normally after using ‘Puppy Linux’ to rescue files from previous drives that I could not access after replacing the main board and OS (with the same model of MB & CPU). I think I should clarify the order of events. I don’t know what is the norm but when I hear someone in a video talking about choosing the correct disk in the BIOS they refer to the disk with the OS on it, were I have to choose Windows Boot Manager for ‘it’ to choose the correct drive. To me, that means it is not a perfect clone or other info, not cloned, is not being recognised. It seems apparent that it is not recognising the clone as being the same. The problem is when I tried to boot from the original drive it would not boot from it. Not sure which caused it to work but it then booted.

Having said that I have managed to get it to boot after using the windows (10 pro) installation pen drive and using the bootrec /FixMbr - /Fixboot – Rebuild Bcd command prompts.

Now after having trouble booting normally (for other reasons) and so having to re-flash the BIOS I find the cloned drive won’t boot. I simply cloned the OS from one SSD drive to another the same size and it would boot no problem. I like to have a clone of the OS in case a disaster occurs and before my main board died, I had no trouble using 'Macrium Reflect'. Hi, after replacing my main board and processor I am having difficulty in successfully cloning a drive that boots.

Macrium reflect windows 10 to ssd