[SOLVED] Stuck on bios after using Macrium Reflect to copy my HDD to my SSD

Aug 2, 2019
13
0
20
I've disconnected my HDD and I'm only getting the bios whenever I'm booting up the pc. I'm at a loss for what to do as I didn't expect Macrium to literally break my pc by using it. Any help is appreciated.

Specifics:
Win 10
Samsung SSD 950 PRO 250gb
WD10EZEX HDD
Both drives were already installed and functioning until I used Macrium, but the OS was on the HDD and I wanted to copy it over and use the SSD instead.
 
Last edited by a moderator:
Solution
I used the troubleshoot function of the Windows 10 installation media and selected startup repair. This solved the issue of not getting past the BIOS. Hope this helps anyone dealing with the same issue. :)
Aug 2, 2019
13
0
20
Details, please.
What specific drives?
What OS?
Does it work if you return the system back to original config, without the new SSD?
Specifics:
Win 10
Samsung SSD 950 PRO 250gb
WD10EZEX HDD
Both drives were already installed and functioning until I used Macrium, but the OS was on the HDD and I wanted to copy it over and use the SSD instead.
 

USAFRet

Titan
Moderator
Instead of Macrium Reflect, use the Samsung Data Migration tool.

Thusly:
-----------------------------
Specific steps for a successful clone operation:
-----------------------------
Verify the actual used space on the current drive is significantly below the size of the new SSD
Download and install Macrium Reflect (or Samsung Data Migration, if a Samsung SSD)
Power off
Disconnect ALL drives except the current C and the new SSD
Power up
Run the Macrium Reflect (or Samsung Data Migration)
Select ALL the partitions on the existing C drive
Click the 'Clone' button
Wait until it is done
When it finishes, power off
Disconnect ALL drives except for the new SSD
This is to allow the system to try to boot from ONLY the SSD
Swap the SATA cables around so that the new drive is connected to the same SATA port as the old drive
Power up, and verify the BIOS boot order
If good, continue the power up

It should boot from the new drive, just like the old drive.
Maybe reboot a time or two, just to make sure.

If it works, and it should, all is good.

Later, reconnect the old drive and wipe all partitions on it.
This will probably require the commandline diskpart function, and the clean command.

Ask questions if anything is unclear.
-----------------------------
 
Aug 2, 2019
13
0
20
Instead of Macrium Reflect, use the Samsung Data Migration tool.

Thusly:
-----------------------------
Specific steps for a successful clone operation:
-----------------------------
Verify the actual used space on the current drive is significantly below the size of the new SSD
Download and install Macrium Reflect (or Samsung Data Migration, if a Samsung SSD)
Power off
Disconnect ALL drives except the current C and the new SSD
Power up
Run the Macrium Reflect (or Samsung Data Migration)
Select ALL the partitions on the existing C drive
Click the 'Clone' button
Wait until it is done
When it finishes, power off
Disconnect ALL drives except for the new SSD
This is to allow the system to try to boot from ONLY the SSD
Swap the SATA cables around so that the new drive is connected to the same SATA port as the old drive
Power up, and verify the BIOS boot order
If good, continue the power up

It should boot from the new drive, just like the old drive.
Maybe reboot a time or two, just to make sure.

If it works, and it should, all is good.

Later, reconnect the old drive and wipe all partitions on it.
This will probably require the commandline diskpart function, and the clean command.

Ask questions if anything is unclear.
-----------------------------
How do I do any of that whilst not getting past the BIOS? I also can't physically connect the sata canow from the HDD to the SSD as the SSD is connected straight to the motherboard.
 
Last edited:
Aug 2, 2019
13
0
20
I used the troubleshoot function of the Windows 10 installation media and selected startup repair. This solved the issue of not getting past the BIOS. Hope this helps anyone dealing with the same issue. :)
 
Solution