Comment 11 for bug 2061551

Revision history for this message
Chris Parker (cparke) wrote (last edit ):

I don't buy that "buggy firmware" is an issue. In my case, I have this issue now on a Dell XPS 13 9310 2-in-1 laptop after booting Ubuntu 24.04 Live. I have secure booted many other Linux LIVE distros from USB on this computer and never had a BitLocker recovery key issue afterwards! If two name-brand computers are exhibiting the same issue, and only after loading Ubuntu 24.04 Live, I think the OP has a very correct assessment.

I think it is absolutely expected by end users like myself that booting a Live OS will not change anything on the PC simply by being booted, such as hard drives, UEFI, and other BIOS settings. Very disappointed!

Also, I am now kind of stuck, as I don't have the BitLocker Recovery Key. Until this is resolved, I can only boot via Live Linux distros on this machine and can't access my Windows files. Is there any suggested workaround under Linux that can undo the PCR changes or corruption that this Ubuntu bug has caused? I am hoping it may be possible to reverse the changes enough to satisfy the TPM that nothing has actually changed, so it might then release the BitLocker Recovery Key and I could boot Windows again. How do I even check for the condition that this bug causes or read the PCR registers directly under Linux?