Salta al contenuto principale

"Acronis Loader - Unable to run boot menu"

Thread needs solution

Hi all,

Currently i have a problem with my acronis true image 2016. i'm using Windows 7 64 bit, after i'm done backup my local C drive, i activate F11 function. After i reboot my PC i hit F11 then this message appreared "Acronis Loader - Unable to run boot menu"

I saved my .tib file in local D drive.

Can someone help me please.

Thank You

 

0 Users found this helpful

Hello Khairul, 

I am not sure that I understand what the problem is here?

When you backup your local C: drive, are you doing so from within Windows 7 using the Acronis application GUI or are you doing an offline backup using the Acronis Startup Recovery Manager - where you press the F11 key at boot to invoke the ASRM ?

If the backup has run successfully, and saved your backup image (.TIB) file to your D: drive, are you rebooting and trying to invoke the F11 - ASRM utility at that time?

Or are you saying that you are trying to use F11 - ASRM and it is not working?

Sorry for asking lots of questions before we can try to help you.

Note: If the problem is only with ASRM, then you can try to remove the Startup Recovery Manager and then Activate it again.

See the ATIH 2016 User Guide http://www.acronis.com/en-us/support/documentation/ATI2016/#10119.html

Hi Steve Smith,

Thanks for fast reply. Yes, i'm backup my whole C: drive using Acronis GUI and save the .tib file in D: drive. After finished backup i activate Acronis Startup Manager to activate F11 function. Then reboot my PC.

After the BIOS screen, this message will appeare "Starting Acronis Loader" "Press F11 for Acronis Startup Manger" after i hit F11 this message appeare "Acronis Loader - Unable to run boot menu"

Here i attached a picture for your reference. 

Please advise for further step to troubleshoot this issue.

Thank you

Allegato Dimensione
351226-128218.png 3.6 KB
351226-128221.jpg 1.22 MB

Hello Khairul, thank you for the additional information.

Have you installed the latest build 6559 version of ATIH 2016 - if not, I would recommend doing so.

Have you tried removing the Acronis Startup Recovery Manager and reinstalling it again?

See KB document for Troubleshooting the Acronis Startup Recovery Manager

Hi Steve Smith,

I already install the latest version of Acronis True Image 2016. 

I already uninstall Acronis True Image 2016 4 times. The result are still the same.

I will try another shot by following your suggestion.

May i know what the cause of this issue?

Please kindly advise further step to solve this issue.

Thank you

 

Hello Khairul,

I am not sure that I fully understand what the problem is here?

Has the Acronis Startup Recovery Manager (ASRM) ever worked on your computer?
Have you ever been able to press the F11 key at boot time and launch the ASRM environment successfully?

Have you tried following the steps shown in the KB document for Troubleshooting the Acronis Startup Recovery Manager?

Hi Steve Smith,

Yes, i already activated the ASRM after i finished backup. 

Yes, i was able to press F11 but i was unable to enter ASRM environment because of this issue "acronis loader - unable to run boot menu".

I already follow the step from the link that you give me. Before this i already install Acronis True Image to 10 PC's, and never face this type of problem

I also not sure what the cause is. Do you ever face this problem before? Do you know what is the cause? I really want to know what is the cause.

Please kindly advise further step to troubleshoot this issue.

Thank You.

Best Regards,

Khairul

 

Hello Khairul,

If I understand you correctly, I apologise if I do not, ASRM has never worked on this one particular computer, but works fine on up to 10 other PC's.

I have not had this problem myself but I also no longer use ASRM because of other problems that it has caused such as revealing hidden partitions and allocating drive letters to them.

Please can you create the standard Acronis Rescue Media or download a copy of the ISO for the bootable media from your Acronis Account and test to see if this gives you the same error?  The standard Linux based rescue media should be identical to the ASRM in operation and would be a good test to try to isolate this issue further.

Hi Steve Smith,

Yes, you are correct. Only one PC that i working right now got this issue. Other PC's that i worked before got no problem with ASRM.

Ok, i will try create the standard Acronis Rescue Media. I'll give you the result after i test it.

Thank you for your help.

Best regards,

Khairul

I just had the same problem today.

 

I have NEVER before had any problems tring to restore from CD-based rescue media.

Today though, with an image generated on the latest 2016 version of Acronis, I got a page full of unitelligable codes follwed by something like "unable to run boot media".

Fortunately for me I had a laptop and was able to generate another CD using the WINPE-Based media and this seemed to work.

I was VERY lucky I had another PC!

What have you done to cause this issue?

Regards

Mark

Mark,

My guess is that your media is corrupt - perhaps a bad burn, perhaps a bad disc.  I have had too much bad luck with bad discs so have stopped using them and only use USB media now.  

Also, the Acronis media can boot in UEFI or Legacy mode.  When using a USB, it is much easier to pick one or the other using your one-time boot menu so that you can specifically pick one or the other.  I believe that even though the CD's support both as well, many systems default to trying to boot the newer media in Legacy mode and may not be possible if secure boot is not disabled or if the bios doesn't allow it.  Using a USB drive should hopefully provide a better boot experience for you.

I would build a USB bootable flash drive with the media creator and test it on both systems to make sure it works on them before you run into another need to use the media type of scenario.  

Personally, I don't use ASRM or let any software modify my OS bootloader - if something goes wrong with the boot, then it won't be able to restore the original bootloader automatically.  A lot of people who attempt to start a Clone from within Windows, end up with this problem becuase there bios is not configured correctly to allow the boot after this change.  Using your offline recovery media to boot into Acronis will avoid any chance of the Windows bootloader from being modified and will prevent bootup issues.  Long story short... if you plan to either clone or do a disk/parption restore... don't start the process in Windows and use your newly created UsB recovery media to start the process instead and this will alleviate unnecessary headaches.

Hi

I tried four different disks (two CD and two DVD) and two different DVD burners so I doubt it's media.

(Especially since the WINPE version burnt with no problems using the same batch of disks and burners).

I also tried to generate USB media on two different USB sticks.

Neither were recognised by my PC (Asus p67pE mobo).

 

I've used Acronis TI for many years.

I had no problem with versions prior to 2016 on the same HW with CDs.

In fact the first version of TI 2016 I purchased (and the first update I got), I made sure to test out with bootable CDs and it worked fine.

Something has changed along the line in the last few revisions.

Regards

Mark

Mark Allison wrote:

Fortunately for me I had a laptop and was able to generate another CD using the WINPE-Based media and this seemed to work.

I was VERY lucky I had another PC!

Mark, have you tried creating the standard Rescue Media on your laptop given that you were able to create the WinPE media there and that worked for you?

Am I correct in assuming that both computers are running ATIH 2016 build 6571 so that we are comparing apples with apples (not pears)?

Have you tested the rescue media on both computers, do they both give the same issue?

With regards to media - we had one user in the forum who spent weeks trying to resolve a similar problem that was eventually proven to be the brand of media being used - Verbatim IIRC.  Changing to a different brand and the issue was solved immediately!