Known Issues & Limitations

Known Issues

• (There were no confirmed issues when this document was created.)

Limitations

• [Note: This limitation does not apply to users of Windows Vista and later versions of Windows.] On Windows XP/2003, VeraCrypt does not support encrypting an entire system drive that contains extended (logical) partitions. You can encrypt an entire system drive provided that it contains only primary partitions. Extended (logical) partitions must not be created on any system drive that is partially or fully encrypted (only primary partitions may be created on it).Note: If you need to encrypt an entire drive containing extended partitions, you can encrypt the system partition and, in addition, create partition-hosted VeraCrypt volumes within any non- system partitions on the drive. Alternatively, you may want to consider upgrading to Windows Vista or a later version of Windows.
• VeraCrypt currently does not support encrypting a system drive that has been converted to a dynamic disk.
• VeraCrypt volume passwords must consist only of printable ASCII characters. Other characters in passwords are not supported and may cause various problems (e.g., inability to mount a volume).
• To work around a Windows XP issue, the VeraCrypt boot loader is always automatically configured for the version of the operating system under which it is installed. When the version of the system changes (for example, the VeraCrypt boot loader is installed when Windows Vista is running but it is later used to boot Windows XP) you may encounter various known and unknown issues (for example, on some notebooks, Windows XP may fail to display the log-on screen). Note that this affects multi-boot configurations, VeraCrypt Rescue Disks, and decoy/hidden operating systems (therefore, if the hidden system is e.g. Windows XP, the decoy system should be Windows XP too).
• The ability to mount a partition that is within the key scope of system encryption without pre- boot authentication (for example, a partition located on the encrypted system drive of another operating system that is not running), which can be done e.g. by selecting System> Mount Without Pre-Boot Authentication, is limited to primary partitions (extended/logical partitions cannot be mounted this way).
• Due to a Windows 2000 issue, VeraCrypt does not support the Windows Mount Manager under Windows 2000. Therefore, some Windows 2000 built-in tools, such as Disk Defragmenter, do not work on VeraCrypt volumes. Furthermore, it is not possible to use the Mount Manager services under Windows 2000, e.g., assign a mount point to a VeraCrypt volume (i.e., attach a VeraCrypt volume to a folder).
• VeraCrypt does not support pre-boot authentication for operating systems installed within VHD files, except when booted using appropriate virtual-machine software such as Microsoft Virtual PC.
• The Windows Volume Shadow Copy Service is currently supported only for partitions within the key scope of system encryption (e.g. a system partition encrypted by VeraCrypt, or a non- system partition located on a system drive encrypted by VeraCrypt, mounted when the encrypted operating system is running). Note: For other types of volumes, the Volume Shadow Copy Service is not supported because the documentation for the necessary API is not available.
• Windows boot settings cannot be changed from within a hidden operating system if the system does not boot from the partition on which it is installed. This is due to the fact that, for security reasons, the boot partition is mounted as read-only when the hidden system is running. To be able to change the boot settings, please start the decoy operating system.
• Encrypted partitions cannot be resized except partitions on an entirely encrypted system drive that are resized while the encrypted operating system is running.
• When the system partition/drive is encrypted, the system cannot be upgraded (for example, from Windows XP to Windows Vista) or repaired from within the pre-boot environment (using a Windows setup CD/DVD or the Windows pre-boot component). In such cases, the system partition/drive must be decrypted first. Note: A running operating system can beupdated (security patches, service packs, etc.) without any problems even when the system partition/drive is encrypted.
• System encryption is supported only on drives that are connected locally via an ATA/SCSI interface (note that the term ATA also refers to SATA and eSATA).
• When system encryption is used (this also applies to hidden operating systems), VeraCrypt does not support multi-boot configuration changes (for example, changes to the number of operating systems and their locations). Specifically, the configuration must remain the same as it was when the VeraCrypt Volume Creation Wizard started to prepare the process of encryption of the system partition/drive (or creation of a hidden operating system).
  
  Note: The only exception is the multi-boot configuration where a running VeraCrypt-encrypted operating system is always located on drive #0, and it is the only operating system located on the drive (or there is one VeraCrypt-encrypted decoy and one VeraCrypt-encrypted hidden operating system and no other operating system on the drive), and the drive is connected or disconnected before the computer is turned on (for example, using the power switch on an external eSATA drive enclosure). There may be any additional operating systems (encrypted or unencrypted) installed on other drives connected to the computer (when drive #0 is disconnected, drive #1 becomes drive #0, etc.)
