Skip to main content

After Cloning Bootmrg is missing

Thread needs solution

Hello,

I cloned with True Image 2010 my Windows 7 System. It consists auf several partions, 2 of them are hidden and system because i have an Acer with preinstalled Windows 7 Ultimate.
After cloning this HD and changing the plugs of the HD the new HD is telling me "Bootmgr is missing"
I have googled the issue and it is told that the Windows 7 Install DVD AND the Rescue DVD have an option to repair the system. I should repeat the repair 3 times and than it should work.
It this correct? I am asking this for sure cause i don't want to try things that don't work and costs hours of work.
Are there are other possibilities per example to fix the problem with TrueImage itself?
Other possibility: Boot Windows 7 Install DVD, go to command mode with F10 and type:
bootrec /FixMbr
bootrec /FixBoot
bootrec /RebuildBCD
Is this correct?

Sorry for my bad english, I am German.
Thx in advance!

0 Users found this helpful

Mathias,

You can go either way (using the repair tool or the series of bootrec commands).

Verify that your clone operation worked right when you boot on the Installation DVD,. Use the command prompt to list the contents of your main system drive, use diskpart to list the partitions, etc...

We have seen cases where the user made a mistake and clone the wrong disk to the wrong disk and erased everything, which was the root cause of the bootmgr missing.

Hello,

I am using Acronis Advacned worksation 11.0 and I've been experiencing issues regarding a hard drive clone.

When I create the backup job, I select disk volumes backup, choose the desired hard drive, choose destination, Simple backup, Backup completes with no warnings, recover the backup on similar hardware, then get the bootmgr mssing, press ctrl, alt + del... I've tried different worksations and hard drives, still no luck. Any suggestions other than repairing the Mbr through windows?

The best way to fix this issue is to use the windows cd, if you don't have one, you can get one here.

Of all the times i have gotten that error, it has been rare that just running system repair has worked, but the bootrec command soloution is the best soloution.