asked on

BOOTMGR is missing on Windows Server 2003

I had a failed disk on a Windows Server 2003 R2, and after the disk got replaced, I got "BOOTMGR is missing, press Ctrl+Alt+Del to restart". I know there's a way to fix these type of errors in Windows XP by replacing the "ntldr", "ntdetect.com", and "bootcfg /rebuild", but don't know what to do for Windows Server 2003. Please advise. Thanks..

SOLUTION

mi3er

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

Premkumar Yogeswaran

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

footech

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER CERTIFIED SOLUTION

swgit

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

footech

I've never done a repair install on a production server. To be honest, although I would be curious about its results, if I got to the same point and didn't have any other options I would elect to either restore the machine (if a backup was available) or rebuild.

First, however, "Nothing works so far." Can you elaborate, what steps have you tried?

swgit

ASKER

@mi3er - this is not permissions problem, but thanks for your input @prem - this is how i used to fix boot problem for windows os, however, it didn't really work in this case after i tried. thanks for reminding me of the other options @footech - "Nothing works so far" means the following steps did not fix the problem:

replaced "ntldr", "ntdetect.com", and ran "bootcfg /rebuild" in the recovery console did not solve the problem

also from the recovery console, "fixboot" and "fixmbr" did not solve the problem either

So I ended up doing the following:

imaged all disk partitions just in case

repaired windows ("Repair" option after F8) > this resulted in successful boot up to Windows. However,

all system drivers need reinstalled

network configuration needs reconfig'ed or applied

all Windows updates reapplied

restored most recent backups

So far so good... there are minor errors here and there between the app and database, but I'm okay with the result now, as I can get thing up and running, even with some errors. Thanks all for your help. Please do let me know if you have any questions.