Vista - "BOOTMGR is Missing"

I an running VISTA-32 and when trying to boot-up I get the 'bootmgr is missing' and press cont/del/alt to continue...round and round back to same it goes.

Have tried to repair with MS system disk but still the same.

Is the problem in the BIOS, or will a Clean Install correct the problem?

I would experiment to figure it out myself but have already spent most of a day dinking with it! (Probably if I have to do a Clean install I will load Vista-64)

Thanks in advance

Try this and let us know:
Fixing "BOOTMGR is missing" Error While Trying to Boot Windows Vista :: the How-To Geek
OR
Try the solution2 from:
http://cyberst0rm.blogspot.com/2007/...issing-in.html

Thanks BRUMMY!

I have tried the first suggestion several times and "no dice".

Will try the second suggestion later today when I get back to the computer.

I have tried also to use ACRONIS true image previous system copies to no avail. These things usually save my bacon from all sort of problems, but apparently not this time

solution#2 has a step where "ren c:\boot\bcd bcd.old" is supposed to be entered. When it is done, it advises that it is not a valid command.

As nothing seems to correct the situation and I replaced the C drive with a new hard disk/ loaded an Acronis True Image copy I had made a couple weeks ago, and it still booted up with BOOTMGR IS MISSING... I would guess that it is in either the BIOS or a faulty Mother Board?

If anyone knows if flashing the Bios would have this component I would appreciatee the information.

The errant file was identified as: {9DEA862C-5CDD-4E70-ACC1-F32B344D4795} if that means anything to anyone?!?

It will start-up after running the Vista disk to repair the failure to boot, but it will not reboot without it.

BRINK; want to weigh-in here? (thanks)

Unless you changed any settings in the BIOS (ie the boot order) flashing it will not make a difference.

Is the new HDD showing up in BIOS?

Is it set as the first device in the boot order?

Is the new HDD the only drive you currently have in your system and is it partitioned?

Is the new HDD showing up in BIOS? <YES>

Is it set as the first device in the boot order? <YES>

Is the new HDD the only drive you currently have in your system and is it partitioned? <NO> There are two 640G Western Digital SATAS and an external 500G Seagate USB. System drive is partitioned.

Keep in mind that nothing in the configuration was changed from working fine mode to this bootup problem [EXCEPT] updating Acronis 11 to Acronis 2009... that was when the particular problem began. I don't think that was the cause as I have used old Acronis boot disks in Acronis 10; 11; and 2009 and reset previously saved images in each. ALL doing the same bootup error after each was reinstalled. The original HD was reinstalled with a fresh VISTA ULTIMATE install and SPINRITE was just run (all-nighter) with NO errors on the HD drive. Still has "BOOTMGR IS MISSING" error...

Going to call GIGABYTE support today to see if there are any suggestions there.

THANKS!

The reason I asked this is that I had a possibly similar-ish issue occur on another machine a while ago.

It turned out that a second hard drive had remnants of an XP boot loader that for unknown reasons decided it was the primary drive and gave me the same BOOTMGR issue.

Like yourself, I ran the start up repair several times and even though it was 'sucessfully' repaired, it still defaulted to the secondary drive.

The way I fixed it was to physically disconnect the secondary drive and re-run the start up repair. Once the MBR was re-written and everything was booting normally, I re-added the drive.

I suspect that Acronis may have altered your MBR location, or re-designated the system partition. I could also be way off track

There were some commands I used in the recovery console that pinpointed the problem originally, but unfortunately it is late and I am drawing a complete blank as to what they were. My apologies for being vague

Thanks SMARTEYEBALL for the input. Turns out that somehow the BIOS had been changed (must have been the program load) so it was trying to boot from the SLAVE H/D. Switched BIOS to boot from the Master and it was OK!

OH, for anyone who was put off by the avitar... "It's Not My Fault" !

lol, no worries mate. Glad to hear it's all okay again