2017, v8041 Recovery Media Fails to load after Boot Menu Selection
I've got Windows 10 1607 64 bit installed on my main drive. I created a backup image of my drive and am trying to test recovery before wiping my drive. However, I'm unable to get Acronis to load (either from DVD media or USB media). I've never had this problem in the past with earlier versions of the software. I've tried both 32 and 64 bit media, but primarily 64. Once I select option 2 (Acronis True Image (64-bit)), it says the following:
Please wait...
Runtime error:
Error 0x1480012
Line Info: 0x76df0d19c4c8565a
$module: bootwiz_efia64
This is my first time using ATI 2017. Anyone else have this problem?
Thanks,
Brett


- Accedi per poter commentare

Hello Steve,
I've been using ATI since at least 2009. I have used it with this particular system before (with a CD), though it was running Windows 8.1 at the time and version 2014 (I bought 2016, but never ended up using it, and now I have 2017). I've got an Asus Maximus VI Formula motherboard. It is UEFI enabled and I believe Secure boot is enabled. I've not tried disabling it. The main disk drive is an SSD and is running in AHCI mode (no RAIDs). I ended up using the latest version of the "MVP Tool - CUSTOM ATI WINPE BUILDER" without adding any extra drivers. I was able to boot from my USB stick using that to access my ATI backup images (stored on local HDD's). This surprised me, as I've never had to jump through hoops to be able to restore before. I've usually just used the built-in recovery media builder that Acronis provides and that's done the trick. There must be something different in this version of 2017 that the developers looked over?
Kind Regards,
Brett
- Accedi per poter commentare

Brett, with each new version of the product, Acronis tends to update the standard, Linux based, Rescue media to a later Linux kernel version and that may go some way to explaining why the media works differently.
See KB 1537: Acronis Bootable Media which shows the different Linux kernels used for product versions, though this doesn't look to have been updated yet for the 2017 product media.
- Accedi per poter commentare

Brett,
You shoujld check if Secure Boot is enabled on your board. If iit is I would suspect that as the root cause. The default Linux based media can have issue with Secure Boot enabled. The WinPE version of the media offers better support for Secure Boot and would explain why it works.
- Accedi per poter commentare

Hello Brett,
There are also these three possible reasons of the bootable media boot error like you have seen:
1) error in writing the data to the media itself, be it USB stick or an optical disc. Solution for this possible cause is simply "try again with a different media"
2) issue with the files that are used by the builder to construct the media. Here you can download a pre-made .ISO image of the bootable media and burn it to a CD or DVD as a disc image. For that, sign into your account at account.acronis.com, click Downloads and then click "Bootable Media ISO". This will start the download of the bootable .iso file. When it finishes copying, right-click the .iso file in File Explorer and select "Burn disc image" and proceed with writing the media
3) this last possible cause is the most difficult to investigate and resolve - it is a compatibility issue in combination of particular versions of Acronis EFI loader, motherboard, firmware and UEFI settings. If recreating the media from the program and using the pre-made ISO image does not help, you can submit a ticket for a more in-depth investigation. In order to get the issue fixed in some update in the future, we would need to escalate such ticket to the Development Team.
Regards,
Slava
- Accedi per poter commentare