Home
» LINUX
»
How to Access a Windows BitLocker Partition in Linux
How to Access a Windows BitLocker Partition in Linux
Short answer: use Dislocker to unlock the BitLocker volume, then mount the virtual NTFS file it exposes. Linux’s ordinary NTFS support does not decrypt BitLocker on its own. The commands below use read-only mode at both layers so you can copy files without writing to the Windows volume.
Before you begin
You need administrator access on Linux, the correct BitLocker partition, and a protector credential for that volume. A Windows sign-in password or PIN is not necessarily the BitLocker password. If the volume uses a 48-digit recovery password, Dislocker can prompt for it instead. Microsoft explains where recovery keys may be backed up in its recovery-key guide; for a work or school device, contact its administrator.
Dislocker’s upstream documentation describes support for BitLocker formats from Windows Vista through Windows 10 and BitLocker To Go. That documentation does not promise compatibility with every newer Windows configuration or protector, so results can depend on the volume and Dislocker build. Review the project notes if your setup differs.
Install Dislocker
Use your distribution’s trusted package source. On Ubuntu or Debian, the package is available in the distribution archives; package availability can depend on release and enabled repositories:
sudo apt update
sudo apt install dislocker
Fedora’s upstream installation notes list these packages:
Install Dislocker from your distribution’s package source; the package manager and output vary by system.
Unlock and mount the partition
1. Identify the BitLocker partition
List the available block devices and compare their sizes with the Windows partition. Replace the example device below with the partition you identify; it may look like /dev/nvme0n1p3 or /dev/sdc1.
lsblk -o NAME,SIZE,TYPE
lsblk may not label a BitLocker volume clearly. Check the parent disk and partition size carefully. Do not choose a small EFI, recovery, or Linux partition based only on its position in the list.
A sample block-device tree; device names and sizes differ from computer to computer.
2. Create two mount points
Dislocker needs one directory for its FUSE mount, and Linux needs another directory for the NTFS view:
sudo mkdir -p /mnt/bitlocker /mnt/windows
The first path will contain Dislocker’s virtual file, dislocker-file. The second path will show the decrypted filesystem after you mount that file.
Create separate directories for Dislocker and the mounted NTFS filesystem.
3. Unlock the volume with Dislocker
Run Dislocker against the partition, adding -r to prevent writes to the underlying BitLocker volume. The -u option asks for a BitLocker user-password protector; it is not automatically your Windows account password.
Enter the requested password at the prompt. Do not append it to the command, where it could be saved in shell history or exposed in process details. For a 48-digit recovery password, use -p in place of -u; Dislocker will prompt for the recovery password:
In both commands, replace /dev/nvme0n1p3 with your actual partition. After a successful unlock, Dislocker exposes /mnt/bitlocker/dislocker-file. It is a virtual NTFS volume linked to the encrypted partition, not a separate copy.
Dislocker prompts for a protector credential without displaying the entered secret.
4. Mount the NTFS view read-only
Mount Dislocker’s virtual file with loopback and read-only options:
sudo mount -o loop,ro /mnt/bitlocker/dislocker-file /mnt/windows
The additional ro option keeps this filesystem view read-only. Keep the Dislocker mount active while you use /mnt/windows.
Mount the virtual NTFS file with both loopback and read-only options.
5. Browse or copy files
Open /mnt/windows in your file manager or use it from the terminal. Copy anything you need to a different writable disk or partition. The read-only setup is intentional: Dislocker can pass writes through to the original encrypted volume when not run read-only.
The mounted path works like a browsable directory; the actual files depend on your Windows volume.
Unmount safely
Close files and applications using the mounted volume, then unmount the NTFS view first and Dislocker second:
Do not shut down Linux while either mount is active. If an unmount reports “target is busy,” close the file-manager window and any terminal or application using the volume, then retry. Avoid a force unmount while files are open.
Unmount the NTFS view before releasing Dislocker’s mount.After the Windows view is unmounted, unmount the Dislocker directory.
If the volume will not mount
Credential rejected: confirm whether the protector is a BitLocker user password or a recovery password. A Windows sign-in PIN is not a substitute. Check Microsoft’s recovery-key guidance or ask the device administrator.
Wrong device or missing file: verify the partition path with lsblk and check that the Dislocker command completed. The NTFS mount command needs the resulting dislocker-file.
Volume state warning: do not bypass Dislocker’s state check with its force/state option just to make the mount proceed. Return to Windows, back up important data, and check the correct drive with Microsoft’s CHKDSK guidance. Repair options can change the filesystem.