Windows 7 Won't Boot, MBR or BCD or something Windows needs to boot NOT HW related.

KT888

Distinguished
May 5, 2012
79
0
18,640
Windows 7 Ultimate won't boot. I shut it down normally last night but then my cat moved the mouse on my desk which causes my PC to wake up and since I had just closed it because I was turning in for the night and I did not want it to boot up again I unplugged it quickly. It hadn't reached windows and I'm pretty sure post hadn't even run yet or finished at least but...

This morning Windows won't boot I didn't add any new hardware or software and I'm thinking boot record or C\boot directory has been corrupted or something. BCD corrupted or some problem with the partition record or some file that was being used when the power was cut didn't close properly and became corrupted. Anyway some file Windows needs to boot.

The Windows drive that won't boot works fine if I connect it to another Windows installation so it's not the drive itself and I can run all the hardware in my system from another Windows Installation (A clone of the dead drive) so it's not an issue with any of the hardware connected to the system.

I don't have the experience to know what those files are specifically and I was hoping someone out there would be willing to share their knowledge & expeience with me.

Chronologically what happens is

machine boots, says Windows failed to start. A recent hardware or software change might be the cause.
Lists two options

- Launch Staretup Repair (recommended)
- Start Windows Normally

Startup Repair fails says
"Startup Repair cannot repair this computer automatically
"If you have recently attached a device to this computer, such as a camera or portable music player, remove it and restart your computer blah blah blah and on it goes.
It says Click Finish to exit and shut down your computer.

System restore says "No restore points have been created on your computer's system drive."

i checked the memory and it's fine.

Launching Windows normally there is actually a BSOD but i can't read anything that displays because my system reboots immediately. When i comes up again it says
"reboot and Select proper Boot device
or Insert Boot Media in selected Boot device and press a key"

So my machine is trying a different drive on reboot but if I force it to use the Windows drive it's a repeat of the above.

I do have an earier clone of this drive that does work (It's just an earlier version) so I have a copy of any files windows needs if someone could help me know what files windows needs.

I checked the MiniDumps folder in the Windows folder and there are no MiniDumps of the failure.

Thanks to any who can help.
 

Well this means it's not the boot files since it does boot.
I had this happen to me a short while back and it was due to the registry being messed up,this fixed it for me.
https://www.sevenforums.com/tutorials/139576-startup-repair-infinite-loop-recovery.html
Since you can connect the drive to a working version of windows it's much easier to do so and do the necessary steps from windows,although still using cmd (command prompt) so that you will copy protected files.
 

KT888

Distinguished
May 5, 2012
79
0
18,640
Just to clarify the drive does not boot. I meant by that it will do post (A pre Windows thing) I can get into the bios but when it tries to boot into windows it won't do that.

So I did as you suggested and it didn't work
I replaced the files from within Windows since I can see the drive fine as an extra drive.

When I booted up with the drive after replacing the files A blue screen (Not like a BSOD) more like the blue Windows desktop background they use. It doesn't fill the screen (like it's using a lower resolution)
It just sits on that screen for 2 or 3 minutes then it reboots and does the exact same thing.
I let it go like that 4 times (just in case it was actually doing something productive)

Well it appears now I'm really s...d.
I just copied back the files the instructions had me make a copy of and the drive is still doing the same thing. sits on the blue screen for a few minutes and reboots. and again and again etc.

Any other ideas?
I can still see the drive in Windows.

...
Sigh