"BOOTMGR missing" after upgrading Windows 7 Home Premium to Ultimate

[AlexBridgez]

"BOOTMGR missing" after upgrading Windows 7 Home Premium to Ultimate

Hello Sevenforums,
This is my first post so please tell me if I do anything wrong. After using Windows Anytime Upgrade to upgrade my Windows 7 Home Premium to Ultimate and restarting, I get the "BOOTMGR missing error". Interestingly, if I shut down the laptop at this screen and turn it on, it loads the OS selection screen perfectly (Windows 7 and Ubuntu 11.10 dualboot).

I've tried the "repair windows" function, running the startup problems fixer, but to no luck.
Below is what came out from bcdedit:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>bcdedit

Windows Boot Manager
--------------------
identifier {bootmgr}
device boot
description Windows Boot Manager
locale en-US
inherit {globalsettings}
extendedinput Yes
resumeobject {c279be75-9b51-11de-9b93-a29d207e6d0e}
displayorder {current}
{f0c0bb8d-8788-11e1-864f-f78e62f68c09}
toolsdisplayorder {memdiag}
timeout 30
displaybootmenu Yes
customactions 0x1000085000001
0x5400000f
custom:5400000f {7f30e192-c241-11df-89c1-ec1233da63e2}

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {7f30e192-c241-11df-89c1-ec1233da63e2}
recoveryenabled Yes
testsigning No
osdevice partition=C:
systemroot \Windows
resumeobject {c279be75-9b51-11de-9b93-a29d207e6d0e}
nx OptIn

Real-mode Boot Sector
---------------------
identifier {f0c0bb8d-8788-11e1-864f-f78e62f68c09}
device partition=C:
path \ubuntu\winboot\wubildr.mbr
description Ubuntu

I noticed there isn't even a path listed for the boot manager. I am moderately computer savvy (I know some bare bones basic coding in linux and dos) but I have absolutley no idea what to do. :shock:

 

[gregrocker]

Make sure Win7 HD is set first HD to boot in BIOS setup, Mark Active Win7 or it's 100mb System Reserved partition (preferred), run Startup Repair - Run 3 Separate Times until Win7 starts on its own.

Then use this method to Dual boot Ubuntu-Win7 which may help avoid GRUB irreparably corrupting Win7 when it's on the same HD.

Safest is to install each to separate HD's booted only via BIOS boot order or one-time BIOS Boot Menu.

 

[AlexBridgez]

Hi! Thanks for the fast response.I am running on a laptop with only one HD. This has all been caused by the upgrade to Ultimate. My Ubuntu is installed using wubi, so it doesn'y have it's own partition. How could I find out where the BCD store is looking for the bootmgr file. I have copied a bootmgr file from a Win 7 repair DVD I have. Is there any way I could manually add it to the BCD store?

P.S. Any idea why the upgrade would do this to the boot manager?

Thanks

 

[gregrocker]

If you have GRUB on the drive it can corrupt Win7 in many ways and often beyond repair.

Run the repairs I suggested to see if you can start Win7. If not there are other steps including to rescue your data and reinstall in Troubleshooting Windows 7 Failure to Boot

 

[AlexBridgez]

The strange thing is that when I first turn on the laptop i get the error. However when I reboot the laptop I can boot into Win 7 fine. Does having GRUB on my HD have the same effect on an upgraded Win 7 a it does on an HD that has just had Win 7 installed? Again thanks for taking the time to reply to a noob

 

[boyans]

Here GRUB does not play any role on initial booting - Wubi method of installation is pretty clean.
Wubi/GRUB is not installed here even in a partition boot record (PBR).

First stage of Wubi is here:
c:\ubuntu\winboot\wubildr.mbr

I would do some memory tests.

The different behaviour between "warm" and "cold" boot points to some hardware problem.

 

[karlsnooks]

Alex,
Carry out the procedure given by GregRocker.

 

[AlexBridgez]

UPDATE: After a couple of days of frustration and confusion, the error magically disappeared. I can now successfully boot into and out of both OS's with no issue. Should I mark this as solved?

 

[wanchoo]

Of course, yes. But how did the problem magically disappear?

Please tell us more.

UPDATE: After a couple of days of frustration and confusion, the error magically disappeared. I can now successfully boot into and out of both OS's with no issue. Should I mark this as solved?

 

[AlexBridgez]

I think it went away after I installed some windows live updates. It said it had to restart. It restarted with me expecting the error, but instead the OS boot options screen came up as it should. I tried booting in and out of Ubuntu and Windows with no problems (well Ubuntu crashed once when shutting down but it did that before). As I said should I mark this as solved even though I have no idea what solved it? Thanks