Can't Activate New Boot Drive

sbr01

Prominent
Apr 18, 2017
4
0
510
Hello all. I've been using a Samsung 850 EVO 500gb as my sole drive without issue. Recently, I picked up a 960 EVO 1tb and wanted to clone my 850 and make the 960 my new boot drive. I downloaded the Samsung Data Migration Software and copied everything over without issue. However, once I went into BIOS and marked the 960 as boot priority #1, it wouldn't boot to windows, instead displaying the error message: "Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key". I did notice that my 850 displays "Window Boot Manager: Samsung 850 EVO" in BIOS. Do I need to change something in Windows Boot Manager? How would I go about this? Any help is most appreciated.
 
Solution
Somehow the 960's boot partition never got marked Active; you might have to usb or dvd boot a disk manager to mark 960's boot partition Active; of course the OS partition should already be set to Primary. I'm thinking Windows install DVD's Startup Repair may be all you need to fix this common HD situation.


I did disconnect the 850, yes. However, I still get the "Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key" error message.
 
Somehow the 960's boot partition never got marked Active; you might have to usb or dvd boot a disk manager to mark 960's boot partition Active; of course the OS partition should already be set to Primary. I'm thinking Windows install DVD's Startup Repair may be all you need to fix this common HD situation.
 
Solution
I don't have a disc but I used the USB drive I used to install windows and ran the Startup Repair, but it said it could not fix my startup issue. How can I get into the disc manager?
 
Okay I finally got it. The partition was there, but Windows had set the drive to being offline due to a signature conflict with the 850. I forced it online, restarted, and on the second restart I noticed I had an option for Windows Boot Manager on the 960 (entirely possible it was there after 1 restart, but I didn't notice). @RolandJS thank you for helping!