• When the notebook battery power is low, Windows may omit sending the appropriate messages to running applications when the computer is entering power saving mode. Therefore, VeraCrypt may fail to auto-dismount volumes in such cases.
• Preserving of any timestamp of any file (e.g. a container or keyfile) is not guaranteed to be reliably and securely performed (for example, due to filesystem journals, timestamps of file attributes, or the operating system failing to perform it for various documented and undocumented reasons). Note: When you write to a file-hosted hidden volume, the timestamp of the container may change. This can be plausibly explained as having been caused by changing the (outer) volume password. Also note that VeraCrypt never preserves timestamps of system favorite volumes (regardless of the settings).
• Special software (e.g., a low-level disk editor) that writes data to a disk drive in a way that circumvents drivers in the driver stack of the class ‘DiskDrive’ (GUID of the class is 4D36E967- E325-11CE-BFC1-08002BE10318) can write unencrypted data to a non-system drive hosting a mounted VeraCrypt volume (‘Partition0’) and to encrypted partitions/drives that are within the key scope of active system encryption (VeraCrypt does not encrypt such data written that way). Similarly, software that writes data to a disk drive circumventing drivers in the driver stack of the class ‘Storage Volume’ (GUID of the class is 71A27CDD-812A-11D0-BEC7-08002BE2092F) can write unencrypted data to VeraCrypt partition-hosted volumes (even if they are mounted).
• For security reasons, when a hidden operating system is running, VeraCrypt ensures that all local unencrypted filesystems and non-hidden VeraCrypt volumes are read-only. However, this does not apply to filesystems on CD/DVD-like media and on custom, atypical, or non-standard devices/media (for example, any devices/media whose class is other than the Windows device class ‘Storage Volume’ or that do not meet the requirements of this class (GUID of the class is 71A27CDD-812A-11D0-BEC7-08002BE2092F)).
• Device-hosted VeraCrypt volumes located on floppy disks are not supported. Note: You can still create file-hosted VeraCrypt volumes on floppy disks.
• Windows Server editions don't allow the use of mounted VeraCrypt volumes as a path for server backup. This can solved by activating sharing on the VeraCrypt volume through Explorer interface (of course, you have to put the correct permission to avoid unauthorized access) and then choosing the option "Remote shared folder" (it is not remote of course but Windows needs a network path). Their you can type the path of the shared drive (for example \\ServerName\sharename) and the backup will be configured correctly.
• Due to Microsoft design flaws in NTFS sparse files handling, you may encounter system errors when writing data to large Dynamic volumes (more than few hundreds GB). To avoid this, the recommended size for a Dynamic volume container file for maximum compatibility is 300 GB. The following link gives more details concerning this limitation: http://www.flexhex.com/docs/articles/sparse-files.phtml#msdn
• Further limitations are listed in the section Security Model.

Known Issues & Limitations

Known Issues

• (There were no confirmed issues when this document was created.)

Limitations

