Aller au contenu principal

TrueImage 2017 - BMR Run Error

Thread needs solution

I have a new client that uses the 2017 product.  I have a good image of the hdd on a spare 1TB HDD.   Using their account, I created a USB flash drive with the Universal Restore (restore to different new computer).

I get the following error message.  Is this wanting the USB drivers?  or is there another driver i need?

Thanks,

Darryl

Fichier attaché Taille
faag - acronis error - jan14 2019.jpg 159.43 Ko
0 Users found this helpful

Darryl, welcome to these public User Forums.

Sorry but I am not sure what you are actually trying to do here and why you are using Acronis Universal Restore?

AUR is only needed when you are migrating a backup of a Windows OS system from one computer to use this on a second computer with different hardware, where this is applied after the backup has been restored to a drive in that second computer using the normal Acronis Rescue Media.

See KB 58579: Acronis True Image 2017: Restoring to Dissimilar Hardware with Acronis Universal Restore

Also KB 45432: Acronis Software: Troubleshooting Universal Restore and Bootability Issues

Thanks for the KBs.

I thought from the reading (before your post) that AUR is the proper tool to use when restoring a image to a different computer (in this case, a new computer).  The thought being the new computer would be identical to the old computer.

Is this not correct - 

  1. make new backup image
  2. validate image
  3. create AUR media
  4. boot new computer from AUR media
  5. point to image and restore

Your comment means I need restore the image then do AUR.

Thanks!

 

Darryl, there are more considerations when migrating an installed Windows OS to new hardware.

If you create the Acronis boot media as per KB 58579 (referenced above) then this media is used to first boot into the normal Acronis Rescue media - True Image application to perform the restore of the backup, then shutdown and booted again, this time to the Universal Restore application.

However, for this to be successful, both computers have to support how Windows will boot, i.e. both use the same CPU architecture (you cannot restore a 64-bit OS to a 32-bit system), both need to support booting into Windows using the same BIOS mode (as shown by running msinfo32 in Windows), so both boot using Legacy, or both boot using UEFI.  If your old system was Legacy, and the new is UEFI only, then the restore has to also migrate the OS data from MBR to GPT as required by UEFI.  Both computers need to support the same disk controller mode of operation, i.e. both using SATA drives in AHCI mode.

Further, if you are migrating a Windows 7 OS to new hardware, you need to ensure that you have all required drivers for new hardware in that new computer for which Windows 7 has no native support, such as NVMe PCIe M.2 drives which may also be using a SATA controller mode of RAID for which further drivers would be needed.

Windows 7 is now in its final year of support by Microsoft so you may want to consider taking the opportunity to upgrade to Windows 10 when moving to a new computer system.  Windows 10 is significantly more flexible at handling change of hardware than Windows 7 has ever been, and in most cases, Windows 10 OS migration does not need to use Universal Restore.