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.
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.