When you start your Windows Server 2003-based computer, you may receive the following error message:
NTLDR is missing
Press any key to restart
This problem may occur if the basic input/output system (BIOS) on your computer is outdated, or if one or more of the following Windows boot files are missing or damaged:
Ntldr
Ntdetect.com
Boot.ini
To resolve this issue, verify that the BIOS on your computer is current, and then use one or more of the following methods, depending on your situation, to repair the Windows Server 2003 Startup environment.
Important To prevent data loss, Microsoft recommends that you fully back up your data periodically. The backup of data must be a part of any disaster recovery plan.
Verify that the BIOS on the computer is current
Make sure that the latest revision for BIOS is installed on the computer. Contact the computer manufacturer for information about how to obtain and install the latest BIOS update that is available for the computer.
For information about how to configure and to verify the correct BIOS settings for the computer, see the computer documentation or contact the manufacturer of the computer.
For information about how to contact your hardware vendor, visit the following Microsoft Web site:
http://support.microsoft.com/gp/vendors
For more information about how to contact BIOS manufacturers, click the following article numbers to view the articles in the Microsoft Knowledge Base:
243909 List of BIOS manufacturer Web site, part 1
243971 List of BIOS manufacturer Web sites, part 2
Back to the top
Repair the Windows Startup environment
To repair the Windows startup environment, use one or more of the following methods, depending on your situation.
Method 1: Use a boot disk
To use a boot disk to repair the Windows Startup environment, follow these steps:
Create a Windows Server 2003 boot disk that contains the following files:
Ntldr
Ntdetect.com
Boot.ini
Ntbootdd.sys
Note Ntbootdd.sys may not be included on all Windows Server 2003 computers.
For more information about how to create a boot disk, click the following article numbers to view the articles in the Microsoft Knowledge Base:
301680 How to create a boot disk for an NTFS or FAT partition in Windows
101668 How to use a Windows boot disk to prevent boot failure in Windows 2000 or Windows NT
Modify the Boot.ini file to point to the correct hard disk controller and to the correct volume for your Windows installation.
For more information about how to modify the Boot.ini file, click the following article number to view the article in the Microsoft Knowledge Base:
323427 How to manually edit the Boot.ini file in a Windows Server 2003 environment
Insert the boot disk into the floppy disk drive, and then restart the computer.
Copy the Ntldr file, the Ntdetect.com file, and the Boot.ini file from the boot disk to the system partition of the local hard disk.
Method 2: Use the Recovery Console
Microsoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft support professionals can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific needs.
If you have limited programming experience, you may want to contact a Microsoft Certified Partner or Microsoft Advisory Services. For more information, visit these Microsoft Web sites:
Microsoft Certified Partners - https://partner.microsoft.com/global/30000104
Microsoft Advisory Services - http://support.microsoft.com/gp/advisoryservice
For more information about the support options that are available and about how to contact Microsoft, visit the following Microsoft Web site:http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS To use the Recovery Console to repair the Windows Startup environment, follow these steps:
Use the Windows Server 2003 CD-ROM to restart the computer.
At the Welcome to Setup screen, press R to repair the Windows Server 2003 installation.
To use the Recovery Console to repair the Windows Server 2003 installation, press C.
Type the number that corresponds to the Windows installation that you want to repair, and then press ENTER. For more information about the Recovery Console, see the "Recovery Console overview" topic in Windows Server 2003 Help and Support Center.
Type the Administrator password, and then press ENTER.
Type map, and then press ENTER. Make a note of the drive letter that is assigned to the CD-ROM drive that contains the Windows Server 2003 CD-ROM.
Type:
copy Drive:\i386\ntldr c:\
NoteDrive is the drive letter that you noted in step 6, and then press ENTER.
Type:
copy drive:\i386\ntdetect.com c:\
If you are prompted to overwrite the file, type y, and then press ENTER.
Note In these commands, a space exists between ntldr and c:\, and between ntdetect.com and c:\.
Type the following command, and then press ENTER:
type c:\Boot.ini
A list that is similar to the following list appears:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows Server 2003, Standard" /fastdetect
If you receive the following error message, the Boot.ini file may be missing or damaged:
The system cannot find the file or directory specified.
If the Boot.ini file is missing or damaged, re-create it. To do so, follow these steps:
Use a text editor, such as Notepad or Edit.com, to create a boot loader file that is similar to the following boot loader file:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows Server 2003, Standard" /fastdetect
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
102873 BOOT.INI and ARC path naming conventions and usage
Save the file to a floppy disk. When you do so, in the Save As box, type:
Boot.ini
Note If you used Notepad to create the file, make sure that the .txt extension is not appended to the Boot.ini file name.
Type the following command at the Recovery Console command prompt to copy the Boot.ini file from the floppy disk to the computer:
copy a:\Boot.ini c:\
Type exit, and then press ENTER. The computer restarts.
Method 3: Use the Windows Server 2003 CD-ROM
To use the Windows Server 2003 CD-ROM to repair the Windows Startup environment, follow these steps:
Insert the Windows Server 2003 CD-ROM into the CD-ROM drive or into the DVD-ROM drive, and then start Windows Server 2003 Setup.
On the Welcome to Setup page, press the R key.
On the Windows Server 2003 Repair Options page, press R.
When you are prompted to select one of the repair options, press M.
To select Verify Windows Server 2003 system files, press the UP ARROW two times, and then press ENTER..
Press the DOWN ARROW to select Continue (perform selected tasks), and then press ENTER. You receive the following message:
You need an Emergency Repair disk for the Windows Server 2003
installation you want to repair.
Use one of the following methods, as appropriate to your situation:
If you have an emergency repair disk, follow these steps:
Press ENTER.
Insert the emergency repair disk into the floppy disk drive, and then press ENTER.
Follow the instructions that appear on the screen to repair the installation, and then restart the computer.
If you do not have an emergency repair disk, follow these steps:
Press L. You receive a message that is similar to the following message:
Setup has found Windows Server 2003 in the following folder:
drive:\WINDOWS "Microsoft Windows Server 2003"
Press ENTER.
Setup examines the disks, and then finishes the repair.
The Setup program cannot locate the Windows Server 2003 installation
If the Setup program cannot locate the Windows Server 2003 installation, follow these steps:
Start Windows Server 2003 Setup.
On the Setup will install Windows Server 2003 on partition page, use the ARROW keys to select Leave the current file system intact (no changes), and then press ENTER.
Press ESC to install Windows Server 2003 to a new folder.
In the Select the folder in which the files should be copied box, type \tempwin, and then press ENTER.
Setup installs a new copy of Windows Server 2003.
Log on to the new copy of Windows Server 2003.
Click Start, and then click Run.
In the Open box, type cmd, and then click OK.
At the command prompt, type the following command, and then press ENTER:
drive:
Note In the command, drive is the boot drive of the computer. For example, type c:, and then press ENTER.
Type the following command, and then press ENTER:
attrib -h -r -s Boot.ini
Type the following command, and then press ENTER:
edit Boot.ini
Edit.com opens a Boot.ini file that is similar to the following file:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\TEMPWIN
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\TEMPWIN="Microsoft Windows Server 2003, Standard" /fastdetect
In the Boot.ini file, replace all instances of "TEMPWIN" with "WINDOWS". A Boot.ini file appears that is similar to the following file:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows Server 2003, Standard" /fastdetect
Press ALT+F, and then press S.
Press ALT+F, and then press X.
Type the following command, and then press ENTER:
attrib +h +r +s Boot.ini
Type exit, and then press ENTER to quit the command prompt.
Restart the computer.
At the Please select the operating system to start screen, use the ARROW keys to select Microsoft Windows Server 2003, and then press ENTER.
Start Windows Explorer, locate the following folders, and then delete them:
Tempwin
All Users.Tempwin
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
228004 Changing active partition can make your system unbootable
