4

I have a problem booting Windows 10 from grub. When I tried to do it I got this message:

/EndEntire
file path: /ACPI....../File(bootmgfw.efi)/EndEntire
error: cannot load image.

I then Googled and found this solved problem, which tells you to edit the grub.cfg file.

Edit /boot/grub/grub.cfg

Find

### BEGIN /etc/grub.d/30_os-prober ###

menuentry 'Windows 10 (loader) (on /dev/sdXX)'

After

chainloader +1

Write

ntldr /bootmgr

When I tried to apply that I got this error, in addition to the original one

error: can't find command `ntldr'.

This might be due to my grub.cfg file not looking like the one in the link but I don't know how to adapt the solution.

As the grub.cfg file is quite lengthy, this is the section mentioned in the other solution.

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Boot Manager (on /dev/sda2)' --class windows --class     os $menuentry_id_option 'osprober-efi-4CBE-1366' {
    insmod part_gpt
    insmod fat
    set root='hd0,gpt2'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-    efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  4CBE-1366
    else
      search --no-floppy --fs-uuid --set=root 4CBE-1366
    fi
        chainloader /EFI/Microsoft/Boot/bootmgfw.efi
    }
set timeout_style=menu
if [ "${timeout}" = 0 ]; then
  set timeout=10
fi
### END /etc/grub.d/30_os-prober ###

The full file can be found here if needed.

I've tried to update grub, no difference.

Edit:

Output from terminal

kajsa@Yoga ~ $ sudo update-grub
[sudo] password for kajsa: 
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.4.0-53-generic
Found initrd image: /boot/initrd.img-4.4.0-53-generic
Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for EFI firmware configuration
done

Any suggestions?

Kajsa
  • 141

1 Answers1

0

bootmgfw.efi appears to be part of the Windows boot config. If that is affected, the easy solution is to try the Startup Repair Utility. It's an option that appears after booting into Windows recovery using a bootable USB

The hard way is to rebuild the boot config using bootrec (guide). To access this utility:

  1. Boot into Windows recovery using a bootable USB
  2. Select the command prompt option
  3. Change directory into the Windows installation directory
  4. Run the bootrec commands in the linked guide.

However, if the real issue is from the error: cannot load image, it's from hiberfil.sys. That file needs to be deleted for boot to happen. Here's a guide

Looi
  • 26