BOOTMGR issue using True Image Echo and Windows 7
I will attempt to provide as much detail as possible. Please advise if more is necessary to suggest a solution.
Using Acronis True Image Workstation 9.7 with Acronis Universal Restore, sent to me as an .iso file which I burned onto a CD-R:
- I created a full .tib backup archive of a laptop computer's active partition, listed by the Backup Wizard as E: (26.5 of 232.1 GB used, NTFS format), to an external USB drive, listed as C: (28.31 of 232.9 GB used, NTFS format).
- There were no interruptions of the backup process, and the archive was succesfully created.
- On a hardware-identical computer, using the same Acronis disc, I restored this archive onto the same drive, again listed as E: with the external USB drive listed as C:. Restoring as an active partition, I validated the archive before restoration, and the archive was succesfully restored.
- Upon removing both the CD and the USB drive, I restarted the newly restored computer, and received a "BOOTMGR is missing, press Ctrl+Alt+Del to restart" message.
- I attempted this with a third laptop computer, checking that it would boot Win7 before Acronis was used, and upon following the same restore process with the archive created from the first laptop, the BOOTMGR message was received as well.
I don't have the option of using a Win7 repair disc since both the original and the target laptop shipped with Win7 preloaded. However, this seems irrelevant, as it is clearly in the process of using Acronis that the target laptop becomes unable to boot - either this information is lost in the backup process or is not correctly restored in the restore process.
While on some brands of laptop the boot information is contained in a separate partition, this is not the case with these laptops - while there is a separate recovery partition, these were not involved in either process, and appear to be identical to all three laptops involved.
I recall that upon encountering a similar issue, I was sent an updated version of the Acronis TIEW - has there been another patch since (roughly last summer) which will circumvent this issue?
Many thanks for bearing with me. Again, please advise if more information is required.

- Log in to post comments