Skip to main content

UEFI WIN10 64-bit can't be recovered properly

Thread needs solution

Installed UEFI windows10 version1809 64-bit OS in mSATA 32GB. Backup those OS in USB using Acronis True Image 2018.

From existing backup Image in USB, I try to recover the image in another SATADOM 32GB by Acronis. Select Existing backup image. then go to Recovery page, click "Recovery options", default 'disk' method, in that disk type image restoring will show error message like windows will not boot. Hence I have done by Partitions type shown in Recoverypage.jpg ,selecting the image which has i)Recovery partitions ii)EFI partitions iii)Unnamed partition. No error popup message shown Partitions method. I gave "Recover Now" option.

After successful completion of restore image in SATADOM disk. Then I boot system with SATADOM newly restore images, it shows error code 0xc0000359 & winload.efi file is missing shown in Booterror.jpg

note: I have not faced these kind of issue in Legacy win10 version1809 64bit OS.

 

0 Users found this helpful

Raj, welcome to these public User Forums.

I do not see any screen image files with your post.

Please can you confirm how you are doing this Recovery action?
Are you booting from the Acronis Rescue Media or doing this from within Windows 10?
If booting from the Rescue Media, are you booting in UEFI mode?

The error message that says Windows will not boot is caused normally because the Recovery is being done for a UEFI boot system from Rescue Media booted in Legacy mode, which then will migrate the UEFI / GPT backup to being BIOS MBR format instead.

For a UEFI boot system, you must boot the Rescue Media in the same mode to avoid any migration away from GPT.

See KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media for more information.

Please also ensure only one of the drives is connected upon OS boot.if a UEFI bios detects 2 "identical" disks with the same boot priority and OS information, the bios will attempt to notify the bootloader information for both and can make them unbootable.

Definitely make sure you boot the rescue media in UEFI mode though! This is the same requirement as Windows OS install media. If you want/need legacy, boot in legacy mode. If you want/need UEFI, boot in UEFI mode.

Generally speaking, you can convert from Legacy to UEFI/GPT with Acronis rescue media, but not revert from UEFI to legacy (and remain bootable). 

Have you tried going back to the disk method and ignoring the error? I think it shows the error because it's detecting it as a flash drive. I'd try it and see if it's any different. 

Also just to be sure, it is formatted as GPT? It should be.

Last, let it fail to boot 3 times. If you can get an F8 prompt to boot in safe mode on the 4th attempt, you might be able to press on. I had a similar experience going from a standard SATA to my first PCIe NVMe that turned out to be just a "locked disk" which resolved itself as soon as safe boot was applied and then it booted fine after that.

I don't much about the satadom but it should essentially be the same as a SATA drive , just in ultra compact form, so it should be possible to restore and boot from.

Are there any special drivers needed for it too?

I had the same issue and tried a bunch of things.  I'm not sure which one, but some of the last steps I did and it came back was "Disable Block SID Authentication in TCG Storage", this is probably similar to temporarily disabling EFI Security (not sure if this was needed).

I got the error again, so I went into recovery environment and then went to "Safe Mode with Prompt" to just try anything at this point not expecting anything.  I was surprised after reboot, my login screen came up and asked for my PIN.  I went in and got a prompt.  Typed "exit" and rebooted.  Behold, it booted normally.

God, what a cluster!  I use Acronis because it has saved my bacon many times (and I also do traditional file clone/synch in case Acronis can't recover)...but each time I have to recover it is an adventure and hours long "figuring out EFI and Windows boot crap".  I don't use Apple products, but I can see why folks use it as I hear "Time Machine" just works.