thank you for that information, I have run the mini windows xp and have exported the bcupdate.exe into the C drive, unfortunately when I try and run it in dos prompt I get the message that C: is running and I cant run the Bcupdate any ideas?
ntldr missing error message Windows xp home
Hey,
I turned my pc off the other night closed as normal but now I am getting the NTLDR missing error message, I do not have the Windows dics as it is a 6 year old pc. The computer is a Pachard Bell but I have upgraded the system and I dont think it has any of their parts left, I have norton running on the system, any ideas how to fix this? I have looked at a lot of help pages but all of them talk about the windows cd, is it a major problem if I do not have this?
Any help would be great.
Windows for home | Previous Windows versions | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
55 answers
Sort by: Oldest
-
Anonymous
2012-04-06T23:54:46+00:00 -
Anonymous
2012-04-07T18:47:50+00:00 While it is possible that a fragmented MBR is the issue, I doubt it is. And, as noted above by Wunders, if your computer has sp2 or later it is not the issue as a fix for the issue was added to sp2.
There are a number of thing which can cause the NTLDR missing error, including, but not limited to, the hard drive. To fix this issue, one must usually use the process of elimination.
Personally, I would first have you go into the bios (system setup) and make sure the hard drive is listed. If not, you have found your problem. If it is listed you can move on to the steps I have provided above.
-
Anonymous
2012-04-09T13:49:21+00:00 Thank you for this update, I checked the Bios setup and my hard drive is showing, what next?
I have sp3 loaded.
-
Anonymous
2012-04-09T14:42:24+00:00 Thank you for this update, I checked the Bios setup and my hard drive is showing, what next?
I have sp3 loaded.
As both Tech-Geek and Wunders correctly pointed out, since you are running XP at the SP3 level, you do NOT need to pay attention to the advice to run BCUpdate2.exe.
The first thing you should do is boot off the Hiren's CD and go into Recovery Console. Then select your installation (probably "1") and enter the password for the "Administator" account (probably no password, so just press the enter key). At the C:\WINDOWS prompt, enter the following command"
chkdsk /r
(there is a space before the slash)
This will take a long time to complete, so be patient! Also you might even need to run it a second time.
If that does not solve the problem, you will need to rebuild the boot.ini file (the following is based upon instructions from regular contributor JoseIbarra):
cd \ [if you are not already at the C:\ prompt]
attrib -shr boot.ini (removes the System, Hidden, Read Only attributes)
ren boot.ini boot.ini.bak (rename the potentially afflicted file; THIS IS CRUCIAL!)
bootcfg /rebuild (run bootcfg /rebuild and create a new c:\boot.ini file)
The reason you need to rename the current (potentially afflicted) boot.ini is so that when you run the bootcfg /rebuild command, you do not build on top of the current suspicious boot.ini file.
Hopefully there will be ONLY ONE identified Windows Install:
(If not, let us know!)
When you are asked "Add installation to boot list?" enter Y (then press Enter key)
When bootcfg /rebuild asks for Load identifier enter whatever text is appropriate (this is strictly for show), in your case:
Microsoft Windows XP Media Center Edition (then press Enter key)
When it asks for load options enter:
/fastdetect /noexecute=optin
Press Enter to create the new c:\boot.ini file.
When you get done, you can see the contents of your new c:\boot.ini file by entering this command:
type boot.ini
If the c:\boot.ini file doesn't look right, just delete it and start over.
This is what your boot.ini file will hopefully look like:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Media Center Edition " /noexecute=optin /fastdetect (this is one line [beginning with multi]; watch the wrap!)
Note that this part of the instructions above is CRUCIAL:
ren boot.ini boot.ini.bak
This command accomplishes two things:
- It backs up your messed-up boot.ini file. It is always prudent to make backups!
- It effectively deletes boot.ini from your system. If you do not delete boot.ini, you will wind up with that big mess you described where you have seven or so operating systems to choose from! Once your boot.ini file is deleted, you can then run bootcfg /rebuild and your new boot.ini file should be perfect and sleek and clean. :-)
-
Anonymous
2012-04-09T20:50:30+00:00 thank you for that great information, I am geting stuck on the part about the recovery console on the cd options, I have not been able to find this, please could you let me know where this is in the options on the cd.
cheers