It does on Fedora.
The new problem though is computers with TPM 2 and Windows 10/11
preinstalled are frequently (and increasingly) coming with BitLocker
enabled. And the key is predicated on the boot chain being TPM
verifiable. By booting shim+grub first, it changes the measurements, and
Windows c
Chainloading Windows UEFI works fine with the current shim+GRUB I
believe.
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091464
Fedora has fixed this problem differently than SUSE has, so it might be
worth Ubuntu devs taking a look at what they did and seeing if it's
applicable.
This is the complete git log for GRUB2 in Fedora:
http://pkgs.fedoraproject.org/cgit/rpms/grub2.git/log/
I think this is the applicable commit:
h
Adding myself to this bug. Not being able to do a clean installation of
Ubuntu alongside Windows (because then the Windows boot will break) is
against the Ubuntu philosophy of accessibility itself, and objectively
it is a complete regression in functionality.
--
You received this bug notification
Hello,
GRUB binary doesn't have the cryptos to do the signs verification unlike
shim, so the chainload process fails under Secure Boot.
As Valmar said, for the OpenSUSE version of GRUB2, Michael Chang came
out with a patch on 2012 that make GRUB rely on shim verification to
chainload other binari
The Asus still boots Windows with secure boot enabled with the default
bootloader (/EFI/Boot/bootx64.eri) replaced with a copy of shimx64.efi
(and grubx64.efi present).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Today I saw a fresh install of the original Ubuntu 16.04 successfully
boot Windows 10 on an Asus X200CA, 64 bit (Windows patched to date) with
secure boot enabled. This machine had previously been running 14.04,
and could not boot Windows with secure boot enabled. The other
difference is that the
No, the problem still exists on a Toshiba Satellite S855 UEFI firmware
6.60, with Ubuntu 16.04 fully updated and trying to boot Windows 10 with
secure boot enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
I could not reproduce on a new machine this bug (though this
installation guide http://ubuntuforums.org/showthread.php?t=2317843
suggested turning off Secure Boot on Dell XPS 15 9550)
Can it be that latest Ubuntu 16.04 has this problem fixed? Or maybe the
key-chain is fixed for some hardware and s
** Summary changed:
- Unable to chainload Windows 8 with Secure Boot enabled
+ Unable to chainload Windows 8 and 10 with Secure Boot enabled
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091464
Titl
10 matches
Mail list logo