• [Note: This limitation does not apply to users of Windows Vista and later versions of Windows.] On Windows XP/2003, VeraCrypt does not support encrypting an entire system drive that contains extended (logical) partitions. You can encrypt an entire system drive provided that it contains only primary partitions. Extended (logical) partitions must not be created on any system drive that is partially or fully encrypted (only primary partitions may be created on it).Note: If you need to encrypt an entire drive containing extended partitions, you can encrypt the system partition and, in addition, create partition-hosted VeraCrypt volumes within any non- system partitions on the drive. Alternatively, you may want to consider upgrading to Windows Vista or a later version of Windows.
• VeraCrypt currently does not support encrypting a system drive that has been converted to a dynamic disk.
• VeraCrypt volume passwords must consist only of printable ASCII characters. Other characters in passwords are not supported and may cause various problems (e.g., inability to mount a volume).
• To work around a Windows XP issue, the VeraCrypt boot loader is always automatically configured for the version of the operating system under which it is installed. When the version of the system changes (for example, the VeraCrypt boot loader is installed when Windows Vista is running but it is later used to boot Windows XP) you may encounter various known and unknown issues (for example, on some notebooks, Windows XP may fail to display the log-on screen). Note that this affects multi-boot configurations, VeraCrypt Rescue Disks, and decoy/hidden operating systems (therefore, if the hidden system is e.g. Windows XP, the decoy system should be Windows XP too).
• The ability to mount a partition that is within the key scope of system encryption without pre- boot authentication (for example, a partition located on the encrypted system drive of another operating system that is not running), which can be done e.g. by selecting System> Mount Without Pre-Boot Authentication, is limited to primary partitions (extended/logical partitions cannot be mounted this way).
• Due to a Windows 2000 issue, VeraCrypt does not support the Windows Mount Manager under Windows 2000. Therefore, some Windows 2000 built-in tools, such as Disk Defragmenter, do not work on VeraCrypt volumes. Furthermore, it is not possible to use the Mount Manager services under Windows 2000, e.g., assign a mount point to a VeraCrypt volume (i.e., attach a VeraCrypt volume to a folder).
• VeraCrypt does not support pre-boot authentication for operating systems installed within VHD files, except when booted using appropriate virtual-machine software such as Microsoft Virtual PC.
• The Windows Volume Shadow Copy Service is currently supported only for partitions within the key scope of system encryption (e.g. a system partition encrypted by VeraCrypt, or a non- system partition located on a system drive encrypted by VeraCrypt, mounted when the encrypted operating system is running). Note: For other types of volumes, the Volume Shadow Copy Service is not supported because the documentation for the necessary API is not available.
• Windows boot settings cannot be changed from within a hidden operating system if the system does not boot from the partition on which it is installed. This is due to the fact that, for security reasons, the boot partition is mounted as read-only when the hidden system is running. To be able to change the boot settings, please start the decoy operating system.
• Encrypted partitions cannot be resized except partitions on an entirely encrypted system drive that are resized while the encrypted operating system is running.
• When the system partition/drive is encrypted, the system cannot be upgraded (for example, from Windows XP to Windows Vista) or repaired from within the pre-boot environment (using a Windows setup CD/DVD or the Windows pre-boot component). In such cases, the system partition/drive must be decrypted first. Note: A running operating system can beupdated (security patches, service packs, etc.) without any problems even when the system partition/drive is encrypted.
• System encryption is supported only on drives that are connected locally via an ATA/SCSI interface (note that the term ATA also refers to SATA and eSATA).
• When system encryption is used (this also applies to hidden operating systems), VeraCrypt does not support multi-boot configuration changes (for example, changes to the number of operating systems and their locations). Specifically, the configuration must remain the same as it was when the VeraCrypt Volume Creation Wizard started to prepare the process of encryption of the system partition/drive (or creation of a hidden operating system).
  
  Note: The only exception is the multi-boot configuration where a running VeraCrypt-encrypted operating system is always located on drive #0, and it is the only operating system located on the drive (or there is one VeraCrypt-encrypted decoy and one VeraCrypt-encrypted hidden operating system and no other operating system on the drive), and the drive is connected or disconnected before the computer is turned on (for example, using the power switch on an external eSATA drive enclosure). There may be any additional operating systems (encrypted or unencrypted) installed on other drives connected to the computer (when drive #0 is disconnected, drive #1 becomes drive #0, etc.)
