Salta al contenuto principale

Boot Manager Failure after restoring image to larger/new laptop drive. Windows7 build 7100

Thread needs solution
Beginner
Messaggi: 1
Commenti: 0

I have been trying to upgrade to a larger laptop drive from 250gb to 500gb using Home 2010 beta. I took the following steps:

1)      Created full drive backup of my source drive and saved it on external USB drive;

2)      Created Acronis bootable disc by means of the program and checked its functionality. Booted computer with it and checked that external drive recognizes without any issues;

3)      Attached new drive to the notebook;

4)      Booted  from Acronis bootable disc and restored the image to the new drive.

Everything went fine. The new hard drive booted up,ran and Windows 7 ran without problem, but displayed a message that new hardware had been detected and had been installed and needed a reboot. When rebooted windows began to run then blue-screened. The Windows 7 repair disk attempted but failed to make the needed repairs but the error message was Boot Manager Generic Failure 0xc000000e. Any help appreciated.

0 Users found this helpful
Beginner
Messaggi: 1
Commenti: 9

#1

 this should help i had to put in a new drive after trying to restore with acronis and getting the same error

 I had to repartion the drive with two partions one for the" C:\" partion and the "100meg" partion. the 100 meg partion its called a" system reserved" holds all the boot files and folders without this partion you will never boot.  windows 7 creates the all the partions you will need. look at the attached file for the explanation for what i am talking about. 

I would suggest you install windows 7 on the new drive then restore the backup---that should keep the partions in tack. Do not reformat let acronis do it.

 you can setup the partions manually using  Acronis. goto utilities  then  click on new disk and follow the instructions.

Sorry if the explanation is not to clear.

also make sure after you restore that you  remove the usb drive when you reboot it may be looking at that instead of the new drive.