Sounds like you altered the boot information with the second install and it's getting hung up looking for boot information and an OS that isn't there.
Give this a try....
open an elevated command prompt through a recovery media of some sort. Many options to choose from.
Type the following. (the text in caps only. the rest is comments. Hit Enter after each line.
FIrst we'll try the simple fix:
BOOTREC/FIXMBR
BOOTREC/FIXBOOT
BOOTREC/SCANOS
BOOTREC/REBUILDBCD
(Exit and reboot)
Assuming this is a GPT/non UEFI bios installation, this should fix it. If that fails. We'll do something a little more complex. Again, elevated command prompt window.
DISKPART SEL DISK 0 (Assuming the system disk is in fact, 0. If not, then sel disk 1)
LIST VOL (you may see several volumes here)
One of your volumes should be an EFI partition. It will b a FAT32 partition without a drive letter. Select the EFI partition. For example, if the EFI partition i volume 2, then type
SEL VOL 2 (again, the EFI partition can be any number and the volume number you type needs to be that number. I have heard of cases where the EFI partition just totally disappeared. I've also had people not realize they were using a traditional boot.ini file instead of EFI. Unfortunately there's no way for me to tell them apart. So hopefully you know what you have. )
ASSIGN LETTER = Q: (This is an arbitrary drive letter we're temporarily assigning that is not in use in my system. Make sure it's not in use on yours)
it will tell you it's assigned a letter. Next type:
EXIT (it should exit Diskpart, not the command prompt. You need to stay in the cmd window
CD /D Q:\EFI\MICROSOFT\BOOT\
(Q is the arbitrary drive letter we assigned.
It's possible that the BOOT folder is located at EFI\BOOT or some other directory on the drive. If you can't get to the boot directory as stated, use the DIR /P command to view the folder and see if you can navigate to the folder to figure out the path. )
BOOTREC /FIXBOOT (basically what we had to do here is repair the volume and since you can't execute repairs on a drive with no drive letter, we gave it one. Then we changed to that drive and executed a command to fix it. Now we'll rebuild the BCD store that has the boot data on it.
You should still be on the Q drive. We'll rename the existing BCD store just for kicks. Probably unnecessary if it is messed up but better to be safe than sorry.
REN BCD BCD.old
(Now for the master fixer command thingie)
BCDBOOT C:\WINDOWS/L EN-US/S Q: /F ALL (This says to get the Windows boot environment data from the system windows directory on the disk you're using and push it to the Q drive. The /F part updates the BIOS to match. NOTE: I'm assuming that your Windows installation is on the C drive. If not, use the drive letter that Windows is on.
Facebook
Twitter
Instagram