Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1700397

Summary:	Windows loader halts requesting bitlocker recovery code following update to grub on uefi dual boot laptop
Product:	[Fedora] Fedora	Reporter:	Bill <thetaeridanus>
Component:	grub2	Assignee:	Peter Jones <pjones>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	30	CC:	bugzilla, fmartine, lkundrak, pjones, rik.theys
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-23 03:31:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bill 2019-04-16 13:00:43 UTC

Description of problem:


I have a uefi dual boot setup of the fedora 30 beta and Windows 10 on a Dell Latitude laptop. The Windows 10 install is bitlocker encrypted. Every time after grub gets updated via dnf, any subsequent first boot of Windows from the grub boot menu causes the Windows loader to halt, requesting the bitlocker recovery code. This is quite annoying as it is a forty digit number. This occurred on the initial install of f29 on this laptop about three months ago and also on the updgrade from f29 > f30 pre release. The problem has recurred when ever an upgrade to grub has been picked up via dnf update. Not sure if this is working as designed, or a bug but it is quite annoying. Luckily I had recorded the bit locker recovery code before the initial dual boot install.

Would appreciate knowing if there is any way to fix this. 

PS, I believe Windows stores the bitlocker keys in the laptop TPM so maybe the upgrade of grub is disturbing that somehow. There is no problem on a kernel update.








Additional info:

Comment 1 Javier Martinez Canillas 2019-05-22 19:34:53 UTC

(In reply to Bill from comment #0)
> Description of problem:
> 
> 
> I have a uefi dual boot setup of the fedora 30 beta and Windows 10 on a Dell
> Latitude laptop. The Windows 10 install is bitlocker encrypted. Every time
> after grub gets updated via dnf, any subsequent first boot of Windows from
> the grub boot menu causes the Windows loader to halt, requesting the
> bitlocker recovery code. This is quite annoying as it is a forty digit
> number. This occurred on the initial install of f29 on this laptop about
> three months ago and also on the updgrade from f29 > f30 pre release. The
> problem has recurred when ever an upgrade to grub has been picked up via dnf
> update. Not sure if this is working as designed, or a bug but it is quite
> annoying. Luckily I had recorded the bit locker recovery code before the
> initial dual boot install.
> 
> Would appreciate knowing if there is any way to fix this. 
> 
> PS, I believe Windows stores the bitlocker keys in the laptop TPM so maybe
> the upgrade of grub is disturbing that somehow. There is no problem on a
> kernel update.

If you are using BitLoacker then you shouldn't chainload Windows from GRUB since the TPM measurements will change. If you want to use Windows with BitLocker then you need to add a new Boot Entry for Windows and use your UEFI firmware to choose which OS to boot.

Comment 2 Bill 2019-05-23 03:31:45 UTC

Thanks for the explanation. May as well close this.

Comment 3 Chris Murphy 2022-02-02 19:27:51 UTC

See bug 2049849