Thread: Lost Win 8 DP fancy new Boot Screen

First make sure that you have a current image of your disk(s)/partition(s) just to make sure you have a strong fall back position.
Use either OS to label your drive(s) / partition(s) (Windows7 and Windows8) to help resolve any confusion during the process.
Here's what I did to restore the Windows 8 boot menu.
I booted from the Windows 8 DVD install media and select the repair option / advanced options / command prompt
In the command prompt I enumerated my drives by simply using the cd\ and the dir command to see which one was which
I found that X:\ was my current boot media environment
C:\ was my reserved system partiion
D:\ Was my disk labeled Windows7
and E:\ was my disk labeled Windows8
Yours may very well be different for various reasons
With this information I typed the following command
bcdboot E:\Windows hit enter
typed exit hit enter
rebooted and the Windows 8 multiboot menu was back.
Hope this helps.
Randy

Trouble is correct about the proper command, but all you have to do is open an Adminstrative command prompt from within Win 8. If C: is the Windows 8 partition, type:

bcdboot C:\Windows

I don't like it because it reboots my system when I go to Windows 7.

Originally Posted by Saltgrass

Trouble is correct about the proper command, but all you have to do is open an Adminstrative command prompt from within Win 8. If C: is the Windows 8 partition, type:

bcdboot C:\Windows

I don't like it because it reboots my system when I go to Windows 7.

Thanks Clark, good to know that I was right and also good to know that there are some step savings to be had. However this was not an option for me as I was caught, for reasons unknown to me at this screen and unable to boot into either. Not sure what I did to get myself into that problem, just know what I did to get my self out of it and now know that I can bring up either boot menu using that technique when needed. And I agree about the issue with the reboot to bring up the Win7 install, seems rather a pain and hopefully will be worked out in subsequent release maybe, maybe not.
Regards
Randy

That is a good error message, as far as it does give some pertinent information.

Oh, and I have never run a Virtual install, so not really aware of how that might react...