Cloned/restored Win10Pro drive to NVMe drive -- won't boot

First I used Partition Magician's copy-to-SSD function, then again tried
Macrium Reflect to restore an image from one drive to another, but in
neither case will the machine boot from that NVMe drive: "Windows failed
to start.... Insert your Windows installation disc... Click 'Repair your
computer.'"

But this fails: "unable to repair"

It complains about the file \Windows\system32\winload.exe

and then

"Status: 0xc000000e "

But that file is present on the NVMe drive.

Any alternative to reinstalling from scratch on the NVMe drive? And if I
do so, can I then easily copy everything else on top of it so I get my
original configuration back?

BTW, the NVMe drive is not connected to the motherboard (which is too
old to have that feature) but is mounted on a PCIe adapter, so it does
not show in the BIOS but shows in the boot EasyBCD boot menu. Is that
the problem? Can't the boot loader transfer control to *any* other drive?

Perce

On 2020-04-01 6:54 p.m., Percival P. Cassidy wrote:
First I used Partition Magician's copy-to-SSD function, then again tried
Macrium Reflect to restore an image from one drive to another, but in
neither case will the machine boot from that NVMe drive: "Windows failed
to start.... Insert your Windows installation disc... Click 'Repair your
computer.'"

But this fails: "unable to repair"

It complains about the file \Windows\system32\winload.exe

and then

"Status: 0xc000000e "

But that file is present on the NVMe drive.

Any alternative to reinstalling from scratch on the NVMe drive? And if I
do so, can I then easily copy everything else on top of it so I get my
original configuration back?

BTW, the NVMe drive is not connected to the motherboard (which is too
old to have that feature) but is mounted on a PCIe adapter, so it does
not show in the BIOS but shows in the boot EasyBCD boot menu. Is that
the problem? Can't the boot loader transfer control to *any* other drive?

Perce

Apparently NVMe drives mounted on a PCIe card are not bootable, It has
to be mounted in a motherboard socket, I tried this sometime ago and
found that to be true. I now have a new M/B with 2 NVMe sockets and that
works, and one useless PCIe card in my parts drawer.

Rene

Percival P. Cassidy wrote:
First I used Partition Magician's copy-to-SSD function, then again tried
Macrium Reflect to restore an image from one drive to another, but in
neither case will the machine boot from that NVMe drive: "Windows failed
to start.... Insert your Windows installation disc... Click 'Repair your
computer.'"

But this fails: "unable to repair"

It complains about the file \Windows\system32\winload.exe

and then

"Status: 0xc000000e "

But that file is present on the NVMe drive.

Any alternative to reinstalling from scratch on the NVMe drive? And if I
do so, can I then easily copy everything else on top of it so I get my
original configuration back?

BTW, the NVMe drive is not connected to the motherboard (which is too
old to have that feature) but is mounted on a PCIe adapter, so it does
not show in the BIOS but shows in the boot EasyBCD boot menu. Is that
the problem? Can't the boot loader transfer control to *any* other drive?

Perce

This link may help to answer all your Nvme questions:

https://www.win-raid.com/t871f50-Gui...UEFI-BIOS.html

If your bios cannot be modded then get a new MB.
The speed increase is worth it.
10x faster than an SSD and 30x faster than a WD Black.

Percival P. Cassidy wrote:
First I used Partition Magician's copy-to-SSD function, then again tried
Macrium Reflect to restore an image from one drive to another, but in
neither case will the machine boot from that NVMe drive: "Windows failed
to start.... Insert your Windows installation disc... Click 'Repair your
computer.'"

But this fails: "unable to repair"

It complains about the file \Windows\system32\winload.exe

and then

"Status: 0xc000000e "

But that file is present on the NVMe drive.

Any alternative to reinstalling from scratch on the NVMe drive? And if I
do so, can I then easily copy everything else on top of it so I get my
original configuration back?

BTW, the NVMe drive is not connected to the motherboard (which is too
old to have that feature) but is mounted on a PCIe adapter, so it does
not show in the BIOS but shows in the boot EasyBCD boot menu. Is that
the problem? Can't the boot loader transfer control to *any* other drive?

Perce

https://neosmart.net/wiki/0xc000000e...ection-failed/

The boot selection failed because a
required device is inaccessible boot error message [Vista+]

This implies that perhaps the driver method is not
present or not possible. The OS could be switching over
to its native driver at that point.

Another possibility, is some wrinkle of Secure Boot.
You should be able to UEFI boot without Secure Boot
being enabled. For example, under trying conditions,
I needed to set my Secure Boot to "Other OS" in the
Asus BIOS, to get Windows 7 to boot. Even though
Windows 7 is a Microsoft OS, the key for Microsoft
OSes might not work with Windows 7.

Since it sounds like you're using a native NVMe slot
and not some bodged PCI Express card, maybe the
motherboard end of things is otherwise OK. Perhaps
there is NVMe support baked into the BIOS, so
INT 0x13 calls (DOS style reads) work until
the handoff to the OS driver.

What you could look at, is boot from the previous
device, and check Device Manager and see if there
is a driver for the NVMe showing. Plus, go over
to the Disk Management window and verify the NVMe
can be "explored" and the files are visible. This
proves that the original disk had an OS NVMe driver.
If these things were not true, you'd try and get
the NVMe to be "visible" while using the original
disk, before cloning over again.

Without any articles, these are things I'd try or
look at, before sallying forth to Google.

I looked at the Neosmart one, so I could get
a nicer string to look at.

