

It seems like this is the replacement (since Windows Vista) for the boot.ini file and you need a special command line tool (BCDEdit) to modify it. I then proceeded to go down the road of creating a new Boot Configuration Data file, which I had never done before. This led me to the Nuclear Holocaust recovery process documented in the Neosmart wiki. Additionally, the /fixmbr switch reported it worked correctly, but the /fixboot switch reported “element not found.” If it doesn’t work, reboot, repeat the above steps and addĪnd reboot again. I first started by using the bootrec command line tool to attempt to repair the boot records. It reported to have found the problem and fixed it (no valid boot partition), but upon rebooting I was left with the same error. I let it perform the automatic startup repair. So, I got the Windows 7 DVD and booted from it and went into the repair mode, which seems to be very similar to what Windows Vista offers. I also made several changes to the boot order to insure something weird wasn’t going on there. I disconnected my CD and DVD drives, two external hdd trays and my USB card reader, just to make sure it wasn’t trying to boot off an invalid device. I’ve been very pleased…until now!įrom a h/w perspective, I went through several iterations of disconnecting disk devices on the inside of the tower to eliminate each device as a potential invalid boot source. I run a RAID 1 array using two Seagate ST3750640NS drives with Intel Storage Manager. My computer is a home built tower with an ASUS P5Q-EM motherboard which was purchased on, so it’s not very old! I was thinking “infant mortality failure” but I didn’t want to give in to a hardware problem just yet. I seriously doubt that downloading the VMWare player had anything to do with my problem. I’m not even sure what caused it to reboot. No power failures or anything like that had occurred. This was all very interesting because I hadn’t done anything to reboot the computer.

"Reboot and select proper boot device, or insert boot media in selected boot device and press any key." When I came back to it about an hour later I was presented by a boot screen that said, I had just walked away from my Windows 7 desktop after initiating a download of some VMWare software.