• When the notebook battery power is low, Windows may omit sending the appropriate messages to running applications when the computer is entering power saving mode. Therefore, VeraCrypt may fail to auto-dismount volumes in such cases.
• Preserving of any timestamp of any file (e.g. a container or keyfile) is not guaranteed to be reliably and securely performed (for example, due to filesystem journals, timestamps of file attributes, or the operating system failing to perform it for various documented and undocumented reasons). Note: When you write to a file-hosted hidden volume, the timestamp of the container may change. This can be plausibly explained as having been caused by changing the (outer) volume password. Also note that VeraCrypt never preserves timestamps of system favorite volumes (regardless of the settings).
• Special software (e.g., a low-level disk editor) that writes data to a disk drive in a way that circumvents drivers in the driver stack of the class ‘DiskDrive’ (GUID of the class is 4D36E967- E325-11CE-BFC1-08002BE10318) can write unencrypted data to a non-system drive hosting a mounted VeraCrypt volume (‘Partition0’) and to encrypted partitions/drives that are within the key scope of active system encryption (VeraCrypt does not encrypt such data written that way). Similarly, software that writes data to a disk drive circumventing drivers in the driver stack of the class ‘Storage Volume’ (GUID of the class is 71A27CDD-812A-11D0-BEC7-08002BE2092F) can write unencrypted data to VeraCrypt partition-hosted volumes (even if they are mounted).
• For security reasons, when a hidden operating system is running, VeraCrypt ensures that all local unencrypted filesystems and non-hidden VeraCrypt volumes are read-only. However, this does not apply to filesystems on CD/DVD-like media and on custom, atypical, or non-standard devices/media (for example, any devices/media whose class is other than the Windows device class ‘Storage Volume’ or that do not meet the requirements of this class (GUID of the class is 71A27CDD-812A-11D0-BEC7-08002BE2092F)).
• Device-hosted VeraCrypt volumes located on floppy disks are not supported. Note: You can still create file-hosted VeraCrypt volumes on floppy disks.
• Windows Server editions don't allow the use of mounted VeraCrypt volumes as a path for server backup. This can solved by activating sharing on the VeraCrypt volume through Explorer interface (of course, you have to put the correct permission to avoid unauthorized access) and then choosing the option "Remote shared folder" (it is not remote of course but Windows needs a network path). There, you can type the path of the shared drive (for example \\ServerName\sharename) and the backup will be configured correctly.
• Due to Microsoft design flaws in NTFS sparse files handling, you may encounter system errors when writing data to large Dynamic volumes (more than few hundreds GB). To avoid this, the recommended size for a Dynamic volume container file for maximum compatibility is 300 GB. The following link gives more details concerning this limitation: http://www.flexhex.com/docs/articles/sparse-files.phtml#msdn
• Further limitations are listed in the section Security Model.

Release Notes

1.0f-2(April 5^th, 2015):

• All OSs:
  • Mounting speed improvement, up to 20% quicker on 64-bit (contributed by Nils Maier)
  • Add option to set default hash/TrueCryptMode used for mounting volumes.
  • Use TrueCryptMode/Hash specified in command line in password dialog.
• Windows:
  • Solve CryptAcquireContext vulnerability reported by Open Crypto Audit Phase II.
  • Proper handling of random generator failures. Inform user in such cases.
  • TrueCrypt Mode related changes:
    • Support mounting TrueCrypt system partition (no conversion yet)
    • Support TrueCrypt volumes as System Favorites.
    • Correct displaying wrong TrueCrypt mode in volume properties when SHA-256 is used.
  • Solve PIN BLOCKED issue with smart cards in a special case.
  • Correctly handle file access errors when mounting containers.
  • Solve several issues reported by the Static Code Analysis too Coverity.
  • Bootloader: Add "Verifying Password..." message.
  • When UAC prompt fails (for example timeout), offer the user to retry the operation.
  • Uninstall link now open the standard "Add/Remove Programs" window.
  • On uninstall, remove all VeraCrypt references from registry and disk.
  • Included VeraCryptExpander in the Setup.
  • Add option to temporary cache password when mounting multiple favorites.
  • Minor fixes and enhancements (see git history for more information)
