Messed up OS booting after failed installation of W7 using W8.1 on the other drive

[Mike Rook]

Hello,
to quickly get an idea of what is going on, please see this:
https://neosmart.net/wiki/winload-efi-missing-corrupt/

However, my problem is a bit more complicated. I use two OS on my PC - W7 and W8.1. I needed to make a clean install of W7, so I did it like I always do (at least I think so). I downloaded W7 iso from mircrosoft page using my key, wiped the drive, made new patition, then used daemon tools to boot the iso file and install the system. However, the installation failed and left me with the problem you can see above.
I have already installed the W7 on the other drive succesfully using flash drive boot converted from the iso file. But while booting the drive where W8.1 is, I still get the W7 boot error screen. So, the computer thinks, there should be W7 on the drive. How do I explain to the system there is no such system and it should just boot W8.1 normally without attempting to boot winload.efi? If you understand it well, you can see there is no reason in trying to repair W8.1, because this OS has no issues at all, it is the trace left somewhere on the drive after the failed installation.
I have already wiped temp files issued on the date of the accident - no change. It is not a system breaking error, but it makes me a bit upset to see this screen each time I launch the computer.

Thank you for your tips, guys!

 

[USAFRet]

You need to go back to the beginning and start all over again.
Create a DVD or USB bootable, not daemon from the other drive.
Disconnect ALL drives except for the one you want the OS on.
Install, deleting ALL existing partitions on that drive.

Or, you could mess about with EasyBCD and attempt to "fix it".

Personally, I'd just start over.

 

[rgd1101]

MERGED QUESTION
Question from Mike Rook : "Cleaning W8.1 after failing to install W7 on another drive using W8.1 drive"

Hello,
I needed to reinstall my W7 drive, thus I used my other OS, which is W8.1 to do it. I downloaded ISO from microsoft using my W7 key, which went ok. I have wiped the drive entirely, made new patition, I have assigned a letter, I have set it to be a NTFS drive of GPT type, everything just as it should be.
I used daemon tools in W8.1 to install clean W7 on the other drive, not upgrade. Everything went ok until the 1st restart. While booting, it left a message there was something wrong with the winload.efi and the installation could not go on.
Problem is, whenever I start the comp now, it does the same thing, so the failed instalation left some garbage in W8.1 and I have no idea how to get rid of it without destroying this OS.
1st thing is - I need to make this functional OS completely OK
2nd thing is - any idea why the installation failed? Maybe some tips to make it work (I have already made a USB bootable device with W7, but it did not want to install OS on GPT drive which I do not understand why and I do not feel like changing it to MBR.

Well, I hope I made myself clear.
Thank you for your tips, guys!

Hi,
update:
to see what is going on with the boot:
https://neosmart.net/wiki/winload-efi-missing-corrupt/
BUT, there is a problem. It looks like my attempt to intall W7 using W8.1 caused the system to think W7 should be on the drive where W8.1 is, thus while booting I get this W7 booting error, because, simply, there is no such system on that drive. So the question now is: How do I tell the system it should not try to boot W7 from that drive? Because repairing boot of W8.1 makes no sence since that OS has no problem with booting.

 

[Mike Rook]

You need to go back to the beginning and start all over again.
Create a DVD or USB bootable, not daemon from the other drive.
Disconnect ALL drives except for the one you want the OS on.
Install, deleting ALL existing partitions on that drive.

Or, you could mess about with EasyBCD and attempt to "fix it".

Personally, I'd just start over.

Thank you very much!
I treid the EasyBCD - there were 2 boot entries and one of them was installation boot set as primary. I just deleted it using the program and the issue is gone.
You made me happy, man.

 

[Mike Rook]

Sorry, rgd1101, I wanted to delete the previous post, you were quicker