<strong>Note to users who created volumes with 1.17 version of VeraCrypt or earlier: </strong><br/>

<span style="color:#ff0000;">To avoid hinting whether your volumes contain a hidden volume or not, or if you depend on plausible deniability when using hidden volumes/OS, then you must recreate both the outer and hidden volumes including system encryption and hidden OS, discarding existing volumes created prior to 1.18a version of VeraCrypt.</span></li>

</p>

<ul>

<li><strong>Windows:</strong>

<ul>

<li>MBR Bootloader: dynamically determine boot loader memory segment instead of hardcoded values (proposed by neos6464)</li>

<li>MBR Bootloader: workaround for issue affecting creation of hidden OS on some SSD drives.</li>

<li>Fix issue related to Windows Update breaking VeraCrypt UEFI bootloader.</li>

<li>New security features:</li>

<ul>

<li>Erase system encryption keys from memory during shutdown/reboot to help mitigate some cold boot attacks</li>

<li>Add option when system encryption is used to erase all encryption keys from memory when a new device is connected to the system.</li>

<li>Add new driver entry point that can be called by applications to erase encryption keys from memory in case of emergency.</li>

</ul>

<li>Add mount option that allows mounting a volume without attaching it to the specified drive letter.</li>

<li>Update libzip to version 1.5.1</li>

<li>Do not create uninstall shortcut in startmenu when installing VeraCrypt. (by Sven Strickroth)</li>

#define VERSION_NUM 0x0124

// Release date

#define TC_RELEASE_DATE_YEAR 2019

#define TC_RELEASE_DATE_MONTH 1

//

VS_VERSION_INFO VERSIONINFO

FILEFLAGSMASK 0x17L

#ifdef _DEBUG

FILEFLAGS 0x1L

Class = "Encryption" ;This is determined by the work this filter driver does

ClassGuid = {a0a701c0-a511-42ff-aa6c-06dc0395576f} ;This value is determined by the Class

Provider = %ProviderString%

CatalogFile = veracrypt.cat