Instruction on how to troubleshoot and resolve issues with Acronis Universal Restore or Acronis Universal Deploy
About Universal Restore and Universal Deploy
Universal restore technology is intended to provide ability to boot operating system after migration to dissimilar hardware. Most common issues are related to non-bootable operating system after restore with Universal Restore.
Please pay attention to the following prerequisites:
Acronis Universal Restore is applied after recovery process;
Acronis Universal Restore does not install drivers on the most recent Windows operating systems (Windows 10, Windows Server 2012R2, 2016, 2019) by design. These operating systems restrict installation of drivers via Universal Restore and contain a lot of preinstalled drivers and in most cases are able to boot itself on new hardware.
Detailed issue description Collect information on image source (OS, hardware, how image was taken), what restore/deployment settings were used (screenshots are preferable, mulitcast/unicast to be checked for deployment issues), how the restored PC is booted (from Windows, media on PXE/CD/USB, type of media), peculiarities of the hardware and environment (special RAID, subnets etc.), error message and everything to effectively understand and later reproduce the issue.
Disk report analysis
Disk report is saved automatically as a part of Acronisinfo gathered from bootable media.
1. Check if active flag is set on the appropriate partition.
2. Check partition layout: MBR should end on 63 sector; first partition should start either from 64 sector (before Vista) or from 2048 sector (starting from Vista).
3. Check if MBR has some traces of encryption software.
Drivers
Upload exactly same pack of drivers that is used for Acronis Universal Restore (and additionally link to these drivers download page). If recovery log contains error messages related to drivers you may do the following:
Open inf file with Wordpad and check if architecture and OS parameters are corresponding to recovered OS.
You can also use InfVerif utility from Microsoft to verify drivers.
Most reliable way is to install clean OS of the same edition on the target machine using these drivers.
BSOD screenshot
Information we need here is BSOD error number and full message, including 4 values in brackets and text of the error message.