Direkt zum Inhalt

Critcal "Bug" with Rescue Media & Acronis Startup Recovery Manager!

Thread needs solution

Hi, 

a couple of days ago I upgraded Acronis from 2012 to 2016. So far I am ver satisfied with it, the program itself works perfectly for me.

But today I created a Rescue Media Disk from inside of ATIH 2016, the DVD creating was successful. So I wanted to try it out - just to be sure in case of emergency. 

I restarted my PC and booted from the rescue disk. I saw the blue Acronis screen where I could select to start Acronis, Acronis 64 bit and so on. So I selected Acronis, and saw a black screen with the Acronis logo in the top left corner, under it the text: "Loading, please wait...". After a few seconds it disappears and "normally" the Acronis interface should show up now - but nothing happens. The screen just turns black.
I waited about 10 min. for something to show up but -> nothing! Even the disc drive stops doing anything (no sounds, no LED to be busy). 

Then I activated the "Acronis Startup Recovery Manager", removed the Rescue disk and rebooted. I pressed F11, selected Acronis and it was exactly the same. So in a case of emergency, I have no chance to start a recovery! There must be a critical bug in the whole rescue system, my old ATIH 2012 Rescue disk works perfectly..

Is this a known bug? Please push out an update as soon as possible!

0 Users found this helpful

Markus,

We've had a few people report bad media as an issue - one guy had verbatim disks and flash drives and they all failed - always.  He switched brands and his media started working correctly.  Maybe try another burn and test again, but if it's still bad, try a USB flash drive, or another type of disk.

I have noticed that boot times do seem to be a little slower, but ultimately, ti usually boots up within a minute at most.

The other thing to make sure is that you're booting your media to match how your OS was installed.  Boot it in legacy mode if you have a Legacy OS install (blue screen with graphic icons for the menu - this seems to be how you have booted based upon your description above), or in UEFI mode for a UEFI OS install (black screen with thie Dos-like letters for the menu).  

To verify how you boot the media, use your one time boot menu or boot override menu and specifically select the correct boot method that matches your OS install type.

Thanks for your reply Bobbo_3C0X,

Bobbo_3C0X1 wrote:

We've had a few people report bad media as an issue - one guy had verbatim disks and flash drives and they all failed - always.  He switched brands and his media started working correctly.  Maybe try another burn and test again, but if it's still bad, try a USB flash drive, or another type of disk.

I went this morning to the city and bought high-quality Sony DVD-Rs and a USB-Stick to test your suggestion. 
Creating the rescue media on both, DVD and USB, was successful. I can start with both my PC, select Acronis and so on until it "should" show up - but again, nothing happens. So I'm very sure now, that it's not the fault of the DVD or USB-Stick. 

Bobbo_3C0X1 wrote:

The other thing to make sure is that you're booting your media to match how your OS was installed.  Boot it in legacy mode if you have a Legacy OS install (blue screen with graphic icons for the menu - this seems to be how you have booted based upon your description above), or in UEFI mode for a UEFI OS install (black screen with thie Dos-like letters for the menu).  

To verify how you boot the media, use your one time boot menu or boot override menu and specifically select the correct boot method that matches your OS install type.

I'm not quite sure which type I have, I think it's UEFI. I made a screenshot for you of my BIOS (attached files).
Furthermore, I made screenshots of every different screen I can see while trying to run Acronis. They are arranged in 1,2,3 and 4.
The last, "4_Screenshot" might be uninteresting, it's the state directly after "3_Screenshot" with the lines "Acronis Loading please wait". I left my PC in this state for about 20 min - but nothing happens.

I am really helpless and need help urgently!

 

Anhang Größe
358918-129220.jpg 386.44 KB
358918-129223.jpg 598.62 KB
358918-129226.jpg 369.44 KB
358918-129229.jpg 405.38 KB
358918-129232.jpg 330.85 KB

Markus, your image of your BIOS shows that this is UEFI but your screenshot 1 shows the Legacy main menu for the Acronis boot media (blue screen with graphics).

Please run the msinfo32.exe utility from within Windows and look for the information shown in my screenshot attached below, in particular, the BIOS Mode that is shown.  This should state either Legacy or UEFI to show exactly which mode your Windows OS boots in, that you need to match when booting from the Acronis bootable media.

The other check you should look at is the Secure Boot State - you must not have Secure Boot enabled in BIOS in order to boot correctly in UEFI mode from the Acronis bootable media.

Anhang Größe
358938-129238.png 14.01 KB

Hi Steve Smith, thanks for your reply. 

I run msinfo32.exe but I can't find my BIOS mode in there. It looks completely different to your screenshot. I'll attach a screenshot of my system information from msinfo32.exe. Maybe you can see more than I can...

Furthermore, there's nothing about Secure Boot State, I'll look into my BIOS and try to find such an entry. 

Anhang Größe
358988-129247.jpg 114.54 KB

Maybe we're now one step closer:

I found an option to boot my USB-Stick in UEFI mode (there's no such an option for my dvd device).
--> Screenshot 1

When I do it, Acronis fails to start and reports an "EFI runtime error" 
--> Screenshot 2

I also tried once again booting from my ATIH 2012 rescrue DVD and this works perfectly! So I'm very sure it's a bug in the new 2016 system thing.

Anhang Größe
358992-129250.jpg 682.4 KB
358992-129253.jpg 1.05 MB

Hi Markus,

I don't think so. I have v6569 media and can boot it on a multitude of different makes/models from different manufacturers in both UEFI and Legacy mode.  I just tested on my home PC build (gigabyte motherboard), varios Dell Latitude and Precision laptops, an Asus T200 transformer and an HP DM1Z netbook - all no issues.  OK - one issue, at one point it did seem to hang after making the UEFI selection and the initial Acronis logo - I waited at least 5 minutes where it normally boots in about 30 seconds on the same machine.  I then powered off, moved to another USB port and it booted up as expected.  I went back to the original USB port and booted as expected again so not sure what happened that time, but suspect somethign with the actual USB port or the USB drive that one time.

2012 only supported Legacy mode - UEFI wasn't an option so it would always boot in legacy mode, making things a bit more simple.

2016 can boot legacy or UEFI, but the bios has to be setup to support different boot types as well.  Often times, secure boot must be disabled to boot into USB drives as UEFI.  Some motherboards require that you move the boot order of the USB drive to the #1 position as well. 

Other times, USB drives appear to work fine, but because they have been formatted by other tools (let's say Macrium reflect that adds it's own bootloader, or another Linux distro of some type), there are hidden partitions on the flash drive that Windows can't see or detect, but cause boot issues.  I would run diskpart /clean on the thumb drive first.  Go back into Windows disk management and initialize the drive and assign a drive lettrer.  Then run fat32format.exe against that new drive letter and that will ensure there are no hidden paritions lurking on the USB drive. 

Then, how are you creating the bootable media?  From within Acronis 2016 v6569 or using the universal restore media builder?  Make sure to use the one in Acronis 2016 v6569 first.  If that has the same results, then try creqating it with the Universal REstore media builder instead and see if the behavior is the same or not.  The latest version of Universal Restore is v6027 and should be in your online account download.  If you have an older version this could be part of the issue if it's not directly related to your bios.