[Bug 1956385] Re: ubiquity incorrectly detects bitlocker as enabled

[Dan Bungert]

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
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1956385

Title:
  ubiquity incorrectly detects bitlocker as enabled

Status in ubiquity package in Ubuntu:
  New

Bug description:
  I followed the instructions to check and see if bitlocker was enabled
  and it is in fact not enabled yet I still cannot install Ubuntu
  alongside Windows 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity 21.10.10
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  4 20:35:02 2022
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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