Acronis recovery from archive fails to load

Windows 10 Home AMD 64bit 12GB memory. Testing Acronis Archive and
recovery.
Archived system using Acronis. Archive contains MBR, Small boot
partition, and C partition.
Recovered all 3 items to new disc, apparently OK, but new system fails
to boot with error code C000000e, and refers to
C:\Windows\System32\winload.exe. Windows repair disc fails to fix this
error.
I have repeated this several times always with the same error.
NB The original system continues to load OK!
What am I missing?

Oldster wrote:
Windows 10 Home AMD 64bit 12GB memory. Testing Acronis Archive and
recovery.
Archived system using Acronis. Archive contains MBR, Small boot
partition, and C partition.
Recovered all 3 items to new disc, apparently OK, but new system fails
to boot with error code C000000e, and refers to
C:\Windows\System32\winload.exe. Windows repair disc fails to fix this
error.
I have repeated this several times always with the same error.
NB The original system continues to load OK!
What am I missing?

STATUS_NO_SUCH_DEVICE 0xC000000E

That suggests a pointer in the BCD is referring to
something, where the identifier has been changed.

I hope the original disk and the clone of the disk,
have not been connected at the same time while you're
practicing booting.

"Good" software changes the identifiers in BCD as well
as changing the GUID of the partitions pointed to by the
BCD. This allows the disks to be relatively independent
of one another. If the disks were identical (in the "dd"
copied sense), you might be in a lot more trouble. You don't
really want the disk copies to be "that exact". It's better
if the cloning or archiving tool, gives the new disk its
own set of "randomly assigned, self consistent" identifiers.
That's why these third party tools work so well. The clone
is not "forensic quality", on purpose.

This is the tool I use to fix "no boot" problems. I used
this just the other day, when my Win10 boot SSD decided
to take a nose dive. It worked. The boot repair is available
on the macrium emergency boot CD, so even if a system doesn't boot,
you can attempt to fix the BCD and friends, without
moving the disk around or anything.

http://reflect.macrium.com/help/v5/r...t_problems.htm

*******

On the old (working) system.

1) Install Macrium 6.3.1849 and make an emergency boot CD.
This product is free. No adware. This first file is a
stub downloaded. It has an interface with tick boxes,
so you can select the proper two (total) files to download.

http://updates.macrium.com/reflect/v6/ReflectDLv6.exe

gives downloader 6.0.553.0

It has a 32 bit or 64 bit option, to match your working machine.
This is the main program.

v6.3.1849_reflect_setup_free_x86.exe 44,303,520 bytes

SHA1: A11293417C4A48972D104B94B5C2B530C375774A

v6.3.1849_reflect_setup_free_x64.exe 46,645,904 bytes

SHA1: 2AFF03BD9AFD677F65647F890026F4D239C70005

To make the emergency CD, the download will look for a second
file, a WINPE. Either WINPE5 or WINPE10 will suffice, as both
support USB3 storage devices. Earlier versions don't and only
run at USB2 speed.

A WinPE from Microsoft, is maybe 500MB. Macrium will massage the
larger download and compress it into a ZIP when it selects the
parts it really wanted.

The "install right away" button is pretty aggressive. I like to
finish the download first. and then use the two files in a more
leisurely fashion. After you select the main program download
and the WinPE download type, re-check the "Install Now" button and
untick it. Check check and recheck that, because that button
will re-enable itself if you look sideways at it.

2) Once the software is installed, find the emergency boot CD option
in the menu. I like to make an ISO9660 file and burn it with Imgburn,
rather than use PrimoBurn? included in the package.

3) Boot the affected machine and its clone disk with the Rescue CD as your
OS. Select the Repair option from one of the Macrium CD menus. It'll scan
first for all OSes. You describe having only one OS, so that part should be
easy. It will offer to repair four things, and you can repair all of
them for your first try (four tick boxes).

Then reboot and see what happens, now using the HDD as your
boot device, and with the CD ejected.

In some cases, I've had to do Macrium Boot Repair followed by
Windows Boot Repair. But the last time I tried, only the former
was needed. As the Windows Boot repair by itself didn't work.

*******

If you're a glutton for punishment, you don't need any third party software.

Boot the win10 installer DVD.

Boot to Command Prompt

bcdedit /store C:\boot\BCD

and it should enumerate. If a field is blank
instead of having a drive letter, that means something
is unlinked. Use web articles to repair, as a lot has
been written since BCD showed up. At first, it was
a total vacuum on recipes, but now there are quite a few.
I've manually re-entered drive letters in there and fixed
stuff. It can be done. The bcdedit command supports
"offline" repair of boot partitions by editing the BCD.

If you were doing it on your *working* system, using just

bcdedit

does an online scan and uses the currently booted BCD info
for enumeration purposes. Specifying another partition
using /store is for other boot partitions or setups
you're not using at the moment. so doing just "bcdedit"
on the working system, in Command Prompt, will give you an
idea of what fields were supposed to be populated.

The MBR boot flag could point to System Reserved and
the System Reserved could have a \boot in it and a BCD.
Or, you can move \boot and BCD to C: and make a
"single partition" setup, as examples. The boot flag
goes on the partition that has that sort of material.
And this is partially why, you have to "dir" the partitions
and make sure you found where \boot is hiding and use
the drive letter from that partition in the BCD command.

