Skip to main content

NTLDR is Missing

NTLDR stands for New Technology Loader, and it is a program that is usually loaded from the hard drive boot sector. It is used to display the Microsoft Windows NT startup menu, and it helps load Microsoft Windows NT. "NTLDR is missing" is an error that prevents Windows from starting up, and a number of factors can cause this error. The procedure to fix this error depends on its cause.

Here are some of the known causes and their solutions:
Computer is booting from a nonbootable source – One of the common reasons for this error is using a nonbootable floppy disk or CD-ROM to boot the computer. You can prevent this error by ensuring that no diskette is in the computer unless you want the computer to boot from it. If you want the computer to boot from the diskette and you’re getting this error, then the diskette may not have all the required files. Also, you may receive this error while installing Windows XP or Windows Server 2000. This error can be prevented by ensuring that the BIOS has the appropriate boot settings.

Computer hard disk drive is not properly set up in BIOS – Improper hard disk drive settings can cause the "NTLDR is missing" error; to avoid this, you need to ensure that hard disk drive is properly configured.

Improper configuration in boot.ini file – Ensure that boot.ini is on the root directory of the hard disk and that it points to the correct location of the operating system. Also, the partitions must be properly defined.

Upgrading from Windows 95, Windows 98, or Windows ME computer that is using FAT32 – If you’re getting this error while performing the aforementioned upgradation, then try the following steps: Use a Windows 95, Windows 98, or Windows ME bootable diskette to boot the computer.

At the A:> prompt, type: Sys c: Press the enter key, and wait for the message "System Transferred." Once you’ve received this message, remove the floppy diskette and then reboot the computer.

Addition of a new hard disk drive – If you’re adding a new hard disk to a system that already has Windows installed on it, then you’re likely to receive the "NTLDR is missing" error. So, ensure that the hard disk drive being added is a blank drive.

Corrupt master boot record or corrupt boot sector – "NTLDR is missing" error is also caused by a corrupt boot sector and/or corrupt master boot record. To fix this, you need to use the Windows Recovery console. Fixboot and fixmbr commands are used for this purpose.

Using a corrupted version of Windows XP or Windows 2000 – If you’re running a corrupted version of Windows on your computer, then you’re likely to experience this error very frequently. Reinstalling Windows XP or Windows 2000 is the best solution in this case.

Hard disk drive cable is either loose or faulty – If your computer hard disk drive uses an EIDE/IDE interface, make sure that the hard disk cable is firmly connected. Replacing the hard disk drive cable or disconnecting and reconnecting it can fix this problem.

Popular posts from this blog


The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N