bcdedit issue? M.2 SATA to NVME clone: Windows 10 won't boot (Linux OK, New Win install OK) [on hold]
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I cloned my M.2 SATA drive to a new NVME drive - simply did raw dd copy. My Linux installation needed minor tweaks to /etc/fstab due to the device names being different (/dev/nvme0n1px vs. /dev/sdax). My Windows install will not boot. The disk is GPT, and I believe the original Windows 10 was UEFI - the Linux installation definitely was. I did a fresh Windows install in a spare partition and it boots fine. I've mostly figured out bcdedit, and I've edited the BCD entry for my original install with no success. I have the correct BCD device, osdevice, and path based on the drive letter that I see for the Windows partition using diskpart / list volume.
Is there anything else that might need to be edited to enable Windows to boot? In particular, are there any configuration files or registry entries that need to be changed based on the change from SATA to NVME?
uefi nvme clone
asked yesterday
user2657480
1
New contributor
user2657480 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as off-topic by Rui F Ribeiro, RalfFriedl, sebasth, JigglyNaga, Archemar 11 hours ago
- This question does not appear to be about Unix or Linux within the scope defined in the help center.
add a comment |
up vote
0
down vote
favorite
I cloned my M.2 SATA drive to a new NVME drive - simply did raw dd copy. My Linux installation needed minor tweaks to /etc/fstab due to the device names being different (/dev/nvme0n1px vs. /dev/sdax). My Windows install will not boot. The disk is GPT, and I believe the original Windows 10 was UEFI - the Linux installation definitely was. I did a fresh Windows install in a spare partition and it boots fine. I've mostly figured out bcdedit, and I've edited the BCD entry for my original install with no success. I have the correct BCD device, osdevice, and path based on the drive letter that I see for the Windows partition using diskpart / list volume.
Is there anything else that might need to be edited to enable Windows to boot? In particular, are there any configuration files or registry entries that need to be changed based on the change from SATA to NVME?
uefi nvme clone
asked yesterday
user2657480
1
New contributor
user2657480 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as off-topic by Rui F Ribeiro, RalfFriedl, sebasth, JigglyNaga, Archemar 11 hours ago
- This question does not appear to be about Unix or Linux within the scope defined in the help center.
hmmm sounds like an interesting problem, however I must admit that I (and probably most here) would not have as much information as somebody over at Super User would. Since this is primarily a Windows related issue, you may get better responses there.
– bgregs
yesterday
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I cloned my M.2 SATA drive to a new NVME drive - simply did raw dd copy. My Linux installation needed minor tweaks to /etc/fstab due to the device names being different (/dev/nvme0n1px vs. /dev/sdax). My Windows install will not boot. The disk is GPT, and I believe the original Windows 10 was UEFI - the Linux installation definitely was. I did a fresh Windows install in a spare partition and it boots fine. I've mostly figured out bcdedit, and I've edited the BCD entry for my original install with no success. I have the correct BCD device, osdevice, and path based on the drive letter that I see for the Windows partition using diskpart / list volume.
Is there anything else that might need to be edited to enable Windows to boot? In particular, are there any configuration files or registry entries that need to be changed based on the change from SATA to NVME?
uefi nvme clone
asked yesterday
user2657480
1
New contributor
user2657480 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I cloned my M.2 SATA drive to a new NVME drive - simply did raw dd copy. My Linux installation needed minor tweaks to /etc/fstab due to the device names being different (/dev/nvme0n1px vs. /dev/sdax). My Windows install will not boot. The disk is GPT, and I believe the original Windows 10 was UEFI - the Linux installation definitely was. I did a fresh Windows install in a spare partition and it boots fine. I've mostly figured out bcdedit, and I've edited the BCD entry for my original install with no success. I have the correct BCD device, osdevice, and path based on the drive letter that I see for the Windows partition using diskpart / list volume.
Is there anything else that might need to be edited to enable Windows to boot? In particular, are there any configuration files or registry entries that need to be changed based on the change from SATA to NVME?
uefi nvme clone
uefi nvme clone
asked yesterday
user2657480
1
New contributor
user2657480 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
user2657480
1
New contributor
user2657480 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
user2657480
1
New contributor
user2657480 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
user2657480
1
asked yesterday
user2657480
1
1
New contributor
user2657480 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
user2657480 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
user2657480 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as off-topic by Rui F Ribeiro, RalfFriedl, sebasth, JigglyNaga, Archemar 11 hours ago
- This question does not appear to be about Unix or Linux within the scope defined in the help center.
put on hold as off-topic by Rui F Ribeiro, RalfFriedl, sebasth, JigglyNaga, Archemar 11 hours ago
- This question does not appear to be about Unix or Linux within the scope defined in the help center.
hmmm sounds like an interesting problem, however I must admit that I (and probably most here) would not have as much information as somebody over at Super User would. Since this is primarily a Windows related issue, you may get better responses there.
– bgregs
yesterday
add a comment |
hmmm sounds like an interesting problem, however I must admit that I (and probably most here) would not have as much information as somebody over at Super User would. Since this is primarily a Windows related issue, you may get better responses there.
– bgregs
yesterday
hmmm sounds like an interesting problem, however I must admit that I (and probably most here) would not have as much information as somebody over at Super User would. Since this is primarily a Windows related issue, you may get better responses there.
– bgregs
yesterday
hmmm sounds like an interesting problem, however I must admit that I (and probably most here) would not have as much information as somebody over at Super User would. Since this is primarily a Windows related issue, you may get better responses there.
– bgregs
yesterday
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
hmmm sounds like an interesting problem, however I must admit that I (and probably most here) would not have as much information as somebody over at Super User would. Since this is primarily a Windows related issue, you may get better responses there.
– bgregs
yesterday