Aller au contenu principal

Acronis Startup Recovery Manager

Thread needs solution

Any clues or advice? Thanks. Starting up a Dell XPS laptop with F11, the idea in this case to be self-contained in the case of emergency while travelling. The SSD is partitioned with C for the OS & D for data. The Acronis system backup image in this case is located on D.

Boots fine from F11, but the Acronis software cannot be used because it will not respond to the trackpad nor the touchscreen; apparently only a wired mouse. This would seem a little primitive, eg: Paragon HD Manager or EaseUS Todo Backback both work fine in this particular scenario. 

Any clues on how to get that going? There appears to be no options to configure this in the Acronis tools.

0 Users found this helpful

Paul, welcome to these public User Forums.

ASRM is essentially a small Linux based boot environment from which to launch the standalone Acronis True Image application, and as such, it has limited support for various devices which need specific device drivers for support.

You can test this by either downloading the Linux .ISO image for the rescue media from your Acronis account, or else using the Advanced option of the Acronis Rescue Media Builder tool to create the Linux version of the rescue media, which I would expect would exhibit the same issues.

The way around this would be to create the Simple version of the rescue media which uses the Windows Recovery Environment (WinRE) on your laptop for the media, which then includes the drivers needed for your hardware components.

The rescue media can be created on  a USB memory stick (2GB up to max 32GB in size) and then kept in your travel case for the laptop ready for when / if needed.

See KB 61632: Acronis True Image 2019: how to create bootable media - for more details.

WinPE rescue media is the way to go.  If you build it with the WinRE option, it will use your systems hidden Windows Recovery Environment partition (winre.wim as the baseline) which already includes your system drivers so the trackpad should be usable right off the bat. 

if, for some reason, it does not, you can get the Dell Win10 PE driver pack, or driver pack for your specific Dell system (although I don't believe either will be necessary), directly from Dell.  We put together a common driver pack page on the MVP Google Drive:

https://docs.google.com/document/d/1RSVbF5C3ykSGOKnD_vLh3xX6-LxqY8VXp9XZd7MMQrs/edit#

Bobbo_3C0X1 wrote:

WinPE rescue media is the way to go.  If you build it with the WinRE option, it will use your systems hidden Windows Recovery Environment partition (winre.wim as the baseline) which already includes your system drivers so the trackpad should be usable right off the bat. 

if, for some reason, it does not, you can get the Dell Win10 PE driver pack, or driver pack for your specific Dell system (although I don't believe either will be necessary), directly from Dell.  We put together a common driver pack page on the MVP Google Drive:

https://docs.google.com/document/d/1RSVbF5C3ykSGOKnD_vLh3xX6-LxqY8VXp9X…

Thanks for this and other suggestions above. Yes, have built recovery media on USB stick & all works fine with drivers etc. The specific question I was asking however was: can this be achieved via the F11 boot option & without any rescue media such as USB stick, DVD ISO or similar?

Again, the idea here is to have the laptop completely self contained & without the need to carry USB stick, mouse etc. And again, other backup vendors seem to have this covered with the injection of basic drivers and/or networking in the case of standalone boot menu options.

In the case of Acronis, this would appear to be 'no', but I may well be missing something. eg: when building the WinPE rescue environment, there appeared to be no options here, only to make USB or ISO.

Thanks again.

Paul, take a look at the MVP Custom ATIPE Builder script (link in Rob's and my signatures), as this creates both an ISO and WIM image of the WinPE rescue media.

You could then use a utility such as EasyBCD to add one of these images to your Windows Boot Menu (BCD configuration), i.e. use the ISO for Legacy or the WIM for UEFI systems.

Steve's answer is the way to go and how I wished it worked by default. Right now, F11 switches to Linux rescue media, actually modifying the bootloader in the process, and can cause issues on systems with uefi, especially if drivers are missing, the disk is encrypted or secure boot is enabled in the BIOS. Adding a simple boot menu entry and pointing to the .wim takes all the risk out of it and results in nearly the same process in the end 

Otherwise, keep a USB drive handy and use your one time bios boot menu to easily boot it. I just press f12 and select the USB and am good to go.