Sign in with
Sign up | Sign in
Your question

Computer wont start ntldr is missing

Last response: in Windows 7
Share
September 1, 2012 4:10:54 AM

Hello,
computer wont start ntldr is missing
a b $ Windows 7
September 1, 2012 4:25:09 AM

man, that sucks. It is often easiest to reformat the computer and start over from scratch when this happens, but you can put in a windows disc and try the repair option.

This can often be caused by the beginnings of HDD failure, so be sure to test your HDD for errors when you get a chance. Once a drive starts to die, the rest of it tends to go rather quickly.

This can also be caused by a virus. Try repairing your computer with a windows disc and then get into safe mode and run your antivirus software from there. Most virii that attack nt loader tend to be pretty bad, so formatting is suggested to be sure that it is gone.

Lastly, this can sometimes be caused by major hardware changes such as a motherboard, or a bad HDD cloaning process to a new drive. Major hardware changes sometimes will require you to reformat the system to take into account these changes, or else use software such as the for-pay version of Acronis which will let you make hardware agnostic image deployments of Windows to get arround such issues.


Good luck!
m
0
l
September 9, 2012 6:11:42 PM

I get the same exact message. The only difference is mine is a completely new build with a brand new WD 500 GB HDD. Help?
m
0
l
Related resources
a b $ Windows 7
September 10, 2012 3:41:52 PM

same advice as above. Try running the repair option from the OS disc, otherwise reformat and reload windows.

Test disc for errors or problems, and if any do show up then be sure to RMA your HDD while it is under store warranty as that is much easier to deal with than the manufacturer's warranty.
m
0
l
September 10, 2012 6:35:36 PM

Also make sure you did not plug the drive into a different sata port?

Since original install, for example windows was installed while 2 drives was installed, windows might add the boot loader to the physical hdd 0, and windows might be on hdd 1, and now since 0 and 1 was swapped or one was removed with ntldr, you get this nasty error.


m
0
l
a b $ Windows 7
September 11, 2012 12:15:48 AM

Drive letters are assigned to drive names, not SATA ports, so moving drives to different ports should not be an issue. BIOS will scan all drives for something bootable, and try to boot from it, no matter where it ended up, so it should not be an issue there either. In fact, the only times I have seen this happen is from either a virus, or a failing drive. Not saying that it could not be something else... just highly unlikely.
m
0
l
September 11, 2012 8:33:23 AM

CaedenV said:
Drive letters are assigned to drive names, not SATA ports, so moving drives to different ports should not be an issue. BIOS will scan all drives for something bootable, and try to boot from it, no matter where it ended up, so it should not be an issue there either. In fact, the only times I have seen this happen is from either a virus, or a failing drive. Not saying that it could not be something else... just highly unlikely.


Not true.
It depends on your BIOS. Most BIOS will use HDD's in Legacy/IDE mode by default and then drive position relative to port is VERY IMPORTANT. :fou: 
m
0
l
!