• MacOSX:
  • Solve issue volumes not auto-dismounting when quitting VeraCrypt.
  • Solve issue VeraCrypt window not reopening by clicking dock icon.
• Linux/MacOSX:
  • Solve preferences dialog not closing when clicking on the 'X' icon.
  • Solve read-only issue when mounting non-FAT volumes in some cases.
  • Support opening/exploring mounted volumes on desktops other than Gnome/KDE.
  • Solve various installer issues when running on less common configurations
  • Minor fixes (see git history for more information)

1.0f-1 (January 4^th, 2015)

• All OSs:
  • Add support for old TrueCrypt 6.0.
  • Change naming of cascades algorithms in GUI for a better description.
• Linux/MacOSX:
  • Make cancel button of the preference dialog working.
  • Solve impossibility to enter a one digit size for the volume.
  • Add wait dialog to the benchmark calculation.
• Windows:
  • Add TrueCrypt mode to the mounted volume information.
  • For Windows XP, correct the installer graphical artefacts.

1.0f (December 30, 2014)

• All OSs:
  • Add support for mounting TrueCrypt volumes.
  • Add support for converting TrueCrypt containers and non-system partitions.
  • Add support for SHA-256 for volume encryption.
  • Make SHA-512 the default key derivation algorithm and change the order of preference of derivation algorithms : SHA-512 -> Whirlpool -> SHA-256 -> RIPEMD160
  • Deprecate RIPEMD160 for non-system encryption.
  • Speedup mount operation by enabling choice of correct hash algorithm.
  • Display a wait dialog during lengthy operations to avoid freezing the GUI.
  • Implement creation of multiple keyfiles at once, with predefined or random size.
  • Always display random gathering dialog before performing sensitive operations.
  • Links in the application now points to the online resources on Codeplex
  • First version of proper VeraCrypt User Guide
• MacOSX:
  • Implement support for hard drives with a large sector size (> 512).
  • Link against new wxWidgets version 3.0.2.
  • Solve truncated text in some Wizard windows.
• Linux:
  • Add support of NTFS formatting of volumes.
  • Correct issue on opening of the user guide PDF.
  • Better support for hard drives with a large sector size (> 512).
  • Link against new wxWidgets version 3.0.2.
• Windows:
  
  • Security: fix vulnerability in bootloader detected by Open Crypto Audit and make it more robust.
  • Add support for SHA-256 in system boot encryption.
  • Various optimizations in bootloader.
  • Complete fix of ShellExecute security issue.
  • Kernel driver: check that the password length received from bootloader is less or equal to 64.
  • Correct a random crash when clicking the link for more information on keyfiles
  • Implement option to auto-dismount when user session is locked
  • Add self-test vectors for SHA-256
  • Modern look-and-feel by enabling visual styles
  • few minor fixed.

Changes between 1.0f-1 and 1.0f-2 (5 April 2015) :

• All OSs:
  • Mounting speed improvement, up to 20% quicker on 64-bit (contributed by Nils Maier)
  • Add option to set default hash/TrueCryptMode used for mounting volumes.
  • Use TrueCryptMode/Hash specified in command line in password dialog.

