macOS: prepare APFS formatter device aliases

When creating an APFS filesystem inside a newly created device-hosted volume, VeraCrypt prepared only the raw hdiutil device path before invoking newfs_apfs. On macOS, newfs_apfs may resolve or reopen the corresponding block device path, which can fail with Permission denied for non-root GUI runs.

Prepare both raw and block aliases for the temporary formatter device, restore changed owners afterward, and share the helper between GUI and text-mode volume creation. Restore each changed alias independently so one restore failure does not skip the rest.

README.md

@@ -29,7 +29,7 @@ called 'TrueCrypt' or 'VeraCrypt'
 ## Requirements for Building VeraCrypt for Windows:
 
 A detailed guide on how to build VeraCrypt on Windows can be found in
-the [documentation](./doc/html/CompilingGuidelineWin.html) in the repository and
+the [documentation](./doc/html/en/CompilingGuidelineWin.html) in the repository and
 it is also available [online](https://veracrypt.jp/en/CompilingGuidelineWin.html) or on the [mirror](https://veracrypt.io/en/CompilingGuidelineWin.html).
 
 IMPORTANT:
@@ -78,7 +78,7 @@ For build instructions, please refer to the file src\Boot\EFI\Readme.txt.
 # II. Linux and Mac OS X
 
 A detailed guide on how to build VeraCrypt on Linux can be found in
-the [documentation](./doc/html/CompilingGuidelineLinux.html) in the repository and
+the [documentation](./doc/html/en/CompilingGuidelineLinux.html) in the repository and
 it is also available [online](https://veracrypt.jp/en/CompilingGuidelineLinux.html) or on the [mirror](https://veracrypt.io/en/CompilingGuidelineLinux.html).
 
 ## Requirements for Building VeraCrypt for Linux and Mac OS X:
@@ -211,7 +211,7 @@ This software as a whole:
 Copyright (c) 2025 AM Crypto. All rights reserved.  
 
 Portions of this software:  
-Copyright (c) 2025 AM Crypto. All rights reserved.
+Copyright (c) 2025 AM Crypto. All rights reserved.  
 Copyright (c) 2013-2025 IDRIX. All rights reserved.  
 Copyright (c) 2003-2012 TrueCrypt Developers Association. All rights reserved.  
 Copyright (c) 1998-2000 Paul Le Roux. All rights reserved.  

Tests/bench.bat

@@ -61,7 +61,7 @@ if not exist !mydriveletter!:\ (
     goto :exit
 )
 
-"!VERACRYPT_PATH!" /dismount !mydriveletter! /silent /q
+"!VERACRYPT_PATH!" /unmount !mydriveletter! /silent /q
 exit /b
 
 :: Subroutine to measure the time taken for a command to execute

Translations/Language.ar.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="ar" name="العربية" en-name="Arabic" version="0.2.0" translators="Ahmad Gharbeia, Khaled Hosny, Ali Khojah" />
     <font lang="ar" class="normal" size="11" face="default" />
     <font lang="ar" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="ar" key="IDT_NEW_PASSWORD">‮كلمة السر:</entry>
     <entry lang="ar" key="IDT_PARALLELIZATION_OPTIONS">الأوامر البرمجية المصغرة بالتوازي</entry>
     <entry lang="ar" key="IDT_PKCS11_LIB_PATH">‮مسار مكتبة ‪PKCS #11‬</entry>
-    <entry lang="ar" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="ar" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="ar" key="IDT_KDF">KDF:</entry>
+    <entry lang="ar" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="ar" key="IDT_PW_CACHE_OPTIONS">‮ذاكرة كلمات السّر</entry>
     <entry lang="ar" key="IDT_SECURITY_OPTIONS">‮خيارات الأمان</entry>
     <entry lang="ar" key="IDT_EMV_OPTIONS">خيارات EMV</entry>
@@ -813,7 +813,7 @@
     <entry lang="ar" key="SECONDARY_KEY_SIZE_LRW">‮ضبط حجم المفتاح (طور ‪LRW‬)</entry>
     <entry lang="ar" key="BITS">‮بتات</entry>
     <entry lang="ar" key="BLOCK_SIZE">‮حجم الكتلة</entry>
-    <entry lang="ar" key="PKCS5_PRF">‮PKCS-5 PRF</entry>
+    <entry lang="ar" key="KDF">‮KDF</entry>
     <entry lang="ar" key="PKCS5_ITERATIONS">‮عدد دورات ‪PKCS-5‬</entry>
     <entry lang="ar" key="VOLUME_CREATE_DATE">‮أُنشئ المجلد</entry>
     <entry lang="ar" key="VOLUME_HEADER_DATE">‮آخر تعديل للترويسة</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="ar" key="INSECURE_MODE">[وضع غير آمن]</entry>
     <entry lang="ar" key="IDC_DISABLE_SCREEN_PROTECTION">تعطيل الحماية من لقطات الشاشة وتسجيل الشاشة</entry>
     <entry lang="ar" key="DISABLE_SCREEN_PROTECTION_WARNING">تحذير: تعطيل حماية الشاشة يقلل بشكل كبير من مستوى الأمان. فعّل هذا الخيار فقط إذا كانت لديك حاجة محددة لالتقاط واجهة VeraCrypt. قد يؤدي ذلك إلى تعريض البيانات الحساسة لأدوات التقاط الشاشة وميزات تسجيل الشاشة مثل Windows 11 Recall.</entry>
+    <entry lang="ar" key="MEMORY_COST">كلفة الذاكرة</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.be.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="be" name="Беларуская" en-name="Belarusian" version="0.1.0" translators="Aleg Azarousky" />
     <font lang="be" class="normal" size="11" face="default" />
     <font lang="be" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="be" key="IDT_NEW_PASSWORD">Пароль:</entry>
     <entry lang="en" key="IDT_PARALLELIZATION_OPTIONS">Thread-Based Parallelization</entry>
     <entry lang="en" key="IDT_PKCS11_LIB_PATH">PKCS #11 Library Path</entry>
-    <entry lang="be" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="en" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="be" key="IDT_KDF">KDF:</entry>
+    <entry lang="en" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="be" key="IDT_PW_CACHE_OPTIONS">Кэшаванне пароляў</entry>
     <entry lang="en" key="IDT_SECURITY_OPTIONS">Security Options</entry>
     <entry lang="en" key="IDT_EMV_OPTIONS">EMV Options</entry>
@@ -813,7 +813,7 @@
     <entry lang="en" key="SECONDARY_KEY_SIZE_LRW">Tweak Key Size (LRW Mode)</entry>
     <entry lang="be" key="BITS">біт</entry>
     <entry lang="be" key="BLOCK_SIZE">Памер блока</entry>
-    <entry lang="be" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="be" key="KDF">KDF</entry>
     <entry lang="be" key="PKCS5_ITERATIONS">Лік ітэрацый PKCS-5</entry>
     <entry lang="be" key="VOLUME_CREATE_DATE">Том створаны</entry>
     <entry lang="be" key="VOLUME_HEADER_DATE">Апошняя змена загалоўка</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="en" key="INSECURE_MODE">[INSECURE MODE]</entry>
     <entry lang="en" key="IDC_DISABLE_SCREEN_PROTECTION">Disable protection against screenshots and screen recording</entry>
     <entry lang="en" key="DISABLE_SCREEN_PROTECTION_WARNING">WARNING: Disabling screen protection significantly reduces security. Enable this option ONLY if you have a specific need to capture VeraCrypt's interface. This may expose sensitive data to screenshot tools and screen recording features such as Windows 11 Recall.</entry>
+    <entry lang="en" key="MEMORY_COST">Memory Cost</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.bg.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="bg" name="Български" en-name="Bulgarian" version="0.1.0" translators="Lachezar Gorchev" />
     <font lang="bg" class="normal" size="11" face="default" />
     <font lang="bg" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="bg" key="IDT_NEW_PASSWORD">Парола:</entry>
     <entry lang="en" key="IDT_PARALLELIZATION_OPTIONS">Thread-Based Parallelization</entry>
     <entry lang="bg" key="IDT_PKCS11_LIB_PATH">Път към PKCS #11 библиотека</entry>
-    <entry lang="bg" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="en" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="bg" key="IDT_KDF">KDF:</entry>
+    <entry lang="en" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="bg" key="IDT_PW_CACHE_OPTIONS">Кеширане на паролите</entry>
     <entry lang="bg" key="IDT_SECURITY_OPTIONS">Опции на сигурността</entry>
     <entry lang="en" key="IDT_EMV_OPTIONS">EMV Options</entry>
@@ -813,7 +813,7 @@
     <entry lang="bg" key="SECONDARY_KEY_SIZE_LRW">Размер на tweak ключа (LRW режим)</entry>
     <entry lang="bg" key="BITS">бита</entry>
     <entry lang="bg" key="BLOCK_SIZE">Размер на блока</entry>
-    <entry lang="bg" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="bg" key="KDF">KDF</entry>
     <entry lang="bg" key="PKCS5_ITERATIONS">PKCS-5 брой на повторенията</entry>
     <entry lang="bg" key="VOLUME_CREATE_DATE">Томът е създаден на</entry>
     <entry lang="bg" key="VOLUME_HEADER_DATE">Последна промяна на заглавната част</entry>
@@ -1640,12 +1640,53 @@
     <entry lang="en" key="LINUX_RESTART_FOR_LANGUAGE_CHANGE">For the language change to come into effect, VeraCrypt needs to be restarted.</entry>
     <entry lang="en" key="ERR_XTS_MASTERKEY_VULNERABLE">WARNING: The volume's master key is vulnerable to an attack that compromises data security.\n\nPlease create a new volume and transfer the data to it.</entry>
     <entry lang="en" key="ERR_SYSENC_XTS_MASTERKEY_VULNERABLE">WARNING: The encrypted system's master key is vulnerable to an attack that compromises data security.\nPlease decrypt the system partition/drive and then re-encrypt it.</entry>
-    <entry lang="en" key="ERR_XTS_MASTERKEY_VULNERABLE_SHORT">WARNING: The volume's master key has a security vulnerability.</entry>  
+    <entry lang="en" key="ERR_XTS_MASTERKEY_VULNERABLE_SHORT">WARNING: The volume's master key has a security vulnerability.</entry>
     <entry lang="en" key="MOUNTPOINT_BLOCKED">ERROR: The volume mount point is blocked because it overrides a protected system directory.\n\nPlease choose a different mount point.</entry>
     <entry lang="en" key="MOUNTPOINT_NOTALLOWED">ERROR: The volume mount point is not allowed because it overrides a directory that is part of the PATH environment variable.\n\nPlease choose a different mount point.</entry>
     <entry lang="en" key="INSECURE_MODE">[INSECURE MODE]</entry>
     <entry lang="en" key="IDC_DISABLE_SCREEN_PROTECTION">Disable protection against screenshots and screen recording</entry>
     <entry lang="en" key="DISABLE_SCREEN_PROTECTION_WARNING">WARNING: Disabling screen protection significantly reduces security. Enable this option ONLY if you have a specific need to capture VeraCrypt's interface. This may expose sensitive data to screenshot tools and screen recording features such as Windows 11 Recall.</entry>
+    <entry lang="en" key="MEMORY_COST">Memory Cost</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.ca.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="ca" name="Català" en-name="Catalan" version="0.1.0" translators="CESICAT, Centre de Seguretat de la Informació de Catalunya" />
     <font lang="ca" class="normal" size="11" face="default" />
     <font lang="ca" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="ca" key="IDT_NEW_PASSWORD">Contrasenya:</entry>
     <entry lang="ca" key="IDT_PARALLELIZATION_OPTIONS">Paral·lelització per fils</entry>
     <entry lang="ca" key="IDT_PKCS11_LIB_PATH">Ubicació de la biblioteca PKCS #11</entry>
-    <entry lang="ca" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="en" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="ca" key="IDT_KDF">KDF:</entry>
+    <entry lang="en" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="ca" key="IDT_PW_CACHE_OPTIONS">Recordar contrasenyes</entry>
     <entry lang="ca" key="IDT_SECURITY_OPTIONS">Opcions de seguretat</entry>
     <entry lang="en" key="IDT_EMV_OPTIONS">EMV Options</entry>
@@ -813,7 +813,7 @@
     <entry lang="ca" key="SECONDARY_KEY_SIZE_LRW">Mida de la clau d'ajust (mode LRW)</entry>
     <entry lang="ca" key="BITS">bits</entry>
     <entry lang="ca" key="BLOCK_SIZE">Mida del bloc</entry>
-    <entry lang="ca" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="ca" key="KDF">KDF</entry>
     <entry lang="ca" key="PKCS5_ITERATIONS">Comptador d'iteracions PKCS-5</entry>
     <entry lang="ca" key="VOLUME_CREATE_DATE">Data de creació</entry>
     <entry lang="ca" key="VOLUME_HEADER_DATE">Capçalera modificada</entry>
@@ -1640,12 +1640,53 @@
     <entry lang="en" key="LINUX_RESTART_FOR_LANGUAGE_CHANGE">For the language change to come into effect, VeraCrypt needs to be restarted.</entry>
     <entry lang="en" key="ERR_XTS_MASTERKEY_VULNERABLE">WARNING: The volume's master key is vulnerable to an attack that compromises data security.\n\nPlease create a new volume and transfer the data to it.</entry>
     <entry lang="en" key="ERR_SYSENC_XTS_MASTERKEY_VULNERABLE">WARNING: The encrypted system's master key is vulnerable to an attack that compromises data security.\nPlease decrypt the system partition/drive and then re-encrypt it.</entry>
-    <entry lang="en" key="ERR_XTS_MASTERKEY_VULNERABLE_SHORT">WARNING: The volume's master key has a security vulnerability.</entry>  
+    <entry lang="en" key="ERR_XTS_MASTERKEY_VULNERABLE_SHORT">WARNING: The volume's master key has a security vulnerability.</entry>
     <entry lang="en" key="MOUNTPOINT_BLOCKED">ERROR: The volume mount point is blocked because it overrides a protected system directory.\n\nPlease choose a different mount point.</entry>
     <entry lang="en" key="MOUNTPOINT_NOTALLOWED">ERROR: The volume mount point is not allowed because it overrides a directory that is part of the PATH environment variable.\n\nPlease choose a different mount point.</entry>
     <entry lang="en" key="INSECURE_MODE">[INSECURE MODE]</entry>
     <entry lang="en" key="IDC_DISABLE_SCREEN_PROTECTION">Disable protection against screenshots and screen recording</entry>
     <entry lang="en" key="DISABLE_SCREEN_PROTECTION_WARNING">WARNING: Disabling screen protection significantly reduces security. Enable this option ONLY if you have a specific need to capture VeraCrypt's interface. This may expose sensitive data to screenshot tools and screen recording features such as Windows 11 Recall.</entry>
+    <entry lang="en" key="MEMORY_COST">Memory Cost</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.co.xml

@@ -6,7 +6,9 @@ Information about Corsican localization:
 	https://github.com/veracrypt/VeraCrypt/blob/master/Translations/Language.co.xml
 
 2. History of Corsican translation for VeraCrypt:
-	- Updated in 2025 by Patriccollu di Santa Maria è Sichè: May 5th (1.26.21), May 25th (1.26.24)
+	- Updated in 2026 by Patriccollu di Santa Maria è Sichè: May 2nd (1.26.28), May 9th (1.26.28)
+	- Updated in 2025 by Patriccollu di Santa Maria è Sichè: May 5th (1.26.21), May 25th (1.26.24), June 26th (1.26.27),
+	          Aug. 31st (1.26.27), Sep. 27th (1.26.27)
 	- Updated in 2024 by Patriccollu di Santa Maria è Sichè: Aug. 2nd (1.26.13), Aug. 10th (1.26.13)
 	- Updated in 2023 by Patriccollu di Santa Maria è Sichè: May 29th (1.26), May 30th (1.26), June 1st (1.26),
 	          June 2nd (1.26), June 5th (1.26.2), June 21st (1.26.2), June 23rd (1.26.2), June 25th (1.26.2),
@@ -19,8 +21,8 @@ Information about Corsican localization:
 	https://github.com/Patriccollu/Lingua_Corsa-Infurmatica/blob/ceppu/Prughjetti/VeraCrypt/Traduzzione.md
 -->
 <VeraCrypt>
-	<localization prog-version="1.26.24">
-		<language langid="co" name="Corsu" en-name="Corsican" version="1.4.8" translators="Patriccollu di Santa Maria è Sichè"/>
+	<localization prog-version="1.26.28">
+		<language langid="co" name="Corsu" en-name="Corsican" version="1.5.3" translators="Patriccollu di Santa Maria è Sichè"/>
 		<font lang="co" class="normal" size="11" face="default"/>
 		<font lang="co" class="bold" size="13" face="Arial"/>
 		<font lang="co" class="fixed" size="12" face="Lucida Console"/>
@@ -310,8 +312,8 @@ Information about Corsican localization:
 	    <entry lang="co" key="IDT_NEW_PASSWORD">Parolla d’intesa :</entry>
 	    <entry lang="co" key="IDT_PARALLELIZATION_OPTIONS">Parallelizazione</entry>
 	    <entry lang="co" key="IDT_PKCS11_LIB_PATH">Chjassu di biblioteca PKCS #11</entry>
-	    <entry lang="co" key="IDT_PKCS5_PRF">PKCS-5 PRF :</entry>
-	    <entry lang="co" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF :</entry>
+	    <entry lang="co" key="IDT_KDF">KDF :</entry>
+	    <entry lang="co" key="IDT_NEW_KDF">KDF :</entry>
 	    <entry lang="co" key="IDT_PW_CACHE_OPTIONS">Impiatta di a parolla d’intesa</entry>
 	    <entry lang="co" key="IDT_SECURITY_OPTIONS">Ozzioni di sicurità</entry>
 	    <entry lang="co" key="IDT_EMV_OPTIONS">Ozzioni EMV</entry>
@@ -379,7 +381,7 @@ Information about Corsican localization:
 	    <entry lang="co" key="IDT_KEYFILES_SIZE">Dimensione di i schedarii chjave :</entry>
 	    <entry lang="co" key="IDT_KEYFILES_BASE_NAME">Nome di basa di i schedarii chjave :</entry>
 	    <entry lang="co" key="IDT_LANGPACK_AUTHORS">Traduttu da :</entry>
-	    <entry lang="co" key="IDT_PLAINTEXT">Dimensione di u testu in chjaru :</entry>
+	    <entry lang="co" key="IDT_PLAINTEXT">Dimensione di u testu rozu :</entry>
 	    <entry lang="co" key="IDT_PLAINTEXT_SIZE_UNIT">bits</entry>
 	    <entry lang="co" key="IDT_POOL_CONTENTS">Cuntenutu di a riserva</entry>
 	    <entry lang="co" key="IDT_PRF">Mischju PRF :</entry>
@@ -393,7 +395,7 @@ Information about Corsican localization:
 	    <entry lang="co" key="IDT_TEST_CIPHERTEXT">Crittogramu (esadecimale)</entry>
 	    <entry lang="co" key="IDT_TEST_DATA_UNIT_NUMBER">Numeru d’unità di dati (esadecimale di 64 bit, dimensione d’unità di dati di 512 ottetti)</entry>
 	    <entry lang="co" key="IDT_TEST_KEY">Chjave (esadecimale)</entry>
-	    <entry lang="co" key="IDT_TEST_PLAINTEXT">Testu in chjaru (esadecimale)</entry>
+	    <entry lang="co" key="IDT_TEST_PLAINTEXT">Testu rozu (esadecimale)</entry>
 	    <entry lang="co" key="IDT_TOKEN_KEYFILE_NAME">Nome di u schedariu chjave :</entry>
 	    <entry lang="co" key="IDT_XTS_MODE">Modu XTS</entry>
 	    <entry lang="co" key="MENU_SYSTEM_ENCRYPTION">&amp;Sistema</entry>
@@ -639,12 +641,12 @@ Information about Corsican localization:
 	    <entry lang="co" key="NONSYS_INPLACE_ENC_RESUME_PASSWORD_PAGE_HELP">Ci vole à stampittà a parolla d’intesa è/o u(i) schedariu(i) chjave per u vulume non sistema induve vò vulete ripiglià u trattamentu di cifratura o di dicifratura in piazza.\n\nRimarca : Dopu u cliccu nant’à « Seguente », VeraCrypt pruverà di truvà tutti i vulumi non sistema induve u trattamentu di cifratura o di dicifratura hè statu interrottu è induve l’intestatura di vulume VeraCrypt po esse dicifrata impieghendu a parolla d’intesa è/o u(i) schedariu(i) chjave pruvisti. S’è più d’un tale vulume hè trovu, duverete scegliene unu à a tappa chì vene.</entry>
 	    <entry lang="co" key="NONSYS_INPLACE_ENC_RESUME_VOL_SELECT_HELP">Ci vole à selezziunà unu di i vulumi di a lista. A lista cuntene ogni vulume non sistema accessibile induve u trattamentu di cifratura o di dicifratura hè statu interrottu è induve l’intestatura di vulume hè stata dicifrata currettamente impieghendu a parolla d’intesa è/o u(i) schedariu(i) chjave pruvisti.</entry>
 	    <entry lang="co" key="NONSYS_INPLACE_DEC_PASSWORD_PAGE_HELP">Ci vole à stampittà a parolla d’intesa è/o u(i) schedariu(i) chjave per u vulume VeraCrypt non sistema chì vò vulete dicifrà.</entry>
-	    <entry lang="co" key="PASSWORD_HELP">Hè assai impurtante di sceglie una bella parolla d’intesa. Duveriate scartà di scegliene unu chì cuntene una parolla unica chì pò esse trova in un dizziunariu (o una cumbinazione di 2, 3 o 4 di tale parolle). Ùn duveria micca cuntene di nome o di data di nascita. Ùn duveria micca esse faciule à induvinà. Una bella parolle d’intesa hè una cumbinazione aleatoria di lettere maiuscule è minuscule, di numeri è di caratteri speziali, tale chì @ ^ = $ * + ecc. Vi ricumandemu di sceglie una parolla d’intesa d’omancu 20 caratteri (u più longu hè u megliu). A longhezza massima pussibule hè 128 caratteri.</entry>
+	    <entry lang="co" key="PASSWORD_HELP">Hè assai impurtante di sceglie una bella parolla d’intesa. Duveriate scartà di scegliene unu chì cuntene una parolla unica chì pò esse trova in un dizziunariu (o una cumbinazione di 2, 3 o 4 di tale parolle). Ùn duveria micca cuntene di nome o di data di nascita. Ùn duveria micca esse faciule à induvinà. Una bella parolle d’intesa hè una cumbinazione aleatoria di lettere maiuscule è minuscule, di numeri è di caratteri speziali, tale chì @ ^ = $ * + ecc. Vi ricumandemu di sceglie una parolla d’intesa d’omancu 20 caratteri (u più longu hè u megliu). A lunghezza massima pussibule hè 128 caratteri.</entry>
 	    <entry lang="co" key="PASSWORD_HIDDENVOL_HELP">Ci vole à sceglie una parolla d’intesa per u vulume piattatu.</entry>
 	    <entry lang="co" key="PASSWORD_HIDDEN_OS_HELP">Ci vole à sceglie una parolla d’intesa per u sistema operatoriu piattatu (i.e. per u vulume piattatu).</entry>
 	    <entry lang="co" key="PASSWORD_HIDDEN_OS_NOTE">IMPURTANTE : A parolla d’intesa chì vò sciglite à sta tappa per u sistema operatoriu piattatu deve esse veramente sfarente di e duie altre parolle d’intesa (i.e. quella di u vulume esternu è quella di u sistema operatoriu d’ingannu).</entry>
 	    <entry lang="co" key="PASSWORD_HIDDENVOL_HOST_DIRECT_HELP">Ci vole à stampittà a parolla d’intesa per u vulume dentru quellu vò vulete creà un vulume piattatu.\n\nDopu u cliccu nant’à « Seguente », VeraCrypt pruverà di muntà u vulume. Da ch’ellu hè muntatu u vulume, a so cartografia di l’unità d’allucamentu serà analizata per determinà a dimensione di l’area ininterrotta di spaziu liberu (s’ellu esiste) di quellu a fine hè alineata cù a fine di u vulume. St’area s’adatterà à u vulume piattatu è dunque limiterà a so dimensione massima pussibule. L’analisa di a cartografia di l’unità d’allucamentu hè necessaria per assicurà chì alcunu datu nant’à u vulume esternu ùn serà pistatu da u vulume piattatu.</entry>
-	    <entry lang="co" key="PASSWORD_HIDDENVOL_HOST_HELP">\nCi vole à sceglie una parolla d’intesa per u vulume esternu. Què serà a parolla d’intesa ch’ella vi serà pussibule di palisà à qualunque chì u vi dumanda o vi sfurza à fallu.\n\nIMPURTANTE : A parolla d’intesa deve esse veramente sfarente di quella chì vò sciglierete per u vulume piattatu.\n\nNota : A longhezza massima pussibule di a parolla d’intesa hè 128 caratteri.</entry>
+	    <entry lang="co" key="PASSWORD_HIDDENVOL_HOST_HELP">\nCi vole à sceglie una parolla d’intesa per u vulume esternu. Què serà a parolla d’intesa ch’ella vi serà pussibule di palisà à qualunque chì u vi dumanda o vi sfurza à fallu.\n\nIMPURTANTE : A parolla d’intesa deve esse veramente sfarente di quella chì vò sciglierete per u vulume piattatu.\n\nNota : A lunghezza massima pussibule di a parolla d’intesa hè 128 caratteri.</entry>
 	    <entry lang="co" key="PASSWORD_SYSENC_OUTERVOL_HELP">Ci vole à sceglie una parolla d’intesa per u vulume esternu. Què serà a parolla d’intesa chì vò puderete dà à qualunque chì vi custringhje à palisà a parolla d’intesa per a prima partizione daretu a partizione di u sistema, induve si truveranu u vulume esternu è u vulume piattatu (chì cuntene u sistema operatoriu piattatu). L’esistenza di u vulume piattatu (è di u sistema operatoriu piattatu) resterà sicretu. Sappiate chì a parolla d’intesa ùn hè micca per u sistema operatoriu d’ingannu.\n\nIMPURTANTE : A parolla d’intesa deve esse veramente sfarente di quella chì vò sciglierete per u vulume piattatu (i.e. per u sistema operatoriu piattatu).</entry>
 	    <entry lang="co" key="PASSWORD_HIDVOL_HOST_TITLE">Parolla d’intesa di u vulume esternu</entry>
 	    <entry lang="co" key="PASSWORD_HIDVOL_TITLE">Parolla d’intesa di u vulume piattatu</entry>
@@ -703,7 +705,7 @@ Information about Corsican localization:
 	    <entry lang="co" key="TEST_INCORRECT_SECONDARY_KEY_SIZE">A chjave secundaria pruvista hè troppu longa o troppu corta.</entry>
 	    <entry lang="co" key="TEST_CIPHERTEXT_SIZE">U crittogramu di prova pruvistu hè troppu longu o troppu cortu.</entry>
 	    <entry lang="co" key="TEST_KEY_SIZE">A chjave di prova pruvista hè troppu longa o troppu corta.</entry>
-	    <entry lang="co" key="TEST_PLAINTEXT_SIZE">U testu in chjaru di prova pruvistu hè troppu longu o troppu cortu.</entry>
+	    <entry lang="co" key="TEST_PLAINTEXT_SIZE">U testu rozu di prova pruvistu hè troppu longu o troppu cortu.</entry>
 	    <entry lang="co" key="TWO_LAYER_CASCADE_HELP">Dui ciframenti in cascata operendu in modu XTS. Prima, ogni bloccu hè cifratu cù %s (chjave di %d bit) eppò cù %s (chjave di %d bit). Ogni ciframentu impiegheghja a so propia chjave. Tutte e chjavi sò indipendentemente mutualmente.</entry>
 	    <entry lang="co" key="THREE_LAYER_CASCADE_HELP">Trè ciframenti in cascata operendu in modu XTS. Prima, ogni bloccu hè cifratu cù %s (chjave di %d bit) eppò cù %s (chjave di %d bit) è infine cù %s (chjave di %d bit). Ogni ciframentu impiegheghja a so propia chjave. Tutte e chjavi sò indipendentemente mutualmente.</entry>
 	    <entry lang="co" key="AUTORUN_MAY_NOT_ALWAYS_WORK">Sappiate chì, secondu à a cunfigurazione di u sistema operatoriu, ste funzioni di lanciata autumatica è di muntatura autumatica ponu funziunà solu quandu i dischi viaghjadori sò creati nant’à i medià di tipu CD/DVD. Sappiate dinù ch’ellu ùn hè micca un prublema in VeraCrypt (ghjè una limitazione di Windows).</entry>
@@ -832,7 +834,7 @@ Information about Corsican localization:
 	    <entry lang="co" key="SECONDARY_KEY_SIZE_LRW">Dimensione di a chjave Tweak (Modu LRW)</entry>
 	    <entry lang="co" key="BITS">bits</entry>
 	    <entry lang="co" key="BLOCK_SIZE">Dimensione di u bloccu</entry>
-	    <entry lang="co" key="PKCS5_PRF">PKCS-5 PRF</entry>
+	    <entry lang="co" key="KDF">KDF</entry>
 	    <entry lang="co" key="PKCS5_ITERATIONS">Numeru d’iterazioni PKCS-5</entry>
 	    <entry lang="co" key="VOLUME_CREATE_DATE">Vulume creatu</entry>
 	    <entry lang="co" key="VOLUME_HEADER_DATE">Ultima mudificazione di l’intestatura</entry>
@@ -1026,7 +1028,7 @@ Information about Corsican localization:
 	    <entry lang="co" key="FREE_SPACE_FOR_WRITING_TO_OUTER_VOLUME">AVERTIMENTU : S’è vò vulete, à l’avvene, aghjunghje più di dati o di schedarii à u vulume esternu, duveriate sceglie una dimensione più chjuca per u vulume piattatu.\n\nDa veru, vulete cuntinuà cù a dimensione specificata ?</entry>
 	    <entry lang="co" key="NO_VOLUME_SELECTED">Alcunu vulume ùn hè selezziunatu.\n\nCliccu nant’à « Apparechju » o « Schedariu » per selezziunà un vulume VeraCrypt.</entry>
 	    <entry lang="co" key="NO_SYSENC_PARTITION_SELECTED">Alcuna partizione ùn hè selezziunata.\n\nCliccu nant’à « Apparechju » per selezziunà una partizione smuntata chì richiede, da regula, l’autenticazione di prepiccera (per indettu, una partizione lucalizata nant’à u lettore cifratu di u sistema d’un altru sistema operatoriu, chì ùn funziuneghja micca, o a partizione cifrata di u sistema d’un altru sistema operatoriu).\n\nNota : A partizione selezziunata serà muntata cum’è un vulume VeraCrypt nurmale senza autenticazione di prepiccera. Què pò esse ghjuvevule, per indettu, per l’operazioni di salvaguardia o di riparazione.</entry>
-	    <entry lang="co" key="CONFIRM_SAVE_DEFAULT_KEYFILES">AVERTIMENTU : S’è i schedarii chjave sò predefiniti è attivati, serà impussibule di muntà i vulumi chì ùn impieganu micca sti schedarii chjave.. Dunque, dopu à l’attivazione di i schedarii chjave predefiniti, tinite à mente di disattivà l’ozzione « Impiegà i schedarii chjave » (sottu u campu di stampittera di a parolla d’intesa) ogni volta chì vò muntate tale vulumi.\n\nDa veru, vulete arregistrà i schedarii chjave è chjassi selezziunati cum’è predefinizione ?</entry>
+	    <entry lang="co" key="CONFIRM_SAVE_DEFAULT_KEYFILES">AVERTIMENTU : S’è i schedarii chjave sò predefiniti è attivati, serà impussibule di muntà i vulumi chì ùn impieganu micca sti schedarii chjave. Dunque, dopu à l’attivazione di i schedarii chjave predefiniti, tinite à mente di disattivà l’ozzione « Impiegà i schedarii chjave » (sottu u campu di stampittera di a parolla d’intesa) ogni volta chì vò muntate tale vulumi.\n\nDa veru, vulete arregistrà i schedarii chjave è chjassi selezziunati cum’è predefinizione ?</entry>
 	    <entry lang="co" key="HK_AUTOMOUNT_DEVICES">Muntatura autumatica di l’apparechji</entry>
 	    <entry lang="co" key="HK_UNMOUNT_ALL">Tuttu smuntà</entry>
 	    <entry lang="co" key="HK_WIPE_CACHE">Nettà l‘impiatta</entry>
@@ -1281,7 +1283,7 @@ Information about Corsican localization:
 	    <entry lang="co" key="RETRY_HIDDEN_SECTOR_DETECTION">Pruvà torna di scopre i settori piattati</entry>
 	    <entry lang="co" key="ENABLE_BAD_SECTOR_ZEROING">Sbagliu : U cuntenutu d’unu o parechji settori nant’à u discu ùn ponu micca esse letti (forse per via d’un difettu fisicu).\n\nU trattamentu di a cifratura in piazza pò cuntinuà solu qundu i settori seranu torna leghjevule. VeraCrypt pò pruvà di rende sti settori leghjevule grazia à una scrittura di zeri nant’à i settori (in appressu, tutti sti blocchi di zeri seranu cifrati). Sarrimanenti, sappiate chì tutti i dati piazzati in i settori illeghjevule seranu persi. S’è vò vulete evità què, pudete pruvà di ricuperà certe parti di i dati dannighjati grazia à un attrezzu terzu adequatu.\n\nNota : In u casu di settori dannighjati fisicamente (à u cuntrariu d’una deteriurazione simplice di i dati è di sbaglii di somma di cuntrollu) a maiò parte di i tipi d’apparechji di memoria attribuiscenu torna i settori di manera interna quandu ci hè un tentativu di scriveci i dati (dunque, i dati esistente nant’à i settor dannighjati ponu stà non cifrati nant’à u lettore).\n\nVulete chì VeraCrypt scrivi zeri nant’à i settori illeghjevule ?</entry>
 	    <entry lang="co" key="DISCARD_UNREADABLE_ENCRYPTED_SECTORS">Sbagliu : U cuntenutu d’unu o parechji settori nant’à u discu ùn ponu micca esse letti (forse per via d’un difettu fisicu).\n\nPer pudè cuntinuà cù a dicifratura, VeraCrypt hà da allatà u cuntenutu di i settori illeghjevule (u cuntenutu serà rimpiazzatu cù dati pseudo aleatorii). Sappiate chì, prima di cuntinuà, pudete pruvà di ricuperà certe parti di i dati dannighjati grazia à un attrezzu terzu adequatu.\n\nVulete chì VeraCrypt rimpiazzi subitu i dati in i settori illeghjevule ?</entry>
-	    <entry lang="co" key="ZEROED_BAD_SECTOR_COUNT">Nota : VeraCrypt hà rimpiazzatu u cuntenutu di %I64d settori illeghjevule (%s) cù blocchi cifrati di zeri di testu in chjaru.</entry>
+	    <entry lang="co" key="ZEROED_BAD_SECTOR_COUNT">Nota : VeraCrypt hà rimpiazzatu u cuntenutu di %I64d settori illeghjevule (%s) cù blocchi cifrati di zeri di testu rozu.</entry>
 	    <entry lang="co" key="SKIPPED_BAD_SECTOR_COUNT">Nota : VeraCrypt hà rimpiazzatu u cuntenutu di %I64d settori illeghjevule (%s) cù dati pseudo aleatorii.</entry>
 	    <entry lang="co" key="ENTER_TOKEN_PASSWORD">Stampittate a parolla d’intesa o u PIN per u gettone « %s » :</entry>
 	    <entry lang="co" key="PKCS11_LIB_LOCATION_HELP">Per permette à VeraCrypt d’accede à un gettone di sicurità o à una carta à stampinu, ci vole à installà in primu locu una biblioteca di prugramma PKCS #11 per u gettone o per a carta à stampinu. Un tale biblioteca pò esse pruvista cù l’apparechju o esse dispunibule in scaricamentu nant’à u situ web di u venditore o d’altri terzi.\nDopu l’installazione di a biblioteca, pudete, sia selezziunalla manualmente via un cliccu nant’à « Selezziunà a bibliuteca », sia lascià VeraCrypt truvalla è selezziunalla autumaticamente via un cliccu nant’à « Scuperta autumatica di a bibliuteca » (a ricerca si ferà solu in u cartulare di u sistema di Windows).</entry>
@@ -1442,8 +1444,8 @@ Information about Corsican localization:
 	    <entry lang="co" key="IDC_BLOCK_SYSENC_TRIM">Bluccà a cumanda TRIM per a partizione o u lettore di u sistema</entry>
 	    <entry lang="co" key="WINDOWS_EFI_BOOT_LOADER_MISSING">SBAGLIU : U caricadore di u sistema EFI di Windows ùn pò micca esse lucalizatu nant’à u discu. L’operazione hà da esse interrotta.</entry>
 	    <entry lang="co" key="SYSENC_EFI_UNSUPPORTED_SECUREBOOT">À st’ora, ùn hè micca pussibule di cifrà un sistema s’è SecureBoot hè attivatu è s’è e chjavi persunalizate di VeraCrypt ùn sò micca caricate in u « firmware » di a mascina. SecureBoot deve esse disattivatu in a cunfigurazione di u BIOS per permette a cifratura di u sistema.</entry>
-	    <entry lang="co" key="PASSWORD_PASTED_TRUNCATED">U testu incullatu hè statu truncatu perchè a longhezza massima di a parolla d’intesa hè %d caratteri</entry>
-	    <entry lang="co" key="PASSWORD_MAXLENGTH_REACHED">A parolla d’intesa hà dighjà toccu a so longhezza massima di %d caratteri.\nAlcunu caratteru addiziunale ùn hè permessu.</entry>
+	    <entry lang="co" key="PASSWORD_PASTED_TRUNCATED">U testu incullatu hè statu truncatu perchè a lunghezza massima di a parolla d’intesa hè %d caratteri</entry>
+	    <entry lang="co" key="PASSWORD_MAXLENGTH_REACHED">A parolla d’intesa hà dighjà toccu a so lunghezza massima di %d caratteri.\nAlcunu caratteru addiziunale ùn hè permessu.</entry>
 	    <entry lang="co" key="IDC_SELECT_LANGUAGE_LABEL">Selezziunà a lingua à impiegà durante l’installazione :</entry>
 	    <entry lang="co" key="VOLUME_TOO_LARGE_FOR_HOST">SBAGLIU : A dimensione di u cuntenidore di schedariu hè più maiò chè u spaziu liberu dispunibule nant’à u discu.</entry>
 	    <entry lang="co" key="IDC_ALLOW_WINDOWS_DEFRAG">Permette à u diframmentatore di discu di Windows di diframmentà a partizione o u lettore non sistema</entry>
@@ -1454,7 +1456,7 @@ Information about Corsican localization:
 	    <entry lang="co" key="CLEAR_KEYS_ON_DEVICE_INSERTION_WARNING">NOTE IMPURTANTE :\n - Tinite à mente chì st’ozzione ùn persisterà micca dopu una piantata o un rilanciu di l’urdinatore, dunque ci vulerà à selezziunalla torna ogni volta chì a mascina hè lanciata.\n\n - Quandu st’ozzione hè attivata è chì un novu apparechju hè cunnessu, a mascina hà da bluccassi è, in fine di contu, hà da piantassi di funziunà perchè Windows ùn pò micca accede à u discu cifratu vistu chì e so chjavi di cifratura sò state squassate da a memoria.\n</entry>
 	    <entry lang="co" key="STARTING">Avviu in corsu</entry>
 	    <entry lang="co" key="IDC_ENABLE_CPU_RNG">Impiegà u generatore aleatoriu di u prucessore CPU cum’è surghjente addiziunale d’energia</entry>
-	    <entry lang="co" key="IDC_USE_LEGACY_MAX_PASSWORD_LENGTH">Impiegà l’anziana longhezza massima di parolla d’intesa (64 caratteri)</entry>
+	    <entry lang="co" key="IDC_USE_LEGACY_MAX_PASSWORD_LENGTH">Impiegà l’anziana lunghezza massima di parolla d’intesa (64 caratteri)</entry>
 	    <entry lang="co" key="IDC_ENABLE_RAM_ENCRYPTION">Attivà a cifratura di e chjavi è di e parolle d’intesa piazzate in RAM</entry>
 	    <entry lang="co" key="IDT_BENCHMARK">Calibrera :</entry>
 	    <entry lang="co" key="IDC_DISABLE_MOUNT_MANAGER">Creà solu l’apparechju virtuale senza muntallu nant’à a lettera di lettore selezziunata</entry>
@@ -1665,6 +1667,47 @@ Information about Corsican localization:
 	    <entry lang="co" key="INSECURE_MODE">[MODU NONSICURU]</entry>
 	    <entry lang="co" key="IDC_DISABLE_SCREEN_PROTECTION">Disattivà a prutezzione contr’à e catture di screnu è l’arregistramentu di screnu</entry>
 	    <entry lang="co" key="DISABLE_SCREEN_PROTECTION_WARNING">AVERTIMENTU : A disattivazione di a prutezzione di screnu riduce forte a sicurità. Attivà st’ozzione SOLU s’è vo avete un bisognu specificu di catturà l’interfaccia di VeraCrypt. Què pò palisà i dati sensibile à l’attrezzi di screnu è à e funzioni d’arregistramentu di screnu cum’è Windows 11 Recall.</entry>
+	    <entry lang="co" key="MEMORY_COST">Costu di a memoria</entry>
+	    <entry lang="co" key="IDT_KDF_ALGO">Cudificazione KDF</entry>
+	    <entry lang="co" key="IDD_PREFERENCES_TAB_GENERAL">Generale</entry>
+	    <entry lang="co" key="IDD_PREFERENCES_TAB_ACTIONS">Azzioni</entry>
+	    <entry lang="co" key="IDD_PREFERENCES_TAB_PASSWORD">Parolla d’intesa</entry>
+	    <entry lang="co" key="IDC_SECURE_DESKTOP_ENABLE_IME">Attivà l’editore di metoda di stampittera (IME) in u scagnu sicuru</entry>
+	    <entry lang="co" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">AVERTIMENTU : Attivà st’ozzione solu s’è vo scuntrate prublemi quandu si selezziuneghja schedarii chjave o gettoni in u casu d’un scagnu sicuru.</entry>
+	    <entry lang="co" key="ERR_KEY_DERIVATION_FAILED">Fiascu di derivazione di a chjave. Què pò esse cagiunatu da mancanza di memoria o da un’operazione interrotta.</entry>
+	    <entry lang="co" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">A partizione o u lettore di u sistema hè dighjà dicifrata(u) ma u chjassu di u caricadore di piccera EFI da Microsoft ùn hè statu risturatu à u ghjestiunariu di piccera Windows. Solu i schedarii di piccera EFI richiede una riparazione. Impiegà l’ozzione di riparazione cù u discu di succorsu VeraCrypt o fà una piccera nant’à u medià di ricuperazione Windows è lancià « bcdboot W:\\Windows /s S: /f UEFI » dopu avè rimpiazzatu W: da a lettera di lettore di u vulume Windows eppò S: da a lettera di lettore di a partizione di u sistema EFI. Chjassu :</entry>
+	    <entry lang="co" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">A partizione o u lettore di u sistema hè dighjà dicifrata(u) ma u chjassu di u caricadore di piccera alternativu di ritornu EFI cuntene dighjà u caricadore di piccera VeraCrypt. Solu i schedarii di piccera EFI richiede una riparazione. Impiegà l’ozzione di riparazione cù u discu di succorsu VeraCrypt o fà una piccera nant’à u medià di ricuperazione Windows è lancià « bcdboot W:\\Windows /s S: /f UEFI » dopu avè rimpiazzatu W: da a lettera di lettore di u vulume Windows eppò S: da a lettera di lettore di a partizione di u sistema EFI. Chjassu :</entry>
+	    <entry lang="co" key="IDM_REPAIR_EFI_BOOT_LOADER">Riparazione di u caricadore di piccera EFI…</entry>
+	    <entry lang="co" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt hà da risturà i chjassi di u caricadore di piccera EFI da Windows è hà da caccià l’elementi di piccera EFI è i schedarii VeraCrypt.\n\nImpiegà què solu quandu a partizione o u lettore di u sistema hè dicifrata(u) sana(u) è chì Windows pò fà a piccera senza cifratura di u sistema.\n\nVulete cuntinuà ?</entry>
+	    <entry lang="co" key="EFI_BOOT_LOADER_FILE_READ_FAILED">Ùn si pò micca leghje cumpletamente u schedariu di u caricadore di piccera EFI :</entry>
+	    <entry lang="co" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">Ùn si pò micca ispettà u caricadore di piccera EFI perchè hè troppu maiò :</entry>
+	    <entry lang="co" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">A partizione o u lettore di u sistema hè dighjà dicifrata(u) è i schedarii di u caricadore di piccera EFI sò stati risturati ma VeraCrypt ùn pò caccià unu o più di i so elementi di microprugramma di piccera. I schedarii EFI di VeraCrypt sò stati lasciati in piazza è cusì tuttu elementu rimanente di microprugramma serà sempre assuciatu à un caricadore esistente. Pruvà torna da Amministratore o caccià l’elementu di piccera VeraCrypt da a cunfigurazione di u microprugramma dopu avè verificatu chì u ghjestiunariu di piccera Windows era lanciatu nurmalmente.</entry>
+	    <entry lang="co" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">Ùn si pò micca riparà u caricadore di piccera EFI quandu a cifratura o a dicifratura hè attiva o incumpleta. Compie o cuntinuà u trattamentu in attesa di cifratura o di dicifratura di u sistema prima di pruvà torna.</entry>
+	    <entry lang="co" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">St’azzione di riparazione hè dispunibule solu nant’à i sistemi chì facenu a piccera in modu UEFI à partesi d’una partizione di sistema GPT.</entry>
+	    <entry lang="co" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">U caricadore di piccera EFI hè statu riparatu currettamente.</entry>
+	    <entry lang="co" key="PIM_ARGON2_HELP">PIM (Multiplicatore d’Iterazioni Persunali) hè u valore chì cuntrolleghja i costi di memoria è di durata impiegati da a derivazione di a chjave d’intestatura Argon2id cusì :\n      Memoria = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterazioni = 3 + ((PIM - 1) / 3) per PIM 31 o inferiore, osinnò 13 + (PIM - 31)\n\nQuandu u campu hè viotu o definitu à 0, VeraCrypt impiegheghja u PIM predefinitu Argon2 (12), chì impiegheghja 416 Mio di memoria è 6 iterazioni.\n\nQuandu a parolla d’intesa hè menu longa chè 20 caratteri, u PIM Argon2 ùn pò micca esse inferiore à 12 per mantene un livellu minimu di sicurità.\nQuandu a parolla d’intesa hè omancu di 20 caratteri, u PIM pò esse definitu à un qualunque valore.\n\nUn valore PIM Argon2 più maiò chè 12 aumenteghja l’aghjovu di memoria fine à 1024 Mio eppò aumenteghja l’iterazioni. Què aumenterà a durata di muntatura. Un chjucu valore PIM Argon2 (menu chè 12) riducerà a durata di muntatura ma què pò riduce a sicurità s’è a parolla d’intesa ùn hè abbastanza forta.</entry>
+	    <entry lang="co" key="PIM_ARGON2_LARGE_WARNING">Avete sceltu un valore PIM Argon2 chì hè più maiò chè u valore predefinitu di VeraCrypt.\nSappiate chì què pò richiede più memoria è aumenterà a durata di muntatura.</entry>
+	    <entry lang="co" key="PIM_ARGON2_SMALL_WARNING">Avete sceltu un valore PIM Argon2 più chjucu chè u valore predefinitu di VeraCrypt. Sappiate chì, s’è a vostra parolla d’intesa ùn hè abbastanza forta, què pò riduce u livellu di sicurità.\n\nCunfirmate chì vò impiegate una parolla d’intesa forta ?</entry>
+	    <entry lang="co" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">A parolla d’intesa deve cuntene omancu 20 caratteri per pudè impiegà u valore PIM Argon2 specificatu.\nE parolle d’intesa più corte ponu solu esse impiegate s’è u PIM Argon2 hè uguale à 12 o superiore.</entry>
+	    <entry lang="co" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Muntà i vulumi NTFS cù u pilotu ntfs3 di u nocciulu Linux</entry>
+	    <entry lang="co" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Solu Linux. Quandu st’ozzione hè attivata, VeraCrypt esamineghja l’apparechju virtuale dicifratu cù « blkid -p » è munta i sistemi di schedarii NTFS scuperti cù ntfs3 invece di u terminale NTFS predefinitu. S’è a scuperta NTFS ùn riesce, VeraCrypt impiegheghja a selezzione autumatica nurmale di sistema di schedarii. S’è ntfs3 hè indispunibule, o bluccatu da a distribuzione, a muntatura pò fiascà. St’ozzione d’accettazione pò evità i blucchime d’interruzzione o d’invernazione cagiunati da sistemi di schedarii FUSE cù spaziu d’utilizatore senza risposta.</entry>
+	    <entry lang="co" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Fiascu di a smuntatura nurmale di u vulume {0}. Què pò accade quandu qualchì appiecazione hà sempre schedarii o cartulari aperti nant’à u vulume, o quandu l’apparechju di salvaguardia hè statu discunnessu è chì a muntatura hè diventata instabile.\n\nS’è l’apparechju hè sempre cunnessu, sceglie Nò, chjode l’appiecazioni chì impieganu u vulume è pruvà torna à smuntallu.\n\nS’è l’apparechju hè statu discunnessu o s’è a muntatura hè instabile, VeraCrypt pò fà un tentativu di nettata d’urgenza stacchendu u sistema di schedarii di manera attimpata è cacciendu - o pianificà a cacciatura di - l’oggetti di u nocciulu VeraCrypt. E scritture in attesa ponu esse fiascate, i dati ponu esse persi, è a nettata pò stà in attesa fin’à ciò chì l’appiecazioni chjodinu i schedarii aperti. Verificà u sistema di schedarii cù « fsck » o cù l’attrezzu di riparazione adequatu prima d’impiegallu torna.\n\nCuntinuà ?</entry>
+	    <entry lang="co" key="LINUX_EMERGENCY_UNMOUNTED">A nettata d’urgenza per u vulume {0} hè stata lanciata. S’è u vulume hè statu discunnessu, o a muntatura era instabile, o ancu ci era scritture in attesa, verificà u sistema di schedarii cù « fsck » o cù l’attrezzu di riparazione adequatu prima d’impiegallu torna.</entry>
+	    <entry lang="co" key="FORMAT_STAGE_WRITING_DATA">Creazione di i dati di u vulume. Aspittate per piacè.</entry>
+	    <entry lang="co" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Cumpiimentu di a creazione di u vulume : scrittura di l’intestatura di a salvaguardia.</entry>
+	    <entry lang="co" key="FORMAT_STAGE_FLUSHING_DATA">Cumpiimentu di a creazione di u vulume : viutatura di i dati nant’à u discu. St’azzione pò piglià parechji minuti nant’à i vulumi maiò o nant’à una memoria lenta o USB.</entry>
+	    <entry lang="co" key="FORMAT_STAGE_FINISHED">Cumpiimentu di a creazione di u vulume.</entry>
+	    <entry lang="co" key="FORMAT_STAGE_ABORTED">A creazione di u vulume hè stata interrotta.</entry>
+	    <entry lang="co" key="FORMAT_STAGE_ERROR">Fiascu di a creazione di u vulume.</entry>
+	    <entry lang="co" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Cumpiimentu di a creazione di u vulume : muntatura di u vulume timpurariu.</entry>
+	    <entry lang="co" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Cumpiimentu di a creazione di u vulume : appruntata di l’apparechju timpurariu.</entry>
+	    <entry lang="co" key="FORMAT_STAGE_CREATING_FILESYSTEM">Cumpiimentu di a creazione di u vulume : creazione di u sistema di schedarii impieghendu {0}.</entry>
+	    <entry lang="co" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Cumpiimentu di a creazione di u vulume : smuntatura di u vulume timpurariu.</entry>
+	    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+	    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+	    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+	    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+	    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
 	</localization>
 	<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
 		<xs:element name="VeraCrypt">

Translations/Language.cs.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="cs" name="Čeština" en-name="Czech" version="1.3.0" translators="Vítek Moser, Lagardere" />
     <font lang="cs" class="normal" size="11" face="default" />
     <font lang="cs" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="cs" key="IDT_NEW_PASSWORD">Heslo:</entry>
     <entry lang="cs" key="IDT_PARALLELIZATION_OPTIONS">Paralelizace založená na vláknech</entry>
     <entry lang="cs" key="IDT_PKCS11_LIB_PATH">PKCS #11 cesta ke knihovně</entry>
-    <entry lang="cs" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="cs" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="cs" key="IDT_KDF">KDF:</entry>
+    <entry lang="cs" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="cs" key="IDT_PW_CACHE_OPTIONS">Mezipaměť pro hesla</entry>
     <entry lang="cs" key="IDT_SECURITY_OPTIONS">Možnosti zabezpečení</entry>
     <entry lang="en" key="IDT_EMV_OPTIONS">EMV Options</entry>
@@ -813,7 +813,7 @@
     <entry lang="cs" key="SECONDARY_KEY_SIZE_LRW">Velikost vylepšeného klíče (režim LRW)</entry>
     <entry lang="cs" key="BITS">bitů</entry>
     <entry lang="cs" key="BLOCK_SIZE">Velikost bloku</entry>
-    <entry lang="cs" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="cs" key="KDF">KDF</entry>
     <entry lang="cs" key="PKCS5_ITERATIONS">PKCS-5 počet iterací</entry>
     <entry lang="cs" key="VOLUME_CREATE_DATE">Diskový oddíl byl vytvořen</entry>
     <entry lang="cs" key="VOLUME_HEADER_DATE">Hlavička byla naposledy změněna</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="cs" key="INSECURE_MODE">[NEZABEZPEČENÝ REŽIM]</entry>
     <entry lang="cs" key="IDC_DISABLE_SCREEN_PROTECTION">Zakázat ochranu proti snímkům obrazovky a záznamu obrazovky</entry>
     <entry lang="cs" key="DISABLE_SCREEN_PROTECTION_WARNING">UPOZORNĚNÍ: Vypnutí ochrany obrazovky výrazně snižuje úroveň zabezpečení. Tuto možnost povolte POUZE v případě, že potřebujete konkrétně zachytit rozhraní VeraCryptu. Toto nastavení může vystavit citlivá data nástrojům pro snímání obrazovky a funkcím pro záznam obrazovky, jako je například Windows 11 Recall.</entry>
+    <entry lang="cs" key="MEMORY_COST">Paměťová náročnost</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.da.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="da" name="Dansk" en-name="Danish" version="0.1.0" translators="Lasse Bond" />
     <font lang="da" class="normal" size="11" face="default" />
     <font lang="da" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="da" key="IDT_NEW_PASSWORD">Kodeord:</entry>
     <entry lang="en" key="IDT_PARALLELIZATION_OPTIONS">Thread-Based Parallelization</entry>
     <entry lang="en" key="IDT_PKCS11_LIB_PATH">PKCS #11 Library Path</entry>
-    <entry lang="da" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="en" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="da" key="IDT_KDF">KDF:</entry>
+    <entry lang="en" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="da" key="IDT_PW_CACHE_OPTIONS">Kodeords hukommelse</entry>
     <entry lang="en" key="IDT_SECURITY_OPTIONS">Security Options</entry>
     <entry lang="en" key="IDT_EMV_OPTIONS">EMV Options</entry>
@@ -813,7 +813,7 @@
     <entry lang="da" key="SECONDARY_KEY_SIZE_LRW">Klemt Nøgle Størrelse (LRW Tilstand)</entry>
     <entry lang="da" key="BITS">bits</entry>
     <entry lang="da" key="BLOCK_SIZE">Blok størrelse</entry>
-    <entry lang="da" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="da" key="KDF">KDF</entry>
     <entry lang="da" key="PKCS5_ITERATIONS">PKCS-5 gentagelse talt</entry>
     <entry lang="da" key="VOLUME_CREATE_DATE">Bind oprettet</entry>
     <entry lang="da" key="VOLUME_HEADER_DATE">Etiket sidst ændret</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="en" key="INSECURE_MODE">[INSECURE MODE]</entry>
     <entry lang="en" key="IDC_DISABLE_SCREEN_PROTECTION">Disable protection against screenshots and screen recording</entry>
     <entry lang="en" key="DISABLE_SCREEN_PROTECTION_WARNING">WARNING: Disabling screen protection significantly reduces security. Enable this option ONLY if you have a specific need to capture VeraCrypt's interface. This may expose sensitive data to screenshot tools and screen recording features such as Windows 11 Recall.</entry>
+    <entry lang="en" key="MEMORY_COST">Memory Cost</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.de.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <!-- Sprachen -->
     <language langid="de" name="Deutsch" en-name="German" version="1.1.8" translators="Harry Haller, Alexander Schorg, Simon Frankenberger, David Arndt, H. Sauer, Dulla, Ettore Atalan, Matthias Kolja Miehl, Felix Reichmann, Bernhard Erdmann" />
     <!-- Schriftarten -->
@@ -11,9 +11,9 @@
     <!-- Steuerelemente  -->
     <entry lang="de" key="IDCANCEL">Abbrechen</entry>
     <entry lang="de" key="IDC_ALL_USERS">Für &amp;alle Benutzer installieren</entry>
-    <entry lang="de" key="IDC_BROWSE">Su&amp;chen ...</entry>
+    <entry lang="de" key="IDC_BROWSE">Su&amp;chen...</entry>
     <entry lang="de" key="IDC_DESKTOP_ICON">VeraCrypt-Symbol auf dem &amp;Desktop erstellen</entry>
-    <entry lang="de" key="IDC_DONATE">Jetzt spenden ...</entry>
+    <entry lang="de" key="IDC_DONATE">Jetzt spenden...</entry>
     <entry lang="de" key="IDC_FILE_TYPE">Verknüpft die &amp;Dateierweiterung .hc mit VeraCrypt</entry>
     <entry lang="de" key="IDC_OPEN_CONTAINING_FOLDER">&amp;Den Speicherort nach dem Beenden öffnen</entry>
     <entry lang="de" key="IDC_PROG_GROUP">VeraCrypt ins &amp;Startmenü eintragen</entry>
@@ -28,8 +28,8 @@
     <entry lang="de" key="IDT_INSTALL_DESTINATION">Geben Sie das Zielverzeichnis für die Installation der Programmdateien von VeraCrypt an. Falls das Zielverzeichnis nicht existiert, wird es automatisch beim Entpacken angelegt.</entry>
     <entry lang="de" key="IDT_UNINSTALL_DIR">Klicken Sie auf „Deinstallieren“, um VeraCrypt von diesem System zu entfernen.</entry>
     <entry lang="de" key="IDC_ABORT_BUTTON">Abbrechen</entry>
-    <entry lang="de" key="IDC_BENCHMARK">&amp;Benchmark ...</entry>
-    <entry lang="de" key="IDC_CIPHER_TEST">&amp;Test ...</entry>
+    <entry lang="de" key="IDC_BENCHMARK">&amp;Benchmark...</entry>
+    <entry lang="de" key="IDC_CIPHER_TEST">&amp;Test...</entry>
     <entry lang="de" key="IDC_DEVICE_TRANSFORM_MODE_FORMAT">Verschlüsseltes Volume erstellen und formatieren</entry>
     <entry lang="de" key="IDC_DEVICE_TRANSFORM_MODE_INPLACE">Partition „in-place“ verschlüsseln</entry>
     <entry lang="de" key="IDC_DISPLAY_KEYS">Erstellte Schlüssel anzeigen (deren Teile)</entry>
@@ -47,7 +47,7 @@
     <entry lang="de" key="IDC_KEYFILES_ENABLE">Schlüsselda&amp;t. verwenden</entry>
     <entry lang="de" key="IDC_KEYFILES_TRY_EMPTY_PASSWORD">Einhängen zuerst ohne Passwort versuchen</entry>
     <entry lang="de" key="IDC_KEYFILES_RANDOM_SIZE">Zufällige Größe (64 &lt;-&gt; 1048576 Bytes)</entry>
-    <entry lang="de" key="IDC_KEY_FILES">Schlüsselda&amp;teien ...</entry>
+    <entry lang="de" key="IDC_KEY_FILES">Schlüsselda&amp;teien...</entry>
     <entry lang="de" key="IDC_LINK_HASH_INFO">Infos über Hash-Algorithmen</entry>
     <entry lang="de" key="IDC_LINK_MORE_INFO_ABOUT_CIPHER">Weitere Informationen</entry>
     <entry lang="de" key="IDC_LINK_PIM_INFO">Informationen zu PIM</entry>
@@ -111,15 +111,15 @@
     <entry lang="de" key="IDC_AUTORUN_START">&amp;VeraCrypt starten</entry>
     <entry lang="de" key="IDC_AUTO_DETECT_PKCS11_MODULE">Bibliothek auto&amp;matisch erkennen</entry>
     <entry lang="de" key="IDC_BOOT_LOADER_CACHE_PASSWORD">&amp;Pre-Boot-Authentifikationspasswort in den Treibercache schreiben (zum Einhängen von Nicht-System-Volumes)</entry>
-    <entry lang="de" key="IDC_BROWSE_DIRS">Durchsuchen ...</entry>
-    <entry lang="de" key="IDC_BROWSE_FILES">Durchsuchen ...</entry>
+    <entry lang="de" key="IDC_BROWSE_DIRS">Durchsuchen...</entry>
+    <entry lang="de" key="IDC_BROWSE_FILES">Durchsuchen...</entry>
     <entry lang="de" key="IDC_CACHE">Passwort und Schlüsseldatei im &amp;Cache halten</entry>
     <entry lang="de" key="IDC_CLOSE_BKG_TASK_WHEN_NOVOL">&amp;Beenden, wenn alle Volumes getrennt wurden</entry>
     <entry lang="de" key="IDC_CLOSE_TOKEN_SESSION_AFTER_MOUNT">Token-&amp;Sitzung schließen, nachdem ein Volume erfolgreich eingehängt wurde</entry>
     <entry lang="de" key="IDC_COPY_EXPANDER">Volume-Erweiterer hinzufügen</entry>
     <entry lang="de" key="IDC_COPY_WIZARD">Assistenten für die Erstellung von VeraCrypt-Volumes hinzufügen</entry>
     <entry lang="de" key="IDC_CREATE">Erstellen</entry>
-    <entry lang="de" key="IDC_CREATE_VOLUME">Volume &amp;erstellen ...</entry>
+    <entry lang="de" key="IDC_CREATE_VOLUME">Volume &amp;erstellen...</entry>
     <entry lang="de" key="IDC_DISABLE_BOOT_LOADER_OUTPUT">Keine Texte im Pre-Boot-Authentifikationsbildschirm &amp;anzeigen (außer die unten definierte Nachricht)</entry>
     <entry lang="de" key="IDC_DISABLE_EVIL_MAID_ATTACK_DETECTION">Erkennung von „Evil Maid“-Angriffen deaktivieren</entry>
     <entry lang="de" key="IDC_ENABLE_HARDWARE_ENCRYPTION">AES-Verschlüsselung durch Nutzung der AES-Befehle des Prozessors beschleunigen (falls unterstützt)</entry>
@@ -146,15 +146,15 @@
     <entry lang="de" key="IDC_HK_MOD_WIN">Win</entry>
     <entry lang="de" key="IDC_HOTKEY_ASSIGN">Zuweisen</entry>
     <entry lang="de" key="IDC_HOTKEY_REMOVE">Aufheben</entry>
-    <entry lang="de" key="IDC_KEYFILES">&amp;Schlüsseldateien ...</entry>
+    <entry lang="de" key="IDC_KEYFILES">&amp;Schlüsseldateien...</entry>
     <entry lang="de" key="IDC_LIMIT_ENC_THREAD_POOL">Diese Anzahl von logischen Prozessoren nicht für Ver- und Entschlüsselung nutzen:</entry>
     <entry lang="de" key="IDC_MORE_INFO_ON_HW_ACCELERATION">Mehr Informationen</entry>
     <entry lang="de" key="IDC_MORE_INFO_ON_THREAD_BASED_PARALLELIZATION">Mehr Informationen</entry>
     <entry lang="de" key="IDC_MORE_SETTINGS">Mehr Einstellungen »</entry>
-    <entry lang="de" key="IDC_MOUNTALL">&amp;Alle Datentr. einhängen ...</entry>
-    <entry lang="de" key="IDC_MOUNT_OPTIONS">&amp;Optionen ...</entry>
+    <entry lang="de" key="IDC_MOUNTALL">&amp;Automatisch einhängen...</entry>
+    <entry lang="de" key="IDC_MOUNT_OPTIONS">&amp;Optionen...</entry>
     <entry lang="de" key="IDC_MOUNT_READONLY">Als schreib&amp;geschütztes Laufwerk einhängen</entry>
-    <entry lang="de" key="IDC_NEW_KEYFILES">Schlüssel&amp;dateien ...</entry>
+    <entry lang="de" key="IDC_NEW_KEYFILES">Schlüssel&amp;dateien...</entry>
     <entry lang="de" key="IDC_OLD_PIM_HELP">(Leer oder 0 für vordefinierte Iterationen)</entry>
     <entry lang="de" key="IDC_PIM_HELP">(Leer oder 0 für vordefinierte Iterationen)</entry>
     <entry lang="de" key="IDC_PREF_BKG_TASK_ENABLE">&amp;Aktiv</entry>
@@ -176,16 +176,16 @@
     <entry lang="de" key="IDC_PREF_WIPE_CACHE_ON_EXIT">Cache beim Beenden sicher &amp;löschen</entry>
     <entry lang="de" key="IDC_PRESERVE_TIMESTAMPS">Änderungszeiten von Containerdateien erhalten</entry>
     <entry lang="de" key="IDC_RESET_HOTKEYS">Zu&amp;rücksetzen</entry>
-    <entry lang="de" key="IDC_SELECT_DEVICE">Datent&amp;räger ...</entry>
-    <entry lang="de" key="IDC_SELECT_FILE">&amp;Datei ...</entry>
-    <entry lang="de" key="IDC_SELECT_PKCS11_MODULE">&amp;Bibliothek wählen ...</entry>
+    <entry lang="de" key="IDC_SELECT_DEVICE">Datent&amp;räger...</entry>
+    <entry lang="de" key="IDC_SELECT_FILE">&amp;Datei...</entry>
+    <entry lang="de" key="IDC_SELECT_PKCS11_MODULE">&amp;Bibliothek wählen...</entry>
     <entry lang="de" key="IDC_SHOW_PASSWORD_CHPWD_NEW">Passwort anze&amp;igen</entry>
     <entry lang="de" key="IDC_SHOW_PASSWORD_CHPWD_ORI">Passwort an&amp;zeigen</entry>
     <entry lang="de" key="IDC_TRAVEL_OPEN_EXPLORER">&amp;Explorer-Fenster für eingehängtes Volume öffnen</entry>
     <entry lang="de" key="IDC_TRAV_CACHE_PASSWORDS">Passwort im Cache halten</entry>
     <entry lang="de" key="IDC_TRUECRYPT_MODE">&amp;TrueCrypt-Modus</entry>
     <entry lang="de" key="IDC_UNMOUNTALL">A&amp;lle Datenträger trennen</entry>
-    <entry lang="de" key="IDC_VOLUME_PROPERTIES">Eigenscha&amp;ften ...</entry>
+    <entry lang="de" key="IDC_VOLUME_PROPERTIES">Eigenscha&amp;ften...</entry>
     <entry lang="de" key="IDC_VOLUME_TOOLS">Volume-&amp;Operationen »</entry>
     <entry lang="de" key="IDC_WIPE_CACHE">&amp;Cache sicher löschen</entry>
     <entry lang="de" key="IDD_DEFAULT_MOUNT_PARAMETERS">VeraCrypt – Parameter beim Einhängen</entry>
@@ -201,71 +201,71 @@
     <entry lang="de" key="IDD_TRAVELER_DLG">VeraCrypt Traveler-Disk-Installation</entry>
     <entry lang="de" key="IDD_VOLUME_PROPERTIES">Eigenschaften des VeraCrypt-Volumes</entry>
     <entry lang="de" key="IDM_ABOUT">&amp;Info über VeraCrypt</entry>
-    <entry lang="de" key="IDM_ADD_REMOVE_VOL_KEYFILES">Schlüssel&amp;dateien dem/vom Volume hinzufügen/entfernen ...</entry>
-    <entry lang="de" key="IDM_ADD_VOLUME_TO_FAVORITES">Eingehängtes Volume zu Favoriten hinzufügen ...</entry>
-    <entry lang="de" key="IDM_ADD_VOLUME_TO_SYSTEM_FAVORITES">Eingehängtes Volume zu Systemfavoriten hinzufügen ...</entry>
-    <entry lang="de" key="IDM_ANALYZE_SYSTEM_CRASH">Einen Systemabsturz analysieren ...</entry>
-    <entry lang="de" key="IDM_BACKUP_VOL_HEADER">Volume-Kopfdaten s&amp;ichern ...</entry>
-    <entry lang="de" key="IDM_BENCHMARK">&amp;Benchmark-Test ...</entry>
-    <entry lang="de" key="IDM_CHANGE_HEADER_KEY_DERIV_ALGO">Algorithmus für &amp;Kopfdatenschlüsselberechnung ändern ...</entry>
-    <entry lang="de" key="IDM_CHANGE_PASSWORD">Volume-&amp;Passwort ändern ...</entry>
-    <entry lang="de" key="IDM_CHANGE_SYS_HEADER_KEY_DERIV_ALGO">Algorithmus für Kopfdatenschlüsselberechnung ändern ...</entry>
-    <entry lang="de" key="IDM_CHANGE_SYS_PASSWORD">Passwort ändern ...</entry>
+    <entry lang="de" key="IDM_ADD_REMOVE_VOL_KEYFILES">Schlüssel&amp;dateien dem/vom Volume hinzufügen/entfernen...</entry>
+    <entry lang="de" key="IDM_ADD_VOLUME_TO_FAVORITES">Eingehängtes Volume zu Favoriten hinzufügen...</entry>
+    <entry lang="de" key="IDM_ADD_VOLUME_TO_SYSTEM_FAVORITES">Eingehängtes Volume zu Systemfavoriten hinzufügen...</entry>
+    <entry lang="de" key="IDM_ANALYZE_SYSTEM_CRASH">Einen Systemabsturz analysieren...</entry>
+    <entry lang="de" key="IDM_BACKUP_VOL_HEADER">Volume-Kopfdaten s&amp;ichern...</entry>
+    <entry lang="de" key="IDM_BENCHMARK">&amp;Benchmark-Test...</entry>
+    <entry lang="de" key="IDM_CHANGE_HEADER_KEY_DERIV_ALGO">Algorithmus für &amp;Kopfdatenschlüsselberechnung ändern...</entry>
+    <entry lang="de" key="IDM_CHANGE_PASSWORD">Volume-&amp;Passwort ändern...</entry>
+    <entry lang="de" key="IDM_CHANGE_SYS_HEADER_KEY_DERIV_ALGO">Algorithmus für Kopfdatenschlüsselberechnung ändern...</entry>
+    <entry lang="de" key="IDM_CHANGE_SYS_PASSWORD">Passwort ändern...</entry>
     <entry lang="de" key="IDM_CLEAR_HISTORY">Volume-Ve&amp;rlauf löschen</entry>
     <entry lang="de" key="IDM_CLOSE_ALL_TOKEN_SESSIONS">Alle Sicherheitstoken-Sitzungen schließen</entry>
     <entry lang="de" key="IDM_CONTACT">&amp;Kontakt</entry>
-    <entry lang="de" key="IDM_CREATE_HIDDEN_OS">Verstecktes Betriebssystem erstellen ...</entry>
-    <entry lang="de" key="IDM_CREATE_RESCUE_DISK">Rettungsdatenträger erstellen ...</entry>
-    <entry lang="de" key="IDM_CREATE_VOLUME">&amp;Neues Volume erstellen ...</entry>
-    <entry lang="de" key="IDM_DECRYPT_NONSYS_VOL">Dauerhaft entschlüsseln ...</entry>
-    <entry lang="de" key="IDM_DEFAULT_KEYFILES">&amp;Standardschlüsseldateien ...</entry>
-    <entry lang="de" key="IDM_DEFAULT_MOUNT_PARAMETERS">Standardparameter beim Einhängen ...</entry>
-    <entry lang="de" key="IDM_DONATE">Jetzt spenden ...</entry>
-    <entry lang="de" key="IDM_ENCRYPT_SYSTEM_DEVICE">Systempartition/Systemlaufwerk verschlüsseln ...</entry>
+    <entry lang="de" key="IDM_CREATE_HIDDEN_OS">Verstecktes Betriebssystem erstellen...</entry>
+    <entry lang="de" key="IDM_CREATE_RESCUE_DISK">Rettungsdatenträger erstellen...</entry>
+    <entry lang="de" key="IDM_CREATE_VOLUME">&amp;Neues Volume erstellen...</entry>
+    <entry lang="de" key="IDM_DECRYPT_NONSYS_VOL">Dauerhaft entschlüsseln...</entry>
+    <entry lang="de" key="IDM_DEFAULT_KEYFILES">&amp;Standardschlüsseldateien...</entry>
+    <entry lang="de" key="IDM_DEFAULT_MOUNT_PARAMETERS">Standardparameter beim Einhängen...</entry>
+    <entry lang="de" key="IDM_DONATE">Jetzt spenden...</entry>
+    <entry lang="de" key="IDM_ENCRYPT_SYSTEM_DEVICE">Systempartition/Systemlaufwerk verschlüsseln...</entry>
     <entry lang="de" key="IDM_FAQ">Häufig gestellte &amp;Fragen (FAQ)</entry>
     <entry lang="de" key="IDM_HELP">&amp;Benutzerhandbuch</entry>
     <entry lang="de" key="IDM_HOMEPAGE">Webseite</entry>
-    <entry lang="de" key="IDM_HOTKEY_SETTINGS">&amp;Tastenkombinationen ...</entry>
-    <entry lang="de" key="IDM_KEYFILE_GENERATOR">&amp;Schlüsseldatei(en) erstellen ...</entry>
-    <entry lang="de" key="IDM_LANGUAGE">&amp;Sprache ...</entry>
+    <entry lang="de" key="IDM_HOTKEY_SETTINGS">&amp;Tastenkombinationen...</entry>
+    <entry lang="de" key="IDM_KEYFILE_GENERATOR">&amp;Schlüsseldatei(en) erstellen...</entry>
+    <entry lang="de" key="IDM_LANGUAGE">&amp;Sprache...</entry>
     <entry lang="de" key="IDM_LICENSE">&amp;Lizenzvereinbarung</entry>
-    <entry lang="de" key="IDM_MANAGE_TOKEN_KEYFILES">Sicherheitstoken-Schlüsseldateien verwalten ...</entry>
-    <entry lang="de" key="IDM_MOUNTALL">&amp;Alle Datenträger-Volumes automatisch einhängen ...</entry>
+    <entry lang="de" key="IDM_MANAGE_TOKEN_KEYFILES">Sicherheitstoken-Schlüsseldateien verwalten...</entry>
+    <entry lang="de" key="IDM_MOUNTALL">&amp;Alle Datenträger-Volumes automatisch einhängen...</entry>
     <entry lang="de" key="IDM_MOUNT_FAVORITE_VOLUMES">&amp;Favoriten einhängen</entry>
-    <entry lang="de" key="IDM_MOUNT_SYSENC_PART_WITHOUT_PBA">Ohne Pre-Boot-&amp;Authentifikation einhängen ...</entry>
-    <entry lang="de" key="IDM_MOUNT_VOLUME">Volume &amp;einhängen ...</entry>
-    <entry lang="de" key="IDM_MOUNT_VOLUME_OPTIONS">Volume einhängen (mit &amp;Optionen) ...</entry>
+    <entry lang="de" key="IDM_MOUNT_SYSENC_PART_WITHOUT_PBA">Ohne Pre-Boot-&amp;Authentifikation einhängen...</entry>
+    <entry lang="de" key="IDM_MOUNT_VOLUME">Volume &amp;einhängen...</entry>
+    <entry lang="de" key="IDM_MOUNT_VOLUME_OPTIONS">Volume einhängen (mit &amp;Optionen)...</entry>
     <entry lang="de" key="IDM_NEWS">&amp;Neuigkeiten</entry>
     <entry lang="de" key="IDM_ONLINE_HELP">Online-&amp;Hilfe</entry>
     <entry lang="de" key="IDM_ONLINE_TUTORIAL">&amp;Anleitung für Anfänger</entry>
-    <entry lang="de" key="IDM_ORGANIZE_FAVORITES">Favoriten-Volume-Einstellungen ...</entry>
-    <entry lang="de" key="IDM_ORGANIZE_SYSTEM_FAVORITES">Systemfavoriten-Volume-Einstellungen ...</entry>
-    <entry lang="de" key="IDM_PERFORMANCE_SETTINGS">Leistung/Treiberkonfiguration ...</entry>
+    <entry lang="de" key="IDM_ORGANIZE_FAVORITES">Favoriten-Volume-Einstellungen...</entry>
+    <entry lang="de" key="IDM_ORGANIZE_SYSTEM_FAVORITES">Systemfavoriten-Volume-Einstellungen...</entry>
+    <entry lang="de" key="IDM_PERFORMANCE_SETTINGS">Leistung/Treiberkonfiguration...</entry>
     <entry lang="de" key="IDM_PERMANENTLY_DECRYPT_SYS">Systempartition/Systemlaufwerk dauerhaft entschlüsseln</entry>
-    <entry lang="de" key="IDM_PREFERENCES">&amp;Voreinstellungen ...</entry>
+    <entry lang="de" key="IDM_PREFERENCES">&amp;Voreinstellungen...</entry>
     <entry lang="de" key="IDM_REFRESH_DRIVE_LETTERS">&amp;Laufwerksbuchstaben aktualisieren</entry>
-    <entry lang="de" key="IDM_REMOVE_ALL_KEYFILES_FROM_VOL">&amp;Alle Schlüsseldateien vom Volume entfernen ...</entry>
-    <entry lang="de" key="IDM_RESTORE_VOL_HEADER">Volume-Kopfdaten &amp;wiederherstellen ...</entry>
+    <entry lang="de" key="IDM_REMOVE_ALL_KEYFILES_FROM_VOL">&amp;Alle Schlüsseldateien vom Volume entfernen...</entry>
+    <entry lang="de" key="IDM_RESTORE_VOL_HEADER">Volume-Kopfdaten &amp;wiederherstellen...</entry>
     <entry lang="de" key="IDM_RESUME_INTERRUPTED_PROC">Unterbrochenen Prozess fortsetzen</entry>
-    <entry lang="de" key="IDM_SELECT_DEVICE">Datent&amp;räger oder Partition auswählen ...</entry>
-    <entry lang="de" key="IDM_SELECT_FILE">&amp;Datei auswählen ...</entry>
+    <entry lang="de" key="IDM_SELECT_DEVICE">Datent&amp;räger oder Partition auswählen...</entry>
+    <entry lang="de" key="IDM_SELECT_FILE">&amp;Datei auswählen...</entry>
     <entry lang="de" key="IDM_SYSENC_RESUME">Unterbrochenen Prozess fortsetzen</entry>
-    <entry lang="de" key="IDM_SYSENC_SETTINGS">Systemverschlüsselung ...</entry>
-    <entry lang="de" key="IDM_SYSTEM_ENCRYPTION_STATUS">Eigenschaften ...</entry>
-    <entry lang="de" key="IDM_SYS_ENC_SETTINGS">Einstellungen ...</entry>
-    <entry lang="de" key="IDM_SYS_FAVORITES_SETTINGS">Systemfavoriten-Volumes ...</entry>
+    <entry lang="de" key="IDM_SYSENC_SETTINGS">Systemverschlüsselung...</entry>
+    <entry lang="de" key="IDM_SYSTEM_ENCRYPTION_STATUS">Eigenschaften...</entry>
+    <entry lang="de" key="IDM_SYS_ENC_SETTINGS">Einstellungen...</entry>
+    <entry lang="de" key="IDM_SYS_FAVORITES_SETTINGS">Systemfavoriten-Volumes...</entry>
     <entry lang="de" key="IDM_TC_DOWNLOADS">&amp;Downloads</entry>
-    <entry lang="de" key="IDM_TEST_VECTORS">&amp;Testvektoren ...</entry>
-    <entry lang="de" key="IDM_TOKEN_PREFERENCES">Sicherheitstokens ...</entry>
-    <entry lang="de" key="IDM_TRAVELER">Traveler-Disk-Installation ...</entry>
+    <entry lang="de" key="IDM_TEST_VECTORS">&amp;Testvektoren...</entry>
+    <entry lang="de" key="IDM_TOKEN_PREFERENCES">Sicherheitstokens...</entry>
+    <entry lang="de" key="IDM_TRAVELER">Traveler-Disk-Installation...</entry>
     <entry lang="de" key="IDM_UNMOUNTALL">A&amp;lle Volumes trennen</entry>
     <entry lang="de" key="IDM_UNMOUNT_VOLUME">Volume &amp;trennen</entry>
     <entry lang="de" key="IDM_VERIFY_RESCUE_DISK">Rettungsdatenträger überprüfen</entry>
     <entry lang="de" key="IDM_VERIFY_RESCUE_DISK_ISO">ISO-Abbild vom Rettungsdatenträger überprüfen</entry>
     <entry lang="de" key="IDM_VERSION_HISTORY">&amp;Versionsverlauf</entry>
-    <entry lang="de" key="IDM_VOLUME_EXPANDER">Volume-Erweiterer ...</entry>
+    <entry lang="de" key="IDM_VOLUME_EXPANDER">Volume-Erweiterer...</entry>
     <entry lang="de" key="IDM_VOLUME_PROPERTIES">E&amp;igenschaften des VeraCrypt-Volumes</entry>
-    <entry lang="de" key="IDM_VOLUME_WIZARD">VeraCrypt-Volume &amp;erstellen ...</entry>
+    <entry lang="de" key="IDM_VOLUME_WIZARD">VeraCrypt-Volume &amp;erstellen...</entry>
     <entry lang="de" key="IDM_WEBSITE">VeraCrypt-&amp;Webseite</entry>
     <entry lang="de" key="IDM_WIPE_CACHE">&amp;Passwort-Cache sicher löschen</entry>
     <entry lang="de" key="IDOK">OK</entry>
@@ -294,8 +294,8 @@
     <entry lang="de" key="IDT_NEW_PASSWORD">Passwort:</entry>
     <entry lang="de" key="IDT_PARALLELIZATION_OPTIONS">Thread-basierte Parallelisierung</entry>
     <entry lang="de" key="IDT_PKCS11_LIB_PATH">Pfad der PKCS #11-Bibliothek</entry>
-    <entry lang="de" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="de" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="de" key="IDT_KDF">KDF:</entry>
+    <entry lang="de" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="de" key="IDT_PW_CACHE_OPTIONS">Passwort-Cache (im Speicher des VeraCrypt-Treibers)</entry>
     <entry lang="de" key="IDT_SECURITY_OPTIONS">Sicherheitsoptionen</entry>
     <entry lang="de" key="IDT_EMV_OPTIONS">EMV-Optionen</entry>
@@ -305,18 +305,18 @@
     <entry lang="de" key="IDT_TRAVEL_ROOT">Traveler-Disk-Dateien erstellen in (Traveler-Disk-Stammverzeichnis):</entry>
     <entry lang="de" key="IDT_VOLUME">Volume</entry>
     <entry lang="de" key="IDT_WINDOWS_RELATED_SETTING">Windows</entry>
-    <entry lang="de" key="IDC_ADD_KEYFILE_PATH">&amp;Pfad ...</entry>
+    <entry lang="de" key="IDC_ADD_KEYFILE_PATH">&amp;Pfad...</entry>
     <entry lang="de" key="IDC_AUTO">&amp;Autotest für alle</entry>
     <entry lang="de" key="IDC_CONTINUE">&amp;Fortsetzen</entry>
     <entry lang="de" key="IDC_DECRYPT">&amp;Entschlüsseln</entry>
     <entry lang="de" key="IDC_DELETE">&amp;Löschen</entry>
     <entry lang="de" key="IDC_ENCRYPT">&amp;Verschlüsseln</entry>
-    <entry lang="de" key="IDC_EXPORT">&amp;Exportieren ...</entry>
-    <entry lang="de" key="IDC_GENERATE_AND_SAVE_KEYFILE">Schlüsseldatei(en) &amp;erstellen u. speichern ...</entry>
-    <entry lang="de" key="IDC_GENERATE_KEYFILE">Schlüsseldatei(en) &amp;erstellen ...</entry>
+    <entry lang="de" key="IDC_EXPORT">&amp;Exportieren...</entry>
+    <entry lang="de" key="IDC_GENERATE_AND_SAVE_KEYFILE">Schlüsseldatei(en) &amp;erstellen u. speichern...</entry>
+    <entry lang="de" key="IDC_GENERATE_KEYFILE">Schlüsseldatei(en) &amp;erstellen...</entry>
     <entry lang="de" key="IDC_GET_LANG_PACKS">Sprachpaket herunterladen</entry>
     <entry lang="de" key="IDC_HW_AES_LABEL_LINK">Hardwarebeschleunigtes AES:</entry>
-    <entry lang="de" key="IDC_IMPORT_KEYFILE">&amp;Schlüsseldateien auf den Token importieren ...</entry>
+    <entry lang="de" key="IDC_IMPORT_KEYFILE">&amp;Schlüsseldateien auf den Token importieren...</entry>
     <entry lang="de" key="IDC_KEYADD">Dateien &amp;hinzuf.</entry>
     <entry lang="de" key="IDC_KEYFILES_ENABLE_HIDVOL_PROT">Schlüsselda&amp;t. verwenden</entry>
     <entry lang="de" key="IDC_KEYFILES_HIDVOL_PROT">&amp;Schlüsseldat. ...</entry>
@@ -327,7 +327,7 @@
     <entry lang="de" key="IDC_MOUNT_REMOVABLE">Als &amp;Wechselmedium einhängen</entry>
     <entry lang="de" key="IDC_MOUNT_SYSENC_PART_WITHOUT_PBA">Partition mit &amp;Systemverschlüsselung ohne Pre-Boot-Authentifikation einhängen</entry>
     <entry lang="de" key="IDC_PARALLELIZATION_LABEL_LINK">Parallelisierung:</entry>
-    <entry lang="de" key="IDC_PERFORM_BENCHMARK">Test ...</entry>
+    <entry lang="de" key="IDC_PERFORM_BENCHMARK">Test...</entry>
     <entry lang="de" key="IDC_PRINT">&amp;Drucken</entry>
     <entry lang="de" key="IDC_PROTECT_HIDDEN_VOL">Verstecktes Volume vor &amp;Beschädigung durch äußeres Volume schützen</entry>
     <entry lang="de" key="IDC_RESET">&amp;Zurücksetzen</entry>
@@ -371,8 +371,8 @@
     <entry lang="de" key="IDT_SECONDARY_KEY">Sekundärschlüssel (hexadezimal)</entry>
     <entry lang="de" key="IDT_SECURITY_TOKEN">Sicherheitstoken:</entry>
     <entry lang="de" key="IDT_SORT_METHOD">Sortiermethode:</entry>
-    <entry lang="de" key="IDT_STATIC_MODELESS_WAIT_DLG_INFO">Bitte warten. Dieser Prozess kann sehr lange dauern ...</entry>
-    <entry lang="de" key="IDT_STATIC_MODAL_WAIT_DLG_INFO">Bitte warten ...\nDieser Prozess kann sehr lange dauern und VeraCrypt kann vorübergehend hängen bleiben.</entry>
+    <entry lang="de" key="IDT_STATIC_MODELESS_WAIT_DLG_INFO">Bitte warten. Dieser Prozess kann sehr lange dauern...</entry>
+    <entry lang="de" key="IDT_STATIC_MODAL_WAIT_DLG_INFO">Bitte warten...\nDieser Prozess kann sehr lange dauern und VeraCrypt kann vorübergehend hängen bleiben.</entry>
     <entry lang="de" key="IDT_TEST_BLOCK_NUMBER">Blocknummer:</entry>
     <entry lang="de" key="IDT_TEST_CIPHERTEXT">Chiffretext (hexadezimal)</entry>
     <entry lang="de" key="IDT_TEST_DATA_UNIT_NUMBER">Dateneinheitnummer (64 Bit hexadezimal, die Größe einer Dateneinheit beträgt 512 Byte)</entry>
@@ -387,7 +387,7 @@
     <entry lang="de" key="MENU_SETTINGS">Einstellun&amp;gen</entry>
     <entry lang="de" key="MENU_HELP">&amp;Hilfe</entry>
     <entry lang="de" key="MENU_WEBSITE">   Web&amp;seite   </entry>
-    <entry lang="de" key="ABOUTBOX">&amp;Über VeraCrypt ...</entry>
+    <entry lang="de" key="ABOUTBOX">&amp;Über VeraCrypt...</entry>
     <entry lang="de" key="ACCESSMODEFAIL">Das Schreibschutzattribut des alten Volumes konnte nicht geändert werden. Überprüfen Sie bitte die Dateizugriffsrechte.</entry>
     <entry lang="de" key="ACCESS_DENIED">FEHLER: Zugriff verweigert.\n\nDie Partition ist entweder 0 Sektoren groß, oder es handelt sich um die Bootpartition.</entry>
     <entry lang="de" key="ADMINISTRATOR">Administrator</entry>
@@ -416,7 +416,7 @@
     <entry lang="de" key="CIPHER_HIDVOL_TITLE">Verschl.-Methode des versteckten Vol.</entry>
     <entry lang="de" key="CIPHER_TITLE">Verschlüsselungseinstellungen</entry>
     <entry lang="de" key="CLEAN_WINMRU_FAILED">WARNUNG: Die Pfadinformation des zuletzt ausgewählten Volumes bzw. der zuletzt ausgewählten Schlüsseldatei konnte nicht gelöscht werden. Diese Information wird vom Dateiauswahlfenster gespeichert.</entry>
-    <entry lang="de" key="COMPRESSION_NOT_SUPPORTED">FEHLER: Das Volume wurde auf Dateisystemebene komprimiert. Komprimierte Volumes werden nicht von VeraCrypt unterstützt. Die Kompression von verschlüsselten Daten ist ineffektiv und redundant.\n\nEntfernen Sie das Komprimierungsattribut bitte wie folgt:\n1. Rechtsklick auf Container-Datei innerhalb des Windows-Explorers (nicht in VeraCrypt).\n2. „Eigenschaften“ auswählen.\n3. Im „Eigenschaften“-Dialogfenster auf „Erweitert ...“ klicken.\n4. Im Dialogfenster „Erweiterte Attribute“ die Option „Inhalt komprimieren, um Speicherplatz zu sparen“ deaktivieren und auf „OK“ klicken.\n5. Im Dialogfenster „Eigenschaften“ auf „OK“ klicken.</entry>
+    <entry lang="de" key="COMPRESSION_NOT_SUPPORTED">FEHLER: Das Volume wurde auf Dateisystemebene komprimiert. Komprimierte Volumes werden nicht von VeraCrypt unterstützt. Die Kompression von verschlüsselten Daten ist ineffektiv und redundant.\n\nEntfernen Sie das Komprimierungsattribut bitte wie folgt:\n1. Rechtsklick auf Container-Datei innerhalb des Windows-Explorers (nicht in VeraCrypt).\n2. „Eigenschaften“ auswählen.\n3. Im „Eigenschaften“-Dialogfenster auf „Erweitert...“ klicken.\n4. Im Dialogfenster „Erweiterte Attribute“ die Option „Inhalt komprimieren, um Speicherplatz zu sparen“ deaktivieren und auf „OK“ klicken.\n5. Im Dialogfenster „Eigenschaften“ auf „OK“ klicken.</entry>
     <entry lang="de" key="CREATE_FAILED">Volume %s konnte nicht erstellt werden</entry>
     <entry lang="de" key="DEVICE_FREE_BYTES">Die Größe von %s ist %.2f Bytes</entry>
     <entry lang="de" key="DEVICE_FREE_KB">Die Größe von %s ist %.2f KB</entry>
@@ -426,13 +426,13 @@
     <entry lang="de" key="DEVICE_FREE_PB">Die Größe von %s ist %.2f PB</entry>
     <entry lang="de" key="DEVICE_IN_USE_FORMAT">WARNUNG: Der Datenträger bzw. die Partition wird bereits vom Betriebssystem oder von Anwendungen benutzt! Das Formatieren des Datenträgers bzw. der Partition kann zu Datenbeschädigung und Systeminstabilität führen.\n\nDennoch mit dem Formatieren beginnen?</entry>
     <entry lang="de" key="DEVICE_IN_USE_INPLACE_ENC">WARNUNG: Die Partition wird vom Betriebssystem oder von einer Anwendung verwendet. Sie sollten jede Anwendung, die möglicherweise die Partition verwendet, schließen (einschließlich Antiviren-Software).\n\nFortfahren?</entry>
-    <entry lang="de" key="FORMAT_CANT_UNMOUNT_FILESYS">FEHLER: Der Datenträger bzw. die Partition enthält ein Dateisystem, das nicht ausgehängt werden konnte. Das Dateisystem wird möglicherweise vom Betriebssystem verwendet. Das Formatieren würde sehr wahrscheinlich Daten beschädigen und zu Systeminstabilität führen.\n\nEmpfehlungen zur Behebung des Problems: Zuerst die Partition löschen und anschließend die Partition ohne Formatierung neu erstellen.\n\n1) Im Startmenü Rechtsklick auf „Computer“ oder „Arbeitsplatz“ und dann „Verwalten“ auswählen. Das Fenster „Computerverwaltung“ sollte erscheinen.\n2) „Datenspeicher“ &gt; „Datenträgerverwaltung“ im Fenster „Computerverwaltung“ auswählen.\n3) Rechtsklick auf die zu verschlüsselnde Partition und entweder „Partition löschen ...“, „Volume löschen ...“ oder „Logisches Laufwerk löschen ...“ auswählen.\n4) Auf „Ja“ klicken. Sollte Windows zum Neustart des Rechners auffordern, dieser Aufforderung folgen, die Schritte 1 und 2 wiederholen und mit Schritt 5 fortsetzen.\n5) Rechtsklick auf den als „Nicht zugeordnet“/„Freier Speicherplatz“ bezeichneten Bereich und entweder „Neue Partition ...“, „Neues einfaches Volume ...“ oder „Neues logisches Laufwerk ...“ auswählen.\n6) Den Anweisungen des daraufhin erscheinenden Fensters „Assistent zum Erstellen neuer Partitionen“ bzw. „Assistent zum Erstellen neuer einfacher Volumes“ folgen. Auf der Seite „Partition formatieren“ des Assistenten entweder „Diese Partition nicht formatieren“ oder „Dieses Volume nicht formatieren“ auswählen. Anschließend auf „Weiter“ und danach auf „Fertigstellen“ klicken.\n7) Der Name des in VeraCrypt ausgewählten Datenträgers bzw. der Partition ist jetzt u. U. falsch. Schließen Sie deshalb den Assistenten zum Erstellen von VeraCrypt-Volumes (falls dieser noch offen ist) und starten Sie den Assistenten neu.\n8) Versuchen Sie erneut, den Datenträger bzw. die Partition zu verschlüsseln.\n\nSollte sich VeraCrypt erneut weigern, den Datenträger bzw. die Partition zu verschlüsseln, so können Sie stattdessen auch die Erstellung eines Containerdatei-Volumes in Betracht ziehen.</entry>
+    <entry lang="de" key="FORMAT_CANT_UNMOUNT_FILESYS">FEHLER: Der Datenträger bzw. die Partition enthält ein Dateisystem, das nicht ausgehängt werden konnte. Das Dateisystem wird möglicherweise vom Betriebssystem verwendet. Das Formatieren würde sehr wahrscheinlich Daten beschädigen und zu Systeminstabilität führen.\n\nEmpfehlungen zur Behebung des Problems: Zuerst die Partition löschen und anschließend die Partition ohne Formatierung neu erstellen.\n\n1) Im Startmenü Rechtsklick auf „Computer“ oder „Arbeitsplatz“ und dann „Verwalten“ auswählen. Das Fenster „Computerverwaltung“ sollte erscheinen.\n2) „Datenspeicher“ &gt; „Datenträgerverwaltung“ im Fenster „Computerverwaltung“ auswählen.\n3) Rechtsklick auf die zu verschlüsselnde Partition und entweder „Partition löschen...“, „Volume löschen...“ oder „Logisches Laufwerk löschen...“ auswählen.\n4) Auf „Ja“ klicken. Sollte Windows zum Neustart des Rechners auffordern, dieser Aufforderung folgen, die Schritte 1 und 2 wiederholen und mit Schritt 5 fortsetzen.\n5) Rechtsklick auf den als „Nicht zugeordnet“/„Freier Speicherplatz“ bezeichneten Bereich und entweder „Neue Partition...“, „Neues einfaches Volume...“ oder „Neues logisches Laufwerk...“ auswählen.\n6) Den Anweisungen des daraufhin erscheinenden Fensters „Assistent zum Erstellen neuer Partitionen“ bzw. „Assistent zum Erstellen neuer einfacher Volumes“ folgen. Auf der Seite „Partition formatieren“ des Assistenten entweder „Diese Partition nicht formatieren“ oder „Dieses Volume nicht formatieren“ auswählen. Anschließend auf „Weiter“ und danach auf „Fertigstellen“ klicken.\n7) Der Name des in VeraCrypt ausgewählten Datenträgers bzw. der Partition ist jetzt u. U. falsch. Schließen Sie deshalb den Assistenten zum Erstellen von VeraCrypt-Volumes (falls dieser noch offen ist) und starten Sie den Assistenten neu.\n8) Versuchen Sie erneut, den Datenträger bzw. die Partition zu verschlüsseln.\n\nSollte sich VeraCrypt erneut weigern, den Datenträger bzw. die Partition zu verschlüsseln, so können Sie stattdessen auch die Erstellung eines Containerdatei-Volumes in Betracht ziehen.</entry>
     <entry lang="de" key="INPLACE_ENC_CANT_LOCK_OR_UNMOUNT_FILESYS">FEHLER: Das Dateisystem konnte nicht gesperrt und/oder getrennt werden. Es könnte vom Betriebssystem oder von Programmen verwendet werden (z. B. Backup-Software oder Virenscanner). Die Verschlüsselung der Partition könnte Daten beschädigen oder das System instabil werden lassen.\n\nBitte schließen Sie jede Anwendung, die möglicherweise die Partition verwendet (einschließlich Antiviren-Software), und versuchen Sie es erneut. Wenn dies nicht hilft, folgen Sie bitte den unten stehenden Schritten.</entry>
     <entry lang="de" key="DEVICE_IN_USE_INFO">WARNUNG: Einige der angeschlossenen Datenträger bzw. Partitionen werden bereits verwendet!\n\nDas Ignorieren dieser Meldung kann zu unerwünschten Ergebnissen einschließlich einer Systeminstabilität führen.\n\nEs wird dringend empfohlen, alle Anwendungen, die möglicherweise diese Datenträger bzw. Partitionen verwenden, zu schließen.</entry>
     <entry lang="de" key="DEVICE_PARTITIONS_ERR">Der ausgewählte Datenträger enthält Partitionen!\n\nDas Formatieren des Datenträgers könnte zu Systeminstabilitäten und/oder Datenbeschädigung führen. Bitte wählen Sie stattdessen eine Partition auf diesem Datenträger aus oder entfernen Sie sämtliche Partitionen vom Datenträger, damit VeraCrypt den Datenträger sicher formatieren kann.</entry>
     <entry lang="de" key="DEVICE_PARTITIONS_ERR_W_INPLACE_ENC_NOTE">Das ausgewählte Nicht-Systemlaufwerk enthält Partitionen.\n\nVerschlüsselte laufwerksbasierte VeraCrypt-Volumes können nur auf Laufwerken erstellt werden, die keine Partitionen enthalten (einschließlich Festplatten und Solid-State-Laufwerken). Ein Laufwerk, das Partitionen enthält, kann nur vollständig „in-place“ verschlüsselt werden (Verwendung eines Hauptschlüssels), wenn es das Laufwerk ist, auf dem Windows installiert ist und von dem es startet.\n\nWenn Sie das ausgewählte Nicht-Systemlaufwerk mit einem Hauptschlüssel verschlüsseln möchten, dann müssen Sie zuerst alle Partitionen auf dem Laufwerk löschen, damit VeraCrypt es sicher formatieren kann (Formatieren eines Laufwerks, das Partitionen enthält, kann Systeminstabilität und/oder Datenbeschädigung hervorrufen). Alternativ können Sie jede Partition auf dem Laufwerk individuell verschlüsseln (jede Partition wird mit einem anderen Hauptschlüssel verschlüsselt).\n\nHinweis: Wenn Sie alle Partitionen von einem GPT-Datenträger löschen möchten, dann müssen Sie es in einen MBR-Datenträger umwandeln (z. B. mit der Datenträgerverwaltung), um versteckte Partitionen zu löschen.</entry>
     <entry lang="de" key="WHOLE_NONSYS_DEVICE_ENC_CONFIRM">WARNUNG: Wenn Sie das gesamte Gerät verschlüsseln (im Gegensatz zu einer Partition auf dem Gerät), wird das Betriebssystem dieses Gerät als neu, leer und unformatiert erkennen (da es keine Partitionstabelle enthalten wird). Das kann dazu führen, dass das Gerät vom System spontan initialisiert wird (oder dass Sie gefragt werden, ob Sie das Gerät initialisieren möchten), was das Volume beschädigen kann. Außerdem wird es nicht möglich sein, das Volume beständig als Favorit einzuhängen (z. B., wenn sich der Laufwerksbuchstabe ändert) oder ihm eine Favoriten-Volume-Bezeichnung zuzuweisen.\n\nUm diese Probleme zu vermeiden, sollten Sie erwägen eine Partition auf dem Gerät zu erstellen und diese zu verschlüsseln.\n\nSind Sie sicher, dass Sie das gesamte Gerät verschlüsseln möchten?</entry>
-    <entry lang="de" key="AFTER_FORMAT_DRIVE_LETTER_WARN">WICHTIG: Bitte beachten Sie, dass dieses Volume NICHT mit dem derzeit zugewiesenen Laufwerksbuchstaben %c: eingehängt werden kann!\n\nUm das Volume einzuhängen, klicken Sie „Alle Datentr. einhängen ...“ im Hauptfenster von VeraCrypt. Alternativ können Sie auch im Hauptfenster „Datenträger oder Partition auswählen ...“, diese(n) Partition/Datenträger wählen und „Einhängen ...“ klicken. Dem Volume können Sie dann einen anderen Laufwerksbuchstaben aus der Liste im Hauptfenster zuweisen.\n\nDer vorherige Laufwerksbuchstabe %c: sollte nur benutzt werden, wenn Sie die Verschlüsselung von der Partition/dem Datenträger entfernen möchten (z. B., wenn Sie keine Verschlüsselung mehr benötigen). In diesem Fall wählen Sie das Laufwerk %c: in der Liste „Dieser PC“ mit Rechtsklick aus und wählen Sie „Formatieren ...“. Ansonsten sollte der Laufwerksbuchstabe %c: nie benutzt werden (außer, Sie entfernen ihn und weisen ihn einer anderen Partition oder einem anderen Datenträger zu; siehe VeraCrypt-FAQ).</entry>
+    <entry lang="de" key="AFTER_FORMAT_DRIVE_LETTER_WARN">WICHTIG: Bitte beachten Sie, dass dieses Volume NICHT mit dem derzeit zugewiesenen Laufwerksbuchstaben %c: eingehängt werden kann!\n\nUm das Volume einzuhängen, klicken Sie „Automatisch einhängen...“ im Hauptfenster von VeraCrypt. Alternativ können Sie auch im Hauptfenster „Datenträger oder Partition auswählen...“, diese(n) Partition/Datenträger wählen und „Einhängen...“ klicken. Dem Volume können Sie dann einen anderen Laufwerksbuchstaben aus der Liste im Hauptfenster zuweisen.\n\nDer vorherige Laufwerksbuchstabe %c: sollte nur benutzt werden, wenn Sie die Verschlüsselung von der Partition/dem Datenträger entfernen möchten (z. B., wenn Sie keine Verschlüsselung mehr benötigen). In diesem Fall wählen Sie das Laufwerk %c: in der Liste „Dieser PC“ mit Rechtsklick aus und wählen Sie „Formatieren...“. Ansonsten sollte der Laufwerksbuchstabe %c: nie benutzt werden (außer, Sie entfernen ihn und weisen ihn einer anderen Partition oder einem anderen Datenträger zu; siehe VeraCrypt-FAQ).</entry>
     <entry lang="de" key="OS_NOT_SUPPORTED_FOR_NONSYS_INPLACE_ENC">Die In-Place-Verschlüsselung eines Nicht-Systemlaufwerks wird nicht von Ihrem Betriebssystem unterstützt (nur von Windows Vista oder neuer).\n\nDer Grund dafür ist, dass die aktuell laufende Version nicht das Verkleinern eines Dateisystems beherrscht (Das Dateisystem muss verkleinert werden, um Platz für die Volume-Kopfdaten und die Sicherungskopfdaten zu schaffen).</entry>
     <entry lang="de" key="ONLY_NTFS_SUPPORTED_FOR_NONSYS_INPLACE_ENC">Die ausgewählte Partition scheint kein NTFS-Dateisystem zu enthalten. Nur Partitionen, die ein NTFS-Dateisystem enthalten, können „in-place“ verschlüsselt werden.\n\nHinweis: Der Grund hierfür ist, dass Windows das Verkleinern von anderen Dateisystemtypen nicht unterstützt. Das Dateisystem muss verkleinert werden, um Platz für die Volume-Kopfdaten und die Sicherungskopfdaten zu schaffen.</entry>
     <entry lang="de" key="ONLY_MOUNTED_VOL_SUPPORTED_FOR_NONSYS_INPLACE_ENC">Die ausgewählte Partition scheint kein NTFS-Dateisystem zu enthalten. Nur Partitionen, die ein NTFS-Dateisystem enthalten, können „in-place“ verschlüsselt werden.\n\nWenn Sie ein verschlüsseltes VeraCrypt-Volume innerhalb dieser Partition erstellen möchten, dann wählen Sie die Option „Verschlüsseltes Volume erstellen und formatieren“ (anstelle der Option „Partition ‚in-place‘ verschlüsseln“).</entry>
@@ -473,8 +473,8 @@
     <entry lang="de" key="PERMANENTLY_DECRYPT">&amp;Dauerhaft entschlüsselt</entry>
     <entry lang="de" key="EXIT">Beenden</entry>
     <entry lang="de" key="EXT_PARTITION">Legen Sie bitte ein logisches Laufwerk für diese erweiterte Partition an und wiederholen Sie anschließend den Vorgang.</entry>
-    <entry lang="de" key="FILE_HELP">Ein VeraCrypt-Volume kann in einer Containerdatei liegen, die sich auf einer Festplatte, einer Partition, einem USB-Stick usw. befindet. Eine VeraCrypt-Containerdatei verhält sich wie eine normale Datei. Sie kann wie eine normale Datei kopiert, bewegt oder gelöscht werden. Klicken Sie auf „Datei ...“, um einen Dateinamen und den Speicherort für die Containerdatei zu wählen.\n\nACHTUNG: Wenn Sie eine bestehende Datei wählen, wird VeraCrypt diese NICHT verschlüsseln. Die Datei wird gelöscht und mit der Containerdatei ersetzt. Sie können bestehende Dateien verschlüsseln, indem Sie diese später in den neuen VeraCrypt-Container verschieben, den Sie gerade erstellen.</entry>
-    <entry lang="de" key="FILE_HELP_HIDDEN_HOST_VOL">Wählen Sie den Speicherort des äußeren Volumes (in diesem wird später das versteckte Volume erstellt).\nEin VeraCrypt-Volume kann in einer Datei liegen (eine VeraCrypt-Containerdatei), die sich auf einer Festplatte, einer Partition, einem USB-Stick usw. befindet. Eine Containerdatei verhält sich genau wie eine normale Datei, sie kann z. B. kopiert oder gelöscht werden. Klicken Sie auf „Datei ...“, um einen Dateinamen und den Speicherort für die Containerdatei zu wählen.\n\nACHTUNG: Wenn Sie eine bestehende Datei wählen, wird VeraCrypt diese NICHT verschlüsseln; die Datei wird gelöscht und mit der Containerdatei ersetzt. Sie können bestehende Dateien verschlüsseln, indem Sie diese in den neuen VeraCrypt-Container verschieben.</entry>
+    <entry lang="de" key="FILE_HELP">Ein VeraCrypt-Volume kann in einer Containerdatei liegen, die sich auf einer Festplatte, einer Partition, einem USB-Stick usw. befindet. Eine VeraCrypt-Containerdatei verhält sich wie eine normale Datei. Sie kann wie eine normale Datei kopiert, bewegt oder gelöscht werden. Klicken Sie auf „Datei...“, um einen Dateinamen und den Speicherort für die Containerdatei zu wählen.\n\nACHTUNG: Wenn Sie eine bestehende Datei wählen, wird VeraCrypt diese NICHT verschlüsseln. Die Datei wird gelöscht und mit der Containerdatei ersetzt. Sie können bestehende Dateien verschlüsseln, indem Sie diese später in den neuen VeraCrypt-Container verschieben, den Sie gerade erstellen.</entry>
+    <entry lang="de" key="FILE_HELP_HIDDEN_HOST_VOL">Wählen Sie den Speicherort des äußeren Volumes (in diesem wird später das versteckte Volume erstellt).\nEin VeraCrypt-Volume kann in einer Datei liegen (eine VeraCrypt-Containerdatei), die sich auf einer Festplatte, einer Partition, einem USB-Stick usw. befindet. Eine Containerdatei verhält sich genau wie eine normale Datei, sie kann z. B. kopiert oder gelöscht werden. Klicken Sie auf „Datei...“, um einen Dateinamen und den Speicherort für die Containerdatei zu wählen.\n\nACHTUNG: Wenn Sie eine bestehende Datei wählen, wird VeraCrypt diese NICHT verschlüsseln; die Datei wird gelöscht und mit der Containerdatei ersetzt. Sie können bestehende Dateien verschlüsseln, indem Sie diese in den neuen VeraCrypt-Container verschieben.</entry>
     <entry lang="de" key="DEVICE_HELP">Verschlüsselte, laufwerksbasierte VeraCrypt-Volumes können innerhalb einer Partition auf Festplatten, Solid-State-Laufwerken, USB-Sticks und anderen unterstützten Laufwerken erstellt werden. Partitionen können außerdem „in-place“ verschlüsselt werden.\n\nAußerdem können laufwerksbasierte VeraCrypt-Volumes auf Laufwerken erstellt werden, die keine Partitionen beinhalten (einschließlich Festplatten und Solid-State-Laufwerken).\n\nHinweis: Ein Laufwerk, das Partitionen enthält, kann nur vollständig „in-place“ verschlüsselt werden (Verwendung eines Hauptschlüssels), wenn es das Laufwerk ist, auf dem Windows installiert ist und von dem es startet.</entry>
     <entry lang="de" key="DEVICE_HELP_NO_INPLACE">Ein laufwerksbasiertes VeraCrypt-Volume kann innerhalb einer Festplatte, eines Solid-State-Laufwerks, USB-Stick und anderen Speichergeräten erstellt werden.\n\nWARNUNG: Beachten Sie, dass die Partition/das Laufwerk formatiert werden und alle derzeit darauf gespeicherten Daten verloren gehen.</entry>
     <entry lang="de" key="DEVICE_HELP_HIDDEN_HOST_VOL">\nWählen Sie den Speicherort für die Erstellung des äußeren Volumes. In diesem wird später das versteckte Volume erstellt.\n\nEin äußeres Volume kann auf einer Festplattenpartition, einem Solid-State-Laufwerk, USB-Stick u. a. Speicherlaufwerken erstellt werden. Äußere Volumes können auch auf Laufwerken erstellt werden, die keine Partitionen enthalten (einschließlich Festplatten und SSDs).\n\nWARNUNG: Beachten Sie, dass die Partition bzw. der Datenträger formatiert wird und alle zurzeit darauf gespeicherte Daten verloren gehen.</entry>
@@ -504,13 +504,13 @@
     <entry lang="de" key="WIPE_FINISHED">Der Inhalt der Partition/des Laufwerks wurde erfolgreich gelöscht.</entry>
     <entry lang="de" key="WIPE_FINISHED_DECOY_SYSTEM_PARTITION">Der Inhalt der Partition, auf der das ursprüngliche System lag (eine Kopie des versteckten Systems), wurde erfolgreich gelöscht.</entry>
     <entry lang="de" key="DECOY_OS_VERSION_WARNING">Bitte stellen Sie sicher, dass die Windows-Version, die Sie installieren werden, die gleiche ist wie die Version, die Sie gerade laufen haben. Dies ist notwendig, da beide Systeme dieselbe Bootpartition verwenden werden.</entry>
-    <entry lang="de" key="SYSTEM_ENCRYPTION_FINISHED">Die Systempartition/das Systemlaufwerk wurde erfolgreich verschlüsselt.\n\nBitte beachten Sie: Wenn Sie VeraCrypt-Volumes beim Windowsstart einhängen möchten, wählen Sie nach dem Einhängen unter „Favoriten“ &gt; „Eingehängtes Volume zu Systemfavoriten hinzufügen ...“.</entry>
+    <entry lang="de" key="SYSTEM_ENCRYPTION_FINISHED">Die Systempartition/das Systemlaufwerk wurde erfolgreich verschlüsselt.\n\nBitte beachten Sie: Wenn Sie VeraCrypt-Volumes beim Windowsstart einhängen möchten, wählen Sie nach dem Einhängen unter „Favoriten“ &gt; „Eingehängtes Volume zu Systemfavoriten hinzufügen...“.</entry>
     <entry lang="de" key="SYSTEM_DECRYPTION_FINISHED">Die Systempartition/das Systemlaufwerk wurde erfolgreich entschlüsselt.</entry>
     <entry lang="de" key="FORMAT_FINISHED_HELP">\n\nDas VeraCrypt-Volume wurde erstellt und ist einsatzbereit. Mit „Weiter“ können Sie ein weiteres VeraCrypt-Volume erstellen. Anderenfalls klicken Sie auf „Beenden“.</entry>
     <entry lang="de" key="SYSENC_HIDDEN_VOL_FORMAT_FINISHED_HELP">\n\nDas versteckte VeraCrypt-Volume wurde erfolgreich erstellt. Das versteckte Betriebssystem befindet sich in diesem versteckten Volume.\n\nKlicken Sie auf „Weiter“, um fortzufahren.</entry>
     <entry lang="de" key="NONSYS_INPLACE_ENC_FINISHED_TITLE">Volume vollständig verschlüsselt</entry>
     <entry lang="de" key="NONSYS_INPLACE_DEC_FINISHED_TITLE">Volume vollständig entschlüsselt</entry>
-    <entry lang="de" key="NONSYS_INPLACE_ENC_FINISHED_INFO">WICHTIG: UM DIESES NEU ERSTELLTE VERACRYPT-VOLUME EINZUHÄNGEN UND AUF DIE DATEN ZUZUGREIFEN, KLICKEN SIE AUF „Alle Datentr. einhängen ...“ IM VERACRYPT-HAUPTFENSTER. Nachdem Sie das richtige Passwort eingegeben und/oder die korrekten Schlüsseldateien angegeben haben, wird das Volume unter dem Laufwerksbuchstaben eingehängt, den Sie aus der Liste im VeraCrypt-Hauptfenster wählen. Sie können auf die verschlüsselten Daten über den gewählten Laufwerksbuchstaben zugreifen.\n\nBITTE MERKEN SIE SICH DIE OBEN GENANNTEN SCHRITTE. SIE MÜSSEN DIESE JEDES MAL BEFOLGEN, WENN SIE DAS VOLUME EINHÄNGEN UND AUF DARIN BEFINDLICHE DATEN ZUGREIFEN MÖCHTEN. Alternativ klicken Sie im VeraCrypt-Hauptbildschirm auf „Datenträger ...“, wählen diese(s) Partition/Volume aus und klicken auf „Einhängen ...“.\n\nDie Partition/das Volume wurde erfolgreich verschlüsselt, enthält jetzt ein vollverschlüsseltes VeraCrypt-Volume und ist einsatzbereit.</entry>
+    <entry lang="de" key="NONSYS_INPLACE_ENC_FINISHED_INFO">WICHTIG: UM DIESES NEU ERSTELLTE VERACRYPT-VOLUME EINZUHÄNGEN UND AUF DIE DATEN ZUZUGREIFEN, KLICKEN SIE AUF „Automatisch einhängen...“ IM VERACRYPT-HAUPTFENSTER. Nachdem Sie das richtige Passwort eingegeben und/oder die korrekten Schlüsseldateien angegeben haben, wird das Volume unter dem Laufwerksbuchstaben eingehängt, den Sie aus der Liste im VeraCrypt-Hauptfenster wählen. Sie können auf die verschlüsselten Daten über den gewählten Laufwerksbuchstaben zugreifen.\n\nBITTE MERKEN SIE SICH DIE OBEN GENANNTEN SCHRITTE. SIE MÜSSEN DIESE JEDES MAL BEFOLGEN, WENN SIE DAS VOLUME EINHÄNGEN UND AUF DARIN BEFINDLICHE DATEN ZUGREIFEN MÖCHTEN. Alternativ klicken Sie im VeraCrypt-Hauptbildschirm auf „Datenträger...“, wählen diese(s) Partition/Volume aus und klicken auf „Einhängen...“.\n\nDie Partition/das Volume wurde erfolgreich verschlüsselt, enthält jetzt ein vollverschlüsseltes VeraCrypt-Volume und ist einsatzbereit.</entry>
     <entry lang="de" key="NONSYS_INPLACE_DEC_FINISHED_INFO">Das VeraCrypt-Volume wurde erfolgreich entschlüsselt.</entry>
     <entry lang="de" key="NONSYS_INPLACE_DEC_FINISHED_DRIVE_LETTER_SEL_INFO">Das VeraCrypt-Volume wurde erfolgreich entschlüsselt.\n\nBitte wählen Sie einen Laufwerksbuchstaben aus, der dem entschlüsselten Laufwerk zugewiesen werden soll, und klicken Sie auf „Fertigstellen“.\n\nWICHTIG: Solange dem entschlüsselten Laufwerk kein Laufwerksbuchstabe zugewiesen wurde, kann nicht auf die darauf vorhandenen Daten zugegriffen werden.</entry>
     <entry lang="de" key="NONSYS_INPLACE_DEC_FINISHED_NO_DRIVE_LETTER_AVAILABLE">WARNUNG: Um auf die entschlüsselten Daten zugreifen zu können, muss dem entschlüsselten Laufwerk ein Laufwerksbuchstabe zugewiesen werden, jedoch steht momentan kein freier Laufwerksbuchstabe zur Verfügung.\n\nBitte einen verwendeten Laufwerksbuchstaben freigeben (z. B. durch Abziehen eines USB-Sticks oder anderer externer Laufwerke) und dann mit „OK“ bestätigen.</entry>
@@ -571,7 +571,7 @@
     <entry lang="de" key="MAX_HIDVOL_SIZE_TB">Die maximal mögliche Größe für ein verstecktes Volume innerhalb dieses Volumes ist %.2f TB.</entry>
     <entry lang="de" key="MOUNTED_NOPWCHANGE">Volume-Passwort/Schlüsseldateien können nicht geändert werden, solange das Volume eingehängt ist. Trennen Sie bitte zuvor das Volume.</entry>
     <entry lang="de" key="MOUNTED_NO_PKCS5_PRF_CHANGE">Der Algorithmus für die Kopfdatenschlüsselberechnung kann nicht geändert werden, solange das Volume eingehängt ist. Trennen Sie bitte zuvor das Volume.</entry>
-    <entry lang="de" key="MOUNT_BUTTON">E&amp;inhängen ...</entry>
+    <entry lang="de" key="MOUNT_BUTTON">E&amp;inhängen...</entry>
     <entry lang="de" key="NEW_VERSION_REQUIRED">Zum Einhängen dieses Volumes wird eine neuere VeraCrypt-Version benötigt.</entry>
     <entry lang="de" key="VOL_CREATION_WIZARD_NOT_FOUND">FEHLER: Der Assistent zum Erstellen von VeraCrypt-Volumes wurde nicht gefunden.\n\nBitte stellen Sie sicher, dass sich die Datei „VeraCrypt Format.exe“ in dem Ordner befindet, aus dem „VeraCrypt.exe“ gestartet wurde. Falls diese Datei fehlt, muss VeraCrypt neu installiert oder die Datei „VeraCrypt Format.exe“ gesucht und gestartet werden.</entry>
     <entry lang="de" key="VOL_EXPANDER_NOT_FOUND">FEHLER: Der Volume-Erweiterer wurde nicht gefunden.\n\nBitte stellen Sie sicher, dass sich die Datei „VeraCryptExpander.exe“ in dem Ordner befindet, aus dem „VeraCrypt.exe“ gestartet wurde. Falls diese Datei fehlt, muss VeraCrypt neu installiert oder die Datei „VeraCryptExpander.exe“ gesucht und gestartet werden.</entry>
@@ -644,13 +644,13 @@
     <entry lang="de" key="PASSWORD_WRONG_CAPSLOCK_ON">\n\nWARNUNG: Die Feststelltaste ist aktiviert. Dies führt möglicherweise zu einer falschen Passworteingabe.</entry>
     <entry lang="de" key="PIM_CHANGE_WARNING">MERKEN! Für Volume-Einhängung</entry>
     <entry lang="de" key="PIM_HIDVOL_HOST_TITLE">PIM des äußeren Volumes</entry>
-    <entry lang="de" key="PIM_HIDVOL_TITLE">PIM des verste  ckten Volumes</entry>
+    <entry lang="de" key="PIM_HIDVOL_TITLE">PIM des versteckten Volumes</entry>
     <entry lang="de" key="PIM_HIDDEN_OS_TITLE">PIM für verstecktes Betriebssystem</entry>
     <entry lang="de" key="PIM_HELP">Der PIM (Persönlicher Iterationsmultiplikator) ist ein Wert, der die Anzahl der Iterationen für die Kopfdatenschlüsselableitung wie folgt steuert:\n      Iterationen = 15000 + (PIM x 1000).\n\nWird der Wert leer gelassen oder auf 0 gesetzt, benutzt VeraCrypt einen Standardwert (485), der hohe Sicherheit gewährleistet.\n\nWenn das Passwort weniger als 20 Zeichen hat, kann der PIM nicht kleiner als 485 sein, um ein minimales Sicherheitslevel zu gewährleisten.\nWenn das Passwort 20 Zeichen oder mehr hat, kann der PIM beliebig gesetzt werden.\nEin PIM-Wert größer als 485 verlangsamt das Einhängen. Ein niedriger PIM-Wert (kleiner als 485) beschleunigt das Einhängen, kann aber die Sicherheit verringern, wenn ein zu schwaches Passwort gewählt wurde.</entry>
     <entry lang="de" key="PIM_SYSENC_HELP">Der PIM (Persönlicher Iterationsmultiplikator) ist ein Wert, der die Anzahl der Iterationen für die Kopfdatenschlüsselableitung wie folgt steuert:\n      Iterationen = PIM x 2048.\n\nWird der Wert leer gelassen oder auf 0 gesetzt, benutzt VeraCrypt einen Standardwert, der hohe Sicherheit gewährleistet.\n\nWenn das Passwort weniger als 20 Zeichen hat, kann der PIM nicht kleiner als 98 sein, um ein minimales Sicherheitslevel zu gewährleisten.\nWenn das Passwort 20 Zeichen oder mehr hat, kann der PIM beliebig gesetzt werden.\nEin PIM-Wert größer als 98 verlangsamt den Bootvorgang. Ein niedriger PIM-Wert (kleiner als 98) beschleunigt den Bootvorgang, kann aber die Sicherheit verringern, wenn ein zu schwaches Passwort gewählt wurde.</entry>
     <entry lang="de" key="PIM_SYSENC_CHANGE_WARNING">MERKEN! Für Bootvorgang</entry>
     <entry lang="de" key="PIM_LARGE_WARNING">Der gewählte PIM-Wert ist größer als der VeraCrypt-Standardwert.\nBitte beachten Sie, dass dies den Einhänge- bzw. Bootvorgang erheblich verlangsamt.</entry>
-    <entry lang="de" key="PIM_SMALL_WARNING">Der gewählte PIM-Wert (Persönlicher Iterationsmultiplikator) ist kleiner als der VeraCrypt-Standardwert.\nBitte beachten Sie, dass dies die Sicherheit verringern kann, wenn ein zu schwaches Passwort gewählt wurde!\n\nBestätigen Sie, dass Sie ein starkes Passwort gewählt haben?</entry>
+    <entry lang="de" key="PIM_SMALL_WARNING">Der gewählte PIM-Wert (Persönlicher Iterationsmultiplikator) ist kleiner als der VeraCrypt-Standardwert.\nBitte beachten Sie, dass ein zu schwaches Passwort die Sicherheit beeinträchtigen kann.\n\nBestätigen Sie, dass Sie ein sicheres Passwort verwenden?</entry>
     <entry lang="de" key="PIM_SYSENC_TOO_BIG">Der größtmögliche Wert für den PIM (Persönlicher Iterationsmultiplikator) ist 65535.</entry>
     <entry lang="de" key="PIM_TITLE">Volume-PIM</entry>
     <entry lang="de" key="HIDDEN_FILES_PRESENT_IN_KEYFILE_PATH">\n\nWARNUNG: Versteckte Dateien wurden im Suchpfad gefunden. Diese versteckten Dateien können nicht als Schlüsseldateien verwendet werden. Wenn Sie diese Dateien als Schlüsseldateien verwenden möchten, müssen Sie das Attribut „Versteckt“ entfernen (Rechtsklick auf die Datei, „Eigenschaften“ wählen, „Versteckt“ abwählen, „OK“ klicken). Hinweis: Versteckte Dateien sind nur sichtbar, wenn die entsprechende Option im Explorer aktiviert ist („Datei“ &gt; „Ordner- und Suchoptionen ändern“ &gt; „Ansicht“).</entry>
@@ -658,7 +658,7 @@
     <entry lang="de" key="FOUND_NO_PARTITION_W_DEFERRED_INPLACE_ENC">VeraCrypt hat kein Volume gefunden, wo die Verschlüsselung unterbrochen wurde und wo die Volume-Kopfdaten durch das angegebene Passwort und/oder der Schlüsseldatei(en) entschlüsselt werden können.\n\nStellen Sie bitte sicher, dass das Passwort und/oder die Schlüsseldatei(en) richtig sind und die Partition/das Volume nicht vom System oder von Anwendungen verwendet wird (einschließlich Antiviren-Software).</entry>
     <entry lang="de" key="SELECTED_PARTITION_ALREADY_INPLACE_ENC">Die ausgewählte Partition oder der Datenträger ist bereits vollständig verschlüsselt.\nHeader Flags = 0x%.8X</entry>
     <entry lang="de" key="SELECTED_PARTITION_NOT_INPLACE_ENC">Die ausgewählte Partition oder der Datenträger benutzen keine „in-place“-Verschlüsselung.\nHeader Flags = 0x%.8X</entry>
-    <entry lang="de" key="SYSENC_MOUNT_WITHOUT_PBA_NOTE">\n\nHinweis: Wenn Sie versuchen, eine Partition einzuhängen, die auf einem verschlüsselten Systemlaufwerk ohne Pre-Boot-Authentifikation ist oder eine verschlüsselte Systempartition einhängen, obwohl das darauf befindliche Betriebssystem nicht gestartet ist, dann wählen Sie „System“ &gt; „Ohne Pre-Boot-Authentifikation einhängen ...“.</entry>
+    <entry lang="de" key="SYSENC_MOUNT_WITHOUT_PBA_NOTE">\n\nHinweis: Wenn Sie versuchen, eine Partition einzuhängen, die auf einem verschlüsselten Systemlaufwerk ohne Pre-Boot-Authentifikation ist oder eine verschlüsselte Systempartition einhängen, obwohl das darauf befindliche Betriebssystem nicht gestartet ist, dann wählen Sie „System“ &gt; „Ohne Pre-Boot-Authentifikation einhängen...“.</entry>
     <entry lang="de" key="MOUNT_WITHOUT_PBA_VOL_ON_ACTIVE_SYSENC_DRIVE">In diesem Modus können Sie keine auf einem Laufwerk befindliche Partition einhängen, von der ein Teil innerhalb des Schlüsselbereiches der aktiven Systemverschlüsselung liegt.\n\nBevor Sie diese Partition in diesem Modus einhängen können, müssen Sie entweder ein Betriebssystem, das auf einem anderen Laufwerk installiert ist (verschlüsselt oder unverschlüsselt), oder ein unverschlüsseltes Betriebssystem starten.</entry>
     <entry lang="de" key="CANT_DECRYPT_PARTITION_ON_ENTIRELY_ENCRYPTED_SYS_DRIVE">VeraCrypt kann keine einzelne Partition auf einem vollständig verschlüsselten Systemlaufwerk entschlüsseln. Sie können nur das gesamte Systemlaufwerk entschlüsseln.</entry>
     <entry lang="de" key="CANT_DECRYPT_PARTITION_ON_ENTIRELY_ENCRYPTED_SYS_DRIVE_UNSURE">WARNUNG: Da auf dem Laufwerk der VeraCrypt-Bootloader gefunden wurde, könnte es sich um ein vollständig verschlüsseltes Systemlaufwerk handeln. Wenn dies zutrifft, beachten Sie bitte, dass VeraCrypt keine einzelne Partition auf einem vollständig verschlüsselten Systemlaufwerk entschlüsseln kann (Sie können nur das gesamte Systemlaufwerk entschlüsseln). In diesem Fall können Sie zwar fortfahren, erhalten aber später die Fehlermeldung „Falsches Passwort“.</entry>
@@ -816,7 +816,7 @@
     <entry lang="de" key="SECONDARY_KEY_SIZE_LRW">Tweak-Schlüssellänge (LRW-Modus)</entry>
     <entry lang="de" key="BITS">Bit</entry>
     <entry lang="de" key="BLOCK_SIZE">Blockgröße</entry>
-    <entry lang="de" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="de" key="KDF">KDF</entry>
     <entry lang="de" key="PKCS5_ITERATIONS">PKCS-5-Iterationen</entry>
     <entry lang="de" key="VOLUME_CREATE_DATE">Volume erstellt</entry>
     <entry lang="de" key="VOLUME_HEADER_DATE">Kopfdaten zuletzt geändert</entry>
@@ -905,7 +905,7 @@
     <entry lang="de" key="HOURS">Stunden</entry>
     <entry lang="de" key="MINUTES">Minuten</entry>
     <entry lang="de" key="SECONDS">s</entry>
-    <entry lang="de" key="OPEN">Öffnen ...</entry>
+    <entry lang="de" key="OPEN">Öffnen...</entry>
     <entry lang="de" key="UNMOUNT">Trennen</entry>
     <entry lang="de" key="SHOW_TC">VeraCrypt-Hauptfenster anzeigen</entry>
     <entry lang="de" key="HIDE_TC">VeraCrypt-Hauptfenster verbergen</entry>
@@ -947,7 +947,7 @@
     <entry lang="de" key="KEYFILE_EMPTY_BASE_NAME">Bitte geben Sie einen Namen für die zu erstellenden Schlüsseldateien ein.</entry>
     <entry lang="de" key="KEYFILE_INVALID_BASE_NAME">Der Name für die Schlüsseldateien ist unzulässig.</entry>
     <entry lang="de" key="KEYFILE_ALREADY_EXISTS">Die Schlüsseldatei „%s“ existiert bereits.\nMöchten Sie sie überschreiben? Der Erstellungsprozess wird abgebrochen, wenn Sie „Nein“ wählen.</entry>
-    <entry lang="de" key="HEADER_DAMAGED_AUTO_USED_HEADER_BAK">WARNUNG: Die Kopfdaten von diesem Volume sind beschädigt! VeraCrypt verwendet automatisch die Sicherung der Volume-Kopfdaten, die im Volume eingebettet sind.\n\nSie sollten die Volume-Kopfdaten reparieren, indem Sie „Extras“ &gt; „Volume-Kopfdaten wiederherstellen ...“ auswählen.</entry>
+    <entry lang="de" key="HEADER_DAMAGED_AUTO_USED_HEADER_BAK">WARNUNG: Die Kopfdaten von diesem Volume sind beschädigt! VeraCrypt verwendet automatisch die Sicherung der Volume-Kopfdaten, die im Volume eingebettet sind.\n\nSie sollten die Volume-Kopfdaten reparieren, indem Sie „Extras“ &gt; „Volume-Kopfdaten wiederherstellen...“ auswählen.</entry>
     <entry lang="de" key="VOL_HEADER_BACKED_UP">Die Volume-Kopfdaten wurden erfolgreich gesichert.\n\nWICHTIG: Beim Wiederherstellen der Volume-Kopfdaten mit dieser Sicherungskopie wird auch das aktuelle Volume-Passwort wiederhergestellt. Werden zudem Schlüsseldatei(en) zum Einhängen dieses Volumes benötigt, so werden dieselben Schlüsseldatei(en) auch dann wieder zum Einhängen des Volumes benötigt, nachdem die Volume-Kopfdaten wiederhergestellt worden sind.\n\nWARNUNG: Diese Sicherungskopie der Volume-Kopfdaten kann NUR für die Wiederherstellung von speziell diesem Volume verwendet werden. Sollte die Kopfdatensicherungskopie zur Wiederherstellung der Kopfdaten eines anderen Volumes verwendet werden, kann zwar das Volume eingehängt werden, aber es können KEINE Daten, die in diesem Volume gespeichert sind, entschlüsselt werden (weil der Hauptschlüssel geändert worden ist).</entry>
     <entry lang="de" key="VOL_HEADER_RESTORED">Die Volume-Kopfdaten wurden erfolgreich wiederhergestellt.\n\nWICHTIG: Möglicherweise wurde ein veraltetes Passwort ebenfalls wiederhergestellt. Wurden zudem zum Zeitpunkt der Sicherung Schlüsseldatei(en) zum Einhängen dieses Volumes benötigt, so werden dieselben Schlüsseldatei(en) jetzt ebenfalls wieder zum Einhängen des Volumes benötigt.</entry>
     <entry lang="de" key="EXTERNAL_VOL_HEADER_BAK_FIRST_INFO">Aus Sicherheitsgründen müssen Sie das richtige Passwort für das Volume eingeben (und/oder die richtigen Schlüsseldateien bereitstellen).\n\nHinweis: Wenn das Volume ein verstecktes Volume enthält, dann müssen Sie zuerst das richtige Passwort für das äußere Volume eingeben (und/oder die richtigen Schlüsseldateien bereitstellen). Anschließend müssen Sie das richtige Passwort für das versteckte Volume eingeben (und/oder die richtigen Schlüsseldateien bereitstellen), wenn Sie die Kopfdaten des versteckten Volumes sichern möchten.</entry>
@@ -968,11 +968,11 @@
     <entry lang="de" key="RESCUE_DISK_NON_WIZARD_CREATION_WIN_ISOBURN">Das Rettungsdatenträger-Abbild wurde erstellt und in dieser Datei gespeichert:\n%s\n\nJetzt müssen Sie das Rettungsdatenträger-Abbild auf eine CD oder DVD brennen.\n\nMöchten Sie den Microsoft Windows ISO-Brennprogramm jetzt starten?\n\nNachdem Sie den Rettungsdatenträger gebrannt haben, wählen Sie „System“ &gt; „Rettungsdatenträger überprüfen“, um sicherzustellen, dass die CD korrekt erstellt wurde.</entry>
     <entry lang="de" key="RESCUE_DISK_NON_WIZARD_CHECK_INSERT">Bitte legen Sie den VeraCrypt-Rettungsdatenträger in Ihr CD/DVD-Laufwerk und klicken dann zum Prüfen auf „OK“.</entry>
     <entry lang="de" key="RESCUE_DISK_NON_WIZARD_CHECK_PASSED">Der VeraCrypt-Rettungsdatenträger wurde erfolgreich überprüft.</entry>
-    <entry lang="de" key="RESCUE_DISK_NON_WIZARD_CHECK_FAILED">Es konnte nicht festgestellt werden, ob der Rettungsdatenträger korrekt gebrannt wurde.\n\nWenn Sie die CD/DVD gebrannt haben, dann werfen Sie diese aus und legen die CD/DVD anschließend wieder ein, um es erneut zu versuchen. Bitte versuchen Sie es mit einer anderen Brennsoftware oder mit anderen CD- bzw. DVD-Rohlingen, falls es nicht funktioniert.\n\nWenn Sie einen VeraCrypt-Rettungsdatenträger prüfen, der für einen anderen Hauptschlüssel, Salt-Wert, anderes Passwort usw. erstellt wurde, so beachten Sie, dass bei solchen Rettungsdatenträgern die Überprüfung immer fehlschlagen wird. Um einen mit Ihrem System voll kompatiblen Rettungsdatenträger zu erstellen, wählen Sie „System“ &gt; „Rettungsdatenträger erstellen ...“.</entry>
+    <entry lang="de" key="RESCUE_DISK_NON_WIZARD_CHECK_FAILED">Es konnte nicht festgestellt werden, ob der Rettungsdatenträger korrekt gebrannt wurde.\n\nWenn Sie die CD/DVD gebrannt haben, dann werfen Sie diese aus und legen die CD/DVD anschließend wieder ein, um es erneut zu versuchen. Bitte versuchen Sie es mit einer anderen Brennsoftware oder mit anderen CD- bzw. DVD-Rohlingen, falls es nicht funktioniert.\n\nWenn Sie einen VeraCrypt-Rettungsdatenträger prüfen, der für einen anderen Hauptschlüssel, Salt-Wert, anderes Passwort usw. erstellt wurde, so beachten Sie, dass bei solchen Rettungsdatenträgern die Überprüfung immer fehlschlagen wird. Um einen mit Ihrem System voll kompatiblen Rettungsdatenträger zu erstellen, wählen Sie „System“ &gt; „Rettungsdatenträger erstellen...“.</entry>
     <entry lang="de" key="RESCUE_DISK_ISO_IMAGE_CHECK_PASSED">Der VeraCrypt-Rettungsdatenträger wurde erfolgreich überprüft.</entry>
-    <entry lang="de" key="RESCUE_DISK_ISO_IMAGE_CHECK_FAILED">Die Überprüfung des Rettungsdatenträgers ist fehlgeschlagen.\n\nWenn Sie einen VeraCrypt-Rettungsdatenträger prüfen, der für einen anderen Hauptschlüssel, Salt-Wert, anderes Passwort usw. erstellt wurde, so beachten Sie, dass bei solchen Abbildern die Überprüfung immer fehlschlagen wird. Um ein mit Ihrem System voll kompatibles Abbild zu erstellen, wählen Sie „System“ &gt; „Rettungsdatenträger erstellen ...“.</entry>
+    <entry lang="de" key="RESCUE_DISK_ISO_IMAGE_CHECK_FAILED">Die Überprüfung des Rettungsdatenträgers ist fehlgeschlagen.\n\nWenn Sie einen VeraCrypt-Rettungsdatenträger prüfen, der für einen anderen Hauptschlüssel, Salt-Wert, anderes Passwort usw. erstellt wurde, so beachten Sie, dass bei solchen Abbildern die Überprüfung immer fehlschlagen wird. Um ein mit Ihrem System voll kompatibles Abbild zu erstellen, wählen Sie „System“ &gt; „Rettungsdatenträger erstellen...“.</entry>
     <entry lang="de" key="ERROR_CREATING_RESCUE_DISK">Fehler beim Erstellen des VeraCrypt-Rettungsdatenträgers.</entry>
-    <entry lang="de" key="CANNOT_CREATE_RESCUE_DISK_ON_HIDDEN_OS">Der VeraCrypt-Rettungsdatenträger kann nicht erstellt werden, wenn ein verstecktes Betriebssystem läuft.\n\nUm einen VeraCrypt-Rettungsdatenträger zu erstellen, starten Sie das Köder-Betriebssystem und klicken auf „System“ &gt; „Rettungsdatenträger erstellen ...“.</entry>
+    <entry lang="de" key="CANNOT_CREATE_RESCUE_DISK_ON_HIDDEN_OS">Der VeraCrypt-Rettungsdatenträger kann nicht erstellt werden, wenn ein verstecktes Betriebssystem läuft.\n\nUm einen VeraCrypt-Rettungsdatenträger zu erstellen, starten Sie das Köder-Betriebssystem und klicken auf „System“ &gt; „Rettungsdatenträger erstellen...“.</entry>
     <entry lang="de" key="RESCUE_DISK_CHECK_FAILED">Der VeraCrypt-Rettungsdatenträger kann nicht überprüft werden.\n\nWenn Sie den Rettungsdatenträger gebrannt haben, öffnen und schließen Sie das CD- bzw. DVD-Laufwerk und klicken Sie auf „Weiter“, um es erneut zu versuchen. Falls das nicht hilft, versuchen Sie es bitte mit einer neuen CD/DVD%s.\n\nWenn Sie den Rettungsdatenträger noch nicht gebrannt haben, tun Sie dies bitte jetzt und klicken Sie danach auf „Weiter“.\n\nWenn Sie einen Rettungsdatenträger überprüfen, der vor dem Start von dessen Assistenten erstellt wurde, beachten Sie bitte, dass dieser Rettungsdatenträger nicht verwendet werden kann, weil er für einen anderen Hauptschlüssel erstellt wurde. In diesem Fall brennen Sie bitte einen neuen Rettungsdatenträger.</entry>
     <entry lang="de" key="RESCUE_DISK_CHECK_FAILED_SENTENCE_APPENDIX"> und/oder andere CD-/DVD-Brennsoftware</entry>
     <entry lang="de" key="SYSTEM_FAVORITES_DLG_TITLE">VeraCrypt – Systemfavoriten-Volume</entry>
@@ -980,11 +980,11 @@
     <entry lang="de" key="SYS_FAVORITES_REQUIRE_PBA">Die Systempartition/das Systemlaufwerk scheint nicht verschlüsselt zu sein.\n\nSystemfavoriten-Volumes können nur mit einem Pre-Boot-Authentifikationspasswort eingehängt werden. Um Systemfavoriten-Volumes zu verwenden, müssen Sie deshalb zuerst die Systempartition/das Systemlaufwerk verschlüsseln.</entry>
     <entry lang="de" key="UNMOUNT_FIRST">Trennen Sie bitte zuerst das Volume.</entry>
     <entry lang="de" key="CANNOT_SET_TIMER">FEHLER: Kann Timer nicht einstellen.</entry>
-    <entry lang="de" key="IDPM_CHECK_FILESYS">Dateisystem prüfen ...</entry>
-    <entry lang="de" key="IDPM_REPAIR_FILESYS">Dateisystem reparieren ...</entry>
-    <entry lang="de" key="IDPM_ADD_TO_FAVORITES">Zu Favoriten hinzufügen ...</entry>
-    <entry lang="de" key="IDPM_ADD_TO_SYSTEM_FAVORITES">Zu Systemfavoriten hinzufügen ...</entry>
-    <entry lang="de" key="IDPM_PROPERTIES">Ei&amp;genschaften ...</entry>
+    <entry lang="de" key="IDPM_CHECK_FILESYS">Dateisystem prüfen...</entry>
+    <entry lang="de" key="IDPM_REPAIR_FILESYS">Dateisystem reparieren...</entry>
+    <entry lang="de" key="IDPM_ADD_TO_FAVORITES">Zu Favoriten hinzufügen...</entry>
+    <entry lang="de" key="IDPM_ADD_TO_SYSTEM_FAVORITES">Zu Systemfavoriten hinzufügen...</entry>
+    <entry lang="de" key="IDPM_PROPERTIES">Ei&amp;genschaften...</entry>
     <entry lang="de" key="HIDDEN_VOL_PROTECTION">Verstecktes Volume ist geschützt</entry>
     <entry lang="de" key="NOT_APPLICABLE_OR_NOT_AVAILABLE">Nicht verfügbar</entry>
     <entry lang="de" key="UISTR_YES">Ja</entry>
@@ -997,8 +997,8 @@
     <entry lang="de" key="SIZE_ITEM">Größe:   </entry>
     <entry lang="de" key="PATH_ITEM">Pfad:   </entry>
     <entry lang="de" key="DRIVE_LETTER_ITEM">Laufw.buchstabe:   </entry>
-    <entry lang="de" key="UNSUPPORTED_CHARS_IN_PWD">FEHLER: Das Passwort darf nur ASCII-Zeichen enthalten.\n\nNicht-ASCII-Zeichen im Passwort können dazu führen, dass das Volume nach einer Änderung der Systemkonfiguration nicht eingehängt werden kann. Folgende Zeichen sind zulässig:\n\n  ! " # $ % &amp; ' ( ) * + , - . / 0 1 2 3 4  5 6 7 8 9 : ; &lt; = &gt; ? @ A B C D E F  G H I J K L M N O P Q R S T U V W X  Y Z [ \\ ] ^ _ ` a b c d e f g h i j k l m  n o p q r s t u v w x y z { | } ~</entry>
-    <entry lang="de" key="UNSUPPORTED_CHARS_IN_PWD_RECOM">WARNUNG: Das Passwort enthält Nicht-ASCII-Zeichen. Dies kann nach einer Änderung der Systemkonfiguration dazu führen, dass das Volume nicht eingehängt werden kann.\n\nAlle Nicht-ASCII-Zeichen des Passwortes sollten durch ASCII-Zeichen ersetzt werden („Volume“ -&gt; „Volume-Passwort ändern ...“).\n\nFolgende Zeichen sind ASCII-Zeichen:\n\n  ! " # $ % &amp; ' ( ) * + , - . / 0 1 2 3 4  5 6 7 8 9 : ; &lt; = &gt; ? @ A B C D E F  G H I J K L M N O P Q R S T U V W X  Y Z [ \\ ] ^ _ ` a b c d e f g h i j k l m  n o p q r s t u v w x y z { | } ~</entry>
+    <entry lang="de" key="UNSUPPORTED_CHARS_IN_PWD">FEHLER: Das Passwort darf nur ASCII-Zeichen enthalten.\n\nNicht-ASCII-Zeichen im Passwort können dazu führen, dass das Volume nach einer Änderung der Systemkonfiguration nicht eingehängt werden kann. Folgende Zeichen sind zulässig:\n\n ! " # $ % &amp; ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; &lt; = &gt; ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \\ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~</entry>
+    <entry lang="de" key="UNSUPPORTED_CHARS_IN_PWD_RECOM">WARNUNG: Das Passwort enthält Nicht-ASCII-Zeichen. Dies kann nach einer Änderung der Systemkonfiguration dazu führen, dass das Volume nicht eingehängt werden kann.\n\nAlle Nicht-ASCII-Zeichen des Passwortes sollten durch ASCII-Zeichen ersetzt werden („Volume“ -&gt; „Volume-Passwort ändern...“).\n\nFolgende Zeichen sind ASCII-Zeichen:\n\n ! " # $ % &amp; ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; &lt; = &gt; ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \\ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~</entry>
     <entry lang="de" key="EXE_FILE_EXTENSION_CONFIRM">WARNUNG: Wir empfehlen Ihnen dringend, dass Sie keine Dateierweiterungen für ausführbare Dateien (wie .exe, .sys oder .dll) oder ähnliche Endungen verwenden. Diese Endungen können Windows und Virenscanner dazu bringen, mit dem Container zu interagieren, was wiederum die Leistung des Volumes beeinträchtigt und außerdem zu ernsthaften Problemen führen kann.\n\nWir empfehlen Ihnen, dass Sie die Endung auf „.hc“ ändern.\n\nSind Sie sicher, dass Sie diese problematische Dateiendung behalten möchten?</entry>
     <entry lang="de" key="EXE_FILE_EXTENSION_MOUNT_WARNING">WARNUNG: Dieser Container hat eine Dateiendung, die von Windows für ausführbare Dateien verwendet wird (u. a. .exe, .sys oder .dll) oder eine andere problematische Dateiendung. Dies wird sehr wahrscheinlich Probleme mit Windows und Virenscannern machen, da diese mit dem Container interagieren möchten. Dies wird die Leistung beeinflussen und kann zu anderen schwerwiegenden Problemen führen.\n\nWir empfehlen Ihnen deshalb, die Endung in „.hc“ ändern, nachdem Sie den Container wieder entfernt haben.</entry>
     <entry lang="de" key="HOMEPAGE">Webseite </entry>
@@ -1009,7 +1009,7 @@
     <entry lang="de" key="VOLUME_TOO_LARGE_FOR_WINXP">ACHTUNG: Windows XP unterstützt keine Dateien, die größer als 2048 GB sind. Es zeigt die Fehlermeldung „Nicht genügend Speicherplatz auf dem Datenträger“ an. Deshalb können Sie kein dateibasiertes VeraCrypt-Volume größer als 2048 GB unter Windows XP erstellen.\n\nBitte beachten Sie, dass es trotzdem möglich ist, das gesamte Laufwerk zu verschlüsseln oder ein partitionsbasiertes Volume größer als 2048 GB zu erstellen.</entry>
     <entry lang="de" key="FREE_SPACE_FOR_WRITING_TO_OUTER_VOLUME">WARNUNG: Wenn Sie nachträglich noch weitere Daten/Dateien im äußeren Volume speichern möchten, dann sollten Sie eine kleinere Größe des versteckten Volumes in Betracht ziehen.\n\nMöchten Sie tatsächlich mit der von Ihnen angegebenen Größe fortsetzen?</entry>
     <entry lang="de" key="NO_VOLUME_SELECTED">Es wurde kein Volume ausgewählt.\n\nKlicken Sie bitte auf „Datenträger“ oder „Datei“ und wählen Sie ein VeraCrypt-Volume aus.</entry>
-    <entry lang="de" key="NO_SYSENC_PARTITION_SELECTED">Keine Partition ausgewählt.\n\nKlicken Sie „Datenträger ...“, um eine getrennte Partition zu wählen, die sonst Pre-Boot-Authentifikation voraussetzt (z. B. eine Partition auf einem verschlüsselten Systemlaufwerk mit einem Betriebssystem darauf, das gerade nicht läuft, oder die verschlüsselte Systempartition eines anderen Betriebssystems).\n\nHinweis: Die ausgewählte Partition wird als reguläres VeraCrypt-Volume ohne Pre-Boot-Authentifikation eingehängt. Das ist hilfreich für Sicherungs- oder Reparaturvorgänge.</entry>
+    <entry lang="de" key="NO_SYSENC_PARTITION_SELECTED">Keine Partition ausgewählt.\n\nKlicken Sie „Datenträger...“, um eine getrennte Partition zu wählen, die sonst Pre-Boot-Authentifikation voraussetzt (z. B. eine Partition auf einem verschlüsselten Systemlaufwerk mit einem Betriebssystem darauf, das gerade nicht läuft, oder die verschlüsselte Systempartition eines anderen Betriebssystems).\n\nHinweis: Die ausgewählte Partition wird als reguläres VeraCrypt-Volume ohne Pre-Boot-Authentifikation eingehängt. Das ist hilfreich für Sicherungs- oder Reparaturvorgänge.</entry>
     <entry lang="de" key="CONFIRM_SAVE_DEFAULT_KEYFILES">WARNUNG: Wenn Standardschlüsseldateien festgelegt und aktiviert sind, dann können Volumes, die diese nicht verwenden, nicht eingehängt werden. Daher sollten Sie, nachdem Sie die Standardschlüsseldateien aktiviert haben, das Häkchen bei „Schlüsseldateien verwenden“ (unterhalb des Passwort-Eingabefeldes) entfernen, sobald Sie solche Volumes einhängen möchten.\n\nSind Sie sicher, dass Sie die Schlüsseldateien/-pfade als Standard speichern möchten?</entry>
     <entry lang="de" key="HK_AUTOMOUNT_DEVICES">Alle Datenträger-Volumes automatisch einhängen</entry>
     <entry lang="de" key="HK_UNMOUNT_ALL">Alle Volumes trennen</entry>
@@ -1060,8 +1060,8 @@
     <entry lang="de" key="NO_SYS_ENC_PROCESS_TO_RESUME">Es gibt keinen unterbrochenen Ver- bzw. Entschlüsselungsprozess der Systempartition/des Laufwerks, der fortgesetzt werden kann.\n\nHinweis: Falls Sie einen unterbrochenen Ver- bzw. Entschlüsselungsprozess einer Nicht-Systempartition fortsetzen möchten, wählen Sie\n„Volume“ &gt; „Unterbrochenen Prozess fortsetzen“.</entry>
     <entry lang="de" key="HIDVOL_PROT_BKG_TASK_WARNING">WARNUNG: Der VeraCrypt-Hintergrunddienst ist deaktiviert. Nach dem Beenden von VeraCrypt werden Sie nicht benachrichtigt, sobald eine Beschädigung eines versteckten Volumes verhindert werden konnte.\n\nHinweis: Sie können den Hintergrunddienst jederzeit mit einen Klick der rechten Maustaste auf das VeraCrypt-Symbol im Infobereich (= Systemtray) und durch Auswählen von „Beenden“ beenden.\n\nSoll der VeraCrypt-Hintergrunddienst aktiviert werden?</entry>
     <entry lang="de" key="LANG_PACK_VERSION">Sprachpaket-Version:  %s</entry>
-    <entry lang="de" key="CHECKING_FS">Es wird das Dateisystem des als %s eingehängten VeraCrypt-Volumes überprüft ...</entry>
-    <entry lang="de" key="REPAIRING_FS">Es wird versucht, das Dateisystem des als %s eingehängten VeraCrypt-Volumes zu reparieren ...</entry>
+    <entry lang="de" key="CHECKING_FS">Es wird das Dateisystem des als %s eingehängten VeraCrypt-Volumes überprüft...</entry>
+    <entry lang="de" key="REPAIRING_FS">Es wird versucht, das Dateisystem des als %s eingehängten VeraCrypt-Volumes zu reparieren...</entry>
     <entry lang="de" key="WARN_64_BIT_BLOCK_CIPHER">WARNUNG: Dieses Volume ist mit einem veralteten Verschlüsselungsalgorithmus verschlüsselt.\n\nAlle 64-Bit-Block-Verschlüsselungsalgorithmen (z. B. Blowfish, CAST-128 oder Triple DES) werden allmählich eingestellt. Es wird zwar mit zukünftigen VeraCrypt-Versionen möglich sein, diese Volumes einzuhängen. Es werden aber keine Verbesserungen an der Implementierung der veralteten Verschlüsselungsalgorithmen vorgenommen. Es ist daher ratsam, ein neues VeraCrypt-Volume mit einem 128-Bit-Block-Verschlüsselungsalgorithmus zu erstellen (z. B. AES, Serpent, Twofish) und sämtliche Dateien dieses Volumes auf das neue Volume zu übertragen.</entry>
     <entry lang="de" key="SYS_AUTOMOUNT_DISABLED">Das Betriebssystem ist so konfiguriert, dass neue Volumes nicht automatisch eingehängt werden. Möglicherweise können VeraCrypt-Volumes, die sich auf Datenträgern oder Partitionen befinden, nicht eingehängt werden. Das automatische Einhängen der Volumes kann mit dem Befehl\n\nmountvol.exe /E\n\nund anschließendem Neustart des Computers aktiviert werden.</entry>
     <entry lang="de" key="SYS_ASSIGN_DRIVE_LETTER">Weisen Sie bitte dem Datenträger oder der Partition einen Laufwerksbuchstaben zu, bevor Sie weitermachen („Systemsteuerung“ &gt; „System und Wartung“ &gt; „Verwaltung“ &gt; „Festplattenpartitionen erstellen und formatieren“).\n\nBeachten Sie, dass dies eine Anforderung des Betriebssystems ist.</entry>
@@ -1215,7 +1215,7 @@
     <entry lang="de" key="DECOY_OS_INSTRUCTIONS_PORTION_3">1) Aus Sicherheitsgründen müssen Sie Ihren Computer ausschalten und ihn mehrere Minuten ausgeschaltet lassen (je länger, umso besser). Dies ist notwendig, um den Speicher zu leeren, der sensible Daten enthalten kann. Schalten Sie dann Ihren Computer wieder an, aber starten Sie nicht vom versteckten System aus.\n\n</entry>
     <entry lang="de" key="DECOY_OS_INSTRUCTIONS_PORTION_4">2) Installieren Sie Windows auf der Partition, dessen Inhalt gelöscht wurde (d. h. auf der Partition, auf der das Originalsystem installiert war, dessen Klon das versteckte System ist).\n\nWICHTIG: WENN SIE BEGINNEN, DAS KÖDER-SYSTEM ZU INSTALLIEREN, WIRD ES *NICHT* MÖGLICH SEIN, DAS VERSTECKTE SYSTEM ZU STARTEN (weil der VeraCrypt-Bootloader vom Windows-Systeminstallationsprogramm gelöscht wird). DAS IST NORMAL UND ZU ERWARTEN. BITTE BEWAHREN SIE RUHE. SIE WERDEN DAS VERSTECKTE SYSTEM WIEDER STARTEN KÖNNEN, SOBALD SIE BEGINNEN, DAS KÖDER-SYSTEM ZU VERSCHLÜSSELN (weil VeraCrypt dann automatisch den Bootloader wieder installieren wird).\n\nWICHTIG: Die Größe der Köder-Systempartition muss der des versteckten Systems entsprechen. Diese Voraussetzung ist jetzt erfüllt. Zudem dürfen Sie keine Partition zwischen der Köder-Systempartition und der Partition des versteckten Systems erstellen.\n\n</entry>
     <entry lang="de" key="DECOY_OS_INSTRUCTIONS_PORTION_5">3) Starten Sie das Köder-System (das Sie in Schritt 2 installiert haben) und installieren Sie VeraCrypt darauf.\n\nBedenken Sie, dass das Köder-System niemals sensible Daten enthalten darf.\n\n</entry>
-    <entry lang="de" key="DECOY_OS_INSTRUCTIONS_PORTION_6">4) Starten Sie VeraCrypt auf dem Köder-System und wählen Sie „System“ &gt; „Systempartition/Systemlaufwerk verschlüsseln ...“. Der Assistent zum Erstellen eines VeraCrypt-Volumes sollte dann starten.\n\nFühren Sie die folgenden Schritte im Assistenten zum Erstellen eines VeraCrypt-Volumes aus.\n\n</entry>
+    <entry lang="de" key="DECOY_OS_INSTRUCTIONS_PORTION_6">4) Starten Sie VeraCrypt auf dem Köder-System und wählen Sie „System“ &gt; „Systempartition/Systemlaufwerk verschlüsseln...“. Der Assistent zum Erstellen eines VeraCrypt-Volumes sollte dann starten.\n\nFühren Sie die folgenden Schritte im Assistenten zum Erstellen eines VeraCrypt-Volumes aus.\n\n</entry>
     <entry lang="de" key="DECOY_OS_INSTRUCTIONS_PORTION_7">5) Im Assistenten zum Erstellen eines VeraCrypt-Volumes wählen Sie NICHT die Option „Versteckt“! Lassen Sie die Option „Normal“ ausgewählt und klicken Sie auf „Weiter“.\n\n</entry>
     <entry lang="de" key="DECOY_OS_INSTRUCTIONS_PORTION_8">6) Wählen Sie die Option „Die Windows Systempartition verschlüsseln“; und klicken Sie auf „Weiter“.\n\n</entry>
     <entry lang="de" key="DECOY_OS_INSTRUCTIONS_PORTION_9">7) Falls nur das versteckte Betriebssystem und das Köder-System auf dem Computer installiert sind, wählen Sie nun „Ein Betriebssystem“. Wenn mehr als diese beiden Systeme auf dem Computer installiert sind, wählen Sie „Mehrere Betriebssysteme“. Klicken Sie dann auf „Weiter“.\n\n</entry>
@@ -1241,7 +1241,7 @@
     <entry lang="de" key="SYSTEM_ENCRYPTION_NOT_COMPLETED">Der Ver- bzw. Entschlüsselungsprozess für die Systempartition/für das Laufwerk wurde nicht abgeschlossen. Bitte warten Sie, bis er abgeschlossen ist, bevor Sie fortfahren.</entry>
     <entry lang="de" key="ERR_ENCRYPTION_NOT_COMPLETED">FEHLER: Der Verschlüsselungsprozess von der Partition/dem Laufwerk wurde nicht abgeschlossen. Dieser muss zuerst abgeschlossen werden.</entry>
     <entry lang="de" key="ERR_NONSYS_INPLACE_ENC_INCOMPLETE">FEHLER: Der Verschlüsselungsprozess von der Partition/dem Laufwerk wurde nicht abgeschlossen. Dieser muss zuerst abgeschlossen werden.\n\nHinweis: Um den Prozess fortzusetzen, wählen Sie „Volume“ &gt; „Unterbrochenen Prozess fortsetzen“ in der Menüleiste des VeraCrypt-Hauptfensters.</entry>
-    <entry lang="de" key="ERR_SYS_HIDVOL_HEAD_REENC_MODE_WRONG">Das Passwort ist korrekt, VeraCrypt hat erfolgreich die Volume-Kopfdaten entschlüsselt und festgestellt, dass dieses Volume ein verstecktes System-Volume ist. Allerdings können Sie die Kopfdaten eines versteckten System-Volumes auf diese Weise nicht ändern.\n\nUm das Passwort für ein verstecktes System-Volume zu ändern, starten Sie das Betriebssystem, das sich im versteckten Volume befindet, und wählen Sie dann „System“ &gt; „Passwort ändern ...“ in der Menüleiste des VeraCrypt-Hauptfensters aus.\n\nUm den Algorithmus für die Kopfdatenschlüsselberechnung festzulegen, starten Sie das versteckte Betriebssystem und wählen dann „System“ &gt; „Algorithmus für Kopfdatenschlüsselberechnung ändern ...“ aus.</entry>
+    <entry lang="de" key="ERR_SYS_HIDVOL_HEAD_REENC_MODE_WRONG">Das Passwort ist korrekt, VeraCrypt hat erfolgreich die Volume-Kopfdaten entschlüsselt und festgestellt, dass dieses Volume ein verstecktes System-Volume ist. Allerdings können Sie die Kopfdaten eines versteckten System-Volumes auf diese Weise nicht ändern.\n\nUm das Passwort für ein verstecktes System-Volume zu ändern, starten Sie das Betriebssystem, das sich im versteckten Volume befindet, und wählen Sie dann „System“ &gt; „Passwort ändern...“ in der Menüleiste des VeraCrypt-Hauptfensters aus.\n\nUm den Algorithmus für die Kopfdatenschlüsselberechnung festzulegen, starten Sie das versteckte Betriebssystem und wählen dann „System“ &gt; „Algorithmus für Kopfdatenschlüsselberechnung ändern...“ aus.</entry>
     <entry lang="de" key="CANNOT_DECRYPT_HIDDEN_OS">VeraCrypt unterstützt gegenwärtig nicht die Entschlüsselung einer versteckten Systempartition.\n\nHinweis: Wenn Sie die Köder-Systempartition entschlüsseln möchten, dann starten Sie das Köder-System und wählen dann „System“ &gt; „Systempartition/Systemlaufwerk dauerhaft entschlüsseln“ in der Menüleiste des VeraCrypt-Hauptfensters aus.</entry>
     <entry lang="de" key="ERR_PARAMETER_INCORRECT">FEHLER: Falscher/ungültiger Parameter.</entry>
     <entry lang="de" key="DEVICE_SELECTED_IN_NON_DEVICE_MODE">Sie haben eine Partition oder ein Laufwerk ausgewählt, aber der Assistent, den Sie gewählt haben, ist nur für Containerdateien geeignet.\n\nMöchten Sie den Assistenten wechseln?</entry>
@@ -1256,8 +1256,8 @@
     <entry lang="de" key="UPDATE_TC_IN_DECOY_OS_FIRST">ACHTUNG: Aus Sicherheitsgründen sollten Sie VeraCrypt zuerst auf dem Köder-System aktualisieren, bevor Sie es auf dem versteckten Betriebssystem aktualisieren.\n\nUm dies zu tun, starten Sie das Köder-System und starten das VeraCrypt-Installationsprogramm in diesem System. Starten Sie danach das versteckte Betriebssystem und starten Sie ebenfalls das VeraCrypt-Installationsprogramm.\n\nHinweis: das Köder-System und das versteckte System teilen sich einen Bootloader. Wenn Sie VeraCrypt nur auf dem versteckten Betriebssystem aktualisieren, enthält das Köder-System unterschiedliche Versionen des VeraCrypt-Treibers und der VeraCrypt-Anwendungen. Solch ein Unterschied kann auf die Existenz eines versteckten Betriebssystems auf dem Computer hinweisen.\n\nMöchten Sie fortfahren?</entry>
     <entry lang="de" key="UPDATE_TC_IN_HIDDEN_OS_TOO">Die Versionsnummer des VeraCrypt-Bootloaders, der dieses Betriebssystem gestartet hat, unterscheidet sich von der Versionsnummer des VeraCrypt-Treibers (und von den VeraCrypt-Anwendungen) der auf diesem System installiert ist.\n\nSie sollten das VeraCrypt-Installationsprogramm ausführen (dessen Versionsnummer ist die gleiche wie die des VeraCrypt-Bootloaders), um VeraCrypt auf diesem Betriebssystem zu aktualisieren.</entry>
     <entry lang="de" key="BOOT_LOADER_VERSION_DIFFERENT_FROM_DRIVER_VERSION">Die Versionsnummer des VeraCrypt-Bootloaders, der dieses Betriebssystem gestartet hat, stimmt nicht mit der Versionsnummer des installierten VeraCrypt-Treibers (und der VeraCrypt-Anwendungen) überein. Bitte beachten Sie, dass ältere Versionen Fehler enthalten können, die in neueren Versionen behoben sind.\n\nWenn Sie nicht von dem VeraCrypt-Rettungsdatenträger gestartet haben, sollten Sie VeraCrypt neu installieren oder auf die neueste stabile Version aktualisieren. Der Bootloader wird dabei ebenfalls aktualisiert.\n\nWenn Sie von dem VeraCrypt-Rettungsdatenträger gestartet haben, sollten Sie diese aktualisieren („System“ &gt; „Rettungsdatenträger erstellen“).</entry>
-    <entry lang="de" key="BOOT_LOADER_UPGRADE_OK">Der VeraCrypt-Bootloader wurde erfolgreich aktualisiert.\n\nEs wird dringend empfohlen, einen neuen Rettungsdatenträger zu erstellen (welcher die aktuelle Version des VeraCrypt-Bootloaders enthält) durch Klicken auf „System“ &gt; „Rettungsdatenträger erstellen ...“ nach einem Neustart des Computers.</entry>
-    <entry lang="de" key="BOOT_LOADER_UPGRADE_OK_HIDDEN_OS">Der VeraCrypt-Bootloader wurde aktualisiert.\n\nEs wird dringend empfohlen, dass Sie das Köder-Betriebssystem starten und dann einen neuen VeraCrypt-Rettungsdatenträger erstellen (der die neue Version des VeraCrypt-Bootloaders enthält), indem Sie „System“ &gt; „Rettungsdatenträger erstellen ...“ wählen.</entry>
+    <entry lang="de" key="BOOT_LOADER_UPGRADE_OK">Der VeraCrypt-Bootloader wurde erfolgreich aktualisiert.\n\nEs wird dringend empfohlen, einen neuen Rettungsdatenträger zu erstellen (welcher die aktuelle Version des VeraCrypt-Bootloaders enthält) durch Klicken auf „System“ &gt; „Rettungsdatenträger erstellen...“ nach einem Neustart des Computers.</entry>
+    <entry lang="de" key="BOOT_LOADER_UPGRADE_OK_HIDDEN_OS">Der VeraCrypt-Bootloader wurde aktualisiert.\n\nEs wird dringend empfohlen, dass Sie das Köder-Betriebssystem starten und dann einen neuen VeraCrypt-Rettungsdatenträger erstellen (der die neue Version des VeraCrypt-Bootloaders enthält), indem Sie „System“ &gt; „Rettungsdatenträger erstellen...“ wählen.</entry>
     <entry lang="de" key="BOOT_LOADER_UPGRADE_FAILED">Es ist ein Fehler beim Aktualisieren des VeraCrypt-Bootloaders aufgetreten.</entry>
     <entry lang="de" key="SYS_DRIVE_SIZE_PROBE_TIMEOUT">VeraCrypt konnte die reale Größe des Systemlaufwerks nicht ermitteln und folglich wird die Größe verwendet, die das Betriebssystem angibt (die kleiner sein kann als die reale Größe). Beachten Sie auch, dass dies kein Fehler in VeraCrypt ist.</entry>
     <entry lang="de" key="HIDDEN_SECTOR_DETECTION_FAILED_PREVIOUSLY">WARNUNG: Möglicherweise hat VeraCrypt bereits versucht, versteckte Sektoren auf diesem Systemlaufwerk zu erkennen. Wenn Sie Probleme während des vorherigen Erkennungsprozesses hatten, so können Sie diese vermeiden, indem Sie diesmal die Erkennung von versteckten Sektoren überspringen. Bedenken Sie dabei, dass VeraCrypt die vom Betriebssystem angegebene Größe verwendet (die vielleicht kleiner ist als die tatsächliche Größe).\n\nBeachten Sie, das Problem wurde nicht wegen eines Fehlers in VeraCrypt verursacht.</entry>
@@ -1268,11 +1268,11 @@
     <entry lang="de" key="ZEROED_BAD_SECTOR_COUNT">Hinweis: VeraCrypt hat den Inhalt der %I64d nicht lesbaren Sektoren (%s) mit verschlüsselten NULL-Textblöcken ersetzt.</entry>
     <entry lang="de" key="SKIPPED_BAD_SECTOR_COUNT">Hinweis: VeraCrypt hat den Inhalt der %I64d nicht lesbaren Sektoren (%s) mit zufälligen Daten ersetzt.</entry>
     <entry lang="de" key="ENTER_TOKEN_PASSWORD">Passwort/PIN eingeben für Token „%s“:</entry>
-    <entry lang="de" key="PKCS11_LIB_LOCATION_HELP">Damit VeraCrypt auf eine(n) Token/Smartcard zugreifen kann, müssen Sie zuerst eine PKCS #11-Bibliothek installieren. Diese kann mit dem Gerät mitgeliefert sein oder sie steht zum Herunterladen auf der Webseite des Herstellers oder eines Drittherstellers bereit.\n\nNach der Installation können Sie die Bibliothek durch Klicken auf „Bibliothek wählen ...“ selber wählen oder durch Klicken auf „Bibliothek automatisch erkennen“ im Windows-Systemverzeichnis suchen lassen.</entry>
+    <entry lang="de" key="PKCS11_LIB_LOCATION_HELP">Damit VeraCrypt auf eine(n) Token/Smartcard zugreifen kann, müssen Sie zuerst eine PKCS #11-Bibliothek installieren. Diese kann mit dem Gerät mitgeliefert sein oder sie steht zum Herunterladen auf der Webseite des Herstellers oder eines Drittherstellers bereit.\n\nNach der Installation können Sie die Bibliothek durch Klicken auf „Bibliothek wählen...“ selber wählen oder durch Klicken auf „Bibliothek automatisch erkennen“ im Windows-Systemverzeichnis suchen lassen.</entry>
     <entry lang="de" key="SELECT_PKCS11_MODULE_HELP">Hinweis: Für den Dateinamen und den Speicherort der PKCS #11-Bibliothek, die für Ihren Sicherheitstoken oder Ihre Smartcard installiert wurde, lesen Sie bitte die Dokumentation, die mit dem Token, der Smartcard oder Dritthersteller-Software mitgeliefert wurde.\n\nKlicken Sie auf „OK“, um den Pfad und Dateinamen zu wählen.</entry>
-    <entry lang="de" key="NO_PKCS11_MODULE_SPECIFIED">Um VeraCrypt auf einen Sicherheitstoken oder eine Smartcard zugreifen zu lassen, müssen Sie zuerst eine PKCS #11-Bibliothek für den Token/die Smartcard auswählen. Wählen Sie dazu „Einstellungen“ &gt; „Sicherheitstokens ...“.</entry>
-    <entry lang="de" key="PKCS11_MODULE_INIT_FAILED">Die PKCS #11-Bibliothek konnte nicht initialisiert werden.\n\nStellen Sie bitte sicher, dass der angegebene Pfad und Dateiname auf eine gültige PKCS #11-Bibliothek verweist. Um den Pfad und Dateiname für eine PKCS #11-Bibliothek anzugeben, klicken Sie auf „Einstellungen“ &gt; „Sicherheitstokens ...“.</entry>
-    <entry lang="de" key="PKCS11_MODULE_AUTO_DETECTION_FAILED">Es wurde keine PKCS #11-Bibliothek im Windows-Systemverzeichnis gefunden.\n\nBitte stellen Sie sicher, dass eine PKCS #11-Bibliothek für Ihren Sicherheitstoken (oder für Ihre Smartcard) installiert ist. Solch eine Bibliothek kann mit dem Token/der Smartcard mitgeliefert sein oder zum Herunterladen auf der Webseite des Herstellers oder von Drittherstellern bereitstehen. Wenn sie in einem anderen Verzeichnis installiert ist als im Windows-Verzeichnis, dann klicken Sie auf „Bibliothek wählen ...“, um die Bibliothek anzugeben (z. B. im Ordner, in dem die Software für den Token/die Smartcard installiert ist).</entry>
+    <entry lang="de" key="NO_PKCS11_MODULE_SPECIFIED">Um VeraCrypt auf einen Sicherheitstoken oder eine Smartcard zugreifen zu lassen, müssen Sie zuerst eine PKCS #11-Bibliothek für den Token/die Smartcard auswählen. Wählen Sie dazu „Einstellungen“ &gt; „Sicherheitstokens...“.</entry>
+    <entry lang="de" key="PKCS11_MODULE_INIT_FAILED">Die PKCS #11-Bibliothek konnte nicht initialisiert werden.\n\nStellen Sie bitte sicher, dass der angegebene Pfad und Dateiname auf eine gültige PKCS #11-Bibliothek verweist. Um den Pfad und Dateiname für eine PKCS #11-Bibliothek anzugeben, klicken Sie auf „Einstellungen“ &gt; „Sicherheitstokens...“.</entry>
+    <entry lang="de" key="PKCS11_MODULE_AUTO_DETECTION_FAILED">Es wurde keine PKCS #11-Bibliothek im Windows-Systemverzeichnis gefunden.\n\nBitte stellen Sie sicher, dass eine PKCS #11-Bibliothek für Ihren Sicherheitstoken (oder für Ihre Smartcard) installiert ist. Solch eine Bibliothek kann mit dem Token/der Smartcard mitgeliefert sein oder zum Herunterladen auf der Webseite des Herstellers oder von Drittherstellern bereitstehen. Wenn sie in einem anderen Verzeichnis installiert ist als im Windows-Verzeichnis, dann klicken Sie auf „Bibliothek wählen...“, um die Bibliothek anzugeben (z. B. im Ordner, in dem die Software für den Token/die Smartcard installiert ist).</entry>
     <entry lang="de" key="NO_TOKENS_FOUND">Kein Sicherheitstoken gefunden.\n\nBitte stellen Sie sicher, dass Ihr Sicherheitstoken mit Ihrem Computer verbunden ist und der richtige Gerätetreiber für Ihren Sicherheitstoken installiert ist.</entry>
     <entry lang="de" key="TOKEN_KEYFILE_NOT_FOUND">Sicherheitstoken-Schlüsseldatei nicht gefunden.</entry>
     <entry lang="de" key="TOKEN_KEYFILE_ALREADY_EXISTS">Eine Sicherheitstoken-Schlüsseldatei mit demselben Namen existiert bereits.</entry>
@@ -1286,15 +1286,15 @@
     <entry lang="de" key="TOKEN_SLOT_ID">Steckplatz</entry>
     <entry lang="de" key="TOKEN_NAME">Tokenname</entry>
     <entry lang="de" key="TOKEN_DATA_OBJECT_LABEL">Dateiname</entry>
-    <entry lang="de" key="BOOT_PASSWORD_CACHE_KEYBOARD_WARNING">WICHTIG: Bitte beachten Sie, dass Pre-Boot-Authentifikationspasswörter stets mit einer Standard US-Tastaturbelegung geschrieben werden. Deshalb kann es unmöglich sein, ein Volume, dessen Passwort mit einer anderen Tastaturbelegung erstellt wurde, mit einem Pre-Boot-Authentifikationspasswort einzuhängen. Dies ist kein VeraCrypt-Fehler. Um solch ein Volume mit einem Pre-Boot-Authentifikationspasswort einzuhängen, folgen Sie diesen Schritten:\n\n1) Klicken Sie „Datei“ oder „Datenträger“ und wählen Sie das Volume aus.\n2) Wählen Sie „Volume“ &gt; „Volume-Passwort ändern ...“.\n3) Geben Sie das derzeitige Passwort für das Volume ein.\n4) Ändern Sie die Tastaturbelegung auf „English (US)“, indem Sie auf das Sprachsymbol in der Windows-Taskleiste klicken und „EN English (United States)“ wählen. Falls das Symbol nicht angezeigt wird, gehen Sie in „Systemsteuerung“ &gt; „Regions- und Sprachoptionen“. Klicken Sie auf „Tastatur ändern“ und wählen Sie „Englisch (US)“.\n5) Geben Sie nun in VeraCrypt das neue Pre-Boot-Authentifikationspasswort ein.\n6) Bestätigen Sie das neue Pre-Boot-Authentifikationspasswort und klicken Sie „OK“.\n7) ACHTUNG: Bitte denken Sie daran, dass das Volume-Passwort IMMER mit der US-Tastaturbelegung eingegeben werden muss, wenn Sie diese Schritte befolgen (in der Pre-Boot-Umgebung ist automatisch US-Englisch eingestellt).</entry>
+    <entry lang="de" key="BOOT_PASSWORD_CACHE_KEYBOARD_WARNING">WICHTIG: Bitte beachten Sie, dass Pre-Boot-Authentifikationspasswörter stets mit einer Standard US-Tastaturbelegung geschrieben werden. Deshalb kann es unmöglich sein, ein Volume, dessen Passwort mit einer anderen Tastaturbelegung erstellt wurde, mit einem Pre-Boot-Authentifikationspasswort einzuhängen. Dies ist kein VeraCrypt-Fehler. Um solch ein Volume mit einem Pre-Boot-Authentifikationspasswort einzuhängen, folgen Sie diesen Schritten:\n\n1) Klicken Sie „Datei“ oder „Datenträger“ und wählen Sie das Volume aus.\n2) Wählen Sie „Volume“ &gt; „Volume-Passwort ändern...“.\n3) Geben Sie das derzeitige Passwort für das Volume ein.\n4) Ändern Sie die Tastaturbelegung auf „English (US)“, indem Sie auf das Sprachsymbol in der Windows-Taskleiste klicken und „EN English (United States)“ wählen. Falls das Symbol nicht angezeigt wird, gehen Sie in „Systemsteuerung“ &gt; „Regions- und Sprachoptionen“. Klicken Sie auf „Tastatur ändern“ und wählen Sie „Englisch (US)“.\n5) Geben Sie nun in VeraCrypt das neue Pre-Boot-Authentifikationspasswort ein.\n6) Bestätigen Sie das neue Pre-Boot-Authentifikationspasswort und klicken Sie „OK“.\n7) ACHTUNG: Bitte denken Sie daran, dass das Volume-Passwort IMMER mit der US-Tastaturbelegung eingegeben werden muss, wenn Sie diese Schritte befolgen (in der Pre-Boot-Umgebung ist automatisch US-Englisch eingestellt).</entry>
     <entry lang="de" key="SYS_FAVORITES_KEYBOARD_WARNING">Systemfavoriten-Volumes werden mit dem Pre-Boot-Authentifikationspasswort eingehängt. Wenn irgendein Systemfavoriten-Volume ein anderes Passwort nutzt, wird es nicht eingehängt.</entry>
     <entry lang="de" key="SYS_FAVORITES_ADMIN_ONLY_INFO">Bitte beachten Sie: Um zu verhindern, dass normale VeraCrypt-Vorgänge wie „Alle trennen“, „Automatisches Trennen“ usw. störenden Einfluss auf Systemfavoriten-Volumes nehmen, sollten Sie die Option „Nur Administratoren erlauben, Systemfavoriten in VeraCrypt zu sehen und zu trennen“ aktivieren. Wenn VeraCrypt ohne Administratorrechte ausgeführt wird (Standard ab Windows Vista), werden Systemfavoriten-Volumes zusätzlich nicht in der Laufwerksliste von VeraCrypt angezeigt.</entry>
     <entry lang="de" key="SYS_FAVORITES_ADMIN_ONLY_WARNING">WICHTIG: Wenn Sie diese Option aktivieren und VeraCrypt ohne Administratorrechte ausgeführt wird, werden eingehängte Systemfavoriten-Volumes NICHT im VeraCrypt-Anwendungsfenster angezeigt und können nicht getrennt werden. Deshalb müssen Sie VeraCrypt mit Administratorrechten ausführen, wenn Sie ein Systemfavoriten-Volume einhängen oder entfernen möchten (Rechtsklick auf das VeraCrypt-Icon im Startmenü und „Als Administrator ausführen“ wählen).\nDieselben Einschränkungen bestehen für die Funktion „Alle trennen“, die Tastenkombination „Alle trennen“, die Funktion „Automatisches Trennen“ usw.</entry>
     <entry lang="de" key="SETTING_REQUIRES_REBOOT">Bitte beachten Sie, dass diese Änderung erst nach einem Neustart des Betriebssystems wirksam wird.</entry>
     <entry lang="de" key="COMMAND_LINE_ERROR">Fehler bei der Syntaxanalyse der Kommandozeile.</entry>
     <entry lang="de" key="RESCUE_DISK">Rettungsdatenträger</entry>
-    <entry lang="de" key="SELECT_FILE_AND_MOUNT">&amp;Datei auswählen und einhängen ...</entry>
-    <entry lang="de" key="SELECT_DEVICE_AND_MOUNT">Laufwerk auswä&amp;hlen und einhängen ...</entry>
+    <entry lang="de" key="SELECT_FILE_AND_MOUNT">&amp;Datei auswählen und einhängen...</entry>
+    <entry lang="de" key="SELECT_DEVICE_AND_MOUNT">Laufwerk auswä&amp;hlen und einhängen...</entry>
     <entry lang="de" key="DISABLE_NONADMIN_SYS_FAVORITES_ACCESS">Nur Administratoren erlauben, Systemfavoriten in VeraCrypt zu sehen und zu trennen</entry>
     <entry lang="de" key="MOUNT_SYSTEM_FAVORITES_ON_BOOT">Systemfavoriten-Volumes einhängen, wenn Windows startet (am Anfang der Startphase)</entry>
     <entry lang="de" key="MOUNTED_VOLUME_DIRTY">WARNUNG: Das Dateisystem auf dem Volume, eingehängt als „%s“, wurde nicht ordnungsgemäß getrennt und könnte dadurch Fehler enthalten. Das Verwenden eines beschädigten Dateisystems kann zu Datenverlusten bzw. Datenbeschädigungen führen.\n\nHinweis: Bevor Sie ein Laufwerk physikalisch entfernen oder ausschalten (z. B. ein USB-Stick oder eine externe Festplatte), auf denen ein eingehängtes VeraCrypt-Volume ist, so sollten Sie immer zuerst das Volume in VeraCrypt trennen.\n\n\nMöchten Sie, dass Windows auf dem Dateisystem nach Fehlern sucht und diese behebt (falls vorhanden)?</entry>
@@ -1393,7 +1393,7 @@
     <entry lang="de" key="IDC_FAVORITE_USE_VOLUME_ID">Volume-Kennung zum Einhängen des Favoriten verwenden</entry>
     <entry lang="de" key="VOLUME_ID_INVALID">Die Volume-Kennung ist ungültig</entry>
     <entry lang="de" key="VOLUME_ID_NOT_FOUND">Mit der angegebenen Kennung wurde kein Volume auf dem System gefunden</entry>
-    <entry lang="de" key="IDPM_COPY_VALUE_TO_CLIPBOARD">Wert in die Zwischenablage kopieren ...</entry>
+    <entry lang="de" key="IDPM_COPY_VALUE_TO_CLIPBOARD">Wert in die Zwischenablage kopieren...</entry>
     <entry lang="de" key="IDC_DISABLE_BOOT_LOADER_PIM_PROMPT">Im Pre-Boot-Authentifikationsbildschirm keinen PIM abfragen</entry>
     <entry lang="de" key="DISABLE_BOOT_LOADER_PIM_PROMPT">WARNUNG: Sie sollten nicht vergessen, dass der PIM-Wert unverschlüsselt auf der Festplatte gespeichert wird, wenn Sie diese Option aktivieren.\n\nSind Sie sicher, dass Sie diese Option aktivieren möchten?</entry>
     <entry lang="de" key="PIM_TOO_BIG">Der größtmögliche Wert für den PIM (Persönlicher Iterationsmultiplikator) ist 2147468.</entry>
@@ -1430,7 +1430,7 @@
     <entry lang="de" key="PASSWORD_MAXLENGTH_REACHED">Passwort hat bereits seine maximale Länge von %d Zeichen erreicht.\nEs ist kein zusätzliches Zeichen erlaubt.</entry>
     <entry lang="de" key="IDC_SELECT_LANGUAGE_LABEL">Wählen Sie die Sprache aus, die während der Installation benutzt werden soll:</entry>
     <entry lang="de" key="VOLUME_TOO_LARGE_FOR_HOST">FEHLER: Der Datei-Container ist größer als der verfügbare freie Speicherplatz auf der Festplatte.</entry>
-    <entry lang="de" key="IDC_ALLOW_WINDOWS_DEFRAG">Defragmentierung von Nicht-Systempartitionen/-laufwerken durch Windows-Defragmentier. erlauben</entry>    
+    <entry lang="de" key="IDC_ALLOW_WINDOWS_DEFRAG">Defragmentierung von Nicht-Systempartitionen/-laufwerken durch Windows-Defragmentier. erlauben</entry>
     <entry lang="de" key="CONFIRM_ALLOW_WINDOWS_DEFRAG">WARNUNG: Defragmentierung von Nicht-Systempartitionen/-laufwerken kann Metadaten über ihren Inhalt preisgeben oder Probleme mit versteckten Volumes verursachen, die sie enthalten können.\n\nFortsetzen?</entry>
     <entry lang="de" key="VIRTUAL_DEVICE">Virtuelles Gerät</entry>
     <entry lang="de" key="MOUNTED_VOLUME_NOT_ASSOCIATED">Das ausgewählte eingehängte Volume ist nicht mit seinem Laufwerksbuchstaben in Windows verknüpft und kann daher nicht im Windows Explorer geöffnet werden.</entry>
@@ -1453,7 +1453,7 @@
     <entry lang="de" key="CONFIRM_DISABLE_FAST_STARTUP">WARNUNG: Der Windows-Schnellstart ist aktiviert und es ist bekannt, dass er Probleme bei der Arbeit mit VeraCrypt-Volumes verursacht. Es wird empfohlen, ihn für eine bessere Sicherheit und Benutzerfreundlichkeit zu deaktivieren.\n\nMöchten Sie den Windows-Schnellstart deaktivieren?</entry>
     <entry lang="de" key="QUICK_FORMAT_HELP">Damit das neue Volume im Betriebssystem eingehängt werden kann, muss es mit einem Dateisystem formatiert werden. Bitte wählen Sie einen Typ aus.\n\nWenn das Volume auf einem Laufwerk oder einer Partition liegt, kann „Schnellformatierung“ gewählt werden, um die Verschlüsselung des freien Speicherplatzes zu überspringen.</entry>
     <entry lang="de" key="IDC_ENABLE_HARDWARE_ENCRYPTION_NEG">AES-Verschlüsselung durch Nutzung der AES-Befehle des Prozessors nicht beschleunigen</entry>
-    <entry lang="de" key="IDM_ADD_ALL_VOLUME_TO_FAVORITES">Alle eingehängten Volumes zu Favoriten hinzufügen ...</entry>
+    <entry lang="de" key="IDM_ADD_ALL_VOLUME_TO_FAVORITES">Alle eingehängten Volumes zu Favoriten hinzufügen...</entry>
     <entry lang="de" key="TASKICON_PREF_MENU_ITEMS">Taskleistensymbol</entry>
     <entry lang="de" key="TASKICON_PREF_OPEN_VOL">Eingehängte Volumes öffnen</entry>
     <entry lang="de" key="TASKICON_PREF_UNMOUNT_VOL">Eingehängte Volumes trennen</entry>
@@ -1485,7 +1485,7 @@
     <entry lang="de" key="LINUX_MOUNT_SYSTEM_ENC_PREBOOT">Partition mithilfe der Systemverschlüsselung einhängen (Pre-Boot-Authentifizierung)</entry>
     <entry lang="de" key="LINUX_DO_NOT_MOUNT">Nicht einhängen</entry>
     <entry lang="de" key="LINUX_MOUNT_AT_DIR">Als Verzeichnis einhängen:</entry>
-    <entry lang="de" key="LINUX_SELECT">Auswählen ...</entry>
+    <entry lang="de" key="LINUX_SELECT">Auswählen...</entry>
     <entry lang="de" key="LINUX_UNMOUNT_ALL_WHEN">Alle Volumes aushängen, wenn</entry>
     <entry lang="de" key="LINUX_ENTERING_POWERSAVING">System geht in den Energiesparmodus über</entry>
     <entry lang="de" key="LINUX_LOGIN_ACTION">Aktionen beim Anmelden ausführen</entry>
@@ -1596,7 +1596,7 @@
     <entry lang="de" key="EXPANDER_FINISH_ABORT">FEHLER: Vorgang vom Benutzer abgebrochen.</entry>
     <entry lang="de" key="EXPANDER_FINISH_OK">Beendet. Volume erfolgreich erweitert.</entry>
     <entry lang="de" key="EXPANDER_CANCEL_WARNING">WARNUNG: Die Volume-Erweiterung ist im Gange!\n\nWenn Sie jetzt abbrechen, kann dies zu einer Beschädigung des Volumes führen.\n\nMöchten Sie wirklich abbrechen?</entry>
-    <entry lang="de" key="EXPANDER_STARTING_STATUS">Erweiterung des Volumes ist gestartet ...\n</entry>
+    <entry lang="de" key="EXPANDER_STARTING_STATUS">Erweiterung des Volumes ist gestartet...\n</entry>
     <entry lang="de" key="EXPANDER_HIDDEN_VOLUME_ERROR">Ein äußeres Volume, das ein verstecktes Volume enthält, kann nicht erweitert werden, weil dadurch das versteckte Volume zerstört wird.\n</entry>
     <entry lang="de" key="EXPANDER_SYSTEM_VOLUME_ERROR">Ein VeraCrypt-System-Volume kann nicht erweitert werden.</entry>
     <entry lang="de" key="EXPANDER_NO_FREE_SPACE">Nicht genügend freier Speicherplatz zum Erweitern des Volumes</entry>
@@ -1627,13 +1627,13 @@
     <entry lang="de" key="SCARD_W_REMOVED_CARD">Keine Karte im Lesegerät.\n\nVergewissern Sie sich, dass die Karte richtig eingesteckt ist.</entry>
     <entry lang="de" key="FORMAT_EXTERNAL_FAILED">Der Windows-Befehl format.com konnte das Volume nicht als NTFS/exFAT/ReFS formatieren: Fehler 0x%.8X.\n\nZurückfallen auf die Verwendung der Windows FormatEx-API.</entry>
     <entry lang="de" key="FORMATEX_API_FAILED">Windows FormatEx-API konnte das Volume nicht als NTFS/exFAT/ReFS formatieren.\n\nFehlerstatus = %s.</entry>
-    <entry lang="de" key="EXPANDER_WRITING_RANDOM_DATA">Zufallsdaten in neuen Speicherbereich schreiben ...\n</entry>
-    <entry lang="de" key="EXPANDER_WRITING_ENCRYPTED_BACKUP">Wiederverschlüsselte Backup-Kopfdaten schreiben ...\n</entry>
-    <entry lang="de" key="EXPANDER_WRITING_ENCRYPTED_PRIMARY">Wiederverschlüsselte primäre Kopfdaten schreiben ...\n</entry>
-    <entry lang="de" key="EXPANDER_WIPING_OLD_HEADER">Alte Backup-Kopfdaten löschen ...\n</entry>
-    <entry lang="de" key="EXPANDER_MOUNTING_VOLUME">Volume einhängen ...\n</entry>
-    <entry lang="de" key="EXPANDER_UNMOUNTING_VOLUME">Volume trennen ...\n</entry>
-    <entry lang="de" key="EXPANDER_EXTENDING_FILESYSTEM">Dateisystem erweitern ...\n</entry>
+    <entry lang="de" key="EXPANDER_WRITING_RANDOM_DATA">Zufallsdaten in neuen Speicherbereich schreiben...\n</entry>
+    <entry lang="de" key="EXPANDER_WRITING_ENCRYPTED_BACKUP">Wiederverschlüsselte Backup-Kopfdaten schreiben...\n</entry>
+    <entry lang="de" key="EXPANDER_WRITING_ENCRYPTED_PRIMARY">Wiederverschlüsselte primäre Kopfdaten schreiben...\n</entry>
+    <entry lang="de" key="EXPANDER_WIPING_OLD_HEADER">Alte Backup-Kopfdaten löschen...\n</entry>
+    <entry lang="de" key="EXPANDER_MOUNTING_VOLUME">Volume einhängen...\n</entry>
+    <entry lang="de" key="EXPANDER_UNMOUNTING_VOLUME">Volume trennen...\n</entry>
+    <entry lang="de" key="EXPANDER_EXTENDING_FILESYSTEM">Dateisystem erweitern...\n</entry>
     <entry lang="de" key="PARTIAL_SYSENC_MOUNT_READONLY">WARNUNG: Die Systempartition, die Sie einzuhängen versucht haben, war nicht vollständig verschlüsselt. Als Sicherheitsmaßnahme wurde das Volume '%s' schreibgeschützt eingehängt, um mögliche Beschädigungen oder unerwünschte Änderungen zu verhindern.</entry>
     <entry lang="de" key="IDC_LINK_KEYFILES_EXTENSIONS_WARNING">Wichtige Informationen zur Verwendung von Dateierweiterungen von Drittanbietern</entry>
     <entry lang="de" key="IDC_DISABLE_MEMORY_PROTECTION">Deaktivieren Sie den Speicherschutz für die Kompatibilität der Eingabehilfen</entry>
@@ -1649,6 +1649,47 @@
     <entry lang="de" key="INSECURE_MODE">[UNSICHERER MODUS]</entry>
     <entry lang="de" key="IDC_DISABLE_SCREEN_PROTECTION">Schutz vor Screenshots und Bildschirmaufnahmen deaktivieren</entry>
     <entry lang="de" key="DISABLE_SCREEN_PROTECTION_WARNING">WARNUNG: Das Deaktivieren des Bildschirmschutzes verringert die Sicherheit erheblich. Aktivieren Sie diese Option NUR, wenn Sie die Benutzeroberfläche von VeraCrypt explizit aufzeichnen müssen. Dies kann sensible Daten gegenüber Screenshot-Tools und Bildschirmaufnahmefunktionen wie Windows 11 Recall offenlegen.</entry>
+    <entry lang="de" key="MEMORY_COST">Speicheraufwand</entry>
+    <entry lang="de" key="IDT_KDF_ALGO">KDF-Algorithmus</entry>
+    <entry lang="de" key="IDD_PREFERENCES_TAB_GENERAL">Allgemein</entry>
+    <entry lang="de" key="IDD_PREFERENCES_TAB_ACTIONS">Actionen</entry>
+    <entry lang="de" key="IDD_PREFERENCES_TAB_PASSWORD">Passwort</entry>
+    <entry lang="de" key="IDC_SECURE_DESKTOP_ENABLE_IME">Eingabemethoden-Editor (IME) im Secure Desktop verwenden</entry>
+    <entry lang="de" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNUNG: Verwenden Sie diese Option nur, wenn Probleme bei der Auswahl von Schlüsseldateien/Tokens unter dem Secure Desktop auftreten.</entry>
+    <entry lang="de" key="ERR_KEY_DERIVATION_FAILED">Die Schlüsselableitung ist fehlgeschlagen. Dies kann durch unzureichenden Speicherplatz oder einen unterbrochenen Vorgang verursacht worden sein.</entry>
+    <entry lang="de" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">Die Systempartition bzw. das Systemlaufwerk ist bereits entschlüsselt, aber der Pfad zum EFI-Bootloader von Microsoft wurde nicht im Windows-Bootmanager wiederhergestellt. Es müssen lediglich die EFI-Bootdateien repariert werden. Verwenden Sie die Reparaturoption der VeraCrypt-Rettungsdiskette oder starten Sie das Windows-Wiederherstellungsmedium und führen Sie den Befehl 'bcdboot W:\\Windows /s S: /f UEFI' aus, nachdem Sie W: durch den Laufwerksbuchstaben des Windows-Volumes und S: durch den Laufwerksbuchstaben der EFI-Systempartition ersetzt haben. Pfad:</entry>
+    <entry lang="de" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">Die Systempartition bzw. das Systemlaufwerk ist bereits entschlüsselt, aber der Pfad des EFI-Fallback-Bootloaders enthält weiterhin den VeraCrypt-Bootloader. Es müssen lediglich die EFI-Bootdateien repariert werden. Verwenden Sie die Reparaturoption der VeraCrypt-Rettungsdiskette oder starten Sie das Windows-Wiederherstellungsmedium und führen Sie den Befehl 'bcdboot W:\\Windows /s S: /f UEFI' aus, nachdem Sie W: durch den Laufwerksbuchstaben des Windows-Volumes und S: durch den Laufwerksbuchstaben der EFI-Systempartition ersetzt haben. Pfad:</entry>
+    <entry lang="de" key="IDM_REPAIR_EFI_BOOT_LOADER">EFI-Bootloader reparieren...</entry>
+    <entry lang="de" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt stellt die Pfade des Windows-EFI-Bootloaders wieder her und entfernt die EFI-Boot-Einträge und -Dateien von VeraCrypt.\n\nFühren Sie diesen Vorgang erst durch, wenn die Systempartition bzw. das Systemlaufwerk vollständig entschlüsselt ist und Windows ohne Systemverschlüsselung starten kann.\n\nMöchten Sie fortfahren?</entry>
+    <entry lang="de" key="EFI_BOOT_LOADER_FILE_READ_FAILED">Die EFI-Bootloader-Datei konnte nicht vollständig gelesen werden:</entry>
+    <entry lang="de" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">Die EFI-Bootloader-Datei ist unerwartet groß und wurde nicht überprüft:</entry>
+    <entry lang="de" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">Die Systempartition bzw. das Systemlaufwerk ist bereits entschlüsselt und die EFI-Bootloader-Dateien wurden wiederhergestellt, doch VeraCrypt konnte einen oder mehrere VeraCrypt-Firmware-Boot-Einträge nicht entfernen. Die VeraCrypt-EFI-Dateien wurden an ihrem Speicherort belassen, sodass verbleibende Firmware-Einträge weiterhin auf einen vorhandenen Loader verweisen. Versuchen Sie es erneut als Administrator oder entfernen Sie den VeraCrypt-Boot-Eintrag aus den Firmware-Einstellungen, nachdem Sie sich vergewissert haben, dass der Windows-Boot-Manager normal startet.</entry>
+    <entry lang="de" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">Der EFI-Bootloader kann nicht repariert werden, solange die Systemverschlüsselung oder -entschlüsselung aktiv oder noch nicht abgeschlossen ist. Schließen Sie den laufenden Systemverschlüsselungs- bzw. -entschlüsselungsprozess ab oder setzen Sie ihn fort, bevor Sie es erneut versuchen.</entry>
+    <entry lang="de" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">Diese Reparaturmaßnahme ist nur auf Systemen verfügbar, die im UEFI-Modus von einer GPT-Systempartition booten.</entry>
+    <entry lang="de" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">Der EFI-Bootloader wurde erfolgreich repariert.</entry>
+    <entry lang="de" key="PIM_ARGON2_HELP">Der PIM (Persönlicher Iterationsmultiplikator) steuert den Speicher- und Zeitaufwand für die Ableitung des Argon2id-Kopfschlüssels wie folgt:\n      Speicher = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterationen = 3 + ((PIM - 1) / 3) für PIM 31 oder niedriger, dann 13 + (PIM - 31)\n\nWenn das Feld leer gelassen oder auf 0 gesetzt wird, verwendet VeraCrypt den Standard-Argon2-PIM (12), der 416 MiB Speicher und 6 Iterationen benötigt.\n\nWenn das Passwort weniger als 20 Zeichen lang ist, darf der Argon2-PIM nicht kleiner als 12 sein, um ein Mindestmaß an Sicherheit zu gewährleisten.\nWenn das Passwort 20 Zeichen oder mehr umfasst, kann der Argon2-PIM auf einen beliebigen Wert gesetzt werden.\n\nEin Argon2-PIM größer als 12 erhöht den Speicherbedarf auf bis zu 1024 MiB und erhöht zudem die Anzahl der Iterationen. Dies führt zu einer langsameren Einbindung. Ein kleiner Argon2-PIM-Wert (unter 12) führt zu einer schnelleren Einbindung, kann jedoch die Sicherheit beeinträchtigen, wenn das Passwort nicht stark genug ist.</entry>
+    <entry lang="de" key="PIM_ARGON2_LARGE_WARNING">Sie haben einen Argon2-PIM-Wert gewählt, der größer ist als der Standardwert von VeraCrypt.\nBitte beachten Sie, dass dies mehr Arbeitsspeicher erfordern und zu einer deutlich langsameren Einbindung führen kann.</entry>
+    <entry lang="de" key="PIM_ARGON2_SMALL_WARNING">Sie haben einen Argon2-PIM-Wert gewählt, der kleiner als der Standardwert von VeraCrypt ist. Bitte beachten Sie, dass ein zu schwaches Passwort die Sicherheit beeinträchtigen kann.\n\nBestätigen Sie, dass Sie ein sicheres Passwort verwenden?</entry>
+    <entry lang="de" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Das Passwort muss mindestens 20 Zeichen lang sein, damit der angegebene Argon2-PIM verwendet werden kann.\nKürzere Passwörter können nur verwendet werden, wenn der Argon2-PIM-Wert 12 oder größer ist.</entry>
+    <entry lang="de" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">NTFS-Volumes mit dem NTFS3-Treiber des Linux-Kernels einbinden</entry>
+    <entry lang="de" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Nur Linux. Wenn diese Option aktiviert ist, überprüft VeraCrypt das entschlüsselte virtuelle Gerät mit 'blkid -p' und hängt erkannte NTFS-Dateisysteme mit 'ntfs3' anstelle des standardmäßigen NTFS-Backends ein. Wenn die NTFS-Erkennung fehlschlägt, verwendet VeraCrypt die normale automatische Dateisystemauswahl. Wenn 'ntfs3' nicht verfügbar ist oder von der Distribution blockiert wird, kann das Einbinden fehlschlagen. Diese Opt-in-Option kann Hänger beim Suspendieren oder im Ruhezustand vermeiden, die durch eingefrorene FUSE-Dateisysteme im Benutzerbereich verursacht werden.</entry>
+    <entry lang="de" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Das normale Aushängen des Volumes {0} ist fehlgeschlagen. Dies kann passieren, wenn Anwendungen noch Dateien oder Verzeichnisse auf dem Volume geöffnet haben oder wenn das zugrunde liegende Gerät getrennt wurde und die Einbindung veraltet ist.\n\nWenn das Gerät noch angeschlossen ist, wählen Sie „Nein“, schließen Sie die Anwendungen, die das Volume verwenden, und versuchen Sie erneut, das Volume auszuhängen.\n\nWenn das Gerät getrennt wurde oder die Einbindung veraltet ist, kann VeraCrypt eine Notfallbereinigung versuchen, indem es das Dateisystem verzögert trennt und VeraCrypt-Kernelobjekte entfernt oder deren Entfernung plant. Ausstehende Schreibvorgänge sind möglicherweise fehlgeschlagen, Daten können verloren gegangen sein, und die Bereinigung bleibt möglicherweise ausstehend, bis Anwendungen geöffnete Dateien schließen. Überprüfen Sie das Dateisystem mit 'fsck' oder dem entsprechenden Reparaturtool, bevor Sie es wieder verwenden.\n\nWeiter?</entry>
+    <entry lang="de" key="LINUX_EMERGENCY_UNMOUNTED">Die Notfallbereinigung für das Volume {0} wurde gestartet. Falls das Volume getrennt wurde, die Einbindung veraltet war oder Schreibvorgänge ausstehend waren, überprüfen Sie das Dateisystem mit 'fsck' oder dem entsprechenden Reparaturtool, bevor Sie es erneut verwenden.</entry>
+    <entry lang="de" key="FORMAT_STAGE_WRITING_DATA">Volumendaten werden erstellt. Bitte warten.</entry>
+    <entry lang="de" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Abschluss der Volume-Erstellung: Schreiben der Kopfdatensicherung.</entry>
+    <entry lang="de" key="FORMAT_STAGE_FLUSHING_DATA">Abschluss der Volume-Erstellung: Daten werden auf die Festplatte geschrieben. Bei großen Volumes oder langsamen Speichergeräten bzw. USB-Speichern kann dies einige Minuten dauern.</entry>
+    <entry lang="de" key="FORMAT_STAGE_FINISHED">Die Erstellung des Volumes wird abgeschlossen.</entry>
+    <entry lang="de" key="FORMAT_STAGE_ABORTED">Die Erstellung des Volumes wurde abgebrochen.</entry>
+    <entry lang="de" key="FORMAT_STAGE_ERROR">Die Erstellung des Volumes ist fehlgeschlagen.</entry>
+    <entry lang="de" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Abschluss der Volume-Erstellung: Einbinden des temporären Volumes.</entry>
+    <entry lang="de" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Abschluss der Volume-Erstellung: Vorbereiten des temporären Geräts.</entry>
+    <entry lang="de" key="FORMAT_STAGE_CREATING_FILESYSTEM">Abschluss der Volume-Erstellung: Erstellen des Dateisystems mit {0}.</entry>
+    <entry lang="de" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Abschluss der Volume-Erstellung: Temporäres Volume wird ausgehängt.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <!-- XML-Schema -->
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">

Translations/Language.el.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="el" name="Ελληνικά" en-name="Greek" version="0.1.0" translators="Βασίλης Κοσμίδης" />
     <font lang="el" class="normal" size="11" face="default" />
     <font lang="el" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="el" key="IDT_NEW_PASSWORD">Κωδικός:</entry>
     <entry lang="en" key="IDT_PARALLELIZATION_OPTIONS">Thread-Based Parallelization</entry>
     <entry lang="en" key="IDT_PKCS11_LIB_PATH">PKCS #11 Library Path</entry>
-    <entry lang="el" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="el" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="el" key="IDT_KDF">KDF:</entry>
+    <entry lang="el" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="el" key="IDT_PW_CACHE_OPTIONS">Cache κωδικού</entry>
     <entry lang="en" key="IDT_SECURITY_OPTIONS">Security Options</entry>
     <entry lang="en" key="IDT_EMV_OPTIONS">EMV Options</entry>
@@ -813,7 +813,7 @@
     <entry lang="en" key="SECONDARY_KEY_SIZE_LRW">Tweak Key Size (LRW Mode)</entry>
     <entry lang="el" key="BITS">bits</entry>
     <entry lang="el" key="BLOCK_SIZE">Μέγεθος μπλοκ</entry>
-    <entry lang="el" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="el" key="KDF">KDF</entry>
     <entry lang="el" key="PKCS5_ITERATIONS">PKCS-5 αριθμός επαναλήψεων</entry>
     <entry lang="el" key="VOLUME_CREATE_DATE">Δημιουργία τόμου</entry>
     <entry lang="el" key="VOLUME_HEADER_DATE">Τελευταία τροποποίηση header</entry>
@@ -1522,8 +1522,8 @@
     <entry lang="en" key="LINUX_DOT_LF">.\n</entry>
     <entry lang="en" key="LINUX_NOT_SUPPORTED"> (not supported by components available on this platform).\n</entry>
     <entry lang="en" key="LINUX_KERNEL_OLD">Your system uses an old version of the Linux kernel.\n\nDue to a bug in the Linux kernel, your system may stop responding when writing data to a VeraCrypt volume. This problem can be solved by upgrading the kernel to version 2.6.24 or later.</entry>
-    <entry lang="en" key="LINUX_VOL_MOUNTED">Volume {0} has been mounted.</entry>
     <entry lang="en" key="LINUX_VOL_UNMOUNTED">Volume {0} has been unmounted.</entry>
+    <entry lang="en" key="LINUX_VOL_MOUNTED">Volume {0} has been mounted.</entry>
     <entry lang="en" key="LINUX_OOM">Out of memory.</entry>
     <entry lang="en" key="LINUX_CANT_GET_ADMIN_PRIV">Failed to obtain administrator privileges</entry>
     <entry lang="en" key="LINUX_COMMAND_GET_ERROR">Command {0} returned error {1}.</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="en" key="INSECURE_MODE">[INSECURE MODE]</entry>
     <entry lang="en" key="IDC_DISABLE_SCREEN_PROTECTION">Disable protection against screenshots and screen recording</entry>
     <entry lang="en" key="DISABLE_SCREEN_PROTECTION_WARNING">WARNING: Disabling screen protection significantly reduces security. Enable this option ONLY if you have a specific need to capture VeraCrypt's interface. This may expose sensitive data to screenshot tools and screen recording features such as Windows 11 Recall.</entry>
+    <entry lang="en" key="MEMORY_COST">Memory Cost</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.es.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="es" name="Español" en-name="Spanish" version="1.0.0" translators="Juan Antonio Auñón Ochando" />
     <font lang="es" class="normal" size="11" face="default" />
     <font lang="es" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="es" key="IDT_NEW_PASSWORD">Contraseña:</entry>
     <entry lang="es" key="IDT_PARALLELIZATION_OPTIONS">Paralelización basada en hilos</entry>
     <entry lang="es" key="IDT_PKCS11_LIB_PATH">Ruta de Librería PKCS #11</entry>
-    <entry lang="es" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="es" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="es" key="IDT_KDF">KDF:</entry>
+    <entry lang="es" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="es" key="IDT_PW_CACHE_OPTIONS">Caché de Contraseñas</entry>
     <entry lang="es" key="IDT_SECURITY_OPTIONS">Opciones de seguridad</entry>
     <entry lang="es" key="IDT_EMV_OPTIONS">EMV Opciones</entry>
@@ -813,7 +813,7 @@
     <entry lang="es" key="SECONDARY_KEY_SIZE_LRW">Tamaño de Clave Tweak (Modo LRW)</entry>
     <entry lang="es" key="BITS">bits</entry>
     <entry lang="es" key="BLOCK_SIZE">Tamaño de bloque</entry>
-    <entry lang="es" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="es" key="KDF">KDF</entry>
     <entry lang="es" key="PKCS5_ITERATIONS">Cuenta de iteraciones PKCS-5</entry>
     <entry lang="es" key="VOLUME_CREATE_DATE">Volumen Creado</entry>
     <entry lang="es" key="VOLUME_HEADER_DATE">Última modificación de la cabecera</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="es" key="INSECURE_MODE">[MODO INSEGURO]</entry>
     <entry lang="es" key="IDC_DISABLE_SCREEN_PROTECTION">Deshabilitar la protección contra capturas de pantalla y grabación de pantalla</entry>
     <entry lang="es" key="DISABLE_SCREEN_PROTECTION_WARNING">ADVERTENCIA: Deshabilitar la protección de pantalla reduce significativamente la seguridad. Habilite esta opción SOLO si necesita capturar la interfaz de VeraCrypt por un motivo específico. Esto puede exponer datos sensibles a herramientas de captura de pantalla y funciones de grabación de pantalla, como Windows 11 Recall.</entry>
+    <entry lang="es" key="MEMORY_COST">Costo de Memoria</entry>
+    <entry lang="es" key="IDT_KDF_ALGO">Algoritmo KDF</entry>
+    <entry lang="es" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="es" key="IDD_PREFERENCES_TAB_ACTIONS">Acciones</entry>
+    <entry lang="es" key="IDD_PREFERENCES_TAB_PASSWORD">Contraseña</entry>
+    <entry lang="es" key="IDC_SECURE_DESKTOP_ENABLE_IME">Habilitar el editor de métodos de entrada (IME) en el Escritorio seguro</entry>
+    <entry lang="es" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">ADVERTENCIA: Habilite esta opción SOLO si encuentra problemas al seleccionar archivos clave (Keyfiles) o tokens en el Escritorio seguro.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
 </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.et.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="et" name="Eesti" en-name="Estonian" version="0.1.0" translators="Maiko Mõtsar" />
     <font lang="et" class="normal" size="11" face="vaikimisi" />
     <font lang="et" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="et" key="IDT_NEW_PASSWORD">Salasõna:</entry>
     <entry lang="en" key="IDT_PARALLELIZATION_OPTIONS">Thread-Based Parallelization</entry>
     <entry lang="en" key="IDT_PKCS11_LIB_PATH">PKCS #11 Library Path</entry>
-    <entry lang="et" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="en" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="et" key="IDT_KDF">KDF:</entry>
+    <entry lang="en" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="et" key="IDT_PW_CACHE_OPTIONS">Salasõna vahemälu</entry>
     <entry lang="en" key="IDT_SECURITY_OPTIONS">Security Options</entry>
     <entry lang="en" key="IDT_EMV_OPTIONS">EMV Options</entry>
@@ -813,7 +813,7 @@
     <entry lang="en" key="SECONDARY_KEY_SIZE_LRW">Tweak Key Size (LRW Mode)</entry>
     <entry lang="et" key="BITS">bitti</entry>
     <entry lang="et" key="BLOCK_SIZE">Bloki maht</entry>
-    <entry lang="et" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="et" key="KDF">KDF</entry>
     <entry lang="et" key="PKCS5_ITERATIONS">PKCS-5 iteratsiooni loend</entry>
     <entry lang="et" key="VOLUME_CREATE_DATE">Konteiner loodud</entry>
     <entry lang="et" key="VOLUME_HEADER_DATE">Päist viimati muudetud</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="en" key="INSECURE_MODE">[INSECURE MODE]</entry>
     <entry lang="en" key="IDC_DISABLE_SCREEN_PROTECTION">Disable protection against screenshots and screen recording</entry>
     <entry lang="en" key="DISABLE_SCREEN_PROTECTION_WARNING">WARNING: Disabling screen protection significantly reduces security. Enable this option ONLY if you have a specific need to capture VeraCrypt's interface. This may expose sensitive data to screenshot tools and screen recording features such as Windows 11 Recall.</entry>
+    <entry lang="en" key="MEMORY_COST">Memory Cost</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.eu.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="eu" name="Euskara" en-name="Basque" version="1.0.0" translators="Ander Genua" />
     <font lang="eu" class="normal" size="11" face="default" />
     <font lang="eu" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="eu" key="IDT_NEW_PASSWORD">Pasahitza:</entry>
     <entry lang="eu" key="IDT_PARALLELIZATION_OPTIONS">Prozesuetan Oinarritutako Paralelizazioa</entry>
     <entry lang="eu" key="IDT_PKCS11_LIB_PATH">PKCS #11 Liburutegiaren Helbidea</entry>
-    <entry lang="eu" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="en" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="eu" key="IDT_KDF">KDF:</entry>
+    <entry lang="en" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="eu" key="IDT_PW_CACHE_OPTIONS">Pasahitzen Memoria</entry>
     <entry lang="eu" key="IDT_SECURITY_OPTIONS">Sekurtasun Aukerak</entry>
     <entry lang="en" key="IDT_EMV_OPTIONS">EMV Options</entry>
@@ -813,7 +813,7 @@
     <entry lang="eu" key="SECONDARY_KEY_SIZE_LRW">Tweak Gakoaren Tamaina (LRW Modua)</entry>
     <entry lang="eu" key="BITS">bitak</entry>
     <entry lang="eu" key="BLOCK_SIZE">Blokearen Tamaina</entry>
-    <entry lang="eu" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="eu" key="KDF">KDF</entry>
     <entry lang="eu" key="PKCS5_ITERATIONS">PKCS-5 Iterazio Zenbaketa</entry>
     <entry lang="eu" key="VOLUME_CREATE_DATE">Bolumena sortu da</entry>
     <entry lang="eu" key="VOLUME_HEADER_DATE">Goiburuaren azken aldaketa</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="en" key="INSECURE_MODE">[INSECURE MODE]</entry>
     <entry lang="en" key="IDC_DISABLE_SCREEN_PROTECTION">Disable protection against screenshots and screen recording</entry>
     <entry lang="en" key="DISABLE_SCREEN_PROTECTION_WARNING">WARNING: Disabling screen protection significantly reduces security. Enable this option ONLY if you have a specific need to capture VeraCrypt's interface. This may expose sensitive data to screenshot tools and screen recording features such as Windows 11 Recall.</entry>
+    <entry lang="en" key="MEMORY_COST">Memory Cost</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.fa.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="fa" name="فارسي" en-name="Persian" version="0.1.0" translators="Ali Bitazar, Rodabeh Sarmadi" />
     <font lang="fa" class="normal" size="11" face="default" />
     <font lang="fa" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="fa" key="IDT_NEW_PASSWORD">رمز عبور:</entry>
     <entry lang="en" key="IDT_PARALLELIZATION_OPTIONS">Thread-Based Parallelization</entry>
     <entry lang="en" key="IDT_PKCS11_LIB_PATH">PKCS #11 Library Path</entry>
-    <entry lang="en" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="en" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="en" key="IDT_KDF">KDF:</entry>
+    <entry lang="en" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="en" key="IDT_PW_CACHE_OPTIONS">Password Cache</entry>
     <entry lang="en" key="IDT_SECURITY_OPTIONS">Security Options</entry>
     <entry lang="en" key="IDT_EMV_OPTIONS">EMV Options</entry>
@@ -813,7 +813,7 @@
     <entry lang="en" key="SECONDARY_KEY_SIZE_LRW">Tweak Key Size (LRW Mode)</entry>
     <entry lang="fa" key="BITS">بيت ها</entry>
     <entry lang="fa" key="BLOCK_SIZE">بلوكه كردن سايز</entry>
-    <entry lang="en" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="en" key="KDF">KDF</entry>
     <entry lang="en" key="PKCS5_ITERATIONS">PKCS-5 Iteration Count</entry>
     <entry lang="en" key="VOLUME_CREATE_DATE">Volume Created</entry>
     <entry lang="en" key="VOLUME_HEADER_DATE">Header Last Modified</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="en" key="INSECURE_MODE">[INSECURE MODE]</entry>
     <entry lang="en" key="IDC_DISABLE_SCREEN_PROTECTION">Disable protection against screenshots and screen recording</entry>
     <entry lang="en" key="DISABLE_SCREEN_PROTECTION_WARNING">WARNING: Disabling screen protection significantly reduces security. Enable this option ONLY if you have a specific need to capture VeraCrypt's interface. This may expose sensitive data to screenshot tools and screen recording features such as Windows 11 Recall.</entry>
+    <entry lang="en" key="MEMORY_COST">Memory Cost</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.fi.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="fi" name="Suomi" en-name="Finnish" version="0.4.0" translators="Matti Ruhanen, Jertzukka" />
     <font lang="fi" class="normal" size="11" face="default" />
     <font lang="fi" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="fi" key="IDT_NEW_PASSWORD">Salasana:</entry>
     <entry lang="fi" key="IDT_PARALLELIZATION_OPTIONS">Säijepohjainen rinnakkaistaminen</entry>
     <entry lang="fi" key="IDT_PKCS11_LIB_PATH">PKCS #11 kirjastopolku</entry>
-    <entry lang="fi" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="fi" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="fi" key="IDT_KDF">KDF:</entry>
+    <entry lang="fi" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="fi" key="IDT_PW_CACHE_OPTIONS">Salasanojen muistaminen</entry>
     <entry lang="fi" key="IDT_SECURITY_OPTIONS">Salausasetukset</entry>
     <entry lang="fi" key="IDT_EMV_OPTIONS">EMV-asetukset</entry>
@@ -813,7 +813,7 @@
     <entry lang="fi" key="SECONDARY_KEY_SIZE_LRW">Säätöavaimen koko (LRW-tila)</entry>
     <entry lang="fi" key="BITS">bittiä</entry>
     <entry lang="fi" key="BLOCK_SIZE">Lohkon koko</entry>
-    <entry lang="fi" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="fi" key="KDF">KDF</entry>
     <entry lang="fi" key="PKCS5_ITERATIONS">PKCS-5 iteraatioiden määrä</entry>
     <entry lang="fi" key="VOLUME_CREATE_DATE">Taltio luotu</entry>
     <entry lang="fi" key="VOLUME_HEADER_DATE">Otsikkoa viimeksi muokattu</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="fi" key="INSECURE_MODE">[EPÄTURVALLINEN TILA]</entry>
     <entry lang="fi" key="IDC_DISABLE_SCREEN_PROTECTION">Ota kuvakaappaus- ja näytöntallennussuojaus pois käytöstä</entry>
     <entry lang="fi" key="DISABLE_SCREEN_PROTECTION_WARNING">VAROITUS: Kuvakaappaus- ja näytöntallennussuojauksen poistaminen käytöstä heikentää tietoturvaa merkittävästi. Ota tämä käyttöön VAIN, jos sinun täytyy erityisesti tallentaa VeraCryptin käyttöliittymä. Tämä voi paljastaa arkaluontoisia tietoja kuvakaappausohjelmille ja näytöntallennusominaisuuksille, kuten Windows 11 Recall.</entry>
+    <entry lang="fi" key="MEMORY_COST">Muistikustannus</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.fr.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="fr" name="Français" en-name="French" version="0.3.0" translators="Stéphane S., Olivier M., Thierry T, Mounir IDRASSI" />
     <font lang="fr" class="normal" size="11" face="default" />
     <font lang="fr" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="fr" key="IDT_NEW_PASSWORD">Mot de passe :</entry>
     <entry lang="fr" key="IDT_PARALLELIZATION_OPTIONS">Parallélisation</entry>
     <entry lang="fr" key="IDT_PKCS11_LIB_PATH">Chemin de bibliothèque PKCS #11</entry>
-    <entry lang="fr" key="IDT_PKCS5_PRF">PKCS-5 PRF :</entry>
-    <entry lang="fr" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="fr" key="IDT_KDF">KDF :</entry>
+    <entry lang="fr" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="fr" key="IDT_PW_CACHE_OPTIONS">Mots de passe en cache</entry>
     <entry lang="fr" key="IDT_SECURITY_OPTIONS">Options de sécurité</entry>
     <entry lang="fr" key="IDT_EMV_OPTIONS">Options EMV</entry>
@@ -813,7 +813,7 @@
     <entry lang="fr" key="SECONDARY_KEY_SIZE_LRW">Ajustement de la taille de la clé (mode LRW )</entry>
     <entry lang="fr" key="BITS">bits</entry>
     <entry lang="fr" key="BLOCK_SIZE">Taille du bloc</entry>
-    <entry lang="fr" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="fr" key="KDF">KDF</entry>
     <entry lang="fr" key="PKCS5_ITERATIONS">Nombre d’itérations PKCS-5</entry>
     <entry lang="fr" key="VOLUME_CREATE_DATE">Création du volume</entry>
     <entry lang="fr" key="VOLUME_HEADER_DATE">Modification de l’en-tête</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="fr" key="INSECURE_MODE">[MODE NON SÉCURISÉ]</entry>
     <entry lang="fr" key="IDC_DISABLE_SCREEN_PROTECTION">Désactiver la protection contre la capture et l'enregistrement de l'écran</entry>
     <entry lang="fr" key="DISABLE_SCREEN_PROTECTION_WARNING">AVERTISSEMENT : Désactiver la protection contre la capture d’écran réduit considérablement la sécurité. Activez cette option UNIQUEMENT si vous avez un besoin spécifique de capturer l’interface de VeraCrypt. Cela peut exposer des données sensibles aux outils de capture d’écran et aux fonctionnalités d’enregistrement de l’écran comme Windows 11 Recall.</entry>
+    <entry lang="fr" key="MEMORY_COST">Coût Mémoire</entry>
+    <entry lang="fr" key="IDT_KDF_ALGO">Algorithme KDF</entry>
+    <entry lang="fr" key="IDD_PREFERENCES_TAB_GENERAL">Général</entry>
+    <entry lang="fr" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="fr" key="IDD_PREFERENCES_TAB_PASSWORD">Mot de passe</entry>
+    <entry lang="fr" key="IDC_SECURE_DESKTOP_ENABLE_IME">Activer l'éditeur de méthode de saisie (IME) dans le bureau sécurisé</entry>
+    <entry lang="fr" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">AVERTISSEMENT : Activez cette option uniquement si vous rencontrez des problèmes lors de la sélection de fichiers clés/tokens dans le bureau sécurisé.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.he.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt xmlns:xs="http://www.w3.org/2001/XMLSchema">
-  <localization prog-version="1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="he" name="עברית" en-name="Hebrew" version="0.1.0" translators="thewh1teagle" />
     <font lang="he" class="normal" size="11" face="default" />
     <font lang="he" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="he" key="IDT_NEW_PASSWORD">סיסמה:</entry>
     <entry lang="he" key="IDT_PARALLELIZATION_OPTIONS">מקביליות מבוססת טרדים</entry>
     <entry lang="he" key="IDT_PKCS11_LIB_PATH">נתיב הספרייה PKCS # 11</entry>
-    <entry lang="he" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="he" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="he" key="IDT_KDF">KDF:</entry>
+    <entry lang="he" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="he" key="IDT_PW_CACHE_OPTIONS">מטמון סיסמה</entry>
     <entry lang="he" key="IDT_SECURITY_OPTIONS">אפשרויות אבטחה</entry>
     <entry lang="en" key="IDT_EMV_OPTIONS">EMV Options</entry>
@@ -813,7 +813,7 @@
     <entry lang="he" key="SECONDARY_KEY_SIZE_LRW">גודל מפתח לצבוט (מצב LRW)</entry>
     <entry lang="he" key="BITS">ביטים</entry>
     <entry lang="he" key="BLOCK_SIZE">גודל בלוק</entry>
-    <entry lang="he" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="he" key="KDF">KDF</entry>
     <entry lang="he" key="PKCS5_ITERATIONS">ספירת איטרציה של PKCS-5</entry>
     <entry lang="he" key="VOLUME_CREATE_DATE">אמצעי אחסון נוצר</entry>
     <entry lang="he" key="VOLUME_HEADER_DATE">הכותרת שונה לאחרונה</entry>
@@ -1474,7 +1474,6 @@
     <entry lang="he" key="LINUX_CROSS_SUPPORT_OTHER_HELP">בחר באפשרות זו אם אתה צריך להשתמש בעוצמת הקול בפלטפורמות אחרות.</entry>
     <entry lang="he" key="LINUX_CROSS_SUPPORT_ONLY">אעלה את אמצעי האחסון רק ב- {0}</entry>
     <entry lang="he" key="LINUX_CROSS_SUPPORT_ONLY_HELP">בחר באפשרות זו אם אינך צריך להשתמש בעוצמת הקול בפלטפורמות אחרות.</entry>
-    <entry lang="he" key="LINUX_CROSS_SUPPORT_ONLY_HELP">בחר באפשרות זו אם אינך צריך להשתמש בעוצמת הקול בפלטפורמות אחרות.</entry>
     <entry lang="he" key="LINUX_DESELECT">בטל את הבחירה</entry>
     <entry lang="he" key="LINUX_ADMIN_PW_QUERY">הזן את סיסמת המשתמש או את סיסמת מנהל המערכת שלך:</entry>
     <entry lang="he" key="LINUX_ADMIN_PW_QUERY_TITLE">נדרשות הרשאות מנהל</entry>
@@ -1647,6 +1646,47 @@
     <entry lang="he" key="INSECURE_MODE">[מצב לא מאובטח]</entry>
     <entry lang="he" key="IDC_DISABLE_SCREEN_PROTECTION">השבת הגנה מפני צילומי מסך והקלטת מסך</entry>
     <entry lang="he" key="DISABLE_SCREEN_PROTECTION_WARNING">אזהרה: השבתת הגנת המסך מפחיתה משמעותית את רמת האבטחה. אפשר אפשרות זו אך ורק אם יש צורך מיוחד ללכוד את ממשק VeraCrypt. פעולה זו עשויה לחשוף נתונים רגישים לכלי צילום מסך ותכונות הקלטת מסך כגון Windows 11 Recall.</entry>
+    <entry lang="he" key="MEMORY_COST">עלות זיכרון</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified">
     <xs:element name="VeraCrypt">

Translations/Language.hu.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="hu" name="Magyar" en-name="Hungarian" version="1.0.0" translators="Nyul Balazs > Szaki, Zityi's Translator Te@m" />
     <font lang="hu" class="normal" size="11" face="default" />
     <font lang="hu" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="hu" key="IDT_NEW_PASSWORD">Jelszó:</entry>
     <entry lang="hu" key="IDT_PARALLELIZATION_OPTIONS">Szálalapú párhuzamosítás</entry>
     <entry lang="hu" key="IDT_PKCS11_LIB_PATH">PKCS #11 könyvtár útvonal</entry>
-    <entry lang="hu" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="hu" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="hu" key="IDT_KDF">KDF:</entry>
+    <entry lang="hu" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="hu" key="IDT_PW_CACHE_OPTIONS">Jelszó gyorsítótár</entry>
     <entry lang="hu" key="IDT_SECURITY_OPTIONS">Biztonsági lehetőségek</entry>
     <entry lang="en" key="IDT_EMV_OPTIONS">EMV Options</entry>
@@ -813,7 +813,7 @@
     <entry lang="hu" key="SECONDARY_KEY_SIZE_LRW">Hangolókulcs mérete (LRW mód)</entry>
     <entry lang="hu" key="BITS">bit</entry>
     <entry lang="hu" key="BLOCK_SIZE">Blokkméret</entry>
-    <entry lang="hu" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="hu" key="KDF">KDF</entry>
     <entry lang="hu" key="PKCS5_ITERATIONS">PKCS-5 iterációs szám</entry>
     <entry lang="hu" key="VOLUME_CREATE_DATE">Kötet létrehozva</entry>
     <entry lang="hu" key="VOLUME_HEADER_DATE">Fejléc utolsó módosítása</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="hu" key="INSECURE_MODE">[NEM BIZTONSÁGOS MÓD]</entry>
     <entry lang="hu" key="IDC_DISABLE_SCREEN_PROTECTION">Képernyőkép- és képernyőfelvétel-védelem letiltása</entry>
     <entry lang="hu" key="DISABLE_SCREEN_PROTECTION_WARNING">FIGYELEM: A képernyővédelem letiltása jelentősen csökkenti a biztonságot. Csak akkor engedélyezze ezt, ha kifejezetten szüksége van a VeraCrypt felületének rögzítésére. Ez érzékeny adatokat tehet elérhetővé képernyőkép-készítő és képernyőfelvételi eszközök, például a Windows 11 Recall számára.</entry>
+    <entry lang="hu" key="MEMORY_COST">Memóriaköltség</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.id.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="id" name="Bahasa Indonesia" en-name="Indonesian" version="1.0.0" translators="Tajuddin N. F.; Transifex contributors" />
     <font lang="id" class="normal" size="11" face="default" />
     <font lang="id" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="id" key="IDT_NEW_PASSWORD">Kata Sandi:</entry>
     <entry lang="id" key="IDT_PARALLELIZATION_OPTIONS">Paralelisasi Berbasis Thread</entry>
     <entry lang="id" key="IDT_PKCS11_LIB_PATH">Path Pustaka PKCS #11</entry>
-    <entry lang="id" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="id" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="id" key="IDT_KDF">KDF:</entry>
+    <entry lang="id" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="id" key="IDT_PW_CACHE_OPTIONS">Singgahan Kata Sandi</entry>
     <entry lang="id" key="IDT_SECURITY_OPTIONS">Opsi Keamanan</entry>
     <entry lang="en" key="IDT_EMV_OPTIONS">EMV Options</entry>
@@ -813,7 +813,7 @@
     <entry lang="id" key="SECONDARY_KEY_SIZE_LRW">Ukuran Tombol Tweak (Mode LRW)</entry>
     <entry lang="id" key="BITS">bit</entry>
     <entry lang="id" key="BLOCK_SIZE">Ukuran Blok</entry>
-    <entry lang="id" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="id" key="KDF">KDF</entry>
     <entry lang="id" key="PKCS5_ITERATIONS">Cacah Iterasi PKCS-5</entry>
     <entry lang="id" key="VOLUME_CREATE_DATE">Volume Telah Dibuat</entry>
     <entry lang="id" key="VOLUME_HEADER_DATE">Header Terakhir Dimodifikasi</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="id" key="INSECURE_MODE">[MODE TIDAK AMAN]</entry>
     <entry lang="id" key="IDC_DISABLE_SCREEN_PROTECTION">Nonaktifkan perlindungan terhadap tangkapan layar dan perekaman layar</entry>
     <entry lang="id" key="DISABLE_SCREEN_PROTECTION_WARNING">PERINGATAN: Menonaktifkan perlindungan layar secara signifikan mengurangi keamanan. Aktifkan opsi ini HANYA jika Anda memiliki kebutuhan khusus untuk menangkap antarmuka VeraCrypt. Hal ini dapat mengekspos data sensitif ke alat tangkapan layar dan fitur perekaman layar seperti Windows 11 Recall.</entry>
+    <entry lang="id" key="MEMORY_COST">Biaya Memori</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.it.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="it" name="Italiano" en-name="Italian" version="1.0.1" translators="Maurizio Ballo, Consiglio Gaetano" />
     <font lang="it" class="normal" size="11" face="default" />
     <font lang="it" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="it" key="IDT_NEW_PASSWORD">Password:</entry>
     <entry lang="it" key="IDT_PARALLELIZATION_OPTIONS">Parallelizzazione Thread-Based</entry>
     <entry lang="it" key="IDT_PKCS11_LIB_PATH">PKCS #11 Percorso libreria</entry>
-    <entry lang="it" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="it" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="it" key="IDT_KDF">KDF:</entry>
+    <entry lang="it" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="it" key="IDT_PW_CACHE_OPTIONS">Password nascoste</entry>
     <entry lang="it" key="IDT_SECURITY_OPTIONS">Opzioni sicurezza</entry>
     <entry lang="en" key="IDT_EMV_OPTIONS">EMV Options</entry>
@@ -813,7 +813,7 @@
     <entry lang="it" key="SECONDARY_KEY_SIZE_LRW">Dimensione chiave Tweak (Modo LRW )</entry>
     <entry lang="it" key="BITS">bit</entry>
     <entry lang="it" key="BLOCK_SIZE">Dimensione blocco</entry>
-    <entry lang="it" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="it" key="KDF">KDF</entry>
     <entry lang="it" key="PKCS5_ITERATIONS">Numero iterazioni PKCS-5</entry>
     <entry lang="it" key="VOLUME_CREATE_DATE">Volume creato</entry>
     <entry lang="it" key="VOLUME_HEADER_DATE">Ultima modifica intestazione</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="it" key="INSECURE_MODE">[MODALITÀ NON SICURA]</entry>
     <entry lang="it" key="IDC_DISABLE_SCREEN_PROTECTION">Disabilita la protezione contro screenshot e registrazione dello schermo</entry>
     <entry lang="it" key="DISABLE_SCREEN_PROTECTION_WARNING">ATTENZIONE: Disabilitare la protezione dello schermo riduce significativamente la sicurezza. Attiva questa opzione SOLO se hai una necessità specifica di acquisire l’interfaccia di VeraCrypt. Questo potrebbe esporre dati sensibili a strumenti di cattura schermo e a funzionalità di registrazione come Windows 11 Recall.</entry>
+    <entry lang="it" key="MEMORY_COST">Costo di Memoria</entry>
+    <entry lang="it" key="IDT_KDF_ALGO">Algoritmo KDF</entry>
+    <entry lang="it" key="IDD_PREFERENCES_TAB_GENERAL">Generale</entry>
+    <entry lang="it" key="IDD_PREFERENCES_TAB_ACTIONS">Azioni</entry>
+    <entry lang="it" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="it" key="IDC_SECURE_DESKTOP_ENABLE_IME">Abilita l'editor del metodo di input (IME) nel Desktop sicuro</entry>
+    <entry lang="it" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">ATTENZIONE: Abilita questa opzione SOLO se riscontri problemi durante la selezione di file chiave o token nel Desktop sicuro.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.ja.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="ja" name="日本語" en-name="Japanese" version="1.1.0" translators="OGOSHI Masayuki, Transifex contributors" />
     <font lang="ja" class="normal" size="12" face="MS UI Gothic" />
     <font lang="ja" class="bold" size="16" face="MS UI Gothic" />
@@ -43,7 +43,7 @@
     <entry lang="ja" key="IDC_KB">&amp;KB</entry>
     <entry lang="ja" key="IDC_KEYFILES_ENABLE">キーファイルを使用(&amp;S)</entry>
     <entry lang="ja" key="IDC_KEYFILES_TRY_EMPTY_PASSWORD">最初に空のパスワードでマウントを試してください。</entry>
-    <entry lang="ja" key="IDC_KEYFILES_RANDOM_SIZE">ランダムサイズ ( 64 &lt;-&gt; 1048576 )</entry>    <entry lang="ja" key="IDC_KEY_FILES">キーファイル(&amp;K)</entry>
+    <entry lang="ja" key="IDC_KEYFILES_RANDOM_SIZE">ランダムサイズ ( 64 &lt;-&gt; 1048576 )</entry>
     <entry lang="ja" key="IDC_KEY_FILES">キーファイル(&amp;K)</entry>
     <entry lang="ja" key="IDC_LINK_HASH_INFO">ハッシュアルゴリズムについて</entry>
     <entry lang="ja" key="IDC_LINK_MORE_INFO_ABOUT_CIPHER">暗号について</entry>
@@ -291,8 +291,8 @@
     <entry lang="ja" key="IDT_NEW_PASSWORD">パスワード：</entry>
     <entry lang="ja" key="IDT_PARALLELIZATION_OPTIONS">マルチスレッドによる並列処理設定</entry>
     <entry lang="ja" key="IDT_PKCS11_LIB_PATH">PKCS#11ライブラリの場所</entry>
-    <entry lang="ja" key="IDT_PKCS5_PRF">導出アルゴリズム：</entry>
-    <entry lang="ja" key="IDT_NEW_PKCS5_PRF">導出アルゴリズム：</entry>
+    <entry lang="ja" key="IDT_KDF">導出アルゴリズム：</entry>
+    <entry lang="ja" key="IDT_NEW_KDF">導出アルゴリズム：</entry>
     <entry lang="ja" key="IDT_PW_CACHE_OPTIONS">パスワードの記憶</entry>
     <entry lang="ja" key="IDT_SECURITY_OPTIONS">セキュリティオプション</entry>
     <entry lang="ja" key="IDT_EMV_OPTIONS">EMVオプション</entry>
@@ -813,7 +813,7 @@
     <entry lang="ja" key="SECONDARY_KEY_SIZE_LRW">Tweakキーサイズ(LRWモード)</entry>
     <entry lang="ja" key="BITS">ビット</entry>
     <entry lang="ja" key="BLOCK_SIZE">ブロックサイズ</entry>
-    <entry lang="ja" key="PKCS5_PRF">PKCS#5 疑似乱数関数</entry>
+    <entry lang="ja" key="KDF">PKCS#5 疑似乱数関数</entry>
     <entry lang="ja" key="PKCS5_ITERATIONS">PKCS#5 反復回数</entry>
     <entry lang="ja" key="VOLUME_CREATE_DATE">ボリューム作成日時</entry>
     <entry lang="ja" key="VOLUME_HEADER_DATE">ヘッダ最終更新日時</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="ja" key="INSECURE_MODE">[非セキュアモード]</entry>
     <entry lang="ja" key="IDC_DISABLE_SCREEN_PROTECTION">スクリーンショットおよび画面録画に対する保護を無効にする</entry>
     <entry lang="ja" key="DISABLE_SCREEN_PROTECTION_WARNING">警告: 画面保護を無効にすると、セキュリティが大幅に低下します。VeraCrypt のインターフェースをキャプチャする必要がある特定の状況でのみ、このオプションを有効にしてください。Windows 11 の Recall 機能などのスクリーンショットツールや画面録画機能によって、機密データが露出する可能性があります。</entry>
+    <entry lang="ja" key="MEMORY_COST">メモリコスト</entry>
+    <entry lang="ja" key="IDT_KDF_ALGO">KDFアルゴリズム</entry>
+    <entry lang="ja" key="IDD_PREFERENCES_TAB_GENERAL">全般</entry>
+    <entry lang="ja" key="IDD_PREFERENCES_TAB_ACTIONS">操作</entry>
+    <entry lang="ja" key="IDD_PREFERENCES_TAB_PASSWORD">パスワード</entry>
+    <entry lang="ja" key="IDC_SECURE_DESKTOP_ENABLE_IME">セキュアデスクトップでIMEを有効にする</entry>
+    <entry lang="ja" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">警告: セキュアデスクトップでキーファイルやトークンを選択する際に問題が発生する場合にのみ、このオプションを有効にしてください。</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.ka.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="ka" name="ქართული" en-name="Georgian" version="0.1.0" translators="Kakha Lomiashvili" />
     <font lang="ka" class="normal" size="12" face="Arial" />
     <font lang="ka" class="bold" size="12" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="ka" key="IDT_NEW_PASSWORD">პაროლი:</entry>
     <entry lang="en" key="IDT_PARALLELIZATION_OPTIONS">Thread-Based Parallelization</entry>
     <entry lang="en" key="IDT_PKCS11_LIB_PATH">PKCS #11 Library Path</entry>
-    <entry lang="ka" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="en" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="ka" key="IDT_KDF">KDF:</entry>
+    <entry lang="en" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="ka" key="IDT_PW_CACHE_OPTIONS">პაროლების ქეშირება (დამახსოვრება)</entry>
     <entry lang="en" key="IDT_SECURITY_OPTIONS">Security Options</entry>
     <entry lang="en" key="IDT_EMV_OPTIONS">EMV Options</entry>
@@ -813,7 +813,7 @@
     <entry lang="en" key="SECONDARY_KEY_SIZE_LRW">Tweak Key Size (LRW Mode)</entry>
     <entry lang="ka" key="BITS">ბიტი</entry>
     <entry lang="ka" key="BLOCK_SIZE">ბლოკის ზომა</entry>
-    <entry lang="ka" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="ka" key="KDF">KDF</entry>
     <entry lang="ka" key="PKCS5_ITERATIONS">PKCS-5 ოპერაციების რაოდენობა</entry>
     <entry lang="ka" key="VOLUME_CREATE_DATE">ტომი შექმნილია</entry>
     <entry lang="ka" key="VOLUME_HEADER_DATE">სათაურის ბოლო ცვლილება</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="en" key="INSECURE_MODE">[INSECURE MODE]</entry>
     <entry lang="en" key="IDC_DISABLE_SCREEN_PROTECTION">Disable protection against screenshots and screen recording</entry>
     <entry lang="en" key="DISABLE_SCREEN_PROTECTION_WARNING">WARNING: Disabling screen protection significantly reduces security. Enable this option ONLY if you have a specific need to capture VeraCrypt's interface. This may expose sensitive data to screenshot tools and screen recording features such as Windows 11 Recall.</entry>
+    <entry lang="en" key="MEMORY_COST">Memory Cost</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.ko.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="ko" name="한국어" en-name="Korean" version="0.2.0" translators="Kieaer, Herbert Shin, BaekMu" />
     <font lang="ko" class="normal" size="11" face="돋움" />
     <font lang="ko" class="bold" size="13" face="맑은 고딕" />
@@ -291,8 +291,8 @@
     <entry lang="ko" key="IDT_NEW_PASSWORD">암호:</entry>
     <entry lang="ko" key="IDT_PARALLELIZATION_OPTIONS">스레드 기반 병렬화</entry>
     <entry lang="ko" key="IDT_PKCS11_LIB_PATH">PKCS #11 라이브러리 경로</entry>
-    <entry lang="ko" key="IDT_PKCS5_PRF">PKCS-5 PRF</entry>
-    <entry lang="ko" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="ko" key="IDT_KDF">KDF</entry>
+    <entry lang="ko" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="ko" key="IDT_PW_CACHE_OPTIONS">암호 캐시</entry>
     <entry lang="ko" key="IDT_SECURITY_OPTIONS">보안 옵션</entry>
     <entry lang="ko" key="IDT_EMV_OPTIONS">EMV 옵션</entry>
@@ -813,7 +813,7 @@
     <entry lang="ko" key="SECONDARY_KEY_SIZE_LRW">비틀기 키 크기 (LRW 모드)</entry>
     <entry lang="ko" key="BITS">조금</entry>
     <entry lang="ko" key="BLOCK_SIZE">블록 크기</entry>
-    <entry lang="ko" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="ko" key="KDF">KDF</entry>
     <entry lang="ko" key="PKCS5_ITERATIONS">PKCS-5 반복 횟수</entry>
     <entry lang="ko" key="VOLUME_CREATE_DATE">생성 된 볼륨</entry>
     <entry lang="ko" key="VOLUME_HEADER_DATE">헤더가 마지막으로 수정 됨</entry>
@@ -1644,8 +1644,49 @@
     <entry lang="ko" key="MOUNTPOINT_BLOCKED">오류: 볼륨 마운트 위치가 보호된 시스템 디렉터리를 덮어쓰기 때문에 차단되었습니다.\n\n다른 마운트 위치를 선택하세요.</entry>
     <entry lang="ko" key="MOUNTPOINT_NOTALLOWED">오류: 볼륨 마운트 위치가 PATH 환경 변수의 일부인 디렉터리를 덮어쓰기 때문에 허용되지 않습니다.\n\n다른 마운트 위치를 선택하세요.</entry>
     <entry lang="ko" key="INSECURE_MODE">[비보안 모드]</entry>
-    <entry lang="ko" key="IDC_DISABLE_SCREEN_PROTECTION">스크린샷 및 화면 녹화 보호 비활성화하기</entry>  
+    <entry lang="ko" key="IDC_DISABLE_SCREEN_PROTECTION">스크린샷 및 화면 녹화 보호 비활성화하기</entry>
     <entry lang="ko" key="DISABLE_SCREEN_PROTECTION_WARNING">경고: 화면 보호를 비활성화하면 보안이 크게 저하됩니다. VeraCrypt 인터페이스를 캡처해야 하는 특별한 필요가 있을 때만 이 옵션을 활성화하세요. 이 설정은 스크린샷 도구 및 Windows 11 Recall과 같은 화면 녹화 기능에 민감한 데이터가 노출될 수 있습니다.</entry>
+    <entry lang="ko" key="MEMORY_COST">메모리 사용량</entry>
+    <entry lang="ko" key="IDT_KDF_ALGO">KDF 알고리즘</entry>
+    <entry lang="ko" key="IDD_PREFERENCES_TAB_GENERAL">일반</entry>
+    <entry lang="ko" key="IDD_PREFERENCES_TAB_ACTIONS">동작</entry>
+    <entry lang="ko" key="IDD_PREFERENCES_TAB_PASSWORD">암호</entry>
+    <entry lang="ko" key="IDC_SECURE_DESKTOP_ENABLE_IME">보안 데스크톱에서 입력기(IME) 활성화하기</entry>
+    <entry lang="ko" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">경고: 보안 데스크톱에서 키 파일/토큰 선택 시 문제가 발생하는 경우에만 이 옵션을 활성화하세요.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.lv.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="lv" name="Latviešu" en-name="Latvian" version="0.1.0" translators="Edmunds Melkers" />
     <font lang="lv" class="normal" size="11" face="default" />
     <font lang="lv" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="lv" key="IDT_NEW_PASSWORD">Parole:</entry>
     <entry lang="en" key="IDT_PARALLELIZATION_OPTIONS">Thread-Based Parallelization</entry>
     <entry lang="en" key="IDT_PKCS11_LIB_PATH">PKCS #11 Library Path</entry>
-    <entry lang="en" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="en" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="en" key="IDT_KDF">KDF:</entry>
+    <entry lang="en" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="lv" key="IDT_PW_CACHE_OPTIONS">Paroles kešatmiņa</entry>
     <entry lang="en" key="IDT_SECURITY_OPTIONS">Security Options</entry>
     <entry lang="en" key="IDT_EMV_OPTIONS">EMV Options</entry>
@@ -813,7 +813,7 @@
     <entry lang="en" key="SECONDARY_KEY_SIZE_LRW">Tweak Key Size (LRW Mode)</entry>
     <entry lang="lv" key="BITS">biti</entry>
     <entry lang="lv" key="BLOCK_SIZE">Bloka izmērs</entry>
-    <entry lang="lv" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="lv" key="KDF">KDF</entry>
     <entry lang="lv" key="PKCS5_ITERATIONS">PKCS-5 Iterāciju skaits</entry>
     <entry lang="lv" key="VOLUME_CREATE_DATE">Apgabals izveidots</entry>
     <entry lang="lv" key="VOLUME_HEADER_DATE">Galvene pēdējoreiz modificēta</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="en" key="INSECURE_MODE">[INSECURE MODE]</entry>
     <entry lang="en" key="IDC_DISABLE_SCREEN_PROTECTION">Disable protection against screenshots and screen recording</entry>
     <entry lang="en" key="DISABLE_SCREEN_PROTECTION_WARNING">WARNING: Disabling screen protection significantly reduces security. Enable this option ONLY if you have a specific need to capture VeraCrypt's interface. This may expose sensitive data to screenshot tools and screen recording features such as Windows 11 Recall.</entry>
+    <entry lang="en" key="MEMORY_COST">Memory Cost</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.my.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="my" name="မြန်မာ" en-name="Burmese" version="2.0.0" translators="Zaw Myo Htet; Transifex contributors" />
     <font lang="my" class="normal" size="11" face="Myanmar3" />
     <font lang="my" class="bold" size="13" face="Myanmar3" />
@@ -291,8 +291,8 @@
     <entry lang="my" key="IDT_NEW_PASSWORD">စကားဝှက် -</entry>
     <entry lang="my" key="IDT_PARALLELIZATION_OPTIONS">Thread-အခြေပြု ပြိုင်တူပြုလုပ်ခြင်း</entry>
     <entry lang="my" key="IDT_PKCS11_LIB_PATH">PKCS #11 လိုင်ဘရာရီ လမ်းကြောင်း</entry>
-    <entry lang="my" key="IDT_PKCS5_PRF">PKCS-5 PRF-</entry>
-    <entry lang="my" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF -</entry>
+    <entry lang="my" key="IDT_KDF">KDF-</entry>
+    <entry lang="my" key="IDT_NEW_KDF">KDF -</entry>
     <entry lang="my" key="IDT_PW_CACHE_OPTIONS">စကားဝှက် ယာယီ သိမ်းဆည်းခန်း</entry>
     <entry lang="my" key="IDT_SECURITY_OPTIONS">လုံခြုံရေး ရွေးစရာများ</entry>
     <entry lang="en" key="IDT_EMV_OPTIONS">EMV Options</entry>
@@ -815,7 +815,7 @@
     <entry lang="my" key="SECONDARY_KEY_SIZE_LRW">Tweak ကီး အရွယ်ပမာဏ (LRW စနစ်)</entry>
     <entry lang="my" key="BITS">bits</entry>
     <entry lang="my" key="BLOCK_SIZE">အကန့် အရွယ်ပမာဏ</entry>
-    <entry lang="my" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="my" key="KDF">KDF</entry>
     <entry lang="my" key="PKCS5_ITERATIONS">PKCS-5 ထပ်မံ ရေတွက်ခြင်း</entry>
     <entry lang="my" key="VOLUME_CREATE_DATE">Volume ဖန်တီးလိုက်ပြီ</entry>
     <entry lang="my" key="VOLUME_HEADER_DATE">ခေါင်းစီး နောက်ဆုံး ပြုပြင်မှု</entry>
@@ -1648,6 +1648,47 @@
     <entry lang="my" key="INSECURE_MODE">[လုံခြုံမှုမရှိသောမုဒ်]</entry>
     <entry lang="my" key="IDC_DISABLE_SCREEN_PROTECTION">စခရင်ရှော့များနှင့် စခရင်မှတ်တမ်းတင်ခြင်းမှ ကာကွယ်မှုကို ပိတ်ပါ</entry>
     <entry lang="my" key="DISABLE_SCREEN_PROTECTION_WARNING">သတိပေးချက်- စခရင်ကာကွယ်မှုကို ပိတ်ခြင်းသည် လုံခြုံရေးကို သိသိသာသာ လျှော့ချသည်။ VeraCrypt ၏ interface ကို ဖမ်းယူရန် သီးခြားလိုအပ်ချက်ရှိမှသာ ဤရွေးချယ်မှုကို ဖွင့်ပါ။ ၎င်းသည် ထိလွယ်ရှလွယ်ဒေတာများကို စခရင်ရှော့ကိရိယာများနှင့် Windows 11 Recall ကဲ့သို့ စခရင်မှတ်တမ်းတင်ခြင်း အင်္ဂါရပ်များသို့ ဖော်ထုတ်နိုင်သည်။</entry>
+    <entry lang="my" key="MEMORY_COST">မှတ်ဉာဏ်ကုန်ကျစရိတ်</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" attributeFormDefault="unqualified" elementFormDefault="qualified">
     <xs:element name="VeraCrypt">

Translations/Language.nl.xml

@@ -1,7 +1,7 @@
-<?xml version="1.0" encoding="utf-8"?>
+<?xml version='1.0' encoding='UTF-8' standalone='no'?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
-    <language langid="nl" name="Nederlands" en-name="Dutch" version="0.0.0" translators="Jan van der Wal, Peter Tak, Thomas De Rocker"/>
+  <localization prog-version="1.26.28">
+    <language langid="nl" name="Nederlands" en-name="Dutch" version="2026-05-08" translators="Jan van der Wal, Peter Tak, Thomas De Rocker"/>
     <font lang="nl" class="normal" size="11" face="default"/>
     <font lang="nl" class="bold" size="13" face="Arial"/>
     <font lang="nl" class="fixed" size="12" face="Lucida Console"/>
@@ -152,8 +152,8 @@
     <entry lang="nl" key="IDC_MOUNT_OPTIONS">Koppelopties...</entry>
     <entry lang="nl" key="IDC_MOUNT_READONLY">Volume koppelen als alleen-lezen</entry>
     <entry lang="nl" key="IDC_NEW_KEYFILES">Sleutelbestanden...</entry>
-    <entry lang="nl" key="IDC_OLD_PIM_HELP">(Leeg of 0 voor standaard iteraties)</entry>
-    <entry lang="nl" key="IDC_PIM_HELP">(leeg of 0 voor standaard iteraties)</entry>
+    <entry lang="nl" key="IDC_OLD_PIM_HELP">(Leeg of 0 voor standaardwaarden)</entry>
+    <entry lang="nl" key="IDC_PIM_HELP">(Leeg of 0 voor standaardwaarden)</entry>
     <entry lang="nl" key="IDC_PREF_BKG_TASK_ENABLE">Ingeschakeld</entry>
     <entry lang="nl" key="IDC_PREF_CACHE_PASSWORDS">Wachtw. in stuurprog.-geheugen opslaan</entry>
     <entry lang="nl" key="IDC_PREF_UNMOUNT_INACTIVE">Volume automatisch ontkoppelen na inactiviteit lezen/schrijven van</entry>
@@ -291,8 +291,8 @@
     <entry lang="nl" key="IDT_NEW_PASSWORD">Wachtwoord:</entry>
     <entry lang="nl" key="IDT_PARALLELIZATION_OPTIONS">Threadgebaseerde parallellisatie</entry>
     <entry lang="nl" key="IDT_PKCS11_LIB_PATH">Pad naar PKCS #11 bibliotheek</entry>
-    <entry lang="nl" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="nl" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="nl" key="IDT_KDF">KDF:</entry>
+    <entry lang="nl" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="nl" key="IDT_PW_CACHE_OPTIONS">Wachtwoordcache</entry>
     <entry lang="nl" key="IDT_SECURITY_OPTIONS">Beveiligingsopties</entry>
     <entry lang="nl" key="IDT_EMV_OPTIONS">EMV-opties</entry>
@@ -813,7 +813,7 @@
     <entry lang="nl" key="SECONDARY_KEY_SIZE_LRW">Tweak-sleutelgrootte (LRW-modus)</entry>
     <entry lang="nl" key="BITS">bits</entry>
     <entry lang="nl" key="BLOCK_SIZE">Blokgrootte</entry>
-    <entry lang="nl" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="nl" key="KDF">KDF</entry>
     <entry lang="nl" key="PKCS5_ITERATIONS">PKCS-5-iteratieteller</entry>
     <entry lang="nl" key="VOLUME_CREATE_DATE">Volume aangemaakt</entry>
     <entry lang="nl" key="VOLUME_HEADER_DATE">Header laatst gewijzigd</entry>
@@ -1644,8 +1644,49 @@
     <entry lang="nl" key="MOUNTPOINT_BLOCKED">FOUT: Het koppelpunt van het volume is geblokkeerd omdat het een beveiligde systeemmap overschrijft.\n\nKies een ander koppelpunt.</entry>
     <entry lang="nl" key="MOUNTPOINT_NOTALLOWED">FOUT: het koppelpunt voor het volume is niet toegestaan omdat het een map overschrijft die deel uitmaakt van de omgevingsvariabele PATH.\n\nKies een ander koppelpunt.</entry>
     <entry lang="nl" key="INSECURE_MODE">[ONVEILIGE MODUS]</entry>
-    <entry lang="nl" key="IDC_DISABLE_SCREEN_PROTECTION">Bescherming tegen schermafbeeldingen en schermopnames uitschakelen</entry>
-    <entry lang="nl" key="DISABLE_SCREEN_PROTECTION_WARNING">WAARSCHUWING: Het uitschakelen van schermbeveiliging vermindert de veiligheid aanzienlijk. Schakel deze optie ALLEEN in als u een specifieke noodzaak hebt om de interface van VeraCrypt vast te leggen. Dit kan gevoelige gegevens blootstellen aan schermafbeeldingstools en schermopnamefuncties zoals Windows 11 Recall.</entry>
+    <entry lang="nl" key="IDC_DISABLE_SCREEN_PROTECTION">Bescherming tegen screenshots en schermopname uitschakelen</entry>
+    <entry lang="nl" key="DISABLE_SCREEN_PROTECTION_WARNING">WAARSCHUWING: het uitschakelen van schermbeveiliging vermindert de beveiliging aanzienlijk. Schakel deze optie ALLEEN in als u een specifieke behoefte hebt om de interface van VeraCrypt vast te leggen. Dit kan gevoelige gegevens blootstellen aan screenshotprogramma's en schermopnamefuncties zoals Windows 11 Recall.</entry>
+    <entry lang="nl" key="MEMORY_COST">Geheugengebruik</entry>
+    <entry lang="nl" key="IDT_KDF_ALGO">KDF-algoritme</entry>
+    <entry lang="nl" key="IDD_PREFERENCES_TAB_GENERAL">Algemeen</entry>
+    <entry lang="nl" key="IDD_PREFERENCES_TAB_ACTIONS">Acties</entry>
+    <entry lang="nl" key="IDD_PREFERENCES_TAB_PASSWORD">Wachtwoord</entry>
+    <entry lang="nl" key="IDC_SECURE_DESKTOP_ENABLE_IME">De invoermethode-editor (IME) inschakelen in Secure Desktop</entry>
+    <entry lang="nl" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WAARSCHUWING: schakel deze optie alleen in als u problemen ondervindt bij het selecteren van sleutelbestanden/tokens onder Secure Desktop.</entry>
+    <entry lang="nl" key="ERR_KEY_DERIVATION_FAILED">Het afleiden van de sleutel is mislukt. Dit kan worden veroorzaakt door onvoldoende geheugen of een onderbroken bewerking.</entry>
+    <entry lang="nl" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">De systeempartitie/schijf is al ontsleuteld, maar het pad naar de EFI-bootloader van Microsoft is niet hersteld in de Windows Boot Manager. Alleen de EFI-opstartbestanden moeten worden gerepareerd. Gebruik de reparatieoptie van de VeraCrypt Rescue Disk, of start op vanaf het Windows-herstelmedium en voer ‘bcdboot W:\\Windows /s S: /f UEFI’ uit, waarbij u W: vervangt door de stationsletter van het Windows-volume en S: door de stationsletter van de EFI-systeempartitie. Pad:</entry>
+    <entry lang="nl" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">De systeempartitie/schijf is al ontsleuteld, maar het pad naar de fallback-EFI-bootloader bevat nog steeds de VeraCrypt-bootloader. Alleen de EFI-opstartbestanden moeten worden gerepareerd. Gebruik de reparatieoptie van de VeraCrypt Rescue Disk, of start op vanaf het Windows-herstelmedium en voer ‘bcdboot W:\\Windows /s S: /f UEFI’ uit, waarbij u W: vervangt door de stationsletter van het Windows-volume en S: door de stationsletter van de EFI-systeempartitie. Pad:</entry>
+    <entry lang="nl" key="IDM_REPAIR_EFI_BOOT_LOADER">EFI-bootloader repareren...</entry>
+    <entry lang="nl" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt herstelt de paden van de Windows EFI-bootloader en verwijdert de EFI-opstartvermeldingen en -bestanden van VeraCrypt.\n\nGebruik deze optie alleen nadat de systeempartitie/het systeemstation volledig is ontsleuteld en Windows kan opstarten zonder systeemversleuteling.\n\nWilt u doorgaan?</entry>
+    <entry lang="nl" key="EFI_BOOT_LOADER_FILE_READ_FAILED">Het EFI-bootloaderbestand kon niet volledig worden gelezen:</entry>
+    <entry lang="nl" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">Het EFI-bootloaderbestand is onverwacht groot en is niet gecontroleerd:</entry>
+    <entry lang="nl" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">De systeempartitie/schijf is al ontsleuteld en de EFI-bootloaderbestanden zijn hersteld, maar VeraCrypt kon een of meer VeraCrypt-firmware-opstartvermeldingen niet verwijderen. De VeraCrypt-EFI-bestanden zijn op hun plaats gelaten, waardoor eventuele resterende firmware-vermeldingen nog steeds naar een bestaande bootloader verwijzen. Probeer het opnieuw als beheerder of verwijder de VeraCrypt-opstartvermelding uit de firmware-instellingen nadat u hebt gecontroleerd of Windows Boot Manager normaal opstart.</entry>
+    <entry lang="nl" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">De EFI-bootloader kan niet worden gerepareerd terwijl de systeemversleuteling of -ontsleuteling actief of nog niet voltooid is. Voltooi of hervat het lopende systeemversleutelings- of -ontsleutelingsproces voordat u het opnieuw probeert.</entry>
+    <entry lang="nl" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">Deze reparatie is alleen beschikbaar op systemen die in UEFI-modus opstarten vanaf een GPT-systeempartitie.</entry>
+    <entry lang="nl" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">De EFI-bootloader is met succes gerepareerd.</entry>
+    <entry lang="nl" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) bepaalt de geheugen- en tijdskosten van de Argon2id header key afleiding als volgt:\n      Geheugen = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iteraties = 3 + ((PIM - 1) / 3) voor PIM 31 of lager, daarna 13 + (PIM - 31)\n\nWanneer dit veld leeg wordt gelaten of op 0 wordt ingesteld, gebruikt VeraCrypt de standaard Argon2 PIM (12), die 416 MiB geheugen en 6 iteraties gebruikt.\n\nWanneer het wachtwoord minder dan 20 tekens bevat, mag Argon2 PIM niet kleiner zijn dan 12 om een minimaal beveiligingsniveau te behouden.\nWanneer het wachtwoord 20 tekens of meer bevat, kan Argon2 PIM op elke waarde worden ingesteld.\n\nEen Argon2 PIM groter dan 12 verhoogt het geheugengebruik tot 1024 MiB en verhoogt vervolgens het aantal iteraties. Dit leidt tot een tragere koppeling. Een kleine Argon2 PIM (minder dan 12) leidt tot een snellere koppeling, maar kan de beveiliging verminderen als het wachtwoord niet sterk genoeg is.</entry>
+    <entry lang="nl" key="PIM_ARGON2_LARGE_WARNING">U hebt een Argon2 PIM-waarde gekozen die hoger is dan de standaardwaarde van VeraCrypt.\nHoud er rekening mee dat dit meer geheugen kan vergen en kan leiden tot een aanzienlijk tragere koppeling.</entry>
+    <entry lang="nl" key="PIM_ARGON2_SMALL_WARNING">U hebt een Argon2-PIM-waarde gekozen die lager is dan de standaardwaarde van VeraCrypt. Houd er rekening mee dat als uw wachtwoord niet sterk genoeg is, dit kan leiden tot een lagere beveiliging.\n\nBevestigt u dat u een sterk wachtwoord gebruikt?</entry>
+    <entry lang="nl" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Het wachtwoord moet uit minimaal 20 tekens bestaan om de opgegeven Argon2-PIM te kunnen gebruiken.\nKortere wachtwoorden kunnen alleen worden gebruikt als de Argon2-PIM 12 of hoger is.</entry>
+    <entry lang="nl" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">NTFS-volumes koppelen met het ntfs3-stuurprogramma van de Linux-kernel</entry>
+    <entry lang="nl" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Alleen voor Linux. Wanneer deze optie is ingeschakeld, controleert VeraCrypt het ontsleutelde virtuele apparaat met `blkid -p` en koppelt het gedetecteerde NTFS-bestandssystemen met ntfs3 in plaats van de standaard NTFS-backend. Als de NTFS-detectie mislukt, gebruikt VeraCrypt de normale automatische bestandssysteemselectie. Als ntfs3 niet beschikbaar is of door de distributie wordt geblokkeerd, kan het koppelen mislukken. Deze opt-in-optie kan vastlopen tijdens slaapstand of sluimerstand voorkomen dat wordt veroorzaakt door bevroren FUSE-bestandssystemen in de gebruikersruimte.</entry>
+    <entry lang="nl" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Het normaal ontkoppelen van volume {0} is mislukt. Dit kan gebeuren wanneer applicaties nog bestanden of mappen op het volume open hebben staan, of wanneer het onderliggende apparaat is losgekoppeld en de koppeling verouderd is geraakt.\n\nAls het apparaat nog is aangesloten, kies dan ‘Nee’, sluit de applicaties die het volume gebruiken en probeer het ontkoppelen opnieuw.\n\nAls het apparaat is losgekoppeld of de koppeling verouderd is, kan VeraCrypt een noodopruiming uitvoeren door het bestandssysteem lui los te koppelen en VeraCrypt-kernelobjecten te verwijderen of de verwijdering ervan in te plannen. Lopende schrijfbewerkingen zijn mogelijk mislukt, er kan gegevensverlies optreden en de opruiming kan in behandeling blijven totdat applicaties geopende bestanden sluiten. Controleer het bestandssysteem met fsck of het juiste reparatieprogramma voordat u het opnieuw gebruikt.\n\nDoorgaan?</entry>
+    <entry lang="nl" key="LINUX_EMERGENCY_UNMOUNTED">De noodopruiming voor volume {0} is gestart. Als het volume was losgekoppeld, de koppeling verouderd was of er nog schrijfbewerkingen in de wachtrij stonden, controleer dan het bestandssysteem met fsck of het juiste reparatieprogramma voordat u het weer gebruikt.</entry>
+    <entry lang="nl" key="FORMAT_STAGE_WRITING_DATA">Volumegegevens aanmaken. Even geduld.</entry>
+    <entry lang="nl" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Aanmaken van volume voltooien: backup-header schrijven.</entry>
+    <entry lang="nl" key="FORMAT_STAGE_FLUSHING_DATA">Aanmaken van volume voltooien: gegevens worden naar de schijf geschreven. Dit kan enkele minuten duren bij grote volumes of bij trage opslagmedia of USB-opslag.</entry>
+    <entry lang="nl" key="FORMAT_STAGE_FINISHED">Aanmaken van volume voltooien.</entry>
+    <entry lang="nl" key="FORMAT_STAGE_ABORTED">Het aanmaken van het volume is afgebroken.</entry>
+    <entry lang="nl" key="FORMAT_STAGE_ERROR">Het aanmaken van het volume is mislukt.</entry>
+    <entry lang="nl" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Aanmaken van volume voltooien: tijdelijk volume koppelen.</entry>
+    <entry lang="nl" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Aanmaken van volume voltooien: tijdelijk apparaat voorbereiden.</entry>
+    <entry lang="nl" key="FORMAT_STAGE_CREATING_FILESYSTEM">Aanmaken van volume voltooien: bestandssysteem aanmaken met {0}.</entry>
+    <entry lang="nl" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Aanmaken van volume voltooien: tijdelijk volume ontkoppelen.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" attributeFormDefault="unqualified" elementFormDefault="qualified">
     <xs:element name="VeraCrypt">

Translations/Language.nn.xml

@@ -1,11 +1,11 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="nn" name="Norsk Nynorsk" en-name="Norwegian (Nynorsk)" version="0.1.0" translators="Kjell Rune Helland" />
     <font lang="nn" class="normal" size="11" face="default" />
-    <font lang="nn" class="bold" size="13" face="Arial " />
-    <font lang="nn" class="fixed" size="12" face="Lucida Console " />
-    <font lang="nn" class="title" size="21" face="Times New Roman " />
+    <font lang="nn" class="bold" size="13" face="Arial" />
+    <font lang="nn" class="fixed" size="12" face="Lucida Console" />
+    <font lang="nn" class="title" size="21" face="Times New Roman" />
     <entry lang="nn" key="IDCANCEL">Avbryt</entry>
     <entry lang="en" key="IDC_ALL_USERS">Install &amp;for all users</entry>
     <entry lang="en" key="IDC_BROWSE">Bro&amp;wse...</entry>
@@ -291,8 +291,8 @@
     <entry lang="nn" key="IDT_NEW_PASSWORD">Passord:</entry>
     <entry lang="en" key="IDT_PARALLELIZATION_OPTIONS">Thread-Based Parallelization</entry>
     <entry lang="en" key="IDT_PKCS11_LIB_PATH">PKCS #11 Library Path</entry>
-    <entry lang="nn" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="nn" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="nn" key="IDT_KDF">KDF:</entry>
+    <entry lang="nn" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="nn" key="IDT_PW_CACHE_OPTIONS">Passord Snøgglager</entry>
     <entry lang="en" key="IDT_SECURITY_OPTIONS">Security Options</entry>
     <entry lang="en" key="IDT_EMV_OPTIONS">EMV Options</entry>
@@ -813,7 +813,7 @@
     <entry lang="en" key="SECONDARY_KEY_SIZE_LRW">Tweak Key Size (LRW Mode)</entry>
     <entry lang="nn" key="BITS">bits</entry>
     <entry lang="nn" key="BLOCK_SIZE">Blokk Størrelse</entry>
-    <entry lang="nn" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="nn" key="KDF">KDF</entry>
     <entry lang="nn" key="PKCS5_ITERATIONS">PKCS-5 gjenntakings tal</entry>
     <entry lang="nn" key="VOLUME_CREATE_DATE">Volum Oppretta</entry>
     <entry lang="nn" key="VOLUME_HEADER_DATE">Header Sist Endra</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="en" key="INSECURE_MODE">[INSECURE MODE]</entry>
     <entry lang="en" key="IDC_DISABLE_SCREEN_PROTECTION">Disable protection against screenshots and screen recording</entry>
     <entry lang="en" key="DISABLE_SCREEN_PROTECTION_WARNING">WARNING: Disabling screen protection significantly reduces security. Enable this option ONLY if you have a specific need to capture VeraCrypt's interface. This may expose sensitive data to screenshot tools and screen recording features such as Windows 11 Recall.</entry>
+    <entry lang="en" key="MEMORY_COST">Memory Cost</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.pl.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="pl" name="Polski" en-name="Polish" version="1.0.0" translators="Mirek Druchowicz, Janusz Zamecki, Sobiesław Antolak, Begina Felicysym" />
     <font lang="pl" class="normal" size="11" face="default" />
     <font lang="pl" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="pl" key="IDT_NEW_PASSWORD">Hasło:</entry>
     <entry lang="pl" key="IDT_PARALLELIZATION_OPTIONS">Zrównoleglanie wątków</entry>
     <entry lang="pl" key="IDT_PKCS11_LIB_PATH">Ścieżka biblioteki PKCS #11</entry>
-    <entry lang="pl" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="pl" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="pl" key="IDT_KDF">KDF:</entry>
+    <entry lang="pl" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="pl" key="IDT_PW_CACHE_OPTIONS">Pamięć haseł</entry>
     <entry lang="pl" key="IDT_SECURITY_OPTIONS">Opcje bezpieczeństwa</entry>
     <entry lang="pl" key="IDT_EMV_OPTIONS">Opcje EMV</entry>
@@ -646,8 +646,8 @@
     <entry lang="pl" key="PIM_HELP">PIM (Personal Iterations Multiplier), czyli mnożnik osobistych iteracji, to wartość, która następująco kontroluje liczbę iteracji używanych przez derywację klucza nagłówka:\n		Iteracje = 15000 + (PIM x 1000).\n\nGdy pozostawione puste lub ustawione na 0, VeraCrypt użyje wartości domyślnej (485), która zapewnia wysokie bezpieczeństwo.\nGdy hasło jest krótsze niż 20 znaków, PIM nie może być mniejszy niż 485, aby zapewnić minimalny poziom bezpieczeństwa.\nGdy hasło ma 20 znaków lub więcej, PIM może mieć dowolną wartość.\nWartość PIM większa niż 485 spowoduje wolniejsze podłączanie, mała wartość PIM (mniejsza niż 485) spowoduje szybsze podłączanie, ale może zmniejszyć poziom bezpieczeństwa, gdy hasło nie jest wystarczająco silne.</entry>
     <entry lang="pl" key="PIM_SYSENC_HELP">PIM (Personal Iterations Multiplier), czyli mnożnik osobistych iteracji, to wartość, która następująco kontroluje liczbę iteracji używanych przez derywację klucza nagłówka:\n		Iteracje = PIM x 2048.\n\nGdy pozostawione puste lub ustawione na 0, VeraCrypt użyje wartości domyślnej, która zapewnia wysokie bezpieczeństwo.\nGdy hasło jest krótsze niż 20 znaków, PIM nie może być mniejszy niż 98, aby zapewnić minimalny poziom bezpieczeństwa.\nGdy hasło ma 20 znaków lub więcej, PIM może mieć dowolną wartość.\nWartość PIM większa niż 98 spowoduje wolniejsze podłączanie, mała wartość PIM (mniejsza niż 98) spowoduje szybsze podłączanie, ale może zmniejszyć poziom bezpieczeństwa, gdy hasło nie jest wystarczająco silne.</entry>
     <entry lang="pl" key="PIM_SYSENC_CHANGE_WARNING">Zapamiętaj liczbę do uruchomienia systemu</entry>
-    <entry lang="pl" key="PIM_LARGE_WARNING">Wybrałeś wartość PIM, która jest większa niż standardowa wartość VeraCrypt.\nProszę zauważyć, że doprowadzi to do znacznie wolniejszego podłączania lub uruchamiania.</entry>
-    <entry lang="pl" key="PIM_SMALL_WARNING">Wybrałeś PIM, który jest mniejszy niż podstawowa wartość VeraCrypt. Proszę zauważyć, że jeżeli twoje hasło nie jest wystarczająco mocne, moze to doprowadzić do osłabienia bezpieczeństwa.\n\nCzy potwierdzasz użycie silnego hasła?</entry>
+    <entry lang="pl" key="PIM_LARGE_WARNING">Wybrano wartość PIM większą niż domyślna wartość VeraCrypt.\nNależy pamiętać, że może to doprowadzić do znacznie wolniejszego podłączania lub uruchamiania.</entry>
+    <entry lang="pl" key="PIM_SMALL_WARNING">Wybrano wartość PIM mniejszą niż domyślna wartość VeraCrypt. Należy pamiętać, że jeśli hasło nie jest wystarczająco silne, może to prowadzić do osłabienia zabezpieczeń.\n\nCzy potwierdzasz użycie silnego hasła?</entry>
     <entry lang="pl" key="PIM_SYSENC_TOO_BIG">Maksymalna wartość PIM dla szyfrowania systemu wynosi 65535.</entry>
     <entry lang="pl" key="PIM_TITLE">PIM wolumenu</entry>
     <entry lang="pl" key="HIDDEN_FILES_PRESENT_IN_KEYFILE_PATH">\n\nOSTRZEŻENIE: Odnaleziono pliki ukryte na ścieżce wyszukiwaniu plików-kluczy. Takie pliki nie moga zostać użyte jako pliki-klucze. Jeśli potrzebujesz ich jako plików-kluczy, usuń atrybut 'ukryty' (kliknij prawym przyciskiem myszki na każdym z nich, wybierz 'Właściwości', odznacz 'Ukryty' i wciśnij OK). Sugestia: Pliki ukryte widoczne są tylko jeśli włączona jest odpowiednia opcja (Komputer &gt; Organizuj &gt; 'Opcje folderów i wyszukiwania' &gt; Widok).</entry>
@@ -813,7 +813,7 @@
     <entry lang="pl" key="SECONDARY_KEY_SIZE_LRW">Dopasowanie wielkości klucza (tryb LRW)</entry>
     <entry lang="pl" key="BITS">bity</entry>
     <entry lang="pl" key="BLOCK_SIZE">Wielkość bloku</entry>
-    <entry lang="pl" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="pl" key="KDF">KDF</entry>
     <entry lang="pl" key="PKCS5_ITERATIONS">Licznik Iteracji PKCS-5</entry>
     <entry lang="pl" key="VOLUME_CREATE_DATE">Utworzono wolumen</entry>
     <entry lang="pl" key="VOLUME_HEADER_DATE">Data ostatniej modyfikacji nagłówka</entry>
@@ -1103,7 +1103,7 @@
     <entry lang="pl" key="ALGO_NOT_SUPPORTED_FOR_SYS_ENCRYPTION">Ten algorytm nie jest obecnie obsługiwany do szyfrowania systemu.</entry>
     <entry lang="pl" key="ALGO_NOT_SUPPORTED_FOR_TRUECRYPT_MODE">Ten algorytm nie jest obsługiwany w trybie TrueCrypt.</entry>
     <entry lang="pl" key="PIM_NOT_SUPPORTED_FOR_TRUECRYPT_MODE">PIM nie obsługuje trybu TrueCrypt.</entry>
-    <entry lang="pl" key="PIM_REQUIRE_LONG_PASSWORD">Hasło musi zawierać przynajmniej 20 albo więcej znaków, aby móc używać określonego PIM.\nKrótsze hasła mogą być używane tylko wtedy, gdy PIM wynosi 485 albo więcej.</entry>
+    <entry lang="pl" key="PIM_REQUIRE_LONG_PASSWORD">Hasło musi zawierać przynajmniej 20 albo więcej znaków do używania określonego PIM.\nKrótszych haseł można używać tylko wtedy, gdy PIM ma wartość 485 albo większą.</entry>
     <entry lang="pl" key="BOOT_PIM_REQUIRE_LONG_PASSWORD">Hasło uwierzytelniania przed uruchomieniem musi zawierać 20 albo więcej znaków, aby móc używać określonego PIM.\nKrótsze hasła mogą być używane tylko wtedy, gdy PIM wynosi 98 albo więcej.</entry>
     <entry lang="pl" key="KEYFILES_NOT_SUPPORTED_FOR_SYS_ENCRYPTION">Pliki-klucze nie są obecnie obsługiwane/wspierane do szyfrowania systemu.</entry>
     <entry lang="pl" key="CANNOT_RESTORE_KEYBOARD_LAYOUT">Ostrzeżenie: Program VeraCrypt nie mógł odtworzyć oryginalnych ustawień klawiatury. To może spowodować błędne wprowadzenie hasła.</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="pl" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Błąd: Dysk używa rozmiaru sektora innego niż 512 bajty.\n\nZe względu na ograniczenia komponentów dostępnych na Twojej platformie wolumeny oparte na partycjach/urządzeniu nie mogą być tworzone/używane na dysku.\n\nMożliwe rozwiązania:\n- Utwórz na dysku wolumen (kontener) oparty na pliku.\n- Użyj dysku z sektorami 512-bajtowymi.\n- Użyj VeraCrypt na innej platformie.</entry>
     <entry lang="pl" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">Plik/urządzenie hosta jest już używane.</entry>
     <entry lang="pl" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Miejsce na wolumen jest niedostępne.</entry>
-    <entry lang="pl" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt wymaga macFUSE w wersji 2.5 lub nowszego.</entry>
+    <entry lang="pl" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt wymaga macFUSE w wersji 2.5 lub nowszej.</entry>
     <entry lang="pl" key="EXCEPTION_OCCURRED">Wystąpił wyjątek.</entry>
     <entry lang="pl" key="ENTER_PASSWORD">Wprowadź hasło</entry>
     <entry lang="pl" key="ENTER_TC_VOL_PASSWORD">Wprowadź hasło wolumenu VeraCrypt</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="pl" key="INSECURE_MODE">[TRYB NIEBEZPIECZNY]</entry>
     <entry lang="pl" key="IDC_DISABLE_SCREEN_PROTECTION">Wyłącz ochronę przed zrzutami ekranu i nagrywaniem ekranu</entry>
     <entry lang="pl" key="DISABLE_SCREEN_PROTECTION_WARNING">OSTRZEŻENIE: Wyłączenie ochrony ekranu znacząco obniża poziom bezpieczeństwa. Włącz tę opcję TYLKO wtedy, gdy musisz przechwycić interfejs VeraCrypt. Może to narazić wrażliwe dane na dostęp narzędzi do zrzutów ekranu i funkcji nagrywania ekranu, takich jak Windows 11 Recall.</entry>
+    <entry lang="pl" key="MEMORY_COST">Koszt pamięci</entry>
+    <entry lang="pl" key="IDT_KDF_ALGO">Algorytm KDF</entry>
+    <entry lang="pl" key="IDD_PREFERENCES_TAB_GENERAL">Ogólne</entry>
+    <entry lang="pl" key="IDD_PREFERENCES_TAB_ACTIONS">Działania</entry>
+    <entry lang="pl" key="IDD_PREFERENCES_TAB_PASSWORD">Hasło</entry>
+    <entry lang="pl" key="IDC_SECURE_DESKTOP_ENABLE_IME">Włącz edytor metody wprowadzania (IME) na bezpiecznym pulpicie</entry>
+    <entry lang="pl" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">OSTRZEŻENIE: Włącz tę opcję tylko wtedy, gdy napotykasz problemy przy wybieraniu plików-kluczy/tokenów na bezpiecznym pulpicie.</entry>
+    <entry lang="pl" key="ERR_KEY_DERIVATION_FAILED">Nie powiodła się derywacja klucza. Przyczyną może być niewystarczająca ilość pamięci lub przerwanie operacji.</entry>
+    <entry lang="pl" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">Partycję/dysk systemowy już odszyfrowano, ale ścieżka programu rozruchowego EFI Microsoftu nie została przywrócona do menedżera rozruchu systemu Windows. Naprawy wymagają tylko pliki rozruchowe EFI. Użyj opcji naprawy za pomocą płyty odzyskiwania VeraCrypt lub uruchom nośnik odzyskiwania systemu Windows i wykonaj polecenie „bcdboot W:\\Windows /s S: /f UEFI” po zastąpieniu W: literą dysku wolumenu Windows, a S: literą dysku partycji systemowej EFI. Ścieżka:</entry>
+    <entry lang="pl" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">Partycję/dysk systemowy już odszyfrowano, ale ścieżka awaryjnego programu rozruchowego EFI nadal zawiera program rozruchowy VeraCrypt. Naprawy wymagają tylko pliki rozruchowe EFI. Użyj opcji naprawy za pomocą płyty odzyskiwania VeraCrypt lub uruchom nośnik odzyskiwania systemu Windows i wykonaj polecenie „bcdboot W:\\Windows /s S: /f UEFI” po zastąpieniu W: literą dysku wolumenu Windows, a S: literą dysku partycji systemowej EFI. Ścieżka:</entry>
+    <entry lang="pl" key="IDM_REPAIR_EFI_BOOT_LOADER">Napraw program rozruchowy EFI...</entry>
+    <entry lang="pl" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt przywróci ścieżki programu rozruchowego EFI Windows i usunie wpisy rozruchowe oraz pliki EFI VeraCrypt.\n\nUżyj tego tylko po całkowitym odszyfrowaniu partycji/dysku systemowego, gdy system Windows będzie mógł się uruchomić bez szyfrowania systemu.\n\nCzy chcesz kontynuować?</entry>
+    <entry lang="pl" key="EFI_BOOT_LOADER_FILE_READ_FAILED">Nie udało się w pełni odczytać pliku programu rozruchowego EFI:</entry>
+    <entry lang="pl" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">Plik programu rozruchowego EFI jest nieoczekiwanie duży i nie został sprawdzony:</entry>
+    <entry lang="pl" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">Partycję/dysk systemowy już odszyfrowano, a pliki programu rozruchowego EFI zostały przywrócone, ale VeraCrypt nie mógł usunąć jednego lub więcej wpisów rozruchowych oprogramowania układowego VeraCrypt. Pliki EFI VeraCrypt zostały pozostawione, więc wszelkie pozostałe wpisy oprogramowania układowego nadal wskazują na istniejący program rozruchowy. Spróbuj ponownie jako administrator lub usuń wpis rozruchowy VeraCrypt z konfiguracji oprogramowania układowego po potwierdzeniu, że menedżer rozruchu systemu Windows uruchamia się prawidłowo.</entry>
+    <entry lang="pl" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">Nie można naprawić programu rozruchowego EFI, gdy szyfrowanie lub deszyfrowanie systemu jest aktywne lub nieukończone. Przed ponowną próbą zakończ lub wznów oczekujący proces szyfrowania/deszyfrowania systemu.</entry>
+    <entry lang="pl" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">Ta czynność naprawcza jest dostępna tylko w systemach uruchamianych w trybie UEFI z partycji systemowej GPT.</entry>
+    <entry lang="pl" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">Program rozruchowy EFI został pomyślnie naprawiony.</entry>
+    <entry lang="pl" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier), czyli mnożnik osobistych iteracji, kontroluje koszty pamięci i czasu używane przez derywację klucza nagłówka Argon2id w następujący sposób:\n      Pamięć = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iteracje = 3 + ((PIM - 1) / 3) dla PIM 31 lub niższego, następnie 13 + (PIM - 31)\n\nJeśli pozostanie pusty lub ustawiony na 0, VeraCrypt użyje domyślnego PIM Argon2 (12), który używa 416 MiB pamięci i 6 iteracji.\n\nJeśli hasło ma mniej niż 20 znaków, PIM Argon2 nie może być mniejszy niż 12, aby utrzymać minimalny poziom bezpieczeństwa.\nJeśli hasło ma 20 znaków lub więcej, PIM Argon2 można ustawić na dowolną wartość.\n\nPIM Argon2 większy niż 12 zwiększa użycie pamięci do 1024 MiB, a następnie zwiększa liczbę iteracji. Doprowadzi to do wolniejszego podłączania. Niski PIM Argon2 (mniej niż 12) zapewni szybsze podłączanie, ale może obniżyć bezpieczeństwo, jeśli hasło nie będzie wystarczająco silne.</entry>
+    <entry lang="pl" key="PIM_ARGON2_LARGE_WARNING">Wybrano wartość PIM Argon2 większą niż domyślna wartość VeraCrypt.\nNależy pamiętać, że może to wymagać więcej pamięci i prowadzić do znacznie wolniejszego podłączania.</entry>
+    <entry lang="pl" key="PIM_ARGON2_SMALL_WARNING">Wybrano wartość PIM Argon2 mniejszą niż domyślna wartość VeraCrypt. Należy pamiętać, że jeśli hasło nie jest wystarczająco silne, może to prowadzić do osłabienia zabezpieczeń.\n\nCzy potwierdzasz użycie silnego hasła?</entry>
+    <entry lang="pl" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Hasło musi zawierać przynajmniej 20 albo więcej znaków do używania określonego PIM Argon2.\nKrótszych haseł można używać tylko wtedy, gdy PIM Argon2 ma wartość 12 lub większą.</entry>
+    <entry lang="pl" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Podłączaj wolumeny NTFS za pomocą sterownika ntfs3 jądra systemu Linux</entry>
+    <entry lang="pl" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Tylko system Linux. Po włączeniu tej opcji VeraCrypt skanuje odszyfrowane urządzenie wirtualne za pomocą blkid -p i podłącza wykryte systemy plików NTFS za pomocą sterownika NTFS3 zamiast domyślnego NTFS. Jeśli wykrycie NTFS się nie powiedzie, VeraCrypt użyje standardowego automatycznego wyboru systemu plików. Jeśli NTFS3 jest niedostępny lub zablokowany przez dystrybucję, podłączenie może się nie powieść. To opcjonalne ustawienie pozwala uniknąć zawieszeń w trybie uśpienia lub hibernacji spowodowanych przez zamrożone systemy plików FUSE w przestrzeni użytkownika.</entry>
+    <entry lang="pl" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Nie udało się wykonać normalnego odłączenia wolumenu {0}. Może się to zdarzyć, gdy programy nadal mają otwarte pliki lub katalogi na wolumenie lub gdy urządzenie bazowe zostało rozłączone, a podłączenie stało się nieaktualne.\n\nJeśli urządzenie jest nadal podłączone, wybierz opcję „Nie”, zamknij programy korzystające z wolumenu i spróbuj ponownie odłączyć.\n\nJeśli urządzenie zostało rozłączone lub podłączenie jest nieaktualne, VeraCrypt może podjąć próbę awaryjnego czyszczenia poprzez leniwe odłączenie systemu plików i usunięcie lub zaplanowanie usunięcia obiektów jądra VeraCrypt. Oczekujące zapisy mogły się nie powieść, dane mogły zostać utracone, a czyszczenie może pozostać w toku do momentu zamknięcia otwartych plików przez programy. Sprawdź system plików za pomocą fsck lub odpowiedniego narzędzia naprawczego przed ponownym użyciem.\n\nKontynuować?</entry>
+    <entry lang="pl" key="LINUX_EMERGENCY_UNMOUNTED">Rozpoczęto awaryjne czyszczenie wolumenu {0}. Jeśli wolumen był rozłączony, podłączenie było nieaktualne lub występowały oczekujące operacje zapisu, sprawdź system plików za pomocą fsck lub odpowiedniego narzędzia naprawczego przed ponownym użyciem.</entry>
+    <entry lang="pl" key="FORMAT_STAGE_WRITING_DATA">Tworzenie danych wolumenu. Proszę czekać.</entry>
+    <entry lang="pl" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizowanie tworzenia wolumenu: zapisywanie nagłówka kopii zapasowej.</entry>
+    <entry lang="pl" key="FORMAT_STAGE_FLUSHING_DATA">Finalizowanie tworzenia wolumenu: zrzucanie danych na dysk. Może to potrwać kilka minut w przypadku dużych wolumenów lub wolnych nośników danych/pamięci USB.</entry>
+    <entry lang="pl" key="FORMAT_STAGE_FINISHED">Finalizowanie tworzenia wolumenu.</entry>
+    <entry lang="pl" key="FORMAT_STAGE_ABORTED">Tworzenie wolumenu zostało przerwane.</entry>
+    <entry lang="pl" key="FORMAT_STAGE_ERROR">Nie udało się utworzyć wolumenu.</entry>
+    <entry lang="pl" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizowanie tworzenia wolumenu: podłączanie tymczasowego wolumenu.</entry>
+    <entry lang="pl" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizowanie tworzenia wolumenu: przygotowywanie tymczasowego urządzenia.</entry>
+    <entry lang="pl" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizowanie tworzenia wolumenu: tworzenie systemu plików za pomocą {0}.</entry>
+    <entry lang="pl" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizowanie tworzenia wolumenu: odłączanie wolumenu tymczasowego.</entry>
+    <entry lang="pl" key="MACOSX_APFS_SYNTHESIZED_DEVICE">Wybrane urządzenie „{0}” jest kontenerem lub wolumenem syntezowanym APFS i nie można go używać jako hosta surowego wolumenu VeraCrypt.\n\nZamiast tego wybierz fizyczną partycję magazynu APFS{1}.</entry>
+    <entry lang="pl" key="MACOSX_DEVICE_SYSTEM_PARTITION">Wybrane urządzenie „{0}” jest partycją systemową/obsługową systemu macOS i nie może być używane jako host wolumenu VeraCrypt.</entry>
+    <entry lang="pl" key="MACOSX_APFS_SYSTEM_STORE">Wybrany fizyczny magazyn APFS „{0}” zawiera aktualnie zamontowany wolumen systemu macOS i nie może być używany jako host wolumenu VeraCrypt.</entry>
+    <entry lang="pl" key="MACOSX_DEVICE_NOT_WRITABLE">System macOS zgłasza wybrane urządzenie „{0}” jako tylko do odczytu. Wybierz zapisywalną partycję fizyczną lub dysk.</entry>
+    <entry lang="pl" key="MACOSX_APFS_EROFS_HINT">System macOS zgłosił wybrane urządzenie jako tylko do odczytu. Jeśli jest to dysk APFS, upewnij się, że wybrano fizyczną partycję magazynu APFS, a nie wolumen syntezowany przez APFS. Użyj narzędzia dyskowego lub polecenia „diskutil list”, aby zidentyfikować partycję fizyczną, a następnie spróbuj ponownie.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.pt-br.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="pt-br" name="Português-Brasil" en-name="Portuguese (Brazil)" version="0.2.0" translators="Thiago C. L. Mendes, Lecidio S. Alencar , Lucas C. Ferreira, Daniel Dias Rodrigues, Transifex contributors" />
     <font lang="pt-br" class="normal" size="11" face="padrão" />
     <font lang="pt-br" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="pt-br" key="IDT_NEW_PASSWORD">Senha:</entry>
     <entry lang="pt-br" key="IDT_PARALLELIZATION_OPTIONS">Paralelização baseada em threads</entry>
     <entry lang="pt-br" key="IDT_PKCS11_LIB_PATH">Caminho da Biblioteca PKCS #11</entry>
-    <entry lang="pt-br" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="pt-br" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="pt-br" key="IDT_KDF">KDF:</entry>
+    <entry lang="pt-br" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="pt-br" key="IDT_PW_CACHE_OPTIONS">Cache de senhas</entry>
     <entry lang="pt-br" key="IDT_SECURITY_OPTIONS">Opções de Segurança</entry>
     <entry lang="pt-br" key="IDT_EMV_OPTIONS">Opções de EMV</entry>
@@ -813,7 +813,7 @@
     <entry lang="pt-br" key="SECONDARY_KEY_SIZE_LRW">Tamanho da chave de ajuste (Modo LRW)</entry>
     <entry lang="pt-br" key="BITS">bits</entry>
     <entry lang="pt-br" key="BLOCK_SIZE">Tamanho do Bloco</entry>
-    <entry lang="pt-br" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="pt-br" key="KDF">KDF</entry>
     <entry lang="pt-br" key="PKCS5_ITERATIONS">Contagem de Iterações do PKCS-5</entry>
     <entry lang="pt-br" key="VOLUME_CREATE_DATE">Disco Criado</entry>
     <entry lang="pt-br" key="VOLUME_HEADER_DATE">Última modificação do cabeçalho</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="pt-br" key="INSECURE_MODE">[MODO INSEGURO]</entry>
     <entry lang="pt-br" key="IDC_DISABLE_SCREEN_PROTECTION">Desativar proteção contra capturas de tela e gravação de tela</entry>
     <entry lang="pt-br" key="DISABLE_SCREEN_PROTECTION_WARNING">AVISO: Desativar a proteção de tela reduz significativamente a segurança. Ative esta opção SOMENTE se você tiver uma necessidade específica de capturar a interface do VeraCrypt. Isso pode expor dados sensíveis a ferramentas de captura de tela e recursos de gravação, como o Windows 11 Recall.</entry>
+    <entry lang="pt-br" key="MEMORY_COST">Custo de Memória</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.ro.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="ro" name="Română" en-name="Romanian" version="2.0.0" translators="Barna Cosmin Marian" />
     <font lang="ro" class="normal" size="11" face="default" />
     <font lang="ro" class="bold" size="13" face="Arial" />
@@ -21,8 +21,8 @@
     <entry lang="ro" key="IDD_INSTL_DLG">Asistent instalare VeraCrypt</entry>
     <entry lang="ro" key="IDD_UNINSTALL">Dezinstalare VeraCrypt</entry>
     <entry lang="ro" key="IDHELP">&amp;Ajutor</entry>
-    <entry lang="ro" key="IDT_EXTRACT_DESTINATION">Selectați sau introduceți destinaţia unde să fie plasate fișierele extrase:</entry>
-    <entry lang="ro" key="IDT_INSTALL_DESTINATION">Selectați sau introduceți destinaţia unde doriți să fie instalate fișierele programului VeraCrypt. Dacă folderul specificat nu există, va fi creat automat.</entry>
+    <entry lang="ro" key="IDT_EXTRACT_DESTINATION">Selectați sau introduceți destinația unde să fie plasate fișierele extrase:</entry>
+    <entry lang="ro" key="IDT_INSTALL_DESTINATION">Selectați sau introduceți destinația unde doriți să fie instalate fișierele programului VeraCrypt. Dacă folderul specificat nu există, va fi creat automat.</entry>
     <entry lang="ro" key="IDT_UNINSTALL_DIR">Apăsați pe «Dezinstalare» pentru a elimina VeraCrypt din acest sistem.</entry>
     <entry lang="ro" key="IDC_ABORT_BUTTON">Oprire</entry>
     <entry lang="ro" key="IDC_BENCHMARK">&amp;Evaluare</entry>
@@ -42,8 +42,8 @@
     <entry lang="ro" key="IDC_HIDVOL_WIZ_MODE_FULL">Mod normal</entry>
     <entry lang="ro" key="IDC_KB">&amp;KiB</entry>
     <entry lang="ro" key="IDC_KEYFILES_ENABLE">Folo&amp;sire fișiere-cheie</entry>
-    <entry lang="ro" key="IDC_KEYFILES_TRY_EMPTY_PASSWORD">Încercaţi mai întâi montarea fără parolă</entry>
-    <entry lang="ro" key="IDC_KEYFILES_RANDOM_SIZE">Mărime aleatoare ( 64 &lt;-&gt; 1048576 )</entry>
+    <entry lang="ro" key="IDC_KEYFILES_TRY_EMPTY_PASSWORD">Încercați mai întâi montarea fără parolă</entry>
+    <entry lang="ro" key="IDC_KEYFILES_RANDOM_SIZE">Mărime aleatorie ( 64 &lt;-&gt; 1048576 )</entry>
     <entry lang="ro" key="IDC_KEY_FILES">Fișiere-&amp;cheie</entry>
     <entry lang="ro" key="IDC_LINK_HASH_INFO">Informații despre algoritmii de amestecare</entry>
     <entry lang="ro" key="IDC_LINK_MORE_INFO_ABOUT_CIPHER">Mai multe informații</entry>
@@ -72,9 +72,9 @@
     <entry lang="ro" key="IDC_WHOLE_SYS_DRIVE">Criptare tot discul</entry>
     <entry lang="ro" key="IDD_VOL_CREATION_WIZARD_DLG">Asistent creare volum VeraCrypt</entry>
     <entry lang="ro" key="IDT_CLUSTER">Cluster </entry>
-    <entry lang="ro" key="IDT_COLLECTING_RANDOM_DATA_NOTE">IMPORTANT: Mișcați cursorul cât mai aleator posibil în interiorul acestei ferestre. Cu cât îl mișcați mai mult, cu atât mai bine. Aceasta mărește considerabil puterea criptografică a cheilor de criptare. Apoi apăsați pe «Înainte» pentru a continua.</entry>
+    <entry lang="ro" key="IDT_COLLECTING_RANDOM_DATA_NOTE">IMPORTANT: Mișcați cursorul cât mai aleatoriu posibil în interiorul acestei ferestre. Cu cât îl mișcați mai mult, cu atât mai bine. Aceasta mărește considerabil puterea criptografică a cheilor de criptare. Apoi apăsați pe «Înainte» pentru a continua.</entry>
     <entry lang="ro" key="IDT_CONFIRM">&amp;Confirmare:</entry>
-    <entry lang="ro" key="IDT_DONE">Done</entry>
+    <entry lang="ro" key="IDT_DONE">Gata</entry>
     <entry lang="ro" key="IDT_DRIVE_LETTER">Literă unitate:</entry>
     <entry lang="ro" key="IDT_ENCRYPTION_ALGO">Algoritm criptare</entry>
     <entry lang="ro" key="IDT_FILESYSTEM">Fișiere sistem</entry>
@@ -85,19 +85,19 @@
     <entry lang="ro" key="IDT_LEFT">Rămas</entry>
     <entry lang="ro" key="IDT_MASTER_KEY">Cheie principală: </entry>
     <entry lang="ro" key="IDT_MULTI_BOOT">Selectați această opțiune dacă sunt două sau mai multe sisteme de operare instalate în acest computer.\n\nDe exemplu:\n- Windows XP și Windows XP\n- Windows XP și Windows Vista\n- Windows și Mac OS X\n- Windows și Linux\n- Windows, Linux și Mac OS X</entry>
-    <entry lang="ro" key="IDT_NON_SYS_DEVICE">Criptare partiție non-sistem pe un disc intern sau extern (ex. o unitate USB). Opțional, crează un volum ascuns.</entry>
+    <entry lang="ro" key="IDT_NON_SYS_DEVICE">Criptare partiție non-sistem pe un disc intern sau extern (ex. o unitate USB). Opțional, creează un volum ascuns.</entry>
     <entry lang="ro" key="IDT_PARTIAL_POOL_CONTENTS">Conținut sursă curent (parțial)</entry>
     <entry lang="ro" key="IDT_PASS">Salt</entry>
     <entry lang="ro" key="IDT_PASSWORD">Parola:</entry>
     <entry lang="ro" key="IDT_PIM">MIP volum:</entry>
     <entry lang="ro" key="IDT_OLD_PIM">MIP volum:</entry>
     <entry lang="ro" key="IDT_PROGRESS">Progres:</entry>
-    <entry lang="ro" key="IDT_RANDOM_POOL">Sursă aleatoare: </entry>
+    <entry lang="ro" key="IDT_RANDOM_POOL">Sursă aleatorie: </entry>
     <entry lang="ro" key="IDT_SINGLE_BOOT">Selectați această opțiune dacă există un singur sistem de operare instalat în calculator (chiar dacă are mai mulți utilizatori).</entry>
     <entry lang="ro" key="IDT_SPEED">Viteză</entry>
     <entry lang="ro" key="IDT_STATUS">Stare</entry>
-    <entry lang="ro" key="IDT_SYSENC_KEYS_GEN_INFO">Cheile, codul aleator și alte date au fost generate cu succes. Dacă doriți să generați chei noi, apăsați pe «Înapoi» și apoi pe «Înainte». Altfel, apăsați pe «Înainte» pentru a continua.</entry>
-    <entry lang="ro" key="IDT_SYS_DEVICE">Criptare disc/partiție unde este instalat Windows. Oricine va dori să aibă acces și să utilizeze sistemul și fișierele, va trebui să introducă parola corectă de fiecare dată înainte de pornirea sistemului Windows. Opțional, crează un sistem ascuns.</entry>
+    <entry lang="ro" key="IDT_SYSENC_KEYS_GEN_INFO">Cheile, codul aleatoriu și alte date au fost generate cu succes. Dacă doriți să generați chei noi, apăsați pe «Înapoi» și apoi pe «Înainte». Altfel, apăsați pe «Înainte» pentru a continua.</entry>
+    <entry lang="ro" key="IDT_SYS_DEVICE">Criptare disc/partiție unde este instalat Windows. Oricine va dori să aibă acces și să utilizeze sistemul și fișierele, va trebui să introducă parola corectă de fiecare dată înainte de pornirea sistemului Windows. Opțional, creează un sistem ascuns.</entry>
     <entry lang="ro" key="IDT_SYS_PARTITION">Selectați această opțiune pentru a cripta partiția unde este instalat sistemul de operare Windows în acest moment.</entry>
     <entry lang="ro" key="IDT_VOLUME_LABEL">Etichetă volum în Windows:</entry>
     <entry lang="ro" key="IDT_WIPE_MODE">Mod ștergere:</entry>
@@ -134,7 +134,7 @@
     <entry lang="ro" key="IDC_FAVORITE_OPEN_EXPLORER_WIN_ON_MOUNT">Deschidere fereastră &amp;Explorer pentru volumul selectat după ce este montat</entry>
     <entry lang="ro" key="IDC_FAVORITE_REMOVE">&amp;Eliminare</entry>
     <entry lang="ro" key="IDC_FAVORITE_USE_LABEL_IN_EXPLORER">Folosire etichetă favorită ca etichetă în Explorer</entry>
-    <entry lang="ro" key="IDC_FAV_VOL_OPTIONS_GLOBAL_SETTINGS_BOX">Setări globare</entry>
+    <entry lang="ro" key="IDC_FAV_VOL_OPTIONS_GLOBAL_SETTINGS_BOX">Setări globale</entry>
     <entry lang="ro" key="IDC_HK_UNMOUNT_BALLOON_TOOLTIP">Afișare mesaje de informare după demontarea efectuată cu combinații de taste</entry>
     <entry lang="ro" key="IDC_HK_UNMOUNT_PLAY_SOUND">Redare sunet de notificare după demontarea efectuată cu combinații de taste</entry>
     <entry lang="ro" key="IDC_HK_MOD_ALT">Alt</entry>
@@ -147,7 +147,7 @@
     <entry lang="ro" key="IDC_LIMIT_ENC_THREAD_POOL">Nu utiliza următorul număr de procesoare pentru criptare/decriptare:</entry>
     <entry lang="ro" key="IDC_MORE_INFO_ON_HW_ACCELERATION">Informatii suplimentare</entry>
     <entry lang="ro" key="IDC_MORE_INFO_ON_THREAD_BASED_PARALLELIZATION">Informatii suplimentare</entry>
-    <entry lang="ro" key="IDC_MORE_SETTINGS">Setări suplimentare</entry>
+    <entry lang="ro" key="IDC_MORE_SETTINGS">Alte setări...</entry>
     <entry lang="ro" key="IDC_MOUNTALL">&amp;Automontare toate</entry>
     <entry lang="ro" key="IDC_MOUNT_OPTIONS">Opți&amp;uni montare</entry>
     <entry lang="ro" key="IDC_MOUNT_READONLY">Montare volum ca doar-&amp;citire</entry>
@@ -157,10 +157,10 @@
     <entry lang="ro" key="IDC_PREF_BKG_TASK_ENABLE">Activat</entry>
     <entry lang="ro" key="IDC_PREF_CACHE_PASSWORDS">Păstrare parolă în memorie</entry>
     <entry lang="ro" key="IDC_PREF_UNMOUNT_INACTIVE">Autodemontare volum dacă nu s-au citit/scris date de pe el timp de</entry>
-    <entry lang="ro" key="IDC_PREF_UNMOUNT_LOGOFF">Deautentificare utilizator</entry>
+    <entry lang="ro" key="IDC_PREF_UNMOUNT_LOGOFF">Deconectare utilizator</entry>
     <entry lang="ro" key="IDC_PREF_UNMOUNT_SESSION_LOCKED">Blocare sesiune utilizator</entry>
     <entry lang="ro" key="IDC_PREF_UNMOUNT_POWERSAVING">Intrare în mod salvare energie</entry>
-    <entry lang="ro" key="IDC_PREF_UNMOUNT_SCREENSAVER">Pornire screen saver</entry>
+    <entry lang="ro" key="IDC_PREF_UNMOUNT_SCREENSAVER">Pornire economizor ecran</entry>
     <entry lang="ro" key="IDC_PREF_FORCE_AUTO_UNMOUNT">Forțare autodemontare chiar dacă volumul conține fișiere sau foldere deschise</entry>
     <entry lang="ro" key="IDC_PREF_LOGON_MOUNT_DEVICES">Montare volume VeraCrypt aflate pe discuri</entry>
     <entry lang="ro" key="IDC_PREF_LOGON_START">Pornire VeraCrypt în fundal</entry>
@@ -173,7 +173,7 @@
     <entry lang="ro" key="IDC_PREF_WIPE_CACHE_ON_EXIT">Eliminare parole păstrate la ieșire</entry>
     <entry lang="ro" key="IDC_PRESERVE_TIMESTAMPS">Păstrare dată modificare fișiere container</entry>
     <entry lang="ro" key="IDC_RESET_HOTKEYS">Resetare</entry>
-    <entry lang="ro" key="IDC_SELECT_DEVICE">Selectare &amp;partiţie</entry>
+    <entry lang="ro" key="IDC_SELECT_DEVICE">Selectare &amp;partiție</entry>
     <entry lang="ro" key="IDC_SELECT_FILE">Selectare fiși&amp;er</entry>
     <entry lang="ro" key="IDC_SELECT_PKCS11_MODULE">Selectare &amp;librărie</entry>
     <entry lang="ro" key="IDC_SHOW_PASSWORD_CHPWD_NEW">Afișare parolă</entry>
@@ -192,7 +192,7 @@
     <entry lang="ro" key="IDD_PASSWORDCHANGE_DLG">Schimbare parolă sau fișiere-cheie</entry>
     <entry lang="ro" key="IDD_PASSWORD_DLG">Introduceți parola volumului VeraCrypt</entry>
     <entry lang="ro" key="IDD_PERFORMANCE_SETTINGS">VeraCrypt - Opțiuni performanță și driver</entry>
-    <entry lang="ro" key="IDD_PREFERENCES_DLG">VeraCrypt - Preferițe</entry>
+    <entry lang="ro" key="IDD_PREFERENCES_DLG">VeraCrypt - Preferințe</entry>
     <entry lang="ro" key="IDD_SYSENC_SETTINGS">VeraCrypt - Setări criptare sistem</entry>
     <entry lang="ro" key="IDD_TOKEN_PREFERENCES">VeraCrypt - Preferințe dispozitiv de securitate</entry>
     <entry lang="ro" key="IDD_TRAVELER_DLG">Setare disc portabil VeraCrypt</entry>
@@ -216,12 +216,12 @@
     <entry lang="ro" key="IDM_CREATE_VOLUME">Creare volum nou</entry>
     <entry lang="ro" key="IDM_DECRYPT_NONSYS_VOL">Decriptare permanentă...</entry>
     <entry lang="ro" key="IDM_DEFAULT_KEYFILES">Fișiere-cheie implicite</entry>
-    <entry lang="ro" key="IDM_DEFAULT_MOUNT_PARAMETERS">Parametri montare impliciţi...</entry>
+    <entry lang="ro" key="IDM_DEFAULT_MOUNT_PARAMETERS">Parametri montare impliciți...</entry>
     <entry lang="ro" key="IDM_DONATE">Donație</entry>
     <entry lang="ro" key="IDM_ENCRYPT_SYSTEM_DEVICE">Criptare disc/partiție sistem</entry>
-    <entry lang="ro" key="IDM_FAQ">Întrebări puse frevent</entry>
+    <entry lang="ro" key="IDM_FAQ">Întrebări frecvente</entry>
     <entry lang="ro" key="IDM_HELP">Ghid de utilizare</entry>
-    <entry lang="ro" key="IDM_HOMEPAGE">Pagina &amp;Web</entry>
+    <entry lang="ro" key="IDM_HOMEPAGE">Pagina &amp;web</entry>
     <entry lang="ro" key="IDM_HOTKEY_SETTINGS">Combinații taste</entry>
     <entry lang="ro" key="IDM_KEYFILE_GENERATOR">Generator fișiere-cheie</entry>
     <entry lang="ro" key="IDM_LANGUAGE">Limba</entry>
@@ -234,7 +234,7 @@
     <entry lang="ro" key="IDM_MOUNT_VOLUME_OPTIONS">Montare volum cu opțiuni</entry>
     <entry lang="ro" key="IDM_NEWS">Știri</entry>
     <entry lang="ro" key="IDM_ONLINE_HELP">Ajutor online</entry>
-    <entry lang="ro" key="IDM_ONLINE_TUTORIAL">Turorial începători</entry>
+    <entry lang="ro" key="IDM_ONLINE_TUTORIAL">Tutorial începători</entry>
     <entry lang="ro" key="IDM_ORGANIZE_FAVORITES">Organizare volume favorite</entry>
     <entry lang="ro" key="IDM_ORGANIZE_SYSTEM_FAVORITES">Organizare volume sistem favorite</entry>
     <entry lang="ro" key="IDM_PERFORMANCE_SETTINGS">Performanță/Configurare driver</entry>
@@ -274,7 +274,7 @@
     <entry lang="ro" key="IDT_BOOT_LOADER_SCREEN_OPTIONS">Opțiuni ecran pornire sistem</entry>
     <entry lang="ro" key="IDT_CONFIRM_PASSWORD">Confirmare parolă:</entry>
     <entry lang="ro" key="IDT_CURRENT">Curent</entry>
-    <entry lang="ro" key="IDT_CUSTOM_BOOT_LOADER_MESSAGE">Afișează acest mesaj în ecranul de autentificare la pornire sistem (maxim 24 charactere):</entry>
+    <entry lang="ro" key="IDT_CUSTOM_BOOT_LOADER_MESSAGE">Afișează acest mesaj în ecranul de autentificare la pornire sistem (maxim 24 caractere):</entry>
     <entry lang="ro" key="IDT_DEFAULT_MOUNT_OPTIONS">Opțiuni montare implicite</entry>
     <entry lang="ro" key="IDT_UNMOUNT_ACTION">Opțiuni combinații de taste</entry>
     <entry lang="ro" key="IDT_DRIVER_OPTIONS">Configurare driver</entry>
@@ -291,8 +291,8 @@
     <entry lang="ro" key="IDT_NEW_PASSWORD">Parola:</entry>
     <entry lang="ro" key="IDT_PARALLELIZATION_OPTIONS">Paralelizare bazată pe fire de execuție (Hyper-Threading)</entry>
     <entry lang="ro" key="IDT_PKCS11_LIB_PATH">Cale librărie PKCS #11</entry>
-    <entry lang="ro" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="ro" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="ro" key="IDT_KDF">KDF:</entry>
+    <entry lang="ro" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="ro" key="IDT_PW_CACHE_OPTIONS">Păstrare parolă</entry>
     <entry lang="ro" key="IDT_SECURITY_OPTIONS">Opțiuni securitate</entry>
     <entry lang="ro" key="IDT_EMV_OPTIONS">Opțiuni EMV</entry>
@@ -310,9 +310,9 @@
     <entry lang="ro" key="IDC_ENCRYPT">Criptar&amp;e</entry>
     <entry lang="ro" key="IDC_EXPORT">&amp;Exportare</entry>
     <entry lang="ro" key="IDC_GENERATE_AND_SAVE_KEYFILE">Generare și salvare fișier-cheie</entry>
-    <entry lang="ro" key="IDC_GENERATE_KEYFILE">&amp;Generare fișier-cheie aleator</entry>
+    <entry lang="ro" key="IDC_GENERATE_KEYFILE">&amp;Generare fișier-cheie aleatoriu</entry>
     <entry lang="ro" key="IDC_GET_LANG_PACKS">Descărcare pachet lingvistic</entry>
-    <entry lang="ro" key="IDC_HW_AES_LABEL_LINK">Accelerere hardware AES:</entry>
+    <entry lang="ro" key="IDC_HW_AES_LABEL_LINK">Accelerare hardware AES:</entry>
     <entry lang="ro" key="IDC_IMPORT_KEYFILE">&amp;Importare fișier-cheie în dispozitivul de securitate</entry>
     <entry lang="ro" key="IDC_KEYADD">Adăugare &amp;fișiere</entry>
     <entry lang="ro" key="IDC_KEYFILES_ENABLE_HIDVOL_PROT">&amp;Utilizare fișiere-cheie</entry>
@@ -341,7 +341,7 @@
     <entry lang="ro" key="IDD_LANGUAGE">VeraCrypt - Limba</entry>
     <entry lang="ro" key="IDD_MOUNT_OPTIONS">VeraCrypt - Opțiuni montare</entry>
     <entry lang="ro" key="IDD_NEW_TOKEN_KEYFILE">Proprietăți fișier-cheie dispozitiv securitate</entry>
-    <entry lang="ro" key="IDD_RANDOM_POOL_ENRICHMENT">VeraCrypt - Îmbogățire sursă aleatoare</entry>
+    <entry lang="ro" key="IDD_RANDOM_POOL_ENRICHMENT">VeraCrypt - Îmbogățire sursă aleatorie</entry>
     <entry lang="ro" key="IDD_RAWDEVICES_DLG">Selectați o partiție sau un disc</entry>
     <entry lang="ro" key="IDD_STATIC_MODELESS_WAIT_DLG">VeraCrypt</entry>
     <entry lang="ro" key="IDD_TOKEN_KEYFILES">Fișiere-cheie dispozitiv securitate</entry>
@@ -353,7 +353,7 @@
     <entry lang="ro" key="IDT_HIDDEN_PROT_PASSWD">P&amp;arolă volum ascuns:\n(implicit e cea memorată)</entry>
     <entry lang="ro" key="IDT_HIDDEN_VOL_PROTECTION">Protecție volum ascuns</entry>
     <entry lang="ro" key="IDT_KEY">Mărime cheie:</entry>
-    <entry lang="ro" key="IDT_KEYFILE_GENERATOR_NOTE">IMPORTANT: Mișcați cursorul cât mai aleator posibil în această fereastră. Cu cât îl mișcați mai mult, cu atât mai bine. Această mărește semnificativ puterea criptografică a fișierului cheie.</entry>
+    <entry lang="ro" key="IDT_KEYFILE_GENERATOR_NOTE">IMPORTANT: Mișcați cursorul cât mai aleatoriu posibil în această fereastră. Cu cât îl mișcați mai mult, cu atât mai bine. Această mărește semnificativ puterea criptografică a fișierului cheie.</entry>
     <entry lang="ro" key="IDT_KEYFILE_WARNING">ATENȚIONARE:\nDacă pierdeți un fișier-cheie sau orice bit din primii 1024 kilobaiți este modificat, va fi imposibil de montat volumul care utilizează acel fișier-cheie!</entry>
     <entry lang="ro" key="IDT_KEY_UNIT">biți</entry>
     <entry lang="ro" key="IDT_NUMBER_KEYFILES">Număr fișiere-cheie:</entry>
@@ -364,7 +364,7 @@
     <entry lang="ro" key="IDT_PLAINTEXT_SIZE_UNIT">biți</entry>
     <entry lang="ro" key="IDT_POOL_CONTENTS">Conținut curent sursă</entry>
     <entry lang="ro" key="IDT_PRF">Amestecare PRF:</entry>
-    <entry lang="ro" key="IDT_RANDOM_POOL_ENRICHMENT_NOTE">IMPORTANT: Mișcați cursorul cât mai aleator posibil în această fereastră. Cu cât îl mișcați mai mult, cu atât mai bine. Aceasta mărește semnificativ securitatea. Când ați terminat, apăsați pe «Continuare».</entry>
+    <entry lang="ro" key="IDT_RANDOM_POOL_ENRICHMENT_NOTE">IMPORTANT: Mișcați cursorul cât mai aleatoriu posibil în această fereastră. Cu cât îl mișcați mai mult, cu atât mai bine. Aceasta mărește semnificativ securitatea. Când ați terminat, apăsați pe «Continuare».</entry>
     <entry lang="ro" key="IDT_SECONDARY_KEY">Cheie secundară (hexazecimal)</entry>
     <entry lang="ro" key="IDT_SECURITY_TOKEN">Dispozitiv securitate:</entry>
     <entry lang="ro" key="IDT_SORT_METHOD">Metodă sortare:</entry>
@@ -396,7 +396,7 @@
     <entry lang="ro" key="AES_HELP">FIPS-cifru aprobat (Rijndael, publicat în 1998) care poate fi folosit de departamentele și agențiile guvernamentale ale SUA pentru a proteja informațiile clasificate până la nivelul Top Secret. Cheie 256-biți, bloc 128-biți, 14 runde (AES-256). Modul de operare este XTS.</entry>
     <entry lang="ro" key="ALREADY_MOUNTED">Volumul este deja montat.</entry>
     <entry lang="ro" key="ERR_SELF_TESTS_FAILED">ATENȚIE: Cel puțin un algoritm de criptare sau amestecare a eșuat la testul automat intern!\n\nInstalarea VeraCrypt este coruptă.</entry>
-    <entry lang="ro" key="ERR_NOT_ENOUGH_RANDOM_DATA">ATENȚIE: Nu sunt suficiente date în sursa generatorului de numere aleatoare pentru a oferi cantitatea solicitată de date aleatoare.\n\nNu ar trebui să continuați. Selectați „Raportare eroare” din meniul „Ajutor” și raportați această eroare.</entry>
+    <entry lang="ro" key="ERR_NOT_ENOUGH_RANDOM_DATA">ATENȚIE: Nu sunt suficiente date în sursa generatorului de numere aleatorii pentru a oferi cantitatea solicitată de date aleatorii.\n\nNu ar trebui să continuați. Selectați „Raportare eroare” din meniul „Ajutor” și raportați această eroare.</entry>
     <entry lang="ro" key="ERR_HARDWARE_ERROR">Discul este defect (există un defect fizic pe ea) sau cablul este defect sau memoria nu este stabilă.\n\nȚineți cont că aceasta este o problemă cu hardware-ul, nu cu VeraCrypt. Deci, NU raportați aceasta ca o eroare/problemă în VeraCrypt și NU solicitați ajutor privind aceasta în forumul VeraCrypt. Contactați echipa de suport a furnizorului hardware pentru asistență. Vă mulțumim.\n\nNotă: Dacă eroarea apare în mod repetat în același loc, este foarte posibil să fie cauzată de un bloc defect pe disc, care s-ar putea corecta cu ajutorul unor programe specializate (țineți cont că, în multe cazuri, comanda „chkdsk  /r” nu le poate corecta deoarece funcționează doar la nivelul sistemului de fișiere; în unele cazuri, funcția  „chkdsk” nici măcar nu le detectează).</entry>
     <entry lang="ro" key="DEVICE_NOT_READY_ERROR">Dacă accesați un disc de pe un suport portabil, asigurați-vă că acesta este introdus în calculator. Discul/mediul poate fi defect (ar putea exista un defect fizic pe el) sau un cablu ar putea fi defect/deconectat.</entry>
     <entry lang="ro" key="WHOLE_DRIVE_ENCRYPTION_PREVENTED_BY_DRIVERS">Sistemul pare să utilizeze drivere modificate de cipset care conțin o eroare ce împiedică criptarea întregii unități sistem.\n\nÎncercați să actualizați sau să dezinstalați orice drivere de cipset modificate (non-Microsoft) înainte de a continua. Dacă aceasta nu ajută, încercați să criptați doar partiția sistem.</entry>
@@ -423,7 +423,7 @@
     <entry lang="ro" key="DEVICE_FREE_PB">Mărimea lui %s este de %.2f PiB</entry>
     <entry lang="ro" key="DEVICE_IN_USE_FORMAT">AVERTIZARE: Discul/partiția este accesat(ă) de către sistemul de operare sau de către aplicații. Formatarea unității/partiției poate determina coruperea datelor și instabilitatea sistemului.\n\nContinuați?</entry>
     <entry lang="ro" key="DEVICE_IN_USE_INPLACE_ENC">Avertizare: Partiția este accesată de către sistemul de operare sau de către aplicații. Ar trebui să închideți orice aplicație care ar putea accesa partiția (inclusiv programele antivirus).\n\nContinuați?</entry>
-    <entry lang="ro" key="FORMAT_CANT_UNMOUNT_FILESYS">Eroare: Discul/partiția conține un sistem de fișiere care nu a putut fi demontat. Sistemul de fișiere ar putea fi utilizat de către sistemul de operare. Formatarea discului/partiției foarte probabil va putea cauza coruperea datelor și instabilitatea sistemului.\n\nPentru a rezolva această situație, vă recomandăm să ștergeți mai întâi partiția și apoi să o recreați fără formatare. Pentru aceasta, urmați acești pași:\n1) Apăsați cu clic dreapta pe pictograma «Computer» (sau «My Computer») din meniul «Start» și selectați «Manage». Ar trebui să apară fereastra «Computer Management».\n2) În fereastra «Computer Management», selectați «Storage» > «Disk Management».\n3) Apăsați cu clic dreapta pe partiția pe care doriți să o criptați și selectați fie «Delete Partition», fie «Delete Volume», sau «Delete Logical Drive».\n4) Apăsați pe «Yes». Dacă sistemul Windows vă solicită să reporniţi calculatorul, confirmați. Apoi repetați pasul 1 și 2 și continuați de la pasul 5.\n5) Apăsați cu clic dreapta pe zona cu spațiul nealocat/liber și selectați fie «New Partition», fie «New Simple Volume», sau «New Logical Drive».\n6) Ar trebui să apară fereastra «New Partition Wizard» sau «New Simple Volume Wizard»; urmați instrucțiunile afișate. Pe pagina asistentului intitulată «Format Partition», selectați fie «Do not format this partition» fie «Do not format this volume». În același asistent, apăsați pe «Next» și apoi pe «Finish».\n7) De acum calea unității selectate în VeraCrypt s-ar putea să fie greșită. De aceea, ieșiți din «Asistentul de creare volume VeraCrypt» (dacă încă este activ) și apoi porniți-l din nou.\n8) Încercați să criptați discul/partiția din nou.\n\nDacă VeraCrypt eșuează în mod repetat să cripteze discul/partiția, ați putea, în schimb, lua în considerare crearea unui container de tip fișier.</entry>
+    <entry lang="ro" key="FORMAT_CANT_UNMOUNT_FILESYS">Eroare: Discul/partiția conține un sistem de fișiere care nu a putut fi demontat. Sistemul de fișiere ar putea fi utilizat de către sistemul de operare. Formatarea discului/partiției foarte probabil va putea cauza coruperea datelor și instabilitatea sistemului.\n\nPentru a rezolva această situație, vă recomandăm să ștergeți mai întâi partiția și apoi să o recreați fără formatare. Pentru aceasta, urmați acești pași:\n1) Apăsați cu clic dreapta pe pictograma «Computer» (sau «My Computer») din meniul «Start» și selectați «Manage». Ar trebui să apară fereastra «Computer Management».\n2) În fereastra «Computer Management», selectați «Storage» > «Disk Management».\n3) Apăsați cu clic dreapta pe partiția pe care doriți să o criptați și selectați fie «Delete Partition», fie «Delete Volume», sau «Delete Logical Drive».\n4) Apăsați pe «Yes». Dacă sistemul Windows vă solicită să reporniți calculatorul, confirmați. Apoi repetați pasul 1 și 2 și continuați de la pasul 5.\n5) Apăsați cu clic dreapta pe zona cu spațiul nealocat/liber și selectați fie «New Partition», fie «New Simple Volume», sau «New Logical Drive».\n6) Ar trebui să apară fereastra «New Partition Wizard» sau «New Simple Volume Wizard»; urmați instrucțiunile afișate. Pe pagina asistentului intitulată «Format Partition», selectați fie «Do not format this partition» fie «Do not format this volume». În același asistent, apăsați pe «Next» și apoi pe «Finish».\n7) De acum calea unității selectate în VeraCrypt s-ar putea să fie greșită. De aceea, ieșiți din «Asistentul de creare volume VeraCrypt» (dacă încă este activ) și apoi porniți-l din nou.\n8) Încercați să criptați discul/partiția din nou.\n\nDacă VeraCrypt eșuează în mod repetat să cripteze discul/partiția, ați putea, în schimb, lua în considerare crearea unui container de tip fișier.</entry>
     <entry lang="ro" key="INPLACE_ENC_CANT_LOCK_OR_UNMOUNT_FILESYS">Eroare: fișierul sistem nu poate fi blocat și/sau demontat. S-ar putea să fie accesat de către sistemul de operare sau de către aplicații (de exemplu, programe antivirus). Criptarea partiției ar putea cauza coruperea datelor și instabilitatea sistemului.\n\nÎnchideți orice aplicație care ar putea utiliza sistemul de fișiere (inclusiv programe antivirus) și încercați din nou. Dacă asta nu ajută, urmați pașii de mai jos.</entry>
     <entry lang="ro" key="DEVICE_IN_USE_INFO">AVERTIZARE: Unele partiții/discuri montate sunt deja accesate!\n\nIgnorând acest lucru poate determina rezultate nedorite inclusiv instabilitatea sistemului.\n\nVă recomandăm cu insistență să închideți orice aplicație care le-ar putea accesa.</entry>
     <entry lang="ro" key="DEVICE_PARTITIONS_ERR">Discul selectat conține partiții.\n\nFormatarea discului poate cauza instabilitatea sistemului și/sau coruperea datelor. Selectați fie o partiție de pe disc, fie ștergeți toate partițiile de pe disc pentru a permite ca VeraCrypt să-l formateze în siguranță.</entry>
@@ -438,7 +438,7 @@
     <entry lang="ro" key="RAW_DEV_NOT_SUPPORTED_FOR_INPLACE_ENC">VeraCrypt poate cripta din mers doar o partiție, un volum dinamic sau un disc sistem întreg.\n\nDacă doriți să creați un volum criptat VeraCrypt pe discul non-sistem selectat, alegeți opțiunea „Creare volum criptat și formatare”  (în loc de opțiunea „Criptare partiție din mers”).</entry>
     <entry lang="ro" key="INPLACE_ENC_INVALID_PATH">Eroare: VeraCrypt poate cripta din mers doar o partiție, un volum dinamic sau un disc sistem întreg. Verificați dacă este validă calea specificată.</entry>
     <entry lang="ro" key="CANNOT_RESIZE_FILESYS">Eroare: nu se poare reduce sistemul de fișiere (sistemul de fișiere trebuie redus pentru a face loc pentru antetul volumului și a celui de rezervă).\n\nPosibile cauze și soluții:\n\n- Nu există suficient spațiu liber pe volum. Asigurați-vă că nici o altă aplicație nu scrie în sistemul de fișiere.\n\n- Sistem de fișiere corupt. Verificați-l și reparați eventualele erori (apăsați cu clic dreapta pe litera unității respective în lista din „Computer”, apoi selectați „Properties” > „Tools” > „Check Now”, asigurați-vă că opțiunea „Automatically fix file system errors” este selectată și apoi apăsați pe „Start”).\n\nDacă operațiile de mai sus nu ajută, urmați pașii de mai jos.</entry>
-    <entry lang="ro" key="NOT_ENOUGH_FREE_FILESYS_SPACE_FOR_SHRINK">Eroare: nu există suficient spațiu liber pe volum astfel încât sistemul de fișiere nu poate fi redus (sistemul de fișiere trebuie redus pentru a face loc pentru antetul volumului și a celui de rezervă).\n\nȘtergeți orice fișier inutil și goliți „Coșul de gunoi” astfel încât să eliberați minim 256 KiB de spațiu și apoi încercați din nou. Țineți cont că datorită un probleme ce țin de Windows, spațiul liber raportat de către Windows Explorer poate fi incorect până după repornirea sistemului. Dacă repornirea sistemuluinu ajută, sistemul de fișiere poate fi corupt. Verificați și reparați eventualele erori (apăsați cu clic dreapta pe litera unității respective în lista din „Computer”, apoi selectați „Properties” > „Tools” > „Check Now”, asigurați-vă că opțiunea „Automatically fix file system errors” este selectată și apoi apăsați pe „Start”).\n\nDacă operațiile de mai sus nu ajută, urmați pașii de mai jos.</entry>
+    <entry lang="ro" key="NOT_ENOUGH_FREE_FILESYS_SPACE_FOR_SHRINK">Eroare: nu există suficient spațiu liber pe volum astfel încât sistemul de fișiere nu poate fi redus (sistemul de fișiere trebuie redus pentru a face loc pentru antetul volumului și a celui de rezervă).\n\nȘtergeți orice fișier inutil și goliți „Coșul de gunoi” astfel încât să eliberați minim 256 KiB de spațiu și apoi încercați din nou. Țineți cont că datorită un probleme ce țin de Windows, spațiul liber raportat de către Windows Explorer poate fi incorect până după repornirea sistemului. Dacă repornirea sistemului nu ajută, sistemul de fișiere poate fi corupt. Verificați și reparați eventualele erori (apăsați cu clic dreapta pe litera unității respective în lista din „Computer”, apoi selectați „Properties” > „Tools” > „Check Now”, asigurați-vă că opțiunea „Automatically fix file system errors” este selectată și apoi apăsați pe „Start”).\n\nDacă operațiile de mai sus nu ajută, urmați pașii de mai jos.</entry>
     <entry lang="ro" key="DISK_FREE_BYTES">Spațiul liber pe discul %s este de %.2f baiți</entry>
     <entry lang="ro" key="DISK_FREE_KB">Spațiul liber pe discul %s este de %.2f KiB</entry>
     <entry lang="ro" key="DISK_FREE_MB">Spațiul liber pe discul %s este de %.2f MiB</entry>
@@ -447,7 +447,7 @@
     <entry lang="ro" key="DISK_FREE_PB">Spațiul liber pe discul %s este de %.2f PiB</entry>
     <entry lang="ro" key="DRIVELETTERS">Nu s-au putut prelua literele de unități disponibile.</entry>
     <entry lang="ro" key="DRIVER_NOT_FOUND">Eroare: driverul VeraCrypt nu există.\n\nCopiați fișierele „veracrypt.sys” și „veracrypt-x64.sys” în folderul unde se află aplicația VeraCrypt (VeraCrypt.exe).</entry>
-    <entry lang="ro" key="DRIVER_VERSION">Eroare: în acest moment rulează o versiune incompatibilă a driverului VeraCrypt.\n\nDacă încercați să executați VeraCrypt în mod portabil (de ex. fără să-l instalați) și o versiune diferită VeraCrypt este deja instalată, trebuie mai întâi să o dezinstalați (sau să o actualizați folosind programul de instalare al VeraCrypt). Pentru a-l dezinstala, executați pașii următori: în Windows Vista sau ulterior, selectați „Start Menu” > „Computer” > „Uninstall or change a program” > „VeraCrypt” > „Uninstall”; în Windows XP, selectați „Start Menu” > „Settings” > „Control Panel” > „Add Or Remove Programs” > „VeraCrypt” > „Remove”.\n\nSimilar, dacă încercați să rulați VeraCrypt în mod portabil (de ex. fără să-l instalați) și o versiune diferită VeraCrypt este deja executată în mod portabil, trebuie să reporniţi mai întâi sistemul și apoi să executați numai această versiune nouă.</entry>
+    <entry lang="ro" key="DRIVER_VERSION">Eroare: în acest moment rulează o versiune incompatibilă a driverului VeraCrypt.\n\nDacă încercați să executați VeraCrypt în mod portabil (de ex. fără să-l instalați) și o versiune diferită VeraCrypt este deja instalată, trebuie mai întâi să o dezinstalați (sau să o actualizați folosind programul de instalare al VeraCrypt). Pentru a-l dezinstala, executați pașii următori: în Windows Vista sau ulterior, selectați „Start Menu” > „Computer” > „Uninstall or change a program” > „VeraCrypt” > „Uninstall”; în Windows XP, selectați „Start Menu” > „Settings” > „Control Panel” > „Add Or Remove Programs” > „VeraCrypt” > „Remove”.\n\nSimilar, dacă încercați să rulați VeraCrypt în mod portabil (de ex. fără să-l instalați) și o versiune diferită VeraCrypt este deja executată în mod portabil, trebuie să reporniți mai întâi sistemul și apoi să executați numai această versiune nouă.</entry>
     <entry lang="ro" key="ERR_CIPHER_INIT_FAILURE">Eroare: eșuare inițializare cifru.</entry>
     <entry lang="ro" key="ERR_CIPHER_INIT_WEAK_KEY">Eroare: a fost detectată o cheie slabă sau potențial slabă. Cheia va fi eliminată. Mai încercați.</entry>
     <entry lang="ro" key="EXCEPTION_REPORT">A apărut o eroare critică și VeraCrypt trebuie închis. Dacă aceasta este determinată de o eroare din VeraCrypt, am dori să o reparăm. Pentru a ne ajuta, ne puteți trimite raportul de erori generat automat conținând următoarele elemente:\n\n- Versiunea programului\n- Versiunea sistemului de operare\n- Tipul de procesor\n- Numele componentei VeraCrypt\n- Cheia de verificare a fișierului executabil VeraCrypt\n- Numele simbolic al ferestrei de dialog\n- Categoria erorii\n- Adresa erorii\n- Apelarea stivei VeraCrypt\n\nDacă selectați «Da», următorul URL (care conține întregul raport de erori) va fi deschis în navigatorul web implicit.\n\n%hs\n\nDoriți să ne trimiteți raportul de erori de mai sus?</entry>
@@ -472,7 +472,7 @@
     <entry lang="ro" key="EXT_PARTITION">Creați o partiție logică pentru această partiție extinsă și apoi încercați din nou.</entry>
     <entry lang="ro" key="FILE_HELP">Un volum VeraCrypt poate exista într-un fișier (denumit container VeraCrypt), care poate fi stocat pe hard disc, pe o unitate USB portabilă etc. Un container VeraCrypt este ca orice fișier obișnuit (poate fi, de exemplu, mutat sau șters ca orice alt fișier). Apăsați pe «Selectare fișier» pentru a alege nu nume de fișier pentru container și pentru a selecta locul unde doriți să fie creat acesta.\n\nATENȚIE: Dacă selectați un fișier existent, VeraCrypt NU îl va cripta; fișierul va fi șters și înlocuit cu noul container VeraCrypt creat. Veți putea cripta fișierele existente (mai târziu) mutându-le în containerul VeraCrypt pe care urmează să îl creați acum.</entry>
     <entry lang="ro" key="FILE_HELP_HIDDEN_HOST_VOL">Selectați locul unde va fi creat volumul exterior (volumul ascuns va fi creat ulterior în interiorul acestui volum).\n\nUn volum VeraCrypt poate exista într-un fișier (denumit container VeraCrypt), care poate fi stocat pe hard disc, pe o unitate USB portabilă etc. Un container VeraCrypt este ca orice fișier obișnuit (poate fi mutat sau șters ca orice alt fișier). Apăsați pe «Selectare fișier» pentru a alege nu nume de fișier pentru container și pentru a selecta locul unde doriți să fie creat acesta. Dacă selectați un fișier existent, VeraCrypt NU îl va cripta; fișierul va fi șters și înlocuit cu noul container VeraCrypt creat. Veți putea cripta fișierele existente (mai târziu) mutându-le în containerul VeraCrypt pe care urmează să îl creați acum.</entry>
-    <entry lang="ro" key="DEVICE_HELP">Volumele criptate VeraCrypt amplasate pe unități pot fi create pe partițiile de pe hard discuri, unități solid-state, stick-uri de memorie USB și pe orice alt mediu de stocare suportat. Partițiile pot fi de asemenea criptate din mers.\n\nÎn plus, dacă selectați un fișier existent, VeraCrypt NU îl va cripta; fișierul va fi șters și înlocuit cu noul container VeraCrypt creat. Veți putea cripta fișierele existente (mai târziu) mutându-le în containerul VeraCrypt pe care urmează să îl creați acum.  Volumele criptate VeraCrypt pot fi create pe unități care nu conțin partiții (inclusiv hard discuri și unități solid-state).\n\nNotă: Un disc care conține partiții poate fi criptat din mers (utilizând o singură cheie) doar dacă este discul unde este instalat Windows și de pe care pornește.</entry>
+    <entry lang="ro" key="DEVICE_HELP">Volumele criptate VeraCrypt amplasate pe unități pot fi create pe partițiile de pe hard discuri, unități solid-state, dispozitive de memorie USB și pe orice alt mediu de stocare suportat. Partițiile pot fi de asemenea criptate din mers.\n\nÎn plus, dacă selectați un fișier existent, VeraCrypt NU îl va cripta; fișierul va fi șters și înlocuit cu noul container VeraCrypt creat. Veți putea cripta fișierele existente (mai târziu) mutându-le în containerul VeraCrypt pe care urmează să îl creați acum.  Volumele criptate VeraCrypt pot fi create pe unități care nu conțin partiții (inclusiv hard discuri și unități solid-state).\n\nNotă: Un disc care conține partiții poate fi criptat din mers (utilizând o singură cheie) doar dacă este discul unde este instalat Windows și de pe care pornește.</entry>
     <entry lang="ro" key="DEVICE_HELP_NO_INPLACE">Un volum VeraCrypt la nivel de disc poate fi creat într-o partiție de pe hard disc, disc solid-state, memorie USB portabilă și alte dispozitive de stocare.\n\nATENȚIE: discul/partiția va fi formatat(ă) și toate datele curente stocate vor fi șterse.</entry>
     <entry lang="ro" key="DEVICE_HELP_HIDDEN_HOST_VOL">\nSelectați locul unde va fi creat volumul exterior (volumul ascuns va fi creat ulterior în interiorul acestui volum).\n\nVolumele exterioare pot fi create pe partițiile de pe hard disc, unități solid-state, memorii USB portabile și pe orice alt mediu de stocare suportat. Volumele exterioare pot fi create de asemenea pe unități care nu conțin partiții (inclusiv hard discuri și unități solid-state).\n\nATENȚIE: discul/partiția va fi formatat(ă) și toate datele curente stocate vor fi șterse.</entry>
     <entry lang="ro" key="FILE_HELP_HIDDEN_HOST_VOL_DIRECT">\nSelectați volumul VeraCrypt în care doriți să fie creat un volum ascuns.</entry>
@@ -486,7 +486,7 @@
     <entry lang="ro" key="FILESYS_PAGE_HELP_EXPLANATION_HIDVOL">Ținând cont că veți crea un volum exterior, ar trebui să alegeți «Nu». Dacă alegeți «Da», sistemul de fișiere implicit va fi NTFS, care nu este potrivit pentru volume exterioare de tip FAT/exFAT (adică, dimensiunea maximă posibilă a volumului ascuns va fi semnificativ mai mare dacă volumul este formatat ca FAT/exFAT). În mod normal, FAT este implicit atât pentru volumele normale cât și pentru cele ascunse (astfel încât volumele FAT nu sunt suspicioase). Totuși, dacă se indică intenția de a stoca fișiere mai mari de 4 GiB (ceea ce sistemul de fișiere FAT nu permite), atunci FAT nu este sistemul implicit.</entry>
     <entry lang="ro" key="FILESYS_PAGE_HELP_EXPLANATION_HIDVOL_CONFIRM">Sigur doriți să alegeți «Da»?</entry>
     <entry lang="ro" key="DEVICE_TRANSFORM_MODE_PAGE_TITLE">Mod creare volum</entry>
-    <entry lang="ro" key="DEVICE_TRANSFORM_MODE_PAGE_FORMAT_HELP">Aceasta este cea mai sigură cale de a crea un volum VeraCrypt găzduit pe o partiție sau un disc (criptarea din mers, care este cealaltă opțiune, este mai înceată deoarece conținutul fiecărui sector trebuie citit mai întâi, criptat și apoi rescris). Orice date curent stocate pe discul/partiția selectat(ă) vor fi pierdute (datele NU vor fi criptate; ele vor fi suprascrise cu date aleatoare). Dacă doriți să criptați datele existente pe o partiție, alegeți cealaltă opțiune.</entry>
+    <entry lang="ro" key="DEVICE_TRANSFORM_MODE_PAGE_FORMAT_HELP">Aceasta este cea mai sigură cale de a crea un volum VeraCrypt găzduit pe o partiție sau un disc (criptarea din mers, care este cealaltă opțiune, este mai înceată deoarece conținutul fiecărui sector trebuie citit mai întâi, criptat și apoi rescris). Orice date curent stocate pe discul/partiția selectat(ă) vor fi pierdute (datele NU vor fi criptate; ele vor fi suprascrise cu date aleatorii). Dacă doriți să criptați datele existente pe o partiție, alegeți cealaltă opțiune.</entry>
     <entry lang="ro" key="DEVICE_TRANSFORM_MODE_PAGE_INPLACE_HELP">Întreaga partiție selectată și toate datele stocate pe ea vor fi criptate din mers. Dacă partiția este goală, ar trebui să alegeți cealaltă opțiune (volumul va fi creat mult mai repede).</entry>
     <entry lang="ro" key="NOTE_BEGINNING">Notă: </entry>
     <entry lang="ro" key="RESUME">&amp;Reluare</entry>
@@ -507,13 +507,13 @@
     <entry lang="ro" key="SYSENC_HIDDEN_VOL_FORMAT_FINISHED_HELP">\n\nVolumul ascuns VeraCrypt a fost creat cu succes (sistemul de operare ascuns se va afla pe acest volum ascuns).\n\nApăsați pe «Înainte» pentru a continua.</entry>
     <entry lang="ro" key="NONSYS_INPLACE_ENC_FINISHED_TITLE">Volum complet criptat</entry>
     <entry lang="ro" key="NONSYS_INPLACE_DEC_FINISHED_TITLE">Volum complet decriptat</entry>
-    <entry lang="ro" key="NONSYS_INPLACE_ENC_FINISHED_INFO">IMPORTANT: PENTRU A MONTA ACEST VOLUM NOU VERACRYPT ȘI PENTRU A ACCESA DATELE STOCATE PE EL, APĂSAȚI PE „Automontare toate” ÎN FEREASTRA PRINCIPALĂ VERACRYPT. După ce veți introduce parola corectă (și/sau veți furniza fișierele-cheie corecte), volumul va fi montat cu litera unității selectate din lista afișată în fereastra principală VeraCrypt (și veți putea accesa datele criptate accesând litera unității selectate).\n\nMEMORAȚI SAU NOTAȚI-VĂ PAȘII DE MAI SUS. VA TREBUI SĂ-I URMAȚI DE FIECARE DATĂ CÂND VEȚI DORI SĂ MONTAȚI VOLUMUL ȘI SĂ ACCESAȚI DATELE STOCATE PE EL. Alternativ, în fereastra principală a VeraCrypt, apăsați pe „Selectare disc/partiție”, apoi selectați aceast disc/partiție și apăsați pe „Montare volum”.\n\nDiscul/partiția a fost criptat(ă) cu succes (acum conține un volum VeraCrypt complet criptat) și este gata de utilizare.</entry>
+    <entry lang="ro" key="NONSYS_INPLACE_ENC_FINISHED_INFO">IMPORTANT: PENTRU A MONTA ACEST VOLUM NOU VERACRYPT ȘI PENTRU A ACCESA DATELE STOCATE PE EL, APĂSAȚI PE „Automontare toate” ÎN FEREASTRA PRINCIPALĂ VERACRYPT. După ce veți introduce parola corectă (și/sau veți furniza fișierele-cheie corecte), volumul va fi montat cu litera unității selectate din lista afișată în fereastra principală VeraCrypt (și veți putea accesa datele criptate accesând litera unității selectate).\n\nMEMORAȚI SAU NOTAȚI-VĂ PAȘII DE MAI SUS. VA TREBUI SĂ-I URMAȚI DE FIECARE DATĂ CÂND VEȚI DORI SĂ MONTAȚI VOLUMUL ȘI SĂ ACCESAȚI DATELE STOCATE PE EL. Alternativ, în fereastra principală a VeraCrypt, apăsați pe „Selectare disc/partiție”, apoi selectați acest disc/partiție și apăsați pe „Montare volum”.\n\nDiscul/partiția a fost criptat(ă) cu succes (acum conține un volum VeraCrypt complet criptat) și este gata de utilizare.</entry>
     <entry lang="ro" key="NONSYS_INPLACE_DEC_FINISHED_INFO">Volumul VeraCrypt a fost decriptat cu succes.</entry>
     <entry lang="ro" key="NONSYS_INPLACE_DEC_FINISHED_DRIVE_LETTER_SEL_INFO">Volumul VeraCrypt a fost decriptat cu succes.\n\nAlegeți o literă de unitate pe care doriți să o atribuiți volumului decriptat și apoi apăsați pe «Finalizare».\n\nIMPORTANT: Până când nu atribuiți o literă de unitate volumului decriptat, nu veți putea accesa datele stocate pe acesta.</entry>
     <entry lang="ro" key="NONSYS_INPLACE_DEC_FINISHED_NO_DRIVE_LETTER_AVAILABLE">Atenționare: Pentru a putea accesa datele decriptate, trebuie atribuită o literă de unitate volumului decriptat. Totuși, acum nu există nici o literă de unitate liberă.\n\nEliberați o literă de unitate (de exemplu, deconectând o unitate USB sau hard disc extern etc.) și apoi apăsați pe OK.</entry>
     <entry lang="ro" key="FORMAT_FINISHED_INFO">Volumul VeraCrypt a fost creat cu succes.</entry>
     <entry lang="ro" key="FORMAT_FINISHED_TITLE">Volum creat</entry>
-    <entry lang="ro" key="FORMAT_HELP">IMPORTANT: Mișcați cursorul cât mai aleator posibil în interiorul acestei ferestre. Cu cât îl mișcați mai mult, cu atât mai bine. Aceasta mărește considerabil puterea criptografică a cheilor de criptare. Apoi apăsați pe «Formatare» pentru a crea volumul.</entry>
+    <entry lang="ro" key="FORMAT_HELP">IMPORTANT: Mișcați cursorul cât mai aleatoriu posibil în interiorul acestei ferestre. Cu cât îl mișcați mai mult, cu atât mai bine. Aceasta mărește considerabil puterea criptografică a cheilor de criptare. Apoi apăsați pe «Formatare» pentru a crea volumul.</entry>
     <entry lang="ro" key="FORMAT_HIDVOL_HOST_HELP">Apăsați pe «Formatare» pentru a crea volumul exterior. Pentru mai multe informații, consultați documentația.</entry>
     <entry lang="ro" key="FORMAT_HIDVOL_HOST_TITLE">Formatare volum exterior</entry>
     <entry lang="ro" key="FORMAT_HIDVOL_TITLE">Formatare volum ascuns</entry>
@@ -540,7 +540,7 @@
     <entry lang="ro" key="DAMAGE_TO_HIDDEN_VOLUME_PREVENTED">AVERTIZARE: S-a încercat salvarea datelor în zona volumului ascuns a volumului montat ca %c:! VeraCrypt e prevenit salvarea acestor date pentru a proteja volumul ascuns. Aceasta ar fi putut cauza coruperea sistemului de fișiere de pe volumul exterior și Windows ar fi putut raporta o eroare la scriere („Delayed Write Failed” sau „The parameter is incorrect”). Întregul volum (atât partea exterioară cât și cea ascunsă) va fi protejat la scriere până când va fi demontat. Dacă aceasta nu este prima dată când VeraCrypt a prevenit salvarea datelor în zona volumului ascuns a acestui volum, negarea plauzibilă a volumului ascuns ar putea fi afectată (din cauza posibilelor neconcordanțe din cadrul sistemului de fișiere a volumului exterior). Prin urmare, ar trebui să luați în considerare crearea unui nou volum VeraCrypt (cu formatarea rapidă dezactivată) și să mutați fișierele din acest volum în noul volum; acest volum ar trebui șters în siguranță (atât partea exterioară cât și partea ascunsă). Vă recomandăm insistent să reporniți sistemul de operare acum.</entry>
     <entry lang="ro" key="CANNOT_SATISFY_OVER_4G_FILE_SIZE_REQ">Ați indicat intenția de a stoca fișiere mai mari de 4 GiB pe volum. Aceasta necesită ca volumul să fie formatat ca NTFS/exFAT, ceea ce, oricum, nu va fi posibil.</entry>
     <entry lang="ro" key="CANNOT_CREATE_NON_HIDDEN_NTFS_VOLUMES_UNDER_HIDDEN_OS">Țineți cont că atunci când un sistem de operare ascuns rulează, volumele VeraCrypt neascunse nu pot fi formatate ca NTFS/exFAT. Motivul este că acel volum ar trebui montat temporar fără protecția la scriere pentru a permite sistemului de operare să-l formateze ca NTFS/exFAT (pe când formatarea ca și FAT este realizată de către VeraCrypt, nu de către sistemul de operare și fără ca volumul să fie montat). Pentru detalii suplimentare, vedeți mai jos. Puteți crea un volum neascuns NTFS/exFAT din sistemul de operare momeală.</entry>
-    <entry lang="ro" key="HIDDEN_VOL_CREATION_UNDER_HIDDEN_OS_HOWTO">Din motive de securitate, când un sistem de operare rulează, volumele ascunse pot fi create doar în modul „direct” (deoarece volumele exterioare trebuie să fie întotdeauna montate ca doar-citire). Pentru a crea un volum ascuns în siguranță, urmați acești pași:\n\n1) Porniți sistemul de operare momeală.\n\n2) Creați un volum VeraCrypt normal și, pe acest volum, copiați câteva fișiere aparent-importante pe care de fapt NU doriți să le ascundeți (volumul va deveni volumul exterior).\n\n3) Porniți sistemul ascuns și porniți asistentul de creare volume VeraCrypt. Dacă volumul este tip fișier, mutați-l pe o partiție sistem sau pe un alt volum ascuns (altfel, noul volum ascuns creat va fi montat ca doar-citire și nu va putea fi formatat). Urmați instrucțiunile asistentului astfel încât să selectați modul „direct” de creare a volumului ascus.\n\n4) În asistent, selectați volumul creat la pasul 2 și apoi urmați instrucțiunile pentru a crea un volum ascuns în el.</entry>
+    <entry lang="ro" key="HIDDEN_VOL_CREATION_UNDER_HIDDEN_OS_HOWTO">Din motive de securitate, când un sistem de operare rulează, volumele ascunse pot fi create doar în modul „direct” (deoarece volumele exterioare trebuie să fie întotdeauna montate ca doar-citire). Pentru a crea un volum ascuns în siguranță, urmați acești pași:\n\n1) Porniți sistemul de operare momeală.\n\n2) Creați un volum VeraCrypt normal și, pe acest volum, copiați câteva fișiere aparent-importante pe care de fapt NU doriți să le ascundeți (volumul va deveni volumul exterior).\n\n3) Porniți sistemul ascuns și porniți asistentul de creare volume VeraCrypt. Dacă volumul este tip fișier, mutați-l pe o partiție sistem sau pe un alt volum ascuns (altfel, noul volum ascuns creat va fi montat ca doar-citire și nu va putea fi formatat). Urmați instrucțiunile asistentului astfel încât să selectați modul „direct” de creare a volumului ascuns.\n\n4) În asistent, selectați volumul creat la pasul 2 și apoi urmați instrucțiunile pentru a crea un volum ascuns în el.</entry>
     <entry lang="ro" key="HIDDEN_OS_WRITE_PROTECTION_BRIEF_INFO">Din motive de securitate, când un sistem de operare rulează, sistemele de fișiere locale necriptate și volumele VeraCrypt neascunse sunt montate ca doar-citire (nu se pot scrie date pe astfel de sisteme de fișiere sau volume VeraCrypt).\n\nDatele pot fi scrise pe orice sistem de fișiere care se află pe un volum VeraCrypt ascuns (cu condiția ca volumul ascuns să se afle într-un container stocat pe un sistem de fișiere necriptat sau pe orice alt sistem de fișiere ca doar-citire).</entry>
     <entry lang="ro" key="HIDDEN_OS_WRITE_PROTECTION_EXPLANATION">Există trei motive principale pentru care au fost implementate astfel de contramăsuri:\n\n- Activează crearea unei platforme sigure pentru montarea volumelor VeraCrypt ascunse. Oficial, recomandăm  ca volumele ascunse să fie montate numai când un sistem de operare ascuns rulează. (Pentru mai multe informații, consultați subsecțiunea „Security Requirements and Precautions Pertaining to Hidden Volumes” din documentație.)\n\n- În unele cazuri, este posibil de determinat că, la un moment dat, un anumit sistem de fișiere nu a fost montat (sau că un anumit fișier de pe sistemul de fișiere nu a fost salvat sau accesat) într-o anumită instanță a unui sistem de operare (de ex. analizând și comparând jurnalele sistemului de fișiere, data fișierului, jurnalele aplicațiilor, jurnalele erorilor etc.). Aceasta poate indica că un sistem de operare ascuns este instalat pe calculator. Contramăsurile previn aceste situații.\n\n- Ele previn coruperea datelor și permit hibernarea în siguranță. Când Windows revine din hibernare, presupune că toate sistemele de fișiere montate sunt în aceeași stare ca atunci când sistemul a intrat în hibernare. VeraCrypt se asigură de asta prin protejarea la scriere a oricărui sistem de fișiere accesibil atât de pe sistemul momeală cât și de pe cel ascuns. Fără o astfel de protecție, sistemul de fișiere ar putea deveni corupt atunci când este montat de un sistem de operare în timp ce celălalt este în hibernare.</entry>
     <entry lang="ro" key="DECOY_TO_HIDDEN_OS_DATA_TRANSFER_HOWTO">Notă: Dacă trebuie să transferați în mod sigur fișiere de pe sistemul momeală pe cel ascuns, urmați acești pași:\n1) Porniți sistemul momeală.\n2) Salvați fișierele într-un volum necriptat sau într-un volum VeraCrypt exterior/normal.\n3) Porniți sistemul ascuns.\n4) Dacă ați salvat fișierele într-un volum VeraCrypt, montați-l (el va fi montat automat ca doar-citire).\n5) Copiați fișierele pe partiția sistemului ascuns sau pe un alt volum ascuns.</entry>
@@ -554,9 +554,9 @@
     <entry lang="ro" key="ERR_DEVICE_CLI_CREATE_NOT_SUPPORTED">Numai fișierele de tip container pot fi create prin linia de comandă.</entry>
     <entry lang="ro" key="ERR_CONTAINER_SIZE_TOO_BIG">Dimensiunea fișierului container specificată în linia de comandă este mai mare decât spațiul liber disponibil. Volumul nu poate fi creat.</entry>
     <entry lang="ro" key="ERR_VOLUME_SIZE_TOO_SMALL">Dimensiunea volumului specificată în linia de comandă este prea mică. Volumul nu poate fi creat.</entry>
-    <entry lang="ro" key="ERR_VOLUME_SIZE_TOO_BIG">imensiunea volumului specificată în linia de comandă este prea mare. Volumul nu poate fi creat.</entry>
+    <entry lang="ro" key="ERR_VOLUME_SIZE_TOO_BIG">Dimensiunea volumului specificată în linia de comandă este prea mare. Volumul nu poate fi creat.</entry>
     <entry lang="ro" key="INIT_SYS_ENC">Nu se pot inițializa componentele aplicației pentru criptarea sistemului.</entry>
-    <entry lang="ro" key="INIT_RAND">A eșuat inițializarea generatorului de numere aleatoare!</entry>
+    <entry lang="ro" key="INIT_RAND">A eșuat inițializarea generatorului de numere aleatorii!</entry>
     <entry lang="ro" key="CAPI_RAND">Windows Crypto API a eșuat!\n\n\n(Dacă raportați o eroare în legătură cu aceasta, includeți și următoarele informații tehnice în raportul erorii:\n%hs, Last Error = 0x%.8X)</entry>
     <entry lang="ro" key="INIT_REGISTER">Aplicația nu se poate inițializa. A eșuat înregistrarea clasei Dialog.</entry>
     <entry lang="ro" key="INIT_RICHEDIT">Eroare: A eșuat încărcarea librăriei de sistem „Rich Edit”.</entry>
@@ -579,7 +579,7 @@
     <entry lang="ro" key="NODRIVER">Nu se poate stabili conexiunea cu driverul VeraCrypt. VeraCrypt nu poate funcționa dacă driverul nu funcționează.\n\nȚineți cont că, datorită unei probleme din Windows, ar putea fi necesară reautentificarea utilizatorului sau repornirea sistemului pentru ca driverul să poată fi încărcat.</entry>
     <entry lang="ro" key="NOFONT">A apărut o eroare la încărcarea/pregătirea fonturilor.</entry>
     <entry lang="ro" key="NOT_FOUND">Litera unității nu a fost găsită sau litera unității nu a fost specificată.</entry>
-    <entry lang="ro" key="ERR_CANNOT_ASSIGN_DRIVE_LETTER_NONSYS_DEC">Eroare: nu se poate atribui litera de unitate.\n\nPână când nu este atribuită o literă de unitate volumului decriptat, nu veți putea accesa datele stocate pe acesta.\n\nReîncercare?</entry>
+    <entry lang="ro" key="ERR_CANNOT_ASSIGN_DRIVE_LETTER_NONSYS_DEC">Eroare: nu se poate atribui litera de unitate.\n\nPână când nu este atribuită o literă de unitate volumului decriptat, nu veți putea accesa datele stocate pe acesta.\n\nReîncercați?</entry>
     <entry lang="ro" key="DRIVE_LETTER_UNAVAILABLE">Litera unității nu este disponibilă.</entry>
     <entry lang="ro" key="NO_FILE_SELECTED">Nu sunt fișiere selectate!</entry>
     <entry lang="ro" key="NO_FREE_DRIVES">Nu sunt litere de unități disponibile.</entry>
@@ -620,7 +620,7 @@
     <entry lang="ro" key="NONSYS_INPLACE_ENC_RESUME_PASSWORD_PAGE_HELP">Introduceți parola și/sau fișierele-cheie pentru volumul VeraCrypt non-sistem unde doriți să fie reluat procesul de criptare din mers.\n\n\nRemarcă: După ce veți apăsa pe «Înainte», VeraCrypt va încerca să găsească toate volumele non-sistem unde procesul de criptare a fost întrerupt și unde antetul volumului VeraCrypt poate fi decriptat folosind parola și/sau fișierele-cheie. Dacă este găsit mai mult de un volum, va trebui să selectați unul din ele în pasul următor.</entry>
     <entry lang="ro" key="NONSYS_INPLACE_ENC_RESUME_VOL_SELECT_HELP">Selectați unul din volumele afișate. Lista conține fiecare volum non-sistem accesibil unde procesul de criptare a fost întrerupt și a căror antet a fost decriptat folosind parola și/sau fișierele-cheie.</entry>
     <entry lang="ro" key="NONSYS_INPLACE_DEC_PASSWORD_PAGE_HELP">Introduceți parola și/sau fișierele-cheie pentru volumul VeraCrypt non-sistem pe care doriți să-l decriptați.</entry>
-    <entry lang="ro" key="PASSWORD_HELP">Este foarte important să alegeți o parolă bună. Ar trebui să evitați să alegeți una care conține un singur cuvând care se poate afla într-un dicționar (sau o combinație de 2, 3 sau 4 astfel de cuvinte). Ar trebui să nu conțină niciun nume sau dată de naștere. Nu ar trebui să poată fi ghicită ușor. O parolă bună este o combinație amestecată de litere mici și mari, numere și caractere speciale, cum ar fi @ ^ = $ * + etc. Vă recomandăm să alegeți o parolă ce conține mai mult de 20 de caractere (cu cât mai lungă cu atât mai bine). Lungimea maximă posibilă este de 64 de caractere.</entry>
+    <entry lang="ro" key="PASSWORD_HELP">Este foarte important să alegeți o parolă bună. Ar trebui să evitați să alegeți una care conține un singur cuvânt care se poate afla într-un dicționar (sau o combinație de 2, 3 sau 4 astfel de cuvinte). Ar trebui să nu conțină niciun nume sau dată de naștere. Nu ar trebui să poată fi ghicită ușor. O parolă bună este o combinație amestecată de litere mici și mari, numere și caractere speciale, cum ar fi @ ^ = $ * + etc. Vă recomandăm să alegeți o parolă ce conține mai mult de 20 de caractere (cu cât mai lungă cu atât mai bine). Lungimea maximă posibilă este de 64 de caractere.</entry>
     <entry lang="ro" key="PASSWORD_HIDDENVOL_HELP">Alegeți o parolă pentru volumul ascuns.</entry>
     <entry lang="ro" key="PASSWORD_HIDDEN_OS_HELP">Alegeți o parolă pentru sistemul de operare ascuns (adică pentru volumul ascuns).</entry>
     <entry lang="ro" key="PASSWORD_HIDDEN_OS_NOTE">IMPORTANT: Parola pe care ați ales-o pentru sistemul de operare ascuns în acest pas trebuie să fie substanțial diferită de celelalte parole (adică față de parola pentru volumul exterior și de parola pentru sistemul de operare momeală).</entry>
@@ -687,7 +687,7 @@
     <entry lang="ro" key="TEST_PLAINTEXT_SIZE">Textul simplu de testat furnizat este prea lung sau prea scurt.</entry>
     <entry lang="ro" key="TWO_LAYER_CASCADE_HELP">Doi algoritmi în cascadă operând în mod XTS. Fiecare bloc este criptat prima dată cu %s (cheie %d-biți) și apoi cu %s (cheie %d-biți). Fiecare algoritm folosește cheia proprie. Fiecare cheie este reciproc independentă.</entry>
     <entry lang="ro" key="THREE_LAYER_CASCADE_HELP">Trei algoritmi în cascadă operând în mod XTS. Fiecare bloc este criptat prima dată cu %s (cheie %d-biți), apoi cu %hs (cheie %d-biți) și în final cu %s (cheie %d-biți). Fiecare algoritm folosește cheia proprie. Fiecare cheie este reciproc independentă.</entry>
-    <entry lang="ro" key="AUTORUN_MAY_NOT_ALWAYS_WORK">Rețineți că în funcție de configurația sistemului de operare, aceste funcții de autopornire și automontare pot funcționa numai când fișierele discului portabil sunt create pe un mediu nemodificabil de tip CD/DVD. În plus, aceasa nu este o eroare în VeraCrypt (este o limitare a sistemului de operare Windows).</entry>
+    <entry lang="ro" key="AUTORUN_MAY_NOT_ALWAYS_WORK">Rețineți că în funcție de configurația sistemului de operare, aceste funcții de autopornire și automontare pot funcționa numai când fișierele discului portabil sunt create pe un mediu nemodificabil de tip CD/DVD. În plus, aceasta nu este o eroare în VeraCrypt (este o limitare a sistemului de operare Windows).</entry>
     <entry lang="ro" key="TRAVELER_DISK_CREATED">Discul portabil VeraCrypt a fost creat cu succes.\n\nRețineți că, aveți nevoie de drepturi de administrator pentru a rula VeraCrypt în mod portabil. În plus, după examinarea fișierului de regiștri, este posibil de aflat dacă VeraCrypt a fost rulat pe un sistem Windows chiar dacă este executat în mod portabil.</entry>
     <entry lang="ro" key="TC_TRAVELER_DISK">Disc portabil VeraCrypt</entry>
     <entry lang="ro" key="TWOFISH_HELP">Proiectat de Bruce Schneier, John Kelsey, Doug Whiting, David Wagner, Chris Hall și Niels Ferguson. Publicat în 1998. Cheie 256-biți, bloc 128-biți. Modul de operare este XTS. Twofish a fost unul din finaliștii AES.</entry>
@@ -704,14 +704,14 @@
     <entry lang="ro" key="VOL_SEEKING">Eroare căutare amplasare în interiorul volumului.</entry>
     <entry lang="ro" key="VOL_SIZE_WRONG">Eroare: dimensiune volum incorectă.</entry>
     <entry lang="ro" key="WARN_QUICK_FORMAT">AVERTIZARE: Ar trebui să folosiți formatarea rapidă numai în următoarele cazuri:\n\n1) Discul nu conține date importante și nu aveți nevoie de negare plauzibilă.\n2) Discul a fost deja criptat în siguranță și în întregime.\n\nSigur doriți să folosiți formatarea rapidă?</entry>
-    <entry lang="ro" key="CONFIRM_SPARSE_FILE">Containerul dinamic este un fișier NTFS fragmentat prealocat a cărui dimensiune fizică (spațiu pe disc efectiv utilizat) crește pe măsură ce sunt adăugate date în el.\n\nATENȚIE: Performanța volumelor amplasate în fișiere fragmentate este semnificativ mai slabă decât a volumelor obișnuite. Volumele amplasate în fișiere fragmentate sunt, pe deasupra, mai puțin sigure deoarece este posibil de aflat care din sectoarele volumului nu sunt folosite. Prin urmare, volumele amplasate în fișiere nu pot furniza negarea plauzibilă (să gazduiască un volum ascuns). De altfel, țineți cont că, dacă datele sunt scrise într-un fișier  container fragmentat când nu există suficient spațiu pe sistemul de fișiere gazdă, sistemul de fișiere criptat poate deveni corupt.\n\nSigur doriți crearea unui volum tip fișier fragmentat?</entry>
+    <entry lang="ro" key="CONFIRM_SPARSE_FILE">Containerul dinamic este un fișier NTFS fragmentat prealocat a cărui dimensiune fizică (spațiu pe disc efectiv utilizat) crește pe măsură ce sunt adăugate date în el.\n\nATENȚIE: Performanța volumelor amplasate în fișiere fragmentate este semnificativ mai slabă decât a volumelor obișnuite. Volumele amplasate în fișiere fragmentate sunt, pe deasupra, mai puțin sigure deoarece este posibil de aflat care din sectoarele volumului nu sunt folosite. Prin urmare, volumele amplasate în fișiere nu pot furniza negarea plauzibilă (să găzduiască un volum ascuns). De altfel, țineți cont că, dacă datele sunt scrise într-un fișier  container fragmentat când nu există suficient spațiu pe sistemul de fișiere gazdă, sistemul de fișiere criptat poate deveni corupt.\n\nSigur doriți crearea unui volum tip fișier fragmentat?</entry>
     <entry lang="ro" key="SPARSE_FILE_SIZE_NOTE">Trebuie să știți că dimensiunea containerului raportată de către Windows și de către VeraCrypt va fi întotdeauna egală cu dimensiunea lui maximă. Pentru a afla dimensiunea fizică curentă a containerului (spațiul actual utilizat pe disc), apăsați cu clic dreapta pe fișierul container (într-o fereastră Windows Explorer, nu în VeraCrypt), apoi selectați „Properties” și vedeți valoarea „Size on disk”.\n\nÎn plus, dacă mutați un container dinamic pe un alt volum sau disc, dimensiunea fizică a containerului va fi extinsă la cea maximă. (Puteți preveni aceasta prin crearea unui nou container dinamic în locul de destinație, montarea acestuia și apoi mutarea fișierelor de pe vechiul container pe cel nou.)</entry>
     <entry lang="ro" key="PASSWORD_CACHE_WIPED_SHORT">Parola păstrată a fost ștearsă</entry>
     <entry lang="ro" key="PASSWORD_CACHE_WIPED">Parolele (și/sau conținutul fișierelor cheie) stocate în driverul VeraCrypt au fost șterse.</entry>
     <entry lang="ro" key="WRONG_VOL_TYPE">VeraCrypt nu poate schimba parola pentru un volum străin.</entry>
     <entry lang="ro" key="SELECT_FREE_DRIVE">Alegeți o literă de volum liberă din listă.</entry>
     <entry lang="ro" key="SELECT_A_MOUNTED_VOLUME">Selectați un volum montat din lista cu litere de unități.</entry>
-    <entry lang="ro" key="AMBIGUOUS_VOL_SELECTION">Momentan sunt selectate două volume montate (unul în lista cu litere de unități și altul în câmpul de introducere de sub listă).\n\nVAlegeți volumul pe care doriți să-l selectați:</entry>
+    <entry lang="ro" key="AMBIGUOUS_VOL_SELECTION">Momentan sunt selectate două volume montate (unul în lista cu litere de unități și altul în câmpul de introducere de sub listă).\n\nAlegeți volumul pe care doriți să-l selectați:</entry>
     <entry lang="ro" key="CANT_CREATE_AUTORUN">Eroare: nu se poate crea autorun.inf</entry>
     <entry lang="ro" key="ERR_PROCESS_KEYFILE">Eroare la procesarea fișierului cheie!</entry>
     <entry lang="ro" key="ERR_PROCESS_KEYFILE_PATH">Eroare procesare cale fișier-cheie!</entry>
@@ -722,7 +722,7 @@
     <entry lang="ro" key="ERR_PERF_COUNTER">Eroare: nu s-a putut prelua valoarea contorului de performanță.</entry>
     <entry lang="ro" key="ERR_VOL_FORMAT_BAD">Eroare: formatare eronată volum.</entry>
     <entry lang="ro" key="ERR_HIDDEN_NOT_NORMAL_VOLUME">Eroare: ați furnizat o parolă pentru un volum ascuns (nu pentru un volum normal).</entry>
-    <entry lang="ro" key="ERR_HIDDEN_VOL_HOST_ENCRYPTED_INPLACE">Din motive de securitate, un volum ascuns nu poate fi creat într-un volum ce conține un sistem de fișiere care a fost criptat din mers (deoarcere spațiul liber de pe volum nu a fost umplut cu date aleatoare).</entry>
+    <entry lang="ro" key="ERR_HIDDEN_VOL_HOST_ENCRYPTED_INPLACE">Din motive de securitate, un volum ascuns nu poate fi creat într-un volum ce conține un sistem de fișiere care a fost criptat din mers (deoarece spațiul liber de pe volum nu a fost umplut cu date aleatorii).</entry>
     <entry lang="ro" key="LEGAL_NOTICES_DLG_TITLE">VeraCrypt - Mențiuni legale</entry>
     <entry lang="ro" key="ALL_FILES">Toate fișierele</entry>
     <entry lang="ro" key="TC_VOLUMES">Volume VeraCrypt</entry>
@@ -745,23 +745,23 @@
     <entry lang="ro" key="CLUSTER_TOO_SMALL">Dimensiunea selectată a sectorului este prea mică pentru dimensiunea acestui volum. Va fi folosită o dimensiune mai mare pentru sectoare.</entry>
     <entry lang="ro" key="CANT_GET_VOLSIZE">Eroare: nu se poate prelua dimensiunea volumului!\n\nAsigurați-vă că volumul selectat nu este accesat de către sistem sau vreo aplicație.</entry>
     <entry lang="ro" key="HIDDEN_VOL_HOST_SPARSE">Volumele ascunse nu trebuie create în containere dinamice (fișiere fragmentate). Pentru a obține negarea plauzibilă, volumul ascuns trebuie creat într-un container non-dinamic.</entry>
-    <entry lang="ro" key="HIDDEN_VOL_HOST_UNSUPPORTED_FILESYS">Asistemul de creare volum VeraCrypt poate crea un volum ascuns numai într-un volum FAT/exFAT sau NTFS.</entry>
-    <entry lang="ro" key="HIDDEN_VOL_HOST_UNSUPPORTED_FILESYS_WIN2000">În Windows 2000, Asistemul de creare volum VeraCrypt poate crea un volum ascuns numai într-un volum FAT.</entry>
+    <entry lang="ro" key="HIDDEN_VOL_HOST_UNSUPPORTED_FILESYS">Asistentul de creare volume VeraCrypt poate crea un volum ascuns numai într-un volum FAT/exFAT sau NTFS.</entry>
+    <entry lang="ro" key="HIDDEN_VOL_HOST_UNSUPPORTED_FILESYS_WIN2000">În Windows 2000, asistentul de creare volume VeraCrypt poate crea un volum ascuns numai într-un volum FAT.</entry>
     <entry lang="ro" key="HIDDEN_VOL_HOST_NTFS">Notă: Sistemul de fișiere FAT/exFAT este mult mai potrivit pentru volume exterioare decât cel NTFS (adică, dimensiunea maximă posibilă a volumului ascuns va putea fi semnificativ mai mare dacă volumul a fost formatat ca FAT/exFAT).</entry>
     <entry lang="ro" key="HIDDEN_VOL_HOST_NTFS_ASK">Rețineți că sistemul de fișiere FAT/exFAT este mult mai potrivit pentru volume exterioare decât cel NTFS. De exemplu, dimensiunea maximă posibilă a volumului ascuns va putea fi semnificativ mai mare dacă volumul a fost formatat ca FAT/exFAT (deoarece sistemul de fișiere NTFS stochează întotdeauna datele interne exact în mijlocul volumului, prin urmare, volumul ascuns se poate crea doar în a doua jumătate a volumului exterior).\n\nSigur doriți formatarea volumului exterior ca NTFS?</entry>
     <entry lang="ro" key="OFFER_FAT_FORMAT_ALTERNATIVE">Doriți în schimb formatarea volumului ca FAT?</entry>
-    <entry lang="ro" key="FAT_NOT_AVAILABLE_FOR_SO_LARGE_VOLUME">Notă: Acest volum nu poate fi formatat ca FAT, deoarece depășește dimensiunea maximă a volumului suportată de sistemul de fișiere FAT32 pentru aplicarea dimensiunii sectoarelor (2 TiB pentru sectoate de 512 baiți și 16 TiB pentru sectoare de 4096 baiți).</entry>
+    <entry lang="ro" key="FAT_NOT_AVAILABLE_FOR_SO_LARGE_VOLUME">Notă: Acest volum nu poate fi formatat ca FAT, deoarece depășește dimensiunea maximă a volumului suportată de sistemul de fișiere FAT32 pentru aplicarea dimensiunii sectoarelor (2 TiB pentru sectoare de 512 baiți și 16 TiB pentru sectoare de 4096 baiți).</entry>
     <entry lang="ro" key="PARTITION_TOO_SMALL_FOR_HIDDEN_OS">Eroare: Partiția pentru sistemul de operare ascuns (adică prima partiție de după partiția sistem) trebuie să fie cu cel puțin 5% mai mare decât partiția sistem (partiția sistem este cea de pe care rulează acum sistemul de operare instalat).</entry>
     <entry lang="ro" key="PARTITION_TOO_SMALL_FOR_HIDDEN_OS_NTFS">Eroare:  Partiția pentru sistemul de operare ascuns (adică prima partiție de după partiția sistem) trebuie să fie de cel puțin 110% (de 2,1 ori) mai mare decât partiția sistem (partiția sistem este cea pe care rulează acum sistemul de operare instalat). Motivul este că sistemul de fișiere NTFS stochează întotdeauna datele interne în mijlocul volumului și, prin urmare, volumul ascuns (care va conține clona partiției sistem) se poate afla doar în a doua jumătate a partiției.</entry>
-    <entry lang="ro" key="OUTER_VOLUME_TOO_SMALL_FOR_HIDDEN_OS_NTFS">Eroare: dacă volumul exterior este formatat ca NTFS, trebuie să fie de cel puțin 110% (de 2,1 ori) mai mare decât partiția sistem. Motivul este că sistemul de fișiere NTFS stochează întotdeauna datele interne în mijlocul volumului și, prin urmare, volumul ascuns (care va conține clona partiției sistem) se poate afla doar în a doua jumătate a volumului exterior.\n\nNotă: Volumul exterior trebuie să se afle pe aceeasi partiție ca și sistemul de operare ascuns (adică prima partiție de după partiția sistem).</entry>
+    <entry lang="ro" key="OUTER_VOLUME_TOO_SMALL_FOR_HIDDEN_OS_NTFS">Eroare: dacă volumul exterior este formatat ca NTFS, trebuie să fie de cel puțin 110% (de 2,1 ori) mai mare decât partiția sistem. Motivul este că sistemul de fișiere NTFS stochează întotdeauna datele interne în mijlocul volumului și, prin urmare, volumul ascuns (care va conține clona partiției sistem) se poate afla doar în a doua jumătate a volumului exterior.\n\nNotă: Volumul exterior trebuie să se afle pe aceeași partiție ca și sistemul de operare ascuns (adică prima partiție de după partiția sistem).</entry>
     <entry lang="ro" key="NO_PARTITION_FOLLOWS_BOOT_PARTITION">Eroare: nu există partiții după partiția sistem.\n\nRețineți că înainte de a crea un sistem de operare ascuns, trebuie să creați o partiție pentru acesta pe discul sistem. Trebuie să fie prima partiție după partiția sistem și trebuie să fie cel puțin cu 5% mai mare decât partiția sistem (partiția sistem este cea de pe care rulează acum sistemul de operare instalat). Totuși, dacă volumul exterior (a nu se confunda cu partiția sistem) este formatat ca NTFS, partiția pentru sistemul de operare ascuns trebuie să fie de cel puțin 110% (de 2,1 ori) mai mare decât partiția sistem (motivul este că sistemul de fișiere NTFS stochează întotdeauna datele interne în mijlocul volumului și, prin urmare, volumul ascuns, care va conține clona partiției sistem, se poate afla doar în a doua jumătate a partiției).</entry>
-    <entry lang="ro" key="TWO_SYSTEMS_IN_ONE_PARTITION_REMARK">Remarcă: Nu este practică (și prin urmare nu este suportată) instalarea sistemului de operare în două volume VeraCrypt care au fost incluse într-o singură partiție, deoarce folosind un sistem de operare exterior va necesita deseori scrierea de date în zona sistemului de operare ascuns (și dacă astfel de operații de scriere vor fi împiedicate folosind funcția de protejare a volumelor ascunse, aceasta va determina inevitabil căderi ale sistemului, adică erori tip „Ecran albastru”).</entry>
+    <entry lang="ro" key="TWO_SYSTEMS_IN_ONE_PARTITION_REMARK">Remarcă: Nu este practică (și prin urmare nu este suportată) instalarea sistemului de operare în două volume VeraCrypt care au fost incluse într-o singură partiție, deoarece folosind un sistem de operare exterior va necesita deseori scrierea de date în zona sistemului de operare ascuns (și dacă astfel de operații de scriere vor fi împiedicate folosind funcția de protejare a volumelor ascunse, aceasta va determina inevitabil căderi ale sistemului, adică erori tip „Ecran albastru”).</entry>
     <entry lang="ro" key="FOR_MORE_INFO_ON_PARTITIONS">Pentru informații despre crearea și gestionarea partițiilor, consultați documentația furnizată cu sistemul de operare sau contactați echipa de suport tehnic a furnizorului pentru asistență.</entry>
     <entry lang="ro" key="SYSTEM_PARTITION_NOT_ACTIVE">Eroare: sistemul de operare ce rulează acum nu este instalat pe partiția de pornire (prima partiție activă). Această configurație nu este suportată.</entry>
     <entry lang="ro" key="CONFIRM_FAT_FOR_FILES_OVER_4GB">Ați indicat că doriți să stocați fișiere mai mari de 4 GiB în acest volum VeraCrypt. Totuși, ați ales sistemul de fișiere FAT, pe care fișierele mai mari de 4 GiB nu pot fi stocate.\n\nSigur doriți să formatați volumul ca FAT?</entry>
     <entry lang="ro" key="NONSYS_INPLACE_DECRYPTION_BAD_VOL_FORMAT">Eroare: VeraCrypt nu suportă decriptarea din mers a volumelor non-sistem anterioare create de VeraCrypt 1.0b sau mai vechi.\n\nNotă: Puteți totuși decripta fișierele stocate în volum prin copierea/mutarea lor pe un volum necriptat.</entry>
     <entry lang="ro" key="NONSYS_INPLACE_DECRYPTION_CANT_DECRYPT_HID_VOL">Eroare: VeraCrypt nu poate decripta înapoi un volum VeraCrypt ascuns.\n\nNotă: Puteți decripta fișierele stocate în volum prin copierea/mutarea lor pe un volum necriptat.</entry>
-    <entry lang="ro" key="CONFIRM_VOL_CONTAINS_NO_HIDDEN_VOL">Atenție: VeraCrypt nu poate decripta înapoi un volum care conține un volum VeraCrypt ascuns (volumul ascuns va fi suprascris cu date aleatoare).\n\nConfirmați dacă volumul ce va fi decriptat nu conține un volum ascuns.\n\nNotă: Dacă volumul conține un volum ascuns, dar nu vă deranjează că va fi pierdut, puteți selecta «Continuare» (volumul exterior va fi decriptat în siguranță).</entry>
+    <entry lang="ro" key="CONFIRM_VOL_CONTAINS_NO_HIDDEN_VOL">Atenție: VeraCrypt nu poate decripta înapoi un volum care conține un volum VeraCrypt ascuns (volumul ascuns va fi suprascris cu date aleatorii).\n\nConfirmați dacă volumul ce va fi decriptat nu conține un volum ascuns.\n\nNotă: Dacă volumul conține un volum ascuns, dar nu vă deranjează că va fi pierdut, puteți selecta «Continuare» (volumul exterior va fi decriptat în siguranță).</entry>
     <entry lang="ro" key="VOL_CONTAINS_NO_HIDDEN_VOL">Volumul nu conține niciun volum ascuns. Continuare.</entry>
     <entry lang="ro" key="VOL_CONTAINS_A_HIDDEN_VOL">Volumul conține un volum ascuns. Anulare.</entry>
     <entry lang="ro" key="CANT_ACCESS_VOL">Eroare: volumul nu poate fi accesat!\n\nAsigurați-vă că volumul selectat există, că nu este montat sau accesat de către sistem sau vreo aplicație, că aveți drepturi de citire/scriere asupra volumului și că nu este protejat la scriere.</entry>
@@ -772,7 +772,7 @@
     <entry lang="ro" key="INPLACE_ENC_GENERIC_ERR_RESUME">O eroare a împiedicat VeraCrypt să reia procesul de criptare/decriptare a partiției/volumului.\n\nÎncercați să reparați orice problemă raportată anterior și apoi încercați din nou dacă e posibil. Volumul nu poate fi montat până când nu este complet criptat sau decriptat.</entry>
     <entry lang="ro" key="INPLACE_DEC_GENERIC_ERR">O eroare a împiedicat VeraCrypt să decripteze volumul. Încercați să reparați orice problemă raportată anterior și apoi încercați din nou.</entry>
     <entry lang="ro" key="CANT_UNMOUNT_OUTER_VOL">Eroare: volumul exterior nu poate fi demontat!\n\nVolumul nu poate fi demontat dacă conține fișiere și foldere accesate de un program sau de către sistem.\n\nÎnchideți orice program care ar putea accesa fișierele și folderele de pe volum și apoi apăsați pe «Reluare».</entry>
-    <entry lang="ro" key="CANT_GET_OUTER_VOL_INFO">Eroare: nu se pot obține informații depre volumul exterior!\nCrearea volumului nu poate continua.</entry>
+    <entry lang="ro" key="CANT_GET_OUTER_VOL_INFO">Eroare: nu se pot obține informații despre volumul exterior!\nCrearea volumului nu poate continua.</entry>
     <entry lang="ro" key="CANT_ACCESS_OUTER_VOL">Eroare: volumul exterior nu poate fi accesat! Crearea volumului nu poate continua.</entry>
     <entry lang="ro" key="CANT_MOUNT_OUTER_VOL">Eroare: volumul exterior nu poate fi montat! Crearea volumului nu poate continua.</entry>
     <entry lang="ro" key="CANT_GET_CLUSTER_BITMAP">Eroare: nu se poate prelua harta sectoarelor volumului! Crearea volumului nu poate continua.</entry>
@@ -813,7 +813,7 @@
     <entry lang="ro" key="SECONDARY_KEY_SIZE_LRW">Mărime cheie Tweak (Mod LRW)</entry>
     <entry lang="ro" key="BITS">biți</entry>
     <entry lang="ro" key="BLOCK_SIZE">Mărime bloc</entry>
-    <entry lang="ro" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="ro" key="KDF">KDF</entry>
     <entry lang="ro" key="PKCS5_ITERATIONS">Contor iterații PKCS-5</entry>
     <entry lang="ro" key="VOLUME_CREATE_DATE">Volum creat</entry>
     <entry lang="ro" key="VOLUME_HEADER_DATE">Ultima modificare antet</entry>
@@ -852,7 +852,7 @@
     <entry lang="ro" key="UPGRADE">Actualizare</entry>
     <entry lang="ro" key="UNINSTALL">Dezinstalare</entry>
     <entry lang="ro" key="SETUP_ADMIN">Pentru a instala/dezinstala cu succes VeraCrypt, trebuie să aveți drepturi de administrator. Doriți să continuați?</entry>
-    <entry lang="ro" key="TC_INSTALLER_IS_RUNNING">Instalatorul VeraCrypt rulează deja pe acest sistem și efectuează sau pregătește instalarea sau actualizarea programului VeraCrypt. Înainte de a continua, așteptați-l să termine sau închideți-l. Dacă nu-l puteți închide, reporniţi sistemul înainte de a continua.</entry>
+    <entry lang="ro" key="TC_INSTALLER_IS_RUNNING">Instalatorul VeraCrypt rulează deja pe acest sistem și efectuează sau pregătește instalarea sau actualizarea programului VeraCrypt. Înainte de a continua, așteptați-l să termine sau închideți-l. Dacă nu-l puteți închide, reporniți sistemul înainte de a continua.</entry>
     <entry lang="ro" key="INSTALL_FAILED">Instalare eșuată.</entry>
     <entry lang="ro" key="UNINSTALL_FAILED">Dezinstalare eșuată.</entry>
     <entry lang="ro" key="DIST_PACKAGE_CORRUPTED">Acest pachet de distribuție este distrus. Încercați să-l descărcați din nou (de preferat de la pagina web oficială VeraCrypt aflată la adresa veracrypt.jp).</entry>
@@ -865,7 +865,7 @@
     <entry lang="ro" key="INSTALL_OK">VeraCrypt a fost instalat cu succes.</entry>
     <entry lang="ro" key="SETUP_UPDATE_OK">VeraCrypt a fost actualizat cu succes.</entry>
     <entry lang="ro" key="UPGRADE_OK_REBOOT_REQUIRED">VeraCrypt  fost actualizat cu succes. Totuși, înainte de a începe să-l utilizați, calculatorul trebuie repornit.\n\nDoriți să-l reporniți acum?</entry>
-    <entry lang="ro" key="SYS_ENC_UPGRADE_FAILED">Eșuare actualizare VeraCrypt!\n\nIMPORTANT: Înaite de a închide sau reporni sistemul, vă recomandăm insistent să utilizați funcția „System Restore” (meniul „Start” > „All programs” > „Accessories” > „System Tools” > „System Restore”) pentru a restaura sistemul la un punct de restaurare denumit „VeraCrypt installation”. Dacă „System Restore” nu este disponibil, ar trebui să încercați instalarea versiunii originale sau a celei noi din nou, înainte de a închide sau reporni sistemul.</entry>
+    <entry lang="ro" key="SYS_ENC_UPGRADE_FAILED">Eșuare actualizare VeraCrypt!\n\nIMPORTANT: Înainte de a închide sau reporni sistemul, vă recomandăm insistent să utilizați funcția „System Restore” (meniul „Start” > „All programs” > „Accessories” > „System Tools” > „System Restore”) pentru a restaura sistemul la un punct de restaurare denumit „VeraCrypt installation”. Dacă „System Restore” nu este disponibil, ar trebui să încercați instalarea versiunii originale sau a celei noi din nou, înainte de a închide sau reporni sistemul.</entry>
     <entry lang="ro" key="UNINSTALL_OK">VeraCrypt a fost dezinstalat cu succes.\n\nApăsați pe «Finalizare» pentru a șterge instalatorul VeraCrypt și folderul %s. Rețineți că folderul nu va fi șters dacă conține fișiere care nu au fost instalate de către instalatorul VeraCrypt sau create de către VeraCrypt.</entry>
     <entry lang="ro" key="REMOVING_REG">Eliminare intrări regiștri VeraCrypt</entry>
     <entry lang="ro" key="ADDING_REG">Adăugare intrări regiștri</entry>
@@ -948,8 +948,8 @@
     <entry lang="ro" key="VOL_HEADER_BACKED_UP">Rezerva antetului volumului a fost creată cu succes.\n\nIMPORTANT: Restaurarea antetului volumului utilizând această rezervă va restaura și parola volumului curent. În plus, dacă au fost necesare fișiere-cheie pentru a monta volumul, aceleași fișiere-cheie vor fi necesare pentru a monta din nou volumul când antetul volumului va fi restaurat.\n\nATENȚIE: Acest antet volum de rezervă  poate fi utilizat pentru a restaura antetul NUMAI pentru acest volum. Dacă utilizați acest antet de rezervă pentru a restaura un volum diferit, veți putea monta volumul, dar NU veți putea să decriptați datele stocate în volum (deoarece veți modifica cheia principală).</entry>
     <entry lang="ro" key="VOL_HEADER_RESTORED">Antetul volumului a fost restaurat cu succes.\n\nIMPORTANT: o parolă veche ar fi putut fi restaurată de asemenea. În plus, dacă au fost/sunt necesare fișiere-cheie pentru a monta volumul când a fost efectuată rezerva, aceleași fișiere-cheie sunt și acum necesare pentru a monta volumul.</entry>
     <entry lang="ro" key="EXTERNAL_VOL_HEADER_BAK_FIRST_INFO">Din motive de securitate, va trebui să introduceți parola corectă (și/sau să furnizați fișierele-cheie corecte) pentru volum.\n\nNotă: Dacă volumul conține un volum ascuns, va trebui să introduceți parola corectă (și/sau să furnizați fișierele-cheie corecte) pentru volumul exterior mai întâi. După aceea, dacă alegeți să faceți o copie de rezervă a antetului volumului ascuns, va trebui să introduceți parola corectă (și/sau să furnizați fișierele-cheie corecte) pentru volumul ascuns.</entry>
-    <entry lang="ro" key="CONFIRM_VOL_HEADER_BAK">Sigur doriți să creați o copie de rezervă a antetului pentru volumul %s?\n\nDupă ce veți apăsa pe «Da», vi se va solicita numele fișierului copiei de rezervă a antetului.\n\nNotă: Atât antetul volumului standard cât și cel al volumului ascuns va fi recriptat folosind o nouă cheie și stocat în fișierul de rezervă. Dacă nu există un volum ascuns în acest volum, zona rezervată pentru antetul volumului ascuns în fișierul rezervă va fi completată cu date aleatoare (pentru a păstra negarea plauzibilă). Când restaurați un antet de volum dintr-un fișier rezervă, va trebui să introduceți parola corectă (și/sau să furnizați fișierele-cheie corecte) care au fost valide când a fost creată copia de rezervă a antetului volumului. Parola (și/sau fișierele-cheie) va determina, de asemeni, tipul antetului volumului ce va fi restaurat, adică standard sau ascuns (VeraCrypt determină tipul printr-un proces de încercări repetate de decriptare).</entry>
-    <entry lang="ro" key="CONFIRM_VOL_HEADER_RESTORE">Sigur doriți să restaurați antetul pentru volumul %s?\n\nATENȚIE: Restaurând antetul volumului se reastaurează și parola volumului care a fost validă când s-a efectuat copia de rezervă. În plus, dacă au fost necesare fișiere-cheie pentru a monta volumul, aceleași fișiere-cheie vor fi necesare pentru a monta din nou volumul când antetul volumului va fi restaurat.\n\nDupă ce veți apăsa pe «Da», veți selecta fișierul de rezervă al antetului.</entry>
+    <entry lang="ro" key="CONFIRM_VOL_HEADER_BAK">Sigur doriți să creați o copie de rezervă a antetului pentru volumul %s?\n\nDupă ce veți apăsa pe «Da», vi se va solicita numele fișierului copiei de rezervă a antetului.\n\nNotă: Atât antetul volumului standard cât și cel al volumului ascuns va fi recriptat folosind o nouă cheie și stocat în fișierul de rezervă. Dacă nu există un volum ascuns în acest volum, zona rezervată pentru antetul volumului ascuns în fișierul rezervă va fi completată cu date aleatorii (pentru a păstra negarea plauzibilă). Când restaurați un antet de volum dintr-un fișier rezervă, va trebui să introduceți parola corectă (și/sau să furnizați fișierele-cheie corecte) care au fost valide când a fost creată copia de rezervă a antetului volumului. Parola (și/sau fișierele-cheie) va determina, de asemeni, tipul antetului volumului ce va fi restaurat, adică standard sau ascuns (VeraCrypt determină tipul printr-un proces de încercări repetate de decriptare).</entry>
+    <entry lang="ro" key="CONFIRM_VOL_HEADER_RESTORE">Sigur doriți să restaurați antetul pentru volumul %s?\n\nATENȚIE: Restaurând antetul volumului se restaurează și parola volumului care a fost validă când s-a efectuat copia de rezervă. În plus, dacă au fost necesare fișiere-cheie pentru a monta volumul, aceleași fișiere-cheie vor fi necesare pentru a monta din nou volumul când antetul volumului va fi restaurat.\n\nDupă ce veți apăsa pe «Da», veți selecta fișierul de rezervă al antetului.</entry>
     <entry lang="ro" key="DOES_VOLUME_CONTAIN_HIDDEN">Volumul conține un volum ascuns?</entry>
     <entry lang="ro" key="VOLUME_CONTAINS_HIDDEN">Volumul conține un volum ascuns</entry>
     <entry lang="ro" key="VOLUME_DOES_NOT_CONTAIN_HIDDEN">Volumul nu conține un volum ascuns</entry>
@@ -967,10 +967,10 @@
     <entry lang="ro" key="RESCUE_DISK_NON_WIZARD_CHECK_PASSED">Discul de Recuperare VeraCrypt a fost verificat cu succes.</entry>
     <entry lang="ro" key="RESCUE_DISK_NON_WIZARD_CHECK_FAILED">Nu se poate verifica dacă discul de recuperare a fost scris corect.\n\nDacă ați scris discul de recuperare, scoateți-l și reintroduceți-l în CD/DVD; apoi încercați din nou. Dacă tot nu funcționează, încercați alt program de înregistrare CD/DVD și/sau alt mediu inscriptibil.\n\nDacă ați încercat să verificați un Disc de Recuperare VeraCrypt creat pentru o cheie principală, parolă etc. diferită, un astfel de disc de recuperare va eșua întotdeauna această verificare. Pentru a crea un nou disc de recuperare complet compatibil cu configurația curentă, selectați „Sistem” > „Creare disc de recuperare”.</entry>
     <entry lang="ro" key="RESCUE_DISK_ISO_IMAGE_CHECK_PASSED">Imaginea Riscului de Recuperare VeraCrypt a fost verificată cu succes.</entry>
-    <entry lang="ro" key="RESCUE_DISK_ISO_IMAGE_CHECK_FAILED">Verificarea Discului de Recuperare VeraCrypt a eșuat.\n\nDacă ați încercat să verificați o imagine a unui Disc de Recuperare VeraCrypt creată pentru o cheie principală, parolă, cod aleator etc. diferite, țineți minte că astfel de imagine va eșua întotdeaunua la pasul de verificare. Pentru a crea o nouă imagine a discului de recuperare complet compatibilă cu configurația curentă, selectați „Sistem” > „Creare disc de recuperare”.</entry>
+    <entry lang="ro" key="RESCUE_DISK_ISO_IMAGE_CHECK_FAILED">Verificarea Discului de Recuperare VeraCrypt a eșuat.\n\nDacă ați încercat să verificați o imagine a unui Disc de Recuperare VeraCrypt creată pentru o cheie principală, parolă, cod aleatoriu etc. diferite, țineți minte că astfel de imagine va eșua întotdeauna la pasul de verificare. Pentru a crea o nouă imagine a discului de recuperare complet compatibilă cu configurația curentă, selectați „Sistem” > „Creare disc de recuperare”.</entry>
     <entry lang="ro" key="ERROR_CREATING_RESCUE_DISK">Eroare creare Disc de Recuperare VeraCrypt.</entry>
     <entry lang="ro" key="CANNOT_CREATE_RESCUE_DISK_ON_HIDDEN_OS">Discul de Recuperare VeraCrypt nu poate fi creat când sistemul de operare ascuns rulează.\n\nPentru a crea un Disc de Recuperare VeraCrypt, porniți sistemul de operare momeală și apoi selectați „Sistem” > „Creare disc de recuperare”.</entry>
-    <entry lang="ro" key="RESCUE_DISK_CHECK_FAILED">Nu se poate verifica dacă discul de recuperare a fost inscipționat corect.\n\nDacă l-ați creat, scoateți-l și reintroduceți-l în CD/DVD; apoi încercați din nou. Dacă tot nu funcționează, încercați alt program de înregistrare CD/DVD și/sau alt mediu inscriptibil%s.\n\nDacă nu ați scris încă discul de recuperare, faceți-o acum și apoi apăsați pe «Înainte».\n\nDacă ați încercat să verificați un Disc de Recuperare VeraCrypt creat înainte de a porni acest asistent, un astfel de disc de recuperare nu poate fi utilizat, deoarece a fost creat pentru o cheie principală diferită. Trebuie să inscripționați noul disc de recuperare generat.</entry>
+    <entry lang="ro" key="RESCUE_DISK_CHECK_FAILED">Nu se poate verifica dacă discul de recuperare a fost inscripționat corect.\n\nDacă l-ați creat, scoateți-l și reintroduceți-l în CD/DVD; apoi încercați din nou. Dacă tot nu funcționează, încercați alt program de înregistrare CD/DVD și/sau alt mediu inscriptibil%s.\n\nDacă nu ați scris încă discul de recuperare, faceți-o acum și apoi apăsați pe «Înainte».\n\nDacă ați încercat să verificați un Disc de Recuperare VeraCrypt creat înainte de a porni acest asistent, un astfel de disc de recuperare nu poate fi utilizat, deoarece a fost creat pentru o cheie principală diferită. Trebuie să inscripționați noul disc de recuperare generat.</entry>
     <entry lang="ro" key="RESCUE_DISK_CHECK_FAILED_SENTENCE_APPENDIX"> și/sau alt program de inscripționare CD/DVD</entry>
     <entry lang="ro" key="SYSTEM_FAVORITES_DLG_TITLE">VeraCrypt - Volume sistem favorite</entry>
     <entry lang="ro" key="SYS_FAVORITES_HELP_LINK">Ce sunt volumele sistem favorite?</entry>
@@ -1003,7 +1003,7 @@
     <entry lang="ro" key="LARGE_IDE_WARNING_2K">AVERTIZARE: Se pare că nu ați aplicat Service Pack 3 sau ulterior la instalarea Windows. Nu ar trebui să scrieți pe discuri IDE mai mari de 128 GiB în Windows 2000 la care nu ați adăugat Service Pack 3 sau ulterior! Dacă o faceți, datele de pe disc (indiferent dacă e un volum VeraCrypt sau nu) ar putea fi corupte. Rețineți că aceasta este o limitare a sistemului Windows, nu o eroare din VeraCrypt.\n\nNotă: Ar trebui să activați suportul LBA 48-biți în regiștri; pentru mai multe informații, consultați  http://support.microsoft.com/kb/305098/EN-US</entry>
     <entry lang="ro" key="LARGE_IDE_WARNING_2K_REGISTRY">AVERTIZARE: Suportul ATAPI LBA 48-biți este dezactivat în acest sistem. Prin urmare, nu ar trebui să scrieți pe discuri IDE mai mari 128 GiB! Dacă o faceți, datele de pe disc (indiferent dacă e un volum VeraCrypt sau nu) ar putea fi corupte. Rețineți că aceasta este o limitare a sistemului Windows, nu o eroare din VeraCrypt.\n\nPentru a activa suportul LBA 48-biți, adăugați valoarea registrului „EnableBigLba” în cheia registrului HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\atapi\\Parameters și setați-o la 1.\n\nPentru mai multe informații, consultați http://support.microsoft.com/kb/305098</entry>
     <entry lang="ro" key="VOLUME_TOO_LARGE_FOR_FAT32">Eroare: fișierele mai mari de 4 GiB nu pot fi stocate pe un sistem de fișiere FAT32. Prin urmare, volumele VeraCrypt amplasate în fișiere (containere) stocate pe un sistem de fișiere FAT32 nu pot fi mai mari de 4 GiB.\n\nDacă aveți nevoie de un volum mai mare, creați-l pe un sistem de fișiere NTFS (sau, dacă utilizați Windows Vista SP1 sau ulterior, pe un sistem de fișiere exFAT) sau, în loc să creați un volum tip fișier, criptați întreaga partiție sau disc.</entry>
-    <entry lang="ro" key="VOLUME_TOO_LARGE_FOR_WINXP">Avertizare: Windows XP nu suportă fișiere mai mari de 2048 GiB (va raporta eroarea „Not enough storage is available”). Prin urmare, nu puteți crea un volum VeraCrypt tip fișier (container) mai mare de 2048 GiB îm Windows XP.\n\nRețineți că încă e posibil să criptați întregul disc sau să creați un volum VeraCrypt tip-partiție mai mare de 2048 GiB în Windows XP.</entry>
+    <entry lang="ro" key="VOLUME_TOO_LARGE_FOR_WINXP">Avertizare: Windows XP nu suportă fișiere mai mari de 2048 GiB (va raporta eroarea „Not enough storage is available”). Prin urmare, nu puteți crea un volum VeraCrypt tip fișier (container) mai mare de 2048 GiB în Windows XP.\n\nRețineți că încă e posibil să criptați întregul disc sau să creați un volum VeraCrypt tip-partiție mai mare de 2048 GiB în Windows XP.</entry>
     <entry lang="ro" key="FREE_SPACE_FOR_WRITING_TO_OUTER_VOLUME">AVERTIZARE: Dacă doriți să puteți adăuga mai multe date/fișiere pe volumul exterior în viitor, ar trebui să luați în considerare alegerea unei dimensiuni mai mici pentru volumul ascuns.\n\nSigur doriți să continuați cu dimensiunea specificată?</entry>
     <entry lang="ro" key="NO_VOLUME_SELECTED">Nu ați selectat volumul.\n\nApăsați pe «Selectare partiție» sau «Selectare fișier» pentru a selecta un volum VeraCrypt.</entry>
     <entry lang="ro" key="NO_SYSENC_PARTITION_SELECTED">Nu ați selectat partiția.\n\nApăsați pe «Selectare partiție» pentru a selecta o partiție demontată care în mod normal necesită autentificare la pornire (de exemplu, o partiție localizată pe discul sistem criptat a unui alt sistem de operare, care nu rulează sau partiția sistem criptată a altui sistem de operare).\n\nNotă: Partiția selectată va fi montată ca și un volum normal VeraCrypt fără autentificare la pornire. Aceasta este util de ex. pentru operații de reparare sau creare copii de rezervă.</entry>
@@ -1029,10 +1029,10 @@
     <entry lang="ro" key="MOUNTED_VOLUMES_UNMOUNTED">Volumele VeraCrypt au fost demontate.</entry>
     <entry lang="ro" key="VOLUMES_UNMOUNTED_CACHE_WIPED">Volumele VeraCrypt au fost demontate și parola memorată a fost eliminată.</entry>
     <entry lang="ro" key="SUCCESSFULLY_UNMOUNTED">Demontare reușită.</entry>
-    <entry lang="ro" key="CONFIRM_BACKGROUND_TASK_DISABLED">AVERTIZARE: dacă este dezactivată opțiunea „Pornire VeraCrypt în fundal”, vor fi dezactivate următoarele funcții:\n\n1) Scurtăturile\n2) Autodemontarea (de ex. după deautentificare, eliminarea bruscă a unităților gazdă, expirare timp etc.)\n3) Automontare toate favorite\n4) Notificări (de ex., când este împiedicată distrugerea volumelor ascunse)\n5) Pictograma sistem\n\nNotă: Puteți opri programul din fundal oricând, apăsând cu clic dreapta pe pictograma sistem VeraCrypt și selectând „Ieșire”.\n\nSigur doriți să dezactivați permanent pornirea VeraCrypt în fundal?</entry>
-    <entry lang="ro" key="CONFIRM_NO_FORCED_AUTOUNMOUNT">AVERTIZARE: dacă această opțiune este dezactivată, volumele conținând fișiere/foldere deschise NU vor putea fi autodemontate.\n\nSigur doriți să dezactivați această opțiune?</entry>
-    <entry lang="ro" key="WARN_PREF_AUTO_UNMOUNT">AVERTIZARE: volumele conținând fișiere/foldere deschise NU vor putea fi autodemontate.\n\nPentru a împiedica aceasta, activați următoarele opțiuni din această fereastră: „Forțare autodemontare chiar dacă volumul conține fișiere sau foldere deschise”</entry>
-    <entry lang="ro" key="WARN_PREF_AUTO_UNMOUNT_ON_POWER">AVERTIZARE: când bateria sistemului este redusă, Windows poate omite trimiterea mesajelor potrivite pentru executarea aplicațiilor când computerul intră în modul de salvare a energiei. Prin urmare, VeraCrypt poate eșua autodemontarea volumelor în astfel de cazuri.</entry>
+    <entry lang="ro" key="CONFIRM_BACKGROUND_TASK_DISABLED">AVERTIZARE: dacă este dezactivată opțiunea „Pornire VeraCrypt în fundal”, vor fi dezactivate următoarele funcții:\n\n1) Scurtăturile\n2) Autodemontarea (de ex. după deconectare, eliminarea bruscă a unităților gazdă, expirare timp etc.)\n3) Automontare toate favorite\n4) Notificări (de ex., când este împiedicată distrugerea volumelor ascunse)\n5) Pictograma sistem\n\nNotă: Puteți opri programul din fundal oricând, apăsând cu clic dreapta pe pictograma sistem VeraCrypt și selectând „Ieșire”.\n\nSigur doriți să dezactivați permanent pornirea VeraCrypt în fundal?</entry>
+    <entry lang="ro" key="CONFIRM_NO_FORCED_AUTOUNMOUNT">AVERTIZARE: dacă această opțiune este dezactivată, volumele conținând fișiere/foldere deschise NU vor putea fi demontate automat.\n\nSigur doriți să dezactivați această opțiune?</entry>
+    <entry lang="ro" key="WARN_PREF_AUTO_UNMOUNT">AVERTIZARE: volumele conținând fișiere/foldere deschise NU vor putea fi demontate automat.\n\nPentru a împiedica aceasta, activați următoarele opțiuni din această fereastră: „Forțare autodemontare chiar dacă volumul conține fișiere sau foldere deschise”</entry>
+    <entry lang="ro" key="WARN_PREF_AUTO_UNMOUNT_ON_POWER">AVERTIZARE: când bateria sistemului este redusă, Windows poate omite trimiterea mesajelor potrivite pentru executarea aplicațiilor când computerul intră în modul de salvare a energiei. Prin urmare, VeraCrypt poate eșua demontarea automată a volumelor în astfel de cazuri.</entry>
     <entry lang="ro" key="NONSYS_INPLACE_ENC_RESUME_PROMPT">Ați programat procesul de criptare a partiției/volumului. Procesul nu a fost încă completat.\n\nDoriți să reluați procesul acum?</entry>
     <entry lang="ro" key="SYSTEM_ENCRYPTION_RESUME_PROMPT">Ați programat procesul de criptare sau decriptare a partiției/discului sistem. Procesul nu a fost încă completat.\n\nDoriți să porniți (reluați) procesul acum?</entry>
     <entry lang="ro" key="ASK_NONSYS_INPLACE_ENC_NOTIFICATION_REMOVAL">Doriți să vi se solicite dacă doriți să reluați procesul programat de criptare a partițiilor/volumelor non-sistem?</entry>
@@ -1040,7 +1040,7 @@
     <entry lang="ro" key="DO_NOT_PROMPT_ME">Nu, nu mă mai întreba</entry>
     <entry lang="ro" key="NONSYS_INPLACE_ENC_NOTIFICATION_REMOVAL_NOTE">IMPORTANT: puteți relua procesul de criptare a oricărei partiții/volum non-sistem selectând: „Volume” > „Reluare proces întrerupt” din bara de meniu a ferestrei principale VeraCrypt.</entry>
     <entry lang="ro" key="SYSTEM_ENCRYPTION_SCHEDULED_BUT_PBA_FAILED">Ați programat procesul de criptare sau decriptare a partiției/discului sistem. Totuși, autentificarea la pornire a eșuat (sau a fost evitată).\n\nNotă: Dacă ați decriptat partiția/discul sistem în mediul de autentificare la pornire, va trebui să finalizați procesul selectând „Sistem” > „Decriptare permanentă disc/partiție sistem” din bara de meniu a ferestrei principale VeraCrypt.</entry>
-    <entry lang="ro" key="CONFIRM_EXIT">AVERTIZARE: dacă VeraCrypt se închide acum, următoarele funcții vor fi dezactivate:\n\n1) Scurtăturile\n2) Autodemontarea (de ex. după reautentificare, eliminarea bruscă a unității gazdă, expirare timp etc.)\n3) Automontare toate favorite\n4) Notificări (de ex., când este împiedicată distrugerea volumelor ascunse)\n\nNotă: Dacă nu doriți ca VeraCrypt să ruleze în fundal, dezactivați opțiunea „Pornire VeraCrypt în fundal” din meniul „Preferințe” (și, dacă e necesar, dezactivați „Pornire VeraCrypt în fundal” din secțiunea „Acțiuni de executat după intrarea în Windows”, din fereastra de „Preferințe”).\n\nSigur doriți să închideți VeraCrypt?</entry>
+    <entry lang="ro" key="CONFIRM_EXIT">AVERTIZARE: dacă VeraCrypt se închide acum, următoarele funcții vor fi dezactivate:\n\n1) Scurtăturile\n2) Autodemontarea (de ex. după reautentificare, eliminarea bruscă a unității gazdă, expirare timp etc.)\n3) Automontare toate favoritele\n4) Notificări (de ex., când este împiedicată distrugerea volumelor ascunse)\n\nNotă: Dacă nu doriți ca VeraCrypt să ruleze în fundal, dezactivați opțiunea „Pornire VeraCrypt în fundal” din meniul „Preferințe” (și, dacă e necesar, dezactivați „Pornire VeraCrypt în fundal” din secțiunea „Acțiuni de executat după intrarea în Windows”, din fereastra de „Preferințe”).\n\nSigur doriți să închideți VeraCrypt?</entry>
     <entry lang="ro" key="CONFIRM_EXIT_UNIVERSAL">Ieșire?</entry>
     <entry lang="ro" key="CHOOSE_ENCRYPT_OR_DECRYPT">VeraCrypt nu are destule informații pentru a decide dacă trebuie să cripteze sau să decripteze.</entry>
     <entry lang="ro" key="CHOOSE_ENCRYPT_OR_DECRYPT_FINALIZE_DECRYPT_NOTE">VeraCrypt nu are destule informații pentru a decide dacă trebuie să cripteze sau să decripteze.\n\nNotă: dacă ați decriptat partiția/discul sistem în mediul de autentificare la pornire, ar trebui să finalizați procesul apăsând pe «Decriptare».</entry>
@@ -1060,12 +1060,12 @@
     <entry lang="ro" key="CHECKING_FS">Verificare sistem de fișiere de pe volumul VeraCrypt montat ca %s...</entry>
     <entry lang="ro" key="REPAIRING_FS">Încercare reparare sistem de fișiere de pe volumul VeraCrypt montat ca %s...</entry>
     <entry lang="ro" key="WARN_64_BIT_BLOCK_CIPHER">Avertizare: Acest volum este criptat cu un algoritm cu bloc de 64 biți.\n\nToți algoritmii de criptare cu blocuri de 64 biți (de ex., Blowfish, CAST-128, sau Triple DES) sunt dezaprobați. Va fi posibilă montarea acestui volum utilizând versiuni viitoare ale VeraCrypt. Totuși, nu vor fi îmbunătățiri ale implementărilor acestor algoritmi de criptare depășiți. Vă recomandăm să creați un volum criptat VeraCrypt cu un algoritm cu bloc de 128 biți (de ex., AES, Serpent, Twofish etc.) și să mutați toate fișierele de pe acest volum pe noul volum creat.</entry>
-    <entry lang="ro" key="SYS_AUTOMOUNT_DISABLED">Acest sistem nu este configurat să monteze automat noile volume. Ar putea fi imposibilă montarea volumelor VeraCrypt amplasate pe unități. Automontarea poate fi activată prin executarea următoarei comenzi și repornirea sistemului.\n\nmountvol.exe  /E</entry>
+    <entry lang="ro" key="SYS_AUTOMOUNT_DISABLED">Acest sistem nu este configurat să monteze automat noile volume. Ar putea fi imposibilă montarea volumelor VeraCrypt amplasate pe unități. Montarea automată poate fi activată prin executarea următoarei comenzi și repornirea sistemului.\n\nmountvol.exe /E</entry>
     <entry lang="ro" key="SYS_ASSIGN_DRIVE_LETTER">Atribuiți o literă de volum partiției/discului înainte de a continua („Control Panel” > „System and Maintenance” > „Administrative Tools” - „Create and format hard disc partitions”).\n\nRețineți că este o cerință a sistemului de operare.</entry>
     <entry lang="ro" key="MOUNT_TC_VOLUME">Montare volum VeraCrypt</entry>
     <entry lang="ro" key="UNMOUNT_ALL_TC_VOLUMES">Demontare toate volumele VeraCrypt</entry>
     <entry lang="ro" key="UAC_INIT_ERROR">VeraCrypt a eșuat în obținerea drepturilor de administrator.</entry>
-    <entry lang="ro" key="ERR_ACCESS_DENIED">Accesul a fost refuzat de sistemul de operare.\n\nPosibile cauze: sistemul de operare trebuie să aibe drepturi de citire/scriere (sau drepturi de administrator) pentru anumite foldere, fișiere sau unități, pentru a vă putea permite  să citiți și să scrieți date în/din ele. În mod normal, un utilizator fără drepturi de administrare are dreptul de a crea, citi și modifica fișiere în folderul său de documente.</entry>
+    <entry lang="ro" key="ERR_ACCESS_DENIED">Accesul a fost refuzat de sistemul de operare.\n\nPosibile cauze: sistemul de operare trebuie să aibă drepturi de citire/scriere (sau drepturi de administrator) pentru anumite foldere, fișiere sau unități, pentru a vă putea permite  să citiți și să scrieți date în/din ele. În mod normal, un utilizator fără drepturi de administrare are dreptul de a crea, citi și modifica fișiere în folderul său de documente.</entry>
     <entry lang="ro" key="SECTOR_SIZE_UNSUPPORTED">Eroare: discul utilizează o dimensiune a sectoarelor nesuportate.\n\nÎn acest moment nu este posibilă crearea volumelor amplasate pe partiții/unități pe discuri care au sectoare mai mari de 4096 de baiți. Totuși, puteți crea volume amplasate în fișiere (containere) pe astfel de unități.</entry>
     <entry lang="ro" key="SYSENC_UNSUPPORTED_SECTOR_SIZE_BIOS">În acest moment nu este posibilă criptarea sistemului instalat pe un disc care are altă dimensiune a sectoarelor decât 512 baiți.</entry>
     <entry lang="ro" key="NO_SPACE_FOR_BOOT_LOADER">Programul de pornire VeraCrypt necesită cel puțin 32 KiB de spațiu liber la începutul unității sistem (Programul de pornire VeraCrypt trebuie să fie stocat acolo). Din păcate, acest disc nu îndeplinește această condiție.\n\nNU raportați aceasta ca o eroare/problemă în VeraCrypt. Pentru a rezolva această problemă, va trebui să repartiționați discul și lăsați primii 32 KiB ca spațiu liber (în multe cazuri, va trebui să ștergeți și să recreați prima partiție). Vă recomandăm să utilizați managerul de partiții Microsoft care este disponibil, de ex., când instalați Windows.</entry>
@@ -1086,19 +1086,19 @@
     <entry lang="ro" key="SYS_PARTITION_OR_DRIVE_APPEARS_FULLY_ENCRYPTED">Acest disc/partiție pare să fie complet criptat(ă).</entry>
     <entry lang="ro" key="SYSENC_UNSUPPORTED_FOR_DYNAMIC_DISK">VeraCrypt nu suportă criptarea unui disc sistem care a fost convertit în disc dinamic.</entry>
     <entry lang="ro" key="WDE_UNSUPPORTED_FOR_EXTENDED_PARTITIONS">Discul sistem conține partiții extinse (logice).\n\nPuteți cripta un disc sistem întreg conținând partiții extinse (logice) numai pe Windows Vista și versiuni ulterioare de Windows. În Windows XP, puteți cripta un disc sistem întreg cu condiția să conțină numai partiții primare.\n\nNotă: în schimb, puteți cripta partiția sistem în loc de întregul disc sistem (și, în plus, puteți crea volume VeraCrypt amplasate pe partiții pe orice partiție non-sistem de pe disc).</entry>
-    <entry lang="ro" key="WDE_EXTENDED_PARTITIONS_WARNING">AVERTIZARE: deoarece acum rulați Windows XP/2003, după ce veți începe criptarea unității, va trebui să NU mai creați partiții extinse (logice) pe aceasta (veți putea crea numai partiții primare). Orice partiție extinsă (logică) de pe disc va fi inaccesibiă după ce începeți criptarea (discul nu conține momentan nici o astfel de partiție).\n\nNotă: dacă această limitare nu este acceptabilă, puteți să reveniți și să alegeți să criptați numai partiția sistem în loc de întregul disc (și, în plus, puteți crea volume VeraCrypt amplasate pe partiții pe orice partiție non-sistem de pe disc).\n\nAlternativ, dacă această limitare nu este acceptabilă, puteți lua în considerare actualizarea la Windows Vista sau o versiune ulterioară de Windows (puteți cripta un disc sistem întreg conținând partiții extinse/logice numai în Windows Vista sau ulterior).</entry>
-    <entry lang="ro" key="SYSDRIVE_NON_STANDARD_PARTITIONS">Acest disc sistem conține o partiție nonstandard.\n\nDacă nu folosiți un calculator portabil, discul sistem probabil conține o partiție specială de recuperare. După ce întreagul disc sistem este criptat (inclusiv orice partiție de recuperare), sistemul ar putea să nu mai pornească dacă calculatorul folosesște un BIOS proiectat necorespunzător. Va fi de altfel imposibil să accesați partiția de recuperare până când discul sistem nu este decriptat. Prin urmare, vă recomandăm să criptați numai partiția sistem.</entry>
+    <entry lang="ro" key="WDE_EXTENDED_PARTITIONS_WARNING">AVERTIZARE: deoarece acum rulați Windows XP/2003, după ce veți începe criptarea unității, va trebui să NU mai creați partiții extinse (logice) pe aceasta (veți putea crea numai partiții primare). Orice partiție extinsă (logică) de pe disc va fi inaccesibilă după ce începeți criptarea (discul nu conține momentan nici o astfel de partiție).\n\nNotă: dacă această limitare nu este acceptabilă, puteți să reveniți și să alegeți să criptați numai partiția sistem în loc de întregul disc (și, în plus, puteți crea volume VeraCrypt amplasate pe partiții pe orice partiție non-sistem de pe disc).\n\nAlternativ, dacă această limitare nu este acceptabilă, puteți lua în considerare actualizarea la Windows Vista sau o versiune ulterioară de Windows (puteți cripta un disc sistem întreg conținând partiții extinse/logice numai în Windows Vista sau ulterior).</entry>
+    <entry lang="ro" key="SYSDRIVE_NON_STANDARD_PARTITIONS">Acest disc sistem conține o partiție nonstandard.\n\nDacă nu folosiți un calculator portabil, discul sistem probabil conține o partiție specială de recuperare. După ce întregul disc sistem este criptat (inclusiv orice partiție de recuperare), sistemul ar putea să nu mai pornească dacă calculatorul folosește un BIOS proiectat necorespunzător. Va fi de altfel imposibil să accesați partiția de recuperare până când discul sistem nu este decriptat. Prin urmare, vă recomandăm să criptați numai partiția sistem.</entry>
     <entry lang="ro" key="ASK_ENCRYPT_PARTITION_INSTEAD_OF_DRIVE">Doriți să criptați partiția sistem în loc de întregul disc?\n\nPuteți crea volume VeraCrypt amplasate pe partiții pe orice partiție non-sistem de pe disc (pe lângă criptarea partiției sistem).</entry>
     <entry lang="ro" key="WHOLE_SYC_DEVICE_RECOM">Deoarece discul sistem conține numai o partiție care ocupă întregul disc, este de preferat (mult mai sigur) să criptați întregul disc, inclusiv spațiul liber care, de obicei, înconjoară o astfel de partiție.\n\nDoriți să criptați întregul disc sistem?</entry>
     <entry lang="ro" key="TEMP_NOT_ON_SYS_PARTITION">Acest sistem este configurat să stocheze fișierele temporare pe o partiție non-sistem.\n\nFișierele temporare pot fi stocate numai pe partiția sistem.</entry>
-    <entry lang="ro" key="USER_PROFILE_NOT_ON_SYS_PARTITION">Fișierele profilelor utilizatorilor nu sunt stocate pe partiția sistem.\n\nFișierele profilelor utilizatorilor pot fi stocate numai pe partiția sistem.</entry>
+    <entry lang="ro" key="USER_PROFILE_NOT_ON_SYS_PARTITION">Fișierele profilurilor utilizatorilor nu sunt stocate pe partiția sistem.\n\nFișierele profilurilor utilizatorilor pot fi stocate numai pe partiția sistem.</entry>
     <entry lang="ro" key="PAGING_FILE_NOT_ON_SYS_PARTITION">Există un fișier sau fișiere de paginare pe partiții non-sistem.\n\nFișierele de paginare pot fi stocate numai pe partiția sistem.</entry>
     <entry lang="ro" key="RESTRICT_PAGING_FILES_TO_SYS_PARTITION">Doriți să configurați Windows să creeze un fișier de paginare numai pe partiția sistem acum?\n\nRețineți că dacă apăsați pe «Da», calculatorul va fi repornit. Apoi lansați VeraCrypt și încercați să creați sistemul ascuns din nou.</entry>
-    <entry lang="ro" key="LEAKS_OUTSIDE_SYSPART_UNIVERSAL_EXPLANATION">Altfel, negarea plauzibilă a sistemului de operare ascuns poate fi serios afectată.\n\nNotă: dacă un adversar analizează conținutul unor astfel de fișiere (amplasate pe o partiție non-sistem), ar putea afla că ați utilizat acest asistent în modul de creare sistem ascuns (care ar putea indica existența unui sistem de operare ascuns în calculator). În plus, astfel de fișiere stocate pe partiția sistem vor fi șterse în sigurață de către VeraCrypt în timpul procesului de creare a sistemului de operare ascuns.</entry>
+    <entry lang="ro" key="LEAKS_OUTSIDE_SYSPART_UNIVERSAL_EXPLANATION">Altfel, negarea plauzibilă a sistemului de operare ascuns poate fi serios afectată.\n\nNotă: dacă un adversar analizează conținutul unor astfel de fișiere (amplasate pe o partiție non-sistem), ar putea afla că ați utilizat acest asistent în modul de creare sistem ascuns (care ar putea indica existența unui sistem de operare ascuns în calculator). În plus, astfel de fișiere stocate pe partiția sistem vor fi șterse în siguranță de către VeraCrypt în timpul procesului de creare a sistemului de operare ascuns.</entry>
     <entry lang="ro" key="DECOY_OS_REINSTALL_WARNING">AVERTIZARE: în timpul procesului de creare a sistemului de operare ascuns, va trebui să reinstalați sistemul de operare curent (pentru a crea în siguranță un sistem momeală).\n\nNotă: sistemul de operare ce rulează acum și întreg conținutul partiției sistem va fi copiat pe volumul ascuns (pentru a crea sistemul ascuns).\n\n\nSigur veți putea instala din nou Windows folosind un mediu de instalare Windows (sau folosind o partiție cu copia de rezervă)?</entry>
-    <entry lang="ro" key="DECOY_OS_REQUIREMENTS">Din motive de securitate, dacă sistemul de operare curent necesită activarea, ar trebui activat înainte de a continua. Rețineți că sistemul de operare ascuns va fi creat prin copierea conținutului partiției sistem într-un volum ascuns (astfel că, dacă acest sistem de operare nu este activat, atunci nici sistemul de operare ascuns nu va fi activat). Pentru mai multe infomații, consultați secțiunea „Security Requirements and Precautions Pertaining to Hidden Volumes” în „Ghidul de utilizare VeraCrypt”.\n\nImportant: înainte de a continua, asigurați-vă că ați citit secțiunea „Security Requirements and Precautions Pertaining to Hidden Volumes” din „Ghidul de utilizare VeraCrypt”.\n\n\nSistemul de operare curent îndeplinește condiția amintită mai sus?</entry>
+    <entry lang="ro" key="DECOY_OS_REQUIREMENTS">Din motive de securitate, dacă sistemul de operare curent necesită activarea, ar trebui activat înainte de a continua. Rețineți că sistemul de operare ascuns va fi creat prin copierea conținutului partiției sistem într-un volum ascuns (astfel că, dacă acest sistem de operare nu este activat, atunci nici sistemul de operare ascuns nu va fi activat). Pentru mai multe informații, consultați secțiunea „Security Requirements and Precautions Pertaining to Hidden Volumes” în „Ghidul de utilizare VeraCrypt”.\n\nImportant: înainte de a continua, asigurați-vă că ați citit secțiunea „Security Requirements and Precautions Pertaining to Hidden Volumes” din „Ghidul de utilizare VeraCrypt”.\n\n\nSistemul de operare curent îndeplinește condiția amintită mai sus?</entry>
     <entry lang="ro" key="CONFIRM_HIDDEN_OS_EXTRA_BOOT_PARTITION">Acest sistem folosește o partiție suplimentară pentru pornire. VeraCrypt nu suportă hibernarea pe sistemele de operare ascunse care folosesc o partiție suplimentară pentru pornire (sistemele momeală pot intra in hibernare fără probleme).\n\nPartiția de pornire va fi partajată atât pentru sistemul momeală cât și pentru cel ascuns. Prin urmare, pentru a împiedica divulgările de date și probleme la revenirea din hibernare, VeraCrypt trebuie să împiedice sistemul ascuns să scrie în partiția de pornire partajată și să intre în hibernare.\n\n\nDoriți să continuați? Dacă selectați «Nu», vor fi afișate instrucțiuni pentru eliminarea partiției de pornire suplimentare.</entry>
-    <entry lang="ro" key="EXTRA_BOOT_PARTITION_REMOVAL_INSTRUCTIONS">\nPartiția de pornire suplimentară poate fi ștearsă înainte de instalarea Windows. Pentru aceasta, executați pașii următori: \n\n1) Porniți discul de instalare Windows.\n\n2) În ecranul de instalare Windows, apăsați pe „Install now” > „Custom (advanced)”.\n\n3) Apăsați pe „Drive Options”.\n\n4) Selectați partiția sistemului principal și ștergeți-o apăsând pe „Delete” și apoi «OK».\n\n5) Selectați partiția „System Reserved”, apăsând pe „Extend” și măriți dimensiunea acesteia astfel încât să se poată instala sistemul de operare pe ea.\n\n6) Apăsați pe „Apply” și apoi «OK».\n\n7) Instalați Windows pe partiția „System Reserved”.\n\n\nDacă un atacator v-ar întreba de ce ați șters partiția suplimentară de pornire, ați putea raspunde că ați vrut să împiedicați orice divulgare de date posibilă la partiția de pornire necriptată.\n\nNotă: puteți tipări acest text apăsând butonul «Tipărire» de mai jos. Dacă ați salvat o copie a acestui text sau l-ați tipărit (ceea ce vă recomandăm cu insistență, cu excepția cazului în care imprimanta stochează copiile documentelor tipărite pe un hard disc intern), ar trebui să distrugeți orice copie a sa după ștergerea partiției suplimentare (altfel, dacă o astfel de copie este găsită, ar putea da indicii că există un sistem de operare ascuns pe acest calculator).</entry>
+    <entry lang="ro" key="EXTRA_BOOT_PARTITION_REMOVAL_INSTRUCTIONS">\nPartiția de pornire suplimentară poate fi ștearsă înainte de instalarea Windows. Pentru aceasta, executați pașii următori: \n\n1) Porniți discul de instalare Windows.\n\n2) În ecranul de instalare Windows, apăsați pe „Install now” > „Custom (advanced)”.\n\n3) Apăsați pe „Drive Options”.\n\n4) Selectați partiția sistemului principal și ștergeți-o apăsând pe „Delete” și apoi «OK».\n\n5) Selectați partiția „System Reserved”, apăsând pe „Extend” și măriți dimensiunea acesteia astfel încât să se poată instala sistemul de operare pe ea.\n\n6) Apăsați pe „Apply” și apoi «OK».\n\n7) Instalați Windows pe partiția „System Reserved”.\n\n\nDacă un atacator v-ar întreba de ce ați șters partiția suplimentară de pornire, ați putea răspunde că ați vrut să împiedicați orice divulgare de date posibilă la partiția de pornire necriptată.\n\nNotă: puteți tipări acest text apăsând butonul «Tipărire» de mai jos. Dacă ați salvat o copie a acestui text sau l-ați tipărit (ceea ce vă recomandăm cu insistență, cu excepția cazului în care imprimanta stochează copiile documentelor tipărite pe un hard disc intern), ar trebui să distrugeți orice copie a sa după ștergerea partiției suplimentare (altfel, dacă o astfel de copie este găsită, ar putea da indicii că există un sistem de operare ascuns pe acest calculator).</entry>
     <entry lang="ro" key="GAP_BETWEEN_SYS_AND_HIDDEN_OS_PARTITION">Avertizare: există spațiu nealocat între partiția sistem și prima partiție de după aceasta. După ce veți crea sistemul de operare ascuns, nu ar trebui să mai creați vreo partiție în acel spațiu nealocat. Altfel, sistemul de operare ascuns nu va putea să pornească (până când veți șterge noua partiție astfel creată).</entry>
     <entry lang="ro" key="ALGO_NOT_SUPPORTED_FOR_SYS_ENCRYPTION">Acest algoritm nu este momentan suportat pentru criptarea partiției sistem.</entry>
     <entry lang="ro" key="ALGO_NOT_SUPPORTED_FOR_TRUECRYPT_MODE">Acest algoritm nu este suportat pentru modul TrueCrypt.</entry>
@@ -1122,25 +1122,25 @@
     <entry lang="ro" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Nu s-a putut porni pretestul de criptare a sistemului.</entry>
     <entry lang="ro" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Nu s-a putut inițializa procesul de creare a sistemului de operare ascuns.</entry>
     <entry lang="ro" key="WIPE_MODE_TITLE">Mod ștergere</entry>
-    <entry lang="ro" key="INPLACE_ENC_WIPE_MODE_INFO">Pe unele medii de stocare, când datele sunt suprascrise cu alte date, este posibilă recuperarea datelor suprascrise folosind tehnici ca microscopia forțelor magnetice. Aceasta se aplică și datelor care au fost înlocuite cu echivalentul lor criptat (care are loc atunci când VeraCrypt criptează inițial o partiție sau disc necriptat). Conform unor studii și publicații guvernamentale, recuperarea datelor suprascrise poate fi împiedicată (sau făcută foarte dificilă) prin suprascrierea de date aleatoare sau anumite date non-aleatoare de un anumit număr de ori. Prin urmare, dacă credeți că un adversar ar putea folosi astfel de tehnici pentru a recupera datele pe care inteționați să le criptați, ar trebui să alegeți unul din modurile de ștergere (datele existente NU vor fi pierdute). Rețineți că ștergerea NU va fi executată după criptarea completă a partiției/discului. Când partiția/discul este complet criptată, nu se mai scriu date necriptate pe ea. Orice date care vor fi scrise, vor fi mai întâi criptate din mers în memorie și doar apoi datele (criptate) vor fi scrise pe disc.</entry>
-    <entry lang="ro" key="WIPE_MODE_INFO">Pe unele medii de stocare, când datele sunt suprascrise cu alte date, (de ex. când datele sunt șterse), este posibilă recuperarea datelor suprascrise folosind tehnici ca microscopia forțelor magnetice. Conform unor studii și publicații guvernamentale, recuperarea datelor suprascrise poate fi împiedicată (sau făcută foarte dificilă) prin suprascrierea de date aleatoare sau anumite date non-aleatoare de un anumit număr de ori. Prin urmare, dacă credeți că un adversar ar putea folosi astfel de tehnici pentru a recupera datele pe care intenționați să le ștergeți, ar trebui să alegeți unul din modurile de ștergere în pași multipli.\n\nNotă: Cu cât alegeți mai mulți pași de ștergere, cu atât mai mult va dura procesul de ștergere a datelor.</entry>
+    <entry lang="ro" key="INPLACE_ENC_WIPE_MODE_INFO">Pe unele medii de stocare, când datele sunt suprascrise cu alte date, este posibilă recuperarea datelor suprascrise folosind tehnici ca microscopia forțelor magnetice. Aceasta se aplică și datelor care au fost înlocuite cu echivalentul lor criptat (care are loc atunci când VeraCrypt criptează inițial o partiție sau disc necriptat). Conform unor studii și publicații guvernamentale, recuperarea datelor suprascrise poate fi împiedicată (sau făcută foarte dificilă) prin suprascrierea de date aleatorii sau anumite date non-aleatorii de un anumit număr de ori. Prin urmare, dacă credeți că un adversar ar putea folosi astfel de tehnici pentru a recupera datele pe care intenționați să le criptați, ar trebui să alegeți unul din modurile de ștergere (datele existente NU vor fi pierdute). Rețineți că ștergerea NU va fi executată după criptarea completă a partiției/discului. Când partiția/discul este complet criptată, nu se mai scriu date necriptate pe ea. Orice date care vor fi scrise, vor fi mai întâi criptate din mers în memorie și doar apoi datele (criptate) vor fi scrise pe disc.</entry>
+    <entry lang="ro" key="WIPE_MODE_INFO">Pe unele medii de stocare, când datele sunt suprascrise cu alte date, (de ex. când datele sunt șterse), este posibilă recuperarea datelor suprascrise folosind tehnici ca microscopia forțelor magnetice. Conform unor studii și publicații guvernamentale, recuperarea datelor suprascrise poate fi împiedicată (sau făcută foarte dificilă) prin suprascrierea de date aleatorii sau anumite date non-aleatorii de un anumit număr de ori. Prin urmare, dacă credeți că un adversar ar putea folosi astfel de tehnici pentru a recupera datele pe care intenționați să le ștergeți, ar trebui să alegeți unul din modurile de ștergere în pași multipli.\n\nNotă: Cu cât alegeți mai mulți pași de ștergere, cu atât mai mult va dura procesul de ștergere a datelor.</entry>
     <entry lang="ro" key="DEVICE_WIPE_PAGE_TITLE">Ștergere</entry>
     <entry lang="ro" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNotă: puteți întrerupe procesul de ștergere, să opriți calculatorul, să porniți sistemul ascuns din nou și să reluați procesul (acest asistent va fi lansat automat). Totuși, dacă îl întrerupeți, întreg procesul de ștergere va trebui să pornească de la început.</entry>
     <entry lang="ro" key="DEVICE_WIPE_PAGE_INFO">\n\nNotă: dacă opriți procesul de ștergere și apoi încercați să-l reluați, întreg procesul de ștergere va trebui să pornească de la început.</entry>
     <entry lang="ro" key="CONFIRM_WIPE_ABORT">Doriți să opriți procesul de ștergere?</entry>
     <entry lang="ro" key="CONFIRM_WIPE_START">Avertizare: întreg conținutul discului /partiției selectat(ă) va fi șters și pierdut.</entry>
     <entry lang="ro" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">Întreg conținutul partiției unde se află sistemul de operare original va fi șters.\n\nNotă: întreg conținutul partiției ce va fi șters a fost copiat pe partiția sistemului ascuns.</entry>
-    <entry lang="ro" key="WIPE_MODE_WARN">AVERTIZARE: dacă alegeți de ex. mod ștergere în 3-pași, timpul necesar criptării discului/partiției va fi de până la 4 ori mai mare. La fel, dacă alegeți modul de ștergere în 35-pași, va dura de până la 36 de ori mai mult (s-ar putea să dureze chiar câteva săptămâni).\n\nTotuși, ștergerea NU se va efectua după criptarea completă a discului/partiției. Când discul/partiția este complet criptat(ă), nu se mai scriu date necriptate. Orice date care vor fi scrise, vor fi mai întâi criptate din mers în memorie și doar apoi datele (criptate) vor fi scrise pe disc (deci perfomanța NU va fi afectată).\n\nSigur doriți să utilizați modul de ștergere?</entry>
+    <entry lang="ro" key="WIPE_MODE_WARN">AVERTIZARE: dacă alegeți de ex. mod ștergere în 3-pași, timpul necesar criptării discului/partiției va fi de până la 4 ori mai mare. La fel, dacă alegeți modul de ștergere în 35-pași, va dura de până la 36 de ori mai mult (s-ar putea să dureze chiar câteva săptămâni).\n\nTotuși, ștergerea NU se va efectua după criptarea completă a discului/partiției. Când discul/partiția este complet criptat(ă), nu se mai scriu date necriptate. Orice date care vor fi scrise, vor fi mai întâi criptate din mers în memorie și doar apoi datele (criptate) vor fi scrise pe disc (deci performanța NU va fi afectată).\n\nSigur doriți să utilizați modul de ștergere?</entry>
     <entry lang="ro" key="WIPE_MODE_NONE">Fără (cel mai rapid)</entry>
-    <entry lang="ro" key="WIPE_MODE_1_RAND">1-pas (date aleatoare)</entry>
+    <entry lang="ro" key="WIPE_MODE_1_RAND">1-pas (date aleatorii)</entry>
     <entry lang="ro" key="WIPE_MODE_3_DOD_5220">3-pași (US DoD 5220.22-M)</entry>
     <entry lang="ro" key="WIPE_MODE_7_DOD_5220">7-pași (US DoD 5220.22-M)</entry>
     <entry lang="ro" key="WIPE_MODE_35_GUTMANN">35-pași („Gutmann”)</entry>
     <entry lang="ro" key="WIPE_MODE_256">256-pași</entry>
     <entry lang="ro" key="SYS_MULTI_BOOT_MODE_TITLE">Număr sisteme de operare</entry>
     <entry lang="ro" key="MULTI_BOOT_FOR_ADVANCED_ONLY">AVERTIZARE: utilizatorii neexperimentați nu ar trebui să încerce criptarea sistemului Windows în configurații de pornire cu multiple sisteme de operare.\n\nContinuați?</entry>
-    <entry lang="ro" key="HIDDEN_OS_MULTI_BOOT">Când creați/utilizați un sistem de operare ascuns, VeraCrypt suportă configurații de pornire pentru mai multe sisteme de operare doar dacă sunt îndeplinite următoarele condiții:\n\n- Sistemul de operare actual trebuie să fie instalat pe discul de pornire, care nu trebuie să mai conțină vreun alt sistem de de operare.\n\n- Sistemele de operare instalate pe alte discuri nu trebuie să folosească programe de pornire care să fie pe același disc cu sistemul de operare actual instalat.\n\nSunt condițiile de mai sus îndeplinite?</entry>
-    <entry lang="ro" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt nu suportă această configurație de pornire de sisteme multiple când se crează/utilizează un sistem de operare ascuns.</entry>
+    <entry lang="ro" key="HIDDEN_OS_MULTI_BOOT">Când creați/utilizați un sistem de operare ascuns, VeraCrypt suportă configurații de pornire pentru mai multe sisteme de operare doar dacă sunt îndeplinite următoarele condiții:\n\n- Sistemul de operare actual trebuie să fie instalat pe discul de pornire, care nu trebuie să mai conțină vreun alt sistem de operare.\n\n- Sistemele de operare instalate pe alte discuri nu trebuie să folosească programe de pornire care să fie pe același disc cu sistemul de operare actual instalat.\n\nSunt condițiile de mai sus îndeplinite?</entry>
+    <entry lang="ro" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt nu suportă această configurație de pornire de sisteme multiple când se creează/utilizează un sistem de operare ascuns.</entry>
     <entry lang="ro" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Disc pornire</entry>
     <entry lang="ro" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Este sistemul curent de operare instalat pe discul de pornire?\n\nNotă: Uneori, Windows nu este instalat pe același disc unde este instalat programul de pornire Windows (partiția de pornire). Dacă acesta este cazul, atunci selectați «Nu»”.</entry>
     <entry lang="ro" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt nu suportă în acest moment criptarea unui sistem de operare care nu pornește de pe discul pe care este instalat.</entry>
@@ -1155,7 +1155,7 @@
     <entry lang="ro" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt nu suportă în acest moment configurațiile de sisteme multiple unde un program de pornire non-Windows este instalat în sectorul de pornire (MBR).\n\nSoluții posibile:\n\n- Dacă folosiți un program de pornire pentru a porni Windows și Linux, mutați programul de pornire (de obicei, GRUB) de pe sectorul de pornire MBR pe o partiție. Apoi porniți acest asistent din nou și criptați partiția/discul sistem. Rețineți că programul de pornire VeraCrypt va deveni principalul manager de pornire și vă va permite să lansați managerul de pornire original (de ex. GRUB) ca manager secundar (prin apăsarea tastei Esc în ecranul programului de pornire VeraCrypt) și astfel veți putea porni Linux.</entry>
     <entry lang="ro" key="WINDOWS_BOOT_LOADER_HINTS">Dacă sistemul de operare curent este instalat pe partiția de pornire, atunci, după ce îl veți cripta, va trebui să introduceți parola corectă chiar dacă doriți să porniți oricare alt sistem Windows necriptat (deoarece ele vor partaja un singur program de pornire/manager de încărcare Windows.\n\nDacă în schimb, sistemul de operare curent nu este instalat pe o partiție de pornire (sau dacă programul de pornire/managerul de pornire Windows nu este folosit și de un alt sistem de operare), atunci, după ce veți cripta acest sistem, nu va trebui să introduceți parola corectă pentru a porni alt sistem necriptat -- va trebui doar să apăsați tasta Esc pentru a porni sistemul necriptat (dacă sunt mai multe sisteme necriptate, va trebui de asemeni să alegeți care din ele să pornească din meniul managerului de pornire VeraCrypt).\n\nNotă: în mod normal, primul sistem Windows instalat este instalat pe partiția de pornire.</entry>
     <entry lang="ro" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Criptarea zonei protejate gazdă</entry>
-    <entry lang="ro" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">La sfârșitul multor discuri, există o zonă care este în mod normal ascunsă față de sistemul de operare (astfel de zone sunt cunoscute ca zone protejate gazdă). Totuși, unele programe pot citi și scrie date de la/în astfel de zone.\n\nATENȚIE: unii producători de calculatoare pot folosi astfel de zone pentru a stoca programe și date pentru RAID, recuperarea sistemului, setarea sistemului, diagnostic sau pentru alte scopuri. Dacă astfel de programe sau date trebuie să fie accesibile înainte de pornire, zona ascunsă NU ar trebui criptată (alegeți «Nu» mai sus).\n\nDoriți ca VeraCrypt să detectze și să cripteze astfel de zone ascunse (dacă există) de la sfârșitul discului sistem?</entry>
+    <entry lang="ro" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">La sfârșitul multor discuri, există o zonă care este în mod normal ascunsă față de sistemul de operare (astfel de zone sunt cunoscute ca zone protejate gazdă). Totuși, unele programe pot citi și scrie date de la/în astfel de zone.\n\nATENȚIE: unii producători de calculatoare pot folosi astfel de zone pentru a stoca programe și date pentru RAID, recuperarea sistemului, setarea sistemului, diagnostic sau pentru alte scopuri. Dacă astfel de programe sau date trebuie să fie accesibile înainte de pornire, zona ascunsă NU ar trebui criptată (alegeți «Nu» mai sus).\n\nDoriți ca VeraCrypt să detecteze și să cripteze astfel de zone ascunse (dacă există) de la sfârșitul discului sistem?</entry>
     <entry lang="ro" key="SYSENC_TYPE_PAGE_TITLE">Tip criptare sistem</entry>
     <entry lang="ro" key="SYSENC_NORMAL_TYPE_HELP">Selectați această opțiune numai dacă doriți să criptați partiția sistem sau întregul disc sistem.</entry>
     <entry lang="ro" key="SYSENC_HIDDEN_TYPE_HELP">S-ar putea ca cineva să vă forțeze să decriptați sistemul de operare. Sunt multe situații când nu puteți refuza să o faceți (de exemplu, datorită extorcării). Dacă selectați această opțiune, veți crea un sistem de operare ascuns a cărui existență ar trebui să fie imposibil de dovedit (cu condiția să fie urmate anumite reguli). Astfel, nu va trebui să decriptați sau să furnizați parola sistemului de operare ascuns. Pentru explicații detaliate, apăsați pe legătura web de mai jos.</entry>
@@ -1166,7 +1166,7 @@
     <entry lang="ro" key="SYSENC_DRIVE_ANALYSIS_INFO">Așteptați până când VeraCrypt detectează posibile sectoare ascunse la sfârșitul discului. Rețineți că ar putea dura mult timp până la finalizare.\n\nNotă: în cazuri foarte rare, pe unele calculatoare, sistemul poate să nu răspundă pe durata procesului de detectare. Dacă se întâmplă asta, reporniți calculatorul, porniți VeraCrypt, repetați pașii anteriori dar săriți peste procesul de detectare. Rețineți că această situație nu se datorează unei erori din VeraCrypt.</entry>
     <entry lang="ro" key="SYS_ENCRYPTION_SPAN_TITLE">Zona de criptat</entry>
     <entry lang="ro" key="SYS_ENCRYPTION_SPAN_WHOLE_SYS_DRIVE_HELP">Selectați această opțiune dacă doriți să criptați întregul disc pe care se află instalat actualul sistem Windows. Întregul disc, inclusiv toate partițiile sale, vor fi criptate cu excepția primei piste unde va fi stocat programul de pornire VeraCrypt. Oricine va dori să acceseze un sistem instalat pe disc sau fișiere stocate pe el, va trebui să introducă parola corectă de fiecare dată când sistemul pornește. Această opțiune nu poate fi utilizată pentru criptarea unui disc secundar sau disc extern dacă Windows nu este instalat pe el și nu pornește de pe el.</entry>
-    <entry lang="ro" key="COLLECTING_RANDOM_DATA_TITLE">Colectare date aleatoare</entry>
+    <entry lang="ro" key="COLLECTING_RANDOM_DATA_TITLE">Colectare date aleatorii</entry>
     <entry lang="ro" key="KEYS_GEN_TITLE">Chei generate</entry>
     <entry lang="ro" key="CD_BURNER_NOT_PRESENT">VeraCrypt nu a găsit vreo unitate de inscripționat CD/DVD conectată la calculator. VeraCrypt are nevoie de ea pentru a scrie pe un CD/DVD un Disc de Recuperare VeraCrypt care conține o copie de rezervă a cheilor de criptare, a programului de pornire VeraCrypt, programul de încărcare original al sistemului etc.\n\nVă recomandăm cu insistență să inscripționați un Disc de Recuperare VeraCrypt.</entry>
     <entry lang="ro" key="CD_BURNER_NOT_PRESENT_WILL_STORE_ISO">NU am unitate de inscripționat pe CD/DVD, dar voi stoca imaginea ISO a discului de recuperare pe o unitate portabilă (de ex. unitate de memorie USB).</entry>
@@ -1187,13 +1187,13 @@
     <entry lang="ro" key="SYS_ENCRYPTION_PRETEST_INFO2_PORTION_4">Rețineți că pașii anteriori NU funcționează dacă partiția/discul sistem este criptat (nimeni nu poate porni Windows sau accesa fișierele criptate de pe disc fără parola corectă chiar dacă se urmează pașii descriși anterior).\n\n\nRețineți că chiar dacă vă pierdeți Discul de Recuperare VeraCrypt și un atacator potențial îl găsește, acesta NU va putea decripta partiția sau discul sistem fără parola corectă.</entry>
     <entry lang="ro" key="SYS_ENCRYPTION_PRETEST_RESULT_TITLE">Pretestare completată</entry>
     <entry lang="ro" key="SYS_ENCRYPTION_PRETEST_RESULT_INFO">Pretestarea a fost finalizată cu succes.\n\nATENȚIE: dacă alimentarea cu curent este întreruptă în timpul procesului de criptare din mers a datelor sau dacă sistemul de operare se blochează datorită unor erori din programe sau componente hardware defecte în timp ce VeraCrypt criptează datele din mers, porțiuni din date vor fi corupte sau vor fi pierdute. Prin urmare, înainte de a începe criptarea, asigurați-vă că aveți copii de rezervă a fișierelor pe care doriți să le criptați. Dacă nu aveți, faceți o copie de rezervă acum (puteți apăsa pe «Amânare», efectuați copia de rezervă a fișierelor, apoi lansați din nou VeraCrypt oricând și selectați „Sistem” > „Reluare proces întrerupt” pentru a începe criptarea).\n\nCând sunteți gata, apăsați pe «Criptare» pentru a începe criptarea.</entry>
-    <entry lang="ro" key="SYSENC_ENCRYPTION_PAGE_INFO">Puteți apăsa pe «Pauză» sau «Amânare» oricând pentru a întrerupe procesul de criptare sau decriptare, să ieșiți din acest asistent, să reporniţi sau să opriți calculatorul și apoi să reluați procesul, care va continua din punctul de unde a fost oprit. Pentru a preveni încetinirea când sistemul sau aplicațiile scriu sau citesc date de pe discul sistem, VeraCrypt va aștepta automat până când datele sunt scrise sau citite (vezi [Stare] de mai sus) și apoi va continua automat criptarea sau decriptarea.</entry>
-    <entry lang="ro" key="NONSYS_INPLACE_ENC_ENCRYPTION_PAGE_INFO">\n\nPuteți apăsa pe «Pauză» sau «Amânare» oricând pentru a întrerupe procesul de criptare, să ieșiți din acest asistent, să reporniţi sau să opriți calculatorul și apoi să reluați procesul, care va continua din punctul de unde a fost oprit. Rețineți că volumul nu va putea fi montat până când acesta nu va fi criptat în întregime.</entry>
-    <entry lang="ro" key="NONSYS_INPLACE_DEC_DECRYPTION_PAGE_INFO">\n\nPuteți apăsa pe «Pauză» sau «Amânare» oricând pentru a întrerupe procesul de decriptare, să ieșiți din acest asistent, să reporniţi sau să opriți calculatorul și apoi să reluați procesul, care va continua din punctul de unde a fost oprit. Rețineți că volumul nu va putea fi montat până când acesta nu va fi decriptat în întregime.</entry>
+    <entry lang="ro" key="SYSENC_ENCRYPTION_PAGE_INFO">Puteți apăsa pe «Pauză» sau «Amânare» oricând pentru a întrerupe procesul de criptare sau decriptare, să ieșiți din acest asistent, să reporniți sau să opriți calculatorul și apoi să reluați procesul, care va continua din punctul de unde a fost oprit. Pentru a preveni încetinirea când sistemul sau aplicațiile scriu sau citesc date de pe discul sistem, VeraCrypt va aștepta automat până când datele sunt scrise sau citite (vezi [Stare] de mai sus) și apoi va continua automat criptarea sau decriptarea.</entry>
+    <entry lang="ro" key="NONSYS_INPLACE_ENC_ENCRYPTION_PAGE_INFO">\n\nPuteți apăsa pe «Pauză» sau «Amânare» oricând pentru a întrerupe procesul de criptare, să ieșiți din acest asistent, să reporniți sau să opriți calculatorul și apoi să reluați procesul, care va continua din punctul de unde a fost oprit. Rețineți că volumul nu va putea fi montat până când acesta nu va fi criptat în întregime.</entry>
+    <entry lang="ro" key="NONSYS_INPLACE_DEC_DECRYPTION_PAGE_INFO">\n\nPuteți apăsa pe «Pauză» sau «Amânare» oricând pentru a întrerupe procesul de decriptare, să ieșiți din acest asistent, să reporniți sau să opriți calculatorul și apoi să reluați procesul, care va continua din punctul de unde a fost oprit. Rețineți că volumul nu va putea fi montat până când acesta nu va fi decriptat în întregime.</entry>
     <entry lang="ro" key="SYSENC_HIDDEN_OS_INITIAL_INFO_TITLE">Sistem ascuns pornit</entry>
     <entry lang="ro" key="SYSENC_HIDDEN_OS_WIPE_INFO_TITLE">Sistem original</entry>
-    <entry lang="ro" key="SYSENC_HIDDEN_OS_WIPE_INFO">Windows crează (în mod normal, fără știrea sau consimțământul dvs.) diferite fișiere jurnal, fișiere temporare etc., pe partiția sistem. Pe deasupra, el salvează conținutul memoriei RAM în fișierele de paginare și de hibernare aflate pe partiția sistemului. Prin urmare, dacă un adversar analizează fișierele stocate pe partiția sistemului original (sistemul ascuns fiind clona acestuia), el ar putea afla, de exemplu, că ați folosit asistentul VeraCrypt în modul de creare a unui sistem ascuns (ceea ce ar putea indica existența unui sistem de operare ascuns pe calculator).\n\nPentru a preveni astfel de situații VeraCrypt șterge în siguranță, în pașii următori, întregul conținut al partiției unde se află sistemul original. După care, pentru a obține negarea plauzibilă, va trebui să instalați un nou sistem pe partiție și să-l criptați. Astfel veți crea un sistem momeală și întreg procesul de creare a unui sistem de operare ascuns va fi finalizat.</entry>
-    <entry lang="ro" key="OS_WIPING_NOT_FINISHED_ASK">Sistemul de operare ascuns a fost creat cu succes. Totuși, înainte de a începe să-l folosiți (și pentru a obține negarea plauzibiă), trebuie să ștergeți în siguranță (folosind VeraCrypt) întregul conținut al partiției de unde rulează și este instalat actualul sistem de operare. Înainte de a putea face acest lucru, trebuie să reporniți calculatorul și în ecranul programului de pornire VeraCrypt (care apare înainte de a porni Windows), introduceți parola de autentificare la prepornire pentru sistemul de operare ascuns. Apoi, după ce sistemul de operare ascuns pornește, asistentul VeraCrypt va fi lansat automat.\n\nNotă: Dacă alegeți să opriți procesul de creare a sistemului de operare ascuns acum, NU veți putea relua procesul, iar sistemul ascuns NU va putea fi accesibil (deoarece programul de pornire VeraCrypt va fi eliminat).</entry>
+    <entry lang="ro" key="SYSENC_HIDDEN_OS_WIPE_INFO">Windows creează (în mod normal, fără știrea sau consimțământul dvs.) diferite fișiere jurnal, fișiere temporare etc., pe partiția sistem. Pe deasupra, el salvează conținutul memoriei RAM în fișierele de paginare și de hibernare aflate pe partiția sistemului. Prin urmare, dacă un adversar analizează fișierele stocate pe partiția sistemului original (sistemul ascuns fiind clona acestuia), el ar putea afla, de exemplu, că ați folosit asistentul VeraCrypt în modul de creare a unui sistem ascuns (ceea ce ar putea indica existența unui sistem de operare ascuns pe calculator).\n\nPentru a preveni astfel de situații VeraCrypt șterge în siguranță, în pașii următori, întregul conținut al partiției unde se află sistemul original. După care, pentru a obține negarea plauzibilă, va trebui să instalați un nou sistem pe partiție și să-l criptați. Astfel veți crea un sistem momeală și întreg procesul de creare a unui sistem de operare ascuns va fi finalizat.</entry>
+    <entry lang="ro" key="OS_WIPING_NOT_FINISHED_ASK">Sistemul de operare ascuns a fost creat cu succes. Totuși, înainte de a începe să-l folosiți (și pentru a obține negarea plauzibilă), trebuie să ștergeți în siguranță (folosind VeraCrypt) întregul conținut al partiției de unde rulează și este instalat actualul sistem de operare. Înainte de a putea face acest lucru, trebuie să reporniți calculatorul și în ecranul programului de pornire VeraCrypt (care apare înainte de a porni Windows), introduceți parola de autentificare la prepornire pentru sistemul de operare ascuns. Apoi, după ce sistemul de operare ascuns pornește, asistentul VeraCrypt va fi lansat automat.\n\nNotă: Dacă alegeți să opriți procesul de creare a sistemului de operare ascuns acum, NU veți putea relua procesul, iar sistemul ascuns NU va putea fi accesibil (deoarece programul de pornire VeraCrypt va fi eliminat).</entry>
     <entry lang="ro" key="HIDDEN_OS_CREATION_NOT_FINISHED_ASK">Ați programat un proces de creare a unui sistem de operare ascuns. Procesul nu a fost încă finalizat. Pentru a-l completa, va trebui să reporniți calculatorul și, în ecranul programului de pornire VeraCrypt (care apare înainte de a porni Windows), introduceți parola pentru sistemul de operare ascuns.\n\nNotă: Dacă alegeți să opriți procesul de creare a sistemului de operare ascuns acum, NU veți putea relua procesul.</entry>
     <entry lang="ro" key="HIDDEN_OS_CREATION_NOT_FINISHED_CHOICE_RETRY">Repornire calculator și continuare</entry>
     <entry lang="ro" key="HIDDEN_OS_CREATION_NOT_FINISHED_CHOICE_TERMINATE">Oprire permanentă proces de creare sistem de operarea ascuns</entry>
@@ -1201,14 +1201,14 @@
     <entry lang="ro" key="RESCUE_DISK_HELP_PORTION_1">\nDACĂ E POSIBIL, TIPĂRIȚI ACEST TEXT (apăsați pe «Tipărire» mai jos).\n\n\nCum și când se utilizează Discul de Recuperare VeraCrypt (După criptare )\n-----------------------------------------------------------------------------------\n\n</entry>
     <entry lang="ro" key="RESCUE_DISK_HELP_PORTION_2">I. Cum se pornește Discul de Recuperare VeraCrypt\n\nPentru a porni Discul de Recuperare VeraCrypt, introduceți-l în unitatea CD/DVD și reporniți calculatorul. Dacă ecranul Discului de Recuperare VeraCrypt nu apare (sau dacă nu vedeți opțiunea „Repair Options” în secțiunea „Keyboard Controls”), este posibil ca în BIOS să fie configurată pornirea de pe hard disc înainte de unitatea CD/DVD. Dacă acesta este cazul, reporniți calculatorul, apăsați tasta F2 sau Delete (imediat ce vedeți ecranul de pornire BIOS) și așteptați să apară ecranul de configurare pentru BIOS. Dacă ecranul de configurare BIOS nu apare, reporniți (resetați) din nou calculatorul și începeți să apăsați în mod repetat tasta F2 sau Delete imediat ce ați repornit (resetat) calculatorul. Când apare ecranul de configurare pentru BIOS, configurați setările din BIOS pentru a porni unitatea CD/DVD prima dată (pentru informații despre cum se face asta, consultați documentația pentru acest BIOS/placă de bază sau contactați echipa de suport tehnic a furnizorului echipamentului pentru asistență). Apoi reporniți calculatorul. Ecranul Discului de Recuperare VeraCrypt ar trebui acum să apară. Notă: în ecranul Discului de Recuperare VeraCrypt, puteți selecta «Repair Options» apăsând tasta F8 de pe tastatură.\n\n\n</entry>
     <entry lang="ro" key="RESCUE_DISK_HELP_PORTION_3">II. Când și cum se utilizează Discul de Recuperare VeraCrypt (după criptare)\n\n</entry>
-    <entry lang="ro" key="RESCUE_DISK_HELP_PORTION_4">1) Dacă ecranul programului de pornire Veracrypt nu apare după ce porniți calculatorul (sau dacă Windows nu pornește), programul de pornire VeraCrypt poate fi afectat. Discul de Recuperare VeraCrypt vă permite să-l restaurați și astfel să recăpătați accesul la sistemul criptat și la date (totuși, încă va trebui să introduceți parola corectă). În ecranul discului de recuperare, selectați „Repair Options” > „Restore VeraCrypt Boot Loader”. Apoi introduceți parola și apăsați „Y” pentru a confirma acțiunea, eliminați discul de recuperare din unitatea CD/DVD și reporniți calculatorul.\n\n</entry>
-    <entry lang="ro" key="RESCUE_DISK_HELP_PORTION_5">2) Dacă ați introdus în mod repetat parola corectă, dar VeraCrypt spune că parola este incorectă, cheia principală sau alte date critice ar putea fi afectate. Discul de Recuperare VeraCrypt vă permite să le restaurați și astfel să recăpătați accesul la sistemul criptat și la date (totuși, încă va trebui să introduceți parola corectă). În ecranul discului de recuperare, selectați „Repair Options” > „Restore key data”. Apoi introduceți parola și apăsați „Y” pentru a confirma acțiunea, eliminați Discul de Recuperare din unitatea CD/DVD și reporniți calculatorul.\n\n</entry>
-    <entry lang="ro" key="RESCUE_DISK_HELP_PORTION_6">3) Dacă programul de pornire VeraCrypt este distrus, puteți evita executarea acestuia prin pornirea directă de pe Discul de Recuperare VeraCrypt. Introduceți Discul de Recuperare în unitatea CD/DVD și apoi introduceți parola în ecranul Discului de Recuperare.\n\n</entry>
+    <entry lang="ro" key="RESCUE_DISK_HELP_PORTION_4">1) Dacă ecranul programului de pornire VeraCrypt nu apare după ce porniți calculatorul (sau dacă Windows nu pornește), programul de pornire VeraCrypt poate fi afectat. Discul de Recuperare VeraCrypt vă permite să-l restaurați și astfel să recăpătați accesul la sistemul criptat și la date (totuși, încă va trebui să introduceți parola corectă). În ecranul discului de recuperare, selectați „Repair Options” > „Restore VeraCrypt Boot Loader”. Apoi introduceți parola și apăsați „Y” pentru a confirma acțiunea, eliminați discul de recuperare din unitatea CD/DVD și reporniți calculatorul.\n\n</entry>
+    <entry lang="ro" key="RESCUE_DISK_HELP_PORTION_5">2) Dacă ați introdus în mod repetat parola corectă, dar VeraCrypt spune că parola este incorectă, cheia principală sau alte date critice ar putea fi afectate. Discul de Recuperare VeraCrypt vă permite să le restaurați și astfel să recăpătați accesul la sistemul criptat și la date (totuși, încă va trebui să introduceți parola corectă). În ecranul discului de recuperare, selectați „Repair Options” > „Restore key data”. Apoi introduceți parola și apăsați „Y” pentru a confirma acțiunea, eliminați discul de recuperare din unitatea CD/DVD și reporniți calculatorul.\n\n</entry>
+    <entry lang="ro" key="RESCUE_DISK_HELP_PORTION_6">3) Dacă programul de pornire VeraCrypt este distrus, puteți evita executarea acestuia prin pornirea directă de pe Discul de Recuperare VeraCrypt. Introduceți discul de recuperare în unitatea CD/DVD și apoi introduceți parola în ecranul discului de recuperare.\n\n</entry>
     <entry lang="ro" key="RESCUE_DISK_HELP_PORTION_7">4) Dacă Windows este distrus și nu poate porni, Discul de Recuperare VeraCrypt vă permite să decriptați partiția/discul înainte de a porni Windows. În ecranul Discului de Recuperare, selectați „Repair Options” > „Permanently decrypt system partition/drive”. Introduceți parola corectă și așteptați până când este complet decomprimat. Apoi veți putea de ex. porni programul de instalare MS Windows de pe CD/DVD pentru a repara instalarea Windows.\n\n</entry>
-    <entry lang="ro" key="RESCUE_DISK_HELP_PORTION_8">Notă: alternativ, dacă Windows este afectat (nu poate porni) și aveți nevoie să-l reparați (sau să accesați fișiere de pe el), puteți evita să decriptați partiția/discul sistem executând pașii următori: dacă aveți multiple sisteme de operare instalate în calculator, porniți unul care nu necesită autentificare la prepornire. Dacă nu aveți multiple sisteme de operare instalate în calculator, puteți porni un CD/DVD WinPE sau BartPE sau puteți conecta discul sistem ca un disc secundar sau disc extern la un alt calculator și apoi porniți sistemul de operare instalat pe calculator. După ce porniți un sistem, executați VeraCrypt, apăsați pe „Selectare disc/partiție”, selectați partiția sistem afectată, apăsați pe «OK», selectați „Sistem” > „Montare fără autentificare la pornire”, introduceți parola de autentifcare și apăsați pe «OK». Partiția va fi montată ca un volum normal VeraCrypt (datele vor fi decriptate/criptate din mers în memoria RAM, ca de obicei).\n\n\n</entry>
+    <entry lang="ro" key="RESCUE_DISK_HELP_PORTION_8">Notă: alternativ, dacă Windows este afectat (nu poate porni) și aveți nevoie să-l reparați (sau să accesați fișiere de pe el), puteți evita să decriptați partiția/discul sistem executând pașii următori: dacă aveți multiple sisteme de operare instalate în calculator, porniți unul care nu necesită autentificare la prepornire. Dacă nu aveți multiple sisteme de operare instalate în calculator, puteți porni un CD/DVD WinPE sau BartPE sau puteți conecta discul sistem ca un disc secundar sau disc extern la un alt calculator și apoi porniți sistemul de operare instalat pe calculator. După ce porniți un sistem, executați VeraCrypt, apăsați pe „Selectare disc/partiție”, selectați partiția sistem afectată, apăsați pe «OK», selectați „Sistem” > „Montare fără autentificare la pornire”, introduceți parola de autentificare și apăsați pe «OK». Partiția va fi montată ca un volum normal VeraCrypt (datele vor fi decriptate/criptate din mers în memoria RAM, ca de obicei).\n\n\n</entry>
     <entry lang="ro" key="RESCUE_DISK_HELP_PORTION_9">Rețineți că chiar dacă veți pierde Discul de Recuperare VeraCrypt și un posibil adversar îl găsește, acesta NU va fi capabil să decripteze partiția sau discul sistem fără parola corectă.</entry>
     <entry lang="ro" key="DECOY_OS_INSTRUCTIONS_PORTION_1">\n\nI M P O R T A N T -- TIPĂRIȚI ACEST TEXT DACĂ ESTE POSIBIL (apăsați pe «Tipărire» mai jos).\n\n\nNotă: Acest text va fi afișat automat de fiecare dată când pornește sistemul ascuns până când începeți să creați sistemul momeală.\n\n\n</entry>
-    <entry lang="ro" key="DECOY_OS_INSTRUCTIONS_PORTION_2">Cum se crează în siguranță și în mod sigur sistemul momeală\n----------------------------------------------------------------------------\n\nPentru a obține negarea plauzibilă, va trebui să creați acum un sistem de operare momeală. Pentru aceasta, executați următorii pași:\n\n</entry>
+    <entry lang="ro" key="DECOY_OS_INSTRUCTIONS_PORTION_2">Cum se creează în siguranță și în mod sigur sistemul momeală\n----------------------------------------------------------------------------\n\nPentru a obține negarea plauzibilă, va trebui să creați acum un sistem de operare momeală. Pentru aceasta, executați următorii pași:\n\n</entry>
     <entry lang="ro" key="DECOY_OS_INSTRUCTIONS_PORTION_3">1) Din motive de securitate, opriți calculatorul și lăsați-l oprit pentru cel puțin câteva minute (cu cât mai mult, cu atât mai mult). Aceasta este necesar pentru a goli memoria, care conține date importante. Apoi porniți calculatorul, dar nu porniți sistemul ascuns.\n\n</entry>
     <entry lang="ro" key="DECOY_OS_INSTRUCTIONS_PORTION_4">2) Instalați Windows pe o partiție a cărui conținut a fost șters (adică pe partiția unde s-a aflat sistemul de operare original, a cărui clonă este sistemul ascuns).\n\nIMPORTANT: CÂND PORNIȚI INSTALAREA SISTEMULUI MOMEALĂ, SISTEMUL ASCUNS *NU* VA FI POSIBIL DE PORNIT (deoarece programul de pornire VeraCrypt va fi șters de programul de instalare Windows). ACEASTA ESTE NORMAL ȘI DE AȘTEPTAT. VĂ RUGĂM SĂ NU VĂ PANICAȚI. VEȚI PUTEA SĂ PORNIȚI SISTEMUL ASCUNS DIN NOU IMEDIAT CE ÎNCEPEȚI CRIPTAREA SISTEMULUI MOMEALĂ (deoarece VeraCrypt va instala atunci programul de pornire VeraCrypt pe discul sistem).\n\nImportant: dimensiunea partiției sistemului momeală trebuie să rămână la fel cu cea a volumului ascuns (această condiție este acum îndeplinită). În plus, nu trebuie să creați vreo partiție între partiția sistemului momeală și partiția unde se află sistemul ascuns.\n\n</entry>
     <entry lang="ro" key="DECOY_OS_INSTRUCTIONS_PORTION_5">3) Porniți sistemul momeală (pe care l-ați instalat în pasul 2 și instalați pe el VeraCrypt).\n\nRețineți că sistemul momeală nu trebuie să conțină date importante.\n\n</entry>
@@ -1222,7 +1222,7 @@
     <entry lang="ro" key="DECOY_OS_INSTRUCTIONS_PORTION_13">După crearea sistemului momeală\n------------------------------------------------\n\nDupă ce veți cripta sistemul momeală, întregul proces de creare a sistemului de operare ascuns va fi finalizat și veți putea folosi aceste trei parole:\n\n1) Parola de autentificare la prepornire pentru sistemul de operare ascuns.\n\n2) Parola de autentificare la prepornire pentru sistemul de operare momeală.\n\n3) Parola pentru volumul exterior.\n\n</entry>
     <entry lang="ro" key="DECOY_OS_INSTRUCTIONS_PORTION_14">Dacă doriți să porniți sistemul de operare ascuns, va trebui doar să introduceți parola pentru sistemul de operare ascuns în ecranul programului de pornire VeraCrypt (care apare după ce porniți sau reporniți calculatorul).\n\nDacă doriți să porniți sistemul de operare momeală, va trebui doar să introduceți parola pentru sistemul de operare momeală în ecranul programului de pornire VeraCrypt.\n\nParola pentru sistemul momeală poate fi dezvăluită oricui vă forțează să dezvăluiți parola de autentificare la prepornire. Existența volumului ascuns (și deci a sistemului de operare ascuns) va rămâne secretă.\n\n</entry>
     <entry lang="ro" key="DECOY_OS_INSTRUCTIONS_PORTION_15">A treia parolă (pentru volumul exterior) poate fi dezvăluită oricui vă forțează să dezvăluiți parola pentru prima partiție de după partiția sistem, unde se află atât volumul exterior cât și cel ascuns (conținând sistemul de operare ascuns). Existența volumului ascuns (și implicit a sistemului de operare ascuns) va rămâne secretă.\n\n\n</entry>
-    <entry lang="ro" key="DECOY_OS_INSTRUCTIONS_PORTION_16">Dacă ați dezvăluit parola pentru sistemul momeală unui adversar și acesta vă întreabă de ce spațiul liber de pe partiția sistemului (momeală) conține date aleatoare, ați putea răspunde, de exemplu: „Partiția a conținut anterior un sistem criptat cu VeraCrypt, dar am uitat parola de autentificcare la prepornire (sau sistemul a fost afectat și nu a mai pornit), astfel încât a trebuit să reinstalez Windows și să criptez din nou partiția.”\n\n\n</entry>
+    <entry lang="ro" key="DECOY_OS_INSTRUCTIONS_PORTION_16">Dacă ați dezvăluit parola pentru sistemul momeală unui adversar și acesta vă întreabă de ce spațiul liber de pe partiția sistemului (momeală) conține date aleatorii, ați putea răspunde, de exemplu: „Partiția a conținut anterior un sistem criptat cu VeraCrypt, dar am uitat parola de autentificare la prepornire (sau sistemul a fost afectat și nu a mai pornit), astfel încât a trebuit să reinstalez Windows și să criptez din nou partiția.”\n\n\n</entry>
     <entry lang="ro" key="DECOY_OS_INSTRUCTIONS_PORTION_17">Dacă sunt urmate toate instrucțiunile, precauțiile și recomandările afișate în secțiunea „Security Requirements and Precautions Pertaining to Hidden Volumes” din „Ghidul de utilizare VeraCrypt”, ar trebui să fie imposibil de dovedit că există un volum ascuns și un sistem de operare ascuns, chiar dacă este montat un volum exterior sau când este decriptat și pornit sistemul de operare momeală.\n\nDacă salvați o copie a acestui text sau îl tipăriți (ceea ce vă rugăm insistent, cu excepția cazului în care imprimanta stochează copii ale documentelor tipărite pe un disc intern), ar trebui să distrugeți orice copie a acestuia după ce ați creat sistemul de operare momeală și după ce ați înțeles toate informațiile conținute în acesta (altfel, dacă o astfel de copie va fi găsită, ar putea da indicii că există un sistem de operare ascuns pe acest calculator).\n\n</entry>
     <entry lang="ro" key="DECOY_OS_INSTRUCTIONS_PORTION_18">AVERTIZARE: DACĂ NU PROTEJAȚI VOLUMUL ASCUNS (pentru informații despre cum se face asta, consultați secțiunea „Protection of Hidden Volumes Against Damage” din „Ghidul de utilizare VeraCrypt”), NU SCRIEȚI DATE ÎN VOLUMUL EXTERIOR (sistemul de operare ascuns NU este instalat în volumul exterior). ALTFEL, S-AR PUTEA SĂ SUPRASCRIEȚI ȘI SĂ DISTRUGEȚI VOLUMUL ASCUNS (ȘI SISTEMUL DE OPERARE ASCUNS DE PE EL)!</entry>
     <entry lang="ro" key="HIDDEN_OS_CREATION_PREINFO_TITLE">Executare clonare sistem</entry>
@@ -1236,12 +1236,12 @@
     <entry lang="ro" key="SYS_ENCRYPTION_OR_DECRYPTION_IN_PROGRESS">Discul/partiția sistem este în acest moment în proces de criptare, decriptare sau modificare. Întrerupeți procesul de criptare/decriptare/modificare (sau așteptați până la finalizarea acestuia) înainte de a continua.</entry>
     <entry lang="ro" key="SYSTEM_ENCRYPTION_IN_PROGRESS_ELSEWHERE">O instanță a asistentului de creare volume VeraCrypt este pornită acum pe acest sistem și execută sau se pregătește criptarea/decriptarea partiției/discului sistem. Înainte de a continua, așteptați să se finalizeze sau închideți-l. Dacă nu-l puteți închide, reporniți calculatorul înainte de a continua.</entry>
     <entry lang="ro" key="SYSTEM_ENCRYPTION_NOT_COMPLETED">Procesul de criptare sau decriptare a partiției/discului sistem nu a fost finalizat. Așteptați până la finalizarea acestuia înainte de a continua.</entry>
-    <entry lang="ro" key="ERR_ENCRYPTION_NOT_COMPLETED">Eroare: procesul de criptare a partiției/discului sistem nu a fost finalizat. Trebuie mai întrâi finalizat.</entry>
-    <entry lang="ro" key="ERR_NONSYS_INPLACE_ENC_INCOMPLETE">Eroare: procesul de criptare a partiției/volumului nu a fost finalizat. Trebuie mai întrâi finalizat.\n\nNotă: pentru a relua procesul, selectați „Volume” > „Reluare proces întrerupt” din bara meniului ferestrei principale VeraCrypt.</entry>
+    <entry lang="ro" key="ERR_ENCRYPTION_NOT_COMPLETED">Eroare: procesul de criptare a partiției/discului sistem nu a fost finalizat. Trebuie mai întâi finalizat.</entry>
+    <entry lang="ro" key="ERR_NONSYS_INPLACE_ENC_INCOMPLETE">Eroare: procesul de criptare a partiției/volumului nu a fost finalizat. Trebuie mai întâi finalizat.\n\nNotă: pentru a relua procesul, selectați „Volume” > „Reluare proces întrerupt” din bara meniului ferestrei principale VeraCrypt.</entry>
     <entry lang="ro" key="ERR_SYS_HIDVOL_HEAD_REENC_MODE_WRONG">Parola este corectă, VeraCrypt a decriptat cu succes antetul volumului și a detectat că acest volum este un volum sistem ascuns. Totuși, nu puteți modifica antetul volumului sistem ascuns în acest mod.\n\nPentru a modifica parola pentru un volum sistem ascuns, porniți sistemul de operare aflat pe volumul ascuns și apoi selectați „Sistem” > „Schimbare parolă” din bara meniului ferestrei principale VeraCrypt.\n\nPentru a stabili algoritmul cheii de derivare, porniți sistemul de operare ascuns și apoi selectați „Sistem” > „Setare algoritm derivare cheie antet”.</entry>
     <entry lang="ro" key="CANNOT_DECRYPT_HIDDEN_OS">VeraCrypt nu suportă decriptarea din mers a partiției sistemului ascuns.\n\nNotă: dacă doriți decriptarea partiției sistemului momeală, porniți sistemul momeală și apoi selectați „Sistem” > „Decriptare permanentă disc/partiție sistem” din bara meniului ferestrei principale VeraCrypt.</entry>
     <entry lang="ro" key="ERR_PARAMETER_INCORRECT">Eroare: parametru incorect/nevalid.</entry>
-    <entry lang="ro" key="DEVICE_SELECTED_IN_NON_DEVICE_MODE">Ați selectat o partiție sau disc dar tipul de asistent selectat este protrivit numai pentru fișiere container.\n\nDoriți să schimbați tipul asistentului?</entry>
+    <entry lang="ro" key="DEVICE_SELECTED_IN_NON_DEVICE_MODE">Ați selectat o partiție sau disc dar tipul de asistent selectat este potrivit numai pentru fișiere container.\n\nDoriți să schimbați tipul asistentului?</entry>
     <entry lang="ro" key="CONFIRM_CHANGE_WIZARD_MODE_TO_FILE_CONTAINER">Doriți să creați în schimb un fișier container VeraCrypt?</entry>
     <entry lang="ro" key="CONFIRM_SYSTEM_ENCRYPTION_MODE">Ați selectat partiția/discul sistem (sau partiția de pornire), dar tipul de asistent selectat este potrivit numai pentru partiții/discuri non-sistem.\n\nDoriți să instalați autentificarea la prepornire (ceea ce înseamnă că va trebui să introduceți parola de fiecare dată înainte de a porni/reporni Windows) și să criptați partiția/discul sistem?</entry>
     <entry lang="ro" key="CONFIRM_DECRYPT_SYS_DEVICE">Sigur doriți decriptarea permanentă a partiției/discului sistem?</entry>
@@ -1257,15 +1257,15 @@
     <entry lang="ro" key="BOOT_LOADER_UPGRADE_OK_HIDDEN_OS">Programul de pornire VeraCrypt a fost actualizat.\n\nEste foarte important să porniți sistemul de operare momeală și să creați un nou Disc de Recuperare VeraCrypt (care va conține noua versiune a programului de încărcare VeraCrypt) selectând „Sistem” > „Creare disc de recuperare”.</entry>
     <entry lang="ro" key="BOOT_LOADER_UPGRADE_FAILED">Actualizare eșuată a programului de pornire VeraCrypt.</entry>
     <entry lang="ro" key="SYS_DRIVE_SIZE_PROBE_TIMEOUT">VeraCrypt nu a putut detecta dimensiunea reală a discului sistem și, prin urmare, va fi folosită dimensiunea raportată de sistemul de operare (care ar putea fi mai mică decât cea reală). De reținut că aceasta nu este o eroare din VeraCrypt.</entry>
-    <entry lang="ro" key="HIDDEN_SECTOR_DETECTION_FAILED_PREVIOUSLY">AVERTIZARE: se pare că VeraCrypt a încercat deja să detecteze sectoarele ascunse ale acestui disc sistem. Dacă ați întâmpinat vreo problemă în timpul procesului de detectție anterior, puteți evita problemele ignorând detectarea sectoarelor acum. Rețineți că dacă o faceți, VeraCrypt va folosi dimensiunea raportată de către sistemul de operare (care ar putea fi mai mică decât cea reală a discului).\n\nRețineți că această situație nu este datorată unei erori din VeraCrypt.</entry>
-    <entry lang="ro" key="SKIP_HIDDEN_SECTOR_DETECTION">Ignorare detectare sectoare ascunse (utilizare dimensiune rapoartată de către sistemul de operare)</entry>
+    <entry lang="ro" key="HIDDEN_SECTOR_DETECTION_FAILED_PREVIOUSLY">AVERTIZARE: se pare că VeraCrypt a încercat deja să detecteze sectoarele ascunse ale acestui disc sistem. Dacă ați întâmpinat vreo problemă în timpul procesului de detectare anterior, puteți evita problemele ignorând detectarea sectoarelor acum. Rețineți că dacă o faceți, VeraCrypt va folosi dimensiunea raportată de către sistemul de operare (care ar putea fi mai mică decât cea reală a discului).\n\nRețineți că această situație nu este datorată unei erori din VeraCrypt.</entry>
+    <entry lang="ro" key="SKIP_HIDDEN_SECTOR_DETECTION">Ignorare detectare sectoare ascunse (utilizare dimensiune raportată de către sistemul de operare)</entry>
     <entry lang="ro" key="RETRY_HIDDEN_SECTOR_DETECTION">Reîncercare detectare sectoare ascunse</entry>
     <entry lang="ro" key="ENABLE_BAD_SECTOR_ZEROING">Eroare: conținutul unuia sau mai multor sectoare de pe disc nu poate fi citit (probabil datorită unui defect fizic).\n\nProcesul de criptare din mers poate continua numai când sectoarele pot fi citite din nou. VeraCrypt poate încerca să facă aceste sectoare accesibile scriindu-le cu valori zero (ulterior astfel de blocuri ce conțin valori zero vor fi criptate). Totuși, orice date stocate pe sectoarele neaccesibile vor fi pierdute. Dacă doriți să evitați acest lucru, puteți încerca să recuperați porțiunile datelor corupte folosind programe terțe specializate pentru aceasta.\n\nNotă: în cazul sectoarelor defecte fizic (spre deosebire de cazul coruperii datelor sau erorilor de paritate) majoritatea tipurilor de discuri realocă intern aceste sectoare când se încearcă scrierea pe acestea (astfel încât datele corupte existente pe sectoarele defecte pot rămâne necriptate).\n\nDoriți ca VeraCrypt să scrie valori zero pe sectoarele care nu se pot citi?</entry>
-    <entry lang="ro" key="DISCARD_UNREADABLE_ENCRYPTED_SECTORS">Eroare: conținutul unuia sau mai multor sectoare de pe disc nu poate fi citit (probabil datorită unui defect fizic).\n\nPentru a putea continua decriptarea, VeraCrypt va trebui să ignore conținutul sectoarelor neaccesibile (conținutul va fi înlocuit cu date aleatoare). Rețineți că înainte de a continua, puteți încerca recuperarea porțiunilor de date corupte folosind programe terțe specializate pentru aceasta.\n\nDoriți ca VeraCrypt să ignore datele de pe sectoarele neaccesibile acum?</entry>
+    <entry lang="ro" key="DISCARD_UNREADABLE_ENCRYPTED_SECTORS">Eroare: conținutul unuia sau mai multor sectoare de pe disc nu poate fi citit (probabil datorită unui defect fizic).\n\nPentru a putea continua decriptarea, VeraCrypt va trebui să ignore conținutul sectoarelor neaccesibile (conținutul va fi înlocuit cu date aleatorii). Rețineți că înainte de a continua, puteți încerca recuperarea porțiunilor de date corupte folosind programe terțe specializate pentru aceasta.\n\nDoriți ca VeraCrypt să ignore datele de pe sectoarele neaccesibile acum?</entry>
     <entry lang="ro" key="ZEROED_BAD_SECTOR_COUNT">Notă: VeraCrypt a înlocuit conținutul a %I64d sectoare neaccesibile (%s) cu blocuri de text zero criptate.</entry>
-    <entry lang="ro" key="SKIPPED_BAD_SECTOR_COUNT">Notă: VeraCrypt a înlocuit conținutul a %I64d sectoare defecte (%s) cu date aleatoare.</entry>
+    <entry lang="ro" key="SKIPPED_BAD_SECTOR_COUNT">Notă: VeraCrypt a înlocuit conținutul a %I64d sectoare defecte (%s) cu date aleatorii.</entry>
     <entry lang="ro" key="ENTER_TOKEN_PASSWORD">Introduceți parola/PIN-ul pentru dispozitivul „%s”:</entry>
-    <entry lang="ro" key="PKCS11_LIB_LOCATION_HELP">Pentru a permite ca VeraCrypt să acceseze un dispozitiv de securitate sau card inteligent, trebuie să instalați mai întâi librăria software PKCS #11 pentru dispozitive de securitate sau card inteligent. O astfel de librărie poate fi furnizată cu unitatea respectivă sau poate fi disponibilă pentru descărcare de pe pagina web a producătorului sau o altă terță parte.\n\nDupă ce veți instala librăria, puteți fie să o selectați manual apăsând pe «Selectare librărie» sau puteți lăsa ca VeraCrypt să o găsească și să o selecteze automat apăsând pe «Autodetectare librărie» (va fi căutată doar în folderul de sistem Windows).</entry>
+    <entry lang="ro" key="PKCS11_LIB_LOCATION_HELP">Pentru ca VeraCrypt să poată accesa un dispozitiv de securitate sau card inteligent, trebuie să instalați mai întâi librăria software PKCS #11 pentru dispozitive de securitate sau carduri inteligente. Această librărie poate fi furnizată cu unitatea respectivă sau poate fi disponibilă pentru descărcare de pe pagina web a producătorului sau o altă terță parte.\nDupă instalarea librăriei, o puteți selecta fie manual apăsând pe «Selectare librărie» sau alegeți ca VeraCrypt să o găsească și să o selecteze automat apăsând pe «Autodetectare librărie» (va fi căutată doar în folderul de sistem Windows).</entry>
     <entry lang="ro" key="SELECT_PKCS11_MODULE_HELP">Notă: pentru numele fișierului și locul librăriei PKCS #11 instalată pentru dispozitivul de securitate sau cardul inteligent, consultați documentația primită cu dispozitivul, cardul sau programul terței părți.\n\nApăsați pe «OK» pentru a selecta calea și numele fișierului.</entry>
     <entry lang="ro" key="NO_PKCS11_MODULE_SPECIFIED">Pentru a permite ca VeraCrypt să acceseze un dispozitiv de securitate sau card inteligent, trebuie mai întâi să selectați o librărie software PKCS #11 pentru dispozitiv sau card inteligent. Pentru aceasta, selectați „Setări” > „Dispozitive de securitate”.</entry>
     <entry lang="ro" key="PKCS11_MODULE_INIT_FAILED">Eșuare inițializare librărie PKCS #11 a dispozitivului de securitate.\n\nVerificați dacă calea și numele fișierului specificate se referă la o librărie PKCS #11 validă. Pentru a specifica calea și numele fișierului unei librării PKCS #11, selectați „Setări” > „Dispozitive de securitate”.</entry>
@@ -1294,7 +1294,7 @@
     <entry lang="ro" key="SELECT_DEVICE_AND_MOUNT">Selectare &amp;disc/partiție și montare</entry>
     <entry lang="ro" key="DISABLE_NONADMIN_SYS_FAVORITES_ACCESS">Permite numai administratorilor să vadă și să demonteze volume sistem favorite în VeraCrypt</entry>
     <entry lang="ro" key="MOUNT_SYSTEM_FAVORITES_ON_BOOT">Montare volume sistem favorite la pornirea Windows (în faza inițială a procedurii de pornire)</entry>
-    <entry lang="ro" key="MOUNTED_VOLUME_DIRTY">Avertizare: sistemul de fișiere de pe volumul montat „%s” nu a fost demontat în sigurață și deci poate conține erori. Folosirea unui sistem de fișiere corupt poate determina pierderea datelor sau coruperea acestora.\n\nNotă: înainte de a îndepărta fizic sau opri alimentarea unității (cum ar fi o unitate de memorie USB sau hard disc extern) unde se află un volum VeraCrypt montat, întotdeauna ar trebui ca mai întâi să demontați volumul VeraCrypt din programul VeraCrypt.\n\n\nDoriți ca Windows să încerce să detecteze și să fixeze (dacă e cazul) erorile din sistemul de fișiere?</entry>
+    <entry lang="ro" key="MOUNTED_VOLUME_DIRTY">Avertizare: sistemul de fișiere de pe volumul montat „%s” nu a fost demontat în siguranță și deci poate conține erori. Folosirea unui sistem de fișiere corupt poate determina pierderea datelor sau coruperea acestora.\n\nNotă: înainte de a îndepărta fizic sau opri alimentarea unității (cum ar fi o unitate de memorie USB sau hard disc extern) unde se află un volum VeraCrypt montat, întotdeauna ar trebui ca mai întâi să demontați volumul VeraCrypt din programul VeraCrypt.\n\n\nDoriți ca Windows să încerce să detecteze și să fixeze (dacă e cazul) erorile din sistemul de fișiere?</entry>
     <entry lang="ro" key="SYS_FAVORITE_VOLUME_DIRTY">Avertizare: unul sau mai multe volume sistem favorite nu a fost demontat în siguranță și deci poate conține erori în sistemul de fișiere. Verificați jurnalul evenimentelor de sistem pentru mai multe detalii.\n\nUtilizarea un sistem de fișiere corupt poate determina pierderea sau coruperea datelor. Ar trebui să verificați dacă volumele sistem favorite afectate au erori (apăsați cu clic dreapta pe fiecare din ele în fereastra VeraCrypt și selectați „Reparare sistem de fișiere”).</entry>
     <entry lang="ro" key="FILESYS_REPAIR_CONFIRM_BACKUP">Avertizare: repararea unui sistem de fișiere defect folosind comanda Microsoft „chkdsk” poate cauza pierderea fișierelor în zonele afectate. Prin urmare, este recomandat să faceți mai întâi o copie a fișierelor stocate în volumul VeraCrypt pe un alt volum VeraCrypt, sănătos.\n\nDoriți să reparați sistemul de fișiere acum?</entry>
     <entry lang="ro" key="MOUNTED_CONTAINER_FORCED_READ_ONLY">Volumul „%s” a fost montat ca doar-citire deoarece dreptul de scriere nu a fost permis.\n\nVerificați dacă permisiunile de securitate ale fișierului container permit scrierea în el (apăsați cu clic dreapta pe fișierul container și selectați Properties > Security).\n\nRețineți că, datorită unei probleme în Windows, ați putea vedea acest mesaj de avertizare chiar și după ce ați setat permisiunile de securitate adecvate. Aceasta nu este cauzată de o eroare din VeraCrypt. O soluție posibilă este să mutați containerul, de ex. în folderul „Documents”.\n\nDacă intenționați să păstrați volumul ca doar-citire, setați atributul containerului ca doar-citire (apăsați cu clic dreapta pe container și selectați „Properties” > „Read-only”), ceea ce va determina evitarea acestui avertisment.</entry>
@@ -1303,7 +1303,7 @@
     <entry lang="ro" key="LIMIT_ENC_THREAD_POOL_NOTE">Rețineți că tehnologia prin fire de execuție (Hyper-Threading ) pune la dispoziție mai multe nuclee logice la un singur nucleu fizic din procesor. Când este activată funcția de fire de execuție, numărul selectat mai sus reprezintă numărul de procesoare/nuclee logice.</entry>
     <entry lang="ro" key="NUMBER_OF_THREADS">%d nuclee logice</entry>
     <entry lang="ro" key="DISABLED_HW_AES_AFFECTS_PERFORMANCE">Rețineți că accelerarea hardware AES este dezactivată, ceea ce va afecta rezultatele evaluării (performanțe mai slabe).\n\nPentru a activa accelerarea hardware, selectați „Setări” > „Performanță” și activați opțiunea respectivă.</entry>
-    <entry lang="ro" key="LIMITED_THREAD_COUNT_AFFECTS_PERFORMANCE">Rețineți că numărul firelor de execuție este în acest moment limitat, ceea ce va afecta rezultatele evalurii (performanțe mai slabe).\n\nPentru a utiliza întregul potențial al procesorului, selectați „Setări” > „Performață” și dezactivați opțiunea de limitare respectivă.</entry>
+    <entry lang="ro" key="LIMITED_THREAD_COUNT_AFFECTS_PERFORMANCE">Rețineți că numărul firelor de execuție este în acest moment limitat, ceea ce va afecta rezultatele evaluării (performanțe mai slabe).\n\nPentru a utiliza întregul potențial al procesorului, selectați „Setări” > „Performanță” și dezactivați opțiunea de limitare respectivă.</entry>
     <entry lang="ro" key="ASK_REMOVE_DEVICE_WRITE_PROTECTION">Doriți ca VeraCrypt să încerce să elimine protejarea la scriere a partiției/discului?</entry>
     <entry lang="ro" key="CONFIRM_SETTING_DEGRADES_PERFORMANCE">AVERTIZARE: această setare ar putea degrada performanța.\n\nSigur doriți să folosiți această setare?</entry>
     <entry lang="ro" key="HOST_DEVICE_REMOVAL_UNMOUNT_WARN_TITLE">Avertizare: volum VeraCrypt autodemontat</entry>
@@ -1379,7 +1379,7 @@
     <entry lang="ro" key="TRIPLE_DOT_GLYPH_ELLIPSIS">…</entry>
     <entry lang="ro" key="IDC_BOOT_LOADER_CACHE_PIM">Include și MI&amp;P la salvarea parolei de autentificare la pornire</entry>
     <entry lang="ro" key="IDC_PREF_CACHE_PIM">Includere MIP când se salvează o parolă</entry>
-    <entry lang="ro" key="IDC_SHOW_DISCONNECTED_NETWORK_DRIVES">Unitățile de rețea deconectate afişate ca disponibile pentru montare</entry>
+    <entry lang="ro" key="IDC_SHOW_DISCONNECTED_NETWORK_DRIVES">Unitățile de rețea deconectate afișate ca disponibile pentru montare</entry>
     <entry lang="ro" key="PASSWORD_UTF8_TOO_LONG">Parola introdusă este prea lungă: reprezentarea sa în UTF-8 depășește %d de baiți.</entry>
     <entry lang="ro" key="PASSWORD_UTF8_INVALID">Parola introdusă conține caractere în Unicode care nu s-au putut converti în UTF-8.</entry>
     <entry lang="ro" key="INIT_DLL">Eroare: eșuare la încărcarea unei librării de sistem.</entry>
@@ -1395,7 +1395,7 @@
     <entry lang="ro" key="DISABLE_BOOT_LOADER_PIM_PROMPT">ATENȚIONARE: dacă activați această opțiune, valoarea MIP va fi stocată necriptată pe disc.\n\nSigur doriți activarea acestei opțiuni?</entry>
     <entry lang="ro" key="PIM_TOO_BIG">Valoarea maximă pentru Multiplicatorul Iterațiilor Personal (MIP) este 2147468.</entry>
     <entry lang="ro" key="IDC_SKIP_RESCUE_VERIFICATION">Ignorare verificare DRV</entry>
-    <entry lang="ro" key="IDC_HIDE_WAITING_DIALOG">Nu se afișează dialogul cu mesajul de așteptare la efecturarea operațiilor</entry>
+    <entry lang="ro" key="IDC_HIDE_WAITING_DIALOG">Nu se afișează dialogul cu mesajul de așteptare la efectuarea operațiilor</entry>
     <entry lang="ro" key="IDC_DISABLE_BOOT_LOADER_HASH_PROMPT">Nu solicita algoritmul Hash la ecranul de autentificare la pornire</entry>
     <entry lang="ro" key="KUZNYECHIK_HELP">Kuznyechik este un cifru de blocuri prima data publicat în 2015 și definit în Standardul Național al Federației Ruse GOST R 34.12-2015 și în RFC 7801. Chei de 256 de biți, blocuri de 128 de biți. Modul de operare este XTS.</entry>
     <entry lang="ro" key="CAMELLIA_HELP">Dezvoltat în comun de Mitsubishi Electric și NTT din Japonia. Publicat prima oară în 2000. Cheie de 256 de biți, blocuri de 128 de biți. Modul de operare este XTS. A fost aprobat pentru utilizare de către ISO/IEC, proiectul NESSIE al Uniunii Europene și de proiectul japonez CRYPTREC.</entry>
@@ -1403,8 +1403,8 @@
     <entry lang="ro" key="ITERATIONS">Iterații</entry>
     <entry lang="ro" key="PRE-BOOT">Pornire</entry>
     <entry lang="ro" key="RESCUE_DISK_EFI_INFO">Înainte de a putea cripta partiția, trebuie să creați un Disc de Recuperare VeraCrypt (DRV), ce va servi următoarelor scopuri:\n\n- Dacă VeraCrypt Boot Loader, cheia principală sau alte date critice sunt distruse, DRV vă va permite să le restaurați (cu toate acestea, încă va trebui să introduceți parola corectă).\n\n- Dacă Windows este corupt și nu poate porni, DRV permite decriptarea permanentă a partiției înainte de pornirea Windows.\n\n- DRV va conține o copie a EFI boot loader și vă va permite să-l restaurați dacă e necesar.\n\nFișierul ZIP al imaginii Discului de Recuperare VeraCrypt va fi creat la destinația specificată mai jos.</entry>
-    <entry lang="ro" key="RESCUE_DISK_EFI_EXTRACT_INFO">Fișierul ZIP al imaginii Discului de recuperare a fost creat și stocat în acest fișier:\n%s\n\nAcum va trebui să-l extrageți pe un dispozitiv USB care este formatat ca FAT/FAT32.\n\n%lsDupă ce ați creat Discul de Recuperare, apăsați pe «Înainte» pentru a verifica dacă a fost creat corect.</entry>
-    <entry lang="ro" key="RESCUE_DISK_EFI_EXTRACT_INFO_NO_CHECK">Fișierul ZIP al imaginii Discului de recuperare a fost creat și stocat în acest fișier:\n%s\n\nAcum va trebui fie să-l extrageți pe o unitate USB care este formatată ca FAT/FAT32 sau să-l mutați într-un loc sigur pentru o utilizare ulterioară.\n\n%lsApăsați pe «Înainte» pentru a continua.</entry>
+    <entry lang="ro" key="RESCUE_DISK_EFI_EXTRACT_INFO">Fișierul ZIP al imaginii discului de recuperare a fost creat și stocat în acest fișier:\n%s\n\nAcum va trebui să-l extrageți pe un dispozitiv USB care este formatat ca FAT/FAT32.\n\n%lsDupă ce ați creat discul de recuperare, apăsați pe «Înainte» pentru a verifica dacă a fost creat corect.</entry>
+    <entry lang="ro" key="RESCUE_DISK_EFI_EXTRACT_INFO_NO_CHECK">Fișierul ZIP al imaginii discului de recuperare a fost creat și stocat în acest fișier:\n%s\n\nAcum va trebui fie să-l extrageți pe o unitate USB care este formatată ca FAT/FAT32 sau să-l mutați într-un loc sigur pentru o utilizare ulterioară.\n\n%lsApăsați pe «Înainte» pentru a continua.</entry>
     <entry lang="ro" key="RESCUE_DISK_EFI_EXTRACT_INFO_NOTE">IMPORTANT: fișierul zip trebuie extras direct în rădăcina unității USB. De exemplu, dacă litera unității USB este E:, atunci extrăgând arhiva zip ar trebui să fie creat un folder E:\\EFI pe unitatea USB.\n\n</entry>
     <entry lang="ro" key="RESCUE_DISK_EFI_CHECK_FAILED">Nu se poate verifica dacă discul de recuperare a fost extras corect.\n\nDacă ați extras discul de recuperare, scoateți și reintroduceți dispozitivul USB; apoi apăsați pe «Înainte» pentru a reîncerca. Dacă nici acum nu funcționează, încercați cu alt dispozitiv USB sau alt program de dezarhivare.\n\nDacă nu ați extras încă discul de recuperare, atunci extrageți-l acum și apoi apăsați pe «Înainte».\n\nDacă ați încercat să verificați un Disc de Recuperare VeraCrypt creat înainte de a porni acest asistent, un astfel de disc nu poate fi utilizat, deoarece a fost creat pentru o cheie principală diferită. Trebuie să extrageți noua imagine zip a discului de recuperare generat.</entry>
     <entry lang="ro" key="RESCUE_DISK_EFI_NON_WIZARD_CHECK_FAILED">Nu se poate verifica dacă discul de recuperare a fost extras corect.\n\nDacă ați extras imaginea discului de recuperare pe un dispozitiv USB, scoateți-l și reintroduceți-l; apoi reîncercați. Dacă nici acum nu funcționează, încercați cu alt dispozitiv USB sau program de dezarhivare.\n\nDacă ați încercat să verificați un Disc de Recuperare VeraCrypt creat pentru o cheie principală, parolă etc. diferite, un astfel de disc va eșua întotdeauna la verificare. Pentru a crea un nou disc de recuperare complet compatibil cu configurația curentă, selectați „Sistem” > „Creare disc de recuperare”.</entry>
@@ -1418,7 +1418,7 @@
     <entry lang="ro" key="EDIT_DCSPROP_FOR_ADVANCED_ONLY">ATENȚIE: utilizatorii neexperimentați nu ar trebui să încerce editarea manuală a configurației încărcătorului de sistem.\n\nContinuați?</entry>
     <entry lang="ro" key="DCSPROP_XML_VALIDATION_FAILED">ATENȚIE: eșuare la validarea formatului XML al încărcătorului de sistem. Verificați modificările efectuate.</entry>
     <entry lang="ro" key="IDT_ADVANCED_OPTIONS">Opțiuni avansate</entry>
-    <entry lang="ro" key="AFTER_UPGRADE_RESCUE_DISK">Este recomandată crearea unui disc de recuperare Veracrypt nou (ce va conține noua versiune a încărcătorului Veracrypt) selectând „Sistem” > „Creare disc de recuperare”.\nDoriți crearea lui acum?</entry>
+    <entry lang="ro" key="AFTER_UPGRADE_RESCUE_DISK">Este recomandată crearea unui disc de recuperare VeraCrypt nou (ce va conține noua versiune a încărcătorului VeraCrypt) selectând „Sistem” > „Creare disc de recuperare”.\nDoriți crearea lui acum?</entry>
     <entry lang="ro" key="IDC_ALLOW_TRIM_NONSYS_SSD">Permitere comandă TRIM pentru partițiile/unitățile non-sistem SSD</entry>
     <entry lang="ro" key="IDC_BLOCK_SYSENC_TRIM">Blocare comandă TRIM pe partițiile/unitățile sistem</entry>
     <entry lang="ro" key="WINDOWS_EFI_BOOT_LOADER_MISSING">EROARE: încărcătorul de sistem Windows EFI nu a fost găsit pe disc. Operația va fi anulată.</entry>
@@ -1428,13 +1428,13 @@
     <entry lang="ro" key="IDC_SELECT_LANGUAGE_LABEL">Selectați limba folosită la instalare:</entry>
     <entry lang="ro" key="VOLUME_TOO_LARGE_FOR_HOST">EROARE: mărimea fișierului container este mai mare decât spațiul liber disponibil.</entry>
     <entry lang="ro" key="IDC_ALLOW_WINDOWS_DEFRAG">Permitere program de defragmentare din Windows să defragmenteze partițiile/unitățile nonsistem</entry>
-    <entry lang="ro" key="CONFIRM_ALLOW_WINDOWS_DEFRAG">ATENȚIE: defragmentarea partițiilor/unităților nonsistem pot dezvălui metadate despre conținut sau să creeze probleme cu volumele ascunse pe care le-ar putea conține.\n\nContinuare?</entry>
+    <entry lang="ro" key="CONFIRM_ALLOW_WINDOWS_DEFRAG">ATENȚIE: defragmentarea partițiilor/unităților nonsistem pot dezvălui metadate despre conținut sau să creeze probleme cu volumele ascunse pe care le-ar putea conține.\n\nContinuați?</entry>
     <entry lang="ro" key="VIRTUAL_DEVICE">Dispozitiv virtual</entry>
     <entry lang="ro" key="MOUNTED_VOLUME_NOT_ASSOCIATED">Volumul montat selectat nu este asociat cu litera sa din Windows astfel încât nu poate fi deschis în Windows Explorer.</entry>
     <entry lang="ro" key="IDC_CLEAR_KEYS_ON_NEW_DEVICE_INSERTION">Golire chei de criptare din memorie dacă este inserat un nou dispozitiv</entry>
     <entry lang="ro" key="CLEAR_KEYS_ON_DEVICE_INSERTION_WARNING">NOTE IMPORTANTE:\n - Această opțiune nu va persista după oprire/repornire astfel că va trebui reselectată la următoarea pornire a sistemului.\n\n - Cu această opțiune activată și după conectarea unui dispozitiv, sistemul va îngheța și eventual se va bloca cu afișarea ecranului albastru deoarece Windows nu poate accesa discul criptat după ce cheile sunt golite din memorie.\n</entry>
     <entry lang="ro" key="STARTING">Pornire</entry>
-    <entry lang="ro" key="IDC_ENABLE_CPU_RNG">Folosire generator hardware aleator al procesorului ca sursă adițională de entropie</entry>
+    <entry lang="ro" key="IDC_ENABLE_CPU_RNG">Folosire generator hardware aleatoriu al procesorului ca sursă adițională de entropie</entry>
     <entry lang="ro" key="IDC_USE_LEGACY_MAX_PASSWORD_LENGTH">Folosire lungime maximă parolă clasică (64 de caractere)</entry>
     <entry lang="ro" key="IDC_ENABLE_RAM_ENCRYPTION">Activare criptare chei și parole stocate în RAM</entry>
     <entry lang="ro" key="IDT_BENCHMARK">Evaluare:</entry>
@@ -1454,7 +1454,7 @@
     <entry lang="ro" key="TASKICON_PREF_MENU_ITEMS">Pictogramă activitate elemente meniu</entry>
     <entry lang="ro" key="TASKICON_PREF_OPEN_VOL">Deschidere volume montate</entry>
     <entry lang="ro" key="TASKICON_PREF_UNMOUNT_VOL">Demontare volume montate</entry>
-    <entry lang="ro" key="DISK_FREE">Spațiu liber dispoanibil: {0}</entry>
+    <entry lang="ro" key="DISK_FREE">Spațiu liber disponibil: {0}</entry>
     <entry lang="ro" key="VOLUME_SIZE_HELP">Specificați dimensiunea containerului de creat. Rețineți că dimensiunea minimă posibilă a unui volum este de 292 KiB.</entry>
     <entry lang="ro" key="LINUX_CONFIRM_INNER_VOLUME_CALC">AVERTIZARE: ați selectat un alt sistem de fișiere decât FAT pentru volumul exterior.\nRețineți că, în acest caz, VeraCrypt nu poate calcula exact dimensiunea maximă permisă pentru volumul ascuns și va folosi doar o estimare care poate fi greșită.\nDe aceea, aveți responsabilitatea să utilizați o valoare adecvată pentru dimensiunea volumului ascuns, astfel încât să nu se suprapună cu volumul exterior.\n\nDoriți să continuați să utilizați sistemul de fișiere selectat pentru volumul exterior?</entry>
     <entry lang="ro" key="LINUX_PREF_TAB_SECURITY">Securitate</entry>
@@ -1520,13 +1520,13 @@
     <entry lang="ro" key="LINUX_ERROR_SIZE_HIDDEN_VOL">Eroare: volumul ascuns care trebuie creat este mai mare de {0} TiB ({1} GiB).\n\nSoluții posibile:\n- Creați un container/partiție mai mică de {0} TiB.\n</entry>
     <entry lang="ro" key="LINUX_MAX_SIZE_HINT">- Utilizați o unitate cu sectoare de 4096 de baiți pentru a putea crea volume ascunse de partiții/dispozitive găzduite de până la 16 TiB.</entry>
     <entry lang="ro" key="LINUX_DOT_LF">.\n</entry>
-    <entry lang="ro" key="LINUX_NOT_SUPPORTED"> (nesuportat de componenetele disponibile pe această platformă).\n</entry>
+    <entry lang="ro" key="LINUX_NOT_SUPPORTED"> (nesuportat de componentele disponibile pe această platformă).\n</entry>
     <entry lang="ro" key="LINUX_KERNEL_OLD">Sistemul folosește o versiune veche a nucleului Linux.\n\nDin cauza unei erori în nucleul Linux, este posibil ca sistemul să nu mai răspundă atunci când scrieți date pe un volum VeraCrypt. Această problemă poate fi rezolvată prin actualizarea nucleului la versiunea 2.6.24 sau o versiune ulterioară.</entry>
     <entry lang="ro" key="LINUX_VOL_UNMOUNTED">Volumul {0} a fost demontat.</entry>
     <entry lang="ro" key="LINUX_VOL_MOUNTED">Volumul {0} a fost montat.</entry>
     <entry lang="ro" key="LINUX_OOM">În afara memoriei.</entry>
     <entry lang="ro" key="LINUX_CANT_GET_ADMIN_PRIV">Eșuare obținere privilegii de administrare</entry>
-    <entry lang="ro" key="LINUX_COMMAND_GET_ERROR">Commanda {0} a returnat eroarea {1}.</entry>
+    <entry lang="ro" key="LINUX_COMMAND_GET_ERROR">Comanda {0} a returnat eroarea {1}.</entry>
     <entry lang="ro" key="LINUX_CMD_HELP">Ajutor comenzi VeraCrypt</entry>
     <entry lang="ro" key="LINUX_HIDDEN_FILES_PRESENT_IN_KEYFILE_PATH">\n\nAvertizare: în calea fișierului cheie există fișiere ascunse. Dacă trebuie să le folosiți ca fișiere-cheie, eliminați punctul de la începutul numelui fișierelor. Fișierele ascunse sunt vizibile numai dacă sunt activate în opțiunile de sistem.</entry>
     <entry lang="ro" key="LINUX_EX2MSG_DEVICESECTORSIZEMISMATCH">Dimensiunea sectorului volumului VC și a dispozitivul de stocare nu se potrivesc.</entry>
@@ -1535,7 +1535,7 @@
     <entry lang="ro" key="LINUX_EX2MSG_KERNELCRYPTOSERVICETESTFAILED">Testul serviciului criptografic al nucleului a eșuat. Cel mai probabil, serviciul criptografic al nucleului nu acceptă volume mai mari de 2 TiB.\n\nSoluții posibile:\n- Actualizați nucleul Linux la versiunea 2.6.33 sau o versiune ulterioară.\n- Dezactivați utilizarea serviciilor criptografice ale nucleului („Setări” > „Preferințe” > „Integrare sistem”) sau utilizați opțiunea de montare „nokernelcrypto” pe linia de comandă.</entry>
     <entry lang="ro" key="LINUX_EX2MSG_LOOPDEVICESETUPFAILED">Nu s-a putut configura un dispozitiv în buclă.</entry>
     <entry lang="ro" key="LINUX_EX2MSG_MISSINGARGUMENT">Lipsește un argument necesar.</entry>
-    <entry lang="ro" key="LINUX_EX2MSG_MISSINGVOLUMEDATA">Lipsesc datele volumlui.</entry>
+    <entry lang="ro" key="LINUX_EX2MSG_MISSINGVOLUMEDATA">Lipsesc datele volumului.</entry>
     <entry lang="ro" key="LINUX_EX2MSG_MOUNTPOINTREQUIRED">Este necesar punctul de montare.</entry>
     <entry lang="ro" key="LINUX_EX2MSG_MOUNTPOINTUNAVAILABLE">Punctul de montare este deja utilizat.</entry>
     <entry lang="ro" key="LINUX_EX2MSG_PASSWORDEMPTY">Nu s-a specificat o parolă sau fișier-cheie.</entry>
@@ -1580,7 +1580,7 @@
     <entry lang="ro" key="IDT_CURRENT_SIZE">Mărime actuală: </entry>
     <entry lang="ro" key="IDT_NEW_SIZE">Mărime nouă: </entry>
     <entry lang="ro" key="IDT_NEW_SIZE_BOX_TITLE">Introduceți noua dimensiune a volumului</entry>
-    <entry lang="ro" key="IDC_INIT_NEWSPACE">Umplere spațiu nou cu date aleatoare</entry>
+    <entry lang="ro" key="IDC_INIT_NEWSPACE">Umplere spațiu nou cu date aleatorii</entry>
     <entry lang="ro" key="IDC_QUICKEXPAND">Extindere rapidă</entry>
     <entry lang="ro" key="IDT_INIT_SPACE">Umplere spațiu nou: </entry>
     <entry lang="ro" key="EXPANDER_FREE_SPACE">%s spațiu disponibil pe unitatea gazdă</entry>
@@ -1592,7 +1592,7 @@
     <entry lang="ro" key="EXPANDER_FINISH_ERROR">Eroare: extinderea volumului a eșuat.</entry>
     <entry lang="ro" key="EXPANDER_FINISH_ABORT">Eroare: operație anulată de către utilizator.</entry>
     <entry lang="ro" key="EXPANDER_FINISH_OK">Finalizat. S-a reușit extinderea volumului.</entry>
-    <entry lang="ro" key="EXPANDER_CANCEL_WARNING">Avertizare: extinderea volumului este în desfășurare!\n\nOprind-o acum poate determina deterioarea volumului.\n\nSigur doriți să anulați?</entry>
+    <entry lang="ro" key="EXPANDER_CANCEL_WARNING">Avertizare: extinderea volumului este în desfășurare!\n\nOprind-o acum poate determina deteriorarea volumului.\n\nSigur doriți să anulați?</entry>
     <entry lang="ro" key="EXPANDER_STARTING_STATUS">Începere extindere volum...\n</entry>
     <entry lang="ro" key="EXPANDER_HIDDEN_VOLUME_ERROR">Un volum exterior care conține un volum ascuns nu poate fi extins, deoarece acesta distruge volumul ascuns.\n</entry>
     <entry lang="ro" key="EXPANDER_SYSTEM_VOLUME_ERROR">Un volum de sistem VeraCrypt nu poate fi extins.</entry>
@@ -1634,7 +1634,7 @@
     <entry lang="ro" key="PARTIAL_SYSENC_MOUNT_READONLY">Avertizare: Partiția de sistem pe care ați încercat să o montați nu a fost criptată în întregime. Ca măsură de siguranță pentru a preveni o potențială corupere sau modificări nedorite, volumul „%s” a fost montat doar în mod citire.</entry>
     <entry lang="ro" key="IDC_LINK_KEYFILES_EXTENSIONS_WARNING">Informații importante despre utilizarea extensiilor de fișiere terță parte</entry>
     <entry lang="ro" key="IDC_DISABLE_MEMORY_PROTECTION">Dezactivare protecție memorie pentru compatibilitate unelte de accesibilitate</entry>
-    <entry lang="ro" key="DISABLE_MEMORY_PROTECTION_WARNING">AVERTIZARE: dezactivarea protecției memoriei reduce significant securitatea. Activați această opțiune NUMAI dacă aveți de nevoie de uneltele de accesibilitate, cum ar fi naratoarele, pentru a interacționa cu interfața VeraCrypt.</entry>
+    <entry lang="ro" key="DISABLE_MEMORY_PROTECTION_WARNING">AVERTIZARE: dezactivarea protecției memoriei reduce semnificativ securitatea. Activați această opțiune NUMAI dacă aveți de nevoie de uneltele de accesibilitate, cum ar fi naratoarele, pentru a interacționa cu interfața VeraCrypt.</entry>
     <entry lang="ro" key="LINUX_LANGUAGE">Limba</entry>
     <entry lang="ro" key="LINUX_SELECT_SYS_DEFAULT_LANG">Selectați limba implicită a sistemului</entry>
     <entry lang="ro" key="LINUX_RESTART_FOR_LANGUAGE_CHANGE">Pentru a se aplica modificarea limbii, VeraCrypt trebuie repornit.</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="ro" key="INSECURE_MODE">[MOD INSECURIZAT]</entry>
     <entry lang="ro" key="IDC_DISABLE_SCREEN_PROTECTION">Dezactivare protecție împotriva capturilor de ecran și a înregistrării ecranului</entry>
     <entry lang="ro" key="DISABLE_SCREEN_PROTECTION_WARNING">AVERTIZARE: Dezactivarea protecției ecranului reduce semnificativ securitatea. Activați această opțiune NUMAI dacă aveți o nevoie specifică de a captura interfața VeraCrypt. Aceasta poate expune date sensibile aplicațiilor de captură de ecran și funcțiilor de înregistrare a ecranului, precum Windows 11 Recall.</entry>
+    <entry lang="ro" key="MEMORY_COST">Consum de memorie</entry>
+    <entry lang="ro" key="IDT_KDF_ALGO">Algoritm KDF</entry>
+    <entry lang="ro" key="IDD_PREFERENCES_TAB_GENERAL">Generale</entry>
+    <entry lang="ro" key="IDD_PREFERENCES_TAB_ACTIONS">Acțiuni</entry>
+    <entry lang="ro" key="IDD_PREFERENCES_TAB_PASSWORD">Parola</entry>
+    <entry lang="ro" key="IDC_SECURE_DESKTOP_ENABLE_IME">Activare editor metodă de intrare (IME) în desktop-ul securizat</entry>
+    <entry lang="ro" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">AVERTIZARE: Activați această opțiune doar dacă aveți probleme în a selecta token-uri/fișiere cheie când folosiți desktop-ul securizat.</entry>
+    <entry lang="ro" key="ERR_KEY_DERIVATION_FAILED">Derivarea cheii a eșuat. Acest lucru poate fi cauzat de memorie insuficientă sau de o operațiune întreruptă.</entry>
+    <entry lang="ro" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">Partiția/unitatea de sistem este deja decriptată, dar calea către încărcătorul de boot EFI Microsoft nu a fost restaurată în Windows Boot Manager. Doar fișierele de boot EFI necesită reparare. Utilizați opțiunea de reparare din Discul de Recuperare VeraCrypt sau porniți mediul de recuperare Windows și executați „bcdboot W:\\Windows /s S: /f UEFI” după ce înlocuiți W: cu litera unității de volum Windows și S: cu litera unității partiției de sistem EFI. Cale:</entry>
+    <entry lang="ro" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">Partiția/unitatea de sistem este deja decriptată, dar calea încărcătorului de boot EFI de rezervă conține încă încărcătorul de boot VeraCrypt. Doar fișierele de boot EFI necesită reparare. Utilizați opțiunea de reparare din Discul de Recuperare VeraCrypt sau porniți mediul de recuperare Windows și executați „bcdboot W:\\Windows /s S: /f UEFI” după ce înlocuiți W: cu litera unității de volum Windows și S: cu litera unității partiției de sistem EFI. Cale:</entry>
+    <entry lang="ro" key="IDM_REPAIR_EFI_BOOT_LOADER">Reparare încărcător boot EFI...</entry>
+    <entry lang="ro" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt va restaura căile încărcătorului de boot Windows EFI și va elimina intrările și fișierele de boot VeraCrypt EFI.\n\nUtilizați această opțiune numai după ce partiția/unitatea de sistem este complet decriptată și Windows poate porni fără criptarea sistemului.\n\nDoriți să continuați?</entry>
+    <entry lang="ro" key="EFI_BOOT_LOADER_FILE_READ_FAILED">Fișierul încărcătorului de boot EFI nu a putut fi citit complet:</entry>
+    <entry lang="ro" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">Fișierul încărcătorului de boot EFI este neașteptat de mare și nu a fost inspectat:</entry>
+    <entry lang="ro" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">Partiția/unitatea de sistem este deja decriptată și fișierele încărcătorului de boot EFI au fost restaurate, dar VeraCrypt nu a putut elimina una sau mai multe intrări de pornire VeraCrypt din firmware. Fișierele VeraCrypt EFI au fost lăsate la locul lor, așa că orice intrare din firmware rămasă indică în continuare un încărcător existent. Încercați din nou ca administrator sau eliminați intrarea de pornire VeraCrypt din configurarea firmware-ului după ce confirmați că Windows Boot Manager pornește normal.</entry>
+    <entry lang="ro" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">Încărcătorul de boot EFI nu poate fi reparat în timp ce criptarea sau decriptarea sistemului este activă sau incompletă. Finalizați sau reluați procesul de criptare/decriptare a sistemului în așteptare înainte de a reîncerca.</entry>
+    <entry lang="ro" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">Această acțiune de reparare este disponibilă numai pe sistemele care pornesc în modul UEFI de pe o partiție de sistem GPT.</entry>
+    <entry lang="ro" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">Încărcătorul EFI a fost reparat cu succes.</entry>
+    <entry lang="ro" key="PIM_ARGON2_HELP">MIP (Multiplicatorul Iterațiilor Personal) controlează costurile de memorie și timp utilizate de derivarea cheii antetului Argon2id după cum urmează:\n      Memorie = min(64 MiB + ((MIP - 1) x 32 MiB), 1024 MiB)\n      Iterații = 3 + ((MIP - 1) / 3) pentru MIP 31 sau mai mic, apoi 13 + (MIP - 31)\n\nCând este lăsat gol sau setat la 0, VeraCrypt va utiliza MIP Argon2 implicit (12), care utilizează 416 MiB de memorie și 6 iterații.\n\nCând parola are mai puțin de 20 de caractere, MIP Argon2 nu poate fi mai mic de 12 pentru a menține un nivel minim de securitate.\nCând parola are 20 de caractere sau mai mult, MIP Argon2 poate fi setat la orice valoare.\n\nUn MIP Argon2 mai mare de 12 crește utilizarea memoriei până la 1024 MiB și apoi crește iterațiile. Aceasta va duce la o montare mai lentă. Un MIP Argon2 mic (mai puțin de 12) va duce la o montare mai rapidă, dar poate reduce securitatea dacă parola nu este suficient de puternică.</entry>
+    <entry lang="ro" key="PIM_ARGON2_LARGE_WARNING">Ați ales o valoare MIP Argon2 mai mare decât valoarea implicită din VeraCrypt.\nAcest lucru poate necesita mai multă memorie și poate duce la o montare mult mai lentă.</entry>
+    <entry lang="ro" key="PIM_ARGON2_SMALL_WARNING">Ați ales o valoare MIP Argon2 mai mică decât valoarea implicită din VeraCrypt. Dacă parola nu este suficient de puternică, acest lucru ar putea duce la o securitate mai slabă.\n\nConfirmați că utilizați o parolă puternică?</entry>
+    <entry lang="ro" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Parola trebuie să conțină 20 sau mai multe caractere pentru a utiliza valoarea MIP Argon2 specificată. Parolele mai scurte pot fi utilizate numai dacă valoarea MIP Argon2 este 12 sau mai mare.</entry>
+    <entry lang="ro" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Montare volume NTFS cu driverul ntfs3 din kernelul Linux</entry>
+    <entry lang="ro" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Doar în Linux. Când este activat, VeraCrypt verifică dispozitivul virtual decriptat cu blkid -p și montează sistemele de fișiere NTFS detectate cu ntfs3 în loc de implementarea NTFS implicită. Dacă detectarea NTFS eșuează, VeraCrypt utilizează selecția automată normală a sistemului de fișiere. Dacă ntfs3 nu este disponibil sau este blocat de distribuție, montarea poate eșua. Această posibilitate de alegere poate evita blocările în suspendare sau hibernare cauzate de sistemele de fișiere FUSE înghețate în spațiul utilizatorului.</entry>
+    <entry lang="ro" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Demontarea normală a volumului {0} a eșuat. Aceasta poate apărea când aplicațiile au încă fișiere sau foldere deschise pe volum sau când dispozitivul respectiv a fost deconectat și montarea a devenit învechită.\n\nDacă dispozitivul este încă conectat, alegeți Nu, închideți aplicațiile care folosesc volumul și reîncercați demontarea.\n\nDacă dispozitivul a fost deconectat sau montarea este învechită, VeraCrypt poate încerca curățarea de urgență prin detașarea întârziată a sistemului de fișiere și eliminarea sau programarea eliminării obiectelor nucleului VeraCrypt. Scrierile în așteptare ar putea eșua, datele s-ar putea pierde, iar curățarea ar putea rămâne în așteptare până când aplicațiile închid fișierele deschise. Verificați sistemul de fișiere cu fsck sau cu instrumentul de reparare corespunzător înainte de a-l utiliza din nou.\n\nContinuați?</entry>
+    <entry lang="ro" key="LINUX_EMERGENCY_UNMOUNTED">Curățarea de urgență pentru volumul {0} a fost inițiată. Dacă volumul a fost deconectat, montarea era învechită sau existau scrieri în așteptare, verificați sistemul de fișiere cu fsck sau cu instrumentul de reparare corespunzător înainte de a-l reutiliza.</entry>
+    <entry lang="ro" key="FORMAT_STAGE_WRITING_DATA">Se creează datele volumului. Așteptați.</entry>
+    <entry lang="ro" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Se finalizează crearea volumului: se scrie antetul de rezervă.</entry>
+    <entry lang="ro" key="FORMAT_STAGE_FLUSHING_DATA">Se finalizează crearea volumului: se trimit datele pe disc. Acest lucru poate dura câteva minute pe volume mari sau stocare lentă/USB.</entry>
+    <entry lang="ro" key="FORMAT_STAGE_FINISHED">Se finalizează crearea volumului.</entry>
+    <entry lang="ro" key="FORMAT_STAGE_ABORTED">Crearea volumului a fost întreruptă.</entry>
+    <entry lang="ro" key="FORMAT_STAGE_ERROR">Crearea volumului a eșuat.</entry>
+    <entry lang="ro" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Se finalizează crearea volumului: se montează volumul temporar.</entry>
+    <entry lang="ro" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Se finalizează crearea volumului: se pregătește dispozitivul temporar.</entry>
+    <entry lang="ro" key="FORMAT_STAGE_CREATING_FILESYSTEM">Se finalizează crearea volumului: se creează sistemul de fișiere folosind {0}.</entry>
+    <entry lang="ro" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Se finalizează crearea volumului: se demontează volumul temporar.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.ru.xml

@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
-    <language langid="ru" name="Русский" en-name="Russian" version="1.26.24" translators="Dmitry Yerokhin [erodim@mail.ru] (240826)" />
+  <localization prog-version="1.26.28">
+    <language langid="ru" name="Русский" en-name="Russian" version="1.26.24" translators="Dmitry Yerokhin [erodim@mail.ru] (250601)" />
     <font lang="ru" class="normal" size="11" face="default" />
     <font lang="ru" class="bold" size="13" face="Arial" />
     <font lang="ru" class="fixed" size="12" face="Lucida Console" />
@@ -291,8 +291,8 @@
     <entry lang="ru" key="IDT_NEW_PASSWORD">Пароль:</entry>
     <entry lang="ru" key="IDT_PARALLELIZATION_OPTIONS">Потоковое распараллеливание</entry>
     <entry lang="ru" key="IDT_PKCS11_LIB_PATH">Путь к библиотеке PKCS #11</entry>
-    <entry lang="ru" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="ru" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="ru" key="IDT_KDF">KDF:</entry>
+    <entry lang="ru" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="ru" key="IDT_PW_CACHE_OPTIONS">Кэширование (запоминание) паролей</entry>
     <entry lang="ru" key="IDT_SECURITY_OPTIONS">Параметры безопасности</entry>
     <entry lang="ru" key="IDT_EMV_OPTIONS">Параметры EMV</entry>
@@ -813,7 +813,7 @@
     <entry lang="ru" key="SECONDARY_KEY_SIZE_LRW">Длина Tweak-ключа (режим LRW)</entry>
     <entry lang="ru" key="BITS">бит</entry>
     <entry lang="ru" key="BLOCK_SIZE">Размер блока</entry>
-    <entry lang="ru" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="ru" key="KDF">KDF</entry>
     <entry lang="ru" key="PKCS5_ITERATIONS">Число итераций PKCS-5</entry>
     <entry lang="ru" key="VOLUME_CREATE_DATE">Том создан</entry>
     <entry lang="ru" key="VOLUME_HEADER_DATE">Последнее изменение заголовка</entry>
@@ -1645,7 +1645,48 @@
     <entry lang="ru" key="MOUNTPOINT_NOTALLOWED">ОШИБКА: Точка монтирования тома не разрешена, так как она переопределяет папку, которая является частью переменной среды PATH.\n\nВыберите другую точку монтирования.</entry>
     <entry lang="ru" key="INSECURE_MODE">[НЕБЕЗОПАСНЫЙ РЕЖИМ]</entry>
     <entry lang="ru" key="IDC_DISABLE_SCREEN_PROTECTION">Отключить защиту от создания скриншотов и записи экрана</entry>
-    <entry lang="ru" key="DISABLE_SCREEN_PROTECTION_WARNING">ВНИМАНИЕ: Отключение защиты экрана значительно снижает уровень безопасности. Включайте эту опцию ТОЛЬКО при наличии конкретной необходимости захвата интерфейса VeraCrypt. Это может привести к утечке конфиденциальных данных через инструменты создания скриншотов и записи экрана, такие как Windows 11 Recall.</entry>
+    <entry lang="ru" key="DISABLE_SCREEN_PROTECTION_WARNING">ВНИМАНИЕ: Отключение защиты экрана значительно снижает уровень безопасности. Включайте эту опцию ТОЛЬКО при реальной необходимости сделать снимок экрана с интерфейсом VeraCrypt. Это может привести к утечке конфиденциальных данных через средства создания скриншотов и записи экрана, такие как Recall в Windows 11.</entry>
+    <entry lang="ru" key="MEMORY_COST">Затраты памяти</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="ru" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Монтировать тома NTFS с помощью драйвера ntfs3 ядра Linux</entry>
+    <entry lang="ru" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Только Linux. Если включено, VeraCrypt проверяет расшифрованное виртуальное устройство с помощью blkid -p и монтирует обнаруженные файловые системы NTFS с помощью драйвера ntfs3 вместо стандартного NTFS-бэкенда. Если NTFS не удалось определить, VeraCrypt использует обычный автоматический выбор файловой системы. Если ntfs3 недоступен или заблокирован дистрибутивом, монтирование может завершиться ошибкой. Эта необязательная настройка может предотвратить зависания при ждущем режиме или гибернации из-за замороженных файловых систем FUSE, работающих в пользовательском пространстве.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.sk.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="sk" name="Slovenčina" en-name="Slovak" version="0.1.0" translators="Kamil David" />
     <font lang="sk" class="normal" size="11" face="default" />
     <font lang="sk" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="sk" key="IDT_NEW_PASSWORD">Heslo:</entry>
     <entry lang="en" key="IDT_PARALLELIZATION_OPTIONS">Thread-Based Parallelization</entry>
     <entry lang="en" key="IDT_PKCS11_LIB_PATH">PKCS #11 Library Path</entry>
-    <entry lang="sk" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="en" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="sk" key="IDT_KDF">KDF:</entry>
+    <entry lang="en" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="sk" key="IDT_PW_CACHE_OPTIONS">Medzipamäť pre hesla</entry>
     <entry lang="en" key="IDT_SECURITY_OPTIONS">Security Options</entry>
     <entry lang="en" key="IDT_EMV_OPTIONS">EMV Options</entry>
@@ -813,7 +813,7 @@
     <entry lang="en" key="SECONDARY_KEY_SIZE_LRW">Tweak Key Size (LRW Mode)</entry>
     <entry lang="sk" key="BITS">bitov</entry>
     <entry lang="sk" key="BLOCK_SIZE">Veľkosť bloku</entry>
-    <entry lang="sk" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="sk" key="KDF">KDF</entry>
     <entry lang="sk" key="PKCS5_ITERATIONS">PKCS-5 počet iterácií</entry>
     <entry lang="sk" key="VOLUME_CREATE_DATE">Oddiel bol vytvorený</entry>
     <entry lang="sk" key="VOLUME_HEADER_DATE">Hlavička bola naposledy zmenená</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="en" key="INSECURE_MODE">[INSECURE MODE]</entry>
     <entry lang="en" key="IDC_DISABLE_SCREEN_PROTECTION">Disable protection against screenshots and screen recording</entry>
     <entry lang="en" key="DISABLE_SCREEN_PROTECTION_WARNING">WARNING: Disabling screen protection significantly reduces security. Enable this option ONLY if you have a specific need to capture VeraCrypt's interface. This may expose sensitive data to screenshot tools and screen recording features such as Windows 11 Recall.</entry>
+    <entry lang="en" key="MEMORY_COST">Memory Cost</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.sl.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="sl" name="Slovenščina" en-name="Slovenian" version="0.1.0" translators="Erik David Salam, Sasa Divjak" />
     <font lang="sl" class="normal" size="11" face="default" />
     <font lang="sl" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="sl" key="IDT_NEW_PASSWORD">Geslo:</entry>
     <entry lang="sl" key="IDT_PARALLELIZATION_OPTIONS">Paralelizacija z nitmi</entry>
     <entry lang="sl" key="IDT_PKCS11_LIB_PATH">PKCS #11 mesto knjižice</entry>
-    <entry lang="sl" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="sl" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="sl" key="IDT_KDF">KDF:</entry>
+    <entry lang="sl" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="sl" key="IDT_PW_CACHE_OPTIONS">Predpomnilniška gesla</entry>
     <entry lang="sl" key="IDT_SECURITY_OPTIONS">Varnostne možnosti</entry>
     <entry lang="sl" key="IDT_EMV_OPTIONS">Opcije EMV</entry>
@@ -813,7 +813,7 @@
     <entry lang="sl" key="SECONDARY_KEY_SIZE_LRW">Prilagodi velikost ključa (način LRW)</entry>
     <entry lang="sl" key="BITS">bitov</entry>
     <entry lang="sl" key="BLOCK_SIZE">Velikost bloka</entry>
-    <entry lang="sl" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="sl" key="KDF">KDF</entry>
     <entry lang="sl" key="PKCS5_ITERATIONS">PKCS-5 število iteracij</entry>
     <entry lang="sl" key="VOLUME_CREATE_DATE">Nosilec je ustvarjen</entry>
     <entry lang="sl" key="VOLUME_HEADER_DATE">Zadnja sprememba glave</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="sl" key="INSECURE_MODE">[NEVAREN NACIN]</entry>
     <entry lang="sl" key="IDC_DISABLE_SCREEN_PROTECTION">Onemogoči zaščito pred zajemanjem zaslona in snemanjem zaslona</entry>
     <entry lang="sl" key="DISABLE_SCREEN_PROTECTION_WARNING">OPOZORILO: Onemogočanje zaščite zaslona bistveno zmanjša varnost. Omogoči to možnost SAMO, če imaš poseben razlog za zajem uporabniškega vmesnika VeraCrypt. S tem lahko občutljivi podatki postanejo dostopni orodjem za zajem zaslona in funkcijam snemanja zaslona, kot je Windows 11 Recall.</entry>
+    <entry lang="sl" key="MEMORY_COST">Poraba pomnilnika</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.sv.xml

@@ -1,6 +1,6 @@
-<?xml version="1.0" encoding="utf-8"?>
+<?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="sv" name="Svenska" en-name="Swedish" version="1.0.0" translators="Peter Runesson" />
     <font lang="sv" class="normal" size="11" face="default" />
     <font lang="sv" class="bold" size="13" face="Arial" />
@@ -47,7 +47,7 @@
     <entry lang="sv" key="IDC_KEY_FILES">N&amp;yckelfiler...</entry>
     <entry lang="sv" key="IDC_LINK_HASH_INFO">Information om hashalgoritmer</entry>
     <entry lang="sv" key="IDC_LINK_MORE_INFO_ABOUT_CIPHER">Mer information</entry>
-    <entry lang="sv" key="IDC_LINK_PIM_INFO">Information on PIM</entry>
+    <entry lang="sv" key="IDC_LINK_PIM_INFO">Information om PIM</entry>
     <entry lang="sv" key="IDC_MB">&amp;MiB</entry>
     <entry lang="sv" key="IDC_MORE_INFO_ON_CONTAINERS">Mer information</entry>
     <entry lang="sv" key="IDC_MORE_INFO_ON_SYS_ENCRYPTION">Mer information om systemkryptering</entry>
@@ -194,13 +194,13 @@
     <entry lang="sv" key="IDD_PERFORMANCE_SETTINGS">VeraCrypt - Prestanda och drivrutinsalternativ</entry>
     <entry lang="sv" key="IDD_PREFERENCES_DLG">VeraCrypt - Preferenser</entry>
     <entry lang="sv" key="IDD_SYSENC_SETTINGS">VeraCrypt - Systemkrypteringsinställningar</entry>
-    <entry lang="sv" key="IDD_TOKEN_PREFERENCES">VeraCrypt - Säkerhetstokenpreferenser</entry>
+    <entry lang="sv" key="IDD_TOKEN_PREFERENCES">VeraCrypt - Preferenser för säkerhetstoken</entry>
     <entry lang="sv" key="IDD_TRAVELER_DLG">VeraCrypt Resenär-diskinställning</entry>
     <entry lang="sv" key="IDD_VOLUME_PROPERTIES">VeraCrypt-volymegenskaper</entry>
     <entry lang="sv" key="IDM_ABOUT">Om</entry>
     <entry lang="sv" key="IDM_ADD_REMOVE_VOL_KEYFILES">Lägg till/ta bort nyckelfiler till/från volym...</entry>
     <entry lang="sv" key="IDM_ADD_VOLUME_TO_FAVORITES">Lägg till monterad volym till favoriter...</entry>
-    <entry lang="sv" key="IDM_ADD_VOLUME_TO_SYSTEM_FAVORITES">Lägg till monterad volym till favoriter...</entry>
+    <entry lang="sv" key="IDM_ADD_VOLUME_TO_SYSTEM_FAVORITES">Lägg till monterad volym till systemfavoriter...</entry>
     <entry lang="sv" key="IDM_ANALYZE_SYSTEM_CRASH">Analysera en systemkrasch...</entry>
     <entry lang="sv" key="IDM_BACKUP_VOL_HEADER">Säkerhetskopiera volymhuvud...</entry>
     <entry lang="sv" key="IDM_BENCHMARK">Prestandamätning...</entry>
@@ -291,8 +291,8 @@
     <entry lang="sv" key="IDT_NEW_PASSWORD">Lösenord:</entry>
     <entry lang="sv" key="IDT_PARALLELIZATION_OPTIONS">Trådbaserad parallellism</entry>
     <entry lang="sv" key="IDT_PKCS11_LIB_PATH">PKCS #11-bibliotekssökväg</entry>
-    <entry lang="sv" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="sv" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="sv" key="IDT_KDF">KDF:</entry>
+    <entry lang="sv" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="sv" key="IDT_PW_CACHE_OPTIONS">Lösenordscache</entry>
     <entry lang="sv" key="IDT_SECURITY_OPTIONS">Säkerhetsalternativ</entry>
     <entry lang="sv" key="IDT_EMV_OPTIONS">EMV-alternativ</entry>
@@ -447,7 +447,7 @@
     <entry lang="sv" key="DISK_FREE_PB">Ledigt utrymme på enheten %s är %.2f PiB</entry>
     <entry lang="sv" key="DRIVELETTERS">Det gick inte att hämta tillgängliga enhetsbokstäver.</entry>
     <entry lang="sv" key="DRIVER_NOT_FOUND">Fel: VeraCrypt-drivrutinen hittades inte.\n\nKopiera filerna "veracrypt.sys" och "veracrypt-x64.sys" till mappen där huvudapplikationen VeraCrypt (VeraCrypt.exe) finns.</entry>
-    <entry lang="sv" key="DRIVER_VERSION">Fel: En inkompatibel version av VeraCrypt-drivrutinen körs för närvarande.\n\nOm du försöker köra VeraCrypt i portabelt läge (dvs. utan att installera det) och en annan version av VeraCrypt redan är installerad måste du avinstallera den först (eller uppgradera) den med VeraCrypt-installationsprogrammet). För att avinstallera det, följ dessa steg: I Windows Vista eller senare, välj "Start-meny" &gt; Dator > "Avinstallera eller ändra ett program" &gt; VeraCrypt > Avinstallera; i Windows XP, välj "Start-meny" &gt; Inställningar > "Kontrollpanelen" &gt; "Lägg till eller ta bort program" &gt; VeraCrypt > Ta bort.\n\nPå liknande sätt, om du försöker köra VeraCrypt i portabelt läge (dvs. utan att installera det) och en annan version av VeraCrypt körs redan i portabelt läge, måste du starta om systemet först och sedan köra endast denna nya version.</entry>
+    <entry lang="sv" key="DRIVER_VERSION">Fel: En inkompatibel version av VeraCrypt-drivrutinen körs för närvarande.\n\nOm du försöker köra VeraCrypt i portabelt läge (dvs. utan att installera det) och en annan version av VeraCrypt redan är installerad måste du först avinstallera den, eller uppgradera den med hjälp av VeraCrypt-installationsprogrammet. För att avinstallera det, följ dessa steg: I Windows Vista eller senare, välj "Start-meny" &gt; Dator > "Avinstallera eller ändra ett program" &gt; VeraCrypt > Avinstallera; i Windows XP, välj "Start-meny" &gt; Inställningar > "Kontrollpanelen" &gt; "Lägg till eller ta bort program" &gt; VeraCrypt > Ta bort.\n\nPå liknande sätt, om du försöker köra VeraCrypt i portabelt läge (dvs. utan att installera det) och en annan version av VeraCrypt körs redan i portabelt läge, måste du starta om systemet först och sedan köra endast denna nya version.</entry>
     <entry lang="sv" key="ERR_CIPHER_INIT_FAILURE">Fel: Chifferinitieringsfel.</entry>
     <entry lang="sv" key="ERR_CIPHER_INIT_WEAK_KEY">Fel: En svag eller en potentiellt svag nyckel har upptäckts. Nyckeln kommer att kasseras. Försök igen.</entry>
     <entry lang="sv" key="EXCEPTION_REPORT">Ett kritiskt fel har uppstått och VeraCrypt måste avslutas. Om detta orsakas av ett fel i VeraCrypt vill vi åtgärda det. För att hjälpa oss kan du skicka oss en automatiskt genererad felrapport som innehåller följande:\n\n- Programversion\n- Operativsystemversion\n- CPU-typ\n- VeraCrypt-komponentens namn\n- Den körbara filens kontrollsumma\n- Symboliskt namn på dialogfönstret\n- Felkategori\n- Feladress\n- VeraCrypt-anropsstack\n\nOm du väljer "Ja" kommer följande URL (som innehåller hela felrapporten) att öppnas i din standardwebbläsare.\n\n%hs\n\nVill du skicka ovanstående felrapport till oss?</entry>
@@ -627,13 +627,13 @@
     <entry lang="sv" key="PASSWORD_HIDDENVOL_HOST_DIRECT_HELP">Ange lösenordet för volymen där du vill skapa en dold volym.\n\nNär du klickar på Nästa kommer VeraCrypt att försöka montera volymen. Så snart volymen är monterad, skannas dess klusterbitmapp för att bestämma storleken på det oavbrutna området med ledigt utrymme (om det finns något) vars ände är i linje med slutet av volymen. Detta område kommer att rymma den dolda volymen och begränsar därför dess maximala storlek. Klusterbitmappsskanning är nödvändig för att säkerställa att inga data på den yttre volymen kommer att skrivas över av den dolda volymen.</entry>
     <entry lang="sv" key="PASSWORD_HIDDENVOL_HOST_HELP">\nVälj ett lösenord för den yttre volymen. Detta kommer att vara lösenordet som du kommer att kunna avslöja för en motståndare om du blir ombedd eller tvingad att göra det.\n\nVIKTIGT: Lösenordet måste skilja sig väsentligt från det du väljer för den dolda volymen.\n\nObs: Den maximala lösenordslängden är 128 tecken.</entry>
     <entry lang="sv" key="PASSWORD_SYSENC_OUTERVOL_HELP">Välj ett lösenord för den yttre volymen. Detta kommer att vara lösenordet som du kommer att kunna avslöja för alla som tvingar dig att avslöja lösenordet för den första partitionen bakom systempartitionen, där både den yttre volymen och den dolda volymen (som innehåller det dolda operativsystemet) kommer att finnas. Existensen av den dolda volymen (och det dolda operativsystemet) kommer att förbli hemlig. Observera att det här lösenordet inte är för skenoperativsystemet.\n\nVIKTIGT: Lösenordet måste skilja sig väsentligt från det du väljer för den dolda volymen (dvs. för det dolda operativsystemet).</entry>
-    <entry lang="sv" key="PASSWORD_HIDVOL_HOST_TITLE">Outer Volume Password</entry>
+    <entry lang="sv" key="PASSWORD_HIDVOL_HOST_TITLE">Lösenord för yttre volym</entry>
     <entry lang="sv" key="PASSWORD_HIDVOL_TITLE">Lösenord för dold volym</entry>
     <entry lang="sv" key="PASSWORD_HIDDEN_OS_TITLE">Lösenord för dolt operativsystem</entry>
     <entry lang="sv" key="PASSWORD_LENGTH_WARNING">VARNING: Korta lösenord är enkla att knäcka med hjälp av uttömmande attacktekniker (brute force)!\n\nVi rekommenderar att du väljer ett lösenord som består av minst 20 tecken. Är du säker på att du vill använda ett kort lösenord?</entry>
     <entry lang="sv" key="PASSWORD_TITLE">Volymlösenord</entry>
     <entry lang="sv" key="PASSWORD_WRONG">Operationen misslyckades på grund av ett eller flera av följande:\n - Felaktigt lösenord.\n - Felaktigt volym PIM-nummer.\n - Felaktig PRF (hash).\n - Inte en giltig volym.</entry>
-    <entry lang="sv" key="PASSWORD_OR_KEYFILE_WRONG">Operationen misslyckades på grund av ett eller flera av följande:\n - Felaktig nyckelfil/felaktiga nyckelfiler.\n - Felaktigt lösenord.\n - Felaktigt volym-PIM-nummer.\n - Felaktig PRF (hash).\n - Inte en giltig volym .</entry>
+    <entry lang="sv" key="PASSWORD_OR_KEYFILE_WRONG">Operationen misslyckades på grund av ett eller flera av följande:\n - Felaktig nyckelfil/felaktiga nyckelfiler.\n - Felaktigt lösenord.\n - Felaktigt volym-PIM-nummer.\n - Felaktig PRF (hash).\n - Inte en giltig volym.</entry>
     <entry lang="sv" key="PASSWORD_OR_MODE_WRONG">Operationen misslyckades på grund av ett eller flera av följande:\n - Fel monteringsläge.\n - Felaktigt lösenord.\n - Felaktigt volym-PIM-nummer.\n - Felaktig PRF (hash).\n - Inte en giltig volym.</entry>
     <entry lang="sv" key="PASSWORD_OR_KEYFILE_OR_MODE_WRONG">Operationen misslyckades på grund av ett eller flera av följande:\n - Fel monteringsläge.\n - Felaktig nyckelfil/felaktiga nyckelfiler.\n - Felaktigt lösenord.\n - Felaktigt volym-PIM-nummer.\n - Felaktig PRF (hash). \n - Inte en giltig volym.</entry>
     <entry lang="sv" key="PASSWORD_WRONG_AUTOMOUNT">Automatisk montering misslyckades på grund av ett eller flera av följande:\n - Felaktigt lösenord.\n - Felaktigt volym-PIM-nummer.\n - Felaktig PRF (hash).\n - Ingen giltig volym hittades.</entry>
@@ -813,7 +813,7 @@
     <entry lang="sv" key="SECONDARY_KEY_SIZE_LRW">Justera nyckelstorlek (LRW-läge)</entry>
     <entry lang="sv" key="BITS">bitar</entry>
     <entry lang="sv" key="BLOCK_SIZE">Blockstorlek</entry>
-    <entry lang="sv" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="sv" key="KDF">KDF</entry>
     <entry lang="sv" key="PKCS5_ITERATIONS">PKCS-5 iterationsantal</entry>
     <entry lang="sv" key="VOLUME_CREATE_DATE">Volym skapad</entry>
     <entry lang="sv" key="VOLUME_HEADER_DATE">Huvudet senast ändrat</entry>
@@ -1256,7 +1256,7 @@
     <entry lang="sv" key="BOOT_LOADER_UPGRADE_OK">VeraCrypt-startinläsaren har uppgraderats.\n\nDet rekommenderas starkt att du skapar en ny VeraCrypt-återställningsdisk (som kommer att innehålla den nya versionen av VeraCrypt-startinläsaren) genom att välja "System" &gt; "Skapa återställningsdisk" efter att du har startat om din dator.</entry>
     <entry lang="sv" key="BOOT_LOADER_UPGRADE_OK_HIDDEN_OS">VeraCrypt-startinläsaren har uppgraderats.\n\nDet rekommenderas starkt att du startar skenoperativsystemet och sedan skapar en ny VeraCrypt-återställningsdisk (som kommer att innehålla den nya versionen av VeraCrypt-startinläsaren) genom att välja "System" &gt; "Skapa återställningsdisk".</entry>
     <entry lang="sv" key="BOOT_LOADER_UPGRADE_FAILED">Det gick inte att uppgradera VeraCrypt-startinläsaren.</entry>
-    <entry lang="sv" key="SYS_DRIVE_SIZE_PROBE_TIMEOUT">VeraCrypt kunde inte avgöra systemenhetens verkliga storlek och kommer därför att använda den storlek som rapporteras av operativsystemet. Observera även att detta är inte är ett fel i VeraCrypt.</entry>
+    <entry lang="sv" key="SYS_DRIVE_SIZE_PROBE_TIMEOUT">VeraCrypt kunde inte avgöra systemenhetens verkliga storlek och kommer därför att använda den storlek som rapporteras av operativsystemet. Observera även att detta inte är något fel i VeraCrypt.</entry>
     <entry lang="sv" key="HIDDEN_SECTOR_DETECTION_FAILED_PREVIOUSLY">VARNING: Det verkar som att VeraCrypt redan har försökt identifiera dolda sektorer på denna systemenhet. Om fel uppstod under den föregående identifieringsprocessen kan du undvika dem genom att denna gång hoppa över identifieringen av dolda sektorer. Observera att VeraCrypt då kommer att använda sig av den storlek som rapporteras av operativsystemet, vilken kan vara mindre än enhetens verkliga storlek.\n\nObservera att detta inte orsakas av ett fel i VeraCrypt.</entry>
     <entry lang="sv" key="SKIP_HIDDEN_SECTOR_DETECTION">Hoppa över identifieringen av dolda sektorer (använd storleken som rapporteras av operativsystemet)</entry>
     <entry lang="sv" key="RETRY_HIDDEN_SECTOR_DETECTION">Försök identifiera dolda sektorer igen</entry>
@@ -1427,7 +1427,7 @@
     <entry lang="sv" key="PASSWORD_MAXLENGTH_REACHED">Lösenordet har redan nått sin maximala längd på %d tecken.\nInga ytterligare tecken är tillåtna.</entry>
     <entry lang="sv" key="IDC_SELECT_LANGUAGE_LABEL">Välj vilket språk som ska användas under installationen:</entry>
     <entry lang="sv" key="VOLUME_TOO_LARGE_FOR_HOST">FEL: Storleken på filbehållaren är större än det tillgängliga lediga utrymmet på disken.</entry>
-    <entry lang="sv" key="IDC_ALLOW_WINDOWS_DEFRAG">Tillåt Windows-diskdefragmenterare att defragmentera icke-systempartition/enhet</entry>    
+    <entry lang="sv" key="IDC_ALLOW_WINDOWS_DEFRAG">Tillåt Windows-diskdefragmenterare att defragmentera icke-systempartition/enhet</entry>
     <entry lang="sv" key="CONFIRM_ALLOW_WINDOWS_DEFRAG">VARNING: Defragmentering av icke-systempartitioner/enheter kan läcka metadata om deras innehåll eller orsaka problem med dolda volymer som de kan innehålla.\n\nFortsätt?</entry>
     <entry lang="sv" key="VIRTUAL_DEVICE">Virtuell enhet</entry>
     <entry lang="sv" key="MOUNTED_VOLUME_NOT_ASSOCIATED">Den valda monterade volymen är inte associerad med dess enhetsbokstav i Windows och kan därför inte öppnas i Windows Utforskaren.</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="sv" key="INSECURE_MODE">[OSÄKERT]</entry>
     <entry lang="sv" key="IDC_DISABLE_SCREEN_PROTECTION">Inaktivera skydd mot skärmdumpar och skärminspelning</entry>
     <entry lang="sv" key="DISABLE_SCREEN_PROTECTION_WARNING">VARNING: Att inaktivera skärmskydd minskar säkerheten avsevärt. Aktivera det här alternativet ENDAST om du har ett specifikt behov av att fånga VeraCrypts gränssnitt. Detta kan exponera känslig information för skärmdumpsverktyg och skärminspelningsfunktioner, såsom Windows 11 Recall.</entry>
+    <entry lang="sv" key="MEMORY_COST">Minnesåtgång</entry>
+    <entry lang="sv" key="IDT_KDF_ALGO">KDF-algoritmen</entry>
+    <entry lang="sv" key="IDD_PREFERENCES_TAB_GENERAL">Allmänt</entry>
+    <entry lang="sv" key="IDD_PREFERENCES_TAB_ACTIONS">Åtgärder</entry>
+    <entry lang="sv" key="IDD_PREFERENCES_TAB_PASSWORD">Lösenord</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.th.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="th" name="ภาษาไทย" en-name="Thai" version="0.0.0" translators=""/>
     <font lang="th" class="normal" size="11" face="default" />
     <font lang="th" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="th" key="IDT_NEW_PASSWORD">รหัสผ่านใหม่:</entry>
     <entry lang="th" key="IDT_PARALLELIZATION_OPTIONS">การทำงานแบบขนานโดยใช้เธรด</entry>
     <entry lang="th" key="IDT_PKCS11_LIB_PATH">เส้นทางไลบรารี PKCS #11</entry>
-    <entry lang="th" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="th" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF ใหม่:</entry>
+    <entry lang="th" key="IDT_KDF">KDF:</entry>
+    <entry lang="th" key="IDT_NEW_KDF">KDF ใหม่:</entry>
     <entry lang="th" key="IDT_PW_CACHE_OPTIONS">ตัวเลือกการแคชรหัสผ่าน</entry>
     <entry lang="th" key="IDT_SECURITY_OPTIONS">ตัวเลือกความปลอดภัย</entry>
     <entry lang="th" key="IDT_EMV_OPTIONS">ตัวเลือก EMV</entry>
@@ -813,7 +813,7 @@
     <entry lang="th" key="SECONDARY_KEY_SIZE_LRW">ขนาดคีย์เฉพาะ (โหมด LRW)</entry>
     <entry lang="th" key="BITS">บิต</entry>
     <entry lang="th" key="BLOCK_SIZE">ขนาดบล็อก</entry>
-    <entry lang="th" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="th" key="KDF">KDF</entry>
     <entry lang="th" key="PKCS5_ITERATIONS">จำนวนการวนของ PKCS-5</entry>
     <entry lang="th" key="VOLUME_CREATE_DATE">สร้างวอลุ่มเมื่อ</entry>
     <entry lang="th" key="VOLUME_HEADER_DATE">ส่วนหัวแก้ไขล่าสุดเมื่อ</entry>
@@ -1397,7 +1397,6 @@
     <entry lang="th" key="IDC_SKIP_RESCUE_VERIFICATION">ข้ามการยืนยันดิสก์กู้คืน</entry>
     <entry lang="th" key="IDC_HIDE_WAITING_DIALOG">ไม่แสดงกล่องข้อความรอเมื่อดำเนินการ</entry>
     <entry lang="th" key="IDC_DISABLE_BOOT_LOADER_HASH_PROMPT">ไม่ต้องขออัลกอริธึมแฮชในหน้าจอรับรองบูท</entry>
-    <entry lang="th" key="GOST89_HELP">การเข้ารหัสบล็อก GOST ที่ถูกกำหนดในมาตรฐาน GOST 28147-89 ภายใต้ชื่อ Magma นั้นเป็นมาตรฐานการเข้ารหัสแบบสมมาตรของรัฐบาลโซเวียตและรัสเซีย\n\nพัฒนาขึ้นในช่วงปี 1970 มาตรฐานนี้ถูกจัดเป็น "Top Secret" และจากนั้นถูกลดระดับเป็น "Secret" ในปี 1990 มันเป็นทางเลือกของโซเวียตต่ออัลกอริทึมมาตรฐานของสหรัฐอเมริกา, DES</entry>
     <entry lang="th" key="KUZNYECHIK_HELP">Kuznyechik เป็นบล็อคไซเฟอร์ที่เผยแพร่ครั้งแรกในปี 2015 และกำหนดไว้ในมาตรฐานแห่งชาติของสหพันธรัฐรัสเซีย GOST R 34.12-2015 และยังใน RFC 7801. คีย์ 256-บิต, บล็อก 128-บิต. โหมดการดำเนินการคือ XTS.</entry>
     <entry lang="th" key="CAMELLIA_HELP">ร่วมพัฒนาโดย Mitsubishi Electric และ NTT ของญี่ปุ่น. เผยแพร่ครั้งแรกในปี 2000. คีย์ 256-บิต, บล็อก 128-บิต. โหมดการดำเนินการคือ XTS. ได้รับการอนุมัติให้ใช้โดย ISO/IEC, โครงการ NESSIE ของสหภาพยุโรป และโครงการ CRYPTREC ของญี่ปุ่น.</entry>
     <entry lang="th" key="TIME">เวลา</entry>
@@ -1428,7 +1427,7 @@
     <entry lang="th" key="PASSWORD_MAXLENGTH_REACHED">รหัสผ่านถึงความยาวสูงสุดของ %d อักขระแล้ว.\nไม่สามารถป้อนอักขระเพิ่มเติมได้.</entry>
     <entry lang="th" key="IDC_SELECT_LANGUAGE_LABEL">เลือกภาษาที่จะใช้ระหว่างการติดตั้ง:</entry>
     <entry lang="th" key="VOLUME_TOO_LARGE_FOR_HOST">ข้อผิดพลาด: ขนาดของไฟล์ปริมาณใหญ่กว่าพื้นที่ว่างที่มีบนดิสก์.</entry>
-    <entry lang="th" key="IDC_ALLOW_WINDOWS_DEFRAG">อนุญาตให้ Windows Disk Defragmenter ให้รวบรวมพื้นที่ว่างเพิ่มของพาร์ติชัน/ไดรฟ์ที่ไม่ใช่ระบบ</entry>    
+    <entry lang="th" key="IDC_ALLOW_WINDOWS_DEFRAG">อนุญาตให้ Windows Disk Defragmenter ให้รวบรวมพื้นที่ว่างเพิ่มของพาร์ติชัน/ไดรฟ์ที่ไม่ใช่ระบบ</entry>
     <entry lang="th" key="CONFIRM_ALLOW_WINDOWS_DEFRAG">คำเตือน: การรวบรวมพื้นที่ว่างเพิ่มของพาร์ติชัน/ไดรฟ์ที่ไม่ใช่ระบบอาจเปิดเผยข้อมูลเกี่ยวกับเนื้อหาของพวกเขาหรือก่อให้เกิดปัญหากับปริมาณที่ซ่อนที่อาจมีในพวกเขา.\n\nดำเนินการต่อ?</entry>
     <entry lang="th" key="VIRTUAL_DEVICE">อุปกรณ์เสมือน</entry>
     <entry lang="th" key="MOUNTED_VOLUME_NOT_ASSOCIATED">ปริมาณที่ติดตั้งไว้ที่เลือกไม่เกี่ยวข้องกับตัวอักษรไดรฟ์ของมันใน Windows และไม่สามารถเปิดได้ใน Windows Explorer.</entry>
@@ -1647,6 +1646,47 @@
     <entry lang="th" key="INSECURE_MODE">[โหมดไม่ปลอดภัย]</entry>
     <entry lang="en" key="IDC_DISABLE_SCREEN_PROTECTION">Disable protection against screenshots and screen recording</entry>
     <entry lang="en" key="DISABLE_SCREEN_PROTECTION_WARNING">WARNING: Disabling screen protection significantly reduces security. Enable this option ONLY if you have a specific need to capture VeraCrypt's interface. This may expose sensitive data to screenshot tools and screen recording features such as Windows 11 Recall.</entry>
+    <entry lang="en" key="MEMORY_COST">Memory Cost</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.tr.xml

@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8' standalone='no'?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="tr" name="Türkçe" en-name="Turkish" version="1.26.20" translators="FabSec; By Fabriel, Ali İskender Turan, Zeynel Abidin Öztürk, Mehmet Keçeci, Kaya Zeren" />
     <font lang="tr" class="normal" size="11" face="default" />
     <font lang="tr" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="tr" key="IDT_NEW_PASSWORD">Parola:</entry>
     <entry lang="tr" key="IDT_PARALLELIZATION_OPTIONS">İşlem temelli paralelleştirme</entry>
     <entry lang="tr" key="IDT_PKCS11_LIB_PATH">PKCS #11 kitaplığı yolu</entry>
-    <entry lang="tr" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="tr" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="tr" key="IDT_KDF">KDF:</entry>
+    <entry lang="tr" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="tr" key="IDT_PW_CACHE_OPTIONS">Parola ön belleği</entry>
     <entry lang="tr" key="IDT_SECURITY_OPTIONS">Güvenlik seçenekleri</entry>
     <entry lang="tr" key="IDT_EMV_OPTIONS">EMV Seçenekleri</entry>
@@ -813,7 +813,7 @@
     <entry lang="tr" key="SECONDARY_KEY_SIZE_LRW">Ayarlanan anahtar boyutu (LRW kipi)</entry>
     <entry lang="tr" key="BITS">bit</entry>
     <entry lang="tr" key="BLOCK_SIZE">Blok boyutu</entry>
-    <entry lang="tr" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="tr" key="KDF">KDF</entry>
     <entry lang="tr" key="PKCS5_ITERATIONS">PKCS-5 çevrim sayısı</entry>
     <entry lang="tr" key="VOLUME_CREATE_DATE">Birim oluşturuldu</entry>
     <entry lang="tr" key="VOLUME_HEADER_DATE">Üst bilgi değiştirilme zamanı</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="tr" key="INSECURE_MODE">[GÜVENSİZ MOD]</entry>
     <entry lang="tr" key="IDC_DISABLE_SCREEN_PROTECTION">Ekran görüntüsü ve ekran kaydına karşı korumayı devre dışı bırak</entry>
     <entry lang="tr" key="DISABLE_SCREEN_PROTECTION_WARNING">UYARI: Ekran korumasını devre dışı bırakmak güvenliği önemli ölçüde azaltır. Bu seçeneği YALNIZCA VeraCrypt arayüzünü yakalamak için özel bir ihtiyacınız varsa etkinleştirin. Bu işlem, hassas verilerin ekran görüntüsü araçları ve Windows 11 Recall gibi ekran kaydı özelliklerine maruz kalmasına neden olabilir.</entry>
+    <entry lang="tr" key="MEMORY_COST">Bellek Maliyeti</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.uk.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="uk" name="Українська" en-name="Ukrainian" version="1.1.0" translators="Kravchuk Olexandr, Babchuk Volodymyr" />
     <font lang="uk" class="normal" size="11" face="default" />
     <font lang="uk" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="uk" key="IDT_NEW_PASSWORD">Пароль:</entry>
     <entry lang="uk" key="IDT_PARALLELIZATION_OPTIONS">Потокове Розпаралелювання</entry>
     <entry lang="uk" key="IDT_PKCS11_LIB_PATH">Шлях до бібліотеки PKCS #11</entry>
-    <entry lang="uk" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="uk" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="uk" key="IDT_KDF">KDF:</entry>
+    <entry lang="uk" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="uk" key="IDT_PW_CACHE_OPTIONS">Кешування (запамятовування) паролів</entry>
     <entry lang="uk" key="IDT_SECURITY_OPTIONS">Параметри безпеки</entry>
     <entry lang="uk" key="IDT_EMV_OPTIONS">Параметри EMV</entry>
@@ -813,7 +813,7 @@
     <entry lang="uk" key="SECONDARY_KEY_SIZE_LRW">довжина Tweak-ключа (LRW-режим)</entry>
     <entry lang="uk" key="BITS">біт(и,ів)</entry>
     <entry lang="uk" key="BLOCK_SIZE">Розмір блоку</entry>
-    <entry lang="uk" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="uk" key="KDF">KDF</entry>
     <entry lang="uk" key="PKCS5_ITERATIONS">Кількість ітерацій PKCS-5</entry>
     <entry lang="uk" key="VOLUME_CREATE_DATE">Том створено</entry>
     <entry lang="uk" key="VOLUME_HEADER_DATE">Остання зміна заголовку</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="uk" key="INSECURE_MODE">[НЕБЕЗПЕЧНИЙ РЕЖИМ]</entry>
     <entry lang="uk" key="IDC_DISABLE_SCREEN_PROTECTION">Вимкнути захист від створення знімків екрана та запису екрану</entry>
     <entry lang="uk" key="DISABLE_SCREEN_PROTECTION_WARNING">ПОПЕРЕДЖЕННЯ: Вимкнення захисту екрана значно знижує безпеку. Активуйте цю опцію ЛИШЕ за наявності конкретної потреби зафіксувати інтерфейс VeraCrypt. Це може призвести до витоку чутливих даних через інструменти створення знімків екрана та запису екрану, наприклад, Windows 11 Recall.</entry>
+    <entry lang="uk" key="MEMORY_COST">Витрати пам'яті</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.uz.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="uz" name="Ўзбекча" en-name="Uzbek (Cyrillic)" version="0.1.0" translators="Abdurauf Azizov, Dmitry Yerokhin" />
     <font lang="uz" class="normal" size="11" face="default" />
     <font lang="uz" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="uz" key="IDT_NEW_PASSWORD">Пароль:</entry>
     <entry lang="en" key="IDT_PARALLELIZATION_OPTIONS">Thread-Based Parallelization</entry>
     <entry lang="uz" key="IDT_PKCS11_LIB_PATH">Путь к библиотеке PKCS #11</entry>
-    <entry lang="uz" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="en" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="uz" key="IDT_KDF">KDF:</entry>
+    <entry lang="en" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="uz" key="IDT_PW_CACHE_OPTIONS">Кэширование (запоминание) паролей</entry>
     <entry lang="uz" key="IDT_SECURITY_OPTIONS">Параметры безопасности</entry>
     <entry lang="en" key="IDT_EMV_OPTIONS">EMV Options</entry>
@@ -813,7 +813,7 @@
     <entry lang="uz" key="SECONDARY_KEY_SIZE_LRW">Длина Tweak-ключа (LRW-режим)</entry>
     <entry lang="uz" key="BITS">бит</entry>
     <entry lang="uz" key="BLOCK_SIZE">Размер блока</entry>
-    <entry lang="uz" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="uz" key="KDF">KDF</entry>
     <entry lang="uz" key="PKCS5_ITERATIONS">Число итераций PKCS-5</entry>
     <entry lang="uz" key="VOLUME_CREATE_DATE">Том создан</entry>
     <entry lang="uz" key="VOLUME_HEADER_DATE">Последнее изменение заголовка</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="en" key="INSECURE_MODE">[INSECURE MODE]</entry>
     <entry lang="en" key="IDC_DISABLE_SCREEN_PROTECTION">Disable protection against screenshots and screen recording</entry>
     <entry lang="en" key="DISABLE_SCREEN_PROTECTION_WARNING">WARNING: Disabling screen protection significantly reduces security. Enable this option ONLY if you have a specific need to capture VeraCrypt's interface. This may expose sensitive data to screenshot tools and screen recording features such as Windows 11 Recall.</entry>
+    <entry lang="en" key="MEMORY_COST">Memory Cost</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.vi.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="vi" name="Tiếng Việt" en-name="Vietnamese" version="0.1.0" translators="Nguyễn Kim Huy" />
     <font lang="vi" class="normal" size="11" face="default" />
     <font lang="vi" class="bold" size="13" face="Arial" />
@@ -291,8 +291,8 @@
     <entry lang="vi" key="IDT_NEW_PASSWORD">Mật mã:</entry>
     <entry lang="en" key="IDT_PARALLELIZATION_OPTIONS">Thread-Based Parallelization</entry>
     <entry lang="vi" key="IDT_PKCS11_LIB_PATH">Đường dẫn Thư viện của PKCS #11</entry>
-    <entry lang="vi" key="IDT_PKCS5_PRF">PKCS-5 PRF:</entry>
-    <entry lang="en" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF:</entry>
+    <entry lang="vi" key="IDT_KDF">KDF:</entry>
+    <entry lang="en" key="IDT_NEW_KDF">KDF:</entry>
     <entry lang="vi" key="IDT_PW_CACHE_OPTIONS">Tạm trữ Mật mã</entry>
     <entry lang="vi" key="IDT_SECURITY_OPTIONS">Tùy chọn bảo mật</entry>
     <entry lang="en" key="IDT_EMV_OPTIONS">EMV Options</entry>
@@ -813,7 +813,7 @@
     <entry lang="vi" key="SECONDARY_KEY_SIZE_LRW">Kích cỡ Khóa Vặn (Phương thức LRW)</entry>
     <entry lang="vi" key="BITS">bits</entry>
     <entry lang="vi" key="BLOCK_SIZE">Kích cỡ Khối</entry>
-    <entry lang="vi" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="vi" key="KDF">KDF</entry>
     <entry lang="vi" key="PKCS5_ITERATIONS">Đếm Lần lặp lại của PKCS-5</entry>
     <entry lang="vi" key="VOLUME_CREATE_DATE">Tập đĩa đã được Cấu tạo</entry>
     <entry lang="vi" key="VOLUME_HEADER_DATE">Phần đầu được Sửa đổi lần Cuối</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="en" key="INSECURE_MODE">[INSECURE MODE]</entry>
     <entry lang="en" key="IDC_DISABLE_SCREEN_PROTECTION">Disable protection against screenshots and screen recording</entry>
     <entry lang="en" key="DISABLE_SCREEN_PROTECTION_WARNING">WARNING: Disabling screen protection significantly reduces security. Enable this option ONLY if you have a specific need to capture VeraCrypt's interface. This may expose sensitive data to screenshot tools and screen recording features such as Windows 11 Recall.</entry>
+    <entry lang="en" key="MEMORY_COST">Memory Cost</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.zh-cn.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="zh-cn" name="简体中文" en-name="Chinese (Simplified)" version="1.0.3" translators="Barney Li, Zhangjintao, Nkh0472, 风之暇想" />
     <font lang="zh-cn" class="normal" size="12" face="Microsoft YaHei" />
     <font lang="zh-cn" class="bold" size="14" face="Microsoft YaHei" />
@@ -292,8 +292,8 @@
     <entry lang="zh-cn" key="IDT_NEW_PASSWORD">密码：</entry>
     <entry lang="zh-cn" key="IDT_PARALLELIZATION_OPTIONS">基于线程的并行计算</entry>
     <entry lang="zh-cn" key="IDT_PKCS11_LIB_PATH">PKCS #11 运行库路径</entry>
-    <entry lang="zh-cn" key="IDT_PKCS5_PRF">PKCS-5 PRF：</entry>
-    <entry lang="zh-cn" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF：</entry>
+    <entry lang="zh-cn" key="IDT_KDF">KDF：</entry>
+    <entry lang="zh-cn" key="IDT_NEW_KDF">KDF：</entry>
     <entry lang="zh-cn" key="IDT_PW_CACHE_OPTIONS">密码缓存</entry>
     <entry lang="zh-cn" key="IDT_SECURITY_OPTIONS">安全选项</entry>
     <entry lang="zh-cn" key="IDT_EMV_OPTIONS">EMV选项</entry>
@@ -814,7 +814,7 @@
     <entry lang="zh-cn" key="SECONDARY_KEY_SIZE_LRW">调整密钥大小（LRW 模式）</entry>
     <entry lang="zh-cn" key="BITS">位</entry>
     <entry lang="zh-cn" key="BLOCK_SIZE">块大小</entry>
-    <entry lang="zh-cn" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="zh-cn" key="KDF">KDF</entry>
     <entry lang="zh-cn" key="PKCS5_ITERATIONS">PKCS-5 迭代次数</entry>
     <entry lang="zh-cn" key="VOLUME_CREATE_DATE">加密卷创建时间</entry>
     <entry lang="zh-cn" key="VOLUME_HEADER_DATE">头信息上次修改时间</entry>
@@ -1647,6 +1647,47 @@
     <entry lang="zh-cn" key="INSECURE_MODE">[不安全模式]</entry>
     <entry lang="zh-cn" key="IDC_DISABLE_SCREEN_PROTECTION">禁用屏幕截图与录屏保护</entry>
     <entry lang="zh-cn" key="DISABLE_SCREEN_PROTECTION_WARNING">警告：禁用屏幕截图与录屏保护会显著降低安全性。仅当您有特定需求捕获 VeraCrypt 界面时，才需启用此选项。这可能会使敏感数据暴露给屏幕截图工具和 Windows 11 Recall 等录屏功能。</entry>
+    <entry lang="zh-cn" key="MEMORY_COST">内存成本</entry>
+    <entry lang="zh-cn" key="IDT_KDF_ALGO">KDF算法</entry>
+    <entry lang="zh-cn" key="IDD_PREFERENCES_TAB_GENERAL">常规</entry>
+    <entry lang="zh-cn" key="IDD_PREFERENCES_TAB_ACTIONS">动作</entry>
+    <entry lang="zh-cn" key="IDD_PREFERENCES_TAB_PASSWORD">密码</entry>
+    <entry lang="zh-cn" key="IDC_SECURE_DESKTOP_ENABLE_IME">在安全桌面中启用输入法编辑器（IME）</entry>
+    <entry lang="zh-cn" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">警告：仅当您在安全桌面下选择密钥文件/令牌时遇到问题时，才启用此选项。</entry>
+    <entry lang="zh-cn" key="ERR_KEY_DERIVATION_FAILED">密钥派生失败。这可能由内存不足或操作被中断导致。</entry>
+    <entry lang="zh-cn" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">系统分区/驱动器已解密，但 EFI Microsoft 引导加载程序路径未恢复到 Windows 启动管理器。仅需修复 EFI 引导文件。请使用 VeraCrypt 救援盘修复选项，或启动 Windows 恢复介质，运行 'bcdboot W:\\Windows /s S: /f UEFI'（将 W: 替换为 Windows 卷的驱动器号，S: 替换为 EFI 系统分区的驱动器号）。路径：</entry>
+    <entry lang="zh-cn" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">系统分区/驱动器已解密，但 EFI 回退引导加载程序路径中仍包含 VeraCrypt 引导加载程序。仅需修复 EFI 引导文件。请使用 VeraCrypt 救援盘修复选项，或启动 Windows 恢复介质，运行 'bcdboot W:\\Windows /s S: /f UEFI'（将 W: 替换为 Windows 卷的驱动器号，S: 替换为 EFI 系统分区的驱动器号）。路径：</entry>
+    <entry lang="zh-cn" key="IDM_REPAIR_EFI_BOOT_LOADER">修复 EFI 引导加载程序...</entry>
+    <entry lang="zh-cn" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt 将还原 Windows EFI 引导加载程序路径，并移除 VeraCrypt EFI 引导项和文件。\n\n仅在系统分区/驱动器已完全解密且 Windows 无需系统加密即可启动后使用。\n\n是否继续？</entry>
+    <entry lang="zh-cn" key="EFI_BOOT_LOADER_FILE_READ_FAILED">无法完整读取 EFI 引导加载程序文件：</entry>
+    <entry lang="zh-cn" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">EFI 引导加载程序文件意外过大，未进行检查：</entry>
+    <entry lang="zh-cn" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">系统分区/驱动器已解密且 EFI 引导文件已还原，但 VeraCrypt 无法移除一个或多个 VeraCrypt 固件引导项。VeraCrypt EFI 文件已保留，因此任何剩余的固件项仍指向现有的加载程序。请以管理员身份重试，或在确认 Windows 启动管理器正常启动后从固件设置中移除 VeraCrypt 引导项。</entry>
+    <entry lang="zh-cn" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">系统加密或解密正在进行或未完成时，无法修复 EFI 引导加载程序。请先完成或继续挂起的系统加密/解密过程，然后再重试。</entry>
+    <entry lang="zh-cn" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">此修复操作仅适用于从 GPT 系统分区以 UEFI 模式启动的系统。</entry>
+    <entry lang="zh-cn" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">EFI 引导加载程序已成功修复。</entry>
+    <entry lang="zh-cn" key="PIM_ARGON2_HELP">PIM（个人迭代乘数）控制 Argon2id 头部密钥派生所使用的内存和时间开销，规则如下：\n      内存 = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      迭代次数 = 当 PIM ≤ 31 时，为 3 + ((PIM - 1) / 3)；当 PIM > 31 时，为 13 + (PIM - 31)\n\n当留空或设为 0 时，VeraCrypt 将使用默认的 Argon2 PIM（12），此时占用 416 MiB 内存并执行 6 次迭代。\n\n当密码长度不足 20 个字符时，为了维持最低安全级别，Argon2 PIM 不能小于 12。\n当密码长度达到 20 个或更多字符时，Argon2 PIM 可以设为任意值。\n\n大于 12 的 Argon2 PIM 会增加内存占用（最高 1024 MiB），然后增加迭代次数，这会导致挂载变慢。较小的 Argon2 PIM（小于 12）会加快挂载速度，但如果密码强度不够，会降低安全性。</entry>
+    <entry lang="zh-cn" key="PIM_ARGON2_LARGE_WARNING">您选择的 Argon2 PIM 值大于 VeraCrypt 的默认值。\n请注意，这可能需要更多内存，并导致挂载速度显著变慢。</entry>
+    <entry lang="zh-cn" key="PIM_ARGON2_SMALL_WARNING">您选择的 Argon2 PIM 值小于 VeraCrypt 的默认值。请注意，如果您的密码强度不够，这可能导致安全性降低。\n\n您确认正在使用强密码吗？</entry>
+    <entry lang="zh-cn" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">密码必须包含 20 个或更多字符，才能使用指定的 Argon2 PIM。\n较短的密码只有在 Argon2 PIM 大于或等于 12 时才能使用。</entry>
+    <entry lang="zh-cn" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">使用 Linux 内核 ntfs3 驱动程序挂载 NTFS 卷</entry>
+    <entry lang="zh-cn" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">仅限 Linux。启用后，VeraCrypt 会使用 blkid -p 探测解密的虚拟设备，并使用 ntfs3 挂载检测到的 NTFS 文件系统，而不是默认的 NTFS 后端。如果 NTFS 检测失败，VeraCrypt 将使用正常的自动文件系统选择。如果 ntfs3 不可用或被发行版阻止，挂载可能会失败。此手动启用选项可以避免因冻结的用户空间 FUSE 文件系统导致的挂起或休眠卡顿。</entry>
+    <entry lang="zh-cn" key="LINUX_EMERGENCY_UNMOUNT_WARNING">卷 {0} 的正常卸载失败。当应用程序仍在卷上打开文件或目录，或者后端设备已断开连接导致挂载状态失效时，可能会发生这种情况。\n\n如果设备仍处于连接状态，请选择“否”，关闭使用该卷的应用程序，然后再次尝试卸载。\n\n如果设备已断开连接或挂载状态已失效，VeraCrypt 可以尝试执行紧急清理：惰性脱离文件系统，并移除或安排移除 VeraCrypt 内核对象。待处理的写入可能已失败，数据可能丢失，并且清理操作可能保持挂起状态，直到应用程序关闭打开的文件。再次使用前，请使用 fsck 或相应的修复工具检查文件系统。\n\n继续？</entry>
+    <entry lang="zh-cn" key="LINUX_EMERGENCY_UNMOUNTED">已对卷 {0} 启动紧急清理。如果卷已断开连接、挂载状态失效或存在待处理的写入操作，请在再次使用前使用 fsck 或相应的修复工具检查文件系统。</entry>
+    <entry lang="zh-cn" key="FORMAT_STAGE_WRITING_DATA">正在创建卷数据。请稍候。</entry>
+    <entry lang="zh-cn" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">正在完成卷创建：写入备份卷头信息。</entry>
+    <entry lang="zh-cn" key="FORMAT_STAGE_FLUSHING_DATA">正在完成卷创建：将数据刷新到磁盘。对于大型卷或慢速/USB 存储设备，这可能需要几分钟时间。</entry>
+    <entry lang="zh-cn" key="FORMAT_STAGE_FINISHED">正在完成卷创建。</entry>
+    <entry lang="zh-cn" key="FORMAT_STAGE_ABORTED">卷创建已中止。</entry>
+    <entry lang="zh-cn" key="FORMAT_STAGE_ERROR">卷创建失败。</entry>
+    <entry lang="zh-cn" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">正在完成卷创建：挂载临时卷。</entry>
+    <entry lang="zh-cn" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">正在完成卷创建：准备临时设备。</entry>
+    <entry lang="zh-cn" key="FORMAT_STAGE_CREATING_FILESYSTEM">正在完成卷创建：使用 {0} 创建文件系统。</entry>
+    <entry lang="zh-cn" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">正在完成卷创建：卸载临时卷。</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.zh-hk.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="zh-hk" name="正體中文(香港)" en-name="Traditional Chinese (Hong Kong)" version="0.1.0" translators="PUN Chi Ho, Yeung Tim Ming" />
     <font lang="zh-hk" class="normal" size="12" face="Microsoft JhengHei UI" />
     <font lang="zh-hk" class="bold" size="13" face="Microsoft JhengHei UI Bold" />
@@ -291,8 +291,8 @@
     <entry lang="zh-hk" key="IDT_NEW_PASSWORD">密碼：</entry>
     <entry lang="zh-hk" key="IDT_PARALLELIZATION_OPTIONS">以執行緒為基礎的平行運算</entry>
     <entry lang="zh-hk" key="IDT_PKCS11_LIB_PATH">PKCS #11 程式庫路徑</entry>
-    <entry lang="en" key="IDT_PKCS5_PRF">PKCS-5 PRF：</entry>
-    <entry lang="en" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF：</entry>
+    <entry lang="en" key="IDT_KDF">KDF：</entry>
+    <entry lang="en" key="IDT_NEW_KDF">KDF：</entry>
     <entry lang="zh-hk" key="IDT_PW_CACHE_OPTIONS">密碼暫存</entry>
     <entry lang="zh-hk" key="IDT_SECURITY_OPTIONS">保安設定選項</entry>
     <entry lang="zh-hk" key="IDT_EMV_OPTIONS">EMV 設定選項</entry>
@@ -813,7 +813,7 @@
     <entry lang="zh-hk" key="SECONDARY_KEY_SIZE_LRW">調整加密鑰大小(LRW 模式)</entry>
     <entry lang="zh-hk" key="BITS">位元</entry>
     <entry lang="zh-hk" key="BLOCK_SIZE">區塊大小</entry>
-    <entry lang="zh-hk" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="zh-hk" key="KDF">KDF</entry>
     <entry lang="zh-hk" key="PKCS5_ITERATIONS">PKCS-5 反覆運算重復次數</entry>
     <entry lang="zh-hk" key="VOLUME_CREATE_DATE">加密區建立時間</entry>
     <entry lang="zh-hk" key="VOLUME_HEADER_DATE">標頭數據的上次修改時間</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="zh-hk" key="INSECURE_MODE">[不安全模式]</entry>
     <entry lang="en" key="IDC_DISABLE_SCREEN_PROTECTION">Disable protection against screenshots and screen recording</entry>
     <entry lang="en" key="DISABLE_SCREEN_PROTECTION_WARNING">WARNING: Disabling screen protection significantly reduces security. Enable this option ONLY if you have a specific need to capture VeraCrypt's interface. This may expose sensitive data to screenshot tools and screen recording features such as Windows 11 Recall.</entry>
+    <entry lang="en" key="MEMORY_COST">Memory Cost</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.zh-tw.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.24">
+  <localization prog-version="1.26.28">
     <language langid="zh-tw" name="繁體中文" en-name="Chinese (Taiwan)" version="0.1.0" translators="Barney Li, Simon Ma, ChangMing Hsu" />
     <font lang="zh-tw" class="normal" size="12" face="MingLiU" />
     <font lang="zh-tw" class="bold" size="15" face="MingLiU" />
@@ -291,8 +291,8 @@
     <entry lang="zh-tw" key="IDT_NEW_PASSWORD">密碼：</entry>
     <entry lang="zh-tw" key="IDT_PARALLELIZATION_OPTIONS">基於執行緒的並行化</entry>
     <entry lang="en" key="IDT_PKCS11_LIB_PATH">PKCS #11 Library Path</entry>
-    <entry lang="zh-tw" key="IDT_PKCS5_PRF">PKCS-5 PRF：</entry>
-    <entry lang="zh-tw" key="IDT_NEW_PKCS5_PRF">PKCS-5 PRF：</entry>
+    <entry lang="zh-tw" key="IDT_KDF">KDF：</entry>
+    <entry lang="zh-tw" key="IDT_NEW_KDF">KDF：</entry>
     <entry lang="zh-tw" key="IDT_PW_CACHE_OPTIONS">密碼快取</entry>
     <entry lang="zh-tw" key="IDT_SECURITY_OPTIONS">安全選項</entry>
     <entry lang="en" key="IDT_EMV_OPTIONS">EMV Options</entry>
@@ -813,7 +813,7 @@
     <entry lang="en" key="SECONDARY_KEY_SIZE_LRW">Tweak Key Size (LRW Mode)</entry>
     <entry lang="zh-tw" key="BITS">位元</entry>
     <entry lang="zh-tw" key="BLOCK_SIZE">區塊大小</entry>
-    <entry lang="zh-tw" key="PKCS5_PRF">PKCS-5 PRF</entry>
+    <entry lang="zh-tw" key="KDF">KDF</entry>
     <entry lang="zh-tw" key="PKCS5_ITERATIONS">PKCS-5 反覆運算次數</entry>
     <entry lang="zh-tw" key="VOLUME_CREATE_DATE">加密區建立時間</entry>
     <entry lang="zh-tw" key="VOLUME_HEADER_DATE">標頭資訊上次修改時間</entry>
@@ -1646,6 +1646,47 @@
     <entry lang="en" key="INSECURE_MODE">[INSECURE MODE]</entry>
     <entry lang="en" key="IDC_DISABLE_SCREEN_PROTECTION">Disable protection against screenshots and screen recording</entry>
     <entry lang="en" key="DISABLE_SCREEN_PROTECTION_WARNING">WARNING: Disabling screen protection significantly reduces security. Enable this option ONLY if you have a specific need to capture VeraCrypt's interface. This may expose sensitive data to screenshot tools and screen recording features such as Windows 11 Recall.</entry>
+    <entry lang="en" key="MEMORY_COST">Memory Cost</entry>
+    <entry lang="en" key="IDT_KDF_ALGO">KDF Algorithm</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_GENERAL">General</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_ACTIONS">Actions</entry>
+    <entry lang="en" key="IDD_PREFERENCES_TAB_PASSWORD">Password</entry>
+    <entry lang="en" key="IDC_SECURE_DESKTOP_ENABLE_IME">Enable Input Method Editor (IME) in Secure Desktop</entry>
+    <entry lang="en" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop.</entry>
+    <entry lang="en" key="ERR_KEY_DERIVATION_FAILED">Key derivation failed. This may be caused by insufficient memory or an interrupted operation.</entry>
+    <entry lang="en" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path:</entry>
+    <entry lang="en" key="IDM_REPAIR_EFI_BOOT_LOADER">Repair EFI Boot Loader...</entry>
+    <entry lang="en" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue?</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_READ_FAILED">The EFI boot loader file could not be read completely:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">The EFI boot loader file is unexpectedly large and was not inspected:</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. Complete or resume the pending system encryption/decryption process before retrying.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">This repair action is available only on systems booting in UEFI mode from a GPT system partition.</entry>
+    <entry lang="en" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">The EFI boot loader has been repaired successfully.</entry>
+    <entry lang="en" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controls the memory and time costs used by Argon2id header key derivation as follows:\n      Memory = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterations = 3 + ((PIM - 1) / 3) for PIM 31 or lower, then 13 + (PIM - 31)\n\nWhen left empty or set to 0, VeraCrypt will use the default Argon2 PIM (12), which uses 416 MiB of memory and 6 iterations.\n\nWhen the password is less than 20 characters, Argon2 PIM can't be smaller than 12 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, Argon2 PIM can be set to any value.\n\nAn Argon2 PIM larger than 12 increases memory usage up to 1024 MiB and then increases iterations. This will lead to slower mounting. A small Argon2 PIM (less than 12) will lead to quicker mounting but it can reduce security if the password is not strong enough.</entry>
+    <entry lang="en" key="PIM_ARGON2_LARGE_WARNING">You have chosen an Argon2 PIM value that is larger than VeraCrypt default value.\nPlease note that this can require more memory and lead to much slower mounting.</entry>
+    <entry lang="en" key="PIM_ARGON2_SMALL_WARNING">You have chosen an Argon2 PIM value that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to weaker security.\n\nDo you confirm that you are using a strong password?</entry>
+    <entry lang="en" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Password must contain 20 or more characters in order to use the specified Argon2 PIM.\nShorter passwords can only be used if the Argon2 PIM is 12 or greater.</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3">Mount NTFS volumes with the Linux kernel ntfs3 driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_NTFS3_HELP">Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue?</entry>
+    <entry lang="en" key="LINUX_EMERGENCY_UNMOUNTED">Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_DATA">Creating volume data. Please wait.</entry>
+    <entry lang="en" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizing volume creation: writing backup header.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FLUSHING_DATA">Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage.</entry>
+    <entry lang="en" key="FORMAT_STAGE_FINISHED">Finalizing volume creation.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ABORTED">Volume creation has been aborted.</entry>
+    <entry lang="en" key="FORMAT_STAGE_ERROR">Volume creation failed.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizing volume creation: mounting temporary volume.</entry>
+    <entry lang="en" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizing volume creation: preparing temporary device.</entry>
+    <entry lang="en" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizing volume creation: creating filesystem using {0}.</entry>
+    <entry lang="en" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizing volume creation: dismounting temporary volume.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYNTHESIZED_DEVICE">The selected device '{0}' is an APFS synthesized container or volume and cannot be used as a raw VeraCrypt volume host.\n\nSelect the physical APFS store partition{1} instead.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_SYSTEM_PARTITION">The selected device '{0}' is a macOS system/support partition and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_APFS_SYSTEM_STORE">The selected APFS physical store '{0}' contains the currently mounted macOS system volume and cannot be used as a VeraCrypt volume host.</entry>
+    <entry lang="en" key="MACOSX_DEVICE_NOT_WRITABLE">macOS reports the selected device '{0}' as read-only. Select a writable physical partition or disk.</entry>
+    <entry lang="en" key="MACOSX_APFS_EROFS_HINT">macOS reported the selected device as read-only. If this is an APFS disk, make sure you selected the physical APFS store partition, not an APFS synthesized volume. Use Disk Utility or 'diskutil list' to identify the physical partition, then retry.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

contrib/EncryptData.ps1

@@ -6,7 +6,7 @@
 .DESCRIPTION
     • Chooses an exFAT cluster size (auto or explicit).
     • Calculates the minimum container size using an iterative approach for FAT/Bitmap sizing, plus safety margin.
-    • Creates, mounts, copies, verifies, and dismounts – all guarded by -WhatIf/-Confirm (SupportsShouldProcess).
+    • Creates, mounts, copies, verifies, and unmounts – all guarded by -WhatIf/-Confirm (SupportsShouldProcess).
     • Finds VeraCrypt automatically or takes a -VeraCryptDir override.
     • Encryption and hash algorithms are parameters.
     • Password can be passed via SecureString prompt or pipeline.
@@ -420,13 +420,13 @@ try {
 } finally {
     if (Test-Path variable:plainPassword) { Clear-Variable plainPassword -ErrorAction SilentlyContinue }
     if ($mounted) {
-        if ($PSCmdlet.ShouldProcess("Drive $driveLetter", "Dismount VeraCrypt volume")) {
-            Write-Verbose "Dismounting drive $driveLetter..."
-            $dismountArgs = @('/dismount', $driveLetter, '/force', '/quit', '/silent')
-            Start-Process -FilePath $VeraCryptExe -ArgumentList $dismountArgs -NoNewWindow -Wait -ErrorAction SilentlyContinue
-            Write-Verbose "Dismount command issued."
+        if ($PSCmdlet.ShouldProcess("Drive $driveLetter", "Unmount VeraCrypt volume")) {
+            Write-Verbose "Unmounting drive $driveLetter..."
+            $unmountArgs = @('/unmount', $driveLetter, '/force', '/quit', '/silent')
+            Start-Process -FilePath $VeraCryptExe -ArgumentList $unmountArgs -NoNewWindow -Wait -ErrorAction SilentlyContinue
+            Write-Verbose "Unmount command issued."
         } else {
-            Write-Host "Dismount skipped due to -WhatIf."
+            Write-Host "Unmount skipped due to -WhatIf."
         }
     }
     foreach($f in @($errFile,$mountFile) | Where-Object { $_ }) {  

doc/chm/en/VeraCrypt.hhc

@@ -207,6 +207,20 @@
 			<param name="Local" value="Streebog.html">
 			</OBJECT>
 	</UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Key Derivation Algorithms">
+		<param name="Local" value="Key Derivation Algorithms.html">
+		</OBJECT>
+	<UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Argon2id">
+			<param name="Local" value="Argon2id.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="PBKDF2">
+			<param name="Local" value="pbkdf2.html">
+			</OBJECT>
+	</UL>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="Supported Operating Systems">
 		<param name="Local" value="Supported Operating Systems.html">
@@ -215,6 +229,16 @@
 		<param name="Name" value="Command Line Usage">
 		<param name="Local" value="Command Line Usage.html">
 		</OBJECT>
+	<UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Windows">
+			<param name="Local" value="Command Line Usage for Windows.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Linux and macOS">
+			<param name="Local" value="Command Line Usage for Unix.html">
+			</OBJECT>
+	</UL>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="Security Model">
 		<param name="Local" value="Security Model.html">

doc/chm/en/VeraCrypt.hhp

@@ -13,6 +13,7 @@ Title=VeraCrypt User Guide
 Acknowledgements.html
 Additional Security Requirements and Precautions.html
 AES.html
+Argon2id.html
 arrow_right.gif
 Authenticity and Integrity.html
 Authors.html
@@ -51,6 +52,8 @@ Cascades.html
 Changing Passwords and Keyfiles.html
 Choosing Passwords and Keyfiles.html
 Command Line Usage.html
+Command Line Usage for Windows.html
+Command Line Usage for Unix.html
 CompilingGuidelineLinux.html
 CompilingGuidelines.html
 CompilingGuidelineWin.html
@@ -90,6 +93,7 @@ Incompatibilities.html
 Introduction.html
 Issues and Limitations.html
 Journaling File Systems.html
+Key Derivation Algorithms.html
 Keyfiles in VeraCrypt.html
 Keyfiles in VeraCrypt_Image_040.gif
 Keyfiles.html
@@ -111,6 +115,7 @@ Notation.html
 Paging File.html
 Parallelization.html
 paypal_30x30.png
+pbkdf2.html
 Personal Iterations Multiplier (PIM).html
 Personal Iterations Multiplier (PIM)_VeraCrypt_ChangePIM_Step1.png
 Personal Iterations Multiplier (PIM)_VeraCrypt_ChangePIM_Step2.png
@@ -177,4 +182,3 @@ Wear-Leveling.html
 Whirlpool.html
 
 [INFOTYPES]
-

doc/html/en/AES.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
@@ -39,13 +38,13 @@
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 The Advanced Encryption Standard (AES) specifies a FIPS-approved cryptographic algorithm (Rijndael, designed by Joan Daemen and Vincent Rijmen, published in 1998) that may be used by US federal departments and agencies to cryptographically protect sensitive
  information [3]. VeraCrypt uses AES with 14 rounds and a 256-bit key (i.e., AES-256, published in 2001) operating in
-<a href="Modes%20of%20Operation.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
-XTS mode</a> (see the section <a href="Modes%20of%20Operation.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="Modes%20of%20Operation.html" style="text-align:left; color:#0080c0; text-decoration:none">
+XTS mode</a> (see the section <a href="Modes%20of%20Operation.html" style="text-align:left; color:#0080c0; text-decoration:none">
 Modes of Operation</a>).</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 In June 2003, after the NSA (US National Security Agency) conducted a review and analysis of AES, the U.S. CNSS (Committee on National Security Systems) announced in [1] that the design and strength of AES-256 (and AES-192) are sufficient to protect classified
  information up to the Top Secret level. This is applicable to all U.S. Government Departments or Agencies that are considering the acquisition or use of products incorporating the Advanced Encryption Standard (AES) to satisfy Information Assurance requirements
  associated with the protection of national security systems and/or national security information [1].</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-<a href="Camellia.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold.html">Next Section &gt;&gt;</a></div>
+<a href="Camellia.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold">Next Section &gt;&gt;</a></div>
 </div><div class="ClearBoth"></div></body></html>

doc/html/en/Acknowledgements.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/Additional Security Requirements and Precautions.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/Argon2id.html

@@ -0,0 +1,174 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
+<meta name="description" content="VeraCrypt is free open-source disk encryption software for Windows, Mac OS X and Linux. In case an attacker forces you to reveal the password, VeraCrypt provides plausible deniability. In contrast to file encryption, data encryption performed by VeraCrypt is real-time (on-the-fly), automatic, transparent, needs very little memory, and does not involve temporary unencrypted files."/>
+<meta name="keywords" content="encryption, security"/>
+<link href="styles.css" rel="stylesheet" type="text/css" />
+</head>
+<body>
+
+<div>
+<a href="Documentation.html"><img src="VeraCrypt128x128.png" alt="VeraCrypt"/></a>
+</div>
+
+<div id="menu">
+    <ul>
+      <li><a href="Home.html">Home</a></li>
+      <li><a href="Code.html">Source Code</a></li>
+      <li><a href="Downloads.html">Downloads</a></li>
+      <li><a class="active" href="Documentation.html">Documentation</a></li>
+      <li><a href="Donation.html">Donate</a></li>
+      <li><a href="https://sourceforge.net/p/veracrypt/discussion/" target="_blank">Forums</a></li>
+    </ul>
+</div>
+
+<div>
+<p>
+<a href="Documentation.html">Documentation</a>
+<img src="arrow_right.gif" alt=">>" style="margin-top: 5px">
+<a href="Key%20Derivation%20Algorithms.html">Key Derivation Algorithms</a>
+<img src="arrow_right.gif" alt=">>" style="margin-top: 5px">
+<a href="Argon2id.html">Argon2id</a>
+</p></div>
+
+<div class="wikidoc">
+<h1>Argon2id</h1>
+<div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+Argon2id is a memory-hard key derivation function designed to resist both time-memory trade-off attacks and side-channel attacks. It was selected as the winner of the Password Hashing Competition (PHC) in 2015 and is defined in RFC 9106. VeraCrypt supports Argon2id as an alternative to PBKDF2-HMAC for header key derivation.
+</div>
+
+<h3>Key Features</h3>
+<ul style="text-align:left; margin-top:18px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>Memory-hard:</strong> Requires a configurable amount of memory, making it resistant to specialized hardware attacks
+</li>
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>Side-channel resistant:</strong> Combines data-dependent and data-independent memory access patterns
+</li>
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>Internal hash function:</strong> Uses BLAKE2b internally, eliminating the need for separate hash algorithm selection
+</li>
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>Tunable parameters:</strong> Allows adjustment of memory cost, time cost, and parallelism
+</li>
+</ul>
+
+<h3>Argon2 Variants</h3>
+<div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+Argon2 has three variants:
+</div>
+<ul style="text-align:left; margin-top:18px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>Argon2d:</strong> Uses data-dependent memory access, resistant to time-memory trade-off attacks but vulnerable to side-channel attacks
+</li>
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>Argon2i:</strong> Uses data-independent memory access, resistant to side-channel attacks but more vulnerable to time-memory trade-off attacks
+</li>
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>Argon2id:</strong> Hybrid approach that combines both variants, providing resistance to both attack types (used by VeraCrypt)
+</li>
+</ul>
+
+<h3>Parameters in VeraCrypt</h3>
+<div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+VeraCrypt uses Argon2id with the following parameter configuration:
+</div>
+
+<h4>Memory Cost (m_cost)</h4>
+<div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+The amount of memory used during the key derivation process, controlled by the PIM value:
+</div>
+<ul style="text-align:left; margin-top:18px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>Formula:</strong> m_cost(pim) = min(64 MiB + (pim - 1) × 32 MiB, 1024 MiB)
+</li>
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>Range:</strong> 64 MiB to 1024 MiB (capped at PIM = 31)
+</li>
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>Default:</strong> 96 MiB (equivalent to PIM = 2)
+</li>
+</ul>
+
+<h4>Time Cost (t_cost)</h4>
+<div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+The number of iterations performed during the key derivation process:
+</div>
+<ul style="text-align:left; margin-top:18px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>For PIM ≤ 31:</strong> t_cost(pim) = 3 + floor((pim - 1) / 3)
+</li>
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>For PIM > 31:</strong> t_cost(pim) = 13 + (pim - 31)
+</li>
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>Default:</strong> 3 iterations (equivalent to PIM = 2)
+</li>
+</ul>
+
+<h4>Parallelism</h4>
+<div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+The number of parallel threads used during computation:
+</div>
+<ul style="text-align:left; margin-top:18px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>Value:</strong> Fixed at 1 thread for all cases in VeraCrypt
+</li>
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>Rationale:</strong> Ensures consistent behavior across different hardware configurations
+</li>
+</ul>
+
+<h3>Advantages over PBKDF2</h3>
+<ul style="text-align:left; margin-top:18px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>Memory hardness:</strong> Requires significant memory allocation, making GPU and ASIC attacks more expensive
+</li>
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>Modern design:</strong> Specifically designed to resist contemporary attack methods
+</li>
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>Side-channel resistance:</strong> Built-in protections against cache-timing and other side-channel attacks
+</li>
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>Standardization:</strong> Officially standardized in RFC 9106
+</li>
+</ul>
+
+<h3>Usage Considerations</h3>
+<div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+When using Argon2id in VeraCrypt:
+</div>
+<ul style="text-align:left; margin-top:18px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>Memory requirements:</strong> Ensure sufficient RAM is available, especially with higher PIM values
+</li>
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>Performance:</strong> Higher memory costs may result in slower mounting times but provide better security
+</li>
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>Compatibility:</strong> Available in VeraCrypt versions that support multiple key derivation functions
+</li>
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
+<strong>No hash selection:</strong> Unlike PBKDF2-HMAC, no separate hash algorithm needs to be chosen
+</li>
+</ul>
+
+<h3>Technical Specifications</h3>
+<div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+<strong>Algorithm:</strong> Argon2id as defined in RFC 9106<br/>
+<strong>Internal hash:</strong> BLAKE2b<br/>
+<strong>Salt size:</strong> 512 bits (same as PBKDF2-HMAC)<br/>
+<strong>Output length:</strong> Variable, depending on the encryption algorithm (e.g., 256 bits for AES-256, 768 bits for AES-Twofish-Serpent cascade)<br/>
+<strong>Version:</strong> Argon2 version 0x13 (19 decimal)
+</div>
+
+<div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+For more information about PIM values and their effect on Argon2id parameters, see the 
+<a href="Personal%20Iterations%20Multiplier%20%28PIM%29.html" style="text-align:left; color:#0080c0; text-decoration:none">
+Personal Iterations Multiplier (PIM)</a> section.
+</div>
+
+</div><div class="ClearBoth"></div></body></html>

doc/html/en/Authenticity and Integrity.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/Authors.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/Avoid Third-Party File Extensions.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
@@ -82,4 +81,4 @@
 	  </ul>
 	</div>
 	
-<div class="ClearBoth"></div></body></html>
+<div class="ClearBoth"></div></div></body></html>

doc/html/en/BLAKE2s-256.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
@@ -47,5 +46,5 @@ VeraCrypt uses only BLAKE2s with its maximum output size of 32-bytes (256 bits).
 </p>
 </div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-<a href="SHA-256.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold.html">Next Section &gt;&gt;</a></div>
+<a href="SHA-256.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold">Next Section &gt;&gt;</a></div>
 </div><div class="ClearBoth"></div></body></html>

doc/html/en/Beginner's Tutorial.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/Camellia.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
@@ -39,9 +38,9 @@
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 Jointly developed by Mitsubishi Electric and NTT of Japan, Camellia is a 128-bit block cipher that was first published on 2000. It has been approved for use by the ISO/IEC, the European Union's NESSIE project and the Japanese CRYPTREC project.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-VeraCrypt uses Camellia with 24 rounds and a 256-bit key operating in <a href="Modes%20of%20Operation.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
-XTS mode</a> (see the section <a href="Modes%20of%20Operation.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
+VeraCrypt uses Camellia with 24 rounds and a 256-bit key operating in <a href="Modes%20of%20Operation.html" style="text-align:left; color:#0080c0; text-decoration:none">
+XTS mode</a> (see the section <a href="Modes%20of%20Operation.html" style="text-align:left; color:#0080c0; text-decoration:none">
 Modes of Operation</a>).</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-<a href="Kuznyechik.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold.html">Next Section &gt;&gt;</a></div>
+<a href="Kuznyechik.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold">Next Section &gt;&gt;</a></div>
 </div><div class="ClearBoth"></div></body></html>

doc/html/en/Cascades.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/Changing Passwords and Keyfiles.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/Choosing Passwords and Keyfiles.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/Command Line Usage for Unix.html

@@ -0,0 +1,337 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
+<meta name="description" content="VeraCrypt is free open-source disk encryption software for Windows, Mac OS X and Linux. In case an attacker forces you to reveal the password, VeraCrypt provides plausible deniability. In contrast to file encryption, data encryption performed by VeraCrypt is real-time (on-the-fly), automatic, transparent, needs very little memory, and does not involve temporary unencrypted files."/>
+<meta name="keywords" content="encryption, security"/>
+<link href="styles.css" rel="stylesheet" type="text/css" />
+</head>
+<body>
+
+<div>
+<a href="Documentation.html"><img src="VeraCrypt128x128.png" alt="VeraCrypt"/></a>
+</div>
+
+<div id="menu">
+	<ul>
+	  <li><a href="Home.html">Home</a></li>
+	  <li><a href="Code.html">Source Code</a></li>
+	  <li><a href="Downloads.html">Downloads</a></li>
+	  <li><a class="active" href="Documentation.html">Documentation</a></li>
+	  <li><a href="Donation.html">Donate</a></li>
+	  <li><a href="https://sourceforge.net/p/veracrypt/discussion/" target="_blank">Forums</a></li>
+	</ul>
+</div>
+
+<div>
+<p>
+<a href="Documentation.html">Documentation</a>
+<img src="arrow_right.gif" alt=">>" style="margin-top: 5px">
+<a href="Command%20Line%20Usage.html">Command Line Usage</a>
+<img src="arrow_right.gif" alt=">>" style="margin-top: 5px">
+<a href="Command%20Line%20Usage%20for%20Unix.html">Linux and macOS</a>
+</p></div>
+
+<div class="wikidoc">
+<div>
+<h1>Command Line Usage for Linux and macOS</h1>
+<p>This section applies to VeraCrypt on Unix-like systems, including Linux and macOS. The Windows command-line syntax is documented separately in <a href="Command%20Line%20Usage%20for%20Windows.html">Command Line Usage for Windows</a>.</p>
+<p>To display the command-line help for the installed VeraCrypt build in a terminal, run:</p>
+<p><code>veracrypt -t --help</code></p>
+<p>The <code>-t</code> or <code>--text</code> option selects the text user interface and must be specified as the first argument. Without <code>-t</code>, <code>veracrypt --help</code> may show the graphical help window when the graphical user interface is available.</p>
+
+<h4>Syntax</h4>
+<p><code>veracrypt [OPTIONS] COMMAND</code></p>
+<p><code>veracrypt [OPTIONS] VOLUME_PATH [MOUNT_DIRECTORY]</code></p>
+<p>If no explicit command is specified and a volume path is given, VeraCrypt mounts the volume. When <code>MOUNT_DIRECTORY</code> is omitted, VeraCrypt uses the default mount directory.</p>
+
+<h4>Commands</h4>
+<table border="1" cellspacing="0" cellpadding="1">
+<tbody>
+<tr>
+<td><em>--auto-mount=devices|favorites</em></td>
+<td>Auto-mount device-hosted volumes, favorite volumes, or both when the values are combined with a comma.</td>
+</tr>
+<tr>
+<td><em>--backup-headers [VOLUME_PATH]</em></td>
+<td>Back up volume headers to a file. Required values not specified on the command line are requested from the user.</td>
+</tr>
+<tr>
+<td><em>-c</em> or <em>--create [VOLUME_PATH]</em></td>
+<td>Create a new volume. Most values are requested from the user if not specified on the command line. See also <em>--encryption</em>, <em>--filesystem</em>, <em>--hash</em>, <em>--keyfiles</em>, <em>--password</em>, <em>--pim</em>, <em>--random-source</em>, <em>--quick</em>, <em>--size</em>, and <em>--volume-type</em>.</td>
+</tr>
+<tr>
+<td><em>--create-keyfile [FILE_PATH]</em></td>
+<td>Create a new keyfile containing pseudo-random data.</td>
+</tr>
+<tr>
+<td><em>-C</em> or <em>--change [VOLUME_PATH]</em></td>
+<td>Change a volume password, PIM, keyfiles, and/or header key derivation algorithm. See also <em>--hash</em>, <em>--new-hash</em>, <em>--new-keyfiles</em>, <em>--new-password</em>, <em>--new-pim</em>, <em>--password</em>, <em>--pim</em>, and <em>--random-source</em>.</td>
+</tr>
+<tr>
+<td><em>-u</em> or <em>--unmount [MOUNTED_VOLUME]</em><br><em>-d</em> or <em>--dismount [MOUNTED_VOLUME]</em></td>
+<td>Unmount a mounted volume. If no mounted volume is specified, all mounted VeraCrypt volumes are unmounted. <em>--dismount</em> is deprecated; use <em>--unmount</em>.</td>
+</tr>
+<tr>
+<td><em>--delete-token-keyfiles</em></td>
+<td>Delete keyfiles from security tokens.</td>
+</tr>
+<tr>
+<td><em>--export-token-keyfile</em></td>
+<td>Export a keyfile from a security token.</td>
+</tr>
+<tr>
+<td><em>--import-token-keyfiles</em></td>
+<td>Import keyfiles to a security token. See also <em>--token-lib</em>.</td>
+</tr>
+<tr>
+<td><em>-l</em> or <em>--list [MOUNTED_VOLUME]</em></td>
+<td>Display mounted volumes. By default, only the volume path, virtual device, and mount point are shown. Use <em>--verbose</em> for more details.</td>
+</tr>
+<tr>
+<td><em>--list-token-keyfiles</em></td>
+<td>Display all available token keyfiles.</td>
+</tr>
+<tr>
+<td><em>--list-securitytoken-keyfiles</em></td>
+<td>Display all available security token keyfiles.</td>
+</tr>
+<tr>
+<td><em>--list-emvtoken-keyfiles</em></td>
+<td>Display all available EMV token keyfiles.</td>
+</tr>
+<tr>
+<td><em>--mount [VOLUME_PATH]</em></td>
+<td>Mount a volume interactively. The volume path and missing options are requested from the user.</td>
+</tr>
+<tr>
+<td><em>--restore-headers [VOLUME_PATH]</em></td>
+<td>Restore volume headers from the embedded backup header or from an external backup file.</td>
+</tr>
+<tr>
+<td><em>--save-preferences</em></td>
+<td>Save user preferences.</td>
+</tr>
+<tr>
+<td><em>--test</em></td>
+<td>Test internal algorithms used in the process of encryption and decryption.</td>
+</tr>
+<tr>
+<td><em>--version</em></td>
+<td>Display VeraCrypt version information.</td>
+</tr>
+<tr>
+<td><em>--volume-properties [MOUNTED_VOLUME]</em></td>
+<td>Display properties of a mounted volume.</td>
+</tr>
+</tbody>
+</table>
+
+<h4>MOUNTED_VOLUME</h4>
+<p>A mounted volume can be specified in any of the following forms:</p>
+<ul>
+<li>Path to the encrypted VeraCrypt volume.</li>
+<li>Mount directory of the volume's filesystem, if mounted.</li>
+<li>Slot number of the mounted volume, when used with <em>--slot</em>.</li>
+</ul>
+
+<h4>Options</h4>
+<table border="1" cellspacing="0" cellpadding="1">
+<tbody>
+<tr>
+<td><em>--allow-insecure-mount</em></td>
+<td>Allow mounting volumes on mount points that are in the user's <code>PATH</code>.</td>
+</tr>
+<tr>
+<td><em>--allow-screencapture</em></td>
+<td>Allow VeraCrypt windows to be included in screenshots and screen recordings. This option applies to macOS builds.</td>
+</tr>
+<tr>
+<td><em>--background-task</em></td>
+<td>Start the VeraCrypt background task.</td>
+</tr>
+<tr>
+<td><em>--display-password</em></td>
+<td>Display password characters while typing.</td>
+</tr>
+<tr>
+<td><em>--encryption=ENCRYPTION_ALGORITHM</em></td>
+<td>Use the specified encryption algorithm when creating a new volume. For cascades, use the algorithm name shown by VeraCrypt, for example <code>AES-Twofish</code>.</td>
+</tr>
+<tr>
+<td><em>--explore</em></td>
+<td>Open a file manager window after the volume is mounted.</td>
+</tr>
+<tr>
+<td><em>--filesystem=TYPE</em></td>
+<td>Filesystem type to mount or create. For mounting, the type is passed to the system mount command. <em>none</em> disables filesystem mounting or creation. Supported creation types depend on the platform: Linux supports <em>FAT</em>, <em>Ext2</em>, <em>Ext3</em>, <em>Ext4</em>, <em>NTFS</em>, <em>exFAT</em>, and <em>Btrfs</em>; macOS supports <em>FAT</em>, <em>HFS</em>/<em>HFS+</em>/<em>MacOsExt</em>, <em>exFAT</em>, and <em>APFS</em>; FreeBSD and Solaris builds support <em>FAT</em> and <em>UFS</em>. Non-FAT creation requires the corresponding system formatter to be available.</td>
+</tr>
+<tr>
+<td><em>-f</em> or <em>--force</em></td>
+<td>Force mounting of a volume in use, unmounting of a volume in use, or overwriting a file. The exact effect depends on the operating system.</td>
+</tr>
+<tr>
+<td><em>--fs-options=OPTIONS</em></td>
+<td>Filesystem mount options passed to the system mount command with <code>-o</code>. This option is available on Linux and other Unix-like builds where supported, but not on macOS.</td>
+</tr>
+<tr>
+<td><em>--hash=HASH</em></td>
+<td>Use the specified header key derivation algorithm when mounting, creating a volume, or changing password/keyfiles. This option also specifies the mixing hash of the random number generator when applicable.</td>
+</tr>
+<tr>
+<td><em>-h</em> or <em>--help</em></td>
+<td>Display detailed command-line help.</td>
+</tr>
+<tr>
+<td><em>-k KEYFILE1[,KEYFILE2,...]</em> or <em>--keyfiles=KEYFILE1[,KEYFILE2,...]</em></td>
+<td>Use the specified keyfiles. When a directory is specified, all files inside it are used non-recursively. Use a double comma (<code>,,</code>) for a comma contained in a keyfile name. A keyfile stored on a security token can be specified as <code>token://slot/SLOT_NUMBER/file/FILENAME</code>; an EMV token keyfile can be specified as <code>emv://slot/SLOT_NUMBER</code>. Use <code>-k ""</code> to disable interactive keyfile prompts.</td>
+</tr>
+<tr>
+<td><em>--legacy-password-maxlength</em></td>
+<td>Use the legacy maximum password length of 64 UTF-8 bytes.</td>
+</tr>
+<tr>
+<td><em>--load-preferences</em></td>
+<td>Load user preferences before processing command-line options, allowing command-line options to override preferences.</td>
+</tr>
+<tr>
+<td><em>-m OPTION1[,OPTION2,...]</em> or <em>--mount-options=OPTION1[,OPTION2,...]</em></td>
+<td>Set VeraCrypt volume mount options. Supported options are <em>headerbak</em>, <em>nokernelcrypto</em>, <em>readonly</em> or <em>ro</em>, <em>system</em>, and <em>timestamp</em> or <em>ts</em>.</td>
+</tr>
+<tr>
+<td><em>--new-hash=HASH</em></td>
+<td>Set the new header key derivation algorithm when changing a volume password or keyfiles. This option is used with <em>--change</em>.</td>
+</tr>
+<tr>
+<td><em>--new-keyfiles=KEYFILE1[,KEYFILE2,...]</em></td>
+<td>Set the new keyfiles when changing a volume password or keyfiles. This option is used with <em>--change</em>.</td>
+</tr>
+<tr>
+<td><em>--new-password=PASSWORD</em></td>
+<td>Set the new password when changing a volume password or keyfiles. This option is used with <em>--change</em>.</td>
+</tr>
+<tr>
+<td><em>--new-pim=PIM</em></td>
+<td>Set the new PIM when changing a volume password or keyfiles. This option is used with <em>--change</em>.</td>
+</tr>
+<tr>
+<td><em>--no-size-check</em></td>
+<td>Disable the check that verifies the requested container size against available free disk space.</td>
+</tr>
+<tr>
+<td><em>--non-interactive</em></td>
+<td>Do not interact with the user. This option is supported only in text mode.</td>
+</tr>
+<tr>
+<td><em>-p PASSWORD</em> or <em>--password=PASSWORD</em></td>
+<td>Use the specified password to mount or open a volume. An empty password can be specified with <code>-p ""</code>.</td>
+</tr>
+<tr>
+<td><em>--pim=PIM</em></td>
+<td>Use the specified PIM to mount or open a volume.</td>
+</tr>
+<tr>
+<td><em>--protect-hidden=yes|no</em></td>
+<td>Write-protect a hidden volume when mounting an outer volume. If enabled, VeraCrypt uses the hidden volume credentials to determine the hidden area and protects it against writes.</td>
+</tr>
+<tr>
+<td><em>--protection-hash=HASH</em></td>
+<td>Use the specified header key derivation algorithm for the hidden volume protected by <em>--protect-hidden=yes</em>.</td>
+</tr>
+<tr>
+<td><em>--protection-keyfiles=KEYFILE1[,KEYFILE2,...]</em></td>
+<td>Use the specified keyfiles for the hidden volume protected by <em>--protect-hidden=yes</em>.</td>
+</tr>
+<tr>
+<td><em>--protection-password=PASSWORD</em></td>
+<td>Use the specified password for the hidden volume protected by <em>--protect-hidden=yes</em>.</td>
+</tr>
+<tr>
+<td><em>--protection-pim=PIM</em></td>
+<td>Use the specified PIM for the hidden volume protected by <em>--protect-hidden=yes</em>.</td>
+</tr>
+<tr>
+<td><em>--quick</em></td>
+<td>Enable quick formatting when creating a volume. This option must not be used when creating an outer volume.</td>
+</tr>
+<tr>
+<td><em>--random-source=FILE</em></td>
+<td>Use the specified file as a source of random data, for example when creating a volume.</td>
+</tr>
+<tr>
+<td><em>--slot=SLOT</em></td>
+<td>Use the specified slot number when mounting, unmounting, listing, or displaying properties of a volume.</td>
+</tr>
+<tr>
+<td><em>--size=SIZE[K|KiB|M|MiB|G|GiB|T|TiB]</em> or <em>--size=max</em></td>
+<td>Use the specified size when creating a new volume. If no suffix is specified, the value is interpreted in bytes. <em>max</em> uses all available free space.</td>
+</tr>
+<tr>
+<td><em>--stdin</em></td>
+<td>Read the password from standard input. This option can be used only with <em>--non-interactive</em> and cannot be combined with <em>--password</em>.</td>
+</tr>
+<tr>
+<td><em>-t</em> or <em>--text</em></td>
+<td>Use the text user interface. This option must be specified as the first argument.</td>
+</tr>
+<tr>
+<td><em>--token-lib=LIB_PATH</em></td>
+<td>Use the specified PKCS #11 security token library.</td>
+</tr>
+<tr>
+<td><em>--token-pin=PIN</em></td>
+<td>Use the specified security token PIN.</td>
+</tr>
+<tr>
+<td><em>--use-dummy-sudo-password</em></td>
+<td>Use a dummy password in <code>sudo</code> to detect whether sudo is already authenticated. This option is available on Linux and FreeBSD builds.</td>
+</tr>
+<tr>
+<td><em>-v</em> or <em>--verbose</em></td>
+<td>Enable verbose output.</td>
+</tr>
+<tr>
+<td><em>--volume-type=normal|hidden</em></td>
+<td>Use the specified volume type when creating a new volume.</td>
+</tr>
+</tbody>
+</table>
+
+<h4>Security Notes</h4>
+<p>Passing a password, PIM, token PIN, or hidden-volume protection password on the command line can be insecure because command-line arguments may be visible in process listings, shell history, or system logs. When possible, let VeraCrypt prompt for sensitive values interactively, or use <em>--stdin</em> with <em>--non-interactive</em> where appropriate. Users must also follow the security requirements and precautions listed in <a href="Security%20Requirements%20and%20Precautions.html">Security Requirements and Precautions</a>.</p>
+
+<h4>Examples</h4>
+<p>Create a new volume using the text user interface:</p>
+<p><code>veracrypt -t -c</code></p>
+<p>Mount a volume:</p>
+<p><code>veracrypt volume.hc /media/veracrypt1</code></p>
+<p>Mount a volume read-only, using keyfiles:</p>
+<p><code>veracrypt -m ro -k keyfile1,keyfile2 volume.hc /media/veracrypt1</code></p>
+<p>Mount a volume without mounting its filesystem:</p>
+<p><code>veracrypt --filesystem=none volume.hc</code></p>
+<p>Mount a volume prompting only for its password:</p>
+<p><code>veracrypt -t -k "" --pim=0 --protect-hidden=no volume.hc /media/veracrypt1</code></p>
+<p>Mount a volume non-interactively and read the password from standard input:</p>
+<p><code>printf '%s\n' "$VERACRYPT_PASSWORD" | veracrypt -t --non-interactive --stdin --pim=0 --protect-hidden=no volume.hc /media/veracrypt1</code></p>
+<p>List mounted volumes with detailed information:</p>
+<p><code>veracrypt -t -v --list</code></p>
+<p>Unmount a volume:</p>
+<p><code>veracrypt -u volume.hc</code></p>
+<p>Unmount all mounted VeraCrypt volumes:</p>
+<p><code>veracrypt -u</code></p>
+
+<h4>Hidden Volume Creation in Text Mode</h4>
+<p>Inexperienced users should use the graphical user interface to create a hidden volume. When using the text user interface, the following procedure must be followed:</p>
+<ol>
+<li>Create an outer volume with no filesystem.</li>
+<li>Create a hidden volume within the outer volume.</li>
+<li>Mount the outer volume using hidden volume protection.</li>
+<li>Create a filesystem on the virtual device of the outer volume.</li>
+<li>Mount the new filesystem and fill it with data.</li>
+<li>Unmount the outer volume.</li>
+</ol>
+<p>If hidden volume protection is triggered at any step, start again from the first step.</p>
+
+</div>
+</div><div class="ClearBoth"></div></body></html>

doc/html/en/Command Line Usage for Windows.html

@@ -0,0 +1,339 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
+<meta name="description" content="VeraCrypt is free open-source disk encryption software for Windows, Mac OS X and Linux. In case an attacker forces you to reveal the password, VeraCrypt provides plausible deniability. In contrast to file encryption, data encryption performed by VeraCrypt is real-time (on-the-fly), automatic, transparent, needs very little memory, and does not involve temporary unencrypted files."/>
+<meta name="keywords" content="encryption, security"/>
+<link href="styles.css" rel="stylesheet" type="text/css" />
+</head>
+<body>
+
+<div>
+<a href="Documentation.html"><img src="VeraCrypt128x128.png" alt="VeraCrypt"/></a>
+</div>
+
+<div id="menu">
+	<ul>
+	  <li><a href="Home.html">Home</a></li>
+	  <li><a href="Code.html">Source Code</a></li>
+	  <li><a href="Downloads.html">Downloads</a></li>
+	  <li><a class="active" href="Documentation.html">Documentation</a></li>
+	  <li><a href="Donation.html">Donate</a></li>
+	  <li><a href="https://sourceforge.net/p/veracrypt/discussion/" target="_blank">Forums</a></li>
+	</ul>
+</div>
+
+<div>
+<p>
+<a href="Documentation.html">Documentation</a>
+<img src="arrow_right.gif" alt=">>" style="margin-top: 5px">
+<a href="Command%20Line%20Usage.html">Command Line Usage</a>
+<img src="arrow_right.gif" alt=">>" style="margin-top: 5px">
+<a href="Command%20Line%20Usage%20for%20Windows.html">Windows</a>
+</p></div>
+
+<div class="wikidoc">
+<div>
+<h1>Command Line Usage for Windows</h1>
+<p>This section applies to the Windows version of VeraCrypt. The Unix-style command-line syntax used on Linux and macOS is documented separately in <a href="Command%20Line%20Usage%20for%20Unix.html">Command Line Usage for Linux and macOS</a>.</p>
+<table border="1" cellspacing="0" cellpadding="1">
+<tbody>
+<tr>
+<td><em>/help</em> or <em>/?</em></td>
+<td>Display command line help.</td>
+</tr>
+<tr>
+<td><em>/truecrypt or /tc</em></td>
+<td>Activate TrueCrypt compatibility mode which enables mounting volumes created with TrueCrypt 6.x and 7.x series.</td>
+</tr>
+<tr>
+<td><em>/hash</em></td>
+<td>It must be followed by a parameter indicating the PRF hash algorithm to use when mounting the volume. Possible values for /hash parameter are: sha256, sha-256, sha512, sha-512, whirlpool, blake2s and blake2s-256. When /hash is omitted, VeraCrypt will try
+ all possible PRF algorithms thus lengthening the mount operation time.</td>
+</tr>
+<tr>
+<td id="volume"><em>/volume</em> or <em>/v</em></td>
+<td>
+<p>It must be followed by a parameter indicating the file and path name of a VeraCrypt volume to mount (do not use when unmounting) or the Volume ID of the disk/partition to mount.<br>
+The syntax of the volume ID is <strong>ID:XXXXXX...XX</strong> where the XX part is a 64 hexadecimal characters string that represent the 32-Bytes ID of the desired volume to mount.<br>
+<br>
+To mount a partition/device-hosted volume, use, for example, /v \Device\Harddisk1\Partition3 (to determine the path to a partition/device, run VeraCrypt and click
+<em>Select Device</em>). You can also mount a partition or dynamic volume using its volume name (for example, /v \\?\Volume{5cceb196-48bf-46ab-ad00-70965512253a}\). To determine the volume name use e.g. mountvol.exe. Also note that device paths are case-sensitive.<br>
+<br>
+You can also specify the Volume ID of the partition/device-hosted volume to mount, for example: /v ID:53B9A8D59CC84264004DA8728FC8F3E2EE6C130145ABD3835695C29FD601EDCA. The Volume ID value can be retrieved using the volume properties dialog.</p>
+</td>
+</tr>
+<tr>
+<td><em>/letter</em> or <em>/l</em></td>
+<td>It must be followed by a parameter indicating the driver letter to mount the volume as. When /l is omitted and when /a is used, the first free drive letter is used.</td>
+</tr>
+<tr>
+<td><em>/explore</em> or <em>/e</em></td>
+<td>Open an Explorer window after a volume has been mounted.</td>
+</tr>
+<tr>
+<td><em>/beep</em> or <em>/b</em></td>
+<td>Beep after a volume has been successfully mounted or unmounted.</td>
+</tr>
+<tr>
+<td><em>/auto</em> or <em>/a</em></td>
+<td>If no parameter is specified, automatically mount the volume. If devices is specified as the parameter (e.g., /a devices), auto-mount all currently accessible device/partition-hosted VeraCrypt volumes. If favorites is specified as the parameter, auto-mount
+ favorite volumes. Note that /auto is implicit if /quit and /volume are specified. If you need to prevent the application window from appearing, use /quit.</td>
+</tr>
+<tr>
+<td><em>/unmount</em> or <em>/u</em></td>
+<td>Unmount volume specified by drive letter (e.g., /u x). When no drive letter is specified, unmounts all currently mounted VeraCrypt volumes.</td>
+</tr>
+<tr>
+<td><em>/dismount</em> or <em>/d</em></td>
+<td>Deprecated. Please use /unmount or /u.</td>
+</tr>
+<tr>
+<td><em>/force</em> or <em>/f</em></td>
+<td>Forces unmount (if the volume to be unmounted contains files being used by the system or an application) and forces mounting in shared mode (i.e., without exclusive access).</td>
+</tr>
+<tr>
+<td><em>/keyfile</em> or <em>/k</em></td>
+<td>It must be followed by a parameter specifying a keyfile or a keyfile search path. For multiple keyfiles, specify e.g.: /k c:\keyfile1.dat /k d:\KeyfileFolder /k c:\kf2 To specify a keyfile stored on a security token or smart card, use the following syntax:
+ token://slot/SLOT_NUMBER/file/FILE_NAME</td>
+</tr>
+<tr id="tryemptypass">
+<td><em>/tryemptypass&nbsp;&nbsp; </em></td>
+<td>ONLY when default keyfile configured or when a keyfile is specified in the command line.<br>
+If it is followed by <strong>y</strong> or <strong>yes</strong> or if no parameter is specified: try to mount using an empty password and the keyfile before displaying password prompt.<br>
+if it is followed by <strong>n </strong>or<strong> no</strong>: don't try to mount using an empty password and the keyfile, and display password prompt right away.</td>
+</tr>
+<tr>
+<td><em>/nowaitdlg</em></td>
+<td>If it is followed by <strong>y</strong> or <strong>yes</strong> or if no parameter is specified: don&rsquo;t display the waiting dialog while performing operations like mounting volumes.<br>
+If it is followed by <strong>n</strong> or <strong>no</strong>: force the display waiting dialog is displayed while performing operations.</td>
+</tr>
+<tr>
+<td><em>/secureDesktop</em></td>
+<td>If it is followed by <strong>y</strong> or <strong>yes</strong> or if no parameter is specified: display password dialog and token PIN dialog in a dedicated secure desktop to protect against certain types of attacks.<br>
+If it is followed by <strong>n</strong> or <strong>no</strong>: the password dialog and token PIN dialog are displayed in the normal desktop.</td>
+</tr>
+<tr>
+<td><em>/tokenlib</em></td>
+<td>It must be followed by a parameter indicating the PKCS #11 library to use for security tokens and smart cards. (e.g.: /tokenlib c:\pkcs11lib.dll)</td>
+</tr>
+<tr>
+<td><em>/tokenpin</em></td>
+<td>It must be followed by a parameter indicating the PIN to use in order to authenticate to the security token or smart card (e.g.: /tokenpin 0000). Warning: This method of entering a smart card PIN may be insecure, for example, when an unencrypted command
+ prompt history log is being saved to unencrypted disk.</td>
+</tr>
+<tr>
+<td><em>/cache</em> or <em>/c</em></td>
+<td>If it is followed by <strong>y</strong> or <strong>yes</strong> or if no parameter is specified: enable password cache;
+<br>
+If it is followed by <strong>p </strong>or<strong> pim</strong>: enable both password and PIM cache (e.g., /c p).<br>
+If it is followed by <strong>n </strong>or<strong> no</strong>: disable password cache (e.g., /c n).<br>
+If it is followed by <strong>f </strong>or<strong> favorites</strong>: temporary cache password when mounting multiple favorites&nbsp; (e.g., /c f).<br>
+Note that turning the password cache off will not clear it (use /w to clear the password cache).</td>
+</tr>
+<tr>
+<td><em>/history</em> or <em>/h</em></td>
+<td>If it is followed by <strong>y</strong> or no parameter: enables saving history of mounted volumes; if it is followed by
+<strong>n</strong>: disables saving history of mounted volumes (e.g., /h n).</td>
+</tr>
+<tr>
+<td><em>/wipecache</em> or <em>/w</em></td>
+<td>Wipes any passwords cached in the driver memory.</td>
+</tr>
+<tr>
+<td><em>/password</em> or <em>/p</em></td>
+<td>It must be followed by a parameter indicating the volume password. If the password contains spaces, it must be enclosed in quotation marks (e.g., /p &rdquo;My Password&rdquo;). Use /p &rdquo;&rdquo; to specify an empty password.
+<em>Warning: This method of entering a volume password may be insecure, for example, when an unencrypted command prompt history log is being saved to unencrypted disk.</em></td>
+</tr>
+<tr>
+<td><em>/pim</em></td>
+<td>It must be followed by a positive integer indicating the PIM (Personal Iterations Multiplier) to use for the volume.</td>
+</tr>
+<tr>
+<td><em>/quit</em> or <em>/q</em></td>
+<td>Automatically perform requested actions and exit (main VeraCrypt window will not be displayed). If preferences is specified as the parameter (e.g., /q preferences), then program settings are loaded/saved and they override settings specified on the command
+ line. /q background launches the VeraCrypt Background Task (tray icon) unless it is disabled in the Preferences.</td>
+</tr>
+<tr>
+<td><em>/silent</em> or <em>/s</em></td>
+<td>If /q is specified, suppresses interaction with the user (prompts, error messages, warnings, etc.). If /q is not specified, this option has no effect.</td>
+</tr>
+<tr>
+<td><em>/mountoption</em> or <em>/m</em></td>
+<td>
+<p>It must be followed by a parameter which can have one of the values indicated below.</p>
+<p><strong>ro</strong> or<strong> readonly</strong>: Mount volume as read-only.</p>
+<p><strong>rm</strong> or <strong>removable</strong>: Mount volume as removable medium (see section
+<a href="Removable%20Medium%20Volume.html">
+<em>Volume Mounted as Removable Medium</em></a>).</p>
+<p><strong>ts</strong> or <strong>timestamp</strong>: Do not preserve container modification timestamp.</p>
+<p><strong>sm</strong> or <strong>system</strong>: Without pre-boot authentication, mount a partition that is within the key scope of system encryption (for example, a partition located on the encrypted system drive of another operating system that is not running).
+ Useful e.g. for backup or repair operations. Note: If you supply a password as a parameter of /p, make sure that the password has been typed using the standard US keyboard layout (in contrast, the GUI ensures this automatically). This is required due to the
+ fact that the password needs to be typed in the pre-boot environment (before Windows starts) where non-US Windows keyboard layouts are not available.</p>
+<p><strong>bk</strong> or <strong>headerbak</strong>: Mount volume using embedded backup header. Note: All volumes created by VeraCrypt contain an embedded backup header (located at the end of the volume).</p>
+<p><strong>recovery</strong>: Do not verify any checksums stored in the volume header. This option should be used only when the volume header is damaged and the volume cannot be mounted even with the mount option headerbak. Example: /m ro</p>
+<p><strong>label=LabelValue</strong>: Use the given string value <strong>LabelValue</strong> as a label of the mounted volume in Windows Explorer. The maximum length for
+<strong>LabelValue&nbsp;</strong> is 32 characters for NTFS volumes and 11 characters for FAT volumes. For example,
+<em>/m label=MyDrive</em> will set the label of the drive in Explorer to <em>MyDrive</em>.</p>
+<p><strong>noattach</strong>: Only create virtual device without actually attaching the mounted volume to the selected drive letter.</p>
+<p>Please note that this switch may be present several times in the command line in order to specify multiple mount options (e.g.: /m rm /m ts)</p>
+</td>
+</tr>
+<tr>
+<td><em>/DisableDeviceUpdate</em>&nbsp;</td>
+<td>Disables periodic internel check on devices connected to the system that is used for handling favorites identified with VolumeID and replace it with on-demande checks.</td>
+</tr>
+<tr>
+<td><em>/protectMemory</em>&nbsp;</td>
+<td>If it is followed by <strong>y</strong> or <strong>yes</strong> or if no parameter is specified: Activates a mechanism that protects VeraCrypt process memory from being accessed by other non-admin processes.
+<br>
+If it is followed by <strong>n</strong> or <strong>no</strong> (ONLY allowed for portable mode): disables the memory protection mechanism (e.g., /protectMemory n).<br>
+</td>
+</tr>
+<tr>
+<td><em>/protectScreen</em>&nbsp;</td>
+<td>If it is followed by <strong>y</strong> or <strong>yes</strong> or if no parameter is specified: Activates a mechanism that protects VeraCrypt against screenshots and screen recordings.
+<br>
+If it is followed by <strong>n</strong> or <strong>no</strong> (ONLY allowed for portable mode): disables the screen protection mechanism (e.g., /protectScreen n).<br>
+</td>
+</tr>
+<tr>
+<td><em>/signalExit</em>&nbsp;</td>
+<td>It must be followed by a parameter specifying the name of the signal to send to unblock a waiting <a href="https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/waitfor" target="_blank">WAITFOR.EXE</a> command when VeraCrypt exists.<br>
+The name of signal must be the same as the one specified to WAITFOR.EXE command (e.g."veracrypt.exe /q /v test.hc /l Z /signal SigName" followed by "waitfor.exe SigName"<br>
+This switch is ignored if /q is not specified</td>
+</tr>
+</tbody>
+</table>
+<h4>VeraCrypt Format.exe (VeraCrypt Volume Creation Wizard):</h4>
+<table border="1" cellspacing="0" cellpadding="0">
+<tbody>
+<tr>
+<td>/create</td>
+<td>Create a container based volume in command line mode. It must be followed by the file name of the container to be created.</td>
+</tr>
+<tr>
+<td>/size</td>
+<td>
+<p>(Only with /create)<br>
+It must be followed by a parameter indicating the size of the container file that will be created. This parameter is a number indicating the size in Bytes. It can have a suffixe 'K', 'M', 'G' or 'T' to indicate that the value is in Kilobytes, Megabytes, Gigabytes
+ or Terabytes respectively. For example:</p>
+<ul>
+<li>/size 5000000: the container size will be 5000000 bytes </li><li>/size 25K: the container size will be 25 KiloBytes. </li><li>/size 100M: the container size will be 100 MegaBytes. </li><li>/size 2G: the container size will be 2 GigaBytes. </li><li>/size 1T: the container size will be 1 TeraBytes. </li></ul>
+</td>
+</tr>
+<tr>
+<td>&nbsp;/password</td>
+<td>&nbsp;(Only with /create)<br>
+It must be followed by a parameter indicating the password of the container that will be created.</td>
+</tr>
+<tr>
+<td>&nbsp;/keyfile or /k</td>
+<td>&nbsp;(Only with /create)<br>
+It must be followed by a parameter specifying a keyfile or a keyfile search path. For multiple keyfiles, specify e.g.: /k c:\keyfile1.dat /k d:\KeyfileFolder /k c:\kf2 To specify a keyfile stored on a security token or smart card, use the following syntax:
+ token://slot/SLOT_NUMBER/file/FILE_NAME</td>
+</tr>
+<tr>
+<td><em>/tokenlib</em></td>
+<td>&nbsp;(Only with /create)<br>
+It must be followed by a parameter indicating the PKCS #11 library to use for security tokens and smart cards. (e.g.: /tokenlib c:\pkcs11lib.dll)</td>
+</tr>
+<tr>
+<td><em>/tokenpin</em></td>
+<td>&nbsp;(Only with /create)<br>
+It must be followed by a parameter indicating the PIN to use in order to authenticate to the security token or smart card (e.g.: /tokenpin 0000). Warning: This method of entering a smart card PIN may be insecure, for example, when an unencrypted command
+ prompt history log is being saved to unencrypted disk.</td>
+</tr>
+<tr>
+<td>&nbsp;<em>/hash</em></td>
+<td>(Only with /create)<br>
+It must be followed by a parameter indicating the PRF hash algorithm to use when creating the volume. It has the same syntax as VeraCrypt.exe.</td>
+</tr>
+<tr>
+<td>/encryption</td>
+<td>(Only with /create)<br>
+It must be followed by a parameter indicating the encryption algorithm to use. The default is AES if this switch is not specified. The parameter can have the following values (case insensitive):
+<ul>
+<li>AES </li><li>Serpent </li><li>Twofish </li><li>Camellia </li><li>Kuznyechik </li><li>AES(Twofish) </li><li>AES(Twofish(Serpent)) </li><li>Serpent(AES) </li><li>Serpent(Twofish(AES)) </li><li>Twofish(Serpent) </li>
+<li>Camellia(Kuznyechik) </li>
+<li>Kuznyechik(Twofish) </li>
+<li>Camellia(Serpent) </li>
+<li>Kuznyechik(AES) </li>
+<li>Kuznyechik(Serpent(Camellia)) </li>
+</ul>
+</td>
+</tr>
+<tr>
+<td>/filesystem</td>
+<td>(Only with /create)<br>
+It must be followed by a parameter indicating the file system to use for the volume. The parameter can have the following values:
+<ul>
+<li>None: don't use any filesystem </li><li>FAT: format using FAT/FAT32 </li><li>NTFS: format using NTFS. Please note that in this case a UAC prompt will be displayed unless the process is run with full administrative privileges.
+</li>
+<li>ExFAT: format using ExFAT. This switch is available starting from Windows Vista SP1 </li>
+<li>ReFS: format using ReFS. This switch is available starting from Windows 10 </li>
+</ul>
+</td>
+</tr>
+<tr>
+<td>/dynamic</td>
+<td>(Only with /create)<br>
+It has no parameters and it indicates that the volume will be created as a dynamic volume.</td>
+</tr>
+<tr>
+<td>/force</td>
+<td>(Only with /create)<br>
+It has no parameters and it indicates that overwrite will be forced without requiring user confirmation.</td>
+</tr>
+<tr>
+<td>/silent</td>
+<td>(Only with /create)<br>
+It has no parameters and it indicates that no message box or dialog will be displayed to the user. If there is any error, the operation will fail silently.</td>
+</tr>
+<tr>
+<td><em>/noisocheck</em> or <em>/n</em></td>
+<td>Do not verify that VeraCrypt Rescue Disks are correctly burned. <strong>WARNING</strong>: Never attempt to use this option to facilitate the reuse of a previously created VeraCrypt Rescue Disk. Note that every time you encrypt a system partition/drive,
+ you must create a new VeraCrypt Rescue Disk even if you use the same password. A previously created VeraCrypt Rescue Disk cannot be reused as it was created for a different master key.</td>
+</tr>
+<tr>
+<td>/nosizecheck</td>
+<td>Don't check that the given size of the file container is smaller than the available disk free. This applies to both UI and command line.</td>
+</tr>
+<tr>
+<td>/quick</td>
+<td>Perform quick formatting of volumes instead of full formatting. This applies to both UI and command line.</td>
+</tr>
+<tr>
+<td>/FastCreateFile</td>
+<td>Enables a faster, albeit potentially insecure, method for creating file containers. This option carries security risks as it can embed existing disk content into the file container, possibly exposing sensitive data if an attacker gains access to it. Note that this switch affects all file container creation methods, whether initiated from the command line, using the /create switch, or through the UI wizard.</td>
+</tr>
+<tr>
+<td><em>/protectMemory</em>&nbsp;</td>
+<td>Activates a mechanism that protects VeraCrypt Format process memory from being accessed by other non-admin processes.</td>
+</tr>
+<tr>
+<td><em>/secureDesktop</em></td>
+<td>If it is followed by <strong>y</strong> or <strong>yes</strong> or if no parameter is specified: display password dialog and token PIN dialog in a dedicated secure desktop to protect against certain types of attacks.<br>
+If it is followed by <strong>n</strong> or <strong>no</strong>: the password dialog and token PIN dialog are displayed in the normal desktop.</td>
+</tr>
+</tbody>
+</table>
+<h4>Syntax</h4>
+<p>VeraCrypt.exe [/tc] [/hash {sha256|sha-256|sha512|sha-512|whirlpool |blake2s|blake2s-256}][/a [devices|favorites]] [/b] [/c [y|n|f]] [/d [drive letter]] [/e] [/f] [/h [y|n]] [/k keyfile or search path] [tryemptypass [y|n]] [/l drive letter] [/m {bk|rm|recovery|ro|sm|ts|noattach}]
+ [/p password] [/pim pimvalue] [/q [background|preferences]] [/s] [/tokenlib path] [/v volume] [/w]</p>
+<p>&quot;VeraCrypt Format.exe&quot; [/n] [/create] [/size number[{K|M|G|T}]] [/p password]&nbsp; [/encryption {AES | Serpent | Twofish | Camellia | Kuznyechik | AES(Twofish) | AES(Twofish(Serpent)) | Serpent(AES) | Serpent(Twofish(AES)) | Twofish(Serpent) | Camellia(Kuznyechik) | Kuznyechik(Twofish) | Camellia(Serpent) | Kuznyechik(AES) | Kuznyechik(Serpent(Camellia)))}] [/hash {sha256|sha-256|sha512|sha-512|whirlpool|blake2s|blake2s-256}]
+ [/filesystem {None|FAT|NTFS|ExFAT|ReFS}] [/dynamic] [/force] [/silent] [/noisocheck] [FastCreateFile] [/quick]</p>
+<p>Note that the order in which options are specified does not matter.</p>
+<h4>Examples</h4>
+<p>Mount the volume <em>d:\myvolume</em> as the first free drive letter, using the password prompt (the main program window will not be displayed):</p>
+<p>veracrypt /q /v d:\myvolume</p>
+<p>Unmount a volume mounted as the drive letter <em>X</em> (the main program window will not be displayed):</p>
+<p>veracrypt /q /d x</p>
+<p>Mount a volume called <em>myvolume.tc</em> using the password <em>MyPassword</em>, as the drive letter
+<em>X</em>. VeraCrypt will open an explorer window and beep; mounting will be automatic:</p>
+<p>veracrypt /v myvolume.tc /l x /a /p MyPassword /e /b</p>
+<p>Create a 10 MB file container using the password <em>test</em> and formatted using FAT:</p>
+<p><code>&quot;C:\Program Files\VeraCrypt\VeraCrypt Format.exe&quot; /create c:\Data\test.hc /password test /hash sha512 /encryption serpent /filesystem FAT /size 10M /force</code></p>
+</div>
+</div><div class="ClearBoth"></div></body></html>

doc/html/en/Command Line Usage.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
@@ -35,295 +34,12 @@
 <div class="wikidoc">
 <div>
 <h1>Command Line Usage</h1>
-<p>Note that this section applies to the Windows version of VeraCrypt. For information on command line usage applying to the
-<strong>Linux and Mac OS X versions</strong>, please run: veracrypt &ndash;h</p>
-<table border="1" cellspacing="0" cellpadding="1">
-<tbody>
-<tr>
-<td><em>/help</em> or <em>/?</em></td>
-<td>Display command line help.</td>
-</tr>
-<tr>
-<td><em>/truecrypt or /tc</em></td>
-<td>Activate TrueCrypt compatibility mode which enables mounting volumes created with TrueCrypt 6.x and 7.x series.</td>
-</tr>
-<tr>
-<td><em>/hash</em></td>
-<td>It must be followed by a parameter indicating the PRF hash algorithm to use when mounting the volume. Possible values for /hash parameter are: sha256, sha-256, sha512, sha-512, whirlpool, blake2s and blake2s-256. When /hash is omitted, VeraCrypt will try
- all possible PRF algorithms thus lengthening the mount operation time.</td>
-</tr>
-<tr>
-<td id="volume"><em>/volume</em> or <em>/v</em></td>
-<td>
-<p>It must be followed by a parameter indicating the file and path name of a VeraCrypt volume to mount (do not use when unmounting) or the Volume ID of the disk/partition to mount.<br>
-The syntax of the volume ID is <strong>ID:XXXXXX...XX</strong> where the XX part is a 64 hexadecimal characters string that represent the 32-Bytes ID of the desired volume to mount.<br>
-<br>
-To mount a partition/device-hosted volume, use, for example, /v \Device\Harddisk1\Partition3 (to determine the path to a partition/device, run VeraCrypt and click
-<em>Select Device</em>). You can also mount a partition or dynamic volume using its volume name (for example, /v \\?\Volume{5cceb196-48bf-46ab-ad00-70965512253a}\). To determine the volume name use e.g. mountvol.exe. Also note that device paths are case-sensitive.<br>
-<br>
-You can also specify the Volume ID of the partition/device-hosted volume to mount, for example: /v ID:53B9A8D59CC84264004DA8728FC8F3E2EE6C130145ABD3835695C29FD601EDCA. The Volume ID value can be retrieved using the volume properties dialog.</p>
-</td>
-</tr>
-<tr>
-<td><em>/letter</em> or <em>/l</em></td>
-<td>It must be followed by a parameter indicating the driver letter to mount the volume as. When /l is omitted and when /a is used, the first free drive letter is used.</td>
-</tr>
-<tr>
-<td><em>/explore</em> or <em>/e</em></td>
-<td>Open an Explorer window after a volume has been mounted.</td>
-</tr>
-<tr>
-<td><em>/beep</em> or <em>/b</em></td>
-<td>Beep after a volume has been successfully mounted or unmounted.</td>
-</tr>
-<tr>
-<td><em>/auto</em> or <em>/a</em></td>
-<td>If no parameter is specified, automatically mount the volume. If devices is specified as the parameter (e.g., /a devices), auto-mount all currently accessible device/partition-hosted VeraCrypt volumes. If favorites is specified as the parameter, auto-mount
- favorite volumes. Note that /auto is implicit if /quit and /volume are specified. If you need to prevent the application window from appearing, use /quit.</td>
-</tr>
-<tr>
-<td><em>/unmount</em> or <em>/u</em></td>
-<td>Unmount volume specified by drive letter (e.g., /u x). When no drive letter is specified, unmounts all currently mounted VeraCrypt volumes.</td>
-</tr>
-<tr>
-<td><em>/dismount</em> or <em>/d</em></td>
-<td>Deprecated. Please use /unmount or /u.</td>
-</tr>
-<tr>
-<td><em>/force</em> or <em>/f</em></td>
-<td>Forces unmount (if the volume to be unmounted contains files being used by the system or an application) and forces mounting in shared mode (i.e., without exclusive access).</td>
-</tr>
-<tr>
-<td><em>/keyfile</em> or <em>/k</em></td>
-<td>It must be followed by a parameter specifying a keyfile or a keyfile search path. For multiple keyfiles, specify e.g.: /k c:\keyfile1.dat /k d:\KeyfileFolder /k c:\kf2 To specify a keyfile stored on a security token or smart card, use the following syntax:
- token://slot/SLOT_NUMBER/file/FILE_NAME</td>
-</tr>
-<tr id="tryemptypass">
-<td><em>/tryemptypass&nbsp;&nbsp; </em></td>
-<td>ONLY when default keyfile configured or when a keyfile is specified in the command line.<br>
-If it is followed by <strong>y</strong> or <strong>yes</strong> or if no parameter is specified: try to mount using an empty password and the keyfile before displaying password prompt.<br>
-if it is followed by <strong>n </strong>or<strong> no</strong>: don't try to mount using an empty password and the keyfile, and display password prompt right away.</td>
-</tr>
-<tr>
-<td><em>/nowaitdlg</em></td>
-<td>If it is followed by <strong>y</strong> or <strong>yes</strong> or if no parameter is specified: don&rsquo;t display the waiting dialog while performing operations like mounting volumes.<br>
-If it is followed by <strong>n</strong> or <strong>no</strong>: force the display waiting dialog is displayed while performing operations.</td>
-</tr>
-<tr>
-<td><em>/secureDesktop</em></td>
-<td>If it is followed by <strong>y</strong> or <strong>yes</strong> or if no parameter is specified: display password dialog and token PIN dialog in a dedicated secure desktop to protect against certain types of attacks.<br>
-If it is followed by <strong>n</strong> or <strong>no</strong>: the password dialog and token PIN dialog are displayed in the normal desktop.</td>
-</tr>
-<tr>
-<td><em>/tokenlib</em></td>
-<td>It must be followed by a parameter indicating the PKCS #11 library to use for security tokens and smart cards. (e.g.: /tokenlib c:\pkcs11lib.dll)</td>
-</tr>
-<tr>
-<td><em>/tokenpin</em></td>
-<td>It must be followed by a parameter indicating the PIN to use in order to authenticate to the security token or smart card (e.g.: /tokenpin 0000). Warning: This method of entering a smart card PIN may be insecure, for example, when an unencrypted command
- prompt history log is being saved to unencrypted disk.</td>
-</tr>
-<tr>
-<td><em>/cache</em> or <em>/c</em></td>
-<td>If it is followed by <strong>y</strong> or <strong>yes</strong> or if no parameter is specified: enable password cache;
-<br>
-If it is followed by <strong>p </strong>or<strong> pim</strong>: enable both password and PIM cache (e.g., /c p).<br>
-If it is followed by <strong>n </strong>or<strong> no</strong>: disable password cache (e.g., /c n).<br>
-If it is followed by <strong>f </strong>or<strong> favorites</strong>: temporary cache password when mounting multiple favorites&nbsp; (e.g., /c f).<br>
-Note that turning the password cache off will not clear it (use /w to clear the password cache).</td>
-</tr>
-<tr>
-<td><em>/history</em> or <em>/h</em></td>
-<td>If it is followed by <strong>y</strong> or no parameter: enables saving history of mounted volumes; if it is followed by
-<strong>n</strong>: disables saving history of mounted volumes (e.g., /h n).</td>
-</tr>
-<tr>
-<td><em>/wipecache</em> or <em>/w</em></td>
-<td>Wipes any passwords cached in the driver memory.</td>
-</tr>
-<tr>
-<td><em>/password</em> or <em>/p</em></td>
-<td>It must be followed by a parameter indicating the volume password. If the password contains spaces, it must be enclosed in quotation marks (e.g., /p &rdquo;My Password&rdquo;). Use /p &rdquo;&rdquo; to specify an empty password.
-<em>Warning: This method of entering a volume password may be insecure, for example, when an unencrypted command prompt history log is being saved to unencrypted disk.</em></td>
-</tr>
-<tr>
-<td><em>/pim</em></td>
-<td>It must be followed by a positive integer indicating the PIM (Personal Iterations Multiplier) to use for the volume.</td>
-</tr>
-<tr>
-<td><em>/quit</em> or <em>/q</em></td>
-<td>Automatically perform requested actions and exit (main VeraCrypt window will not be displayed). If preferences is specified as the parameter (e.g., /q preferences), then program settings are loaded/saved and they override settings specified on the command
- line. /q background launches the VeraCrypt Background Task (tray icon) unless it is disabled in the Preferences.</td>
-</tr>
-<tr>
-<td><em>/silent</em> or <em>/s</em></td>
-<td>If /q is specified, suppresses interaction with the user (prompts, error messages, warnings, etc.). If /q is not specified, this option has no effect.</td>
-</tr>
-<tr>
-<td><em>/mountoption</em> or <em>/m</em></td>
-<td>
-<p>It must be followed by a parameter which can have one of the values indicated below.</p>
-<p><strong>ro</strong> or<strong> readonly</strong>: Mount volume as read-only.</p>
-<p><strong>rm</strong> or <strong>removable</strong>: Mount volume as removable medium (see section
-<a href="Removable%20Medium%20Volume.html">
-<em>Volume Mounted as Removable Medium</em></a>).</p>
-<p><strong>ts</strong> or <strong>timestamp</strong>: Do not preserve container modification timestamp.</p>
-<p><strong>sm</strong> or <strong>system</strong>: Without pre-boot authentication, mount a partition that is within the key scope of system encryption (for example, a partition located on the encrypted system drive of another operating system that is not running).
- Useful e.g. for backup or repair operations. Note: If you supply a password as a parameter of /p, make sure that the password has been typed using the standard US keyboard layout (in contrast, the GUI ensures this automatically). This is required due to the
- fact that the password needs to be typed in the pre-boot environment (before Windows starts) where non-US Windows keyboard layouts are not available.</p>
-<p><strong>bk</strong> or <strong>headerbak</strong>: Mount volume using embedded backup header. Note: All volumes created by VeraCrypt contain an embedded backup header (located at the end of the volume).</p>
-<p><strong>recovery</strong>: Do not verify any checksums stored in the volume header. This option should be used only when the volume header is damaged and the volume cannot be mounted even with the mount option headerbak. Example: /m ro</p>
-<p><strong>label=LabelValue</strong>: Use the given string value <strong>LabelValue</strong> as a label of the mounted volume in Windows Explorer. The maximum length for
-<strong>LabelValue&nbsp;</strong> is 32 characters for NTFS volumes and 11 characters for FAT volumes. For example,
-<em>/m label=MyDrive</em> will set the label of the drive in Explorer to <em>MyDrive</em>.</p>
-<p><strong>noattach</strong>: Only create virtual device without actually attaching the mounted volume to the selected drive letter.</p>
-<p>Please note that this switch may be present several times in the command line in order to specify multiple mount options (e.g.: /m rm /m ts)</p>
-</td>
-</tr>
-<tr>
-<td><em>/DisableDeviceUpdate</em>&nbsp;</td>
-<td>Disables periodic internel check on devices connected to the system that is used for handling favorites identified with VolumeID and replace it with on-demande checks.</td>
-</tr>
-<tr>
-<td><em>/protectMemory</em>&nbsp;</td>
-<td>Activates a mechanism that protects VeraCrypt process memory from being accessed by other non-admin processes.</td>
-</tr>
-<tr>
-<td><em>/signalExit</em>&nbsp;</td>
-<td>It must be followed by a parameter specifying the name of the signal to send to unblock a waiting <a href="https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/waitfor" target="_blank">WAITFOR.EXE</a> command when VeraCrypt exists.<br>
-The name of signal must be the same as the one specified to WAITFOR.EXE command (e.g."veracrypt.exe /q /v test.hc /l Z /signal SigName" followed by "waitfor.exe SigName"<br>
-This switch is ignored if /q is not specified</td>
-</tr>
-</tbody>
-</table>
-<h4>VeraCrypt Format.exe (VeraCrypt Volume Creation Wizard):</h4>
-<table border="1" cellspacing="0" cellpadding="0">
-<tbody>
-<tr>
-<td>/create</td>
-<td>Create a container based volume in command line mode. It must be followed by the file name of the container to be created.</td>
-</tr>
-<tr>
-<td>/size</td>
-<td>
-<p>(Only with /create)<br>
-It must be followed by a parameter indicating the size of the container file that will be created. This parameter is a number indicating the size in Bytes. It can have a suffixe 'K', 'M', 'G' or 'T' to indicate that the value is in Kilobytes, Megabytes, Gigabytes
- or Terabytes respectively. For example:</p>
+<p>VeraCrypt uses different command-line syntaxes on Windows and on Unix-like systems. Select the page that matches your operating system:</p>
 <ul>
-<li>/size 5000000: the container size will be 5000000 bytes </li><li>/size 25K: the container size will be 25 KiloBytes. </li><li>/size 100M: the container size will be 100 MegaBytes. </li><li>/size 2G: the container size will be 2 GigaBytes. </li><li>/size 1T: the container size will be 1 TeraBytes. </li></ul>
-</td>
-</tr>
-<tr>
-<td>&nbsp;/password</td>
-<td>&nbsp;(Only with /create)<br>
-It must be followed by a parameter indicating the password of the container that will be created.</td>
-</tr>
-<tr>
-<td>&nbsp;/keyfile or /k</td>
-<td>&nbsp;(Only with /create)<br>
-It must be followed by a parameter specifying a keyfile or a keyfile search path. For multiple keyfiles, specify e.g.: /k c:\keyfile1.dat /k d:\KeyfileFolder /k c:\kf2 To specify a keyfile stored on a security token or smart card, use the following syntax:
- token://slot/SLOT_NUMBER/file/FILE_NAME</td>
-</tr>
-<tr>
-<td><em>/tokenlib</em></td>
-<td>&nbsp;(Only with /create)<br>
-It must be followed by a parameter indicating the PKCS #11 library to use for security tokens and smart cards. (e.g.: /tokenlib c:\pkcs11lib.dll)</td>
-</tr>
-<tr>
-<td><em>/tokenpin</em></td>
-<td>&nbsp;(Only with /create)<br>
-It must be followed by a parameter indicating the PIN to use in order to authenticate to the security token or smart card (e.g.: /tokenpin 0000). Warning: This method of entering a smart card PIN may be insecure, for example, when an unencrypted command
- prompt history log is being saved to unencrypted disk.</td>
-</tr>
-<tr>
-<td>&nbsp;<em>/hash</em></td>
-<td>(Only with /create)<br>
-It must be followed by a parameter indicating the PRF hash algorithm to use when creating the volume. It has the same syntax as VeraCrypt.exe.</td>
-</tr>
-<tr>
-<td>/encryption</td>
-<td>(Only with /create)<br>
-It must be followed by a parameter indicating the encryption algorithm to use. The default is AES if this switch is not specified. The parameter can have the following values (case insensitive):
-<ul>
-<li>AES </li><li>Serpent </li><li>Twofish </li><li>Camellia </li><li>Kuznyechik </li><li>AES(Twofish) </li><li>AES(Twofish(Serpent)) </li><li>Serpent(AES) </li><li>Serpent(Twofish(AES)) </li><li>Twofish(Serpent) </li>
-<li>Camellia(Kuznyechik) </li>
-<li>Kuznyechik(Twofish) </li>
-<li>Camellia(Serpent) </li>
-<li>Kuznyechik(AES) </li>
-<li>Kuznyechik(Serpent(Camellia)) </li>
+<li><a href="Command%20Line%20Usage%20for%20Windows.html">Command Line Usage for Windows</a></li>
+<li><a href="Command%20Line%20Usage%20for%20Unix.html">Command Line Usage for Linux and macOS</a></li>
 </ul>
-</td>
-</tr>
-<tr>
-<td>/filesystem</td>
-<td>(Only with /create)<br>
-It must be followed by a parameter indicating the file system to use for the volume. The parameter can have the following values:
-<ul>
-<li>None: don't use any filesystem </li><li>FAT: format using FAT/FAT32 </li><li>NTFS: format using NTFS. Please note that in this case a UAC prompt will be displayed unless the process is run with full administrative privileges.
-</li>
-<li>ExFAT: format using ExFAT. This switch is available starting from Windows Vista SP1 </li>
-<li>ReFS: format using ReFS. This switch is available starting from Windows 10 </li>
-</ul>
-</td>
-</tr>
-<tr>
-<td>/dynamic</td>
-<td>(Only with /create)<br>
-It has no parameters and it indicates that the volume will be created as a dynamic volume.</td>
-</tr>
-<tr>
-<td>/force</td>
-<td>(Only with /create)<br>
-It has no parameters and it indicates that overwrite will be forced without requiring user confirmation.</td>
-</tr>
-<tr>
-<td>/silent</td>
-<td>(Only with /create)<br>
-It has no parameters and it indicates that no message box or dialog will be displayed to the user. If there is any error, the operation will fail silently.</td>
-</tr>
-<tr>
-<td><em>/noisocheck</em> or <em>/n</em></td>
-<td>Do not verify that VeraCrypt Rescue Disks are correctly burned. <strong>WARNING</strong>: Never attempt to use this option to facilitate the reuse of a previously created VeraCrypt Rescue Disk. Note that every time you encrypt a system partition/drive,
- you must create a new VeraCrypt Rescue Disk even if you use the same password. A previously created VeraCrypt Rescue Disk cannot be reused as it was created for a different master key.</td>
-</tr>
-<tr>
-<td>/nosizecheck</td>
-<td>Don't check that the given size of the file container is smaller than the available disk free. This applies to both UI and command line.</td>
-</tr>
-<tr>
-<td>/quick</td>
-<td>Perform quick formatting of volumes instead of full formatting. This applies to both UI and command line.</td>
-</tr>
-<tr>
-<td>/FastCreateFile</td>
-<td>Enables a faster, albeit potentially insecure, method for creating file containers. This option carries security risks as it can embed existing disk content into the file container, possibly exposing sensitive data if an attacker gains access to it. Note that this switch affects all file container creation methods, whether initiated from the command line, using the /create switch, or through the UI wizard.</td>
-</tr>
-<tr>
-<td><em>/protectMemory</em>&nbsp;</td>
-<td>Activates a mechanism that protects VeraCrypt Format process memory from being accessed by other non-admin processes.</td>
-</tr>
-<tr>
-<td><em>/secureDesktop</em></td>
-<td>If it is followed by <strong>y</strong> or <strong>yes</strong> or if no parameter is specified: display password dialog and token PIN dialog in a dedicated secure desktop to protect against certain types of attacks.<br>
-If it is followed by <strong>n</strong> or <strong>no</strong>: the password dialog and token PIN dialog are displayed in the normal desktop.</td>
-</tr>
-</tbody>
-</table>
-<h4>Syntax</h4>
-<p>VeraCrypt.exe [/tc] [/hash {sha256|sha-256|sha512|sha-512|whirlpool |blake2s|blake2s-256}][/a [devices|favorites]] [/b] [/c [y|n|f]] [/d [drive letter]] [/e] [/f] [/h [y|n]] [/k keyfile or search path] [tryemptypass [y|n]] [/l drive letter] [/m {bk|rm|recovery|ro|sm|ts|noattach}]
- [/p password] [/pim pimvalue] [/q [background|preferences]] [/s] [/tokenlib path] [/v volume] [/w]</p>
-<p>&quot;VeraCrypt Format.exe&quot; [/n] [/create] [/size number[{K|M|G|T}]] [/p password]&nbsp; [/encryption {AES | Serpent | Twofish | Camellia | Kuznyechik | AES(Twofish) | AES(Twofish(Serpent)) | Serpent(AES) | Serpent(Twofish(AES)) | Twofish(Serpent) | Camellia(Kuznyechik) | Kuznyechik(Twofish) | Camellia(Serpent) | Kuznyechik(AES) | Kuznyechik(Serpent(Camellia)))}] [/hash {sha256|sha-256|sha512|sha-512|whirlpool|blake2s|blake2s-256}]
- [/filesystem {None|FAT|NTFS|ExFAT|ReFS}] [/dynamic] [/force] [/silent] [/noisocheck] [FastCreateFile] [/quick]</p>
-<p>Note that the order in which options are specified does not matter.</p>
-<h4>Examples</h4>
-<p>Mount the volume <em>d:\myvolume</em> as the first free drive letter, using the password prompt (the main program window will not be displayed):</p>
-<p>veracrypt /q /v d:\myvolume</p>
-<p>Unmount a volume mounted as the drive letter <em>X</em> (the main program window will not be displayed):</p>
-<p>veracrypt /q /d x</p>
-<p>Mount a volume called <em>myvolume.tc</em> using the password <em>MyPassword</em>, as the drive letter
-<em>X</em>. VeraCrypt will open an explorer window and beep; mounting will be automatic:</p>
-<p>veracrypt /v myvolume.tc /l x /a /p MyPassword /e /b</p>
-<p>Create a 10 MB file container using the password <em>test</em> and formatted using FAT:</p>
-<p><code>&quot;C:\Program Files\VeraCrypt\VeraCrypt Format.exe&quot; /create c:\Data\test.hc /password test /hash sha512 /encryption serpent /filesystem FAT /size 10M /force</code></p>
+<p>On Linux and macOS, command-line help for the installed VeraCrypt build can also be displayed in a terminal with:</p>
+<p><code>veracrypt -t --help</code></p>
 </div>
 </div><div class="ClearBoth"></div></body></html>

doc/html/en/CompilingGuidelineLinux.html

@@ -1,6 +1,11 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
+<!DOCTYPE html>
+<html lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
+<meta name="description" content="VeraCrypt is free open-source disk encryption software for Windows, Mac OS X and Linux. In case an attacker forces you to reveal the password, VeraCrypt provides plausible deniability. In contrast to file encryption, data encryption performed by VeraCrypt is real-time (on-the-fly), automatic, transparent, needs very little memory, and does not involve temporary unencrypted files."/>
+<meta name="keywords" content="encryption, security"/>
+<link href="styles.css" rel="stylesheet" type="text/css" />
 <style>
 .textbox {
   vertical-align: top;
@@ -23,14 +28,6 @@
 
 
 </style>
-
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
-<head>
-<meta http-equiv="content-type" content="text/html; charset=utf-8" />
-<title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
-<meta name="description" content="VeraCrypt is free open-source disk encryption software for Windows, Mac OS X and Linux. In case an attacker forces you to reveal the password, VeraCrypt provides plausible deniability. In contrast to file encryption, data encryption performed by VeraCrypt is real-time (on-the-fly), automatic, transparent, needs very little memory, and does not involve temporary unencrypted files."/>
-<meta name="keywords" content="encryption, security"/>
-<link href="styles.css" rel="stylesheet" type="text/css" />
 </head>
 <body>
 
@@ -83,15 +80,15 @@ The following components are required for compiling VeraCrypt:
 <div class="wikidoc">
 <p>Below are the procedure steps. Clicking on any of the link takes directly to the related step:
 <ul>
-<li><strong><a href="#InstallationOfGNUMake">Installation of GNU Make</a></li></strong>
-<li><strong><a href="#InstallationOfGNUCompiler">Installation of GNU C/C++ Compiler</a></li></strong>
-<li><strong><a href="#InstallationOfYASM">Installation of YASM</a></li></strong>
-<li><strong><a href="#InstallationOfPKGConfig">Installation of pkg-config</a></li></strong>
-<li><strong><a href="#InstallationOfwxWidgets">Installation of wxWidgets 3.2</a></li></strong>
-<li><strong><a href="#InstallationOfFuse">Installation of libfuse</a></li></strong>
-<li><strong><a href="#InstallationOfPCSCLite">Installation of libpcsclite</a></li></strong>
-<li><strong><a href="#DownloadVeraCrypt">Download VeraCrypt</a></li></strong>
-<li><strong><a href="#CompileVeraCrypt">Compile VeraCrypt</a></li></strong>
+<li><strong><a href="#InstallationOfGNUMake">Installation of GNU Make</a></strong></li>
+<li><strong><a href="#InstallationOfGNUCompiler">Installation of GNU C/C++ Compiler</a></strong></li>
+<li><strong><a href="#InstallationOfYASM">Installation of YASM</a></strong></li>
+<li><strong><a href="#InstallationOfPKGConfig">Installation of pkg-config</a></strong></li>
+<li><strong><a href="#InstallationOfwxWidgets">Installation of wxWidgets 3.2</a></strong></li>
+<li><strong><a href="#InstallationOfFuse">Installation of libfuse</a></strong></li>
+<li><strong><a href="#InstallationOfPCSCLite">Installation of libpcsclite</a></strong></li>
+<li><strong><a href="#DownloadVeraCrypt">Download VeraCrypt</a></strong></li>
+<li><strong><a href="#CompileVeraCrypt">Compile VeraCrypt</a></strong></li>
 </ul>
 </p>
 <p>They can also be performed by running the below list of commands in a terminal or by copying them to a script:<br>

doc/html/en/CompilingGuidelineWin.html

@@ -1,6 +1,14 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<!DOCTYPE html>
+<html lang="en">
 
+
+
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
+<meta name="description" content="VeraCrypt is free open-source disk encryption software for Windows, Mac OS X and Linux. In case an attacker forces you to reveal the password, VeraCrypt provides plausible deniability. In contrast to file encryption, data encryption performed by VeraCrypt is real-time (on-the-fly), automatic, transparent, needs very little memory, and does not involve temporary unencrypted files."/>
+<meta name="keywords" content="encryption, security"/>
+<link href="styles.css" rel="stylesheet" type="text/css" />
 <style>
 .textbox {
   vertical-align: top;
@@ -23,14 +31,6 @@
 
 
 </style>
-
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
-<head>
-<meta http-equiv="content-type" content="text/html; charset=utf-8" />
-<title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
-<meta name="description" content="VeraCrypt is free open-source disk encryption software for Windows, Mac OS X and Linux. In case an attacker forces you to reveal the password, VeraCrypt provides plausible deniability. In contrast to file encryption, data encryption performed by VeraCrypt is real-time (on-the-fly), automatic, transparent, needs very little memory, and does not involve temporary unencrypted files."/>
-<meta name="keywords" content="encryption, security"/>
-<link href="styles.css" rel="stylesheet" type="text/css" />
 </head>
 <body>
 
@@ -93,27 +93,27 @@ The following components are required for compiling VeraCrypt:
 <div class="wikidoc">
 Below are the procedure steps. Clicking on any of the link takes directly to the related step:
 <ul>
-<li><strong><a href="#InstallationOfMicrosoftVisualStudio2010">Installation of Microsoft Visual Studio 2010</a></li></strong>
-<li><strong><a href="#InstallationOfMicrosoftVisualStudio2010ServicePack1">Installation of Microsoft Visual Studio 2010 Service Pack 1</a></li></strong>
-<li><strong><a href="#InstallationOfNASM">Installation of NASM</a></li></strong>
-<li><strong><a href="#InstallationOfYASM">Installation of YASM</a></li></strong>
-<li><strong><a href="#InstallationOfVisualCPP">Installation of Microsoft Visual C++ 1.52</a></li></strong>
-<li><strong><a href="#InstallationOfWindowsSDK71PP">Installation of the Windows SDK 7.1</a></li></strong>
-<li><strong><a href="#InstallationOfWDK71PP">Installation of the Windows Driver Kit 7.1</a></li></strong>
-<li><strong><a href="#InstallationOfSDK81PP">Installation of the Windows 8.1 SDK</a></li></strong>
-<li><strong><a href="#InstallationOfGzip">Installation of gzip</a></li></strong>
-<li><strong><a href="#InstallationOfUpx">Installation of upx</a></li></strong>
-<li><strong><a href="#InstallationOf7zip">Installation of 7zip</a></li></strong>
-<li><strong><a href="#InstallationOfWix3">Installation of Wix3</a></li></strong>
-<li><strong><a href="#InstallationOfVS2019">Installation of Microsoft Visual Studio 2019</a></li></strong>
-<li><strong><a href="#InstallationOfWDK10">Installation of the Windows Driver Kit 2004</a></li></strong>
-<li><strong><a href="#InstallationOfVisualBuildTools">Installation of the Visual Studio build tools</a></li></strong>
-<li><strong><a href="#DownloadVeraCrypt">Download VeraCrypt Source Files</a></li></strong>
-<li><strong><a href="#CompileWin32X64">Compile the Win32/x64 Versions of VeraCrypt</a></li></strong>
-<li><strong><a href="#CompileARM64">Compile the ARM64 Version of VeraCrypt</a></li></strong>
-<li><strong><a href="#BuildVeraCryptExecutables">Build the VeraCrypt Executables</a></li></strong>
-<li><strong><a href="#ImportCertificates">Import the Certificates</a></li></strong>
-<li><strong><a href="#KnownIssues">Known Issues</a></li></strong>
+<li><strong><a href="#InstallationOfMicrosoftVisualStudio2010">Installation of Microsoft Visual Studio 2010</a></strong></li>
+<li><strong><a href="#InstallationOfMicrosoftVisualStudio2010ServicePack1">Installation of Microsoft Visual Studio 2010 Service Pack 1</a></strong></li>
+<li><strong><a href="#InstallationOfNASM">Installation of NASM</a></strong></li>
+<li><strong><a href="#InstallationOfYASM">Installation of YASM</a></strong></li>
+<li><strong><a href="#InstallationOfVisualCPP">Installation of Microsoft Visual C++ 1.52</a></strong></li>
+<li><strong><a href="#InstallationOfWindowsSDK71PP">Installation of the Windows SDK 7.1</a></strong></li>
+<li><strong><a href="#InstallationOfWDK71PP">Installation of the Windows Driver Kit 7.1</a></strong></li>
+<li><strong><a href="#InstallationOfSDK81PP">Installation of the Windows 8.1 SDK</a></strong></li>
+<li><strong><a href="#InstallationOfGzip">Installation of gzip</a></strong></li>
+<li><strong><a href="#InstallationOfUpx">Installation of upx</a></strong></li>
+<li><strong><a href="#InstallationOf7zip">Installation of 7zip</a></strong></li>
+<li><strong><a href="#InstallationOfWix3">Installation of Wix3</a></strong></li>
+<li><strong><a href="#InstallationOfVS2019">Installation of Microsoft Visual Studio 2019</a></strong></li>
+<li><strong><a href="#InstallationOfWDK10">Installation of the Windows Driver Kit 2004</a></strong></li>
+<li><strong><a href="#InstallationOfVisualBuildTools">Installation of the Visual Studio build tools</a></strong></li>
+<li><strong><a href="#DownloadVeraCrypt">Download VeraCrypt Source Files</a></strong></li>
+<li><strong><a href="#CompileWin32X64">Compile the Win32/x64 Versions of VeraCrypt</a></strong></li>
+<li><strong><a href="#CompileARM64">Compile the ARM64 Version of VeraCrypt</a></strong></li>
+<li><strong><a href="#BuildVeraCryptExecutables">Build the VeraCrypt Executables</a></strong></li>
+<li><strong><a href="#ImportCertificates">Import the Certificates</a></strong></li>
+<li><strong><a href="#KnownIssues">Known Issues</a></strong></li>
 </ul>
 </div>
 

doc/html/en/CompilingGuidelines.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
@@ -39,9 +38,9 @@
 <p>In order to build VeraCrypt from the source code, you can follow these step-by-step guidelines:
 <ul style="text-align:left; margin-top:18px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
-<a href="CompilingGuidelineWin.html" style="text-align:left; color:#0080c0; text-decoration:none.html">Windows Build Guide</a>
+<a href="CompilingGuidelineWin.html" style="text-align:left; color:#0080c0; text-decoration:none">Windows Build Guide</a>
 </li><li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
-<a href="CompilingGuidelineLinux.html" style="text-align:left; color:#0080c0; text-decoration:none.html">Linux Build Guide</a>
+<a href="CompilingGuidelineLinux.html" style="text-align:left; color:#0080c0; text-decoration:none">Linux Build Guide</a>
 </li></ul>
 </p>
 </div><div class="ClearBoth"></div></body></html>

doc/html/en/Contact.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/Contributed Resources.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/Conversion_Guide_VeraCrypt_1.26_and_Later.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Conversion Guide for Versions 1.26 and Later</title>

doc/html/en/Converting TrueCrypt volumes and partitions.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/Creating New Volumes.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
@@ -104,7 +103,7 @@ You can create FAT (whether it will be FAT12, FAT16, or FAT32, is automatically
 For more information about creating VeraCrypt volumes, see also the section <a href="Hidden%20Volume.html">
 <em>Hidden Volume</em></a>.</p>
 <p>&nbsp;</p>
-<p><a href="Favorite%20Volumes.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold.html">Next Section &gt;&gt;</a></p>
+<p><a href="Favorite%20Volumes.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold">Next Section &gt;&gt;</a></p>
 </div>
 </div>
 

doc/html/en/Data Leaks.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/Default Mount Parameters.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
@@ -42,10 +41,11 @@
 <p><img src="Home_VeraCrypt_Default_Mount_Parameters.png" alt="Default Mount Parameters Dialog"></p>
 <p>Make your modifications and then click OK.</p>
 <p>The chosen values are then written to VeraCrypt main configuration file (Configuration.xml) making them persistent.</p>
+<p>Under Linux, default filesystem mount options can also be specified in the <em>Mount options</em> field. For example, entering <code>noatime</code> makes VeraCrypt pass this option to Linux <code>mount -o</code> for subsequent mounts. These defaults can still be changed for an individual mount from the password dialog's <em>Options</em> button.</p>
 <p>All subsequent password request dialogs will use the default values chosen previously. For example, if in the Default Mount Parameters dialog you check TrueCrypt Mode and you select SHA-512 as a PRF, then subsequent password dialogs will look like:<br>
 <img src="Default Mount Parameters_VeraCrypt_password_using_default_parameters.png" alt="Mount Password Dialog using default values"></p>
 <p>&nbsp;</p>
-<p><strong>Note:</strong> The default mount parameters can be overridden by the&nbsp;<a href="Command%20Line%20Usage.html">Command Line</a> switches
+<p><strong>Note:</strong> The default mount parameters can be overridden by the&nbsp;<a href="Command%20Line%20Usage%20for%20Windows.html">Command Line</a> switches
 <strong>/tc</strong> and <strong>/hash</strong> which always take precedence.</p>
 <p>&nbsp;</p>
 </div><div class="ClearBoth"></div></body></html>

doc/html/en/Defragmenting.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/Digital Signatures.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/Disclaimers.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/Documentation.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
@@ -85,8 +84,17 @@
 <li><a href="BLAKE2s-256.html">BLAKE2s-256</a>
 </li><li><a href="SHA-256.html">SHA-256</a> </li><li><a href="SHA-512.html">SHA-512</a> </li><li><a href="Whirlpool.html">Whirlpool</a>
 </li><li><a href="Streebog.html">Streebog</a></li></ul>
+</li><li><strong><a href="Key%20Derivation%20Algorithms.html">Key Derivation Algorithms</a></strong>
+<ul>
+<li><a href="Argon2id.html">Argon2id</a></li>
+<li><a href="pbkdf2.html">PBKDF2</a></li>
+</ul>
 </li><li><strong><a href="Supported%20Operating%20Systems.html">Supported Operating Systems</a></strong>
 </li><li><strong><a href="Command%20Line%20Usage.html">Command Line Usage</a></strong>
+<ul>
+<li><a href="Command%20Line%20Usage%20for%20Windows.html">Windows</a>
+</li><li><a href="Command%20Line%20Usage%20for%20Unix.html">Linux and macOS</a>
+</li></ul>
 </li><li><strong><a href="Security%20Model.html">Security Model</a></strong>
 </li><li><strong><a href="Security%20Requirements%20and%20Precautions.html">Security Requirements And Precautions<br>
 </a></strong>

doc/html/en/Donation.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/Donation_Bank.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/EMV Smart Cards.html

@@ -1,5 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
   <head>
     <meta http-equiv="content-type" content="text/html; charset=utf-8" />
     <title>
@@ -76,7 +76,7 @@
           <em style="text-align: left">EMV Smart Cards</em> in the chapter
           <a
             href="Keyfiles%20in%20VeraCrypt.html"
-            style="text-align: left; color: #0080c0; text-decoration: none.html"
+            style="text-align: left; color: #0080c0; text-decoration: none"
           >
             <em style="text-align: left">Keyfiles</em></a
           >.

doc/html/en/Encryption Algorithms.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
@@ -268,5 +267,5 @@ XTS</td>
 For information about XTS mode, please see the section <a href="Modes%20of%20Operation.html" style="text-align:left; color:#0080c0; text-decoration:none">
 Modes of Operation</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-<a href="AES.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold.html">Next Section &gt;&gt;</a></div>
+<a href="AES.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold">Next Section &gt;&gt;</a></div>
 </div><div class="ClearBoth"></div></body></html>

doc/html/en/Encryption Scheme.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
@@ -51,10 +50,15 @@ Hidden Operating System</a>). If there is a hidden volume within this volume (or
 </li><li>Now VeraCrypt attempts to decrypt the standard volume header read in (1). All data used and generated in the course of the process of decryption are kept in RAM (VeraCrypt never saves them to disk). The following parameters are unknown&dagger; and have
  to be determined through the process of trial and error (i.e., by testing all possible combinations of the following):
 <ol type="a">
-<li>PRF used by the header key derivation function (as specified in PKCS #5 v2.0; see the section
+<li>Key Derivation Function (KDF) and associated parameters:
+<ul>
+<li><strong>PBKDF2-HMAC:</strong> PRF used by the header key derivation function (as specified in PKCS #5 v2.0; see the section
 <a href="Header%20Key%20Derivation.html">
 <em>Header Key Derivation, Salt, and Iteration Count</em></a>), which can be one of the following:
-<p>HMAC-SHA-512, HMAC-SHA-256, HMAC-BLAKE2S-256, HMAC-Whirlpool. If a PRF is explicitly specified by the user, it will be used directly without trying the other possibilities.</p>
+HMAC-SHA-512, HMAC-SHA-256, HMAC-BLAKE2S-256, HMAC-Whirlpool, HMAC-Streebog.</li>
+<li><strong>Argon2id:</strong> Memory-hard key derivation function with internal BLAKE2b hash function.</li>
+</ul>
+<p>If a PRF is explicitly specified by the user, it will be used directly without trying the other possibilities.</p>
 <p>A password entered by the user (to which one or more keyfiles may have been applied &ndash; see the section
 <a href="Keyfiles%20in%20VeraCrypt.html">
 <em>Keyfiles</em></a>), a PIM value (if specified) and the salt read in (1) are passed to the header key derivation function, which produces a sequence of values (see the section
@@ -85,5 +89,5 @@ Hidden Operating System</a>). If there is a hidden volume within this volume (or
 <em>is</em> known (it can be determined by analyzing the contents of the unencrypted VeraCrypt Boot Loader stored in the first logical drive track or on the VeraCrypt Rescue Disk).</p>
 <p>** The master keys were generated during the volume creation and cannot be changed later. Volume password change is accomplished by re-encrypting the volume header using a new header key (derived from a new password).</p>
 <p>&nbsp;</p>
-<p><a href="Modes%20of%20Operation.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold.html">Next Section &gt;&gt;</a></p>
+<p><a href="Modes%20of%20Operation.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold">Next Section &gt;&gt;</a></p>
 </div><div class="ClearBoth"></div></body></html>

doc/html/en/FAQ.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
@@ -38,7 +37,7 @@
 Last Updated July 2nd, 2017</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <em style="text-align:left">This document is not guaranteed to be error-free and is provided &quot;as is&quot; without warranty of any kind. For more information, see
-<a href="Disclaimers.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="Disclaimers.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 Disclaimers</a>.</em></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
@@ -82,13 +81,13 @@ FBI failing to decrypt a TrueCrypt volume after a year of trying</a>. While we c
 <br style="text-align:left">
 <strong style="text-align:left">Is there a &quot;Quick Start Guide&quot; or some tutorial for beginners?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-Yes. The first chapter, <strong style="text-align:left"><a href="Beginner%27s%20Tutorial.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">Beginner's Tutorial</a></strong>, in the VeraCrypt
+Yes. The first chapter, <strong style="text-align:left"><a href="Beginner%27s%20Tutorial.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">Beginner's Tutorial</a></strong>, in the VeraCrypt
  User Guide contains screenshots and step-by-step instructions on how to create, mount, and use a VeraCrypt volume.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <br style="text-align:left">
 <strong style="text-align:left">Can I encrypt a partition/drive where Windows is installed?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-Yes, see the chapter <a href="System%20Encryption.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+Yes, see the chapter <a href="System%20Encryption.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 System Encryption</a> in the VeraCrypt User Guide.</div>
 <div id="BootingHang" style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <strong>The system encryption Pre Test fails because the bootloader hangs with the messaging &quot;booting&quot; after successfully verifying the password. How to make the Pre Test succeed?</strong></div>
@@ -171,11 +170,11 @@ Create two or more partitions on your USB flash drive. Leave the first partition
 Note: Windows can only access the primary partition of a USB flash drive, nevertheless the extra partitions remain accessible through VeraCrypt.
 </li><li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
 Create a VeraCrypt file container on the USB flash drive (for information on how to do so, see the chapter
-<strong style="text-align:left"><a href="Beginner%27s%20Tutorial.html" style="text-align:left; color:#0080c0; text-decoration:none.html">Beginner's Tutorial</a></strong>, in the
+<strong style="text-align:left"><a href="Beginner%27s%20Tutorial.html" style="text-align:left; color:#0080c0; text-decoration:none">Beginner's Tutorial</a></strong>, in the
 <a href="https://veracrypt.jp/en/Documentation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 VeraCrypt User Guide</a>). If you leave enough space on the USB flash drive (choose an appropriate size for the VeraCrypt container), you will also be able to store VeraCrypt on the USB flash drive (along with the container &ndash; not
 <em style="text-align:left">in</em> the container) and you will be able to run VeraCrypt from the USB flash drive (see also the chapter
-<a href="Portable%20Mode.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="Portable%20Mode.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 Portable Mode</a> in the <a href="https://veracrypt.jp/en/Documentation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 VeraCrypt User Guide</a>). </li></ol>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
@@ -190,7 +189,7 @@ Yes. The entire file system within a VeraCrypt volume is encrypted (including fi
 <strong style="text-align:left">Does VeraCrypt use parallelization?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 Yes. Increase in encryption/decryption speed is directly proportional to the number of cores/processors your computer has. For more information, please see the chapter
-<a href="Parallelization.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="Parallelization.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 Parallelization</a> in the <a href="https://veracrypt.jp/en/Documentation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 documentation</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
@@ -198,29 +197,29 @@ documentation</a>.</div>
 <strong style="text-align:left">Can data be read from and written to an encrypted volume/drive as fast as if the drive was not encrypted?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 Yes, since VeraCrypt uses pipelining and parallelization. For more information, please see the chapters
-<a href="Pipelining.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
-Pipelining</a> and <a href="Parallelization.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="Pipelining.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
+Pipelining</a> and <a href="Parallelization.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 Parallelization</a> in the <a href="https://veracrypt.jp/en/Documentation.html" style="text-align:left; color:#0080c0; text-decoration:none">
 documentation</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <br style="text-align:left">
 <strong style="text-align:left">Does VeraCrypt support hardware-accelerated encryption?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-Yes. For more information, please see the chapter <a href="Hardware%20Acceleration.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+Yes. For more information, please see the chapter <a href="Hardware%20Acceleration.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 Hardware Acceleration</a> in the <a href="https://veracrypt.jp/en/Documentation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 documentation</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <br style="text-align:left">
 <strong style="text-align:left">Is it possible to boot Windows installed in a hidden VeraCrypt volume?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-Yes, it is. For more information, please see the section <a href="Hidden%20Operating%20System.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+Yes, it is. For more information, please see the section <a href="Hidden%20Operating%20System.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 Hidden Operating System</a> in the <a href="https://veracrypt.jp/en/Documentation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 documentation</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <br style="text-align:left">
 <strong style="text-align:left">Will I be able to mount my VeraCrypt volume (container) on any computer?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-Yes, <a href="VeraCrypt%20Volume.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+Yes, <a href="VeraCrypt%20Volume.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 VeraCrypt volumes</a> are independent of the operating system. You will be able to mount your VeraCrypt volume on any computer on which you can run VeraCrypt (see also the question '<em style="text-align:left">Can I use VeraCrypt on Windows if I do not have
  administrator privileges?</em>').</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
@@ -233,21 +232,21 @@ Before you unplug or turn off the device, you should always unmount the VeraCryp
 <br style="text-align:left">
 <strong style="text-align:left">What is a hidden operating system?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-See the section <a href="Hidden%20Operating%20System.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+See the section <a href="Hidden%20Operating%20System.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 Hidden Operating System</a> in the <a href="https://veracrypt.jp/en/Documentation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 documentation</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <br style="text-align:left">
 <strong style="text-align:left">What is plausible deniability?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-See the chapter <a href="Plausible%20Deniability.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+See the chapter <a href="Plausible%20Deniability.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 Plausible Deniability</a> in the <a href="https://veracrypt.jp/en/Documentation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 documentation</a>.</div>
 <div id="SystemReinstallUpgrade" style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <br style="text-align:left">
 <strong style="text-align:left">Will I be able to mount my VeraCrypt partition/container after I reinstall or upgrade the operating system?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-Yes, <a href="VeraCrypt%20Volume.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+Yes, <a href="VeraCrypt%20Volume.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 VeraCrypt volumes</a> are independent of the operating system. However, you need to make sure your operating system installer does not format the partition where your VeraCrypt volume resides.<br style="text-align:left">
 <br style="text-align:left">
 Note: If the system partition/drive is encrypted and you want to reinstall or upgrade Windows, you need to decrypt it first (select
@@ -257,19 +256,19 @@ Note: If the system partition/drive is encrypted and you want to reinstall or up
 <br style="text-align:left">
 <strong style="text-align:left">Can I upgrade from an older version of VeraCrypt to the latest version without any problems?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-Generally, yes. However, before upgrading, please read the <a href="Release%20Notes.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+Generally, yes. However, before upgrading, please read the <a href="Release%20Notes.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 release notes</a> for all versions of VeraCrypt that have been released since your version was released. If there are any known issues or incompatibilities related to upgrading from your version to a newer one, they will be listed in the
-<a href="Release%20Notes.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="Release%20Notes.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 release notes</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <br style="text-align:left">
 <strong style="text-align:left">Can I upgrade VeraCrypt if the system partition/drive is encrypted or do I have to decrypt it first?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 Generally, you can upgrade to the latest version without decrypting the system partition/drive (just run the VeraCrypt installer and it will automatically upgrade VeraCrypt on the system). However, before upgrading, please read the
-<a href="Release%20Notes.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="Release%20Notes.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 release notes</a> for all versions of VeraCrypt that have been released since your version was released. If there are any known issues or incompatibilities related to upgrading from your version to a newer one, they will be listed in the
-<a href="Release%20Notes.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
-release notes</a>. Note that this FAQ answer is also valid for users of a <a href="Hidden%20Operating%20System.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="Release%20Notes.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
+release notes</a>. Note that this FAQ answer is also valid for users of a <a href="Hidden%20Operating%20System.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 hidden operating system</a>. Also note that you cannot <em style="text-align:left">
 down</em>grade VeraCrypt if the system partition/drive is encrypted.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
@@ -302,7 +301,7 @@ Right-click the mounted volume in the drive list in the main VeraCrypt window an
 The System Favorites Organizer window should appear now. In this window, enable the option '<em style="text-align:left">Mount system favorite volumes when Windows starts</em>' and click
 <em style="text-align:left">OK</em>. </li></ol>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-For more information, see the chapter <a href="System%20Favorite%20Volumes.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+For more information, see the chapter <a href="System%20Favorite%20Volumes.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 System Favorite Volumes</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <br style="text-align:left">
@@ -315,7 +314,7 @@ Mount the volume (to the drive letter to which you want it to be mounted every t
 </li><li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
 Right-click the mounted volume in the drive list in the main VeraCrypt window and select '<em style="text-align:left">Add to Favorites</em>'.
 </li><li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
-The <a href="Favorite%20Volumes.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+The <a href="Favorite%20Volumes.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 Favorites</a> Organizer window should appear now. In this window, enable the option '<em style="text-align:left">Mount selected volume upon logon</em>' and click
 <em style="text-align:left">OK</em>. </li></ol>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
@@ -331,7 +330,7 @@ In the section '<em style="text-align:left">Actions to perform upon logon to Win
 <em style="text-align:left">OK</em>. </li></ol>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 Note: VeraCrypt will not prompt you for a password if you have enabled caching of the
-<a href="System%20Encryption.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="System%20Encryption.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 pre-boot authentication</a> password (<em style="text-align:left">Settings</em> &gt; '<em style="text-align:left">System Encryption</em>') and the volumes use the same password as the system partition/drive.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <br style="text-align:left">
@@ -344,14 +343,14 @@ Mount the volume (to the drive letter to which you want it to be mounted every t
 </li><li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
 Right-click the mounted volume in the drive list in the main VeraCrypt window and select '<em style="text-align:left">Add to Favorites</em>'.
 </li><li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
-The <a href="Favorite%20Volumes.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+The <a href="Favorite%20Volumes.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 Favorites</a> Organizer window should appear now. In this window, enable the option '<em style="text-align:left">Mount selected volume when its host device gets connected</em>' and click
 <em style="text-align:left">OK</em>. </li></ol>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 Then, when you insert the USB flash drive into the USB port, you will be asked for the volume password (and/or keyfiles) (unless it is cached) and if it is correct, the volume will be mounted.<br style="text-align:left">
 <br style="text-align:left">
 Note: VeraCrypt will not prompt you for a password if you have enabled caching of the
-<a href="System%20Encryption.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="System%20Encryption.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 pre-boot authentication</a> password (<em style="text-align:left">Settings</em> &gt; '<em style="text-align:left">System Encryption</em>') and the volume uses the same password as the system partition/drive.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <br style="text-align:left">
@@ -362,7 +361,7 @@ Yes. Select <em style="text-align:left">Settings</em> &gt; '<em style="text-alig
 <a name="notraces" style="text-align:left; color:#0080c0; text-decoration:none"></a><br style="text-align:left">
 <strong style="text-align:left">I live in a country that violates basic human rights of its people. Is it possible to use VeraCrypt without leaving any 'traces' on unencrypted Windows?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-Yes. This can be achieved by running VeraCrypt in <a href="Portable%20Mode.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+Yes. This can be achieved by running VeraCrypt in <a href="Portable%20Mode.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 portable mode</a> under <a href="http://www.nu2.nu/pebuilder/" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 BartPE</a> or in a similar environment. BartPE stands for &quot;Bart's Preinstalled Environment&quot;, which is essentially the Windows operating system prepared in a way that it can be entirely stored on and booted from a CD/DVD (registry, temporary files, etc., are
  stored in RAM &ndash; hard drive is not used at all and does not even have to be present). The freeware
@@ -380,7 +379,7 @@ Download the VeraCrypt self-extracting package to the RAM disk (which BartPE aut
 <strong style="text-align:left">I2P</strong></a>, <a href="http://www.torproject.org/" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 <strong style="text-align:left">Tor</strong></a>, or a similar anonymizing network.
 </li><li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
-Verify the digital signatures of the downloaded file (see <a href="Digital%20Signatures.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+Verify the digital signatures of the downloaded file (see <a href="Digital%20Signatures.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 this</a> section of the documentation for more information). </li><li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
 Run the downloaded file, and select <em style="text-align:left">Extract</em> (instead of
 <em style="text-align:left">Install</em>) on the second page of the VeraCrypt Setup wizard. Extract the contents to the RAM disk.
@@ -388,9 +387,9 @@ Run the downloaded file, and select <em style="text-align:left">Extract</em> (in
 Run the file <em style="text-align:left">VeraCrypt.exe</em> from the RAM disk. </li></ol>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 Note: You may also want to consider creating a hidden operating system (see the section
-<a href="Hidden%20Operating%20System.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="Hidden%20Operating%20System.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 Hidden Operating System</a> in the <a href="https://veracrypt.jp/en/Documentation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
-documentation</a>). See also the chapter <a href="Plausible%20Deniability.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+documentation</a>). See also the chapter <a href="Plausible%20Deniability.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 Plausible Deniability</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <br style="text-align:left">
@@ -405,14 +404,14 @@ Yes, VeraCrypt supports all keyboard layouts. Because of BIOS requirement, the p
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 Yes. You can write data to the decoy system partition anytime without any risk that the hidden volume will get damaged (because the decoy system is
 <em style="text-align:left">not</em> installed within the same partition as the hidden system). For more information, see the section
-<a href="Hidden%20Operating%20System.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="Hidden%20Operating%20System.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 Hidden Operating System</a> in the <a href="https://veracrypt.jp/en/Documentation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 documentation</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <br style="text-align:left">
 <strong style="text-align:left">Can I use VeraCrypt on Windows if I do not have administrator privileges?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-See the chapter '<a href="Using%20VeraCrypt%20Without%20Administrator%20Privileges.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">Using VeraCrypt Without Administrator Privileges</a>'
+See the chapter '<a href="Using%20VeraCrypt%20Without%20Administrator%20Privileges.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">Using VeraCrypt Without Administrator Privileges</a>'
  in the <a href="https://veracrypt.jp/en/Documentation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 documentation</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
@@ -424,8 +423,8 @@ No.</div>
 <br style="text-align:left">
 <strong style="text-align:left">How does VeraCrypt verify that the correct password was entered?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-See the section <a href="Encryption%20Scheme.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
-Encryption Scheme</a> (chapter <a href="Technical%20Details.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+See the section <a href="Encryption%20Scheme.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
+Encryption Scheme</a> (chapter <a href="Technical%20Details.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 Technical Details</a>) in the <a href="https://veracrypt.jp/en/Documentation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 documentation</a>.</div>
 <div id="encrypt-in-place" style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
@@ -447,7 +446,7 @@ If you want to encrypt a non-system partition in place, you can do so provided t
 <br style="text-align:left">
 <strong style="text-align:left">Can I run VeraCrypt if I don't install it?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-Yes, see the chapter <a href="Portable%20Mode.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+Yes, see the chapter <a href="Portable%20Mode.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 Portable Mode</a> in the <a href="https://veracrypt.jp/en/Documentation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 VeraCrypt User Guide</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
@@ -471,7 +470,7 @@ The only thing that TPM is almost guaranteed to provide is a false sense of secu
  features is usually a way to create so-called bloatware). <br style="text-align:left">
 <br style="text-align:left">
 For more information, please see the sections <a title="Physical%20Security&quot;" style="text-align:left; color:#0080c0; text-decoration:none">
-Physical Security</a> and <a href="Malware.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
+Physical Security</a> and <a href="Malware.html" style="text-align:left; color:#0080c0; text-decoration:none">
 Malware</a> in the <a href="https://veracrypt.jp/en/Documentation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 documentation</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
@@ -483,15 +482,15 @@ No. VeraCrypt automatically unmounts all mounted VeraCrypt volumes on system shu
 <br style="text-align:left">
 <strong style="text-align:left">Which type of VeraCrypt volume is better &ndash; partition or file container?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-<a href="VeraCrypt%20Volume.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">File containers</a> are normal files so you can work with them as with any normal files (file containers
- can be, for example, moved, renamed, and deleted the same way as normal files). <a href="VeraCrypt%20Volume.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="VeraCrypt%20Volume.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">File containers</a> are normal files so you can work with them as with any normal files (file containers
+ can be, for example, moved, renamed, and deleted the same way as normal files). <a href="VeraCrypt%20Volume.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 Partitions/drives</a> may be better as regards performance. Note that reading and writing to/from a file container may take significantly longer when the container is heavily fragmented. To solve this problem, defragment the file system in which the container
  is stored (when the VeraCrypt volume is unmounted).</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <br style="text-align:left">
 <strong style="text-align:left">What's the recommended way to back up a VeraCrypt volume?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-See the chapter <a href="How%20to%20Back%20Up%20Securely.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
+See the chapter <a href="How%20to%20Back%20Up%20Securely.html" style="text-align:left; color:#0080c0; text-decoration:none">
 How to Back Up Securely</a> in the <a href="https://veracrypt.jp/en/Documentation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 documentation</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
@@ -515,10 +514,10 @@ Yes. However, if you need to mount a VeraCrypt volume that is stored on a read-o
 <br style="text-align:left">
 <strong style="text-align:left">Is it possible to change the password for a hidden volume?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-Yes, the password change dialog works both for standard and <a href="Hidden%20Volume.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+Yes, the password change dialog works both for standard and <a href="Hidden%20Volume.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 hidden volumes</a>. Just type the password for the hidden volume in the 'Current Password' field of the 'Volume Password Change' dialog.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px; font-size:10px; line-height:12px">
-Remark: VeraCrypt first attempts to decrypt the standard <a href="VeraCrypt%20Volume%20Format%20Specification.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+Remark: VeraCrypt first attempts to decrypt the standard <a href="VeraCrypt%20Volume%20Format%20Specification.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 volume header</a> and if it fails, it attempts to decrypt the area within the volume where the hidden volume header may be stored (if there is a hidden volume within). In case it is successful, the password change applies to the hidden volume. (Both attempts
  use the password typed in the 'Current Password' field.)</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
@@ -537,7 +536,7 @@ Yes, VeraCrypt volumes behave like real physical disk devices, so it is possible
 <strong style="text-align:left">Does VeraCrypt support 64-bit versions of Windows?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 Yes, it does. <span style="text-align:left; font-size:10px; line-height:12px">Note: 64-bit versions of Windows load only drivers that are digitally signed with a digital certificate issued by a certification authority approved for issuing kernel-mode code signing
- certificates. VeraCrypt complies with this requirement (the VeraCrypt driver is <a href="Digital%20Signatures.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
+ certificates. VeraCrypt complies with this requirement (the VeraCrypt driver is <a href="Digital%20Signatures.html" style="text-align:left; color:#0080c0; text-decoration:none">
 digitally signed</a> with the digital certificate of IDRIX, which was issued by the certification authority Thawte).</span></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <br style="text-align:left">
@@ -554,7 +553,7 @@ veracrypt-uninstall.sh</strong>. On Ubuntu, you can use &quot;<strong>sudo verac
 <br style="text-align:left">
 <strong style="text-align:left">Is there a list of all operating systems that VeraCrypt supports?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-Yes, see the chapter <a href="Supported%20Operating%20Systems.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+Yes, see the chapter <a href="Supported%20Operating%20Systems.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 Supported Operating Systems</a> in the <a href="https://veracrypt.jp/en/Documentation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 VeraCrypt User Guide</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
@@ -567,7 +566,7 @@ Yes.</div>
 <strong style="text-align:left">What will happen when a part of a VeraCrypt volume becomes corrupted?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 In encrypted data, one corrupted bit usually corrupts the whole ciphertext block in which it occurred. The ciphertext block size used by VeraCrypt is 16 bytes (i.e., 128 bits). The
-<a href="Modes%20of%20Operation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="Modes%20of%20Operation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 mode of operation</a> used by VeraCrypt ensures that if data corruption occurs within a block, the remaining blocks are not affected. See also the question '<em style="text-align:left">What do I do when the encrypted filesystem on my VeraCrypt volume is corrupted?</em></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <br style="text-align:left">
@@ -579,57 +578,57 @@ File system within a VeraCrypt volume may become corrupted in the same way as an
 <br style="text-align:left">
 <strong style="text-align:left">We use VeraCrypt in a corporate/enterprise environment. Is there a way for an administrator to reset a volume password or pre-boot authentication password when a user forgets it (or loses a keyfile)?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-Yes. Note that there is no &quot;backdoor&quot; implemented in VeraCrypt. However, there is a way to &quot;reset&quot; volume passwords/<a href="Keyfiles.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">keyfiles</a>
- and <a href="System%20Encryption.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+Yes. Note that there is no &quot;backdoor&quot; implemented in VeraCrypt. However, there is a way to &quot;reset&quot; volume passwords/<a href="Keyfiles.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">keyfiles</a>
+ and <a href="System%20Encryption.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 pre-boot authentication</a> passwords. After you create a volume, back up its header to a file (select
 <em style="text-align:left">Tools</em> -&gt; <em style="text-align:left">Backup Volume Header</em>) before you allow a
-<a href="Using%20VeraCrypt%20Without%20Administrator%20Privileges.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
-non-admin user</a> to use the volume. Note that the <a href="VeraCrypt%20Volume%20Format%20Specification.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
-volume header</a> (which is encrypted with a <a href="Header%20Key%20Derivation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
-header key</a> derived from a password/keyfile) contains the <a href="Encryption%20Scheme.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="Using%20VeraCrypt%20Without%20Administrator%20Privileges.html" style="text-align:left; color:#0080c0; text-decoration:none">
+non-admin user</a> to use the volume. Note that the <a href="VeraCrypt%20Volume%20Format%20Specification.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
+volume header</a> (which is encrypted with a <a href="Header%20Key%20Derivation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
+header key</a> derived from a password/keyfile) contains the <a href="Encryption%20Scheme.html" style="text-align:left; color:#0080c0; text-decoration:none">
 master key</a> with which the volume is encrypted. Then ask the user to choose a password, and set it for him/her (<em style="text-align:left">Volumes</em> -&gt;
 <em style="text-align:left">Change Volume Password</em>); or generate a user keyfile for him/her. Then you can allow the user to use the volume and to change the password/keyfiles without your assistance/permission. In case he/she forgets his/her password or
  loses his/her keyfile, you can &quot;reset&quot; the volume password/keyfiles to your original admin password/keyfiles by restoring the volume header from the backup file (<em style="text-align:left">Tools</em> -&gt;
 <em style="text-align:left">Restore Volume Header</em>). <br style="text-align:left">
 <br style="text-align:left">
-Similarly, you can reset a <a href="System%20Encryption.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
-pre-boot authentication</a> password<a href="System%20Encryption.html" style="text-align:left; color:#0080c0; text-decoration:none.html">.
-</a>To create a backup of the master key data (that will be stored on a <a href="VeraCrypt%20Rescue%20Disk.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
-VeraCrypt Rescue Disk</a> and encrypted with your administrator password), select '<em style="text-align:left">System</em>' &gt; '<a href="VeraCrypt%20Rescue%20Disk.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none"><em style="text-align:left.html">Create
- Rescue Disk</em></a>'. To set a user <a href="System%20Encryption.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+Similarly, you can reset a <a href="System%20Encryption.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
+pre-boot authentication</a> password<a href="System%20Encryption.html" style="text-align:left; color:#0080c0; text-decoration:none">.
+</a>To create a backup of the master key data (that will be stored on a <a href="VeraCrypt%20Rescue%20Disk.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
+VeraCrypt Rescue Disk</a> and encrypted with your administrator password), select '<em style="text-align:left">System</em>' &gt; '<a href="VeraCrypt%20Rescue%20Disk.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none"><em style="text-align:left">Create
+ Rescue Disk</em></a>'. To set a user <a href="System%20Encryption.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 pre-boot authentication</a> password, select '<em style="text-align:left">System</em>' &gt; '<em style="text-align:left">Change Password</em>'. To restore your administrator password, boot the VeraCrypt Rescue Disk, select '<em style="text-align:left">Repair
  Options</em>' &gt; '<em style="text-align:left">Restore key data</em>' and enter your administrator password.
 <br style="text-align:left">
 <span style="text-align:left; font-size:10px; line-height:12px">Note: It is not required to burn each
-<a href="VeraCrypt%20Rescue%20Disk.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="VeraCrypt%20Rescue%20Disk.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 VeraCrypt Rescue Disk</a> ISO image to a CD/DVD. You can maintain a central repository of ISO images for all workstations (rather than a repository of CDs/DVDs). For more information see the section
-<a href="Command%20Line%20Usage.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="Command%20Line%20Usage%20for%20Windows.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 Command Line Usage</a> (option <em style="text-align:left">/noisocheck</em>).</span></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <br style="text-align:left">
 <strong style="text-align:left">Can our commercial company use VeraCrypt free of charge?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-Provided that you comply with the terms and conditions of the <a href="VeraCrypt%20License.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+Provided that you comply with the terms and conditions of the <a href="VeraCrypt%20License.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 VeraCrypt License</a>, you can install and run VeraCrypt free of charge on an arbitrary number of your computers.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <br style="text-align:left">
 <strong style="text-align:left">We share a volume over a network. Is there a way to have the network share automatically restored when the system is restarted?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-Please see the chapter '<a href="Sharing%20over%20Network.html" style="text-align:left; color:#0080c0; text-decoration:none.html">Sharing over Network</a>' in the
+Please see the chapter '<a href="Sharing%20over%20Network.html" style="text-align:left; color:#0080c0; text-decoration:none">Sharing over Network</a>' in the
 <a href="https://veracrypt.jp/en/Documentation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 VeraCrypt User Guide</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <br style="text-align:left">
 <strong style="text-align:left">It is possible to access a single VeraCrypt volume simultaneously from multiple operating systems (for example, a volume shared over a network)?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-Please see the chapter '<a href="Sharing%20over%20Network.html" style="text-align:left; color:#0080c0; text-decoration:none.html">Sharing over Network</a>' in the
+Please see the chapter '<a href="Sharing%20over%20Network.html" style="text-align:left; color:#0080c0; text-decoration:none">Sharing over Network</a>' in the
 <a href="https://veracrypt.jp/en/Documentation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 VeraCrypt User Guide</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <br style="text-align:left">
 <strong style="text-align:left">Can a user access his or her VeraCrypt volume via a network?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-Please see the chapter '<a href="Sharing%20over%20Network.html" style="text-align:left; color:#0080c0; text-decoration:none.html">Sharing over Network</a>' in the
+Please see the chapter '<a href="Sharing%20over%20Network.html" style="text-align:left; color:#0080c0; text-decoration:none">Sharing over Network</a>' in the
 <a href="https://veracrypt.jp/en/Documentation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 VeraCrypt User Guide</a>.</div>
 <div id="non_system_drive_letter" style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
@@ -662,14 +661,14 @@ Yes, but you will need to remove the drive letter assigned to the device. For in
 How do I remove or undo encryption if I do not need it anymore? How do I permanently decrypt a volume?
 </strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-Please see the section '<a href="Removing%20Encryption.html" style="text-align:left; color:#0080c0; text-decoration:none.html">How to Remove Encryption</a>' in the
+Please see the section '<a href="Removing%20Encryption.html" style="text-align:left; color:#0080c0; text-decoration:none">How to Remove Encryption</a>' in the
 <a href="https://veracrypt.jp/en/Documentation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 VeraCrypt User Guide</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <br style="text-align:left">
 <strong style="text-align:left">What will change when I enable the option '<em style="text-align:left">Mount volumes as removable media</em>'?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-Please see the section '<a href="Removable%20Medium%20Volume.html" style="text-align:left; color:#0080c0; text-decoration:none.html">Volume Mounted as Removable Medium</a>' in the
+Please see the section '<a href="Removable%20Medium%20Volume.html" style="text-align:left; color:#0080c0; text-decoration:none">Volume Mounted as Removable Medium</a>' in the
 <a href="https://veracrypt.jp/en/Documentation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 VeraCrypt User Guide</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
@@ -695,8 +694,8 @@ If you believe that an adversary will be able to decrypt the volume (for example
 <br style="text-align:left">
 <strong style="text-align:left">How does VeraCrypt know which encryption algorithm my VeraCrypt volume has been encrypted with?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-Please see the section <a href="Encryption%20Scheme.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
-Encryption Scheme</a> (chapter <a href="Technical%20Details.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none.html">
+Please see the section <a href="Encryption%20Scheme.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
+Encryption Scheme</a> (chapter <a href="Technical%20Details.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 Technical Details</a>) in the <a href="https://veracrypt.jp/en/Documentation.html" target="_blank" style="text-align:left; color:#0080c0; text-decoration:none">
 documentation</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
@@ -766,4 +765,4 @@ For more details on the Windows Sandbox feature and its associated virtual hard
 <strong style="text-align:left">I haven't found any answer to my question in the FAQ &ndash; what should I do?</strong></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 Please search the VeraCrypt documentation and website.</div>
-</div><div class="ClearBoth"></div></body></html>
+</div><div class="ClearBoth"></div></div></body></html>

doc/html/en/Favorite Volumes.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
@@ -109,7 +108,7 @@ Note that a favorite volume can also be a <strong>partition that is within the k
 Favorites </em>&gt; <em>Organize Favorite Volumes</em>, select the volume, click <em>
 Remove</em>, and click OK.</p>
 <p>&nbsp;</p>
-<p><a href="System%20Favorite%20Volumes.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold.html">Next Section &gt;&gt;</a></p>
+<p><a href="System%20Favorite%20Volumes.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold">Next Section &gt;&gt;</a></p>
 </div>
 </div>
 </body></html>

doc/html/en/Hardware Acceleration.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
@@ -35,7 +34,7 @@
 <div class="wikidoc">
 <h1>Hardware Acceleration</h1>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-Some processors (CPUs) support hardware-accelerated <a href="AES.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
+Some processors (CPUs) support hardware-accelerated <a href="AES.html" style="text-align:left; color:#0080c0; text-decoration:none">
 AES</a> encryption,* which is typically 4-8 times faster than encryption performed by the purely software implementation on the same processors.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 By default, VeraCrypt uses hardware-accelerated AES on computers that have a processor where the Intel AES-NI instructions are available. Specifically, VeraCrypt uses the AES-NI instructions that perform so-called AES rounds (i.e. the main portions of the AES

doc/html/en/Hash Algorithms.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
@@ -35,24 +34,25 @@
 <div class="wikidoc">
 <h1>Hash Algorithms</h1>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-In the Volume Creation Wizard, in the password change dialog window, and in the Keyfile Generator dialog window, you can select a hash algorithm. A user-selected hash algorithm is used by the VeraCrypt Random Number Generator as a pseudorandom &quot;mixing&quot; function,
- and by the header key derivation function (HMAC based on a hash function, as specified in PKCS #5 v2.0) as a pseudorandom function. When creating a new volume, the Random Number Generator generates the master key, secondary key (XTS mode), and salt. For more
- information, please see the section <a href="Random%20Number%20Generator.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
-Random Number Generator</a> and section <a href="Header%20Key%20Derivation.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
-Header Key Derivation, Salt, and Iteration Count</a>.</div>
+In the Volume Creation Wizard, in the password change dialog window, and in the Keyfile Generator dialog window, you can select a hash algorithm when using PBKDF2-HMAC as the key derivation function. When Argon2id is selected as the key derivation function, no hash algorithm selection is available as Argon2id uses its own internal BLAKE2b hash function.
+</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-VeraCrypt currently supports the following hash algorithms:</div>
+For PBKDF2-HMAC, the user-selected hash algorithm is used by the VeraCrypt Random Number Generator as a pseudorandom &quot;mixing&quot; function, and by the header key derivation function (HMAC based on a hash function, as specified in PKCS #5 v2.0) as a pseudorandom function. When creating a new volume, the Random Number Generator generates the master key, secondary key (XTS mode), and salt. For more
+ information, please see the section <a href="Random%20Number%20Generator.html" style="text-align:left; color:#0080c0; text-decoration:none">
+Random Number Generator</a> and section <a href="Header%20Key%20Derivation.html" style="text-align:left; color:#0080c0; text-decoration:none">
+Header Key Derivation, Salt, and Iteration Count</a>.</div>
+VeraCrypt currently supports the following hash algorithms for PBKDF2-HMAC:</div>
 <ul style="text-align:left; margin-top:18px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
-<a href="BLAKE2s-256.html"><strong style="text-align:left.html">BLAKE2s-256</strong></a>
+<a href="BLAKE2s-256.html"><strong style="text-align:left">BLAKE2s-256</strong></a>
 </li><li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
-<a href="SHA-256.html"><strong style="text-align:left.html">SHA-256</strong></a>
+<a href="SHA-256.html"><strong style="text-align:left">SHA-256</strong></a>
 </li><li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
-<a href="SHA-512.html"><strong style="text-align:left.html">SHA-512</strong></a>
+<a href="SHA-512.html"><strong style="text-align:left">SHA-512</strong></a>
 </li><li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
-<a href="Whirlpool.html"><strong style="text-align:left.html">Whirlpool</strong></a>
+<a href="Whirlpool.html"><strong style="text-align:left">Whirlpool</strong></a>
 </li><li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
 <strong style="text-align:left"><a href="Streebog.html">Streebog</a></strong>
 </li></ul>
-<p><a href="BLAKE2s-256.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold.html">Next Section &gt;&gt;</a></p>
+<p><a href="BLAKE2s-256.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold">Next Section &gt;&gt;</a></p>
 </div><div class="ClearBoth"></div></body></html>

doc/html/en/Header Key Derivation.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
@@ -38,29 +37,38 @@
 <h1>Header Key Derivation, Salt, and Iteration Count</h1>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 Header key is used to encrypt and decrypt the encrypted area of the VeraCrypt volume header (for
-<a href="System%20Encryption.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="System%20Encryption.html" style="text-align:left; color:#0080c0; text-decoration:none">
 system encryption</a>, of the keydata area), which contains the master key and other data (see the sections
-<a href="Encryption%20Scheme.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
-Encryption Scheme</a> and <a href="VeraCrypt%20Volume%20Format%20Specification.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="Encryption%20Scheme.html" style="text-align:left; color:#0080c0; text-decoration:none">
+Encryption Scheme</a> and <a href="VeraCrypt%20Volume%20Format%20Specification.html" style="text-align:left; color:#0080c0; text-decoration:none">
 VeraCrypt Volume Format Specification</a>). In volumes created by VeraCrypt (and for
-<a href="System%20Encryption.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
-system encryption</a>), the area is encrypted in XTS mode (see the section <a href="Modes%20of%20Operation.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
-Modes of Operation</a>). The method that VeraCrypt uses to generate the header key and the secondary header key (XTS mode) is PBKDF2, specified in PKCS #5 v2.0; see
-<a href="References.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
-[7]</a>.</div>
+<a href="System%20Encryption.html" style="text-align:left; color:#0080c0; text-decoration:none">
+system encryption</a>), the area is encrypted in XTS mode (see the section <a href="Modes%20of%20Operation.html" style="text-align:left; color:#0080c0; text-decoration:none">
+Modes of Operation</a>). VeraCrypt supports two key derivation functions for generating header keys: PBKDF2 (specified in PKCS #5 v2.0) and Argon2id.</div>
+
+<h3>PBKDF2-HMAC Key Derivation</h3>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-512-bit salt is used, which means there are 2<sup style="text-align:left; font-size:85%">512</sup> keys for each password. This significantly decreases vulnerability to 'off-line' dictionary/'rainbow table' attacks (pre-computing all the keys for a dictionary
- of passwords is very difficult when a salt is used) [7]. The salt consists of random values generated by the
-<a href="Random%20Number%20Generator.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
-VeraCrypt random number generator</a> during the volume creation process. The header key derivation function is based on HMAC-SHA-512, HMAC-SHA-256, HMAC-BLAKE2S-256, HMAC-Whirlpool or HMAC-Streebog (see [8, 9, 20, 22]) &ndash; the user selects which. The length of the derived
+The PBKDF2 method uses HMAC-based pseudorandom functions with the following hash algorithms available: SHA-512, SHA-256, BLAKE2s-256, Whirlpool, or Streebog (see [8, 9, 20, 22]) – the user selects which. The length of the derived
  key does not depend on the size of the output of the underlying hash function. For example, a header key for the AES-256 cipher is always 256 bits long even if HMAC-SHA-512 is used (in XTS mode, an additional 256-bit secondary header key is used; hence,
  two 256-bit keys are used for AES-256 in total). For more information, refer to [7]. A large number of iterations of the key derivation function have to be performed to derive a header key, which increases the time necessary to perform an exhaustive search
  for passwords (i.e., brute force attack)&nbsp;[7].</div>
+
+<h3>Argon2id Key Derivation</h3>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-<p>Prior to version 1.12, VeraCrypt always used a fixed number of iterations That depended only on the volume type and the derivation algorithm used.
+Argon2id is a memory-hard key derivation function that provides resistance against both time-memory trade-off attacks and side-channel attacks. Unlike PBKDF2-HMAC, Argon2id does not use a separate hash algorithm selection – it uses its own internal hash function (BLAKE2b). Argon2id requires three parameters: memory cost (amount of memory used), time cost (number of iterations), and parallelism (number of threads). VeraCrypt sets the parallelism parameter to 1 for all cases.</div>
+
+<div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+512-bit salt is used for both key derivation functions, which means there are 2<sup style="text-align:left; font-size:85%">512</sup> keys for each password. This significantly decreases vulnerability to 'off-line' dictionary/'rainbow table' attacks (pre-computing all the keys for a dictionary
+ of passwords is very difficult when a salt is used) [7]. The salt consists of random values generated by the
+<a href="Random%20Number%20Generator.html" style="text-align:left; color:#0080c0; text-decoration:none">
+VeraCrypt random number generator</a> during the volume creation process.</div>
+
+<div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+<p>Prior to version 1.12, VeraCrypt always used PBKDF2-HMAC with a fixed number of iterations that depended only on the volume type and the hash algorithm used.
 Starting from version 1.12, the <a href="Personal%20Iterations%20Multiplier%20%28PIM%29.html">
-PIM </a>field (<a href="Personal%20Iterations%20Multiplier%20%28PIM%29.html">Personal Iterations Multiplier</a>) enables users to have more control over the number of iterations used by the key derivation function.</p>
-<p>
+PIM </a>field (<a href="Personal%20Iterations%20Multiplier%20%28PIM%29.html">Personal Iterations Multiplier</a>) enables users to have more control over the computational parameters used by the key derivation function.</p>
+
+<h4>PBKDF2-HMAC Parameters</h4>
 <p>When a <a href="Personal%20Iterations%20Multiplier%20%28PIM%29.html">
 PIM </a>value is not specified or if it is equal to zero, VeraCrypt uses the default values expressed below:<br/>
 <ul>
@@ -70,12 +78,16 @@ PIM </a>value is not specified or if it is equal to zero, VeraCrypt uses the def
 </li></ul>
 </p>
 <p>When a <a href="Personal%20Iterations%20Multiplier%20%28PIM%29.html">
-PIM </a>value is given by the user, the number of iterations of the key derivation function is calculated as follows:</p>
+PIM </a>value is given by the user, the number of iterations of the PBKDF2 key derivation function is calculated as follows:</p>
 <ul>
 <li>For system encryption that doesn't use SHA-512 or Whirlpool: Iterations = <strong>PIM x 2048</strong>
 </li><li>For system encryption that uses SHA-512 or Whirlpool: Iterations = <strong>15000 &#43; (PIM x 1000)</strong>
 </li><li>For non-system encryption and file containers: Iterations = <strong>15000 &#43; (PIM x 1000)</strong>
 </li></ul>
+
+<h4>Argon2id Parameters</h4>
+<p>When Argon2id is selected as the key derivation function, the PIM value controls both memory and time costs as described in the <a href="Personal%20Iterations%20Multiplier%20%28PIM%29.html">PIM section</a>. If no PIM is specified, default parameters equivalent to PIM = 12 are used (416 MiB memory, 6 iterations).</p>
+
 </div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 Header keys used by ciphers in a cascade are mutually independent, even though they are derived from a single password (to which keyfiles may have been applied). For example, for the AES-Twofish-Serpent cascade, the header key derivation function is instructed
@@ -85,5 +97,5 @@ Header keys used by ciphers in a cascade are mutually independent, even though t
  for XTS mode, the first secondary key is used by Serpent, the second secondary key is used by Twofish, and the third secondary key by AES). Hence, even when an adversary has one of the keys, he cannot use it to derive the other keys, as there is no feasible
  method to determine the password from which the key was derived (except for brute force attack mounted on a weak password).</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-<a href="Random%20Number%20Generator.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold.html">Next Section &gt;&gt;</a></div>
+<a href="Random%20Number%20Generator.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold">Next Section &gt;&gt;</a></div>
 </div><div class="ClearBoth"></div></body></html>

doc/html/en/Hibernation File.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/Hidden Operating System.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
@@ -39,11 +38,11 @@
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 It may happen that you are forced by somebody to decrypt the operating system. There are many situations where you cannot refuse to do so (for example, due to extortion). VeraCrypt allows you to create a hidden operating system whose existence should be impossible
  to prove (provided that certain guidelines are followed). Thus, you will not have to decrypt or reveal the password for the hidden operating system. For more information, see the section
-<a href="VeraCrypt%20Hidden%20Operating%20System.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
-Hidden Operating System</a> in the chapter <a href="Plausible%20Deniability.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="VeraCrypt%20Hidden%20Operating%20System.html" style="text-align:left; color:#0080c0; text-decoration:none">
+Hidden Operating System</a> in the chapter <a href="Plausible%20Deniability.html" style="text-align:left; color:#0080c0; text-decoration:none">
 Plausible Deniability</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 &nbsp;</div>
-<p><a href="Supported%20Systems%20for%20System%20Encryption.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold.html">Next Section &gt;&gt;</a></p>
+<p><a href="Supported%20Systems%20for%20System%20Encryption.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold">Next Section &gt;&gt;</a></p>
 </div>
 </body></html>

doc/html/en/Hidden Volume.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
@@ -61,7 +60,7 @@ not</em> mounted). Then click <em style="text-align:left">Mount</em>, and enter
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 VeraCrypt first attempts to decrypt the standard volume header using the entered password. If it fails, it loads the area of the volume where a hidden volume header can be stored (i.e. bytes 65536&ndash;131071, which contain solely random data when there is
  no hidden volume within the volume) to RAM and attempts to decrypt it using the entered password. Note that hidden volume headers cannot be identified, as they appear to consist entirely of random data. If the header is successfully decrypted (for information
- on how VeraCrypt determines that it was successfully decrypted, see the section <a href="Encryption%20Scheme.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
+ on how VeraCrypt determines that it was successfully decrypted, see the section <a href="Encryption%20Scheme.html" style="text-align:left; color:#0080c0; text-decoration:none">
 Encryption Scheme</a>), the information about the size of the hidden volume is retrieved from the decrypted header (which is still stored in RAM), and the hidden volume is mounted (its size also determines its offset).</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 A hidden volume can be created within any type of VeraCrypt volume, i.e., within a file-hosted volume or partition/device-hosted volume (requires administrator privileges). To create a hidden VeraCrypt volume, click on
@@ -71,27 +70,27 @@ A hidden volume can be created within any type of VeraCrypt volume, i.e., within
 When creating a hidden volume, it may be very difficult or even impossible for an inexperienced user to set the size of the hidden volume such that the hidden volume does not overwrite data on the outer volume. Therefore, the Volume Creation Wizard automatically
  scans the cluster bitmap of the outer volume (before the hidden volume is created within it) and determines the maximum possible size of the hidden volume.***</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-If there are any problems when creating a hidden volume, refer to the chapter <a href="Troubleshooting.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
+If there are any problems when creating a hidden volume, refer to the chapter <a href="Troubleshooting.html" style="text-align:left; color:#0080c0; text-decoration:none">
 Troubleshooting</a> for possible solutions.<br style="text-align:left">
 <br style="text-align:left">
 <br style="text-align:left">
 Note that it is also possible to create and boot an operating system residing in a hidden volume (see the section
-<a href="Hidden%20Operating%20System.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="Hidden%20Operating%20System.html" style="text-align:left; color:#0080c0; text-decoration:none">
 Hidden Operating System</a> in the chapter <a href="Plausible%20Deniability.html">
 Plausible Deniability</a>).</div>
 <hr align="left" size="1" width="189" style="text-align:left; height:0px; border-width:0px 1px 1px; border-style:solid; border-color:#000000">
 <p><span style="text-align:left; font-size:10px; line-height:12px">* Provided that all the instructions in the VeraCrypt Volume Creation Wizard have been followed and provided that the requirements and precautions listed in the subsection
-<a href="Security%20Requirements%20for%20Hidden%20Volumes.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="Security%20Requirements%20for%20Hidden%20Volumes.html" style="text-align:left; color:#0080c0; text-decoration:none">
 Security Requirements and Precautions Pertaining to Hidden Volumes</a> are followed<em style="text-align:left">.</em></span><br style="text-align:left">
 <span style="text-align:left; font-size:10px; line-height:12px">** Provided that the options
 <em style="text-align:left">Quick Format</em> and <em style="text-align:left">Dynamic</em> are disabled and provided that the volume does not contain a filesystem that has been encrypted in place (VeraCrypt does not allow the user to create a hidden volume
  within such a volume). For information on the method used to fill free volume space with random data, see chapter
-<a href="Technical%20Details.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
-Technical Details</a>, section <a href="VeraCrypt%20Volume%20Format%20Specification.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="Technical%20Details.html" style="text-align:left; color:#0080c0; text-decoration:none">
+Technical Details</a>, section <a href="VeraCrypt%20Volume%20Format%20Specification.html" style="text-align:left; color:#0080c0; text-decoration:none">
 VeraCrypt Volume Format Specification</a><em style="text-align:left">.</em></span><br style="text-align:left">
 <span style="text-align:left; font-size:10px; line-height:12px">*** The wizard scans the cluster bitmap to determine the size of the uninterrupted area of free space (if there is any) whose end is aligned with the end of the outer volume. This area accommodates
  the hidden volume and therefore the size of this area limits the maximum possible size of the hidden volume. On Linux and Mac OS X, the wizard actually does not scan the cluster bitmap, but the driver detects any data written to the outer volume and uses their
  position as previously described.</span></p>
 <p>&nbsp;</p>
-<p><a href="Protection%20of%20Hidden%20Volumes.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold.html">Next Section &gt;&gt;</a></p>
+<p><a href="Protection%20of%20Hidden%20Volumes.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold">Next Section &gt;&gt;</a></p>
 </div><div class="ClearBoth"></div></body></html>

doc/html/en/Hot Keys.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/How to Back Up Securely.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
@@ -63,7 +62,7 @@ backup</em> volume. </li></ol>
 </li><li>That one of the volumes is a backup of the other. </li></ul>
 <h3>System Partitions</h3>
 <p>Note: In addition to backing up files, we recommend that you also back up your VeraCrypt Rescue Disk (select
-<em>System</em> &gt; <em>Create Rescue Disk</em>). For more information, see the section Vera<em>Crypt Rescue Disk</em>.</p>
+<em>System</em> &gt; <em>Create Rescue Disk</em>). For more information, see the section <em>VeraCrypt Rescue Disk</em>.</p>
 <p>To back up an encrypted system partition securely and safely, it is recommended to follow these steps:</p>
 <ol>
 <li>If you have multiple operating systems installed on your computer, boot the one that does not require pre-boot authentication.<br>

doc/html/en/Incompatibilities.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
@@ -39,12 +38,12 @@ Activation of Adobe Photoshop&reg; and Other Products Using FLEXnet Publisher&re
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <em style="text-align:left">Note: The issue described below does <strong style="text-align:left">
 not</strong> affect you if you use a non-cascade encryption algorithm (i.e., AES, Serpent, or Twofish).* The issue also does
-<strong style="text-align:left">not</strong> affect you if you do not use <a href="System%20Encryption.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<strong style="text-align:left">not</strong> affect you if you do not use <a href="System%20Encryption.html" style="text-align:left; color:#0080c0; text-decoration:none">
 system encryption</a> (pre-boot authentication).</em></div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 Acresso FLEXnet Publisher activation software, formerly Macrovision SafeCast, (used for activation of third-party software, such as Adobe Photoshop) writes data to the first drive track. If this happens when your system partition/drive is encrypted by VeraCrypt,
  a portion of the VeraCrypt Boot Loader will be damaged and you will not be able to start Windows. In that case, please use your
-<a href="VeraCrypt%20Rescue%20Disk.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
+<a href="VeraCrypt%20Rescue%20Disk.html" style="text-align:left; color:#0080c0; text-decoration:none">
 VeraCrypt Rescue Disk</a> to regain access to your system. There are two ways to do so:</div>
 <ol style="text-align:left; margin-top:18px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px">
@@ -56,7 +55,7 @@ If you do not want to boot your system from the VeraCrypt Rescue Disk CD/DVD eve
 Restore VeraCrypt Boot Loader</em>. However, note that this will deactivate the third-party software.
 </li></ol>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
-For information on how to use your VeraCrypt Rescue Disk, please see the chapter <a href="VeraCrypt%20Rescue%20Disk.html" style="text-align:left; color:#0080c0; text-decoration:none.html">
+For information on how to use your VeraCrypt Rescue Disk, please see the chapter <a href="VeraCrypt%20Rescue%20Disk.html" style="text-align:left; color:#0080c0; text-decoration:none">
 VeraCrypt Rescue Disk</a>.</div>
 <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
 <strong style="text-align:left">Possible permanent solution</strong>: decrypt the system partition/drive, and then re-encrypt it using a non-cascade encryption algorithm (i.e., AES, Serpent, or Twofish).*</div>
@@ -76,6 +75,6 @@ More information can be found at <a href="https://sourceforge.net/p/veracrypt/ti
 <br style="text-align:left">
 <br style="text-align:left">
 <br style="text-align:left">
-&nbsp;&nbsp;See also: <a href="Issues%20and%20Limitations.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold.html">
-Known Issues &amp; Limitations</a>,&nbsp;&nbsp;<a href="Troubleshooting.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold.html">Troubleshooting</a></p>
+&nbsp;&nbsp;See also: <a href="Issues%20and%20Limitations.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold">
+Known Issues &amp; Limitations</a>,&nbsp;&nbsp;<a href="Troubleshooting.html" style="text-align:left; color:#0080c0; text-decoration:none; font-weight:bold">Troubleshooting</a></p>
 </div><div class="ClearBoth"></div></body></html>

doc/html/en/Introduction.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/Issues and Limitations.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/Journaling File Systems.html

@@ -1,6 +1,5 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 <title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>

doc/html/en/Key Derivation Algorithms.html

@@ -0,0 +1,51 @@
+<!DOCTYPE html>
+
+<html lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title>
+<meta name="description" content="VeraCrypt is free open-source disk encryption software for Windows, Mac OS X and Linux. In case an attacker forces you to reveal the password, VeraCrypt provides plausible deniability. In contrast to file encryption, data encryption performed by VeraCrypt is real-time (on-the-fly), automatic, transparent, needs very little memory, and does not involve temporary unencrypted files."/>
+<meta name="keywords" content="encryption, security"/>
+<link href="styles.css" rel="stylesheet" type="text/css" />
+</head>
+<body>
+<div>
+<a href="Documentation.html"><img src="VeraCrypt128x128.png" alt="VeraCrypt"/></a>
+</div>
+<div id="menu">
+    <ul>
+      <li><a href="Home.html">Home</a></li>
+      <li><a href="Code.html">Source Code</a></li>
+      <li><a href="Downloads.html">Downloads</a></li>
+      <li><a class="active" href="Documentation.html">Documentation</a></li>
+      <li><a href="Donation.html">Donate</a></li>
+      <li><a href="https://sourceforge.net/p/veracrypt/discussion/" target="_blank">Forums</a></li>
+    </ul>
+</div>
+<div>
+<p>
+<a href="Documentation.html">Documentation</a>
+<img src="arrow_right.gif" alt=">>" style="margin-top: 5px">
+<a href="Key%20Derivation%20Algorithms.html">Key Derivation Algorithms</a>
+</p></div>
+<div class="wikidoc">
+<h1>Key Derivation Algorithms</h1>
+
+<div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+A key derivation function (KDF) transforms your password (and optional keyfiles) into cryptographic keys used to decrypt a VeraCrypt volume header. KDFs slow down brute-force attacks and protect against precomputation by incorporating a large random salt and a tunable work factor (e.g., iterations, memory).
+</div>
+
+<h3>Available Algorithms in VeraCrypt</h3>
+<ul style="text-align:left; margin-top:18px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
+<li style="text-align:left; margin-top:0px; margin-bottom:8px; padding:0px">
+<strong><a href="Argon2id.html" style="color:#0080c0; text-decoration:none">Argon2id</a>:</strong> A modern, memory-hard KDF (based on BLAKE2b internally). Recommended for new volumes. No separate hash selection is required.
+</li>
+<li style="text-align:left; margin-top:0px; margin-bottom:0px; padding:0px">
+<strong><a href="pbkdf2.html" style="color:#0080c0; text-decoration:none">PBKDF2-HMAC</a>:</strong> A widely deployed KDF that uses HMAC with a selectable hash function. Supported HMAC hashes in VeraCrypt:
+<a href="SHA-512.html" style="color:#0080c0; text-decoration:none">SHA-512</a>, <a href="SHA-256.html" style="color:#0080c0; text-decoration:none">SHA-256</a>, <a href="Whirlpool.html" style="color:#0080c0; text-decoration:none">Whirlpool</a>, <a href="BLAKE2s-256.html" style="color:#0080c0; text-decoration:none">BLAKE2s-256</a>, and <a href="Streebog.html" style="color:#0080c0; text-decoration:none">Streebog</a>.
+</li>
+</ul>
+
+
+</div>
+</div><div class="ClearBoth"></div></body></html>