NTLDR
Dear recipient:
Enclosed bellow please find information with regards to you issue. Also please be aware that this operating system is set to high for security reasons and such is on automated mode for said purpose, perhaps the information requested did contain a word or phrase that activated the security program, please accept my apology, the security mode cannot be changed since the same operate with very sensible and guarded material. This system uses encryption to protect your information from being viewed by someone else as it is transmitted across the Internet. Thank you for bringing this matter to my attention. This operating system is normally used for classify informative material and research data center.
Once again, please accept my humble apologies.
Regards,
Angel Manuel Cancel
Developer Research Team
E-mail: microsoft.microsoft92@gmail.com
TROUBLESHOOTING METHOD A
"NTLDR is missing" error message when you install or upgrade Windows XP over Windows 95, Windows 98, or Windows Millennium Edition
SYMPTOMS
This section is intended for advanced computer users. If you are not comfortable with advanced troubleshooting, you might want to ask someone for help or contact support. For information about how to do this, visit the following Microsoft Web site:
http://support.microsoft.com/contactus
When you try to install Windows XP or upgrade to Windows XP on a computer that runs Microsoft Windows 95, Windows 98, or Windows Millennium Edition, you may receive the following error message after the first restart during the installation:
NTLDR is missing
Press any key to restart
CAUSE
This problem may occur if your existing Windows 95, Windows 98, or Windows Millennium Edition installation was cloned and then applied to a drive that has a different geometry from that of the source drive of the cloned copy.
For example, you are running Windows 98 on a 4-gigabyte (GB) drive. After you upgrade to a 30-GB hard disk, you use a third-party disk-imaging utility to make a mirror image of your Windows 98 installation, and then apply the image to the new drive. Later, you upgrade to Windows XP. To do this, you install Windows XP over the cloned image of Windows 98.
For this problem to occur, all the following conditions must be true:
? The system/startup partition is formatted with the FAT32 file system.
? The computer starts by using INT-13 extensions. (This is a partition larger than 7.8 GB with a System-ID type of 0C in the partition table).
? Because of the cloning procedure, the Heads (sides) value in the FAT32 BIOS Parameter Block (BPB) does not match the geometry of the physical drive.
The Windows 95, Windows 98, or Windows Millennium Edition startup code ignores the Heads value in the BPB and starts those programs even though the value is not valid. However, the startup code in Microsoft Windows 2000 and Windows XP requires this value, and startup is unsuccessful if the value is not valid.
RESOLUTION
To resolve this problem, correct the Heads (sides) value in the FAT32 BPB so that the Windows XP startup can continue. To update the value, rewrite the Windows 95, Windows 98, or Windows Millennium Edition startup code. To do this, follow these steps:
1. Restart the computer by using a Windows 95, Windows 98, or Windows Millennium Edition startup disk that contains the Sys.com file. (By default, this file is included.)
2. Make a backup copy of the Msdos.sys file in the root directory of the system drive. To do this, type the following commands at a command prompt:
attrib -h -r -s c:\msdos.sys
rename msdos.sys *.ysy
3. At a command prompt, type sys c: to rewrite the Windows 95, Windows 98, or Windows Millennium Edition startup code with accurate BPB information. If this command runs successfully, go to step 4.
If you are using a Windows Millennium Edition startup disk, and you receive the following error message, one or more files in the Windows Millennium Edition installation have been removed:
Cannot find the system file in the standard locations on drive C:
Follow these steps to put the correct files on the drive so that the sys command can locate them:
a. Type the following commands. Press ENTER after each command:
c:
cd\windows
If Windows is installed in a folder other than the Windows folder, adjust the commands accordingly.
b. Try to switch to the Command folder by typing the following command:
cd command
If you receive an error message that the path is not found, type the following command to create the Command folder, and then run the cd command command again:
md command
c. Switch to the EBD folder by typing the following command:
cd ebd
If you do not receive an error message that the path is not found, type the following command to create the EBD folder, and then repeat the cd ebd command:
md ebd
d. In the EBD folder, use the following commands to copy the Io.sys file from the root of the hard disk and to rename the Io.sys file to Winboot.sys:
attrib -s -h -r c:\io.sys
copy c:\io.sys winboot.sys
Winboot.sys is the file that Sys.com requires.
e. Switch back to drive A, and then type the following commands:
a:
sys c:
Type the following commands to restore the original Msdos.sys file. Press ENTER after each command:
attrib -s -h -r c:\msdos.sys
copy c:\msdos.ysy c:\msdos.sys
Press Y to overwrite the existing Msdos.sys file. You will receive a "1 FILE(S) COPIED" verification that the file was overwritten.
4. Restart the computer to Windows 95, Windows 98, or Windows Millennium Edition, and then try to install or upgrade to Windows XP again.
Note Or, after you run the sys c: command, you can start to the Recovery Console, and then use the fixboot command to rewrite the Windows XP startup code. With this procedure, the original installation continues normally.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
178947 Registry file was not found. Registry services may...
318948 "NTLDR is missing or corrupt" error message during Windows 2000 or Windows NT 4.0 upgrade
320397 Windows may not start and you may receive an "NTLDR is missing" error message if Windows is not up-to-date and there are too many files in the root folder
883275 You cannot start your computer after you modify the permissions in Windows Server 2003, in Windows XP, or in Windows 2000
812492 Error message when you start your computer with a non-system disk
315261 The computer does not start after you change the active partition by using the Disk Management tool
If the articles listed here do not help you resolve the problem or if you experience symptoms that differ from those that are described in this article, search the Microsoft Knowledge Base for more information. To search the Microsoft Knowledge Base, visit the following Microsoft Web site:
http://support.microsoft.com
Then, type the text of the error message that you receive, or type a description of the problem in the Search Support (KB)
APPLIES TO
? Microsoft Windows XP Home Edition
? Microsoft Windows XP Professional
Keywords: kbresolve kbfilesystems kbenv kberrmsg kbprb kbsetup KB314057
TROUBLESHOOTING METHOD B
How to troubleshoot the "NTLDR Is Missing" error message in Windows 2000On This Page
SUMMARY
How to Troubleshoot the "NTLDR Is Missing" Error Message
Verify That the BIOS on the Computer Is Current
Method 1: Use a Boot Disk to Start the Computer
Method 2: Use the Recovery Console
Method 3: Use the Windows 2000 CD-ROM
If Setup Cannot Locate Windows 2000
Additional Resources
Perform a Parallel Installation of Windows 2000
REFERENCES
SUMMARY
This step-by-step article describes methods that you can use to troubleshoot the "NTLDR Is Missing" error message that you may receive when you try to start Microsoft Windows 2000.
How to Troubleshoot the "NTLDR Is Missing" Error Message
When you start your Windows 2000-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, as appropriate to your situation, to repair the Windows 2000 startup environment.
IMPORTANT: Microsoft recommends that you fully back up your data on a regular basis. This is the best defense against data loss, and it 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 to inquire about how to obtain, and then install the latest BIOS update that is available for the computer.
For information about how to configure and how 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 computer manufacturer, click the appropriate article number in the following list to view the article in the Microsoft Knowledge Base:
65416 Hardware and software vendor contact information, A-K
60781 Hardware and software vendor contact information, L-P
60782 Hardware and software vendor contact information, Q-Z
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 sites Part 1
243971 List of BIOS manufacturer Web sites Part 2
To repair the Windows startup environment, use one or more of the following methods, as appropriate to your situation.
Method 1: Use a Boot Disk to Start the Computer
1. Create a Windows 2000 boot disk that contains the following files:
Ntldr
Ntdetect.com
Boot.ini
Ntbootdd.sys
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
2. 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 create a boot disk, click the following article number to view the article in the Microsoft Knowledge Base:
311578 How to edit the Boot.ini file in Windows 2000
3. Insert the boot disk into the computer's floppy disk drive, and then restart the computer.
4. 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
1. Use the Windows 2000 Setup disks to restart the computer, or use the Windows 2000 CD-ROM to restart the computer.
2. At the Welcome to Setup screen, press R to repair the Windows 2000 installation.
3. Press C to repair the Windows 2000 installation by using the Recovery Console.
4. Type the number that corresponds to the Windows installation that you want to repair, and then press ENTER. For example, type 1, and then press ENTER. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
229716 Description of the Windows Recovery Console
5. Type the Administrator password, and then press ENTER.
6. Type map, and then press ENTER. Note the drive letter that is assigned to the CD-ROM drive that contains the Windows 2000 CD-ROM.
7. Type the following commands, pressing ENTER after you type each one, where drive is the drive letter that you typed in step 4 of "Method 2: Use the Recovery Console," of this article:
copy drive:\i386\ntldr c:\
copy drive:\i386\ntdetect.com c:\
If you are prompted to overwrite the file, type y, and then press ENTER.
NOTE: In these commands, there is a space between the ntldr and c:\, and between ntdetect.com and c:\.
8. Type the following command, and then press ENTER:
type c:\Boot.ini
A list similar to the following list appears:
[boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect
If you receive the following message, the Boot.ini file may be missing or damaged:
The system cannot find the file or directory specified.
9. If the Boot.ini file is missing or damaged, create a new one. To do so, follow these steps:
a. Use a text editor, such as Notepad or Edit.com, to create a boot loader file similar to the following boot loader file:
[boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /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
301680 How to create a boot disk for an NTFS or FAT partition in Windows
b. Save the file to a floppy disk as 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.
c. 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:\
10. Type exit, and then press ENTER. The computer restarts.
Method 3: Use the Windows 2000 CD-ROM
1. Insert the Windows 2000 CD-ROM into the computer's CD-ROM drive or DVD-ROM drive, and start Windows 2000 Setup.
2. On the Welcome to Setup page, press R.
3. On the Windows 2000 Repair Options page, press R.
4. When you are prompted to select one of the repair options, press M.
5. Press the UP ARROW, press the UP ARROW again, to select Verify Windows 2000 system files, and then press ENTER to clear the selection.
6. Press the DOWN ARROW to select Continue (perform selected tasks), and then press ENTER. The following message appears:
You need an Emergency Repair disk for the Windows 2000
installation you want to repair.
7. Do one of the following, as appropriate to your situation:
? If you have an Emergency Repair Disk, follow these steps:
a. Press ENTER.
b. Insert the Emergency Repair Disk into the computer's floppy disk drive, and then press ENTER.
c. Follow the instructions to repair the installation, and then restart the computer.
-or-
? If you do not have an Emergency Repair Disk, follow these steps:
a. Press L. You receive a message similar to the following:
Setup has found Windows 2000 in the following folder:
drive:\WINNT "Microsoft Windows 2000"
b. Press ENTER.
Setup examines the disks, and then completes the repair process.
For more information about the emergency repair feature, click the following article number to view the article in the Microsoft Knowledge Base:
231777 How to create an Emergency Repair Disk in Windows 2000
If Setup Cannot Locate Windows 2000
If you do not have a Windows 2000 Emergency Repair Disk, and if Setup cannot locate the Windows 2000 installation, follow these steps:
1. Start Windows 2000 Setup.
2. On the Setup will install Windows 2000 on partition page, select Leave the current file system intact (no changes), and then press ENTER.
3. Press ESC to install Windows 2000 to a new folder.
4. 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 2000.
5. Log on to the new copy of Windows 2000.
6. Click Start, and then click Run.
7. In the Open box, type cmd, and then click OK.
8. At the command prompt, type drive:, where drive is the boot drive of the computer, and then press ENTER. For example, type c:, and then press ENTER.
9. Type attrib -h -r -s Boot.ini, and then press ENTER.
10. Type edit Boot.ini, and then press ENTER.
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 2000 Professional" /fastdetect
1R Replace all instances of TEMPWIN with WINNT. The Boot.ini file that appears is similar to the following file:
[boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect
11. Press ALT+F, and then press S.
12. Press ALT+F, and then press X.
13. Type attrib +h +r +s Boot.ini, and then press ENTER.
14. Type exit to quit the command prompt.
15. Restart the computer.
16. At the Please select the operating system to start screen, use the ARROW keys to select Microsoft Windows 2000, and then press ENTER.
17. Start Windows Explorer, locate the following folders, and then delete them:
Tempwin
All Users.Tempwin
Additional Resources
For more information about how to troubleshoot the "NTLDR is Missing" error message, click the following article numbers to view the articles in the Microsoft Knowledge Base:
255220 "NTLDR is missing" error message when you upgrade or install Windows 2000 over Windows 95, Windows 98 or Windows Millennium Edition
228004 Changing active partition can make your system unbootable
883275 You cannot start your computer after you modify the permissions in Windows Server 2003, in Windows XP, or in Windows 2000
Perform a Parallel Installation of Windows 2000
If you cannot resolve the behavior described in the "Symptoms" section of this article by using any of the methods discussed in this article or by viewing the Knowledge Base articles in the Additional Resources section of this article, perform a parallel installation of Windows 2000, and then use Windows Explorer to copy the data that you want to recover from your original Windows installation.
For more information about how to perform a parallel installation of Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base:
266465 How to perform a parallel installation of Windows 2000 or Windows Server 2003
References
For more information about how to troubleshoot startup problems in Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base:
315396 How to troubleshoot startup problems in Windows 2000
For more information about the differences between the Manual and Fast repair options in Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base:
238359 Differences between manual and fast repair in Windows
301645 How to use Recovery Console on a computer that does not start in Windows 2000.
APPLIES TO
? Microsoft Windows 2000 Server
? Microsoft Windows 2000 Advanced Server
? Microsoft Windows 2000 Professional Edition
? Microsoft Windows 2000 Datacenter Server
TROUBLESHOOTING METHOD C
Windows may not start and you may receive an "NTLDR is missing" error message if Windows is not up-to-date and there are too many files in the root folder
SYMPTOMS
If too many files are copied to the root folder of a boot volume that uses the NTFS file system, you may receive the following error message the next time that you restart the computer:
NTLDR is missing
Press CTRL+ALT+DEL to restart.
If you remove files from the root folder, the master file table (MFT) allocation index does not reduce to its original size.
Note If you are using Windows XP with Service Pack 2 (SP2) or you are using Microsoft Windows 2000 with Service Pack 4 (SP4), this is not your issue. View the "More information" section for similar issues.
CAUSE
This problem may occur if the MFT root folder is severely fragmented. If the MFT root folder contains many files, the MFT may become so fragmented that an additional allocation index is created. Because files are mapped alphabetically in the allocation indexes, the NTLDR file may be pushed to the second allocation index. When this occurs, you receive the error message that is described in the "Symptoms" section.
Typically, files are not written to the root folder. This condition may occur if a program regularly creates and removes temporary files in the root folder, or if many files are copied to the root folder by mistake.
RESOLUTION
To resolve this problem, follow these steps:
1. Contact Microsoft Customer Support Services to obtain the Bcupdate2.exe utility. For more information about how to contact Microsoft Customer Support Services, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
2. Create a boot disk for starting your computer. For more information about how to create a boot disk for a Windows XP-based computer, click the following article number to view the article in the Microsoft Knowledge Base:
305595 How to create a bootable floppy disk for an NTFS or FAT partition in Windows XP
For more information about how to create a boot disk for a Windows 2000-based computer, click the following article number to view the article in the Microsoft Knowledge Base:
119467 How to create a bootable disk for an NTFS or FAT partition
Run the following command at the command prompt to extract the Bcupdate2.exe utility from the software update:
Expand drive_letter:\bcupdate2.ex_ drive_letter:\bcupdate2.exe
3. Run the following command at the command prompt to update the boot code of the NTFS boot sector:
Bcupdate2.exe C: /F
Note Other command-line parameters are supported:
/q - Quiet mode (must include /y)
/y - Don't confirm
/f - Force update of in use volume
/t - Only test for old boot code
4. Press Y if you are prompted to update the volume. You receive the following message after you successfully run this utility:
The boot code was updated successfully.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was first corrected in Windows XP Service Pack 2.
This problem was first corrected in Windows 2000 Service Pack 4. For more information about how to obtain the latest service packs, click the following article numbers to view the articles in the Microsoft Knowledge Base:
322389 How to obtain the latest Windows XP service pack
260910 How to obtain the latest Windows 2000 service pack
Note If you install the Windows XP service pack or the Windows 2000 service pack, you will not resolve problems with an existing volume. You must run the utility to update the boot code separately. The service pack will only write the correct boot code for new volumes.
MORE INFORMATION
For more information about a related topic, click the following article numbers to view the articles in the Microsoft Knowledge Base:
318728 How to troubleshoot the "NTLDR is missing" error message in Windows 2000
886215 You may receive a "NTLDR is missing press any key to restart" error message when you upgrade a Windows 98-based computer to Windows 2000 Professional
816793 How to troubleshoot the "NTLDR is missing" error message in Windows Server 2003
842009 "NTLDR is missing" error when you try to run Automated System Recovery in Windows Server 2003
883275 You cannot start your computer after you modify the permissions in Windows Server 2003, in Windows XP, or in Windows 2000
315261 The computer does not start after you change the active partition by using the Disk Management tool
812492 Error message when you start your computer with a non-system disk
228004 Changing active partition can make your system unbootable
APPLIES TO
? Microsoft Windows XP Home Edition
? Microsoft Windows XP Professional
? Microsoft Windows 2000 Professional Edition
? Microsoft Windows 2000 Server
? Microsoft Windows 2000 Advanced Server
Keywords: kbresolve kbwinxpsp2fix kbwin2ksp4fix kbbug kbfix kbwin2000sp3fix KB320397
TROUBLESHOOTING METHOD D
Issue:
NTLDR is Missing.
RELATED ERRORS:
Below are the full error messages that may be seen when the computer is booting.
NTLDR is Missing
Press any key to restart
Boot: Couldn't find NTLDR
Please insert another disk
NTLDR is missing
Press Ctrl Alt Del to Restart
CAUSE:
1. Computer is booting from a non-bootable source.
2. Computer hard disk drive is not properly setup in BIOS.
3. Corrupt NTLDR and/or NTDETECT.COM file.
4. Misconfiguration with the boot.ini file.
5. Attempting to upgrade from a Windows 95, 98, or ME computer that is using FAT32.
6. New hard disk drive being added.
7. Corrupt boot sector / master boot record.
8. Seriously corrupted version of Windows 2000 or Windows XP.
9. Loose or Faulty IDE/EIDE hard disk drive cable.
SOLUTIONS:
Computer is booting from a non-bootable source
Many times this error is caused when the computer is attempting to boot from a non-bootable floppy disk or CD-ROM. First verify that no floppy diskette is in the computer, unless you are attempting to boot from a diskette.
If you are attempting to boot from a floppy diskette and are receiving this error message it is likely that the diskette does not have all the necessary files and/or is corrupt.
If you are attempting to install Windows XP or Windows 2000 and are receiving this error message as the computer is booting verify that your computer BIOS has the proper boot settings. For example, if you are attempting to run the install from the CD-ROM make sure the CD-ROM is the first boot device, and not the hard disk drive.
Second, when the computer is booting you should receive the below prompt.
Press any key to boot from the CD
Important: When you see this message press any key such as the Enter key immediately, otherwise it will try booting from the hard drive and likely get the NTLDR error again.
Note: If you are not receiving the above message and your BIOS boot options are set properly it's also possible that your CD-ROM drive may not be booting from the CD-ROM properly. Verify the jumpers are set properly on the CD-ROM drive. Additional information about checking the CD-ROM drive connections can be found on document CH000213.
Additional information: This error has also been known to occur when a memory stick is in a card reader and the computer is attempting to boot from it. If you have any type of card reader or flash reader make sure that no memory stick is inside the computer.
Computer hard disk drive is not properly setup in BIOS
Verify that your computer hard disk drive is properly setup in the BIOS / CMOS setup. Improper settings can cause this error. Additional information on how to enter the BIOS / CMOS setup can be found in document CH000192.
Corrupt NTLDR and/or NTDETECT.COM file
Windows 2000 users
Windows XP users
Windows 2000 users
If your computer is using Microsoft Windows 2000 and you are encountering the NTLDR error. Create the below boot.ini file on the floppy diskette drive.
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect
Copy the NTLDR and NTDETECT.COM files from another computer using the same Operating System. Both of these files are located in the root directory of the primary hard disk drive. For example, C:\NTLDR and C:\NTDETECT.COM should be the locations of these files on many computers.
? Please keep in mind that these files are hidden system files, if you need additional help with viewing hidden files in Windows please see document CH000516.
Once these files have been copied to a floppy diskette reboot the computer and copy the NTLDR and NTDETECT.COM files to the root directory of the primary hard disk drive. Below is an example of what commonly should be performed from the A:\> drive.
copy ntldr c:
copy ntdetect.com c:
After the above two files have been copied, remove the floppy diskette and reboot the computer.
WNDOWS XP USERS
1. Insert the Windows XP bootable CD into the computer.
2. When prompted to press any key to boot from the CD, press any key.
3. Once in the Windows XP setup menu press the "R" key to repair Windows.
4. Log into your Windows installation by pressing the "1" key and pressing enter.
5. You will then be prompted for your administrator password, enter that password.
6. Copy the below two files to the root directory of the primary hard disk. In the below example we are copying these files from the CD-ROM drive letter "E". This letter may be different on your computer.
copy e:\i386\ntldr c:\
copy e:\i386\ntdetect.com c:\
7. Once both of these files have been successfully copied, remove the CD from the computer and reboot.
Misconfiguration with the boot.ini file
Edit the boot.ini on the root directory of the hard disk drive and verify that it is pointing to the correct location of your Windows Operating System and that the partitions are properly defined. Additional information about the boot.ini can be found on document CH000492.
Attempting to upgrade from a Windows 95, 98, or ME computer that is using FAT32
If you are getting this error message while you are attempting to upgrade to Windows 2000 or Windows XP from Windows 95, Windows 98, or Windows ME running FAT32 please try the below recommendations.
1. Boot the computer with a Windows 95, Windows 98 or Windows ME bootable diskette.
2. At the A:\> prompt type:
sys c:
3. After pressing enter you should receive the "System Transferred" message. Once this has been completed remove the floppy diskette and reboot the computer.
New hard disk drive being added
If you are attempting to add a new hard disk drive to the computer make sure that drive is a blank drive. Adding a new hard disk drive to a computer that already has Windows installed on it may cause the NTLDR error to occur.
If you are unsure if the new drive is blank or not try booting from a bootable diskette and format the new hard disk drive.
Corrupt boot sector / master boot record
It's possible your computer's hard disk drive may have a corrupt boot sector and/or master boot record. These can be repaired through the Microsoft Windows Recovery console by running the fixboot and fixmbr commands.
Additional information and help in getting into the Microsoft Windows Recovery console can be found on document CH000627.
Seriously corrupted version of Windows 2000 or Windows XP
If you have tried each of the above recommendations that apply to your situation and you continue to experience this issue it is possible you may have a seriously corrupted version of Microsoft Windows. Therefore we would recommend you reinstall Microsoft Windows 2000 and Windows XP.
If you are encountering this issue during your setup you may wish to completely erase your computer hard disk drive and all of its existing data and then install Microsoft Windows 2000 / Windows XP. Additional information about erasing the computer and starting over can be found on document CH000186.
Loose or Faulty IDE/EIDE hard disk drive cable
This issue has been known to be caused by a loose or fault IDE/EIDE cable. If the above recommendation does not resolve your issue and your computer hard disk drive is using an IDE or EIDE interface. Verify the computer hard disk drive cable is firmly connected by disconnected and reconnecting the cable.
If the issue continues it is also a possibility that the computer has a faulty cable, try replacing the hard disk drive cable with another cable and/or a new cable.
ADDITIONAL INFORMATION:
? See NTLDR dictionary definition for a complete definition on this term.
Short for NT loader, NTLDR is a program loaded from the hard drive boot sector that displays the Microsoft Windows NT startup menu and helps Microsoft Windows NT/2000/XP load.
? Information about NTLDR error message and how to fix it can be found on document CH000465.
ALSO SEE: Operating System definitions
Operating system definitions
| A | B | C | D | E | F | G | H | I | J | K | L | M
N | O | P | Q | R | S | T | U | V | W | X | Y | Z
Number
*NIX
A
Access path
ACL
Active desktop
Active directory
Active Window
Add or Remove Programs
Add/Remove Programs
Aero
AfterStep
AIX
Apple DOS
Apple menu
Aqua
ASR
Association
Autoexec.bat
Autoplay
B
Background
Balloon
BeOS
Black Screen of Death
Blue Screen of Death
Bourne shell
BSD
BSOD
BOMB
Boot volume
Bootstrap loader
Button
C
Cacls
Cascade
CD
CE
Chevron
Child
Clipboard
Close
Command button
CLSID
Command interpreter
Command key
Command line
Config.sys
Control panel
Cooperative multitasking
CUI
Cursor
D
Daemon
Desktop
Device Manager
Dialog box
Directory
Disk Operating System
Documents
DOS
Double-headed arrow
Dr. DOS
Drop shadow
Dual boot
E
EFS
Enhanced Mode
Epoch
ERD
ESCD
Executable file
Explorer
External command
F
Fatal exception
File
File manager
File menu
File name
File system
Find Fast
Finder
Folder
Fork
Fstype
G
GDI
General Protection Fault
GNOME
Goobuntu
GPF
Graphic User Interface
GUI
GUID
H
HAL
Hard link
HFS
Hibernate
Hidden files
Hierarchical file system
I
IBM DOS
Icon
Inactive window
Initial Program Load
Inode
Install
Internal command
IOS
IPL
IRQ holder for PCI steering
IRQL
J
Journal
Journaling file system
K
Kernel
Korn shell
L
Linux
LiveCD
Load
Logical device
Long file names
Longhorn
M
Mach kernel
Main
Maximize
Menu
Menu bar
Menu-driven
Microsoft diagnostics
Minimize
Mnemonic
Mouse pointer
MS-DOS
Msconfig
Msinfo32
MUI
Multi-user system
Multitask
My Documents
My Computer
MVS
N
NEXTSTEP
Non-pre-emptive multitasking
Non-windows application
NOS
NTLDR
O
Object-oriented interface
Open Apple key
Operating environment
Operating system
OS/2
OSR2
P
Parent
PC DOS
Plumbing
PM
PNP
Pop-up menu
POSIX
Preemptive multitasking
Prefetch
Presentation manager
Program and Features
Program group
Program manager
Prompt
Push-button
Q
Quick launch
R
ReadyBoost
Real-time operating system
Recovery console
Recycle bin
Reinstall
Reserved words
Resize
S
Sad Mac
Safe mode
Scroll
SE
Second edition
Separator
Service Pack
Shared directory
Shell
Sizing handle
Shortcut
Slipstreaming
SP
Spin box
SSP
Start button
Startup application
Startup folder
Subdirectory
Submenu
SuperFetch
SUID
Swap file
Symbolic link
Sysedit
Sysgen
System
System.ini
System 7
System32
System file
Systray
T
Task
Task list
Task manager
Task switching
Taskbar
Temporary directory
Temporary file
Three finger salute
Tiling
Title bar
Toolbar
Tooltip
TOPS
TOS
Trash
TSR
TweakUI
Tux
U
Ubuntu
Unformatting
Uninstall
Unix
User interface
UUID
V
Variant
VBR
Virtual machine
Vista
W
Wallpaper
Wfw
WGA
Widget
WIMP
Win.com
Win.ini
Win3x
Win9x
Window
Windows
Windows 2000
Windows 2k
Windows 3.0
Windows 3.1
Windows 3.11
Windows 3.x
Windows 95
Windows 95B
Windows 98
Windows 9x
Windows Aero
Windows CE
Windows DOS session
Windows for Workgroups
Windows for Workgroups 3.1
Windows for Workgroups 3.11
Windows key
Windows ME
Windows NT
Windows XP
Wine
Winoldap
Winpopup
WinSE
Workplace shell
WOW
X
X-Window
XENIX
XP
Y
Currently no listings
Z
Currently no listings
