Direkt zum Inhalt

Acronis System Recovery Manager (F11 - bootloader) enabled after system recovery.

Thread needs solution

Does anyone know how to prevent Acronis System Recovery Manager from being enabled by default when recovering disks/partitions using the WinRE recovery medium?

The full system backup was taken from a PC that didn’t have ASRM enabled, as I prefer to use a Windows Bootloader.

I can’t find anything in the documentation that describes this as being the default behaviour, but more importantly how to control whether ASRM is activated as part of the recovery process.

I ended up rebuilding my gaming PC from scratch, as I wasn’t happy to see the Acronis Bootloader - Press F11 message that I was greeted. It also gave me an extra EFI partition. I wasn’t able to successfully upgrade Windows 10 from then on, hence the reason for the rebuild.

Activating ASRM as part of a system restore shouldn’t be a default.

0 Users found this helpful

rwit, welcome to these User Forums.

Sorry but I have never heard of this particular behaviour being reported in these forums, with ASRM being enabled by default following a system restore, and I have never experienced this behaviour for any restores that I have done myself.

I do not use ASRM myself as this would be of no help in the event of any fatal disk failure.

I would suggest opening a Support Case direct with Acronis Support if you want to investigate this further, but they may want you to be able to try to recreate the issue, or perhaps to be able to look at the backup .tib file for diagnostic purposes.

Hi Steve,

This was the first time using Acronis True Image 2018 to recover my system, as I have only ever used earlier versions of Acronis to do this job previously and never had ASRM turn up uninvited.  This should only happen when you run the tool.

Thanks for the advice, but I'm going to mark this up as another occasion when the tech wasn't there when I needed it.  At the time I wanted to get my system up and running as quickly as possible.  Unfortunately, it didn't work out that way for me.

I don't have another system to recreate the problem on and I'm definitely not using this one as it has taken me hours to rebuild and the idea of submitting a .tib file with my actual data on it doesn't appeal to me.  Therefore I don't think I'll be taking this up with support - but thanks all the same.

Just wanted to know how ASRM ended up on my system without explicitly running the ASRM tool?  I've never liked surprises!

 

Understand your situation and would do the same myself (not wanting to upset a working system after going through all the pain of rebuilding it!).

Sorry that I have no explanation for how ASRM got installed when it had not been so when your backup image was created, I can only repeat that this is a totally new scenario to me that hasn't been reported by anyone else in these forums AFAIK, and never seen personally.  Chalk one up for computer gremlins methinks!

Hey everyone,

Thought it only right to update everyone about this.

I know that I said that I wasn’t going to bother trying to recreate the problem, but I did and the good news is that the recovery of my rebuilt system was a success.

Used the WinRE recovery media burnt onto a USB thumb drive to boot my system and recovered successfully to my 1TB HDD. The system booted up without a problem but was significantly slower than my SSD - which was a nice reminder of why I got the SSD in the first place.

Rebooted from SSD and now in the process of recovering the original data back to the HDD.

I can only put the problem down to the fact that at some point in an earlier system incarnation, I had activated ASRM and made a botch of removing it properly.  This is the only reason I can think of that caused the Acronis bootloader to appear.

What I have learned from this is that Acronis True Image is a reliable product, when used correctly and also never to bother activating ASRM because it messes about with the bootloader and Windows 10 upgrades don’t like it. Further more as Steve pointed out - whats’s the point in having ASRM on a failed disk.  Always boot up from recovery media and I seem to have better luck adding additional drivers to WinRE than I’ve had with WinPE.

Cheers,

Russ

Russ, many thanks for the further update and positive feedback.