Any reason for NT Loader Missing?

  • Thread starter Thread starter Lurka
  • Start date Start date
L

Lurka

Hello,

is there any known reason for the "NT loader missing" syndrome? We had
this "problem" with a few XP machines and also a win2k3 server. I
cannot grant the incompetent people handling them didn't screw'em up
(like happily deleting the system folder), but what I'm asking here is
whether any bug has ever been reported that may cause the OS to
suddenly "disappear" after a reboot.

Thank you,
/_urka
 
Lurka said:
Hello,

is there any known reason for the "NT loader missing" syndrome? We had
this "problem" with a few XP machines and also a win2k3 server. I
cannot grant the incompetent people handling them didn't screw'em up
(like happily deleting the system folder), but what I'm asking here is
whether any bug has ever been reported that may cause the OS to
suddenly "disappear" after a reboot.

Thank you,
/_urka
Click to expand...

A common reason for this used to be leaving a non-bootable floppy in the
drive. These days, when fewer & fewer machines even have a floppy
drive, it isn't so common.
 
NTLDR is missing, why does it happen?

[[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 ]]
http://support.microsoft.com/?kbid=318728

[[Cause:
* Computer is booting from a non-bootable source. I.e. a disk left in the
the floppy or CD drive.
* Computer hard disk drive is not properly setup in BIOS.
* Corrupt NTLDR and/or NTDETECT.COM file.
* Misconfiguration with the boot.ini file.
* Attempting to upgrade from a Windows 95, 98, or ME computer that is using
FAT32.
* New hard disk drive being added.
* Corrupt boot sector / master boot record.
* Seriously corrupted version of Windows 2000 or Windows XP.
* Loose or Faulty IDE/EIDE hard disk drive cable. ]]
http://www.computerhope.com/issues/ch000465.htm

[[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. ]]
http://support.microsoft.com/kb/314057

Make sure that there are no disks in any removable drives when you boot.

Error Message When You Start Your Computer with a Non-System Disk
http://support.microsoft.com/kb/812492

An NTLDR or NTDETECT.COM Not Found Error
http://support.microsoft.com/kb/555304

Windows XP Does Not Start on a Computer That Is Configured for Dual Booting
http://support.microsoft.com/kb/315233

You Receive an "NTLDR Is Missing" Error Message When You Start Your Computer
http://support.microsoft.com/kb/320397

HOW TO: Troubleshoot the "NTLDR Is Missing" Error Message in Windows 2000
http://support.microsoft.com/kb/318728

Err Msg: Boot - Can't Find NTLDR, or Windows Could Not Start..
http://support.microsoft.com/kb/101862

"NTLDR Is Missing" Error Message When You Upgrade or Install Windows XP Over
Windows 95, Windows 98, or Windows Millennium Edition
http://support.microsoft.com/kb/314057

The Computer Does Not Start After You Change the Active Partition by Using
the Disk Management Tool
http://support.microsoft.com/kb/315261

Cannot Start Windows XP After You Install Windows 2000
http://support.microsoft.com/kb/283433

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
Lurka said:
Hello,

is there any known reason for the "NT loader missing" syndrome? We had
this "problem" with a few XP machines and also a win2k3 server. I
cannot grant the incompetent people handling them didn't screw'em up
(like happily deleting the system folder), but what I'm asking here is
whether any bug has ever been reported that may cause the OS to
suddenly "disappear" after a reboot.

Thank you,
/_urka
Click to expand...


The most common cause of this particular error, since the days of
WinNT, has been people trying to boot the computer in question with a
non-bootable floopy disk in the drive. Another frequent cause is a
corrupted or damaged C:\Boot.ini file.


--

Bruce Chambers

Help us help you:



They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. -Benjamin Franklin

Many people would rather die than think; in fact, most do. -Bertrand Russell
 
Back
Top