New
#11
k, were not there but were getting places. NTLDR is missing crtl alt delete to restart
That's fine - you might fix it with running startup repair 2-3 times,
or use cmd prompt again and type:
bootsect /nt60 c: /mbr ( or all instead of c - either will do)
then press enter.
Last edited by SIW2; 06 Nov 2009 at 23:07.
SUCCESS! It's amazing how quickly u had that licked when I spent way more time then id like to admit meandering through web tutorials and "maybe I'll try this". Just got a new mobo and win7 ulti so you just made my weekend now that they are functional again :)
I had the same issue as the OP just now.
Found this thread using my phone. Fortunately, this fix worked for me as well.
Does anyone know what causes this issue? I'd like to prevent stuff like this from happening.
The only things out of the ordinary are:
Solid state hard drive.
Another slave drive was attached with a valid Vista 32 install on it (no steps were taken to dual boot or anything).
Windows update recently occurred.
Thanks SIW2, you helped me out a lot!
This thread has been helpful so far. Unfortunatly I haven't been able to resolve this issue on my PC just yet. I had the identical issue as OP. I went through the DOS terminal and typed:
Diskpart
lis vol
I found 2 partitions, and both were in healty status.
I then sel vol C
act
At this point I restarted and recieved the same error as OP:
NTLDR is missing
Press Crtl+Alt+Delete to restart
so I entered into a DOS terminal again and entered: bootsect /nt60 c: /mbr
I am now recieving the error:
BOOTMGR is missing
Press Ctrl+Alt+Del to restart
I have run startup repair several times and still I recieve the same error. Does anyone have any advice to help me fix this issue on my PC? I would really appreciate ANY help I could recieve. Thanks.
Hi will,
Let's start from the beginning.
You already have 7 installed and are now unable to boot ?
What partitions did diskpart list, is there a small 100mb partition and your main windows partition?
Are you awake? LOL
Sorry it took so long to respond. I can honestly say that I didn't think that I would recieve a response so quickely. Thanks for the response.
As it turns out, my buddy had this problem before and he recommended that I check the partion that was turning up as healthy and make sure that it was on the correct HD.
I looked and sure enough the partitions on my primary hard drive weren't even showing up. I checked my cables, and subsequently found the source of my trouble. As oddly as this sounds one of my power cables must have gone bad, because after changing the power suppy cord to my HD it booted up perfectly. Sorry about this false alarm.