That's just to point out the kind of fun you're missing
by using the Macrium repair. BCDedit fixes lots of problems,
while things like bootsect can put back a boot sector
if it was missing. That's unlikely to be the problem though.
Clones don't usually miss that bit.

Acronis should also have a boot repair. The idea is
not foreign. A barely minimal repair effort might be
about three commands, and so an inept company can do
at least that much. Better quality repair jobs also
look in the Registry for stuff. Macrium logs a number
of things it's messing with in the registry some times,
and it seems to be pretty good at preventing boot
problems after cloning.

Paul

Oldster wrote:
****Windows 10 Home AMD 64bit 12GB memory. Testing Acronis Archive and
recovery.
Archived system using Acronis. Archive contains MBR, Small boot partition,
and C partition.
Recovered all 3 items to new disc, apparently OK, but new system fails to
boot with error code C000000e, and refers to
C:\Windows\System32\winload.exe. Windows repair disc fails to fix this error.
I have repeated this several times always with the same error.
NB The original system continues to load OK!
What am I missing?

Windows 10 version ?
Repair disk created on same version that was in place when the Acronis image
was created ?

Acronis Version 2015, 2016 or 2017 ?

Did you use Acronis Universal Restore
https://kb.acronis.com/content/45432

Do you have(did you create) Acronis Bootable Media with Acronis Universal
Restore ?

If earlier, per Acronis https://kb.acronis.com/content/56196
qp
Older versions of Acronis products
Support of Windows 10 will not be implemented into older versions of Acronis
products (e.g. Acronis True Image 2014 or older, Acronis Backup & Recovery
11 or older, Acronis Snap Deploy 4 or older), as Acronis development team
works on the current versions only. Stable functioning of older products on
Windows 10 is not guaranteed.
/qp

OEM built Windows 10 Machine ?
- if so was it as-shipped with TPM 2.0

UEFI, UEFI/BIOS or BIOS ?

GPT or MBR ?
- you mentioned MBR, but just checking for sure

Secure Boot Enabled on the old disk ?
- If so, was it disabled prior to image creation and left disabled prior
to restoration to new disk ?

Device Encryption enabled ?
TPM 2.0 would be present for Device Encryption on W10 Home

Did the original disk have a Recovery Partition ?

Did you use the Micrsoft Media Creation Tool to create Win10 USB media ?
- It serves the same purpose as a Recovery drive


--
...w¡ñ§±¤ñ
msft mvp windows experience 2007-2016, insider mvp 2016-2018

On 19/01/2018 10:50, ...w¡ñ§±¤ñ wrote:
Oldster wrote:
*****Windows 10 Home AMD 64bit 12GB memory. Testing Acronis Archive
and recovery.
Archived system using Acronis. Archive contains MBR, Small boot
partition, and C partition.
Recovered all 3 items to new disc, apparently OK, but new system fails
to boot with error code C000000e, and refers to
C:\Windows\System32\winload.exe. Windows repair disc fails to fix this
error.
I have repeated this several times always with the same error.
NB The original system continues to load OK!
What am I missing?

Windows 10 version ?
1709 16299.192
Repair disk created on same version that was in place when the Acronis
image was created ?
yes

Acronis Version 2015, 2016 or 2017 ?
2018

Did you use Acronis Universal Restore
*https://kb.acronis.com/content/45432
no

Do you have(did you create) Acronis Bootable Media with Acronis
Universal Restore ?
no

If earlier, per Acronis https://kb.acronis.com/content/56196
qp
Older versions of Acronis products
Support of Windows 10 will not be implemented into older versions of
Acronis products (e.g. Acronis True Image 2014 or older, Acronis Backup
& Recovery 11 or older, Acronis Snap Deploy 4 or older), as Acronis
development team works on the current versions only. Stable functioning
of older products on Windows 10 is not guaranteed.
/qp

OEM built Windows 10 Machine ?
no
*- if so was it as-shipped with TPM 2.0

UEFI, UEFI/BIOS or BIOS ?
UEFI/BIOS

GPT or MBR ?
*- you mentioned MBR, but just checking for sure
MBR

Secure Boot Enabled on the old disk ?
No such thing apparent that I can find!
*- If so, was it disabled prior to image creation and left disabled
prior to restoration to new disk ?

Device Encryption enabled ?
No
*TPM 2.0 would be present for Device Encryption on W10 Home

Did the original disk have a Recovery Partition ?
No

Did you use the Micrsoft Media Creation Tool to create Win10 USB media ?
Yes
*- It serves the same purpose as a Recovery drive

On 19/01/2018 09:41, Oldster wrote:
Â*Â*Â*Â*Windows 10 Home AMD 64bit 12GB memory. Testing Acronis Archive and
recovery.
Archived system using Acronis. Archive contains MBR, Small boot
partition, and C partition.
Recovered all 3 items to new disc, apparently OK, but new system fails
to boot with error code C000000e, and refers to
C:\Windows\System32\winload.exe. Windows repair disc fails to fix this
error.
I have repeated this several times always with the same error.
NB The original system continues to load OK!
What am I missing?

Problem believed solved.
It appears that the boot style in the BIOS of my motherboard has 3
settings, EFI, BOTH, Non-EFI. The setting I found was BOTH.
The disc I was recovering was "Non-EFI" but the software I was using,
presumably taken from the BIOS, probably thought the disc should be EFI.
Thus confusion! Changing the BIOS to Non-EFI solved the problem!