Windows 2003 doesn't boot after installing Windows XP

[Max Kubierschky]

Hello,

I have Windows Server 2003 (Standard Edition) on the first partition of my hard disk.
Then I installed Windows XP onto an other partition. Now the boot loader shows them both.
Windows XP starts without problems, but when selecting Windows 2003, there is just a blank
screen with a blinking cursor. I tried FIXMBR and FIXBOOT in the recovery console, but it
doesn't make a difference.

How can I run my Windows 2003 again?



Here some details:

I have also installed two versions of Linux and grub
on the MBR. I start the Windows bootloader on the 2003 partitioen from grub.
According to grub, on the XP partition there is no valid code for booting on the XP partition.
Leaving the MBR to Windows (via FIXMBR) gives me the Windows-bootloader directly, but with the same result
as above.

I can see the data on the 2003-partition from Linux and from XP.


Yours,
Max

 

[Admiral Q]

: Hello,
:
: I have Windows Server 2003 (Standard Edition) on the first
partition of my hard disk.
: Then I installed Windows XP onto an other partition. Now the boot
loader shows them both.
: Windows XP starts without problems, but when selecting Windows
2003, there is just a blank
: screen with a blinking cursor. I tried FIXMBR and FIXBOOT in the
recovery console, but it
: doesn't make a difference.
:
: How can I run my Windows 2003 again?
:
:
:
: Here some details:
:
: I have also installed two versions of Linux and grub
: on the MBR. I start the Windows bootloader on the 2003 partitioen
from grub.
: According to grub, on the XP partition there is no valid code for
booting on the XP partition.
: Leaving the MBR to Windows (via FIXMBR) gives me the
Windows-bootloader directly, but with the same result
: as above.
:
: I can see the data on the 2003-partition from Linux and from XP.
:
:
: Yours,
: Max


Which recovery console - XP's or Win2k3? Since Win2k3 was released
after WinXP, the proper installation order would be XP then Win2k3.
Since you installed XP after Win2k3, you've destroyed the Win2k3
boot files. You need to boot to the recovery console (Win2k3 one
not the XP one) and then do a FIXBOOT and FIXMBR. If this fails,
you may have to do a repair install of Win2k3 in order to get all
the Win2k3 boot files restored properly.

--


Star Fleet Admiral Q @ your service!

Google is your friend!
http://www.google.com

 

[Max Kubierschky]

: Hello,
:
: I have Windows Server 2003 (Standard Edition) on the first
partition of my hard disk.
: Then I installed Windows XP onto an other partition. Now the boot
loader shows them both.
: Windows XP starts without problems, but when selecting Windows
2003, there is just a blank
: screen with a blinking cursor. I tried FIXMBR and FIXBOOT in the
recovery console, but it
: doesn't make a difference.
:
: How can I run my Windows 2003 again?
:
:
:
: Here some details:
:
: I have also installed two versions of Linux and grub
: on the MBR. I start the Windows bootloader on the 2003 partitioen
from grub.
: According to grub, on the XP partition there is no valid code for
booting on the XP partition.
: Leaving the MBR to Windows (via FIXMBR) gives me the
Windows-bootloader directly, but with the same result
: as above.
:
: I can see the data on the 2003-partition from Linux and from XP.
:
:
: Yours,
: Max


Which recovery console - XP's or Win2k3? Since Win2k3 was released
after WinXP, the proper installation order would be XP then Win2k3.
Since you installed XP after Win2k3, you've destroyed the Win2k3
boot files. You need to boot to the recovery console (Win2k3 one
not the XP one) and then do a FIXBOOT and FIXMBR. If this fails,
you may have to do a repair install of Win2k3 in order to get all
the Win2k3 boot files restored properly.

I certainly used the Win2k3 recovery console when trying FIXBOOT and FIXMBR.
As mentioned, that didn't do the job.
But, thank you, the repair install did it!

I wasn't aware that there is such a thing as a repair install. So here for
the ones that might google after me and are similarly unenlightened:

Inserting the Win2k3 install CD and following the normal installation path,
at some point I was presented a 'list' of current installations (with one item).
The installer offered to repair that installation after pressing R, which I did.
It was somewhat scary, as the repair install behaved exactly like a real install,
so I feared to lose my current installation. But the installer left everything
intact and repaired my boot loader.