DiskCryptor is an open source encryption solution that offers encryption of all disk partitions, including system partitions. DiskCryptor's openness is in sharp contrast with other encryption software today, where most of the software with comparable functionality is completely proprietary, making it unacceptable to use for protection of confidential data.
Originally DiskCryptor was developed as a replacement for DriveCrypt Plus Pack and PGP WDE by ntldr, however as he stopped since 2014 we decided to continue the development on our own here.
We have updated DiskCryptor for use with Windows 10 and 11, adding a UEFI/GPT bootloader as well as other minor fixes to improve compatibility. We aim at further improving and maintaining compatibility with modern Windows versions.
- Support of AES, Twofish, Serpent encryption algorithms, including their combinations.
- Transparent encryption of disk partitions.
- Full support for dynamic disks.
- Support for disk devices with large sector size (important for hardware RAID operation).
- High performance, comparable to efficiency of a non-encrypted system.
- Support for hardware AES acceleration:
- AES New Instructions set on recent Intel and AMD CPUs;
- PadLock extensions on VIA processors.
- Support for the SSD TRIM extension.
- Support for hardware AES acceleration:
- Broad choice in configuration of booting an encrypted OS. Support for various multi-boot options.
- Full support for external storage devices.
- Option to create encrypted CD and DVD disks.
- Full support for encryption of external USB storage devices.
- Automatic mounting of disk partitions and external storage devices.
- Support for hot keys and optional command-line interface (CLI).
- Open license GNU GPLv3.
Yes. DiskCryptor is still actively maintained. However, it is a very mature piece of software, and there is little ongoing development required. As a result, releases are infrequent.
No. There will not be a FINAL release. The BETA label is intentional and serves as an explicit warning. DiskCryptor is a free, low-level disk encryption tool; even minor misuse, misconfiguration, or unexpected interactions can result in irreversible data loss.
The BETA designation serves as a clear warning and a legal and practical boundary: you are expected to understand what the software does and to assume full responsibility for its use. DiskCryptor is used entirely at your own risk.
I have personally used DiskCryptor for decades without major issues; however, I understand the implications of each action and always maintain reliable backups.
I installed a Windows update and the DiskCryptor bootloader no longer starts. Windows boots directly into recovery. What should I do?
This typically occurs when the EFI firmware is configured to boot \EFI\Microsoft\Boot\bootmgfw.efi instead of \EFI\DCS\DcsBoot.efi.
In this configuration, DiskCryptor replaces bootmgfw.efi with its own bootloader. A Windows update may restore the original Microsoft bootloader, which breaks the DiskCryptor boot chain. To resolve this, you must replace the file again.
Recovery procedure (from Windows Recovery Environment):
- Boot into WinRE and open a Command Prompt.
- Mount the EFI system partition:
mountvol S: /S - Create a new file:
S:\EFI\DCS\fix_dcs.cmdadd the following contents to the file:
cd \EFI\Microsoft\Boot
del bootmgfw_ms.vc.old
ren bootmgfw_ms.vc bootmgfw_ms.vc.old
ren bootmgfw.efi bootmgfw_ms.vc
copy ..\..\DCS\DcsBoot.efi bootmgfw.efi
- Execute the script to restore the DiskCryptor bootloader. Alternatively, you may run the commands manually one by one.
- Reboot.
This issue may reoccur after future Windows updates. Keeping this script available allows for quick recovery. For a permanent solution, review and correct your EFI boot order so that the system boots \EFI\DCS\DcsBoot.efi directly.
DiskCryptor does not support Secure Boot out of the box. The DiskCryptor bootloader is not signed, and therefore it will not be accepted by a standard Secure Boot configuration. If Secure Boot is required, you must enroll your own private key into the Secure Boot database (DB) and sign the DiskCryptor bootloader files yourself.