Macrium Support Forum

Macrium v8, viBoot, and Preparing to Repair Loop

https://forum.macrium.com/Topic49565.aspx

By TheNephalim - 2 July 2021 6:23 PM

Hello,

I'm having some issues with Macrium viBoot and my backup. I backup my system daily with the Incrementals Forever scheme.

I wanted to test my backup in viBoot. The virtual machine gets created and launches. However, the virtual machine is stuck in a perpetual loop of "Windows 10 Preparing Automatic Repair." I took a look at the properties of the virtual machine in Macrium and ensured that the SSD drive was set as the boot drive and confirmed the appropriate boot order of the disks in Hyper-V, but I'm still stuck in the loop.
I can mount each of the drives contained in the backup successfully. I have also opened and examined files and nothing appears to be corrupted.

At this point, I don't know if there is something I have done wrong in configuring the backup or whether the backup scheme I have chosen is simply not compatible with viBoot.

Any assistance anyone can offer is greatly appreciated.

Sincerely,
Robert Eberhart
By Balaji - 5 July 2021 9:05 AM

Hi Robert,

Could you please open a support ticket via https://www.macrium.com/support 
This will help us collect further information and investigate the issue.

Thank you,

Kind regards
Bala
By TheNephalim - 10 July 2021 3:26 PM

Balaji - 5 July 2021 9:05 AM
Hi Robert,

Could you please open a support ticket via https://www.macrium.com/support 
This will help us collect further information and investigate the issue.

Thank you,

Kind regards
Bala

Hello,

I resolved the issue.

I had a feeling the problem most likely had to do with the order in which the boot entries were checked to start the OS.  I went to the Boot Order section of the Firmware properties.  I initially thought it had to do with the order of the drives.  It's difficult to tell which is which, though.  Regardless, I only have 2 drives, so I moved the bottom up so it was a higher priority.  This did not work.

Still experimenting, I moved the file bootmgfw.efi below the 2 drives in the priority order and this allowed the system to boot properly in Hyper-V.

If you have any questions, please let me know.

Sincerely,
Robert Eberhart