I have a laptop running Windows 7 Ultimate. I have encrypted my drives using BitLocker. Now I have also installed Lubuntu along with Windows. But my encrypted drives are not visible in Linux. How can I fix this?
8Hi Zeal, is your question answered sufficiently? If so, please pick an answer to close the question.– Brett DikemanJan 13, 2012 at 19:49
There's a pretty detailed answer at askubuntu.com/a/617989/25639 too.– unhammerApr 24, 2018 at 7:40
You can access the BitLocker partition under Linux using Dislocker, an open-source driver that is using FUSE (or not).
Note: You need the file on a USB key (the one with the
.bek extension) or the recovery password.
1But i don't have any USB key or recovery password. I did not setup the encryption, it came encrypted from factory settings. Where do i find the key?– Youda008Sep 20, 2018 at 16:40
4@Youda008 if it still boots, run
manage-bde -protectors -get c:to retrieve the key - at your first available opportunity. Otherwise if it decides to stop booting one day (e.g. BIOS change), it will be unrecoverable. Dec 11, 2019 at 8:50
Thanks to Aorimn, his solution worked for me. I'm fairly unexperienced with Unix, so it cost a few hours to figure it out. I thought I would describe the steps I took while my backup is running :)
My problem was that I could not boot Windows, and I needed a way to access my files on a Bitlocked partition. In order to do this, you need a bitlocker recovery password (8 groups of digits) and the ability to boot your system from USB.
- Download and install
LiLion an other Windows machine (Linux Live USB Creator)
LiLiand have it download a lightweight
ubuntuimage. I chose
- Install the image to your USB stick.
- Boot the problematic machine with the USB stick
- When you see the ubuntu boot screen, press a key.
F6, set the following options:
- Make a folder
- Download and extract dislocker
sudo apt-get install libfuse-dev libmbedtls-dev
- change directory to the
sudo make install
- change directory to
sudo fdisk -l
- identify the partition which is bitlocked. Mine was
sudo dislocker -r -V /dev/sda1 -p315442-000000-000000-000000-000000-000000-000000-000000 -- /media/windows(replace your own bitlocker key and source partition)
- change dir to
sudo -iif you can't access it)
mount -o loop dislocker-file /media/mount
- You should now see your files in a mounted drive of the file manager.
Backups are fairly slow, but it might save some trouble if you do end up reinstalling windows. Good luck!
6From the above steps I wasn't clear how
dislockeris functioning, so here is the info, from the source "With FUSE, you have to give the program a mount point. Once keys are decrypted, a file named
dislocker-fileappears into this provided mount point. This file is a virtual NTFS partition, so you can mount it as any NTFS partition and then read from it or write to it."– xptFeb 20, 2014 at 14:59
4dislocker is now (as of Ubuntu 18.04) available in Ubuntu's repositories, so you can install it by running
sudo apt install dislockerinstead of building from source.– DominikMay 14, 2018 at 14:15
Is there a solution other than using dislocker? The problem is that dislocker requires compiling and (like virtually every other time I try) compiling fails.– TensighAug 2, 2018 at 8:04
CryptSetup has added experimental support for BitLocker as of version 2.3.0 (February 2020), which is available in Ubuntu's repos for 20.10 Groovy onwards, although support will likely improve in later versions.
To open a BitLocker device with a password, use:
sudo cryptsetup open --type=bitlk <device> <name>
sudo cryptsetup bitlkOpen <device> <name>
To open the device with a key file, use:
sudo cryptsetup open --type=bitlk --key-file=/etc/cryptsetup-keys.d/<name>.key <device> <name>
To open the device at boot time, add the following to
<name> PARTUUID=<part_uuid> /etc/cryptsetup-keys.d/<name>.key bitlk
If a keyfile is not specified, systemd-cryptsetup(8) will automatically try to load it from
So you may replace the path to the key file with
Possible parameter values:
- device - /dev/sda1
- name - windows
- part_uuid - aaaaaaaa-1111-bbbb-2222-cccccccccccc (find
sudo blkid | grep BitLocker)
Now you can mount the device with the following command:
sudo mount /dev/mapper/windows /path/to/mount/point
When setting up BitLocker on a device choose the option that encrypts the whole device (requires more time). The other option uses Encrypt-On-Write conversion model that makes sure that any new disk writes are encrypted as soon as you turn on BitLocker (data that existed on the device before encryption began can still be read and written without encryption) and is not supported by Cryptsetup.
You will get the following error when you try to open the device with Encrypt-On-Write conversion model:
BITLK devices with type 'encrypt-on-write' cannot be activated.
Cryptsetup 2.3.0 Release Notes
BitLocker configuration: known issues
I just worked out a way to update Kali Linux and install
Using Kali Linux 1.0.9a i386 bootable DVD
Edit "/etc/apt/sources.list" and add:
deb http://us.archive.ubuntu.com/ubuntu trusty main universe
Install programs using Terminal:
apt-get update" apt-get install git libfuse-dev libpolarssl-dev # Continue through update text, allow services to restart if needed git clone git://github.com/Aorimn/dislocker.git cd /dislocker/src make make install
Find drive Bitlocker volume:
Make folders in /mnt:
dislocker -v -V /dev/<volume name> -p<Bitlocker key> -- /mnt/tmp
Check if file exists to confirm proper Bitlocker key:
dislocker-file if correct.
mount -o loop,ro /mnt/tmp/dislocker-file /mnt/dis
/mnt/dis for access to files.
dislockerdoesn't work in Kali Linux 2.0. When I try the
makecommand, following output appears: > dislocker-fuse.c:35:19: fatal error: fuse.h: No such file or directory And manually handling (
apt-get install libfuse-dev) > The following packages have unmet dependencies:
libfuse-dev: > Depends:
libselinux-dev– cagcakAug 18, 2015 at 14:24
1Great step-by-step instructions. Only thanks to this I learned that the dislocker command is not mounting itself (like
sshfsor other things). May 11, 2018 at 7:37
BitLocker is a proprietary, closed-source drive encryption system only supported by Windows. You'll have to remove BitLocker encryption if you want to access your Windows partitions from Linux.
See What is the difference between disabling BitLocker Drive Encryption and decrypting the volume? for instructions on doing so. It would be advisable to have a backup of your data completed first.
Once the drive is decrypted, you can use TrueCrypt instead; reading a System Encryption volume under Linux isn't supported by default, but someone has figured out a work-around. See How to use TrueCrypt®-encrypted Windows system drives on Linux.
At the very least, review the TrueCrypt documentation and more specifically, the list of supported OSes.
Yet another option is PGP Whole Disk Encryption. See PGP Whole Disk Encryption for Dual Boot Linux and Windows XP.
Perhaps update for TrueCrypt. Steve Gibson has a page for it. May 4, 2015 at 11:15
6@BrettDikeman You may want to adjust or delete your answer as it does not apply (or is no longer true). See superuser.com/a/421314/118989. Jun 20, 2017 at 7:18
@TomaszGandor what is the update exactly? Is bitlocker not closed-source anymore? How does Dislocker actually get 'around' it? Jul 5, 2018 at 20:48
Please note that
libpolarssl-dev can't be used, it has been supersede with
libmbedtls-dev so use this instead:
sudo apt-get install libmbedtls-dev
Note: by the way, it was a success using live boot. I am able to read and write. Just follow above steps.
Besides the other answers, there is a package
libbde-utils, providing the command
# bdemount -p Password /dev/sda1 # bdemount -r RecoveryPassword /dev/sda1
see the Ubuntu manual
1Please provide more details otherwise your answer is in danger of getting deleted. Feb 7 at 3:05
I had a similar problem, and just want to share my experience and what I learned in case it helps someone else.
I had a Bitlocker encrypted drive from Windows 10 Pro, 20H2 that was using Encrypt-On-Write. I tried everything from all the useful answers here.
TLDR; as of April 2023, only real Bitlocker can decrypt a drive that uses Encrypt-On-Write.
For reference, my Linux system is Mint 20.3.
I tried dislocker, building it from the latest release tag, and it couldn't decrypt with the recovery key/password.
Then I tried Cryptsetup, building from the latest source as well, it didn't work either. Thanks @denis-savran for your note about Encrypt-On-Write, that got me going in the right direction.
I tried libbde-utils, but just from the Mint 20.3 distro package.
I tried @SrjCoder's suggestion of using a VM. But with VirtualBox on the Linux host, I was not able to see the encrypted drive in the guest Windows system. The unmounted block device that had the encrypted drive was not visible in the VM. I didn't try VMware, and I'm not a VirtualBox expert, so maybe I missed something there.
Finally I installed Windows 10 Pro on a separate machine, and connected the encrypted drive, Windows recognized it as a Bitlocker drive, and I was able to unlock it with the recovery key, and the valuable data was saved! The end.
If you're wondering why I didn't just boot the encrypted drive, it is in a bad state and cannot boot. It blue-screened trying to go back to a restore point. Luckily the data partition was still intact.
If Anyone here not understanding this I have one LongCut Techinique.
- Download Vmware (can also install VirtualBox which is free) and Windows 10/11 ISO (can also install Windows 7/8)
- Then in VMware create a new Virtual Machine with the ISO.
- After Windows installation please connect your drive to this VM via VM tab in there.
- Tada! Enter your BitLocker password and access the files. This Windows can also be used for testing any other things on Windows.
What do you mean by the “LongCut Techinique?” Feb 7 at 1:47
by "LongCut", I think @SrjCoder means the opposite of a "short-cut", since this method takes a lot longer than installing dislocker or cryptsetup in Linux. Apr 24 at 4:51