[Bug 2107771] [NEW] Unable to unlock BitLocker drives on new Windows versions with keys backed up to Microsoft account

Zhang Zhuyue 2107771 at bugs.launchpad.net
Mon Apr 21 11:24:15 UTC 2025


Public bug reported:

This is related to a bug introduced by Microsoft adding a hint of the
key containing the Microsoft account to which the user backed up the
key, causing BitLocker partitions with keys backed up in newer Windows
versions unable to be unlocked, which was fixed in cryptsetup 2.7.3 .

Links to the original bug and fix:

https://gitlab.com/cryptsetup/cryptsetup/-/issues/886

https://gitlab.com/cryptsetup/cryptsetup/-/merge_requests/652

As Ubuntu 24.04's cryptsetup is based on 2.7.0 (and 24.10's based on
2.7.2), I can't unlock my BitLocker drive on my dual boot PC, which is
somewhat inconvenient. I think that it would be good if the fix (only
involving a little change, 7 lines of code) is backported in some future
updates, but I'm new here and don't know if this is legitimate, so
forgive me if this sounds unreasonable.

** Affects: cryptsetup (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
https://bugs.launchpad.net/bugs/2107771

Title:
  Unable to unlock BitLocker drives on new Windows versions with keys
  backed up to Microsoft account

Status in cryptsetup package in Ubuntu:
  New

Bug description:
  This is related to a bug introduced by Microsoft adding a hint of the
  key containing the Microsoft account to which the user backed up the
  key, causing BitLocker partitions with keys backed up in newer Windows
  versions unable to be unlocked, which was fixed in cryptsetup 2.7.3 .

  Links to the original bug and fix:

  https://gitlab.com/cryptsetup/cryptsetup/-/issues/886

  https://gitlab.com/cryptsetup/cryptsetup/-/merge_requests/652

  As Ubuntu 24.04's cryptsetup is based on 2.7.0 (and 24.10's based on
  2.7.2), I can't unlock my BitLocker drive on my dual boot PC, which is
  somewhat inconvenient. I think that it would be good if the fix (only
  involving a little change, 7 lines of code) is backported in some
  future updates, but I'm new here and don't know if this is legitimate,
  so forgive me if this sounds unreasonable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2107771/+subscriptions




More information about the foundations-bugs mailing list