• Windows:
  • Solve CryptAcquireContext vulnerability reported by Open Crypto Audit Phase II.
  • Proper handling of random generator failures. Inform user in such cases.
  • TrueCrypt Mode related changes:
    • Support mounting TrueCrypt system partition (no conversion yet)
    • Support TrueCrypt volumes as System Favorites.
    • Correct displaying wrong TrueCrypt mode in volume properties when SHA-256 is used.
  • Solve PIN BLOCKED issue with smart cards in a special case.
  • Correctly handle file access errors when mounting containers.
  • Solve several issues reported by the Static Code Analysis too Coverity.
  • Bootloader: Add "Verifying Password..." message.
  • When UAC prompt fails (for example timeout), offer the user to retry the operation.
  • Uninstall link now open the standard "Add/Remove Programs" window.
  • On uninstall, remove all VeraCrypt references from registry and disk.
  • Included VeraCryptExpander in the Setup.
  • Add option to temporary cache password when mounting multiple favorites.
  • Minor fixes and enhancements (see git history for more information)

• MacOSX:
  • Solve issue volumes not auto-dismounting when quitting VeraCrypt.
  • Solve issue VeraCrypt window not reopening by clicking dock icon

• Linux/MacOSX:
  • Solve preferences dialog not closing when clicking on the 'X' icon.
  • Solve read-only issue when mounting non-FAT volumes in some cases.
  • Support opening/exploring mounted volumes on desktops other than Gnome/KDE.
  • Solve various installer issues when running on less common configurations
  • Minor fixes (see git history for more information)

Changes between 1.0f and 1.0f-1 (4 January 2015) :

• All OSs:
  • Add support for old TrueCrypt 6.0.
  • Change naming of cascades algorithms in GUI for a better description.
• Linux/MacOSX:
  • Make cancel button of the preference dialog working.
  • Solve impossibility to enter a one digit size for the volume.
  • Add wait dialog to the benchmark calculation.
• Windows:
  • For Windows XP, correct the installer graphical artefacts.
  • Add TrueCrypt mode to the mounted volume information.

Changes between 1.0e and 1.0f (30 December 2014) :

• All OSs:
  • Add support for mounting TrueCrypt volumes.
  • Add support for converting TrueCrypt containers and non-system partitions.
  • Add support for SHA-256 for volume encryption.
  • Make SHA-512 the default key derivation algorithm and change the order of preference of derivation algorithms : SHA-512 -> Whirlpool -> SHA-256 -> RIPEMD160
  • Deprecate RIPEMD160 for non-system encryption.
  • Speedup mount operation by enabling choice of correct hash algorithm.
  • Display a wait dialog during lengthy operations to avoid freezing the GUI.
  • Implement creation of multiple keyfiles at once, with predefined or random size.
  • Always display random gathering dialog before performing sensitive operations.
  • Links in the application now points to the online resources on Codeplex
  • First version of proper VeraCrypt User Guide

• MacOSX:
  • Implement support for hard drives with a large sector size (> 512).
  • Link against new wxWidgets version 3.0.2
  • Solve truncated text in some Wizard windows.

• Linux:
  • Add support of NTFS formatting of volumes.
  • Correct issue on opening of the user guide PDF
  • Better support for hard drives with a large sector size (> 512).
  • Link against new wxWidgets version 3.0.2

• Windows:
  • Security: fix vulnerability in bootloader detected by Open Crypto Audit and make it more robust.
  • Add support for SHA-256 in system boot encryption.
  • Various optimizations in bootloader.
  • Complete fix of ShellExecute security issue.
  • Kernel driver: check that the password length received from bootloader is less or equal to 64.
  • Correct a random crash when clicking the link for more information on keyfiles
  • Implement option to auto-dismount when user session is locked
  • Add self-test vectors for SHA-256
  • Modern look-and-feel by enabling visual styles.
  • few minor fixed.

Changes between 1.0f-1 and 1.0f-2 (5 April 2015) :

• All OSs:
  • Mounting speed improvement, up to 20% quicker on 64-bit (contributed by Nils Maier)
  • Add option to set default hash/TrueCryptMode used for mounting volumes.
  • Use TrueCryptMode/Hash specified in command line in password dialog.

