No grub2 after boot-repair windows 8 hp envy dv6

**oldfred** · April 3rd, 2013

There was just another HP user with the locked efi partition. That is an unusual issue which do do not know how it occurs nor a good fix. But Boot-Repair did not report the locked efi issue on your system.
Just as a test can you edit a file name in your efi? As that seems to be the issue Boot-Repair has.

grub-efi fails to install with Input/output error - locked efi
https://bugs.launchpad.net/ubuntu/+s...2/+bug/1090829

If you cannot edit a filename, backup entire efi partition delete efi partition with gparted, create new efi partition in same place with gparted, set boot flag to make efi and restore files.

**jalexstark** · April 4th, 2013

Yann provided an updated version to the ppa repo. This fixed the menu problem. (Awesome!)
(http://paste.ubuntu.com/5677086/)

Now I cannot boot to windows, since the previous problem persists for booting windows via grub. Each grub menu item gives an error, such as
file path: ... /File(\EFI\Microsoft\Boot)/File(bkpbootmgfw.efi) ...
error: cannot load image.

I think that I am nearly there!

**jalexstark** · April 4th, 2013

...but I can get to Win8 via F9 on start-up; choose EFI file as boot device; choose EFI/Microsoft/Boot/bkpbootmgfw.efi.

**oldfred** · April 4th, 2013

This menu entry in grub2's menu should be using the same file in the efi partition?

menuentry "Windows UEFI bkpbootmgfw.efi" {
search --fs-uuid --no-floppy --set=root C616-56DA
chainloader (${root})/EFI/Microsoft/Boot/bkpbootmgfw.efi
}

**jalexstark** · April 4th, 2013

Yes. Weird.

Full error:

Code:

/EndEntire
file path: /ACPI(a0341d0,0)/PCI(0,11)/ATAPI(0,0,0)/HD(2,c8800,82000,8342c12b8be64e4c,9e,b0)/File(\EFI\Microsoft\Boot)/File(bkpbootmgfw.efi)/EndEntire
error: cannot load image.

Error similar for "Windows Boot UEFI loader":

Code:

/EndEntire
file path: /ACPI(a0341d0,0)/PCI(0,11)/ATAPI(0,0,0)/HD(2,c8800,82000,8342c12b8be64e4c,9e,b0)/File(\EFI\Boot)/File(bkpbootx64.efi)/EndEntire
error: cannot load image.

**oldfred** · April 4th, 2013

Some only boot with secure boot on, others boot with it on or off. Have you tried both?

**jalexstark** · April 4th, 2013

Disabling secure boot seems to have fixed it, as a workaround. Somewhere in between osprober, grub, chainloader and secure booting it goes wrong.

https://bugs.launchpad.net/ubuntu/+s...2/+bug/1091464

Thanks for your essential and timely assistance.

**oldfred** · April 4th, 2013

Glad you have it working.

Must be something in the secure boot or UEFI modifications that make it more difficult for some computers that prevents secure boot.

**YannBuntu** · April 5th, 2013

I agree, I also have the feeling that there are several types of SecureBoot, and that Ubuntu (Linux in general) is still not compatible with all of them.