EasyBCD 2.1.2 "broke" Bootloader and can't acess Win 7 (black screen)

Hi, to start of I must say "I know that feel bro". Basically I have the exact same computer and I too tried to install Ubuntu (university course related) resulting in damaged EFI. I spent countless hours on the web looking for solutions only to arrive here, the exact same problem. However since september there were no new posts whatsever. Did you manage to fix it, how? The thing is that I see myself tampering with it more and more only to make it worse... So im not sure if I should perform the HD clean, partially because I dont want to lose my files, but moreover because I want to keep the separate recovery partition.

Please update me on your progress, would be of immense help.

Have you confirmed the Win7 or it's 100mb System Reservd boot partition is marked Active, then run Startup Repair - Run up to 3 Separate Times.

If so try the other boot repair options in Troubleshooting Windows 7 Failure to Start.

You wouldn't want to clean the HD if you want to run Factory REcovery from its partition on the HD and it still will boot, but I'd run the Clean command if you boot Restore Disks or the Win7 installer to Clean Reinstall.

Thank you for the fast reply! The problem is that I cant make the recovery partition active, it says that since it is not in MBR format it is not possible to do so. Thus the only choice I have left is to do is to clean format the whole HD and install a fresh copy of Windows? Will this change my HD file system to MBR, is this bad because the computer is originally based on GPT. By the way I did enable the legacy stuff, nothing changed though.

Unplug all other HD's and peripherals, Boot into BIOS setup to see if there is an EFI Boot Disk in BIOS Boot order. If so remove it, set DVD drive first to boot. If EFI BIOS also set to Legacy BIOS. Then set SATA controller to AHCI. Save changes and Exit.

Then boot into installer DVD or flash stick burned or written using tool and latest ISO here.
How to Boot your Computer from a Bootable CD or DVD

At first installer screen Press Shift + F10 to open a Command Box, type:

DISKPART
LIST DISK
SEL DIS 0 (after confirming Windows 7 target HD #)
CLEAN
CREATE PARTITION PRIMARY SIZE=102400 (for 100gb partition, adjust as desired)
FORMAT FS=NTFS LABEL="WINDOWS 7"
ACTIVE
EXIT
EXIT

Next click Install Now to Clean Install Windows 7 to the partition you created. If it fails then report back at which step and the verbatim error message.

In addition read over these steps to understand the tools and methods which work best to get and maintain a perfect Clean Reinstall - Factory OEM Windows 7. The steps are the same for retail.

Thank you very much :) Worked flawlessly!

Installed windows and its all good, however after doing a check using disk part (run from the cmd) I only found listed the 2 partitions I set: the windows partition and the data, i.e. there isnt an existing partition containing the gpt boot loader or whatever its called. My question arises from the fact that I am now using an MBR partitioning whereas the computer was designed to use GPT. Would this pose any future problems with hardware/ software, would it run as fast/ smooth as before?

Please post back a screenshot of your maximized Disk Management drive map and listings:

1. Type Disk Management in Start Search box.
2. Open Disk Mgmt. window and maximize it.
3. Type Snipping Tool in Start Search box.
4. Open Snipping Tool, choose Rectangular Snip, click New, draw a box around full drive map and all listings.
5, Save Snip, attach using paper clip in Reply Box.

Tell us what is on each partition, and explain what concerns you and why.

You said EFI was damaged so were given the workaround to install in Legacy BIOS mode. This confers no disadvantage and saves much frustration with install and repairs. If you want to learn more about the EFI here are some resources:

The 30-year-long Reign of BIOS is Over: Why UEFI W... - Input Output
Installing Windows to an EFI-Based Computer
Technical Note: UEFI BIOS vs. Legacy BIOS - YouTube
UEFI (Unified Extensible Firmware Interface) - Install Windows 7 with - Windows 7 Forums

Hi again, attached you will find the requested snapshot of the available HD's. In Disk C: I have the operating system, Disk G: is the partition I use for my files.
I have started to notice unusual behavior i.e. my computer stopped responding although I was not running any heavy duty tasks, on separate occasions chrome stopped responding and I can feel a general lag. The later described behavior was not present before, at all. I'm assuming thus far that it is preferable to run the stock EFI partition table rather than the MBR. Not a specialist or anything but I'd rather have it the way it was. Thank you very much for the help so far, I shouldnt take up your time. I used your resources for background reading and did some further research on my own. Im going to try to deal with this myself. Again thank you for your time.

As long as you've installing in Legacy Mode to an MBR disk, the BIOS will not affect your install performance. I just told you this so I don't know why you assume your problem is with EFI.

More likely it's a problem with the install and setup. How closely did you follow the steps to Clean Reinstall - Factory OEM Windows 7, particularly the way drivers are handled?

I would work through these Troubleshooting Steps for Windows 7.

yes, I have also observed that EasyBCD's user interface is not very user friendly. It deletes our entry at the press of a key or a click, and doesn't even ask us to confirm, doesn't even tell us the consequences of that deletion. And it doesn't have method to UNDO any action that we later realize was wrong.

I had also ended up erasing my multiboot setup by press of a key. luckily, I explored easybcd further and could come to know what horror I have done, and I immediately manually entered that setup again, so I could boot, otherwise both my w7 setup would have become unbootable. Thanks God for big mercies.

I am not very careful and anxious while using easybcd. Sad that no other such good program exists.

Thanks.