From 8e398770544b303d22fe24fbd89034c7f62c6bf6 Mon Sep 17 00:00:00 2001 From: Mounir IDRASSI Date: Sun, 3 Mar 2019 18:44:21 +0100 Subject: Increment version to 1.24-Beta3. Update Release Notes. --- Translations/Language.ar.xml | 3 ++- Translations/Language.be.xml | 13 ++++++------ Translations/Language.bg.xml | 13 ++++++------ Translations/Language.ca.xml | 3 ++- Translations/Language.cs.xml | 3 ++- Translations/Language.da.xml | 13 ++++++------ Translations/Language.de.xml | 3 ++- Translations/Language.el.xml | 13 ++++++------ Translations/Language.es.xml | 3 ++- Translations/Language.et.xml | 13 ++++++------ Translations/Language.eu.xml | 13 ++++++------ Translations/Language.fa.xml | 13 ++++++------ Translations/Language.fi.xml | 13 ++++++------ Translations/Language.fr.xml | 3 ++- Translations/Language.hu.xml | 13 ++++++------ Translations/Language.id.xml | 13 ++++++------ Translations/Language.it.xml | 11 +++++----- Translations/Language.ja.xml | 13 ++++++------ Translations/Language.ka.xml | 13 ++++++------ Translations/Language.ko.xml | 13 ++++++------ Translations/Language.lv.xml | 13 ++++++------ Translations/Language.my.xml | 13 ++++++------ Translations/Language.nl.xml | 13 ++++++------ Translations/Language.nn.xml | 13 ++++++------ Translations/Language.pl.xml | 3 ++- Translations/Language.pt-br.xml | 13 ++++++------ Translations/Language.ro.xml | 13 ++++++------ Translations/Language.ru.xml | 3 ++- Translations/Language.sk.xml | 13 ++++++------ Translations/Language.sl.xml | 13 ++++++------ Translations/Language.sv.xml | 13 ++++++------ Translations/Language.th.xml | 11 +++++----- Translations/Language.tr.xml | 11 +++++----- Translations/Language.uk.xml | 13 ++++++------ Translations/Language.uz.xml | 13 ++++++------ Translations/Language.vi.xml | 13 ++++++------ Translations/Language.zh-cn.xml | 3 ++- Translations/Language.zh-hk.xml | 11 +++++----- Translations/Language.zh-tw.xml | 13 ++++++------ doc/chm/VeraCrypt User Guide.chm | Bin 1955031 -> 1955375 bytes doc/html/Release Notes.html | 32 ++++++++++++++++++++---------- src/Build/Resources/MacOSX/Info.plist.xml | 2 +- src/Common/Tcdefs.h | 6 +++--- src/Driver/Driver.rc | 4 ++-- src/ExpandVolume/ExpandVolume.rc | 8 ++++---- src/Format/Format.rc | 8 ++++---- src/Mount/Mount.rc | 8 ++++---- src/Release/Setup Files/veracrypt-x64.cat | Bin 10583 -> 10796 bytes src/Release/Setup Files/veracrypt-x64.sys | Bin 804568 -> 827824 bytes src/Release/Setup Files/veracrypt.Inf | 2 +- src/Release/Setup Files/veracrypt.cat | Bin 10531 -> 10531 bytes src/Release/Setup Files/veracrypt.sys | Bin 760280 -> 766000 bytes src/Setup/MacOSX/veracrypt.pkgproj | 4 ++-- src/Setup/Portable.rc | 8 ++++---- src/Setup/Setup.rc | 8 ++++---- src/Signing/sign.bat | 2 +- src/Signing/sign_test.bat | 2 +- src/Signing/sign_test_debug.bat | 2 +- 58 files changed, 278 insertions(+), 227 deletions(-) diff --git a/Translations/Language.ar.xml b/Translations/Language.ar.xml index cd82e780..b7e48187 100644 --- a/Translations/Language.ar.xml +++ b/Translations/Language.ar.xml @@ -1,6 +1,6 @@ - + @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.be.xml b/Translations/Language.be.xml index 631ea303..7d7a78b5 100644 --- a/Translations/Language.be.xml +++ b/Translations/Language.be.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Select the language to use during the installation: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Select the language to use during the installation: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.bg.xml b/Translations/Language.bg.xml index 1ff8a7c3..4c337c0e 100644 --- a/Translations/Language.bg.xml +++ b/Translations/Language.bg.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Select the language to use during the installation: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Select the language to use during the installation: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.ca.xml b/Translations/Language.ca.xml index 3eeb6de4..897c1b86 100644 --- a/Translations/Language.ca.xml +++ b/Translations/Language.ca.xml @@ -1,6 +1,6 @@ - + @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.cs.xml b/Translations/Language.cs.xml index 39c36300..7d6bc486 100644 --- a/Translations/Language.cs.xml +++ b/Translations/Language.cs.xml @@ -1,6 +1,6 @@ - + @@ -1433,6 +1433,7 @@ DŮLEŽITÉ UPOZORNĚNÍ:\n - Mějte na paměti, že tato možnost nepřetrvá po vypnutí/restartu systému, proto ji budete muset znovu zapnout po spuštění.\n\n - Je-li tato možnost povolena a bude připojeno nové zařízení, počítač zamrzne a může přejít do BSOD, jelikož Windows nebude mít přístup k zašifrovanému disku, smažete-li klíče z paměti.\n Spuštění Použít náhodné hardwarové generování v CPU jako dodatečný zdroj entropie + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.da.xml b/Translations/Language.da.xml index dfa25f53..33c96d36 100644 --- a/Translations/Language.da.xml +++ b/Translations/Language.da.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Vælg det sprog der skal vises under installationen: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Vælg det sprog der skal vises under installationen: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.de.xml b/Translations/Language.de.xml index 7fe268be..2afe5236 100644 --- a/Translations/Language.de.xml +++ b/Translations/Language.de.xml @@ -1,6 +1,6 @@ - + @@ -1436,6 +1436,7 @@ WICHTIGE HINWEISE:\n - Bitte beachten Sie, dass diese Option nach einem Herunterfahren/Neustart nicht erhalten bleibt, so dass Sie sie beim nächsten Start der Maschine erneut auswählen müssen.\n\n - Wenn diese Option aktiviert ist, wird der Rechner nach dem Anschließen eines neuen Geräts einfrieren und schließlich mit einem BSOD abstürzen, da Windows nach dem Löschen seiner Schlüssel aus dem Speicher nicht mehr auf die verschlüsselte Festplatte zugreifen kann.\n Wird gestartet CPU-Hardware-Zufallsgenerator als zusätzliche Entropiequelle verwenden + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.el.xml b/Translations/Language.el.xml index de1f445c..d562aeb7 100644 --- a/Translations/Language.el.xml +++ b/Translations/Language.el.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Επιλέξτε τη γλώσσα που θα χρησιμοποιηθεί κατά τη διάρκεια της εγκατάστασης: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Επιλέξτε τη γλώσσα που θα χρησιμοποιηθεί κατά τη διάρκεια της εγκατάστασης: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.es.xml b/Translations/Language.es.xml index e9339308..1479dacf 100644 --- a/Translations/Language.es.xml +++ b/Translations/Language.es.xml @@ -1,6 +1,6 @@ - + @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Iniciando Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.et.xml b/Translations/Language.et.xml index 68711225..3126f2b0 100644 --- a/Translations/Language.et.xml +++ b/Translations/Language.et.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Select the language to use during the installation: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Select the language to use during the installation: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.eu.xml b/Translations/Language.eu.xml index 42c75ab3..6ea7ab1d 100644 --- a/Translations/Language.eu.xml +++ b/Translations/Language.eu.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Select the language to use during the installation: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Select the language to use during the installation: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.fa.xml b/Translations/Language.fa.xml index ae4b71ce..69523c27 100644 --- a/Translations/Language.fa.xml +++ b/Translations/Language.fa.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Select the language to use during the installation: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Select the language to use during the installation: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.fi.xml b/Translations/Language.fi.xml index 9c92a03f..fd2bce4b 100644 --- a/Translations/Language.fi.xml +++ b/Translations/Language.fi.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Varmista, että Pelastuslevy on poistettu oikein.\n\nJos olet purkanut Pelastuslevyn -levykuvan, irrota USB-tikku ja asenna se uudelleen. Yritä uudelleen valitsemalla 'Seuraava'. Jos tämä ei auta, kokeile toista USB-muistitikkua ja/tai muuta ZIP-ohjelmistoa.\n\nJos et ole vielä purkanut Pelastuslevyn -ohjelmaa, valitse se ja valitse sitten 'Seuraava'.\n\nJos yritit tarkistaa VeraCryptin Pelastuslevyn, joka on luotu ennen ohjatun toiminnon aloittamista, huomaa, että tällaista pelastuslevyä ei voida käyttää, koska se on luotu toista pääavainta varten. Sinun täytyy purkaa vasta tehdyn Pelastuslevyn ZIP -levykuva. Varmista, että Pelastuslevy on poistettu oikein.\n\nJos olet levittänyt Pelastuslevyn -kuvan USB-muistitikulle, irrota se ja aseta se takaisin paikalleen; yritä uudelleen. Jos tämä ei auta, kokeile muita ZIP-ohjelmistoja ja/tai tietovälineitä.\n\nJos yritit tarkistaa eri pääavain, salasana, suola jne. Varten luotu VeraCryptin Pelastuslevy, huomaa, että tällainen pelastuslevy on aina epäonnistuta tätä tarkistusta. Jos haluat luoda uuden Pelastuslevyn, joka on täysin yhteensopiva nykyisen kokoonpanon kanssa, valitse 'Järjestelmä'> 'Luo Pelastuslevy'. Pelastuslevy -levykuva on luotu ja tallennettu tähän tiedostoon:\n%s\n\nJoten sinun on purettava Pelastuslevy -levykuva USB-muistille, joka on alustettu FAT/FAT32:ksi.\n\nVAROITUS: Huomaa, että zip tiedosto on purettava suoraan USB-tikun juureen. Esimerkiksi jos USB-muistin aseman kirjain on E: purkamalla zip-tiedoston, sen on luotava kansio E:\\EFI USB-muistitikulle.\n\nJos olet luonut Pelastuslevyn, valitse 'Järjestelmä'> 'Vahvista Pelastuslevy' varmistaaksesi, että se on luotu oikein. - Käytä Secure Desktopia salasanojen syöttämiseen + Käytä Secure Desktopia salasanojen syöttämiseen Komentorivin määrittämä tiedostokoko ei ole yhteensopiva valitun ReFS-tiedostojärjestelmän kanssa. Muokkaa käynnistyslataajan kokoonpanoa Näytä EFI Platform -tiedot @@ -1421,10 +1421,10 @@ Estä TRIM-komento järjestelmän osio/asemalle VIRHE: Windows EFI -järjestelmänlataajaa ei löydy levyltä. Toiminto keskeytyy. Tällä hetkellä ei ole mahdollista salata järjestelmää, jos SecureBoot on käytössä ja jos VeraCrypt-mukautettuja avaimia ei ladata laitteen laiteohjelmistoon. SecureBoot on poistettava käytöstä BIOS-kokoonpanossa, jotta järjestelmän salauksessa voidaan edetä. - Liitetty teksti katkaistaan, koska salasanan enimmäispituus on 128 merkkiä - Salasanan enimmäispituus on 128 merkkiä.\nErikoismerkkejä ei sallittu. - Valitse asentamisen aikana käytettävä kieli: - VIRHE: Tiedostosäilö koko on suurempi kuin käytettävissä oleva vapaata tilaa levyllä. + Liitetty teksti katkaistaan, koska salasanan enimmäispituus on 128 merkkiä + Salasanan enimmäispituus on 128 merkkiä.\nErikoismerkkejä ei sallittu. + Valitse asentamisen aikana käytettävä kieli: + VIRHE: Tiedostosäilö koko on suurempi kuin käytettävissä oleva vapaata tilaa levyllä. Salli Windowsin Levyn Eheytyksen eheyttää ei-järjestelmäosio/asema VAROITUS: Järjestelmällisten osioiden tai aseman eheyttäminen voi vuotaa metatietoja sisällöstä tai aiheuttaa piilotettujen tiedostojen aiheuttamaa ongelmaa.\n\nJatketaan? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.fr.xml b/Translations/Language.fr.xml index 50b40cf3..f95c2297 100644 --- a/Translations/Language.fr.xml +++ b/Translations/Language.fr.xml @@ -1,6 +1,6 @@ - + @@ -1433,6 +1433,7 @@ IMPORTANT:\n - Cette option ne persiste pas après l'arrêt ou le redémarrage de la machine et donc il va falloir la sélectionner à nouveau au prochain démarrage.\n\n - Une fois cette option sélectionnée, dès qu'un nouveau périphérique est connecté, l'ordinateur va se figer et Windows s'arrêtera de fonctionner vu qu'il ne peut plus accéder au disque une fois que les clefs de chiffrement ont été effacées de la mémoire.\n Exécution Utiliser le générateur de nombres aléatoires du processeur comme source additionnelle d'entropie + Utiliser l'ancienne valeur pour la longueur maximale de mots de passe (64 caractères) diff --git a/Translations/Language.hu.xml b/Translations/Language.hu.xml index 2013c4fe..c4bad909 100644 --- a/Translations/Language.hu.xml +++ b/Translations/Language.hu.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Betöltő (Boot Loader) Konfig. Szerkesztése Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Válassza ki a telepítés során használandó nyelvet: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Válassza ki a telepítés során használandó nyelvet: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.id.xml b/Translations/Language.id.xml index 1ebca665..5d1d9810 100644 --- a/Translations/Language.id.xml +++ b/Translations/Language.id.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Select the language to use during the installation: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Select the language to use during the installation: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.it.xml b/Translations/Language.it.xml index 2108319c..bc34fe45 100644 --- a/Translations/Language.it.xml +++ b/Translations/Language.it.xml @@ -1,6 +1,6 @@ - + @@ -1421,10 +1421,10 @@ Blocca comandi TRIM sulla partizione/disco di sistema ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Selezionare la lingua da utilizzare durante l'installazione: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Selezionare la lingua da utilizzare durante l'installazione: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Caricamento Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.ja.xml b/Translations/Language.ja.xml index eb90a477..c4dc3b1d 100644 --- a/Translations/Language.ja.xml +++ b/Translations/Language.ja.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - インストール中に利用する言語を選んでください: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + インストール中に利用する言語を選んでください: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.ka.xml b/Translations/Language.ka.xml index ec99a8ab..ed8c66fa 100644 --- a/Translations/Language.ka.xml +++ b/Translations/Language.ka.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Select the language to use during the installation: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Select the language to use during the installation: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.ko.xml b/Translations/Language.ko.xml index 3e8b8717..02ad8f82 100644 --- a/Translations/Language.ko.xml +++ b/Translations/Language.ko.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Select the language to use during the installation: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Select the language to use during the installation: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.lv.xml b/Translations/Language.lv.xml index 1e63f13d..7b477284 100644 --- a/Translations/Language.lv.xml +++ b/Translations/Language.lv.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Select the language to use during the installation: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Select the language to use during the installation: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.my.xml b/Translations/Language.my.xml index 1aeea39b..91dcd84e 100644 --- a/Translations/Language.my.xml +++ b/Translations/Language.my.xml @@ -1,6 +1,6 @@ - + @@ -1409,7 +1409,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1423,10 +1423,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Select the language to use during the installation: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Select the language to use during the installation: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1435,6 +1435,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.nl.xml b/Translations/Language.nl.xml index 0a7ac6d9..2d2b49c5 100644 --- a/Translations/Language.nl.xml +++ b/Translations/Language.nl.xml @@ -1,6 +1,6 @@ - + @@ -1408,7 +1408,7 @@ Verifiëren of de herstelschijf juist is uitgepakt is niet mogelijk.\n\nAls u de herstelschijf hebt uitgepakt, werp de USB-stick dan uit en plaats deze opnieuw; klik daarna op Volgende om het opnieuw te proberen. Als dit niet helpt, probeer dan een andere USB-stick en/of andere ZIP software.\n\nAls u de herstelschijf nog niet hebt uitgepakt, doe het dan nu en klik daarna op Volgende.\n\nAls u probeerde de VeraCrypt herstelschijf te verifiëren voordat u deze wizard startte, dan moet worden opgemerkt dat de herstelschijf niet kan worden gebruikt, dit omdat deze is aangemaakt met een andere hoofdsleutel. U moet het nieuw aangemaakte herstelschijf ZIP-bestand eerst uitpakken. Helaas is controleren of de herstelschijf juist is uitgepakt niet mogelijk.\n\nAls je de herstelschijf hebt uitgepakt naar een usb-stick, plaats deze dan en probeer het opnieuw. Als dit niet helpt, probeer het dan met andere software of een andere apparaat.\n\nAls je een VeraCrypt herstelschijf probeert te controleren die is aangemaakt met een andere sleutel, wachtwoord, salt enz., dan zal het controleren van de herstelschijf altijd mislukken. Om een bruikbare herstelschijf met de huidige configuratie te maken, selecteer dan 'Systeem' > 'Een herstelschijf aanmaken'. Het bestand voor de herstelschijf is aangemaakt en opgeslagen als:\n%s\n\nNu moet u dit bestand uitpakken op een usb-stick welke is geformatteerd als FAT/FAT32.\n\nBELANGRIJK: Het zip-bestand moet u in de basismap van het USB-station uitpakken. Bijvoorbeeld, als uw USB-station E: is, dan moet het uitgepakte zip-bestand een map E:\\EFI op de USB-stick aanmaken.\n\nNdat u de herstelschijf hebt aangemaakt, selecteer 'Systeem' > 'Controleer herstelschijf' om te controleren dat de herstelschijf juist is aangemaakt. - Gebruik het Beveiligd Bureaublad voor wachtwoord invoer + Gebruik het Beveiligd Bureaublad voor wachtwoord invoer De in de opdrachtregel opgegeven bestandsgrootte van het volume is niet compatibel met het geselecteerde ReFS bestandssysteem. Bootloader configuratiebestand bewerken Toon de EFI platform informatie @@ -1422,10 +1422,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Selecteer de taal welke Setup gebruikt tijdens de installatie: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Selecteer de taal welke Setup gebruikt tijdens de installatie: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1434,6 +1434,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.nn.xml b/Translations/Language.nn.xml index fb7f2a52..2eeb40ed 100644 --- a/Translations/Language.nn.xml +++ b/Translations/Language.nn.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Velg språket som skal brukes under installasjonen: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Velg språket som skal brukes under installasjonen: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.pl.xml b/Translations/Language.pl.xml index 086261db..6edfcae3 100644 --- a/Translations/Language.pl.xml +++ b/Translations/Language.pl.xml @@ -1,6 +1,6 @@  - + @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.pt-br.xml b/Translations/Language.pt-br.xml index 9c71be22..1a42f396 100644 --- a/Translations/Language.pt-br.xml +++ b/Translations/Language.pt-br.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Selecione o idioma a ser utilizado durante a instalação: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Selecione o idioma a ser utilizado durante a instalação: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.ro.xml b/Translations/Language.ro.xml index 2485ea1e..10fff004 100644 --- a/Translations/Language.ro.xml +++ b/Translations/Language.ro.xml @@ -1,6 +1,6 @@ - + @@ -168,7 +168,7 @@ Montare volume ca unități detașabile Deschidere fereastră Explorer pentru volumele montate cu succes Păstrare temporară parole în timpul operațiilor de "Montare volume favorite" - Folosire pictogramă diferită în zona de sistem când există volume montate + Folosire pictogramă diferită în zona de sistem când există volume montate Eliminare parole păstrate după autodemontare Eliminare parole păstrate la ieșire Păstrare dată modificare fișiere container @@ -1421,10 +1421,10 @@ Blocare comandă TRIM pe partițiile/unitățile sistem ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Select the language to use during the installation: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Select the language to use during the installation: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.ru.xml b/Translations/Language.ru.xml index 136276fe..e61cc6b1 100644 --- a/Translations/Language.ru.xml +++ b/Translations/Language.ru.xml @@ -1,6 +1,6 @@ - + @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.sk.xml b/Translations/Language.sk.xml index 959d958c..0e257d03 100644 --- a/Translations/Language.sk.xml +++ b/Translations/Language.sk.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Select the language to use during the installation: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Select the language to use during the installation: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.sl.xml b/Translations/Language.sl.xml index eb3da19d..afe234bc 100644 --- a/Translations/Language.sl.xml +++ b/Translations/Language.sl.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Izberite jezik, ki ga želite uporabljati med namestitvijo: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Izberite jezik, ki ga želite uporabljati med namestitvijo: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.sv.xml b/Translations/Language.sv.xml index 46a3d1ca..8f5d311b 100644 --- a/Translations/Language.sv.xml +++ b/Translations/Language.sv.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Select the language to use during the installation: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Select the language to use during the installation: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.th.xml b/Translations/Language.th.xml index eb4494de..df30fe57 100644 --- a/Translations/Language.th.xml +++ b/Translations/Language.th.xml @@ -1,6 +1,6 @@  - + @@ -1422,10 +1422,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Select the language to use during the installation: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Select the language to use during the installation: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1434,6 +1434,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.tr.xml b/Translations/Language.tr.xml index 060d58f0..480dd05e 100644 --- a/Translations/Language.tr.xml +++ b/Translations/Language.tr.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. Kurulum süresince kullanýlacak dili seçin: - ERROR: The size of the file container is larger than the available free space on disk. + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.uk.xml b/Translations/Language.uk.xml index 4a17dc50..41c57698 100644 --- a/Translations/Language.uk.xml +++ b/Translations/Language.uk.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Виберіть мову, яка буде використовуватися під час встановлення: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Виберіть мову, яка буде використовуватися під час встановлення: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.uz.xml b/Translations/Language.uz.xml index 82d44c4a..7147f2cd 100644 --- a/Translations/Language.uz.xml +++ b/Translations/Language.uz.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Select the language to use during the installation: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Select the language to use during the installation: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.vi.xml b/Translations/Language.vi.xml index 6035defb..cfabb5cb 100644 --- a/Translations/Language.vi.xml +++ b/Translations/Language.vi.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Select the language to use during the installation: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Select the language to use during the installation: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.zh-cn.xml b/Translations/Language.zh-cn.xml index 2eef75e8..ec398357 100644 --- a/Translations/Language.zh-cn.xml +++ b/Translations/Language.zh-cn.xml @@ -1,6 +1,6 @@ - + @@ -1433,6 +1433,7 @@ 重要提示：\n - 请记住此选项在关机/重启后不再有效，因此你需要在下一次开机后再次选择这个选项。\n\n - 当此选项启用且有一个新设备接入后，由于在内存中清除密钥后无法访问加密磁盘，电脑将会死机且最终会蓝屏。\n 开始 使用CPU硬件随机数生成器作为额外的熵源 + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.zh-hk.xml b/Translations/Language.zh-hk.xml index 79e6d12a..9e6aa640 100644 --- a/Translations/Language.zh-hk.xml +++ b/Translations/Language.zh-hk.xml @@ -1,6 +1,6 @@ - + @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Select the language to use during the installation: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Select the language to use during the installation: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/Translations/Language.zh-tw.xml b/Translations/Language.zh-tw.xml index df5b0bd8..fffd1144 100644 --- a/Translations/Language.zh-tw.xml +++ b/Translations/Language.zh-tw.xml @@ -1,6 +1,6 @@ - + @@ -1407,7 +1407,7 @@ Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. - Use Secure Desktop for password entry + Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information @@ -1421,10 +1421,10 @@ Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. - Pasted text truncated because the password maximum length is 128 characters - Password already reached its maximum length of 128 characters.\nNo additional character is allowed. - Select the language to use during the installation: - ERROR: The size of the file container is larger than the available free space on disk. + Pasted text truncated because the password maximum length is 128 characters + Password already reached its maximum length of 128 characters.\nNo additional character is allowed. + Select the language to use during the installation: + ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device @@ -1433,6 +1433,7 @@ IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy + Use legacy maximum password length (64 characters) diff --git a/doc/chm/VeraCrypt User Guide.chm b/doc/chm/VeraCrypt User Guide.chm index 1208bc68..6548cb5a 100644 Binary files a/doc/chm/VeraCrypt User Guide.chm and b/doc/chm/VeraCrypt User Guide.chm differ diff --git a/doc/html/Release Notes.html b/doc/html/Release Notes.html index c56bd1a9..1cfcfb5f 100644 --- a/doc/html/Release Notes.html +++ b/doc/html/Release Notes.html @@ -39,17 +39,34 @@ Note to users who created volumes with 1.17 version of VeraCrypt or earlier:
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.