I think I also had a problem once, where winload.exe,
the signing on it had failed, and Windows then
didn't want to use the winload.exe file. But that's
probably a different failure code too.

Paul

"Percival P. Cassidy" wrote:

First I used Partition Magician's copy-to-SSD function, then again
tried Macrium Reflect to restore an image from one drive to
another, but in neither case will the machine boot from that NVMe
drive: "Windows failed to start.... Insert your Windows
installation disc... Click 'Repair your computer.'"

Do another restore. Then boot back into Macrium Reflect and do a repair.
I forget what the path is, just look around for "fix boot problems" or
whatever. You might be able to do that without a reboot after the
restore, but I would reboot first (especially to see if the problem
exists).

On 4/2/20 9:54 AM, John Doe wrote:

First I used Partition Magician's copy-to-SSD function, then again
tried Macrium Reflect to restore an image from one drive to
another, but in neither case will the machine boot from that NVMe
drive: "Windows failed to start.... Insert your Windows
installation disc... Click 'Repair your computer.'"

Do another restore. Then boot back into Macrium Reflect and do a repair.
I forget what the path is, just look around for "fix boot problems" or
whatever. You might be able to do that without a reboot after the
restore, but I would reboot first (especially to see if the problem
exists).

Already tried that -- no joy. I'm going to try the solutions in the link
posted by Paul in Houston TX.

Perce

In article ,
Percival P. Cassidy wrote:
On 4/2/20 9:54 AM, John Doe wrote:

First I used Partition Magician's copy-to-SSD function, then again
tried Macrium Reflect to restore an image from one drive to
another, but in neither case will the machine boot from that NVMe
drive: "Windows failed to start.... Insert your Windows
installation disc... Click 'Repair your computer.'"

Do another restore. Then boot back into Macrium Reflect and do a repair.
I forget what the path is, just look around for "fix boot problems" or
whatever. You might be able to do that without a reboot after the
restore, but I would reboot first (especially to see if the problem
exists).

Already tried that -- no joy. I'm going to try the solutions in the link
posted by Paul in Houston TX.

You're going to travel all the way to Texas to test it?

--
BigBusiness types (aka, Republicans/Conservatives/Independents/Liberatarians/whatevers)
don't hate big government. They *love* big government as a means for them to get
rich, sucking off the public teat. What they don't like is *democracy* - you know,
like people actually having the right to vote and stuff like that.

"Percival P. Cassidy" wrote:

John Doe wrote:

First I used Partition Magician's copy-to-SSD function, then
again tried Macrium Reflect to restore an image from one drive
to another, but in neither case will the machine boot from that
NVMe drive: "Windows failed to start.... Insert your Windows
installation disc... Click 'Repair your computer.'"

Do another restore. Then boot back into Macrium Reflect and do a
repair. I forget what the path is, just look around for "fix boot
problems" or whatever. You might be able to do that without a
reboot after the restore, but I would reboot first (especially to
see if the problem exists).

Already tried that

Have you tried a clean install?

On 2020-04-02 10:28 a.m., Percival P. Cassidy wrote:
On 4/2/20 9:54 AM, John Doe wrote:

First I used Partition Magician's copy-to-SSD function, then again
tried Macrium Reflect to restore an image from one drive to
another, but in neither case will the machine boot from that NVMe
drive: "Windows failed to start.... Insert your Windows
installation disc... Click 'Repair your computer.'"

Do another restore. Then boot back into Macrium Reflect and do a repair.
I forget what the path is, just look around for "fix boot problems" or
whatever. You might be able to do that without a reboot after the
restore, but I would reboot first (especially to see if the problem
exists).

Already tried that -- no joy. I'm going to try the solutions in the link
posted by Paul in Houston TX.

Perce


That looks like a good article, sure worth trying some of their fixes.

Rene

It wants to be a netcop while it acts like a perpetrator.
This idiotic troll doesn't practice what it preaches...

--
(Kenny McCormack) wrote:

Path: not-for-mail
From: (Kenny McCormack)
Newsgroups: alt.comp.os.windows-10
Subject: Cloned/restored Win10Pro drive to NVMe drive -- won't boot
Date: Thu, 2 Apr 2020 16:19:13 -0000 (UTC)
Organization: The official candy of the new Millennium
Message-ID:
References:
Injection-Date: Thu, 2 Apr 2020 16:19:13 -0000 (UTC)
Injection-Info: news.xmission.com; posting-host="shell.xmission.com:166.70.8.4"; logging-data="21868"; "
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: (Kenny McCormack)
X-Received-Bytes: 2110
X-Received-Body-CRC: 4205120720

In article ,
Percival P. Cassidy wrote:
On 4/2/20 9:54 AM, John Doe wrote:

First I used Partition Magician's copy-to-SSD function, then again
tried Macrium Reflect to restore an image from one drive to
another, but in neither case will the machine boot from that NVMe
drive: "Windows failed to start.... Insert your Windows
installation disc... Click 'Repair your computer.'"

Do another restore. Then boot back into Macrium Reflect and do a repair.
I forget what the path is, just look around for "fix boot problems" or
whatever. You might be able to do that without a reboot after the
restore, but I would reboot first (especially to see if the problem
exists).

Already tried that -- no joy. I'm going to try the solutions in the link
posted by Paul in Houston TX.

You're going to travel all the way to Texas to test it?

--
BigBusiness types (aka, Republicans/Conservatives/Independents/Liberatarians/whatevers)
don't hate big government. They *love* big government as a means for them to get
rich, sucking off the public teat. What they don't like is *democracy* - you know,
like people actually having the right to vote and stuff like that.