GNU GRUB - Bugs: bug #61622, Grub 2.06 is incompatible with W10...
You are not allowed to post comments on this tracker with your current authentication level.
bug #61622: Grub 2.06 is incompatible with W10 secure boot and bitlocker : breaks working installation
Submitter: | Eric V <ericv3> | ||
Submitted: | Sun 05 Dec 2021 10:50:17 AM UTC | ||
Category: | Booting | Severity: | Major |
Priority: | 5 - Normal | Item Group: | Software Error |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | Eric V |
Open/Closed: | Open | Release: | Git master |
Release: | Reproducibility: | Every Time | |
Planned Release: | None |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
Powered by Savane 3.13-f8d8.
Corresponding source code
With grub 2.04 from Debian bulleyes installer, with some caveat it was possible to install a dual boot system with a W10 system with secure boot and bitlocker.
The process was documented on various Web pages:
1) suspending bitlocker (not disabling as i would require
disk decryption) before the install on W10,
2) updating grub related packages only,
3) and reenabling bitlocker on W10 after grub install,
This is typically what Windows10 itself does when updating some efi/bios/drivers components.
It did the same with 2.06, and I tough it worked or at least I had the impression it did up to reenabling Bilocker from W10 and rebooting Linux. But today, without any other grub/efi/ related upgrade, trying to boot Windows it asks for the bitlocker key saying some software/hardware components changed.
I have no mean to disable bitlocker permanently as a GPO on Windows will reenable it.
For me this is a major regression that silently breaks existing working installation with 2.04.