Linux-based bootable media

After installation of Acronis vmProtect 9 Virtual Appliance onto ESXi 5.5 host upgrade its virtual hardware up to 10th version in order to avoid "The specified delta disk format 'redoLogFormat' is not supported." error in the log

You can boot the machine from Acronis Bootable Media and manage it locally or remotely

Acronis Backup & Recovery 11/11.5 is fully compatible with Aladdin Secret Disk. Other Acronis products have limited compatiblity

To restore from an unmanaged vault, browse to the network share or local folder where the archive is. To restore from a centralized managed vault, click on Storage node, type in the IP Addres or computer name of the machine where Acronis Storage Node is

Create two separate tasks if you are planning to back up local and network folders

This article explains the general concept of archives and backups as realized in Acronis Backup & Recovery, and how one can resume previous backups into the same archive

An Update is available for True Image 2013 and Acronis Backup & Recovery 11.5

Acronis Bootable Agent can be controlled either locally through the GUI or remotely using the console


  1. You are trying to make a standalone deployment of an image placed on an external HDD to default disk.
  2. Deployment fails with:

E00770022: Deployment has completed with errors.
Failed to prepare to the image deployment operations. Possibly, image is corrupted or is not accessible.

Error code: 0x330022
$module = "stand_alone_glx_1416"
Tag: 0x100FE7C3207C546D
Internal error: Failed to create the image stream reader.


  1. You have a machine with Intel I219-LM NIC.
  2. You boot the machine with Acronis Linux-based bootable media.
  3. The NIC is not detected, you cannot configure network settings.


Limitation of the product.


The issue has been fixed in update 1 of Acronis Backup Advanced 11.7, please update to the latest build.

The issue has been fixed in update 3 of Acronis Snap Deploy 5, please update to the latest build.


  1. You create a 64-bit WinPE-based bootable media by specifying a path to a folder with WinPE files manually (e.g. C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us\winpe.wim).
  2. You boot the target machine with the created media.
  3. Booting fails with the following error:

The operating system couldn't be loaded because a critical system driver is missing or contains errors.
File: \windows\system32\DRIVERS\snapman.sys

Download an ISO image from the Acronis website, burn it to a CD/DVD, and issue a special command to get the proper screen resolution


Acronis Disk Director (any version and edition) is not supported on Mac computers.

This includes:

  1. Installing and using Acronis Disk Director on macOS (any version)
  2. Installing and using Acronis Disk Director on BootCamp Windows
  3. Installing and using Acronis Disk Director on Parallels Windows or any other virtual machine on Mac computer
  4. Running Acronis Disk Director from a bootable media on Mac and any virtual machine on it

You can create a rescue bootable media - a standalone version of Acronis True Image that you can use to boot a crashed machine or a machine without any operating system and restore an image of your system. Follow these instructions to create a bootable media.


You may experience issues with booting a Linux-based bootable media on MSI GE72VR 6RF notebook. Agent locks up while 'Loading the network connection setting...'


Issue can be resolved by adding the acpi=off noapic parameter to the Linux kernel when creating the media:


  1. You create a WinPE bootable media and specify network settings manually.
  2. Manual network settings are ignored; media is configured with DHCP settings.


Issue in the product.


Our development is working on the issue. This article will be updated as soon as the fix is available.

You may be asked by Acronis Support to export your logs with the error from Acronis Backup for issue investigation.

You can also export the error prior to contacting Acronis Support to save time.

Additional parameters that can be applied prior to booting Linux kernel


This article explains how to find out whether Acronis Bootable Media boots in UEFI or Legacy BIOS mode. Keep in mind that bootable media should boot in the same mode as your system to correctly perform restore or clone operation.

The mode your system boots in is shown during the initial machine boot:

In Windows 8 and 10, you can also check the boot mode using System Information:

Fujitsu-Siemens Esprimo V6555 is not supported by Linux-based bootable media

Contact Acronis Support for a resolution

Because Acronis products work with the storage system of an operating system on a very low level, there is a small risk that different conflicts on this level can lead to an operating system crash during backup or other operations. Please follow the instructions below to troubleshoot these issues, depending on what operating system is being used..

In some rare cases there can be some issues with HID devices, e.g. you booted machine from Bootable Media and your USB mouse doesn't move or keyboard doesn't type or types wrong. Follow step-by-step instructions below to troubleshoot the issue.

The full version of Acronis Bootable Rescue Media uses Linux environment, the naming convention of which is different from Windows

By default, Acronis True Image is installed in the language of your operating system (as specified in the System Display Language) if this language is available in Acronis True Image, and will change once you change the system language.

In case you want to use Acronis True Image in another language, you can switch to the desirable language in the user interface (no need to reinstall the product):

Acronis Cyber Protect Home Office:

Make sure that the antivirus software running in your environment does not block Acronis products. See Acronis Software: Making Acronis Products Compatible with Antivirus Software

Under specific circumstances, the software may crash. It is very important to report a crash instead of trying to workaround it. Normal workflow for a crash problem is the following: