There are several typical causes …

Option 1:

The first possibility is very simple and yet probably the most common. It was simply a floppy disk in the floppy drive of the computer and forget trying now from this disk to start.

Option 2:

The second possibility occurs frequently in the following situations:

Win98SE update to Windows XP
Win98SE update to Windows 2000

Usually this error after the first reboot, ie The installation is carried out without problems. Errors can happen especially when Win98 on a large partition with the FAT32 file system is installed.

Is that the case can be quite promising, try:

Computer with Win98SE Startup Disk to restart at the command prompt, then sys c: type -> Reboot
By the command sys c: Win98 of the required system files such as MSDOS.SYS Io.sys and rewritten. After you’ve restarted Win98SE has tried it the desired update to Windows XP or Windows 2000.

Option 3:

If you have two different types of RAM that is used unilaterally and both sides filled with memory modules, is also very often the case with Win XP, the “NTLDR is missing” error. (Tip submitted by M. Reichmann Email: M_Richman@web.de)

Option 4:

After installing a second operating system starts only just installed the operating system, Windows XP, but no more. Through this installation, the boot sector and the bootloader changed. That then leads to error NTLDR is missing. To turn back simply add the computer directly from the Windows XP CD and restore console. Then the following commands.:

Fixmbr C:

FIXBOOT C:

COPY x: \ I386 \ NTLDR C: \

COPY x: \ I386 \ NTDETECT.COM C: \

The x in the commands you need to naturally replace the letter of your CD-ROM drive is. After successful repair, you can when you start between Windows XP and Windows 2000/98/ME choose, depending on what operating systems are installed.

Here you can find other possible causes for the error NTLDR is missing in Windows XP.

Option 5:

In BIOS, the boot disks (boot order) adjusted (like me).
Features: ASUS board P4C800E Deluxe, Win XP, 3 disks (1 on extra PCI controller).

I found this by booting from the original Win XP SP1 CD option “rescue console.” He offered me namely, Windows D: \ WINDOWS to start. There was the file prior to NTLDR well.

This record was previously always C: \ been.

Then I looked up in the BIOS. There was indeed a boot disk the 3rd Hard disk set, at an extra controller (PCI) was contaminated. I have the 1st again Plate (on the C: \ was) set and everything ran again.

Why is the BIOS-ridden, but I can not say.

Option 6:

Also, a virus can cause this error. E.g. Trojan.Killfiles the virus. More information about this virus can be found on the websites of Symantec:

http://securityresponse.symantec.com/avcenter/venc/data/trojan.killfiles.html

Norton is able to detect the virus, but not remove it. After removal, for example, with AntiVir BEDV H can be the guidance system with the possibility of 4 was up and running again make.

Option 7:

A very simple solution for this error may be that you change the boot order. I have a new system up and it was booting from the floppy disk to be accessed. After the drive behind the CD-Rom with scheme CD (XP) was ranked (/ - buttons) worked to install correctly.

Possibility 8:

Mann has tried with a clone tool (Ghost or other) to work, it will be a temp. Partition …. But this remains and is even with status active set.
Solution: boot disk with “fdisk” and use the boot partition with the status of “Active”.