Salta al contenuto principale

Recovery problems

Thread needs solution

Two problems today.

 

1. I have Startup Recovery Manager activated. Today, boot up resulted in "Acronis Loader No Configuration File", and I couldn't get past this. Why should this happen? Ironic that the programme that was supposed to help if I couldn't get into Windows stopped me getting into Windows!

2. My Recovery CDs also failed to run. After reinstalling Windows 10 and Acronis and using a 10 day old backup, I eventually got the computer working again. I then remade the Recovery CDs, but always get this error message in the  file below - how do i get round this and get working CDs?

Allegato Dimensione
Capture.JPG 35.53 KB
1 Users found this helpful

Tom, some more information is needed here to understand these issues?

Have you been able to use the F11 - ASRM hotkey on boot with this computer system to get into the standalone Acronis application?

Have you been able to create the Acronis Rescue Media CD without problem previously?

If the answer to the above questions is yes, then what has changed recently since the last time all was working OK?

Another question: what type of computer system do you have?  Is this a Legacy BIOS system or is it an UEFI system with Secure Boot enabled?

ASRM uses a Linux OS kernel in order to launch the Acronis application, where Secure Boot may not allow this to boot.  Some Rescue Media may also be Linux based depending on how it is built or if it was created on an earlier version of ATI.

In risposta a di truwrikodrorow…

Hello Steve,

 

I only recently moved to 2018 version from 2015 version and can't say if I've used F11 with this version, though I know the option always comes up each time I boot the computer - this time, we never got as far as that message. As far as I know, all I did the day before was read some emails and browse, unless Windows sneakingly added an update

My 2015 rescue disk runs with no problem on the same computer.and F11 has always worked with version 2015

My computer was built by MESH - I don't know how to answer the question about Legacy Boot etc.

I eventually had to restore Win 10, install Lastpass and Acronis 2018 and install a backup and it now behaves in terms of F11 message, but still gives this error for the rescue CDs

 

Hope this helps - thanks for the reply

 

Tom, thanks for the further information.

Following on from your restore of Win 10 and reinstall of ATI 2018, can you actually press the F11 key on boot and get into the ASRM application environment, not just see that the F11 message is shown?

In risposta a di truwrikodrorow…

Hi, Steve,

 

Just tried it and the answer is Yes (after a message asking for Linus kernel something or other [command line?] - answer quiet)

Tom, that is good that F11 is working and therefore any of the Acronis Rescue Media should also be capable of running too.

I have never seen the error you showed in your screen image at the start of this topic, so the next question has to be whether your recovery media is able to boot too?

Note: run the msinfo32 program and check the BIOS mode setting shown in the report, as this is how any recovery media should also be booted.

See KB 59877: Acronis True Image 2017: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media which may be helpful.

In risposta a di truwrikodrorow…

Hi Steve,

 

The error message I mentioned was when I try to make the recovery CDs, not when running them.

Just tested:

- using the 2018 CD, I have to click on any key to boot via the CD, then it whirs for 2 min and eventually starts Acronis.

The 2015 one boots automatically and immediately, then says loading Acronis loader and loads Acronis

Tom, Acronis have moved away from defaulting to creating Linux based rescue media (CD or USB) with ATI 2018, but one downside of this is that the new WinPE media can be a little slower to boot as there is more Windows 'junk' code to get through in the boot process!

I have not seen any other reports in these forums of the strange error from your screen shot for when creating the CD media!

In risposta a di truwrikodrorow…

Hi Steve,

This move to a different way of creating rescue media - there is no option given for creating different types, yes? (or did I miss it). And does whatever it's based on now explain why it asks me to click on any key to run the CD when it didn't ask in 2015 version?

Tom, please see KB 60091: Acronis True Image 2018: how Simple bootable media creation mode works and KB 60820: Acronis True Image 2018: how to create bootable media  which describe the new process for rescue media in the 2018 product.

The main reason for having the Click any key to run the CD is to prevent ATI booting automatically if the CD is left in the drive when you want to boot into Windows.

 

In risposta a di truwrikodrorow…

Hi Steve, Simple version of KB60820 is exactly what I did and the steps aren't any different from previous versions - you select Simple, select CD and go.

I've now had a reply from Acronis that is essentially a waste of time - first suggestion for getting round getting stuck at No Configuration File is to boot into Windows, then run Acronis and turn off Recovery Manager. Since I'd clearly told them I couldn't get INTO Windows, not a lot of help.

 

I've sent them the mysterious error message while creating the Rescue CD