-

1.24-Beta2 (January 31th, 2019):

+

1.24-Beta3 (March 3rd, 2019):

  • All OSs:
    • Increase password maximum length to 128 bytes in UTF-8 encoding.
      • +
        +
      • Add option to use legacy maximum password length (64) instead of new one for compatibility reasons.
        • +
      +
    • Use Hardware RNG based on CPU timing jitter "Jitterentropy" by Stephan Mueller as a good alternative to CPU RDRAND (http://www.chronox.de/jent.html)
    • Speed optimization of XTS mode on 64-bit machine using SSE2 (up to 10% faster).
    • Fix detection of CPU features AVX2/BMI2. Add detection of RDRAND/RDSEED CPU features. Detect Hygon CPU as AMD one.
  • Windows:
      +
    • Implement RAM encryption for keys and passwords using ChaCha12 cipher, t1ha non-cryptographic fast hash and ChaCha20 based CSPRNG.
      • +
        +
      • Available only on 64-bit machines.
        • +
      • Disabled by default. Can be enabled using option in UI.
        • +
      • Less than 10% overhead on modern CPUs.
        • +
      +
    • Mitigate some memory attacks by making VeraCrypt applications memory inaccessible to non-admin users (based on KeePassXC implementation)
      • +
    • New security features:
      • +
        +
      • Erase system encryption keys from memory during shutdown/reboot to help mitigate some cold boot attacks
        • +
      • Add option when system encryption is used to erase all encryption keys from memory when a new device is connected to the system.
        • +
      • Add new driver entry point that can be called by applications to erase encryption keys from memory in case of emergency.
        • +
    • MBR Bootloader: dynamically determine boot loader memory segment instead of hardcoded values (proposed by neos6464)
    • MBR Bootloader: workaround for issue affecting creation of hidden OS on some SSD drives.
    • Fix issue related to Windows Update breaking VeraCrypt UEFI bootloader.
      • @@ -61,19 +78,14 @@
    • Fix ESC on password prompt during Pre-Test not starting Windows.
    • Add menu entry in Rescue Disk that enables starting original Windows loader.
    -
  • Better support Multi-boot for EFI system encryption.
    • -
  • New security features:
    • -
      -
    • Erase system encryption keys from memory during shutdown/reboot to help mitigate some cold boot attacks
      • -
    • Add option when system encryption is used to erase all encryption keys from memory when a new device is connected to the system.
      • -
    • Add new driver entry point that can be called by applications to erase encryption keys from memory in case of emergency.
      • -
    -
  • Use CPU RDRAND or RDSEED as an additional entropy source for our random generator when available.
    • -
  • Add mount option that allows mounting a volume without attaching it to the specified drive letter.
    • +
  • Add option (disabled by default) to use CPU RDRAND or RDSEED as an additional entropy source for our random generator when available.
    • +
  • Add mount option (both UI and command line) that allows mounting a volume without attaching it to the specified drive letter.
  • Update libzip to version 1.5.1
  • Do not create uninstall shortcut in startmenu when installing VeraCrypt. (by Sven Strickroth)
  • Enable selection of Quick Format for file containers creation. Separate Quick Format and Dynamic Volume options in the wizard UI.
  • Fix editor of EFI system encryption configuration file not accepting ENTER key to add new lines.
    • +
  • Avoid simultaneous calls of favorites mounting, for example if corresponding hotkey is pressed multiple times.
    • +
  • Ensure that only one thread at a time can create a secure desktop.
  • Updates and corrections to translations and documentation.
diff --git a/src/Build/Resources/MacOSX/Info.plist.xml b/src/Build/Resources/MacOSX/Info.plist.xml index 53675285..7b66a0e4 100644 --- a/src/Build/Resources/MacOSX/Info.plist.xml +++ b/src/Build/Resources/MacOSX/Info.plist.xml @@ -74,7 +74,7 @@ TRUE CFBundleVersion - 1.24.2 + 1.24.3 CFBundleShortVersionString _VERSION_ diff --git a/src/Common/Tcdefs.h b/src/Common/Tcdefs.h index ed7b330e..f2831aaf 100644 --- a/src/Common/Tcdefs.h +++ b/src/Common/Tcdefs.h @@ -61,15 +61,15 @@ extern unsigned short _rotl16(unsigned short value, unsigned char shift); #endif // Version displayed to user -#define VERSION_STRING "1.24-Beta2" +#define VERSION_STRING "1.24-Beta3" // Version number to compare against driver #define VERSION_NUM 0x0124 // Release date -#define TC_STR_RELEASE_DATE L"January 31, 2019" +#define TC_STR_RELEASE_DATE L"March 3, 2019" #define TC_RELEASE_DATE_YEAR 2019 -#define TC_RELEASE_DATE_MONTH 1 +#define TC_RELEASE_DATE_MONTH 3 #define BYTES_PER_KB 1024LL #define BYTES_PER_MB 1048576LL diff --git a/src/Driver/Driver.rc b/src/Driver/Driver.rc index 00340d3d..749ee1bb 100644 --- a/src/Driver/Driver.rc +++ b/src/Driver/Driver.rc @@ -27,8 +27,8 @@ LANGUAGE LANG_ENGLISH, SUBLANG_ENGLISH_US // VS_VERSION_INFO VERSIONINFO - FILEVERSION 1,24,2,1 - PRODUCTVERSION 1,24,2,1 + FILEVERSION 1,24,3,0 + PRODUCTVERSION 1,24,3,0 FILEFLAGSMASK 0x17L #ifdef _DEBUG FILEFLAGS 0x1L diff --git a/src/ExpandVolume/ExpandVolume.rc b/src/ExpandVolume/ExpandVolume.rc index 67dc4b34..3afdf982 100644 --- a/src/ExpandVolume/ExpandVolume.rc +++ b/src/ExpandVolume/ExpandVolume.rc @@ -192,8 +192,8 @@ IDR_MOUNT_RSRC_HEADER HEADER "resource.h" // VS_VERSION_INFO VERSIONINFO - FILEVERSION 1,24,2,0 - PRODUCTVERSION 1,24,2,0 + FILEVERSION 1,24,3,0 + PRODUCTVERSION 1,24,3,0 FILEFLAGSMASK 0x17L #ifdef _DEBUG FILEFLAGS 0x1L @@ -210,11 +210,11 @@ BEGIN BEGIN VALUE "CompanyName", "IDRIX" VALUE "FileDescription", "VeraCrypt Expander" - VALUE "FileVersion", "1.24-Beta2" + VALUE "FileVersion", "1.24-Beta3" VALUE "LegalTrademarks", "VeraCrypt" VALUE "OriginalFilename", "VeraCryptExpander.exe" VALUE "ProductName", "VeraCrypt" - VALUE "ProductVersion", "1.24-Beta2" + VALUE "ProductVersion", "1.24-Beta3" END END BLOCK "VarFileInfo" diff --git a/src/Format/Format.rc b/src/Format/Format.rc index fd7deee6..39310a68 100644 --- a/src/Format/Format.rc +++ b/src/Format/Format.rc @@ -28,8 +28,8 @@ LANGUAGE LANG_ENGLISH, SUBLANG_ENGLISH_US // VS_VERSION_INFO VERSIONINFO - FILEVERSION 1,24,2,0 - PRODUCTVERSION 1,24,2,0 + FILEVERSION 1,24,3,0 + PRODUCTVERSION 1,24,3,0 FILEFLAGSMASK 0x17L #ifdef _DEBUG FILEFLAGS 0x1L @@ -46,11 +46,11 @@ BEGIN BEGIN VALUE "CompanyName", "IDRIX" VALUE "FileDescription", "VeraCrypt Format" - VALUE "FileVersion", "1.24-Beta2" + VALUE "FileVersion", "1.24-Beta3" VALUE "LegalTrademarks", "VeraCrypt" VALUE "OriginalFilename", "VeraCrypt Format.exe" VALUE "ProductName", "VeraCrypt" - VALUE "ProductVersion", "1.24-Beta2" + VALUE "ProductVersion", "1.24-Beta3" END END BLOCK "VarFileInfo" diff --git a/src/Mount/Mount.rc b/src/Mount/Mount.rc index 9006b46f..a2e0eef3 100644 --- a/src/Mount/Mount.rc +++ b/src/Mount/Mount.rc @@ -548,8 +548,8 @@ END // VS_VERSION_INFO VERSIONINFO - FILEVERSION 1,24,2,0 - PRODUCTVERSION 1,24,2,0 + FILEVERSION 1,24,3,0 + PRODUCTVERSION 1,24,3,0 FILEFLAGSMASK 0x17L #ifdef _DEBUG FILEFLAGS 0x1L @@ -566,11 +566,11 @@ BEGIN BEGIN VALUE "CompanyName", "IDRIX" VALUE "FileDescription", "VeraCrypt" - VALUE "FileVersion", "1.24-Beta2" + VALUE "FileVersion", "1.24-Beta3" VALUE "LegalTrademarks", "VeraCrypt" VALUE "OriginalFilename", "VeraCrypt.exe" VALUE "ProductName", "VeraCrypt" - VALUE "ProductVersion", "1.24-Beta2" + VALUE "ProductVersion", "1.24-Beta3" END END BLOCK "VarFileInfo" diff --git a/src/Release/Setup Files/veracrypt-x64.cat b/src/Release/Setup Files/veracrypt-x64.cat index fb2b13cf..0b3ecb80 100644 Binary files a/src/Release/Setup Files/veracrypt-x64.cat and b/src/Release/Setup Files/veracrypt-x64.cat differ diff --git a/src/Release/Setup Files/veracrypt-x64.sys b/src/Release/Setup Files/veracrypt-x64.sys index c63b7a4d..a4a105b9 100644 Binary files a/src/Release/Setup Files/veracrypt-x64.sys and b/src/Release/Setup Files/veracrypt-x64.sys differ diff --git a/src/Release/Setup Files/veracrypt.Inf b/src/Release/Setup Files/veracrypt.Inf index 6bc212df..af5157c9 100644 --- a/src/Release/Setup Files/veracrypt.Inf +++ b/src/Release/Setup Files/veracrypt.Inf @@ -10,7 +10,7 @@ signature = "$Windows NT$" 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% -DriverVer = 01/31/2019,1.24.2.1 +DriverVer = 03/02/2019,1.24.3.0 CatalogFile = veracrypt.cat diff --git a/src/Release/Setup Files/veracrypt.cat b/src/Release/Setup Files/veracrypt.cat index 82d56af5..ac7d9bf2 100644 Binary files a/src/Release/Setup Files/veracrypt.cat and b/src/Release/Setup Files/veracrypt.cat differ diff --git a/src/Release/Setup Files/veracrypt.sys b/src/Release/Setup Files/veracrypt.sys index 5a8b52f6..6e9c819d 100644 Binary files a/src/Release/Setup Files/veracrypt.sys and b/src/Release/Setup Files/veracrypt.sys differ diff --git a/src/Setup/MacOSX/veracrypt.pkgproj b/src/Setup/MacOSX/veracrypt.pkgproj index 6c3426e2..5b09fef2 100755 --- a/src/Setup/MacOSX/veracrypt.pkgproj +++ b/src/Setup/MacOSX/veracrypt.pkgproj @@ -495,7 +495,7 @@ OVERWRITE_PERMISSIONS VERSION - 1.24.2 + 1.24.3 UUID B14381D9-EC5F-43E4-B971-82AB3D132A64 @@ -1004,7 +1004,7 @@ https://osxfuse.github.io/ NAME - VeraCrypt 1.24-Beta2 + VeraCrypt 1.24-Beta3 SHARED_GLOBAL_DATA diff --git a/src/Setup/Portable.rc b/src/Setup/Portable.rc index 643b47d6..d20cae47 100644 --- a/src/Setup/Portable.rc +++ b/src/Setup/Portable.rc @@ -26,8 +26,8 @@ LANGUAGE LANG_ENGLISH, SUBLANG_ENGLISH_US // VS_VERSION_INFO VERSIONINFO - FILEVERSION 1,24,2,0 - PRODUCTVERSION 1,24,2,0 + FILEVERSION 1,24,3,0 + PRODUCTVERSION 1,24,3,0 FILEFLAGSMASK 0x17L #ifdef _DEBUG FILEFLAGS 0x1L @@ -44,11 +44,11 @@ BEGIN BEGIN VALUE "CompanyName", "IDRIX" VALUE "FileDescription", "VeraCrypt Portable" - VALUE "FileVersion", "1.24-Beta2" + VALUE "FileVersion", "1.24-Beta3" VALUE "LegalTrademarks", "VeraCrypt" VALUE "OriginalFilename", "VeraCrypt Portable.exe" VALUE "ProductName", "VeraCrypt" - VALUE "ProductVersion", "1.24-Beta2" + VALUE "ProductVersion", "1.24-Beta3" END END BLOCK "VarFileInfo" diff --git a/src/Setup/Setup.rc b/src/Setup/Setup.rc index 1b22348a..3fbf797d 100644 --- a/src/Setup/Setup.rc +++ b/src/Setup/Setup.rc @@ -28,8 +28,8 @@ LANGUAGE LANG_ENGLISH, SUBLANG_ENGLISH_US // VS_VERSION_INFO VERSIONINFO - FILEVERSION 1,24,2,0 - PRODUCTVERSION 1,24,2,0 + FILEVERSION 1,24,3,0 + PRODUCTVERSION 1,24,3,0 FILEFLAGSMASK 0x17L #ifdef _DEBUG FILEFLAGS 0x1L @@ -46,11 +46,11 @@ BEGIN BEGIN VALUE "CompanyName", "IDRIX" VALUE "FileDescription", "VeraCrypt Setup" - VALUE "FileVersion", "1.24-Beta2" + VALUE "FileVersion", "1.24-Beta3" VALUE "LegalTrademarks", "VeraCrypt" VALUE "OriginalFilename", "VeraCrypt Setup.exe" VALUE "ProductName", "VeraCrypt" - VALUE "ProductVersion", "1.24-Beta2" + VALUE "ProductVersion", "1.24-Beta3" END END BLOCK "VarFileInfo" diff --git a/src/Signing/sign.bat b/src/Signing/sign.bat index 58d2759d..5641174d 100644 --- a/src/Signing/sign.bat +++ b/src/Signing/sign.bat @@ -1,6 +1,6 @@ PATH=%PATH%;%WSDK81%\bin\x86;C:\Program Files\7-Zip;C:\Program Files (x86)\7-Zip -set VC_VERSION=1.24-Beta2 +set VC_VERSION=1.24-Beta3 set SIGNINGPATH=%~dp0 cd %SIGNINGPATH% diff --git a/src/Signing/sign_test.bat b/src/Signing/sign_test.bat index fa26b5d9..17ead408 100644 --- a/src/Signing/sign_test.bat +++ b/src/Signing/sign_test.bat @@ -1,5 +1,5 @@ PATH=%PATH%;%WSDK81%\bin\x86;C:\Program Files\7-Zip;C:\Program Files (x86)\7-Zip -set VC_VERSION=1.24-Beta2 +set VC_VERSION=1.24-Beta3 set PFXNAME=TestCertificate\idrix_codeSign.pfx set PFXPASSWORD=idrix set PFXCA=TestCertificate\idrix_TestRootCA.crt diff --git a/src/Signing/sign_test_debug.bat b/src/Signing/sign_test_debug.bat index 7a9ad95f..fda5890f 100644 --- a/src/Signing/sign_test_debug.bat +++ b/src/Signing/sign_test_debug.bat @@ -1,5 +1,5 @@ PATH=%PATH%;%WSDK81%\bin\x86;C:\Program Files\7-Zip;C:\Program Files (x86)\7-Zip -set VC_VERSION=1.24-Beta2 +set VC_VERSION=1.24-Beta3 set PFXNAME=TestCertificate\idrix_codeSign.pfx set PFXPASSWORD=idrix set PFXCA=TestCertificate\idrix_TestRootCA.crt -- cgit v1.2.3