the sector you posted has the same magic bytes as one with bitlocker in place (and not the NTFS magic bytes), so I can understand why lsblk would flag it as bitlocker.
However I notice in my win10 vm that bitlocker has 3 states - On, Suspended, Off, and the On and Suspended states have the same magic bytes. Would you boot the Windows side and report what state Windows thinks the partition is in? I wonder if it's actually in a suspended state. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956385 Title: ubiquity incorrectly detects bitlocker as enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1956385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
