Solved BOOTMGR is Missing - Only Sometimes!

[ESL]

I have a strange problem. I read about the BOOTMGR is Missing problem here, and the associated fixes. I get the BOOTMGR is Missing error message, but only sometimes. When I do a control, alt, delete as the error instructs, the computer then boots up just fine usually. All will continue to be well for a while, and during reboot, it will happen again. I've run the Windows 7 rescue disc startup repair option, but it says a problem cannot be found, yet obviously something is going on. I've done the bootrec /FixMbr, bootrec /FixBoot, and bootrec /Rebuildbcd commands at the DOS prompt. On that last command, it told me the number of Windows installations was 0, which obviously isn't right. I'm confused and frustrated by this. Help!

 

[Kaktussoft]

bootrec /FixMbr fixes the MBR but MBR is already fine!
bootrec /FixBoot fixes volume boot sector that loads BOOTMGR and indeed it tries. so looks fine as well.
bootrec /Rebuildbcd rebuilds only non existent boot options in bcd file (as far as I know).

Sequence is: Load MBR->load volume bootrecord->load BOOTMGR->read bcd store (bootmenu)

Problems only on cold boot? Enter BIOS on boot but don't modify anything... just exit bios without updating anything. That makes any difference? Are you experiencing any other strange problems after succesfull boot?

Please post screenshot of disk management

 

[Kaktussoft]

I have a strange problem. I read about the BOOTMGR is Missing problem here, and the associated fixes. I get the BOOTMGR is Missing error message, but only sometimes. When I do a control, alt, delete as the error instructs, the computer then boots up just fine usually. All will continue to be well for a while, and during reboot, it will happen again. I've run the Windows 7 rescue disc startup repair option, but it says a problem cannot be found, yet obviously something is going on. I've done the bootrec /FixMbr, bootrec /FixBoot, and bootrec /Rebuildbcd commands at the DOS prompt. On that last command, it told me the number of Windows installations was 0, which obviously isn't right. I'm confused and frustrated by this. Help!

reboot ALWAYS gives that error?
boot ALWAYS give that error?
(CTRL-ALT-DEL fixes it, I know)

 

[ESL]

No. The error occurs only occasionally on reboot or boot. Another thing: I have three hard drives (not all connected at once) and I only get the error on the one particular hard drive. I have put back my reliable drive back in my PC for now. Later, I'll put the drive back into my PC that gives me the occasional Bootmgr error and post a screenshot of disk management.

 

[Kaktussoft]

No. The error occurs only occasionally on reboot or boot. Another thing: I have three hard drives (not all connected at once) and I only get the error on the one particular hard drive. I have put back my reliable drive back in my PC for now. Later, I'll put the drive back into my PC that gives me the occasional Bootmgr error and post a screenshot of disk management.

check that disk

chkdsk/f/r c:
chkdsk/f/r d:

etc. seagate disk, or western digital?

 

[ESL]

No. The error occurs only occasionally on reboot or boot. Another thing: I have three hard drives (not all connected at once) and I only get the error on the one particular hard drive. I have put back my reliable drive back in my PC for now. Later, I'll put the drive back into my PC that gives me the occasional Bootmgr error and post a screenshot of disk management.

check that disk

chkdsk/f/r c:
chkdsk/f/r d:

etc. seagate disk, or western digital?

Western Digital. It's a Caviar Black WD7502AAEX 750 GB. I'll get a screenshot of Disk Management and do the chkdsk tonight, and report back tomorrow. Thanks for the replies, gang.

 

[ESL]

 

[ESL]

The chkdsk came back clean. Above is the screenshot from Disk Management.

 

[gregrocker]

It looks correct. Run Startup Repair several times to see if it finds anything to fix.

You can also try Rebuild MBR with Partition Wizard Rebuild MBR - Video Help.

If these fail then I would move the System Boot files to C by marking it Active then running Startup Repair - Run 3 Separate Time. This eliminates the possibility that the 100mb System Reserved partition has become corrupted and creates a new System partition refreshing the MBR.

You can also recreate the 100mb System Reserved partition by deleting it using Partition Wizard bootable CD, creating a new Primary Partition there labeled System Reserved, mark it Active then run the three Startup Repairs to write new System boot files to the partition.

You've now done everything possible short of wiping the HD with Diskpart Clean Command which can overwrite problematic boot sector code and solves many problems we have with installs and boot problems.

Be sure to back up a Win7 image before any of these operations: Backup Complete Computer - Create an Image Backup
Macrium - Image your system
http://www.sevenforums.com/tutorials/105541-startup-repair-run-3-separate-times.html

 

[ESL]

Thanks. I'll give those ideas a shot, and report back.

 

[ESL]

Update: trying the ideas above didn't solve the problem. I read what you mentioned about wiping the drive with the Diskpart command, but since I have KillDisk Pro, I thought I would try that. Since I didn't want to make a bootable DVD of KillDisk and be without my computer for hours (it took 29 hours), I took the drive, connected it to my SATA to USB adapter and ran the Windows version of KillDisk Pro and did a US DoD 5220.22-M erase of the drive.

The result? No BootMGR is Missing message, although during one of the reboots, it came up with "reboot and select boot device or insert boot media in selected boot device and press a key." I ran Windows 7 startup repair from the bootable DVD, and when it got to the part where it said "searching for Windows installations," it couldn't find any and said unknown OS. I ran a fix from the DVD. It said that if it was successful, the computer would restart and Windows would boot normally. Windows then booted normally, and when I ran the startup repair again just to double-check, it found my installation of Windows 7.

From what I've read, this "reboot and select boot device or insert boot media in selected boot device and press a key" message can occur if, during reboot, something as simple as a USB stick is connected to the computer. Is this true? Just to be on the safe side, I'm going to KillDisk the drive again (this time using a single pass of zeros), reinstall Windows and all my programs and settings, and make sure during all reboots that no other storage devices are connected to the computer.

 

[gregrocker]

Diskpart Clean Command can be run from the Win7 installer Command Line or System Repair Disk in less than 30 seconds and wipes anything that can interfere with the boot. This is why I suggested it since any longer method only serves to make data unrecoverable and has zero troubleshooting purpose. Sorry you chose another method which took 29 hours which is the grossest overkill I've ever heard of. I hate to think of how much your drive's life has been shortened. :shock:

If Startup Repair found your installation and repaired it after three recommended passes with reboots, then there is no point in reinstalling unless performance issues remain that call for it.

If you're ready to reinstall anyway then follow these same steps to get and keep a perfect Clean Reinstall - Factory OEM Windows 7

 

[ESL]

Thanks, Greg. I'll give Diskpart a try this time around. I'll keep you posted.

 

[ESL]

I couldn't figure out Diskpart, so I went ahead and used KillDisk again (one pass of zeros), which took ten hours. I reinstalled Windows 7, and had no error messages, but for the heck of it, inserted the Windows 7 boot disk, and immediately I could see the Windows 7 installation, and, of course, no problem could be detected. So, it appears the problem is solved. Thanks, guys, for all your help. This forum is a great service to PC users.