• Windows:
  • Solve CryptAcquireContext vulnerability reported by Open Crypto Audit Phase II.
  • Proper handling of random generator failures. Inform user in such cases.
  • TrueCrypt Mode related changes:
    • Support mounting TrueCrypt system partition (no conversion yet)
    • Support TrueCrypt volumes as System Favorites.
    • Correct displaying wrong TrueCrypt mode in volume properties when SHA-256 is used.
  • Solve PIN BLOCKED issue with smart cards in a special case.
  • Correctly handle file access errors when mounting containers.
  • Solve several issues reported by the Static Code Analysis too Coverity.
  • Bootloader: Add "Verifying Password..." message.
  • When UAC prompt fails (for example timeout), offer the user to retry the operation.
  • Uninstall link now open the standard "Add/Remove Programs" window.
  • On uninstall, remove all VeraCrypt references from registry and disk.
  • Included VeraCryptExpander in the Setup.
  • Add option to temporary cache password when mounting multiple favorites.
  • Minor fixes and enhancements (see git history for more information)

• MacOSX:
  • Solve issue volumes not auto-dismounting when quitting VeraCrypt.
  • Solve issue VeraCrypt window not reopening by clicking dock icon

• Linux/MacOSX:
  • Solve preferences dialog not closing when clicking on the 'X' icon.
  • Solve read-only issue when mounting non-FAT volumes in some cases.
  • Support opening/exploring mounted volumes on desktops other than Gnome/KDE.
  • Solve various installer issues when running on less common configurations
  • Minor fixes (see git history for more information)

Changes between 1.0f and 1.0f-1 (4 January 2015) :

• All OSs:
  • Add support for old TrueCrypt 6.0.
  • Change naming of cascades algorithms in GUI for a better description.
• Linux/MacOSX:
  • Make cancel button of the preference dialog working.
  • Solve impossibility to enter a one digit size for the volume.
  • Add wait dialog to the benchmark calculation.
• Windows:
  • For Windows XP, correct the installer graphical artefacts.
  • Add TrueCrypt mode to the mounted volume information.

Changes between 1.0e and 1.0f (30 December 2014) :

• All OSs:
  • Add support for mounting TrueCrypt volumes.
  • Add support for converting TrueCrypt containers and non-system partitions.
  • Add support for SHA-256 for volume encryption.
  • Make SHA-512 the default key derivation algorithm and change the order of preference of derivation algorithms : SHA-512 -> Whirlpool -> SHA-256 -> RIPEMD160
  • Deprecate RIPEMD160 for non-system encryption.
  • Speedup mount operation by enabling choice of correct hash algorithm.
  • Display a wait dialog during lengthy operations to avoid freezing the GUI.
  • Implement creation of multiple keyfiles at once, with predefined or random size.
  • Always display random gathering dialog before performing sensitive operations.
  • Links in the application now points to the online resources on Codeplex
  • First version of proper VeraCrypt User Guide

• MacOSX:
  • Implement support for hard drives with a large sector size (> 512).
  • Link against new wxWidgets version 3.0.2
  • Solve truncated text in some Wizard windows.

• Linux:
  • Add support of NTFS formatting of volumes.
  • Correct issue on opening of the user guide PDF
  • Better support for hard drives with a large sector size (> 512).
  • Link against new wxWidgets version 3.0.2

• Windows:
  • Security: fix vulnerability in bootloader detected by Open Crypto Audit and make it more robust.
  • Add support for SHA-256 in system boot encryption.
  • Various optimizations in bootloader.
  • Complete fix of ShellExecute security issue.
  • Kernel driver: check that the password length received from bootloader is less or equal to 64.
  • Correct a random crash when clicking the link for more information on keyfiles
  • Implement option to auto-dismount when user session is locked
  • Add self-test vectors for SHA-256
  • Modern look-and-feel by enabling visual styles.
  • few minor fixed.