[SOLVED] Can't boot from new M.2 NVMe SSD ?

Stev3y

Reputable
Jun 9, 2017
19
0
4,510
Hey,
I just bought a new M.2 SSD ( https://www.xpg.com/us/xpg/583 ), and tried cloning Windows from my old SSD (https://www.hyperxgaming.com/en/ssd/fury-sata-solid-state-drive), I used Macrium reflect to clone the drive, I even cloned a small 500mb something amount(some kind of recovery partition which had a windows logo next to it in macrium reflect) from my HDD which was plugged in when I first installed windows on my old SSD, and everytime I try to boot from my new M2 it tells me to insert boot media, or it gives me a bluescreen telling me that winload.exe is missing, doesn't matter if I unplug all my other drives, it still doesn't boot. I tried changing some settings in the BIOS, for example legacy or uefi mode, didn't work, tried disabling CSM, still nothing. I don't know what to do anymore, could anyone help me?
My motherboard:ASRock B450M-pro4
Processor: Ryzen 5 2600
 
Solution
Here is my disk management screenshot
It is not cloned properly.
I'm assuming:
120GB Disk1 is source drive,​
500GB Disk 2 is target drive.​
Is that correct?

Your source 120GB drive is MBR partitioned.
Target 500GB drive is GPT partitioned.
If this was intentional, then macrium can not properly make target bootable. You have to create bootloader manually.

Small 531MB partition on target drive is of wrong type to be bootable. You have to delete it and recreate properly.
Execute following from elevated command prompt (regular command prompt will give error on last steps).
diskpart
list disk
select disk 2
(select 476GB disk)​
list...
Hey,
I just bought a new M2 ( https://www.xpg.com/us/xpg/583 ), and tried cloning Windows from my old SSD (https://www.hyperxgaming.com/en/ssd/fury-sata-solid-state-drive), I used Macrium reflect to clone the drive, I even cloned a small 500mb something amount(some kind of recovery partition which had a windows logo next to it in macrium reflect) from my HDD which was plugged in when I first installed windows on my old SSD, and everytime I try to boot from my new M2 it tells me to insert boot media, or it gives me a bluescreen telling me that winload.exe is missing, doesn't matter if I unplug all my other drives, it still doesn't boot. I tried changing some settings in the BIOS, for example legacy or uefi mode, didn't work, tried disabling CSM, still nothing. I don't know what to do anymore, could anyone help me?
My motherboard:ASRock B450M-pro4
Processor: Ryzen 5 2600
Did you make Rescue USB from MR ? There's a utility to fix BOOT problem on it if you boot from it.
 
  • Like
Reactions: Stev3y
Did you make Rescue USB from MR ? There's a utility to fix BOOT problem on it if you boot from it.
I did not, so I'm supposed to make a rescue usb from macrium reflect and plug it in, then boot from my new NVMe? And after? Because when I boot from the NVMe, it either shows me a black screen saying insert boot media, or it throws me to a blue screen saying winload.exe is missing.
 
Yes, make rescue USB fro Macrium reflect and BOOT from that USB.
So I made a rescue USB, booted from it, then it opened macrium reflect, I pressed on fix windows boot problems, and it detected 2 drives which had windows on it ( View: https://imgur.com/a/efhYaVk
), I selected the second one which is the new one, the one which it doesn't let me boot from, then it showed me this screen asking me where I want to boot from ( View: https://imgur.com/a/llXywaB
), and now it doesn't show my new NVMe (J drive), it doesn't let me boot from it. What should I do?
(Even if i select my other old SSD at the first screen at the second one it still isn't showing me the J drive)
 
Here is my disk management screenshot
It is not cloned properly.
I'm assuming:
120GB Disk1 is source drive,​
500GB Disk 2 is target drive.​
Is that correct?

Your source 120GB drive is MBR partitioned.
Target 500GB drive is GPT partitioned.
If this was intentional, then macrium can not properly make target bootable. You have to create bootloader manually.

Small 531MB partition on target drive is of wrong type to be bootable. You have to delete it and recreate properly.
Execute following from elevated command prompt (regular command prompt will give error on last steps).
diskpart
list disk
select disk 2
(select 476GB disk)​
list partition
select partition x
(select 531MB partition, x=1 or x=2)​
delete partition
create partition efi size=530
format fs=fat32 quick
assign letter=F
exit
bcdboot I:\windows /s F: /f UEFI
bootsect /nt60 I: /force
Show screenshot of the result. There should be no errors.


After this is done,
shutdown your pc,​
disconnect old OS drive (120GB),​
boot into BIOS,​
Set Windows Boot Manager as first in boot order,​
UEFI boot has to be enabled,​
disable secure boot,​
disable fast boot and​
boot into windows.​
It is essential, that source drive is physically disconnected during first boot from target drive.
If you fail to do that, you'll have to reclone.
 
  • Like
Reactions: Stev3y
Solution
It is not cloned properly.
I'm assuming:
120GB Disk1 is source drive,​
500GB Disk 2 is target drive.​
Is that correct?

Your source 120GB drive is MBR partitioned.
Target 500GB drive is GPT partitioned.
If this was intentional, then macrium can not properly make target bootable. You have to create bootloader manually.

Small 531MB partition on target drive is of wrong type to be bootable. You have to delete it and recreate properly.
Execute following from elevated command prompt (regular command prompt will give error on last steps).
diskpart
list disk
select disk 2
(select 476GB disk)​
list partition
select partition x
(select 531MB partition, x=1 or x=2)​
delete partition
create partition efi size=530
format fs=fat32 quick
assign letter=F
exit
bcdboot I:\windows /s F: /f UEFI
bootsect /nt60 I: /force
Show screenshot of the result. There should be no errors.


After this is done,
shutdown your pc,​
disconnect old OS drive (120GB),​
boot into BIOS,​
Set Windows Boot Manager as first in boot order,​
UEFI boot has to be enabled,​
disable secure boot,​
disable fast boot and​
boot into windows.​
It is essential, that source drive is physically disconnected during first boot from target drive.
If you fail to do that, you'll have to reclone.
I followed everything step by step, there were no errors at the cmd part, and I could finally boot to windows from my new NVMe drive. Thank you so much for your help!