However, I observed that my original Windows Boot Manager has a slightly different file path:
Boot0008* Windows Boot Manager HD(2,96800,32000,f1fdeac1-d057-4f3b-9f66-6f74eb3b469b)File(\EFI\Microsoft\Boot\bootmgfw.efi)
compared to Grub:
/ACPI(a0341d0,0)/UnknownMessaging(12)/HD(2,fa800,96000,372001a2fb07f544,a3,ff)/File(\EFI\Microsoft\Boot)/File(bootmgfw.efi).
However, the same menu entry works if I disable Secure Boot. It looks like this slightly different file path only leads to an error when UEFI tries to check the signature....
On my Samsung Series 9 device I do have the exactly same behavior.
I documented this in my blog post: falstaff. agner.ch/ 2012/12/ 18/ubuntu- 12-10-and- windows- 8-with- secure- boot-mode/
http://
However, I observed that my original Windows Boot Manager has a slightly different file path:
Boot0008* Windows Boot Manager HD(2,96800, 32000,f1fdeac1- d057-4f3b- 9f66-6f74eb3b46 9b)File( \EFI\Microsoft\ Boot\bootmgfw. efi)
compared to Grub: 0)/UnknownMessa ging(12) /HD(2,fa800, 96000,372001a2f b07f544, a3,ff)/ File(\EFI\ Microsoft\ Boot)/File( bootmgfw. efi).
/ACPI(a0341d0,
However, the same menu entry works if I disable Secure Boot. It looks like this slightly different file path only leads to an error when UEFI tries to check the signature....