Linux: add Arch package build support

* Update Polish translation

* Update Polish translation

.github/FUNDING.yml

@@ -1 +1 @@
-custom: "https://www.veracrypt.fr/en/Donation.html"
+custom: "https://veracrypt.jp/en/Donation.html"

.github/stale.yml

@@ -20,6 +20,6 @@ closeComment: >
   or it has been fixed in a newer version. If it’s an enhancement
   and hasn't been taken on for so long, then it seems no one has
   the time to implement this.
-  Please reopen if you still encounter this issue with the [latest stable version](https://www.veracrypt.fr/en/Downloads.html).
+  Please reopen if you still encounter this issue with the [latest stable version](https://veracrypt.jp/en/Downloads.html).
   You can also contribute directly by providing a pull request.
   Thank you!

.github/workflows/build-linux.yml

@@ -188,7 +188,7 @@ jobs:
 
     - name: Cleanup old caches
       uses: actions/github-script@v6
-      if: always()
+      if: ${{ always() && github.event_name == 'push' && github.ref == 'refs/heads/master' }}
       with:
         github-token: ${{ secrets.GITHUB_TOKEN }}
         script: |

.github/workflows/xmlvalidate.sh

@@ -1,42 +1,196 @@
 #!/bin/bash
-fail=false
+set -euo pipefail # Exit on error, undefined variable, or pipe failure
 
-# Get all string keys
-KEYS=$(grep -oP '<entry[\ ]+lang="[^"]+"[\ ]+key="\K[^"]+' "$1"/src/Common/Language.xml)
+# --- Configuration ---
+SCRIPT_NAME=$(basename "$0")
+FAIL_FLAG=false
 
-for file in {"$1"/Translations/Language.*.xml,"$1"/src/Common/Language.xml}; do
-  echo "$file"
-  passes=true
-  
-  # Validate xml
-  output=$(fxparser -V "$file")
-  returnvalue=$?
+# --- Colors ---
+COLOR_RED='\033[0;31m'
+COLOR_GREEN='\033[0;32m'
+COLOR_YELLOW='\033[0;33m'
+COLOR_CYAN='\033[0;36m'
+COLOR_MAGENTA='\033[0;35m'
+COLOR_RESET='\033[0m' # No Color
 
-  if [ "$returnvalue" -ne "0" ]; then
-    passes=false
-    fail=true
-    echo $output
-  fi
+# --- Helper Functions for Output ---
+log_info() { echo -e "${COLOR_CYAN}$1${COLOR_RESET}"; }
+log_success() { echo -e "${COLOR_GREEN}$1${COLOR_RESET}"; }
+log_warning() { echo -e "${COLOR_YELLOW}Warning: $1${COLOR_RESET}"; }
+log_error() { echo -e "${COLOR_RED}Error: $1${COLOR_RESET}" >&2; }
+log_detail() { echo -e "  $1"; }
+log_detail_success() { echo -e "  ${COLOR_GREEN}$1${COLOR_RESET}"; }
+log_detail_error() { echo -e "  ${COLOR_RED}$1${COLOR_RESET}"; }
+log_detail_warning() { echo -e "  ${COLOR_YELLOW}$1${COLOR_RESET}"; }
+log_detail_magenta() { echo -e "    ${COLOR_MAGENTA}$1${COLOR_RESET}"; }
 
-  # Ensure each key found in common xml is found in translation xmls
-  for key in $KEYS; do
-    if ! grep -q "$key" "$file"; then
-      echo "Key $key not found in $file"
-      passes=false
-      fail=true
+# --- Parameter Validation ---
+if [ "$#" -ne 1 ]; then
+    log_error "Usage: $SCRIPT_NAME <Path_To_VeraCrypt_Root>"
+    log_error "Example: $SCRIPT_NAME /path/to/VeraCrypt"
+    exit 1
+fi
+
+ROOT_PATH="$1"
+
+if [ ! -d "$ROOT_PATH" ]; then
+    log_error "Root path '$ROOT_PATH' not found or is not a directory."
+    exit 1
+fi
+
+# Define the path to the common Language.xml
+COMMON_FILE="$ROOT_PATH/src/Common/Language.xml"
+
+# Check if the common Language.xml exists
+if [ ! -f "$COMMON_FILE" ]; then
+    log_error "Common Language.xml not found or is not a file at path: $COMMON_FILE"
+    exit 1
+fi
+
+log_info "Extracting keys from $COMMON_FILE"
+
+# Define regex pattern to extract 'key' attributes from <entry> elements
+KEY_EXTRACTION_PATTERN='<entry\s+lang="[^"]+"\s+key="([^"]+)"'
+
+# Extract all keys using grep with PCRE (-P) and only outputting the captured group (-o)
+# Use process substitution and readarray to populate the KEYS array
+# Ensure grep returns 0 even if no match, or handle non-zero for no match
+KEYS_STRING=$(grep -oP "$KEY_EXTRACTION_PATTERN" "$COMMON_FILE" | sed -E 's/.*key="([^"]+)".*/\1/' || true)
+if [ -z "$KEYS_STRING" ]; then
+    KEYS=()
+else
+    readarray -t KEYS < <(echo "$KEYS_STRING")
+fi
+
+
+if [ ${#KEYS[@]} -eq 0 ]; then
+    log_warning "No keys found in $COMMON_FILE using pattern: $KEY_EXTRACTION_PATTERN"
+    # If this should be an error, uncomment next lines:
+    # log_error "No keys found in $COMMON_FILE."
+    # exit 1
+else
+    log_info "Found ${#KEYS[@]} keys."
+fi
+
+# Define the regex for finding invalid escape sequences.
+# Valid sequences: \n, \r, \t, \\, \"
+INVALID_ESCAPE_REGEX='(?<!\\)(?:\\\\)*\\([^nrt\\"])' # This is better
+ALLOWED_ESCAPES_MESSAGE="Allowed sequences are: \\n, \\r, \\t, \\\\ (for literal backslash), \\\" (for literal quote)"
+
+# Retrieve all translation XML files in the Translations folder
+TRANSLATION_FOLDER="$ROOT_PATH/Translations"
+FILES_TO_PROCESS=()
+
+# Add common file first
+FILES_TO_PROCESS+=("$COMMON_FILE")
+
+if [ ! -d "$TRANSLATION_FOLDER" ]; then
+    log_warning "Translations folder not found at path: $TRANSLATION_FOLDER. Skipping translation files."
+else
+    # Use find to get translation files. nullglob helps avoid errors if no files match.
+    shopt -s nullglob
+    for lang_file in "$TRANSLATION_FOLDER"/Language.*.xml; do
+        FILES_TO_PROCESS+=("$lang_file")
+    done
+    shopt -u nullglob # Reset nullglob
+    if [ ${#FILES_TO_PROCESS[@]} -eq 1 ]; then # Only common file was added
+        log_warning "No Language.*.xml files found in $TRANSLATION_FOLDER."
+    fi
+fi
+
+if [ ${#FILES_TO_PROCESS[@]} -eq 0 ]; then
+    log_warning "No files found to process."
+    exit 0 # Or 1 if this is an error condition
+fi
+
+# Iterate through each file and perform validations
+for file in "${FILES_TO_PROCESS[@]}"; do
+    if [ ! -f "$file" ]; then
+        log_warning "File not found or is not a file, skipping: $file"
+        continue
+    fi
+    echo # Newline for readability
+    log_info "Processing file: $file"
+    CURRENT_FILE_PASSES=true
+
+    # 1. Validate XML using fxparser
+    log_detail "Validating XML structure..."
+    # Capture stdout and stderr, get exit code
+    FXPARSER_OUTPUT=$(fxparser -V "$file" 2>&1)
+    FXPARSER_EXIT_CODE=$?
+
+    if [ "$FXPARSER_EXIT_CODE" -ne 0 ]; then
+        CURRENT_FILE_PASSES=false
+        FAIL_FLAG=true
+        log_detail_error "XML Validation Failed for $file (fxparser exit code: $FXPARSER_EXIT_CODE):"
+        while IFS= read -r line; do
+            log_detail_error "    $line"
+        done <<< "$FXPARSER_OUTPUT"
+    else
+        log_detail_success "XML structure is valid."
+    fi
+
+    # 2. Check for invalid backslash escape sequences
+    log_detail "Checking for invalid escape sequences..."
+    # Use grep -P for PCRE, -n for line numbers. --color=never to avoid grep's own coloring here.
+    # We check grep's exit code: 0 if found, 1 if not found, >1 for error.
+    INVALID_ESCAPE_MATCHES=$(grep -P -n --color=never "$INVALID_ESCAPE_REGEX" "$file" || true)
+
+    if [ -n "$INVALID_ESCAPE_MATCHES" ]; then
+        log_detail_error "File '$file' contains potentially invalid backslash escape sequences."
+        log_detail_error "$ALLOWED_ESCAPES_MESSAGE"
+        log_detail_error "Instances found:"
+        while IFS= read -r line_match; do
+            # Extract line number and the line content from grep's output (e.g., "123:content")
+            LINE_NUMBER=$(echo "$line_match" | cut -d: -f1)
+            LINE_CONTENT=$(echo "$line_match" | cut -d: -f2-)
+            # Trim whitespace (optional, but PowerShell did it)
+            TRIMMED_LINE_CONTENT=$(echo "$LINE_CONTENT" | sed 's/^[[:space:]]*//;s/[[:space:]]*$//')
+            log_detail_magenta "Line $LINE_NUMBER: $TRIMMED_LINE_CONTENT"
+        done <<< "$INVALID_ESCAPE_MATCHES"
+        CURRENT_FILE_PASSES=false
+        FAIL_FLAG=true
+    else
+        log_detail_success "No invalid escape sequences found."
+    fi
+
+    # 3. Check for the presence of each key in the current file (if keys were found)
+    if [ ${#KEYS[@]} -gt 0 ]; then
+        log_detail "Checking for key completeness..."
+        KEYS_MISSING_IN_CURRENT_FILE=0
+        for key_entry in "${KEYS[@]}"; do
+            # Search for key="KEY_NAME"
+            SEARCH_PATTERN_FOR_KEY="key=\"$key_entry\""
+            if ! grep -q "$SEARCH_PATTERN_FOR_KEY" "$file"; then
+                log_detail_error "Key '$key_entry' (from $COMMON_FILE) not found in $file"
+                CURRENT_FILE_PASSES=false
+                FAIL_FLAG=true
+                ((KEYS_MISSING_IN_CURRENT_FILE++))
+            fi
+        done
+        if [ "$KEYS_MISSING_IN_CURRENT_FILE" -eq 0 ]; then
+            log_detail_success "All keys from $COMMON_FILE are present."
+        else
+            log_detail_error "$KEYS_MISSING_IN_CURRENT_FILE key(s) missing."
+        fi
+    else
+        log_detail_warning "Skipping key completeness check as no keys were extracted from $COMMON_FILE."
+    fi
+
+    # Output the result for the current file
+    if [ "$CURRENT_FILE_PASSES" = true ]; then
+        log_success "$file PASSED all checks."
+    else
+        log_error "$file FAILED one or more checks."
     fi
-  done
-  
-  if [ "$passes" = true ]; then
-    echo -e "\e[32m$file passes xml validation.\e[0m"
-  else
-    echo -e "\e[31m$file fails xml validation.\e[0m"
-  fi
-  
 done
 
-if [ "$fail" = true ]; then
-  exit 1
+# Exit with appropriate status code
+echo # Newline for readability
+if [ "$FAIL_FLAG" = true ]; then
+    log_error "Overall Result: One or more files failed validation."
+    exit 1
 else
-  exit 0
+    log_success "Overall Result: All processed files passed all checks successfully."
+    exit 0
 fi

.github/workflows/xmlvalidate.yml

@@ -2,13 +2,13 @@ name: Validate XML
 
 on:
   push:
-    branches: [ "ci" ]
+    branches: [ "master" ]
     paths:
       - 'Translations/*'
       - 'src/Common/Language.xml'
       - '.github/workflows/xmlvalidate.*'
   pull_request:
-    branches: [ "ci" ]
+    branches: [ "master" ]
     paths:
       - 'Translations/*'
       - 'src/Common/Language.xml'
@@ -31,6 +31,6 @@ jobs:
       with:
         node-version: 'latest'
     - name: Install fast-xml-parser
-      run: npm install fast-xml-parser -g
+      run: npm install fast-xml-parser@4.5.2 -g
     - name: Run XML validator script
       run: ${{ github.workspace }}/.github/workflows/xmlvalidate.sh "${{ github.workspace }}"

.gitignore

@@ -17,7 +17,15 @@ src/Main/veracrypt
 *.osse41
 *.ossse3
 *.oshani
+*.oaesni
+*.oavx2
 *.oarmv8crypto
+src/Setup/Linux/packaging/
+src/Setup/Linux/usr/
+src/Setup/Linux/veracrypt.AppDir/usr/
+src/Setup/Linux/veracrypt.AppDir/veracrypt.png
+src/Setup/Linux/veracrypt_*.tar.gz
+src/Setup/Linux/veracrypt-*-setup-*
 
 # VC macOS build artifacts
 src/Main/VeraCrypt
@@ -33,6 +41,13 @@ src/Setup/MacOSX/*.pkg
 src/wxrelease
 src/wxdebug
 
+# Arch Linux package build artifacts
+src/Build/Packaging/arch/pkg/
+src/Build/Packaging/arch/src/
+src/Build/Packaging/arch/PKGBUILD.release
+src/Build/Packaging/arch/*.pkg.tar*
+src/Build/Packaging/arch/*.log
+
 src/.vs
 
 src/Boot/Windows/obj
@@ -109,4 +124,4 @@ src/Setup/Release
 src/Setup/PortableRelease
 
 src/SetupDLL/Debug
-src/SetupDLL/Release
+src/SetupDLL/Release

License.txt

@@ -14,7 +14,7 @@ licenses can be found below.
 
 This license does not grant you rights to use any
 contributors' name, logo, or trademarks, including IDRIX,
-VeraCrypt and all derivative names.
+AM Crypto, VeraCrypt and all derivative names.
 For example, the following names are not allowed: VeraCrypt,
 VeraCrypt+, VeraCrypt Professional, iVeraCrypt, etc. Nor any
 other names confusingly similar to the name VeraCrypt (e.g.,

README.md

@@ -29,8 +29,8 @@ 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
-it is also available [online](https://www.veracrypt.fr/en/CompilingGuidelineWin.html).
+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,8 +78,8 @@ 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
-it is also available [online](https://www.veracrypt.fr/en/CompilingGuidelineLinux.html).
+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:
 
@@ -91,7 +91,7 @@ it is also available [online](https://www.veracrypt.fr/en/CompilingGuidelineLinu
 - wxWidgets 3.0 shared library and header files installed or
   wxWidgets 3.0 library source code (available at https://www.wxwidgets.org)
 - FUSE library and header files (available at https://github.com/libfuse/libfuse
-  and https://osxfuse.github.io/)
+  and https://macfuse.github.io/)
 - PCSC-lite library and header files (available at https://github.com/LudovicRousseau/PCSC)
 
 ## Instructions for Building VeraCrypt for Linux and Mac OS X:
@@ -128,6 +128,15 @@ built using the 'NOGUI' parameter:
 
 `$ make NOGUI=1 WXSTATIC=1`
 
+## Arch Linux package build:
+
+Arch Linux users can build and install a package from the current checkout with
+makepkg:
+
+`$ cd src/Build/Packaging/arch`
+
+`$ makepkg -si`
+
 On MacOSX, building a console-only executable is not supported.
 
 ## Mac OS X specifics:
@@ -163,8 +172,8 @@ compile using the following commands:
 
 `$ sudo make install`
 
-After making sure pkg-config is available, download and install OSXFuse from
-https://osxfuse.github.io/
+After making sure pkg-config is available, download and install macFUSE from
+https://macfuse.github.io/
 
 The [build_veracrypt_macosx.sh](./src/Build/build_veracrypt_macosx.sh) script performs the
 full build of VeraCrypt including the creation of the installer pkg. It expects
@@ -177,9 +186,9 @@ src/Main/Main.make (look for lines containing "Developer ID Application" and
 "Developer ID Installer"). You'll have to modify these lines to put the ID of
 your Code Signing certificates or comment them out if you don't have one.
 
-Because of incompatibility issues with OSXFUSE, the SDK 10.9 generates a
-VeraCrypt binary that has issues communicating with the OSXFUSE kernel extension.
-Thus, we recommend using a different OSX SDK version for building VeraCrypt.
+Because of incompatibility issues with macFUSE, the SDK 10.9 generates a
+VeraCrypt binary that has issues communicating with the macFUSE kernel extension.
+Thus, we recommend using a different macOS SDK version for building VeraCrypt.
 
 The Packages installer that is used for the VeraCrypt official build has been notarized by IDRIX and it is available at
 https://github.com/idrassi/packages/releases
@@ -200,16 +209,18 @@ If you intend to implement a feature, please contact us first to make sure:
 3. Whether we need the help of third-party developers with implementing the feature.
 
 Information on how to contact us can be found at:
-https://www.veracrypt.fr/
+https://veracrypt.jp/
+https://veracrypt.io/ (mirror)
 
 # V. Legal Information
 
 ## Copyright Information
 
 This software as a whole:  
-Copyright (c) 2013-2025 IDRIX. All rights reserved.  
+Copyright (c) 2025 AM Crypto. All rights reserved.  
 
 Portions of this software:  
+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.  
@@ -232,4 +243,5 @@ documentation, are the sole property of their respective owners.
 
 # VI. Further Information
 
-https://www.veracrypt.fr
+https://veracrypt.jp
+https://veracrypt.io (mirror)

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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="ar" key="TC_INSTALLER_IS_RUNNING">‮أداة تنصيب ڤيراكربت عاملة حاليا في هذا النظام و تجري أو تهيئ تنصيبا أو تحديثا. قبل المواصلة انتظر حتى تتم عملها أو أغلقها. إن تعذّر إغلاقها فأعد تشغيل النظام.</entry>
     <entry lang="ar" key="INSTALL_FAILED">‮فشل التنصيب.</entry>
     <entry lang="ar" key="UNINSTALL_FAILED">‮فشلت الإزالة.</entry>
-    <entry lang="ar" key="DIST_PACKAGE_CORRUPTED">‮حزمة التوزيع هذه معطوبة. حاول تنزيلها مجددا (يستحسن من موقع ڤيراكربت الرسمي في ‪https://www.veracrypt.fr‬).</entry>
+    <entry lang="ar" key="DIST_PACKAGE_CORRUPTED">‮حزمة التوزيع هذه معطوبة. حاول تنزيلها مجددا (يستحسن من موقع ڤيراكربت الرسمي في ‪https://veracrypt.jp‬).</entry>
     <entry lang="ar" key="CANNOT_WRITE_FILE_X">‮تعذّرت كتابة الملف ‪%s‬</entry>
     <entry lang="ar" key="EXTRACTING_VERB">‮يجري الاستحراج</entry>
     <entry lang="ar" key="CANNOT_READ_FROM_PACKAGE">‮تعذّرت قراءة البيانات من الحزمة.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="ar" key="HIDDEN_OS_CREATION_PREINFO_HELP">‮في الخطوات التالية سينشئ ڤيراكربت نظام التشغيل المخفي بنسخ محتوى قسم النظام إلى المجلد المخفي (البيانات المنسوخة ستُعمى لحظيا بمفتاح تعمية يختلف عن الذي سيستخدم لنظام التشغيل التمويهي). ‮ ‮لاحظ أن هذه الصيرورة ستجري في بيئة ما قبل الإقلاع (قبل أن يشتغل ويندوز) و أنها قد تستغرق وقتا طويلا حتى تتم؛ بضع ساعات أو حتى أياما (حسب حجم قسم النظام و قوة الحاسوب). ‮ ‮سيكون بوسعك مقاطعة الصيرورة و إطفاء الحاسوب ثم بدء نظام التشغيل و معاودة الصيرورة لاحقا. إلا أنك إذا ما قاطعت صيرورة نسخ نظام التشغيل فإنها ستبدأ من البداية عند معاودتها (لأن محتويات قسم النظام ينبغي ألا تتغير أثناء النسخ).</entry>
     <entry lang="ar" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">‮أتريد إلغاء صيرورة إنشاء نظام التسغيل المخفي كلية؟ ‮ ‮ملاحظة: لن يمكنك معاودة الصيرورة إن ألغيتها الآن.</entry>
     <entry lang="ar" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">‮أتريد إلغاء الاختبار المبدئي لتعمية النظام؟</entry>
-    <entry lang="ar" key="BOOT_PRETEST_FAILED_RETRY">فشل الاختبار المبدئي لتشفير فيراكربت. هل تريد إعادة المحاولة?\n\nإذا اخترت 'لا', سيتم إزالة برنامج الإقلاع من فيراكربت.\n\nملاحظة:\n\n- إذا لم يطلب برنامج إقلاع فيراكربت كلمة سر قبل ويندوز, فهذا يعني أن نظام التشغيل ليس مثبتا على نفس القسم الذي يقلع منه. وهذا ليس مدعوما.\n\n- إذا استخدمت خوارزمية تشفير غير AES وفشل عملية الإقلاع (مع إدخالك لكلمة السر), فيمكن أن يكون المحرك به خلل في التصميم. اختر 'لا', وحاول تشفير قسم/قرص النظام مرة أخرى, AES واستخدم خزارزمية تشفير (التي لها أقل المتطلبات بالنسبة للذاكرة).\n\n- للمزيد عن الأسباب والحلول, راجع: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="ar" key="BOOT_PRETEST_FAILED_RETRY">فشل الاختبار المبدئي لتشفير فيراكربت. هل تريد إعادة المحاولة?\n\nإذا اخترت 'لا', سيتم إزالة برنامج الإقلاع من فيراكربت.\n\nملاحظة:\n\n- إذا لم يطلب برنامج إقلاع فيراكربت كلمة سر قبل ويندوز, فهذا يعني أن نظام التشغيل ليس مثبتا على نفس القسم الذي يقلع منه. وهذا ليس مدعوما.\n\n- إذا استخدمت خوارزمية تشفير غير AES وفشل عملية الإقلاع (مع إدخالك لكلمة السر), فيمكن أن يكون المحرك به خلل في التصميم. اختر 'لا', وحاول تشفير قسم/قرص النظام مرة أخرى, AES واستخدم خزارزمية تشفير (التي لها أقل المتطلبات بالنسبة للذاكرة).\n\n- للمزيد عن الأسباب والحلول, راجع: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="ar" key="SYS_DRIVE_NOT_ENCRYPTED">‮لا يبدو أن قسم\\سواقة النظام مُعمّاة (لا جزئيا و لا بالكامل).</entry>
     <entry lang="ar" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">‮قسم\\سواقة النظام مُعمّاة (جزئيا أو بالكامل). ‮ ‮ظهِّر قسم\\سواقة النظام كُليّا قبل المواصلة. لفعل هذا اختر 'نظام' &gt; 'ظهِّر نهائيا قسم\\سواقة النظام' من قائمة نافذة ڤيراكربت الرئيسية.</entry>
     <entry lang="ar" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">حينما يتم تشفير قسم/قرص النظام (كليا أو جزئيا), لا يمكنك تخفيض فيراكربت (لكن يمكنك الترقية أو تثبيت نفس الإصدار).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="ar" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">خطأ: يستخدم المحرك حجم قطاع غير 512 بايت.\n\nبسبب قيود المكونات المتاحة على نظامك، لا يمكن إنشاء / استخدام الأحجام المستضافة على القسم / الجهاز على المحرك.\n\nالحلول الممكنة:\n- إنشاء حجم مستضاف على الملفات (حاوية) على المحرك.\n- استخدام محرك بأحجام قطاع 512 بايت.\n- استخدام VeraCrypt على نظام آخر.</entry>
     <entry lang="ar" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">ملف / جهاز المضيف قيد الاستخدام بالفعل.</entry>
     <entry lang="ar" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">فتحة الحجم غير متاحة.</entry>
-    <entry lang="ar" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">يتطلب VeraCrypt إصدار OSXFUSE 2.5 أو أحدث.</entry>
+    <entry lang="ar" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">يتطلب VeraCrypt إصدار macFUSE 2.5 أو أحدث.</entry>
     <entry lang="ar" key="EXCEPTION_OCCURRED">حدث استثناء</entry>
     <entry lang="ar" key="ENTER_PASSWORD">إدخال كلمة السر</entry>
     <entry lang="ar" key="ENTER_TC_VOL_PASSWORD">‮أدخل كلمة سر مجلد ڤيراكربت</entry>
@@ -1644,6 +1644,50 @@
     <entry lang="ar" key="MOUNTPOINT_BLOCKED">خطأ: نقطة تركيب الحجم محظورة لأنها تحل محل دليل نظام محمي.\n\nيرجى اختيار نقطة تركيب مختلفة.</entry>
     <entry lang="ar" key="MOUNTPOINT_NOTALLOWED">خطأ: نقطة تركيب الحجم غير مسموح بها لأنها تحل محل دليل مدرج ضمن متغير البيئة PATH.\n\nيرجى اختيار نقطة تركيب مختلفة.</entry>
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="en" key="TC_INSTALLER_IS_RUNNING">VeraCrypt Installer is currently running on this system and performing or preparing installation or update of VeraCrypt. Before you proceed, please wait for it to finish or close it. If you cannot close it, please restart your computer before proceeding.</entry>
     <entry lang="be" key="INSTALL_FAILED">Усталёўка не выкананая.</entry>
     <entry lang="be" key="UNINSTALL_FAILED">Выдаленне не выканана.</entry>
-    <entry lang="be" key="DIST_PACKAGE_CORRUPTED">Гэты дыстрыбутыўны пакет пашкоджаны. Загрузіце яго ізноў (пажадана з афіцыйнага сайта VeraCrypt - https://www.veracrypt.fr).</entry>
+    <entry lang="be" key="DIST_PACKAGE_CORRUPTED">Гэты дыстрыбутыўны пакет пашкоджаны. Загрузіце яго ізноў (пажадана з афіцыйнага сайта VeraCrypt - https://veracrypt.jp).</entry>
     <entry lang="be" key="CANNOT_WRITE_FILE_X">Немагчыма запісаць файл %s</entry>
     <entry lang="be" key="EXTRACTING_VERB">Выманне</entry>
     <entry lang="be" key="CANNOT_READ_FROM_PACKAGE">Немагчыма прачытаць дадзеныя з дыстрыбутыва.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="en" key="HIDDEN_OS_CREATION_PREINFO_HELP">In the next steps, VeraCrypt will create the hidden operating system by copying the content of the system partition to the hidden volume (data being copied will be encrypted on the fly with an encryption key different from the one that will be used for the decoy operating system).\n\nPlease note that the process will be performed in the pre-boot environment (before Windows starts) and it may take a long time to complete; several hours or even several days (depending on the size of the system partition and on the performance of your computer).\n\nYou will be able to interrupt the process, shut down your computer, start the operating system and then resume the process. However, if you interrupt it, the entire process of copying the system will have to start from the beginning (because the content of the system partition must not change during cloning).</entry>
     <entry lang="en" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Do you want to cancel the entire process of creation of the hidden operating system?\n\nNote: You will NOT be able to resume the process if you cancel it now.</entry>
     <entry lang="be" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Вы жадаеце адмяніць перад-тэст шыфравання сістэмы?</entry>
-    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="en" key="SYS_DRIVE_NOT_ENCRYPTED">The system partition/drive does not appear to be encrypted (neither partially nor fully).</entry>
     <entry lang="be" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Сістэмны падзел/дыск зашыфраваны (часткова ці цалкам).\n\nПерш чым працягнуць, цалкам дэшыфруйце сістэмны падзел/дыск. Каб гэта зрабіць, абярыце ў галоўным акне VeraCrypt меню 'Сістэма' &gt; 'Permanently Decrypt System Partition/Drive'.</entry>
     <entry lang="en" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">When the system partition/drive is encrypted (partially or fully), you cannot downgrade VeraCrypt (but you can upgrade it or reinstall the same version).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="en" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Error: The drive uses a sector size other than 512 bytes.\n\nDue to limitations of components available on your platform, partition/device-hosted volumes cannot be created/used on the drive.\n\nPossible solutions:\n- Create a file-hosted volume (container) on the drive.\n- Use a drive with 512-byte sectors.\n- Use VeraCrypt on another platform.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">The host file/device is already in use.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Volume slot unavailable.</entry>
-    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires OSXFUSE 2.5 or above.</entry>
+    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires macFUSE 2.5 or above.</entry>
     <entry lang="en" key="EXCEPTION_OCCURRED">Exception occurred</entry>
     <entry lang="en" key="ENTER_PASSWORD">Enter password</entry>
     <entry lang="en" key="ENTER_TC_VOL_PASSWORD">Enter VeraCrypt Volume Password</entry>
@@ -1644,6 +1644,50 @@
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="bg" key="TC_INSTALLER_IS_RUNNING">Инсталатора на VeraCrypt в момента е стартиран на тази система и подготвя или извършва инсталация или обновяване на VeraCrypt. Преди да продължите, моля изчакайте го да свърши или го затворете. Ако не можете да го затворите, моля рестартирайте вашия компютър преди да продължите.</entry>
     <entry lang="bg" key="INSTALL_FAILED">Инсталацията неуспешна.</entry>
     <entry lang="bg" key="UNINSTALL_FAILED">Деинсталация неуспешна.</entry>
-    <entry lang="bg" key="DIST_PACKAGE_CORRUPTED">Този пакет за дистрибуция е повреден. Моля, опитайте да го изтеглите отново (за предпочитане от официалния уебсайт на VeraCrypt - https://www.veracrypt.fr).</entry>
+    <entry lang="bg" key="DIST_PACKAGE_CORRUPTED">Този пакет за дистрибуция е повреден. Моля, опитайте да го изтеглите отново (за предпочитане от официалния уебсайт на VeraCrypt - https://veracrypt.jp).</entry>
     <entry lang="bg" key="CANNOT_WRITE_FILE_X">Не може да се запише файл %s</entry>
     <entry lang="bg" key="EXTRACTING_VERB">Извличане</entry>
     <entry lang="bg" key="CANNOT_READ_FROM_PACKAGE">Не може да се чете от пакета.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="en" key="HIDDEN_OS_CREATION_PREINFO_HELP">In the next steps, VeraCrypt will create the hidden operating system by copying the content of the system partition to the hidden volume (data being copied will be encrypted on the fly with an encryption key different from the one that will be used for the decoy operating system).\n\nPlease note that the process will be performed in the pre-boot environment (before Windows starts) and it may take a long time to complete; several hours or even several days (depending on the size of the system partition and on the performance of your computer).\n\nYou will be able to interrupt the process, shut down your computer, start the operating system and then resume the process. However, if you interrupt it, the entire process of copying the system will have to start from the beginning (because the content of the system partition must not change during cloning).</entry>
     <entry lang="en" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Do you want to cancel the entire process of creation of the hidden operating system?\n\nNote: You will NOT be able to resume the process if you cancel it now.</entry>
     <entry lang="bg" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Желаете ли да прекратите предварителният тест на системното криптиране?</entry>
-    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="bg" key="SYS_DRIVE_NOT_ENCRYPTED">Изглежда, че системният дял/устройство не е криптиран (нито частично, нито изцяло).</entry>
     <entry lang="bg" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Вашият системен дял/устройство е криптиран (частично или изцяло).\n\nМоля, декриптирайте вашият системен дял/устройство изцяло преди да продължите. За да направите това, изберете 'Система' &gt; 'Декриптиране на системния дял/устройство за постоянно' от менюто на гавния процорез на VeraCrypt.</entry>
     <entry lang="en" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">When the system partition/drive is encrypted (partially or fully), you cannot downgrade VeraCrypt (but you can upgrade it or reinstall the same version).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="en" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Error: The drive uses a sector size other than 512 bytes.\n\nDue to limitations of components available on your platform, partition/device-hosted volumes cannot be created/used on the drive.\n\nPossible solutions:\n- Create a file-hosted volume (container) on the drive.\n- Use a drive with 512-byte sectors.\n- Use VeraCrypt on another platform.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">The host file/device is already in use.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Volume slot unavailable.</entry>
-    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires OSXFUSE 2.5 or above.</entry>
+    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires macFUSE 2.5 or above.</entry>
     <entry lang="en" key="EXCEPTION_OCCURRED">Exception occurred</entry>
     <entry lang="en" key="ENTER_PASSWORD">Enter password</entry>
     <entry lang="en" key="ENTER_TC_VOL_PASSWORD">Enter VeraCrypt Volume Password</entry>
@@ -1640,10 +1640,54 @@
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="ca" key="TC_INSTALLER_IS_RUNNING">L'instal·lador del VeraCrypt està realitzant una instal·lació o actualització del programa. Abans de continuar, si us plau esperi que acabi o tenqui'l. Si no el pot tancar, reinicii l'ordinador abans de continuar.</entry>
     <entry lang="ca" key="INSTALL_FAILED">La instal·lació ha fallat.</entry>
     <entry lang="ca" key="UNINSTALL_FAILED">La desinstal·lació ha fallat.</entry>
-    <entry lang="ca" key="DIST_PACKAGE_CORRUPTED">Aquest paquet de distribució està malmès. Si us plau, torni'l a descarregar (preferentment des del lloc web oficial del VeraCrypt, a https://www.veracrypt.fr).</entry>
+    <entry lang="ca" key="DIST_PACKAGE_CORRUPTED">Aquest paquet de distribució està malmès. Si us plau, torni'l a descarregar (preferentment des del lloc web oficial del VeraCrypt, a https://veracrypt.jp).</entry>
     <entry lang="ca" key="CANNOT_WRITE_FILE_X">No s'ha pogut escriure el fitxer %s</entry>
     <entry lang="ca" key="EXTRACTING_VERB">Extraient</entry>
     <entry lang="ca" key="CANNOT_READ_FROM_PACKAGE">No s'han pogut llegir dades del paquet.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="ca" key="HIDDEN_OS_CREATION_PREINFO_HELP">Als passos següents, el VeraCrypt crearà un sistema operatiu ocult copiant el contingut de la partició de sistema al volum ocult (les dades copiades es xifraran al vol amb una clau de xifrat diferent a la que s'utilitza pel sistema operatiu esquer).\n\nAquest procés es durà a terme a l'entorn de prearrencada (abans d'iniciar el Windows) i pot trigar força estona a acabar-se; diverses hores o dies (depenent de la mida de la partició de sistema i del rendiment de l'ordinador).\n\nPorà interrompre el procés, apagar l'ordinador, engegar el sistema operatiu i després continuar el procés. No obstant, si l'interromp, el procés de copiar el sistema haurà de tornar a començar des del principi (ja que el contingut de la partició de sistema no haurien de canviar durant la còpia).</entry>
     <entry lang="ca" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Vol cancel·lar el procés de creació d'un sistema operatiu ocult?\n\nNota: No podrà continuar aquest procés si el cancel·la ara.</entry>
     <entry lang="ca" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Vol cancelar la prova prèvia de xifrat del sistema?</entry>
-    <entry lang="ca" key="BOOT_PRETEST_FAILED_RETRY">Ha fallat la prova prèvia de xifrat del sistema. Vol tornar-ho a provar?\n\nSi selecciona 'No', es desinstal·larà el component d'autenticació prearrencada.\n\nNots.\n\n- Si el gestor d'arranc del VeraCrypt no li demana la contrasenya abans d'engegar el Windows és possible que el seu sistema operatiu no engegui des del disc dur on es troba instal·lat. Això no està suportat.\n\n- Si utilitza un algorisme de xifrat que no sigui AES i la prova prèvia falla (i ha introduït la contrasenya) pot ser degut a un controlador defectuós. Seleccioni 'No' i provi de tornar a xifrar la partició/unitat una altre vegada, però utilitzant l'algorisme de xifrat AES (que necessita menys memòria).\n\n- Per a més possibles causes i solucions, vegi: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="ca" key="BOOT_PRETEST_FAILED_RETRY">Ha fallat la prova prèvia de xifrat del sistema. Vol tornar-ho a provar?\n\nSi selecciona 'No', es desinstal·larà el component d'autenticació prearrencada.\n\nNots.\n\n- Si el gestor d'arranc del VeraCrypt no li demana la contrasenya abans d'engegar el Windows és possible que el seu sistema operatiu no engegui des del disc dur on es troba instal·lat. Això no està suportat.\n\n- Si utilitza un algorisme de xifrat que no sigui AES i la prova prèvia falla (i ha introduït la contrasenya) pot ser degut a un controlador defectuós. Seleccioni 'No' i provi de tornar a xifrar la partició/unitat una altre vegada, però utilitzant l'algorisme de xifrat AES (que necessita menys memòria).\n\n- Per a més possibles causes i solucions, vegi: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="ca" key="SYS_DRIVE_NOT_ENCRYPTED">La partició/unitat de sistema sembla no estar xifrada (ni parcial ni completament).</entry>
     <entry lang="ca" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">La partició/unitat de sistema està xifrada (parcial o completament).\n\nSi us plau, desxifri completament la partició/unitat abans de continuar. Per a fer-ho, seleccioni 'Sistema' &gt; 'Desxifrar la partició/unitat del sistema permenentment'.</entry>
     <entry lang="ca" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">Quan la partició/unitat de sistema està xifrada (parcial o completament) no és possible baixar la versió del VeraCrypt (però es pot actualitzar o reinstal·lar la mateixa versió).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="en" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Error: The drive uses a sector size other than 512 bytes.\n\nDue to limitations of components available on your platform, partition/device-hosted volumes cannot be created/used on the drive.\n\nPossible solutions:\n- Create a file-hosted volume (container) on the drive.\n- Use a drive with 512-byte sectors.\n- Use VeraCrypt on another platform.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">The host file/device is already in use.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Volume slot unavailable.</entry>
-    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires OSXFUSE 2.5 or above.</entry>
+    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires macFUSE 2.5 or above.</entry>
     <entry lang="en" key="EXCEPTION_OCCURRED">Exception occurred</entry>
     <entry lang="en" key="ENTER_PASSWORD">Enter password</entry>
     <entry lang="en" key="ENTER_TC_VOL_PASSWORD">Enter VeraCrypt Volume Password</entry>
@@ -1640,10 +1640,54 @@
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.cs.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="cs" key="TC_INSTALLER_IS_RUNNING">Instalátor programu VeraCrypt momentálně běží na tomto systému a provádí nebo připravuje instalaci nebo update programu VeraCrypt. Než budete pokračovat, počkejte na dokončení nebo jej zavřete. Nemůžete-li ho zavřít, restartujte prosím počítač, než budete pokračovat.</entry>
     <entry lang="cs" key="INSTALL_FAILED">Instalace nebyla úspěšná.</entry>
     <entry lang="cs" key="UNINSTALL_FAILED">Odinstalace nebyla úspěšná.</entry>
-    <entry lang="cs" key="DIST_PACKAGE_CORRUPTED">Distribuční balíček je poškozený. Stáhněte jej prosím znovu (nejlépe z oficiálních stránek programu VeraCrypt na adrese https://www.veracrypt.fr).</entry>
+    <entry lang="cs" key="DIST_PACKAGE_CORRUPTED">Distribuční balíček je poškozený. Stáhněte jej prosím znovu (nejlépe z oficiálních stránek programu VeraCrypt na adrese https://veracrypt.jp).</entry>
     <entry lang="cs" key="CANNOT_WRITE_FILE_X">Nelze zapsat soubor %s</entry>
     <entry lang="cs" key="EXTRACTING_VERB">Rozbalení</entry>
     <entry lang="cs" key="CANNOT_READ_FROM_PACKAGE">Nelze přečíst data z balíčku.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="cs" key="HIDDEN_OS_CREATION_PREINFO_HELP">V následujícím kroku vytvoří VeraCrypt skrytý operační systém tak, že zkopíruje obsah systémového diskového oddílu do skrytého svazku (kopírovaná data budou zašifrována za běhu jiným šifrovacím klíčem, než je ten, co se používá pro klamný operační systém).\n\nÚkon bude proveden v prostředí zavaděče (než se Windows spustí) a může to trvat delší dobu; několik hodin nebo dokonce několik dní (záleží na velikosti systémového diskového oddílu a na výkonu vašeho počítače).\n\nBudete moci úkon přerušit, vypnout počítač a pak spustit operační systém a pokračovat v úkonu. Pokud ho ale přerušíte, celý úkon kopírování systému bude spuštěn úplně od začátku (protože obsah systémového diskového oddílu se nesmí během klonování změnit).</entry>
     <entry lang="cs" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Chcete zrušit celý úkon vytváření skrytého operačního systému?\n\nPoznámka: NEBUDETE moci pokračovat, pokud ho nyní zrušíte.</entry>
     <entry lang="cs" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Chcete zrušit před-testování šifrování systému?</entry>
-    <entry lang="cs" key="BOOT_PRETEST_FAILED_RETRY">Předběžná zkouška zašifrování systému nebyla úspěšná. Chcete to zkusit znovu?\n\nVyberete-li „Ne”, ověřovací součást zavaděče bude odinstalována.\n\nPoznámka:\n\n- Nevyzval-li vás zavaděč VeraCryptu k zadání hesla před spuštěním Windows, je možné, že váš operační systém se nezavádí z disku, na kterém je nainstalován. To není podporováno.\n\n- Pokud jste použili jiný šifrovací algoritmus než AES a předběžná zkouška nebyla úspěšná (a vy jste zadali heslo), může to být způsobeno nevhodně navrženým ovladačem. Vyberte „Ne” a zkuste systémový diskový oddíl/jednotku znovu zašifrovat, ale použijte šifrovací algoritmus AES (který má nejmenší nároky na paměť).\n\n- Pro zjištění, jaké jsou další možné příčiny a řešení, viz: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="cs" key="BOOT_PRETEST_FAILED_RETRY">Předběžná zkouška zašifrování systému nebyla úspěšná. Chcete to zkusit znovu?\n\nVyberete-li „Ne”, ověřovací součást zavaděče bude odinstalována.\n\nPoznámka:\n\n- Nevyzval-li vás zavaděč VeraCryptu k zadání hesla před spuštěním Windows, je možné, že váš operační systém se nezavádí z disku, na kterém je nainstalován. To není podporováno.\n\n- Pokud jste použili jiný šifrovací algoritmus než AES a předběžná zkouška nebyla úspěšná (a vy jste zadali heslo), může to být způsobeno nevhodně navrženým ovladačem. Vyberte „Ne” a zkuste systémový diskový oddíl/jednotku znovu zašifrovat, ale použijte šifrovací algoritmus AES (který má nejmenší nároky na paměť).\n\n- Pro zjištění, jaké jsou další možné příčiny a řešení, viz: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="cs" key="SYS_DRIVE_NOT_ENCRYPTED">Systémový diskový oddíl/disk pravděpodobně není zašifrován (ani částečně ani plně).</entry>
     <entry lang="cs" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Váš systémový diskový oddíl/disk je zašifrován (částečně nebo plně).\n\nPřed pokračováním celý systémový diskový oddíl/disk nejdříve dešifrujte. Chcete-li tak učinit, zvolte „Systém &gt; Trvale dešifrovat systémový diskový oddíl/disk” z nabídky hlavního okna programu VeraCrypt.</entry>
     <entry lang="cs" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">Je-li systémový diskový oddíl/disk zašifrován (částečně nebo úplně), nemůžete snížit verzi VeraCryptu (ale můžete jej aktualizovat nebo přeinstalovat stejnou verzí).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="cs" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Chyba: Disk používá jinou velikost sektoru než 512 bajtů.\n\nVzhledem k omezením komponent dostupných na vaší platformě, svazky hostované diskovým oddílem/zařízením nemohou být vytvořeny/použity.\n\nMožná řešení:\n- Vytvořit na jednotce svazek pro soubory (kontejner).\n- Použít jednotku s 512bajtovými sektory.\n- Použít VeraCrypt na jiné platformě.</entry>
     <entry lang="cs" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">Hostitelský soubor/zařízení se již používá.</entry>
     <entry lang="cs" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Slot pro svazek není k dispozici.</entry>
-    <entry lang="cs" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt vyžaduje minimálně OSXFUSE 2.5.</entry>
+    <entry lang="cs" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt vyžaduje minimálně macFUSE 2.5.</entry>
     <entry lang="cs" key="EXCEPTION_OCCURRED">Vyskytla se chyba</entry>
     <entry lang="cs" key="ENTER_PASSWORD">Zadejte heslo</entry>
     <entry lang="cs" key="ENTER_TC_VOL_PASSWORD">Zadejte heslo ke svazku Veracrypt</entry>
@@ -1644,6 +1644,50 @@
     <entry lang="cs" key="MOUNTPOINT_BLOCKED">CHYBA: Připojovací bod svazku je blokován, jelikož je nadřazen chráněnému systémovému adresáři.\n\nProsím, zvolte jiný přípojovací bod.</entry>
     <entry lang="cs" key="MOUNTPOINT_NOTALLOWED">CHYBA: Připojovací bod svazku není povolen, jelikož přepisuje adresář, jenž je součástí proměnného prostředí PATH.\n\nProsím, vyberte jiný připojovací bod.</entry>
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="da" key="TC_INSTALLER_IS_RUNNING">VeraCrypt Installation kører nu på dette system og udfører eller forbereder installation eller opdatering af VeraCrypt. Før du fortsætter, vent venligst til det afsluttes eller luk det. Hvis du ikke kan lukke det, genstart venligst din computer før du fortsætter.</entry>
     <entry lang="da" key="INSTALL_FAILED">Fejl under installation.</entry>
     <entry lang="da" key="UNINSTALL_FAILED">Fejl under afinstallation.</entry>
-    <entry lang="da" key="DIST_PACKAGE_CORRUPTED">Denne distributions pakke er beskadiget. Prøv venligst at downloade den igen (helst fra det officielle VeraCrypt websted på https://www.veracrypt.fr).</entry>
+    <entry lang="da" key="DIST_PACKAGE_CORRUPTED">Denne distributions pakke er beskadiget. Prøv venligst at downloade den igen (helst fra det officielle VeraCrypt websted på https://veracrypt.jp).</entry>
     <entry lang="da" key="CANNOT_WRITE_FILE_X">Kan ikke skrive fil %s</entry>
     <entry lang="da" key="EXTRACTING_VERB">Udpakker</entry>
     <entry lang="da" key="CANNOT_READ_FROM_PACKAGE">Kan ikke læse data fra pakken.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="en" key="HIDDEN_OS_CREATION_PREINFO_HELP">In the next steps, VeraCrypt will create the hidden operating system by copying the content of the system partition to the hidden volume (data being copied will be encrypted on the fly with an encryption key different from the one that will be used for the decoy operating system).\n\nPlease note that the process will be performed in the pre-boot environment (before Windows starts) and it may take a long time to complete; several hours or even several days (depending on the size of the system partition and on the performance of your computer).\n\nYou will be able to interrupt the process, shut down your computer, start the operating system and then resume the process. However, if you interrupt it, the entire process of copying the system will have to start from the beginning (because the content of the system partition must not change during cloning).</entry>
     <entry lang="da" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Ønsker du at afbryde hele processen med at oprette det skjulte operativsystem?\n\nBemærk: Du vil IKKE være i stand til at fortsætte processen hvis du afbryder nu.</entry>
     <entry lang="da" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Ønsker du at afbryde system krypteringens indledende test?</entry>
-    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="da" key="SYS_DRIVE_NOT_ENCRYPTED">System partition/drev ser ikke ud til at være krypteret (hverken delvist eller helt).</entry>
     <entry lang="da" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Det system partition/drev er krypteret (delvist eller helt).\n\nDekrypter venligst dit system partition/drev helt før du fortsætter. For at gøre dette, vælg 'System' &gt; 'Dekrypter System Partition/Drev Permanent' fra menulinien i VeraCrypt hovedvinduet.</entry>
     <entry lang="en" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">When the system partition/drive is encrypted (partially or fully), you cannot downgrade VeraCrypt (but you can upgrade it or reinstall the same version).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="en" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Error: The drive uses a sector size other than 512 bytes.\n\nDue to limitations of components available on your platform, partition/device-hosted volumes cannot be created/used on the drive.\n\nPossible solutions:\n- Create a file-hosted volume (container) on the drive.\n- Use a drive with 512-byte sectors.\n- Use VeraCrypt on another platform.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">The host file/device is already in use.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Volume slot unavailable.</entry>
-    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires OSXFUSE 2.5 or above.</entry>
+    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires macFUSE 2.5 or above.</entry>
     <entry lang="en" key="EXCEPTION_OCCURRED">Exception occurred</entry>
     <entry lang="en" key="ENTER_PASSWORD">Enter password</entry>
     <entry lang="en" key="ENTER_TC_VOL_PASSWORD">Enter VeraCrypt Volume Password</entry>
@@ -1644,6 +1644,50 @@
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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,8 +1,8 @@
 <?xml version="1.0" encoding="utf-8"?>
 <VeraCrypt>
-  <localization prog-version= "1.26.20">
+  <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" />
+    <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 -->
     <font lang="de" class="normal" size="11" face="default" />
     <font lang="de" class="bold" size="13" face="Arial" />
@@ -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-\nContainerdatei 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>
@@ -612,7 +612,7 @@
     <entry lang="de" key="IDD_PCDM_CHANGE_PKCS5_PRF">Algorithmus für Kopfdatenschlüsselberechnung ändern</entry>
     <entry lang="de" key="IDD_PCDM_ADD_REMOVE_VOL_KEYFILES">Schlüsseldateien dem/vom Volume hinzufügen/entfernen</entry>
     <entry lang="de" key="IDD_PCDM_REMOVE_ALL_KEYFILES_FROM_VOL">Alle Schlüsseldateien vom Volume entfernen</entry>
-    <entry lang="de" key="PASSWORD_CHANGED">Passwort, PIM und/oder Schlüsseldatei(en) wurden erfolgreich geändert.\n\nWICHTIG: Bitte stellen Sie sicher, dass Sie den Abschnitt „Changing Passwords and Keyfiles“ im Kapitel „Security Requirements and Precautions“ im VeraCrypt-\nBenutzerhandbuch gelesen haben.</entry>
+    <entry lang="de" key="PASSWORD_CHANGED">Passwort, PIM und/oder Schlüsseldatei(en) wurden erfolgreich geändert.\n\nWICHTIG: Bitte stellen Sie sicher, dass Sie den Abschnitt „Changing Passwords and Keyfiles“ im Kapitel „Security Requirements and Precautions“ im VeraCrypt-Benutzerhandbuch gelesen haben.</entry>
     <entry lang="de" key="FAVORITE_PIM_CHANGED">Dieses Volume ist ein Systemfavorit und sein PIM wurde geändert.\nMöchten Sie, dass VeraCrypt automatisch die Einstellung des Systemfavoriten aktualisiert (Administratorrechte werden benötigt)?\n\nBitte beachten Sie: Wenn Sie mit „Nein“ antworten, müssen Sie den Systemfavoriten manuell aktualisieren.</entry>
     <entry lang="de" key="SYS_PASSWORD_CHANGED_ASK_RESCUE_DISK">WICHTIG: Wenn Sie Ihren VeraCrypt-Rettungsdatenträger nicht zerstört haben, dann kann Ihre Systempartition/Ihr Systemlaufwerk weiterhin mit dem alten Passwort entschlüsselt werden (durch Starten des VeraCrypt-Rettungsdatenträgers und die Eingabe des alten Passwortes). Sie sollten einen neuen VeraCrypt-Rettungsdatenträger erstellen und den alten vernichten.\n\nMöchten Sie einen neuen Rettungsdatenträger erstellen?</entry>
     <entry lang="de" key="SYS_HKD_ALGO_CHANGED_ASK_RESCUE_DISK">Beachten Sie, dass Ihr VeraCrypt-Rettungsdatenträger weiterhin den vorherigen Algorithmus verwendet. Wenn Sie den vorherigen Algorithmus als unsicher einstufen, dann sollten Sie einen neuen VeraCrypt-Rettungsdatenträger erstellen und den alten vernichten.\n\nMöchten Sie einen neuen Rettungsdatenträger erstellen?</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>
@@ -858,7 +858,7 @@
     <entry lang="de" key="TC_INSTALLER_IS_RUNNING">Das VeraCrypt-Installationsprogramm läuft zurzeit auf diesem Computer und führt eine Installation durch, bereitet eine Installation vor oder aktualisiert VeraCrypt. Bevor Sie fortfahren, warten Sie bitte, bis es beendet ist oder schließen es. Wenn Sie es nicht schließen können, dann starten Sie bitte Ihren Computer neu, bevor Sie fortfahren.</entry>
     <entry lang="de" key="INSTALL_FAILED">Installation fehlgeschlagen.</entry>
     <entry lang="de" key="UNINSTALL_FAILED">Deinstallation fehlgeschlagen.</entry>
-    <entry lang="de" key="DIST_PACKAGE_CORRUPTED">Dieses Paket ist beschädigt. Bitte laden Sie es erneut herunter (vorzugsweise von der offiziellen Webseite https://www.veracrypt.fr).</entry>
+    <entry lang="de" key="DIST_PACKAGE_CORRUPTED">Dieses Paket ist beschädigt. Bitte laden Sie es erneut herunter (vorzugsweise von der offiziellen Webseite https://veracrypt.jp).</entry>
     <entry lang="de" key="CANNOT_WRITE_FILE_X">Kann Datei %s nicht schreiben.</entry>
     <entry lang="de" key="EXTRACTING_VERB">Entpacke</entry>
     <entry lang="de" key="CANNOT_READ_FROM_PACKAGE">Die Paketdaten konnten nicht gelesen werden.</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>
@@ -1232,7 +1232,7 @@
     <entry lang="de" key="HIDDEN_OS_CREATION_PREINFO_HELP">In den nächsten Schritten wird VeraCrypt das versteckte Betriebssystem erstellen, indem der Inhalt der Systempartition in das versteckte Volume kopiert wird. Daten, die kopiert werden, werden „on-the-fly“ (sofort) mit einem anderen Schlüssel als im Köder-System verschlüsselt.\n\nBitte beachten Sie, dass der Prozess in der Pre-Boot-Umgebung durchgeführt wird (bevor Windows startet) und mehrere Stunden oder sogar mehrere Tage dauern kann (abhängig von der Größe der Systempartition und der Leistung Ihres Computers).\n\nSie können den Prozess jederzeit anhalten, Ihren PC ausschalten, neu starten und dann den Prozess fortsetzen. Wenn Sie ihn jedoch unterbrechen, dann muss der gesamte Kopiervorgang des Systems von vorn beginnen (weil sich der Inhalt der Systempartition beim Klonen nicht ändern darf).</entry>
     <entry lang="de" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Möchten Sie den gesamten Vorgang für die Erstellung des versteckten Betriebssystems abbrechen?\n\nHinweis: Sie werden den Vorgang nicht fortsetzen können, wenn Sie ihn jetzt abbrechen.</entry>
     <entry lang="de" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Möchten Sie den Vortest für die Systemverschlüsselung wirklich abbrechen?</entry>
-    <entry lang="de" key="BOOT_PRETEST_FAILED_RETRY">Der VeraCrypt-Systemverschlüsselungsvortest ist fehlgeschlagen. Möchten Sie ihn erneut durchführen?\n\nWenn Sie „Nein“ wählen, wird die Pre-Boot-Authentifikationskomponente deinstalliert.\n\nHinweise:\n\n- Wenn der VeraCrypt-Bootloader vor dem Systemstart nicht nach einem Passwort gefragt hat, ist es möglich, dass das Betriebssystem nicht von dem Laufwerk bootet, auf dem es installiert ist. Dies wird nicht unterstützt.\n\n- Wenn Sie einen anderen Verschlüsselungsalgorithmus als AES nutzen und der Vortest fehlgeschlagen ist (und Sie das Passwort eingegeben haben), kann dies durch einen fehlerhaften Treiber verursacht worden sein. Wählen Sie „Nein“ und versuchen Sie erneut die Systemverschlüsselung durchzuführen, diesmal mit dem AES-Verschlüsselungsalgorithmus (welcher die niedrigsten Speichervoraussetzungen hat).\n\n- Weitere mögliche Ursachen und Lösungen finden Sie unter https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="de" key="BOOT_PRETEST_FAILED_RETRY">Der VeraCrypt-Systemverschlüsselungsvortest ist fehlgeschlagen. Möchten Sie ihn erneut durchführen?\n\nWenn Sie „Nein“ wählen, wird die Pre-Boot-Authentifikationskomponente deinstalliert.\n\nHinweise:\n\n- Wenn der VeraCrypt-Bootloader vor dem Systemstart nicht nach einem Passwort gefragt hat, ist es möglich, dass das Betriebssystem nicht von dem Laufwerk bootet, auf dem es installiert ist. Dies wird nicht unterstützt.\n\n- Wenn Sie einen anderen Verschlüsselungsalgorithmus als AES nutzen und der Vortest fehlgeschlagen ist (und Sie das Passwort eingegeben haben), kann dies durch einen fehlerhaften Treiber verursacht worden sein. Wählen Sie „Nein“ und versuchen Sie erneut die Systemverschlüsselung durchzuführen, diesmal mit dem AES-Verschlüsselungsalgorithmus (welcher die niedrigsten Speichervoraussetzungen hat).\n\n- Weitere mögliche Ursachen und Lösungen finden Sie unter https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="de" key="SYS_DRIVE_NOT_ENCRYPTED">Die Systempartition/das Systemlaufwerk ist offenbar nicht verschlüsselt (weder teilweise noch vollständig).</entry>
     <entry lang="de" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Ihre Systempartition/Ihr Systemlaufwerk ist verschlüsselt (teilweise oder vollständig).\n\nBitte entschlüsseln Sie Ihre Systempartition/Ihr Systemlaufwerk vollständig, bevor Sie fortfahren. Wählen Sie dazu „System“ &gt; „Systempartition/Systemlaufwerk dauerhaft entschlüsseln“ in der Menüleiste des VeraCrypt-Hauptfensters aus.</entry>
     <entry lang="de" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">Wenn die Systempartition/das Systemlaufwerk teilweise oder vollständig verschlüsselt ist, können Sie VeraCrypt nicht downgraden. Sie können es jedoch aktualisieren oder dieselbe Version erneut installieren.</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>
@@ -1556,7 +1556,7 @@
     <entry lang="de" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">FEHLER: Das Laufwerk benutzt eine von 512 Byte verschiedene Sektorgröße.\n\nWegen Komponentenlimitierung auf Ihrer Plattform können partitions- und gerätebasierende Volumes nicht auf dem Laufwerk erstellt/benutzt werden. \n\nMögliche Lösungen:\n- Erstellen Sie einen dateibasierten Volume-Container auf dem Laufwerk.\n- Benutzen Sie ein Laufwerk mit 512-Byte-Sektoren.\n- Benutzen Sie VeraCrypt auf einer anderen Plattform.</entry>
     <entry lang="de" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">Die Host-Datei oder das Host-Gerät ist bereits in Benutzung.</entry>
     <entry lang="de" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Volume-Platz nicht verfügbar.</entry>
-    <entry lang="de" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt erfordert OSXFUSE 2.5 oder höher.</entry>
+    <entry lang="de" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt erfordert macFUSE 2.5 oder höher.</entry>
     <entry lang="de" key="EXCEPTION_OCCURRED">Ausnahme aufgetreten</entry>
     <entry lang="de" key="ENTER_PASSWORD">Passwort eingeben</entry>
     <entry lang="de" key="ENTER_TC_VOL_PASSWORD">VeraCrypt-Volume-Passwort eingeben</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>
@@ -1647,6 +1647,50 @@
     <entry lang="de" key="MOUNTPOINT_BLOCKED">FEHLER: Der Einhängepunkt ist blockiert, da er ein geschütztes Systemverzeichnis überschreibt.\n\nBitte wählen Sie einen anderen Einhängepunkt.</entry>
     <entry lang="de" key="MOUNTPOINT_NOTALLOWED">FEHLER: Der Einhängepunkt ist unzulässig, da er ein Verzeichnis überschreibt, das zur PATH-Umgebungsvariable gehört.\n\nBitte wählen Sie einen anderen Einhängepunkt.</entry>
     <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="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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="de" key="MACOSX_APFS_SYNTHESIZED_DEVICE">Das ausgewählte Gerät '{0}' ist ein synthetischer APFS-Container oder ein synthetisches APFS-Volume und kann nicht als Host für ein VeraCrypt-Raw-Volume verwendet werden.\n\nWählen Sie stattdessen die physische APFS-Speicherpartition{1} aus.</entry>
+    <entry lang="de" key="MACOSX_DEVICE_SYSTEM_PARTITION">Das ausgewählte Gerät '{0}' ist eine macOS-System-/Support-Partition und kann nicht als Host für ein VeraCrypt-Volume verwendet werden.</entry>
+    <entry lang="de" key="MACOSX_APFS_SYSTEM_STORE">Die ausgewählte physische APFS-Speicherpartition '{0}' enthält das derzeit eingebundene macOS-Systemvolume und kann nicht als VeraCrypt-Volume-Host verwendet werden.</entry>
+    <entry lang="de" key="MACOSX_DEVICE_NOT_WRITABLE">macOS meldet, dass das ausgewählte Gerät '{0}' schreibgeschützt ist. Wählen Sie eine beschreibbare physische Partition oder Festplatte aus.</entry>
+    <entry lang="de" key="MACOSX_APFS_EROFS_HINT">macOS hat das ausgewählte Gerät als schreibgeschützt gemeldet. Handelt es sich um eine APFS-Festplatte, stellen Sie sicher, dass Sie die physische APFS-Speicherpartition ausgewählt haben und nicht ein synthetisches APFS-Volume. Identifizieren Sie die physische Partition mit dem Festplatten-Dienstprogramm oder dem Befehl „diskutil list“ und versuchen Sie es dann erneut.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="en" key="TC_INSTALLER_IS_RUNNING">VeraCrypt Installer is currently running on this system and performing or preparing installation or update of VeraCrypt. Before you proceed, please wait for it to finish or close it. If you cannot close it, please restart your computer before proceeding.</entry>
     <entry lang="el" key="INSTALL_FAILED">Η εγκατάσταση απέτυχε.</entry>
     <entry lang="el" key="UNINSTALL_FAILED">Η απεγκατάσταση απέτυχε.</entry>
-    <entry lang="el" key="DIST_PACKAGE_CORRUPTED">Αυτό το πακέτο εγκατάστασης είναι φθαρμένο. Παρακαλώ δοκιμάστε να το κατεβάσετε ξανά (κατά προτίμηση από τον ιστοχώρο του VeraCrypt στη https://www.veracrypt.fr).</entry>
+    <entry lang="el" key="DIST_PACKAGE_CORRUPTED">Αυτό το πακέτο εγκατάστασης είναι φθαρμένο. Παρακαλώ δοκιμάστε να το κατεβάσετε ξανά (κατά προτίμηση από τον ιστοχώρο του VeraCrypt στη https://veracrypt.jp).</entry>
     <entry lang="el" key="CANNOT_WRITE_FILE_X">Αδυναμία εγγραφής αρχείου %s</entry>
     <entry lang="el" key="EXTRACTING_VERB">Εξαγωγή</entry>
     <entry lang="el" key="CANNOT_READ_FROM_PACKAGE">Αδυναμία ανάγνωσης δεδομένων από το πακέτο.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="en" key="HIDDEN_OS_CREATION_PREINFO_HELP">In the next steps, VeraCrypt will create the hidden operating system by copying the content of the system partition to the hidden volume (data being copied will be encrypted on the fly with an encryption key different from the one that will be used for the decoy operating system).\n\nPlease note that the process will be performed in the pre-boot environment (before Windows starts) and it may take a long time to complete; several hours or even several days (depending on the size of the system partition and on the performance of your computer).\n\nYou will be able to interrupt the process, shut down your computer, start the operating system and then resume the process. However, if you interrupt it, the entire process of copying the system will have to start from the beginning (because the content of the system partition must not change during cloning).</entry>
     <entry lang="en" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Do you want to cancel the entire process of creation of the hidden operating system?\n\nNote: You will NOT be able to resume the process if you cancel it now.</entry>
     <entry lang="el" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Θέλετε να ακυρώσετε τον προέλεγχο της κρυπτογράφησης συστήματος;</entry>
-    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="el" key="SYS_DRIVE_NOT_ENCRYPTED">Το διαμέρισμα/οδηγός του συστήματος δε φαίνεται κρυπτογραφημένο (ούτε μερικώς ούτε ολόκληρο).</entry>
     <entry lang="el" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Το διαμέρισμα/οδηγός του συστήματος είναι κρυπτογραφημένο (μερικώς ή ολόκληρο).\n\nΠαρακαλώ αποκρυπτογραφήστε το ολοκληρωτικά πριν συνεχίσετε. Για να το κάνετε αυτό, επιλέξτε 'Σύστημα' &gt; 'Μόνιμη αποκρυπτογράφηση διαμερίσματος/οδηγού συστήματος' από το μενού του κύριου παράθυρου του VeraCrypt.</entry>
     <entry lang="en" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">When the system partition/drive is encrypted (partially or fully), you cannot downgrade VeraCrypt (but you can upgrade it or reinstall the same version).</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>
@@ -1553,7 +1553,7 @@
     <entry lang="en" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Error: The drive uses a sector size other than 512 bytes.\n\nDue to limitations of components available on your platform, partition/device-hosted volumes cannot be created/used on the drive.\n\nPossible solutions:\n- Create a file-hosted volume (container) on the drive.\n- Use a drive with 512-byte sectors.\n- Use VeraCrypt on another platform.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">The host file/device is already in use.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Volume slot unavailable.</entry>
-    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires OSXFUSE 2.5 or above.</entry>
+    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires macFUSE 2.5 or above.</entry>
     <entry lang="en" key="EXCEPTION_OCCURRED">Exception occurred</entry>
     <entry lang="en" key="ENTER_PASSWORD">Enter password</entry>
     <entry lang="en" key="ENTER_TC_VOL_PASSWORD">Enter VeraCrypt Volume Password</entry>
@@ -1644,6 +1644,50 @@
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="es" key="TC_INSTALLER_IS_RUNNING">El Instalador de VeraCrypt ya se está ejecutando en este sistema y está preparando o llevando a cabo la instalación o actualización de VeraCrypt. Antes de continuar, espere a que termine o ciérrelo. Si no puede cerrarlo, reinicie su ordenador antes de continuar.</entry>
     <entry lang="es" key="INSTALL_FAILED">La Instalación falló.</entry>
     <entry lang="es" key="UNINSTALL_FAILED">La Desinstalación falló.</entry>
-    <entry lang="es" key="DIST_PACKAGE_CORRUPTED">Este paquete de distribución está dañado. Intente descargarlo nuevamente (preferentemente desde la página oficial de VeraCrypt en https://www.veracrypt.fr).</entry>
+    <entry lang="es" key="DIST_PACKAGE_CORRUPTED">Este paquete de distribución está dañado. Intente descargarlo nuevamente (preferentemente desde la página oficial de VeraCrypt en https://veracrypt.jp).</entry>
     <entry lang="es" key="CANNOT_WRITE_FILE_X">No se puede escribir el archivo %s</entry>
     <entry lang="es" key="EXTRACTING_VERB">Extrayendo</entry>
     <entry lang="es" key="CANNOT_READ_FROM_PACKAGE">No se puede leer información del paquete.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="es" key="HIDDEN_OS_CREATION_PREINFO_HELP">En los siguientes pasos, VeraCrypt creará el sistema operativo oculto copiando el contenido de la partición del sistema al volumen oculto (los datos que se copien serán cifrados al vuelo con una clave de cifrado diferente de la que se usará para el sistema operativo señuelo).\n\nTenga en cuenta que el proceso se realizará en el entorno de pre-arranque (antes del inicio de Windows) y puede tardar mucho en completarse; varias horas o incluso días (dependiendo del tamaño de la partición del sistema y del rendimiento de su ordenador).\n\nPodrá interrumpir el proceso, apagar su ordenador, iniciar el sistema operativo y luego continuar el proceso. No obstante, si lo interrumpe, el proceso de copiado tendrá que comenzar desde el principio (porque el contenido de la partición del sistema no debe cambiar durante la clonación).</entry>
     <entry lang="es" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">¿Desea cancelar el proceso entero de creación del sistema operativo oculto?\n\nNota: NO podrá continuar el proceso más tarde si lo cancela ahora.</entry>
     <entry lang="es" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">¿Desea cancelar la prueba del cifrado del sistema?</entry>
-    <entry lang="es" key="BOOT_PRETEST_FAILED_RETRY">Ha fallado la prueba del cifrado del sistema VeraCrypt. ¿Desea intentarlo de nuevo?\n\nSi selecciona 'No', el componente de autenticación de pre-arranque será desinstalado.\n\nNotas:\n\n- Si el Cargador de Arranque VeraCrypt no le pidió que introdujera la contraseña antes de que Windows se iniciara, es posible que su sistema operativo no arranque desde la unidad en la que está instalado. Esto no está soportado.\n\n- Si usó un algoritmo de cifrado distinto a AES y la prueba falló (e introdujo la contraseña), la causa puede ser un controlador diseñado inapropiadamente. Seleccione 'No', y trate de cifrar la partición/unidad del sistema otra vez, pero use el algoritmo de cifrado AES (que tiene los requisitos de memoria más bajos).\n\n- Para más causas y soluciones posibles, vea https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="es" key="BOOT_PRETEST_FAILED_RETRY">Ha fallado la prueba del cifrado del sistema VeraCrypt. ¿Desea intentarlo de nuevo?\n\nSi selecciona 'No', el componente de autenticación de pre-arranque será desinstalado.\n\nNotas:\n\n- Si el Cargador de Arranque VeraCrypt no le pidió que introdujera la contraseña antes de que Windows se iniciara, es posible que su sistema operativo no arranque desde la unidad en la que está instalado. Esto no está soportado.\n\n- Si usó un algoritmo de cifrado distinto a AES y la prueba falló (e introdujo la contraseña), la causa puede ser un controlador diseñado inapropiadamente. Seleccione 'No', y trate de cifrar la partición/unidad del sistema otra vez, pero use el algoritmo de cifrado AES (que tiene los requisitos de memoria más bajos).\n\n- Para más causas y soluciones posibles, vea https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="es" key="SYS_DRIVE_NOT_ENCRYPTED">La partición/unidad del sistema no parece estar cifrada (ni parcial ni completamente).</entry>
     <entry lang="es" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Su partición/unidad del sistema está cifrada (parcial o completamente).\n\nDescifre por completo su partición/unidad del sistema antes de continuar. Para ello, seleccione 'Sistema' &gt; 'Descifrar Permanentemente la Partición/Unidad del Sistema' desde el menú de la ventana principal de VeraCrypt.</entry>
     <entry lang="es" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">Si la partición/unidad del sistema está cifrada (parcial o completamente), no puede usar una versión anterior de VeraCrypt (pero puede actualizarlo o reinstalar la misma versión).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="es" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Error: La unidad utiliza un tamaño de sector diferente a 512 bytes.\n\nDebido a las limitaciones de los componentes disponibles en su plataforma, los volúmenes alojados en particiones/dispositivos no se pueden crear/utilizar en la unidad.\n\nPosibles soluciones:\n- Cree un volumen alojado en un archivo (contenedor) en la unidad.\n- Utilice una unidad con sectores de 512 bytes.\n- Utilice VeraCrypt en otra plataforma.</entry>
     <entry lang="es" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">El archivo/dispositivo anfitrión ya está en uso.</entry>
     <entry lang="es" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Ranura de volumen no disponible.</entry>
-    <entry lang="es" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requiere OSXFUSE 2.5 o superior.</entry>
+    <entry lang="es" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requiere macFUSE 2.5 o superior.</entry>
     <entry lang="es" key="EXCEPTION_OCCURRED">Se produjo una excepción</entry>
     <entry lang="es" key="ENTER_PASSWORD">Introducir contraseña</entry>
     <entry lang="es" key="ENTER_TC_VOL_PASSWORD">Introducir contraseña de volumen VeraCrypt</entry>
@@ -1644,6 +1644,50 @@
     <entry lang="es" key="MOUNTPOINT_BLOCKED">ERROR: El punto de montaje del volumen está bloqueado porque sobrescribe un directorio protegido del sistema.\n\nElija un punto de montaje diferente.</entry>
     <entry lang="es" key="MOUNTPOINT_NOTALLOWED">ERROR: No se permite el punto de montaje del volumen porque sobrescribe un directorio que forma parte de la ruta PATH.\n\nElija un punto de montaje diferente.</entry>
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="en" key="TC_INSTALLER_IS_RUNNING">VeraCrypt Installer is currently running on this system and performing or preparing installation or update of VeraCrypt. Before you proceed, please wait for it to finish or close it. If you cannot close it, please restart your computer before proceeding.</entry>
     <entry lang="en" key="INSTALL_FAILED">Installation failed.</entry>
     <entry lang="en" key="UNINSTALL_FAILED">Uninstallation failed.</entry>
-    <entry lang="en" key="DIST_PACKAGE_CORRUPTED">This distribution package is damaged. Please try downloading it again (preferably from the official VeraCrypt website at https://www.veracrypt.fr).</entry>
+    <entry lang="en" key="DIST_PACKAGE_CORRUPTED">This distribution package is damaged. Please try downloading it again (preferably from the official VeraCrypt website at https://veracrypt.jp).</entry>
     <entry lang="en" key="CANNOT_WRITE_FILE_X">Cannot write file %s</entry>
     <entry lang="en" key="EXTRACTING_VERB">Extracting</entry>
     <entry lang="en" key="CANNOT_READ_FROM_PACKAGE">Cannot read data from the package.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="en" key="HIDDEN_OS_CREATION_PREINFO_HELP">In the next steps, VeraCrypt will create the hidden operating system by copying the content of the system partition to the hidden volume (data being copied will be encrypted on the fly with an encryption key different from the one that will be used for the decoy operating system).\n\nPlease note that the process will be performed in the pre-boot environment (before Windows starts) and it may take a long time to complete; several hours or even several days (depending on the size of the system partition and on the performance of your computer).\n\nYou will be able to interrupt the process, shut down your computer, start the operating system and then resume the process. However, if you interrupt it, the entire process of copying the system will have to start from the beginning (because the content of the system partition must not change during cloning).</entry>
     <entry lang="en" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Do you want to cancel the entire process of creation of the hidden operating system?\n\nNote: You will NOT be able to resume the process if you cancel it now.</entry>
     <entry lang="en" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Do you want to cancel the system encryption pretest?</entry>
-    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="en" key="SYS_DRIVE_NOT_ENCRYPTED">The system partition/drive does not appear to be encrypted (neither partially nor fully).</entry>
     <entry lang="en" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Your system partition/drive is encrypted (partially or fully).\n\nPlease decrypt your system partition/drive entirely before proceeding. To do so, select 'System' &gt; 'Permanently Decrypt System Partition/Drive' from the menu bar of the main VeraCrypt window.</entry>
     <entry lang="en" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">When the system partition/drive is encrypted (partially or fully), you cannot downgrade VeraCrypt (but you can upgrade it or reinstall the same version).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="en" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Error: The drive uses a sector size other than 512 bytes.\n\nDue to limitations of components available on your platform, partition/device-hosted volumes cannot be created/used on the drive.\n\nPossible solutions:\n- Create a file-hosted volume (container) on the drive.\n- Use a drive with 512-byte sectors.\n- Use VeraCrypt on another platform.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">The host file/device is already in use.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Volume slot unavailable.</entry>
-    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires OSXFUSE 2.5 or above.</entry>
+    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires macFUSE 2.5 or above.</entry>
     <entry lang="en" key="EXCEPTION_OCCURRED">Exception occurred</entry>
     <entry lang="en" key="ENTER_PASSWORD">Enter password</entry>
     <entry lang="en" key="ENTER_TC_VOL_PASSWORD">Enter VeraCrypt Volume Password</entry>
@@ -1644,6 +1644,50 @@
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="eu" key="TC_INSTALLER_IS_RUNNING">VeraCrypt-en instalatzailea dagoeneko martxan dago sistema honetan instalazio bat egiten edo prestatzen edo VeraCrypt-en eguneraketa batekin. Jarraitu baino lehen, mesedez, bukatzen den arte itxaron ezazu edo itxi ezazu. Ezin baduzu itxi, mesedez, zure ordenagailua berrabiatu ezazu jarraitu baino lehen.</entry>
     <entry lang="eu" key="INSTALL_FAILED">Instalazioak huts egin du.</entry>
     <entry lang="eu" key="UNINSTALL_FAILED">Desinstalazioak huts egin du.</entry>
-    <entry lang="eu" key="DIST_PACKAGE_CORRUPTED">Banaketaren pakete hau hondatuta dago. Mesedez, saiatu zaitez berriro deskargatzen (hobe VeraCrypt-en weborri ofizialetik https://www.veracrypt.fr).</entry>
+    <entry lang="eu" key="DIST_PACKAGE_CORRUPTED">Banaketaren pakete hau hondatuta dago. Mesedez, saiatu zaitez berriro deskargatzen (hobe VeraCrypt-en weborri ofizialetik https://veracrypt.jp).</entry>
     <entry lang="eu" key="CANNOT_WRITE_FILE_X">Ezin da %s fitxategia idatzi</entry>
     <entry lang="eu" key="EXTRACTING_VERB">Ateratzen</entry>
     <entry lang="eu" key="CANNOT_READ_FROM_PACKAGE">Ezin da paketeko informazioa irakurri.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="eu" key="HIDDEN_OS_CREATION_PREINFO_HELP">Hurrengo urratsetan VeraCrypt ezkutuko sistema eragile berria sortuko du sistemaren partizioa ezkutuko bolumenera kopiatuz (kopiatutako datuak segidan zifratuko dira sistema amu bezala dagoen sistema eragileak daukan gako ezberdinarekin).\n\nKontutan izan ezazu prozesu hau hasieraketa aurreko ingurunean (Windows hasi aurretik) egingo dela eta asko iraun dezakela; orduak edo egunak (sistemaren partizioaren tamaina eta ordenagailuaren potentziaren arabera).\n\nProzesua bertan bera uzti ahal izango duzu ordenagailua itzaliz, sistema eragilea hasieratu eta prozesua jarraitu. Hala ere, prozesua mozten baduzu, sistema kopiatzeko prozesu guztia haieratik hasi behar izando da berriro (sistemaren partizioaren edukia ezin daitekeelako aldatu klonatze prozesua martxan dagoenean).</entry>
     <entry lang="eu" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Ezkutuko sistema eragilearen sortzeko prozesua bertan behera utzi nahi al duzu?n\nOharra: Orain uzten baduzu ezingo diozu prozesuari berrekin.</entry>
     <entry lang="eu" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Sistema zifratzeko aurre-azterketa bertan behera utzi nahi al duzu?</entry>
-    <entry lang="eu" key="BOOT_PRETEST_FAILED_RETRY">VeraCrypt-en sistema zifratzeko aurre-azterketak huts egin du. Berriz saiatu nahi duzu?\n\n'Ez' aukeratzen baduzu, hasieraketa aurreko kautotze osagarria desinstalatuko da.\n\nOharrak:\n\n- VeraCrypt Hasieraketa Kargatzaileak ez badizu pasahitzik eskatu Windows hasi aurretik, agian zure sistema eragilea ez da abiatzen instalatuta dagoen unitatetik. Hori ez dago onartua.\n\n- AES ez den zifraketa algoritmo bat erabili baduzu eta aurre-azterketak huts egin badu (eta pasahitza sartu duzu), gaizki diseinatuta dagoen erabiltzaile baten errua izan daiteke. 'Ez' aukeratu ezazu eta sistemaren partizio/unitatea berriz zifratzen saiatu zatez, baina oraingoan AES zifratze algoritmoa erabiliz (zeinek memoria behar baxuenak dituen).\n\n- Zergati eta konponbide gehiago ikusteko: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="eu" key="BOOT_PRETEST_FAILED_RETRY">VeraCrypt-en sistema zifratzeko aurre-azterketak huts egin du. Berriz saiatu nahi duzu?\n\n'Ez' aukeratzen baduzu, hasieraketa aurreko kautotze osagarria desinstalatuko da.\n\nOharrak:\n\n- VeraCrypt Hasieraketa Kargatzaileak ez badizu pasahitzik eskatu Windows hasi aurretik, agian zure sistema eragilea ez da abiatzen instalatuta dagoen unitatetik. Hori ez dago onartua.\n\n- AES ez den zifraketa algoritmo bat erabili baduzu eta aurre-azterketak huts egin badu (eta pasahitza sartu duzu), gaizki diseinatuta dagoen erabiltzaile baten errua izan daiteke. 'Ez' aukeratu ezazu eta sistemaren partizio/unitatea berriz zifratzen saiatu zatez, baina oraingoan AES zifratze algoritmoa erabiliz (zeinek memoria behar baxuenak dituen).\n\n- Zergati eta konponbide gehiago ikusteko: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="eu" key="SYS_DRIVE_NOT_ENCRYPTED">Sistemaren partizioa/unitatea ez dirudi zifratuta dagoenik (ez zati bat, ez guztiz).</entry>
     <entry lang="eu" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Zure sistemaren partizioa/unitatea (zatika edo guztiz) zifratuta dago.\n\nMesedez, sistemaren partizio/unitate osoa argitu jarraitu aurretik. Hori egiteko, 'Sistema' &gt; 'Sistemaren Partizioa/Unitatea Betirako Argitu' aukeratu VeraCrypt lehio nagusiaren menuan.</entry>
     <entry lang="eu" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">Sistemaren partizioa/unitatea (zatika edo guztiz) zifratuta dagoenean, ezin zara VeraCrypt-en bertsio zahar batera aldatu (baina berri bat instalatu edo martxan dagoena berrinstalatu bai).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="en" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Error: The drive uses a sector size other than 512 bytes.\n\nDue to limitations of components available on your platform, partition/device-hosted volumes cannot be created/used on the drive.\n\nPossible solutions:\n- Create a file-hosted volume (container) on the drive.\n- Use a drive with 512-byte sectors.\n- Use VeraCrypt on another platform.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">The host file/device is already in use.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Volume slot unavailable.</entry>
-    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires OSXFUSE 2.5 or above.</entry>
+    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires macFUSE 2.5 or above.</entry>
     <entry lang="en" key="EXCEPTION_OCCURRED">Exception occurred</entry>
     <entry lang="en" key="ENTER_PASSWORD">Enter password</entry>
     <entry lang="en" key="ENTER_TC_VOL_PASSWORD">Enter VeraCrypt Volume Password</entry>
@@ -1644,6 +1644,50 @@
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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" />
@@ -181,7 +181,7 @@
     <entry lang="en" key="IDC_TRAVEL_OPEN_EXPLORER">Open &amp;Explorer window for mounted volume</entry>
     <entry lang="en" key="IDC_TRAV_CACHE_PASSWORDS">&amp;Cache password in driver memory</entry>
     <entry lang="en" key="IDC_TRUECRYPT_MODE">&amp;TrueCrypt Mode</entry>
-    <entry lang="en" key="IDC_UNMOUNTALL">Di&amp;smount All</entry>
+    <entry lang="en" key="IDC_UNMOUNTALL">&amp;Unmount All</entry>
     <entry lang="en" key="IDC_VOLUME_PROPERTIES">&amp;Volume Properties...</entry>
     <entry lang="en" key="IDC_VOLUME_TOOLS">Volume &amp;Tools...</entry>
     <entry lang="en" key="IDC_WIPE_CACHE">&amp;Wipe Cache</entry>
@@ -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>
@@ -855,7 +855,7 @@
     <entry lang="en" key="TC_INSTALLER_IS_RUNNING">VeraCrypt Installer is currently running on this system and performing or preparing installation or update of VeraCrypt. Before you proceed, please wait for it to finish or close it. If you cannot close it, please restart your computer before proceeding.</entry>
     <entry lang="en" key="INSTALL_FAILED">Installation failed.</entry>
     <entry lang="en" key="UNINSTALL_FAILED">Uninstallation failed.</entry>
-    <entry lang="en" key="DIST_PACKAGE_CORRUPTED">This distribution package is damaged. Please try downloading it again (preferably from the official VeraCrypt website at https://www.veracrypt.fr).</entry>
+    <entry lang="en" key="DIST_PACKAGE_CORRUPTED">This distribution package is damaged. Please try downloading it again (preferably from the official VeraCrypt website at https://veracrypt.jp).</entry>
     <entry lang="en" key="CANNOT_WRITE_FILE_X">Cannot write file %s</entry>
     <entry lang="en" key="EXTRACTING_VERB">Extracting</entry>
     <entry lang="en" key="CANNOT_READ_FROM_PACKAGE">Cannot read data from the package.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="en" key="HIDDEN_OS_CREATION_PREINFO_HELP">In the next steps, VeraCrypt will create the hidden operating system by copying the content of the system partition to the hidden volume (data being copied will be encrypted on the fly with an encryption key different from the one that will be used for the decoy operating system).\n\nPlease note that the process will be performed in the pre-boot environment (before Windows starts) and it may take a long time to complete; several hours or even several days (depending on the size of the system partition and on the performance of your computer).\n\nYou will be able to interrupt the process, shut down your computer, start the operating system and then resume the process. However, if you interrupt it, the entire process of copying the system will have to start from the beginning (because the content of the system partition must not change during cloning).</entry>
     <entry lang="en" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Do you want to cancel the entire process of creation of the hidden operating system?\n\nNote: You will NOT be able to resume the process if you cancel it now.</entry>
     <entry lang="en" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Do you want to cancel the system encryption pretest?</entry>
-    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="en" key="SYS_DRIVE_NOT_ENCRYPTED">The system partition/drive does not appear to be encrypted (neither partially nor fully).</entry>
     <entry lang="en" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Your system partition/drive is encrypted (partially or fully).\n\nPlease decrypt your system partition/drive entirely before proceeding. To do so, select 'System' &gt; 'Permanently Decrypt System Partition/Drive' from the menu bar of the main VeraCrypt window.</entry>
     <entry lang="en" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">When the system partition/drive is encrypted (partially or fully), you cannot downgrade VeraCrypt (but you can upgrade it or reinstall the same version).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="en" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Error: The drive uses a sector size other than 512 bytes.\n\nDue to limitations of components available on your platform, partition/device-hosted volumes cannot be created/used on the drive.\n\nPossible solutions:\n- Create a file-hosted volume (container) on the drive.\n- Use a drive with 512-byte sectors.\n- Use VeraCrypt on another platform.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">The host file/device is already in use.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Volume slot unavailable.</entry>
-    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires OSXFUSE 2.5 or above.</entry>
+    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires macFUSE 2.5 or above.</entry>
     <entry lang="en" key="EXCEPTION_OCCURRED">Exception occurred</entry>
     <entry lang="en" key="ENTER_PASSWORD">Enter password</entry>
     <entry lang="en" key="ENTER_TC_VOL_PASSWORD">Enter VeraCrypt Volume Password</entry>
@@ -1644,6 +1644,50 @@
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="fi" key="TC_INSTALLER_IS_RUNNING">VeraCryptin asennusohjelma on juuri käynnissä tässä järjestelmässä ja suorittaa tai valmistelee VeraCryptin asennusta tai päivittämistä. Ennen kuin jatkat, odota sen päättymistä tai sulje se. Jos et voi sulkea sitä, ole hyvä ja käynnistä tietokoneesi uudelleen ennen jatkamista.</entry>
     <entry lang="fi" key="INSTALL_FAILED">Asennus epäonnistui.</entry>
     <entry lang="fi" key="UNINSTALL_FAILED">Asennuksen poisto epäonnistui.</entry>
-    <entry lang="fi" key="DIST_PACKAGE_CORRUPTED">Tämä jaettu paketti on viallinen. Yritä ladata se uudelleen (mieluiten virallisilta VeraCrypt-kotisivuilta osoitteesta https://www.veracrypt.fr).</entry>
+    <entry lang="fi" key="DIST_PACKAGE_CORRUPTED">Tämä jaettu paketti on viallinen. Yritä ladata se uudelleen (mieluiten virallisilta VeraCrypt-kotisivuilta osoitteesta https://veracrypt.jp).</entry>
     <entry lang="fi" key="CANNOT_WRITE_FILE_X">Ei voida kirjoittaa tiedostoa %s</entry>
     <entry lang="fi" key="EXTRACTING_VERB">Puretaan</entry>
     <entry lang="fi" key="CANNOT_READ_FROM_PACKAGE">Datan lukeminen paketista epäonnistui.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="fi" key="HIDDEN_OS_CREATION_PREINFO_HELP">Seuraavassa askeleessa, VeraCrypt-ohjelman luo piilotetun käyttöjärjestelmän kopioimalla järjestelmäosion sisällön piilotetulle taltiolle (kopioitava data salataan lennossa salausavaimella joka eroaa siitä mitä käytetään houkutuslintu käyttöjärjestelmälle).\n\nOle hyvä ja huomioi, että prosessi suorittaa esikäynnistys ympäristössä (ennen kuin Windows käynnistyy) ja sen valmistuminen saattaa kestää kauemmin; useita tunteja tai jopa useita päiviä (riippuen järjestelmäosion koosta ja tietokoneen suorituskyvystä).\n\nSinun on mahdollista keskeyttää prosessin, sulkea tietokone, käynnistää käyttöjärjestelmä ja sitten aloittaa prosessi uudelleen. Kuitenkin, jos keskeytät sen, koko järjestelmän kopiointi prosessi täytyy aloittaa alusta (koska järjestelmäosion sisältö ei saa muuttua kloonauksen aikana).</entry>
     <entry lang="fi" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Haluatko peruuttaa koko piilotetun käyttöjärjestelmän luontitehtävän?\n\nHuomioi: EI ole mahdollista aloittaa tehtävää uudelleen jos keskeytät tehtävän nyt.</entry>
     <entry lang="fi" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Haluatko perua järjestelmän salauksen esitestauksen?</entry>
-    <entry lang="fi" key="BOOT_PRETEST_FAILED_RETRY">VeraCrypt-järjestelmän salaustulos epäonnistui. Haluatko yrittää uudelleen?\n\nJos valitset Ei, esiasennuksen autentikointikomponentti poistetaan.\n\nNotes:\n\n- Jos VeraCryptin Boot Loader ei pyytänyt sinua kirjoittamaan salasanaa ennen kuin Windows käynnistetään, on mahdollista, että käyttöjärjestelmäsi ei käynnisty sen asemasta, johon se on asennettu. Tätä ei tueta.\n\n- Jos käytit salausalgoritmia, joka ei ole AES ja esitesti epäonnistui (ja syötit salasanan), se voi johtua epäasianmukaisesti suunnitellusta ohjaimesta. Valitse 'Ei' ja yritä salaa uudelleen järjestelmäosio/asema, mutta käytä AES-salausalgoritmia (jolla on pienimmät muistivaatimukset).\n\n- Saat lisää syitä ja ratkaisuja, see: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="fi" key="BOOT_PRETEST_FAILED_RETRY">VeraCrypt-järjestelmän salaustulos epäonnistui. Haluatko yrittää uudelleen?\n\nJos valitset Ei, esiasennuksen autentikointikomponentti poistetaan.\n\nNotes:\n\n- Jos VeraCryptin Boot Loader ei pyytänyt sinua kirjoittamaan salasanaa ennen kuin Windows käynnistetään, on mahdollista, että käyttöjärjestelmäsi ei käynnisty sen asemasta, johon se on asennettu. Tätä ei tueta.\n\n- Jos käytit salausalgoritmia, joka ei ole AES ja esitesti epäonnistui (ja syötit salasanan), se voi johtua epäasianmukaisesti suunnitellusta ohjaimesta. Valitse 'Ei' ja yritä salaa uudelleen järjestelmäosio/asema, mutta käytä AES-salausalgoritmia (jolla on pienimmät muistivaatimukset).\n\n- Saat lisää syitä ja ratkaisuja, see: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="fi" key="SYS_DRIVE_NOT_ENCRYPTED">Järjestelmän osio/asema ei ole salattu (ei osittain eikä täysin).</entry>
     <entry lang="fi" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Järjestelmän osio/asema on suojattu (osittain tai täysin).\n\nValitse salauksenpurku järjestelmäosiolle/asemalle pelkästään ennen suoritusta. Tee näin, valitse 'Järjestelmä' &gt; 'Pysyvästi pura järjestelmäosion/aseman salaus' menusta VeraCryptin pääikkunasta.</entry>
     <entry lang="fi" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">Kun järjestelmäosio/asema on salattu (osittain tai täysin), et voi käyttää vanhempaa versiota VeraCrypt-ohjelmasta (mutta voit päivittää sen tai uudelleen asentaa saman version).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="fi" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Virhe: Levy käyttää jotakin muuta sektorikokoa kuin 512 tavua.\n\nAlustallasi saatavilla olevien komponenttien rajoitusten vuoksi, osio- tai laitepohjaisia taltioita ei voida luoda eikä käyttää tällä levyllä.\nMahdollisia ratkaisuja:\n- Luo tiedostopohjainen taltio (säilö) levylle.\n- Käytä levyä jossa on 512 tavun sektorikoko.\n- Käytä VeraCryptiä toisella alustalla.</entry>
     <entry lang="fi" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">Isäntätiedosto/-laite on jo käytössä.</entry>
     <entry lang="fi" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Paikka ei ole käytettävissä.</entry>
-    <entry lang="fi" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt vaatii OSXFUSE 2.5 tai uudemman version.</entry>
+    <entry lang="fi" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt vaatii macFUSE 2.5 tai uudemman version.</entry>
     <entry lang="fi" key="EXCEPTION_OCCURRED">Poikkeus kohdattu</entry>
     <entry lang="fi" key="ENTER_PASSWORD">Anna salasana</entry>
     <entry lang="fi" key="ENTER_TC_VOL_PASSWORD">Anna VeraCrypt-taltion salasana</entry>
@@ -1644,6 +1644,50 @@
     <entry lang="fi" key="MOUNTPOINT_BLOCKED">VIRHE: Taltion liitoskohta on estetty, koska se korvaa suojatun järjestelmäkansion.\n\nValitse toinen liitoskohta.</entry>
     <entry lang="fi" key="MOUNTPOINT_NOTALLOWED">VIRHE: Taltion liitoskohta ei ole sallittu, koska se korvaa PATH-ympäristömuuttujaan kuuluvan sijainnin.\n\nValitse toinen liitoskohta.</entry>
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="fr" key="TC_INSTALLER_IS_RUNNING">L’installeur de VeraCrypt est actuellement exécuté sur votre système et réalise ou prépare l’installation ou la mise à jour de VeraCrypt. Avant de poursuivre, attendez qu’il termine ou se ferme. Si vous ne pouvez pas le fermer, redémarrez votre ordinateur avant de poursuivre.</entry>
     <entry lang="fr" key="INSTALL_FAILED">L’installation a échoué.</entry>
     <entry lang="fr" key="UNINSTALL_FAILED">La désinstallation a échoué.</entry>
-    <entry lang="fr" key="DIST_PACKAGE_CORRUPTED">Ce package est endommagé. Essayez de le télécharger à nouveau (de préférence à partir du site web officiel de VeraCrypt à l’URL https://www.veracrypt.fr).</entry>
+    <entry lang="fr" key="DIST_PACKAGE_CORRUPTED">Ce package est endommagé. Essayez de le télécharger à nouveau (de préférence à partir du site web officiel de VeraCrypt à l’URL https://veracrypt.jp).</entry>
     <entry lang="fr" key="CANNOT_WRITE_FILE_X">Impossible d’écrire dans le fichier %s</entry>
     <entry lang="fr" key="EXTRACTING_VERB">Extraction de</entry>
     <entry lang="fr" key="CANNOT_READ_FROM_PACKAGE">Impossible de lire les données du package.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="fr" key="HIDDEN_OS_CREATION_PREINFO_HELP">Dans les prochaines étapes, VeraCrypt va créer le système d’exploitation caché en copiant le contenu de la partition système sur le volume caché (les données à copier à la volée seront chiffrées avec une clé de chiffrement différente de celle qui sera utilisée pour le système d’exploitation leurre).\n\nVeuillez noter que le processus sera effectué dans l’environnement de préamorçage (avant le démarrage de Windows) et cela peut prendre beaucoup de temps, plusieurs heures ou même plusieurs jours (selon la taille de la partition système et les performances de votre ordinateur).\n\nVous serez en mesure d’interrompre le processus, arrêtez l’ordinateur, démarrez le système d’exploitation et ensuite reprendre le processus. Toutefois, si vous l’interrompez, tout le processus de copie du système devra recommencer depuis le début (parce que le contenu de la partition système ne doit pas changer lors du clonage).</entry>
     <entry lang="fr" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Voulez-vous annuler l’intégralité du processus de création du système d’exploitation caché ?\n\nNote : Vous ne pourrez PAS reprendre le processus si vous l’annulez maintenant.</entry>
     <entry lang="fr" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Voulez-vous annuler le pré-test de chiffrement du système ?</entry>
-    <entry lang="fr" key="BOOT_PRETEST_FAILED_RETRY">Le prétest de chiffrement du système VeraCrypt a échoué. Voulez-vous réessayer ?\n\nSi vous sélectionnez « Non », le composant d’authentification de préamorçage sera désinstallé.\n\nRemarques :\n\n- Si le chargeur de démarrage de VeraCrypt n’a pas demandé d’entrer le mot de passe avant que Windows a commencé à démarrer, il est possible que votre système d’exploitation ne démarre pas depuis le disque sur lequel il est installé. Ceci n’est pas supporté.\\n\n- Si vous avez utilisé un algorithme de chiffrement autre que de l’AES et que le prétest a échoué (et vous avez entré le mot de passe), cela peut avoir été causé par un pilote mal conçu. Sélectionnez « Non » et essayer de chiffrer la partition/lecteur système à nouveau, mais utilisez l’algorithme de chiffrement AES (qui a le plus bas niveau d’exigences).\n\n- Pour plus de détails sur les causes et les solutions, voir : https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="fr" key="BOOT_PRETEST_FAILED_RETRY">Le prétest de chiffrement du système VeraCrypt a échoué. Voulez-vous réessayer ?\n\nSi vous sélectionnez « Non », le composant d’authentification de préamorçage sera désinstallé.\n\nRemarques :\n\n- Si le chargeur de démarrage de VeraCrypt n’a pas demandé d’entrer le mot de passe avant que Windows a commencé à démarrer, il est possible que votre système d’exploitation ne démarre pas depuis le disque sur lequel il est installé. Ceci n’est pas supporté.\\n\n- Si vous avez utilisé un algorithme de chiffrement autre que de l’AES et que le prétest a échoué (et vous avez entré le mot de passe), cela peut avoir été causé par un pilote mal conçu. Sélectionnez « Non » et essayer de chiffrer la partition/lecteur système à nouveau, mais utilisez l’algorithme de chiffrement AES (qui a le plus bas niveau d’exigences).\n\n- Pour plus de détails sur les causes et les solutions, voir : https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="fr" key="SYS_DRIVE_NOT_ENCRYPTED">La partition/le disque système ne semble pas chiffré (totalement ou en partie).</entry>
     <entry lang="fr" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Votre partition/votre disque système est chiffré (totalement ou en partie).\n\nDéchiffrez votre partition/votre disque système entièrement avant de poursuivre. Pour cela sélectionnez ’Système’ &gt; ’Déchiffrer définitivement la partition/le disque système’ depuis la barre des menus de la fenêtre principale VeraCrypt.</entry>
     <entry lang="fr" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">Lorsque la partition/lecteur système est chiffré (partiellement ou totalement), vous ne pouvez pas rétrograder VeraCrypt (mais vous pouvez le mettre à jour ou réinstaller la même version).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="fr" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Erreur : Le disque utilise une taille de secteur autre que 512 octets.\n\nEn raison des limitations des composants disponibles sur votre plateforme, les volumes hébergés sur une partition ou un périphérique ne peuvent pas être créés/utilisés sur ce disque.\n\nSolutions possibles :\n- Créez un volume hébergé dans un fichier (conteneur) sur le disque.\n- Utilisez un disque avec des secteurs de 512 octets.\n- Utilisez VeraCrypt sur une autre plateforme.</entry>
     <entry lang="fr" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">Le fichier/périphérique hôte est déjà utilisé.</entry>
     <entry lang="fr" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">L'emplacement du volume est indisponible.</entry>
-    <entry lang="fr" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt nécessite OSXFUSE 2.5 ou une version ultérieure.</entry>
+    <entry lang="fr" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt nécessite macFUSE 2.5 ou une version ultérieure.</entry>
     <entry lang="fr" key="EXCEPTION_OCCURRED">Une exception s'est produite</entry>
     <entry lang="fr" key="ENTER_PASSWORD">Entrez le mot de passe</entry>
     <entry lang="fr" key="ENTER_TC_VOL_PASSWORD">Entrez le mot de passe du volume VeraCrypt</entry>
@@ -1644,6 +1644,50 @@
     <entry lang="fr" key="MOUNTPOINT_BLOCKED">ERREUR : Le point de montage du volume est bloqué car il remplace un répertoire système protégé.\n\nVeuillez choisir un autre point de montage.</entry>
     <entry lang="fr" key="MOUNTPOINT_NOTALLOWED">ERREUR : Le point de montage du volume n'est pas autorisé car il remplace un répertoire faisant partie de la variable d'environnement PATH.\n\nVeuillez choisir un autre point de montage.</entry>
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="he" key="TC_INSTALLER_IS_RUNNING">VeraCrypt Installer פועל כעת במערכת זו ומבצע או מכין התקנה או עדכון של VeraCrypt.לפני שתמשיך, אנא המתן עד שיסיים או יסגור אותו.אם אינך יכול לסגור אותו, הפעל מחדש את המחשב לפני שתמשיך.</entry>
     <entry lang="he" key="INSTALL_FAILED">ההתקנה נכשלה.</entry>
     <entry lang="he" key="UNINSTALL_FAILED">ההתקנה נכשלה.</entry>
-    <entry lang="he" key="DIST_PACKAGE_CORRUPTED">חבילת הפצה זו נפגעה. נסה להוריד אותה שוב (רצוי מהאתר הרשמי של VeraCrypt בכתובת https://www.veracrypt.fr).</entry>
+    <entry lang="he" key="DIST_PACKAGE_CORRUPTED">חבילת הפצה זו נפגעה. נסה להוריד אותה שוב (רצוי מהאתר הרשמי של VeraCrypt בכתובת https://veracrypt.jp).</entry>
     <entry lang="he" key="CANNOT_WRITE_FILE_X">לא ניתן לכתוב את הקובץ %s</entry>
     <entry lang="he" key="EXTRACTING_VERB">חילוץ</entry>
     <entry lang="he" key="CANNOT_READ_FROM_PACKAGE">לא ניתן לקרוא נתונים מהחבילה.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="he" key="HIDDEN_OS_CREATION_PREINFO_HELP">בשלבים הבאים VeraCrypt תיצור את מערכת ההפעלה הנסתרת על ידי העתקת תוכן מחיצת המערכת לאמצעי אחסון הנסתר (הנתונים המועתקים יוצפנו על ידי תנועה עם מפתח הצפנה שונה מזה שישמש להפעלת הפיתוימערכת). \n \n שים לב שהתהליך יבוצע בסביבת טרום האתחול (לפני הפעלת Windows) וייתכן שיימשך זמן רב עד להשלמתו;מספר שעות או אפילו מספר ימים (תלוי בגודל מחיצת המערכת ובביצועי המחשב שלך). \n \n תוכל להפריע לתהליך, לכבות את המחשב, להפעיל את מערכת ההפעלה ואז לחדש את התהליך.עם זאת, אם תפריע לה, כל תהליך ההעתקה של המערכת יצטרך להתחיל מההתחלה (מכיוון שהתוכן של מחיצת המערכת לא יכול להשתנות במהלך השיבוט).</entry>
     <entry lang="he" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">האם ברצונך לבטל את כל תהליך היצירה של מערכת ההפעלה הנסתרת? \n \n הערה: לא תוכל לחדש את התהליך אם תבטל אותו כעת.</entry>
     <entry lang="he" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">האם ברצונך לבטל את הצפנת המערכת לפני כן?</entry>
-    <entry lang="he" key="BOOT_PRETEST_FAILED_RETRY">בדיקת ההצפנה של מערכת VeraCrypt נכשל.האם ברצונך לנסות שוב? \n \n אם תבחר &amp;apos;לא&amp;apos;, יוסר הסרת התקנה של רכיב האימות לפני האתחול. \n \n הערות: \n \n- אם מטען האתחול של VeraCrypt לא ביקש ממך להזין את הסיסמה.לפני תחילת Windows, ייתכן שמערכת ההפעלה שלך לא אתחול מהכונן עליו היא מותקנת.זה לא נתמך. \n \n- אם השתמשת באלגוריתם הצפנה שאינו AES והבדיקה המוקדמת נכשלה (והזנת את הסיסמה), ייתכן שהיא נגרמה על ידי מנהל התקן שאינו מתאים.בחר &amp;apos;לא&amp;apos;, ונסה להצפין שוב את מחיצת המערכת / כונן, אך השתמש באלגוריתם ההצפנה AES (בעל דרישות הזיכרון הנמוכות ביותר). \n \n- לקבלת סיבות ופתרונות אפשריים נוספים, ראה: https: // www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="he" key="BOOT_PRETEST_FAILED_RETRY">בדיקת ההצפנה של מערכת VeraCrypt נכשל.האם ברצונך לנסות שוב? \n \n אם תבחר &amp;apos;לא&amp;apos;, יוסר הסרת התקנה של רכיב האימות לפני האתחול. \n \n הערות: \n \n- אם מטען האתחול של VeraCrypt לא ביקש ממך להזין את הסיסמה.לפני תחילת Windows, ייתכן שמערכת ההפעלה שלך לא אתחול מהכונן עליו היא מותקנת.זה לא נתמך. \n \n- אם השתמשת באלגוריתם הצפנה שאינו AES והבדיקה המוקדמת נכשלה (והזנת את הסיסמה), ייתכן שהיא נגרמה על ידי מנהל התקן שאינו מתאים.בחר &amp;apos;לא&amp;apos;, ונסה להצפין שוב את מחיצת המערכת / כונן, אך השתמש באלגוריתם ההצפנה AES (בעל דרישות הזיכרון הנמוכות ביותר). \n \n- לקבלת סיבות ופתרונות אפשריים נוספים, ראה: https: // veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="he" key="SYS_DRIVE_NOT_ENCRYPTED">מחיצת המערכת / כונן המערכת לא נראה מוצפן (לא באופן חלקי ולא מלא).</entry>
     <entry lang="he" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">מחיצת / כונן המערכת שלך מוצפנת (חלקית או מלאה). \n \n אנא פענח את מחיצת המערכת / כונן לחלוטין לפני שתמשיך.לשם כך בחר &amp;apos;מערכת&amp;apos;&gt; &amp;apos;פענוח מחיצת מערכת / כונן לצמיתות&amp;apos; משורת התפריטים של חלון VeraCrypt הראשי.</entry>
     <entry lang="he" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">כאשר מחיצת המערכת / כונן מוצפן (באופן חלקי או מלא), אינך יכול לשדרג לאחור את VeraCrypt (אך תוכל לשדרג אותו או להתקין מחדש את אותה גירסה).</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>
@@ -1524,7 +1523,7 @@
     <entry lang="he" key="LINUX_NOT_SUPPORTED">(לא נתמך על ידי רכיבים הזמינים בפלטפורמה זו). \n</entry>
     <entry lang="he" key="LINUX_KERNEL_OLD">המערכת שלך משתמשת בגרסה ישנה של ליבת לינוקס. \n \n בשל באג בליבת הלינוקס, המערכת שלך עשויה להפסיק להגיב בעת כתיבת נתונים לאמצעי אחסון VeraCrypt.ניתן לפתור בעיה זו על ידי שדרוג הגרעין לגרסה 2.6.24 ואילך.</entry>
     <entry lang="he" key="LINUX_VOL_UNMOUNTED">אמצעי האחסון {0} הוסר.</entry>
-    <entry lang="en" key="LINUX_VOL_MOUNTED">Volume {0} has been mounted.</entry>
+    <entry lang="he" key="LINUX_VOL_MOUNTED">אמצעי האחסון {0} הותקן.</entry>
     <entry lang="he" key="LINUX_OOM">מתוך הזיכרון.</entry>
     <entry lang="he" key="LINUX_CANT_GET_ADMIN_PRIV">השגת הרשאות מנהל נכשלה</entry>
     <entry lang="he" key="LINUX_COMMAND_GET_ERROR">הפקודה {0} החזירה שגיאה {1}.</entry>
@@ -1554,7 +1553,7 @@
     <entry lang="he" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">שגיאה: הכונן משתמש בגודל מגזר שאינו 512 בתים. \n \n בשל מגבלות של רכיבים הזמינים בפלטפורמה שלך, לא ניתן ליצור / להשתמש בכמויות מחיצות / התקנים בכונן. \n \n פתרונות אפשריים: \n-צור אמצעי אחסון מתארח (מיכל) בכונן. \n - השתמש בכונן עם מגזרים של 512 בתים. \n - השתמש ב- VeraCrypt בפלטפורמה אחרת.</entry>
     <entry lang="he" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">הקובץ / ההתקן המארח כבר נמצא בשימוש.</entry>
     <entry lang="he" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">חריץ אמצעי האחסון אינו זמין.</entry>
-    <entry lang="he" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt דורש OSXFUSE 2.5 ומעלה.</entry>
+    <entry lang="he" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt דורש macFUSE 2.5 ומעלה.</entry>
     <entry lang="he" key="EXCEPTION_OCCURRED">אירעה שגיאה</entry>
     <entry lang="he" key="ENTER_PASSWORD">הזן את הסיסמה</entry>
     <entry lang="he" key="ENTER_TC_VOL_PASSWORD">הזן את סיסמת אמצעי האחסון של VeraCrypt</entry>
@@ -1569,82 +1568,126 @@
     <entry lang="he" key="UNKNOWN_OPTION">אפשרות לא ידועה</entry>
     <entry lang="he" key="VOLUME_LOCATION">מיקום אמצעי אחסון</entry>
     <entry lang="he" key="VOLUME_HOST_IN_USE">אזהרה: הקובץ / ההתקן המארח {0} כבר נמצא בשימוש! \n \n התעלמות מכך עלולה לגרום לתוצאות לא רצויות כולל חוסר יציבות במערכת.יש לסגור את כל היישומים שעשויים להשתמש בקובץ המארח / בהתקן לפני התקנת אמצעי האחסון. \n \n האם להמשיך בטעינה?</entry>
-    <entry lang="en" key="CANT_INSTALL_WITH_EXE_OVER_MSI">VeraCrypt was previously installed using an MSI package and so it can't be updated using the standard installer.\n\nPlease use the MSI package to update your VeraCrypt installation.</entry>
-    <entry lang="en" key="IDC_USE_ALL_FREE_SPACE">Use all available free space</entry>
-    <entry lang="en" key="SYS_ENCRYPTION_UPGRADE_UNSUPPORTED_ALGORITHM">VeraCrypt cannot be upgraded because the system partition/drive was encrypted using an algorithm that is not supported anymore.\nPlease decrypt your system before upgrading VeraCrypt and then encrypt it again.</entry>
-    <entry lang="en" key="LINUX_EX2MSG_TERMINALNOTFOUND">Supported terminal application could not be found, you need either xterm, konsole or gnome-terminal (with dbus-x11).</entry>
-    <entry lang="en" key="IDM_MOUNT_NO_CACHE">Mount Without Cache</entry>
-    <entry lang="en" key="EXPANDER_INFO">:: VeraCrypt Expander ::\n\nExpand a VeraCrypt volume on the fly without reformatting\n\n\nAll kind of volumes (container files, disks and partitions) formatted with NTFS are supported. The only condition is that there must be enough free space on the host drive or host device of the VeraCrypt volume.\n\nDo not use this software to expand an outer volume containing a hidden volume, because this destroys the hidden volume!\n</entry>
-    <entry lang="en" key="IDC_STEPSEXPAND">1. Select the VeraCrypt volume to be expanded\n2. Click the 'Mount' button</entry>
-    <entry lang="en" key="IDT_VOL_NAME">Volume: </entry>
-    <entry lang="en" key="IDT_FILE_SYS">File system: </entry>
-    <entry lang="en" key="IDT_CURRENT_SIZE">Current size: </entry>
-    <entry lang="en" key="IDT_NEW_SIZE">New size: </entry>
-    <entry lang="en" key="IDT_NEW_SIZE_BOX_TITLE">Enter new volume size</entry>
-    <entry lang="en" key="IDC_INIT_NEWSPACE">Fill new space with random data</entry>
-    <entry lang="en" key="IDC_QUICKEXPAND">Quick Expand</entry>
-    <entry lang="en" key="IDT_INIT_SPACE">Fill new space: </entry>
-    <entry lang="en" key="EXPANDER_FREE_SPACE">%s free space available on host drive</entry>
-    <entry lang="en" key="EXPANDER_HELP_DEVICE">This is a device-based VeraCrypt volume.\n\nThe new volume size will be choosen automatically as the size of the host device.</entry>
-    <entry lang="en" key="EXPANDER_HELP_FILE">Please specify the new size of the VeraCrypt volume (must be at least %I64u KB larger than the current size).</entry>
-    <entry lang="en" key="QUICK_EXPAND_WARNING">WARNING: You should use Quick Expand only in the following cases:\n\n1) The device where the file container is located contains no sensitive data and you do not need plausible deniability.\n2) The device where the file container is located has already been securely and fully encrypted.\n\nAre you sure you want to use Quick Expand?</entry>
-    <entry lang="en" key="EXPANDER_STATUS_TEXT">IMPORTANT: Move your mouse as randomly as possible within this window. The longer you move it, the better. This significantly increases the cryptographic strength of the encryption keys. Then click 'Continue' to expand the volume.</entry>
-    <entry lang="en" key="EXPANDER_STATUS_TEXT_LEGACY">Click 'Continue' to expand the volume.</entry>
-    <entry lang="en" key="EXPANDER_FINISH_ERROR">Error: volume expansion failed.</entry>
-    <entry lang="en" key="EXPANDER_FINISH_ABORT">Error: operation aborted by user.</entry>
-    <entry lang="en" key="EXPANDER_FINISH_OK">Finished. Volume successfully expanded.</entry>
-    <entry lang="en" key="EXPANDER_CANCEL_WARNING">Warning: Volume expansion is in progress!\n\nStopping now may result in a damaged volume.\n\nDo you really want to cancel?</entry>
-    <entry lang="en" key="EXPANDER_STARTING_STATUS">Starting volume expansion ...\n</entry>
-    <entry lang="en" key="EXPANDER_HIDDEN_VOLUME_ERROR">An outer volume containing a hidden volume can't be expanded, because this destroys the hidden volume.\n</entry>
-    <entry lang="en" key="EXPANDER_SYSTEM_VOLUME_ERROR">A VeraCrypt system volume can't be expanded.</entry>
-    <entry lang="en" key="EXPANDER_NO_FREE_SPACE">Not enough free space to expand the volume</entry>
-    <entry lang="en" key="EXPANDER_WARNING_FILE_CONTAINER_JUNK">Warning: The container file is larger than the VeraCrypt volume area. The data after the VeraCrypt volume area will be overwritten.\n\nDo you want to continue?</entry>
-    <entry lang="en" key="EXPANDER_WARNING_FAT">Warning: The VeraCrypt volume contains a FAT file system!\n\nOnly the VeraCrypt volume itself will be expanded, but not the file system.\n\nDo you want to continue?</entry>
-    <entry lang="en" key="EXPANDER_WARNING_EXFAT">Warning: The VeraCrypt volume contains an exFAT file system!\n\nOnly the VeraCrypt volume itself will be expanded, but not the file system.\n\nDo you want to continue?</entry>
-    <entry lang="en" key="EXPANDER_WARNING_UNKNOWN_FS">Warning: The VeraCrypt volume contains an unknown or no file system!\n\nOnly the VeraCrypt volume itself will be expanded, the file system remains unchanged.\n\nDo you want to continue?</entry>
-    <entry lang="en" key="EXPANDER_ERROR_VOLUME_SIZE_TOO_SMALL">New volume size too small, must be at least %I64u kB larger than the current size.</entry>
-    <entry lang="en" key="EXPANDER_ERROR_VOLUME_SIZE_TOO_LARGE">New volume size too large, not enough space on host drive.</entry>
-    <entry lang="en" key="EXPANDER_ERROR_MAX_FILE_SIZE_EXCEEDED">Maximum file size of %I64u MB on host drive exceeded.</entry>
-    <entry lang="en" key="EXPANDER_ERROR_QUICKEXPAND_PRIVILEGES">Error: Failed to get necessary privileges to enable Quick Expand!\nPlease uncheck Quick Expand option and try again.</entry>
-    <entry lang="en" key="EXPANDER_ERROR_MAX_VC_VOLUME_SIZE_EXCEEDED">Maximum VeraCrypt volume size of %I64u TB exceeded!\n</entry>
-    <entry lang="en" key="FULL_FORMAT">Full Format</entry>
-    <entry lang="en" key="FAST_CREATE">Fast Create</entry>
-    <entry lang="en" key="WARN_FAST_CREATE">WARNING: You should use Fast Create only in the following cases:\n\n1) The device contains no sensitive data and you do not need plausible deniability.\n2) The device has already been securely and fully encrypted.\n\nAre you sure you want to use Fast Create?</entry>
-    <entry lang="en" key="IDC_ENABLE_EMV_SUPPORT">Enable EMV Support</entry>
-    <entry lang="en" key="COMMAND_APDU_INVALID">The APDU command sent to the card is not valid.</entry>
-    <entry lang="en" key="EXTENDED_APDU_UNSUPPORTED">Extended APDU commands cannot be used with the current token.</entry>
-    <entry lang="en" key="SCARD_MODULE_INIT_FAILED">Error when loading the WinSCard / PCSC library.</entry>
-    <entry lang="en" key="EMV_UNKNOWN_CARD_TYPE">The card in the reader is not a supported EMV card.</entry>
-    <entry lang="en" key="EMV_SELECT_AID_FAILED">The AID of the card in the reader could not be selected.</entry>
-    <entry lang="en" key="EMV_ICC_CERT_NOTFOUND">ICC Public Key Certificate was not found in the card.</entry>
-    <entry lang="en" key="EMV_ISSUER_CERT_NOTFOUND">Issuer Public Key Certificate was not found in the card.</entry>
-    <entry lang="en" key="EMV_CPLC_NOTFOUND">CPLC was not found in the EMV card.</entry>
-    <entry lang="en" key="EMV_PAN_NOTFOUND">No Primary Account Number (PAN) found in the EMV card.</entry>
-    <entry lang="en" key="INVALID_EMV_PATH">EMV path is invalid.</entry>
-    <entry lang="en" key="EMV_KEYFILE_DATA_NOTFOUND">Unable to build a keyfile from the EMV card's data.\n\nOne of the following is missing:\n- ICC Public Key Certificate.\n- Issuer Public Key Certificate.\n- CPLC data.</entry>
-    <entry lang="en" key="SCARD_W_REMOVED_CARD">No card in the reader.\n\nPlease make sure the card is correctly slotted.</entry>
-    <entry lang="en" key="FORMAT_EXTERNAL_FAILED">Windows format.com command failed to format the volume as NTFS/exFAT/ReFS: Error 0x%.8X.\n\nFalling back to using Windows FormatEx API.</entry>
-    <entry lang="en" key="FORMATEX_API_FAILED">Windows FormatEx API failed to format the volume as NTFS/exFAT/ReFS.\n\nFailure status = %s.</entry>
-    <entry lang="en" key="EXPANDER_WRITING_RANDOM_DATA">Writing random data to new space ...\n</entry>
-    <entry lang="en" key="EXPANDER_WRITING_ENCRYPTED_BACKUP">Writing re-encrypted backup header ...\n</entry>
-    <entry lang="en" key="EXPANDER_WRITING_ENCRYPTED_PRIMARY">Writing re-encrypted primary header ...\n</entry>
-    <entry lang="en" key="EXPANDER_WIPING_OLD_HEADER">Wiping old backup header ...\n</entry>
-    <entry lang="en" key="EXPANDER_MOUNTING_VOLUME">Mounting volume ...\n</entry>
-    <entry lang="en" key="EXPANDER_UNMOUNTING_VOLUME">Unmounting volume ...\n</entry>
-    <entry lang="en" key="EXPANDER_EXTENDING_FILESYSTEM">Extending file system ...\n</entry>
-    <entry lang="en" key="PARTIAL_SYSENC_MOUNT_READONLY">Warning: The system partition you attempted to mount was not fully encrypted. As a safety measure to prevent potential corruption or unwanted modifications, volume '%s' was mounted as read-only.</entry>
-    <entry lang="en" key="IDC_LINK_KEYFILES_EXTENSIONS_WARNING">Important information on using third-party file extensions</entry>
-    <entry lang="en" key="IDC_DISABLE_MEMORY_PROTECTION">Disable memory protection for Accessibility tools compatibility</entry>
-    <entry lang="en" key="DISABLE_MEMORY_PROTECTION_WARNING">WARNING: Disabling memory protection significantly reduces security. Enable this option ONLY if you rely on Accessibility tools, like Screen Readers, to interact with VeraCrypt's UI.</entry>
+    <entry lang="he" key="CANT_INSTALL_WITH_EXE_OVER_MSI">VeraCrypt הותקן בעבר באמצעות חבילת MSI ולכן לא ניתן לעדכן אותו באמצעות מתקין רגיל.\n\nאנא השתמש בחבילת MSI כדי לעדכן את התקנת VeraCrypt שלך.</entry>
+    <entry lang="he" key="IDC_USE_ALL_FREE_SPACE">השתמש בכל השטח הפנוי</entry>
+    <entry lang="he" key="SYS_ENCRYPTION_UPGRADE_UNSUPPORTED_ALGORITHM">לא ניתן לשדרג את VeraCrypt מאחר שמחיצת/כונן המערכת הוצפן באלגוריתם שאינו נתמך עוד.\nאנא פענח את המערכת שלך לפני שדרוג VeraCrypt ואז הצפן אותה מחדש.</entry>
+    <entry lang="he" key="LINUX_EX2MSG_TERMINALNOTFOUND">לא נמצאה אפליקציית מסוף נתמכת; נדרש אחד מהבאים: xterm, konsole או gnome-terminal (עם dbus-x11).</entry>
+    <entry lang="he" key="IDM_MOUNT_NO_CACHE">טעינה ללא מטמון</entry>
+    <entry lang="he" key="EXPANDER_INFO">:: מרחיב VeraCrypt ::\n\nהרחב אמצעי אחסון של VeraCrypt באופן מיידי ללא פירמוט מחדש\n\n\nכל סוגי אמצעי האחסון (קבצי מיכל, דיסקים ומחיצות) המפורמטים עם NTFS נתמכים. התנאי היחיד הוא שחייב להיות מספיק שטח פנוי בכונן המארח או בהתקן המארח של אמצעי האחסון של VeraCrypt.\n\nאין להשתמש בתוכנה זו להרחבת אמצעי אחסון חיצוני המכיל אמצעי אחסון מוסתר, כיוון שפעולה זו תשמיד את אמצעי האחסון המוסתר!\n</entry>
+    <entry lang="he" key="IDC_STEPSEXPAND">1. בחר את אמצעי האחסון של VeraCrypt להרחבה\n2. לחץ על כפתור 'טען'</entry>
+    <entry lang="he" key="IDT_VOL_NAME">אמצעי אחסון: </entry>
+    <entry lang="he" key="IDT_FILE_SYS">מערכת קבצים: </entry>
+    <entry lang="he" key="IDT_CURRENT_SIZE">גודל נוכחי: </entry>
+    <entry lang="he" key="IDT_NEW_SIZE">גודל חדש: </entry>
+    <entry lang="he" key="IDT_NEW_SIZE_BOX_TITLE">הזן גודל חדש לאמצעי האחסון</entry>
+    <entry lang="he" key="IDC_INIT_NEWSPACE">מלא את השטח החדש בנתונים אקראיים</entry>
+    <entry lang="he" key="IDC_QUICKEXPAND">הרחבה מהירה</entry>
+    <entry lang="he" key="IDT_INIT_SPACE">מלא שטח חדש: </entry>
+    <entry lang="he" key="EXPANDER_FREE_SPACE">%s שטח פנוי זמין בכונן המארח</entry>
+    <entry lang="he" key="EXPANDER_HELP_DEVICE">זהו אמצעי אחסון VeraCrypt מבוסס התקן.\n\nגודל אמצעי האחסון החדש ייבחר אוטומטית כגודל ההתקן המארח.</entry>
+    <entry lang="he" key="EXPANDER_HELP_FILE">אנא ציין את הגודל החדש של אמצעי האחסון של VeraCrypt (חייב להיות גדול לפחות ב-%I64u ק"ב מהגודל הנוכחי).</entry>
+    <entry lang="he" key="QUICK_EXPAND_WARNING">אזהרה: עליך להשתמש בהרחבה מהירה רק במקרים הבאים:\n\n1) ההתקן שבו נמצא קובץ המיכל אינו מכיל נתונים רגישים ואינך זקוק להכחשה סבירה.\n2) ההתקן שבו נמצא קובץ המיכל כבר הוצפן באופן מאובטח ומלא.\n\nהאם אתה בטוח שברצונך להשתמש בהרחבה מהירה?</entry>
+    <entry lang="he" key="EXPANDER_STATUS_TEXT">חשוב: הזז את העכבר באופן אקראי ככל האפשר בתוך חלון זה. ככל שתזיז אותו זמן רב יותר, כך ייטב. הדבר מגדיל משמעותית את החוזק הקריפטוגרפי של מפתחות ההצפנה. לאחר מכן לחץ על 'המשך' כדי להרחיב את אמצעי האחסון.</entry>
+    <entry lang="he" key="EXPANDER_STATUS_TEXT_LEGACY">לחץ על 'המשך' כדי להרחיב את אמצעי האחסון.</entry>
+    <entry lang="he" key="EXPANDER_FINISH_ERROR">שגיאה: הרחבת אמצעי האחסון נכשלה.</entry>
+    <entry lang="he" key="EXPANDER_FINISH_ABORT">שגיאה: הפעולה בוטלה על ידי המשתמש.</entry>
+    <entry lang="he" key="EXPANDER_FINISH_OK">הסתיים. אמצעי האחסון הורחב בהצלחה.</entry>
+    <entry lang="he" key="EXPANDER_CANCEL_WARNING">אזהרה: הרחבת אמצעי האחסון מתבצעת!\n\nעצירה כעת עלולה לגרום נזק לאמצעי האחסון.\n\nהאם אתה באמת רוצה לבטל?</entry>
+    <entry lang="he" key="EXPANDER_STARTING_STATUS">מתחיל הרחבת אמצעי אחסון...\n</entry>
+    <entry lang="he" key="EXPANDER_HIDDEN_VOLUME_ERROR">לא ניתן להרחיב אמצעי אחסון חיצוני המכיל אמצעי אחסון מוסתר, מכיוון שפעולה זו תשמיד את אמצעי האחסון המוסתר.\n</entry>
+    <entry lang="he" key="EXPANDER_SYSTEM_VOLUME_ERROR">לא ניתן להרחיב אמצעי אחסון מערכת של VeraCrypt.</entry>
+    <entry lang="he" key="EXPANDER_NO_FREE_SPACE">אין מספיק שטח פנוי להרחבת אמצעי האחסון</entry>
+    <entry lang="he" key="EXPANDER_WARNING_FILE_CONTAINER_JUNK">אזהרה: קובץ המיכל גדול יותר מאזור אמצעי האחסון של VeraCrypt. הנתונים שאחרי אזור אמצעי האחסון של VeraCrypt יידרסו.\n\nהאם ברצונך להמשיך?</entry>
+    <entry lang="he" key="EXPANDER_WARNING_FAT">אזהרה: אמצעי האחסון של VeraCrypt מכיל מערכת קבצים FAT!\n\nרק אמצעי האחסון של VeraCrypt עצמו יורחב, אך לא מערכת הקבצים.\n\nהאם ברצונך להמשיך?</entry>
+    <entry lang="he" key="EXPANDER_WARNING_EXFAT">אזהרה: אמצעי האחסון של VeraCrypt מכיל מערכת קבצים exFAT!\n\nרק אמצעי האחסון של VeraCrypt עצמו יורחב, אך לא מערכת הקבצים.\n\nהאם ברצונך להמשיך?</entry>
+    <entry lang="he" key="EXPANDER_WARNING_UNKNOWN_FS">אזהרה: אמצעי האחסון של VeraCrypt מכיל מערכת קבצים לא ידועה או שאינו מכיל מערכת קבצים כלל!\n\nרק אמצעי האחסון של VeraCrypt עצמו יורחב, מערכת הקבצים תישאר ללא שינוי.\n\nהאם ברצונך להמשיך?</entry>
+    <entry lang="he" key="EXPANDER_ERROR_VOLUME_SIZE_TOO_SMALL">גודל אמצעי האחסון החדש קטן מדי, חייב להיות גדול לפחות ב-%I64u ק"ב מהגודל הנוכחי.</entry>
+    <entry lang="he" key="EXPANDER_ERROR_VOLUME_SIZE_TOO_LARGE">גודל אמצעי האחסון החדש גדול מדי, אין מספיק מקום בכונן המארח.</entry>
+    <entry lang="he" key="EXPANDER_ERROR_MAX_FILE_SIZE_EXCEEDED">חרגת מגודל הקובץ המרבי של %I64u מ"ב בכונן המארח.</entry>
+    <entry lang="he" key="EXPANDER_ERROR_QUICKEXPAND_PRIVILEGES">שגיאה: נכשל ניסיון קבלת ההרשאות הדרושות להפעלת הרחבה מהירה!\nאנא בטל את בחירת אפשרות הרחבה מהירה ונסה שוב.</entry>
+    <entry lang="he" key="EXPANDER_ERROR_MAX_VC_VOLUME_SIZE_EXCEEDED">הגודל המרבי של אמצעי אחסון VeraCrypt (%I64u TB) חורג מהמותר!\n</entry>
+    <entry lang="he" key="FULL_FORMAT">פירמוט מלא</entry>
+    <entry lang="he" key="FAST_CREATE">יצירה מהירה</entry>
+    <entry lang="he" key="WARN_FAST_CREATE">אזהרה: עליך להשתמש ביצירה מהירה רק במקרים הבאים:\n\n1) ההתקן אינו מכיל נתונים רגישים ואינך זקוק להכחשה סבירה.\n2) ההתקן כבר הוצפן באופן מאובטח ומלא.\n\nהאם אתה בטוח שברצונך להשתמש ביצירה מהירה?</entry>
+    <entry lang="he" key="IDC_ENABLE_EMV_SUPPORT">אפשר תמיכת EMV</entry>
+    <entry lang="he" key="COMMAND_APDU_INVALID">פקודת APDU שנשלחה לכרטיס אינה תקפה.</entry>
+    <entry lang="he" key="EXTENDED_APDU_UNSUPPORTED">לא ניתן להשתמש בפקודות APDU מורחבות עם האסימון הנוכחי.</entry>
+    <entry lang="he" key="SCARD_MODULE_INIT_FAILED">שגיאה בעת טעינת ספריית WinSCard / PCSC.</entry>
+    <entry lang="he" key="EMV_UNKNOWN_CARD_TYPE">הכרטיס בקורא אינו כרטיס EMV נתמך.</entry>
+    <entry lang="he" key="EMV_SELECT_AID_FAILED">לא ניתן היה לבחור את ה-AID של הכרטיס בקורא.</entry>
+    <entry lang="he" key="EMV_ICC_CERT_NOTFOUND">תעודת מפתח ציבורי ICC לא נמצאה בכרטיס.</entry>
+    <entry lang="he" key="EMV_ISSUER_CERT_NOTFOUND">תעודת מפתח ציבורי של המנפיק לא נמצאה בכרטיס.</entry>
+    <entry lang="he" key="EMV_CPLC_NOTFOUND">נתוני CPLC לא נמצאו בכרטיס EMV.</entry>
+    <entry lang="he" key="EMV_PAN_NOTFOUND">לא נמצא מספר חשבון ראשי (PAN) בכרטיס EMV.</entry>
+    <entry lang="he" key="INVALID_EMV_PATH">נתיב EMV אינו תקף.</entry>
+    <entry lang="he" key="EMV_KEYFILE_DATA_NOTFOUND">לא ניתן ליצור קובץ מפתח מנתוני כרטיס ה-EMV.\n\nחסר אחד מהבאים:\n- תעודת מפתח ציבורי ICC.\n- תעודת מפתח ציבורי של המנפיק.\n- נתוני CPLC.</entry>
+    <entry lang="he" key="SCARD_W_REMOVED_CARD">אין כרטיס בקורא.\n\nאנא ודא שהכרטיס מוכנס כראוי.</entry>
+    <entry lang="he" key="FORMAT_EXTERNAL_FAILED">פקודת format.com של Windows נכשלה בפירמוט אמצעי האחסון כ-NTFS/exFAT/ReFS: שגיאה 0x%.8X.\n\nמעבר לשימוש ב-FormatEx API של Windows.</entry>
+    <entry lang="he" key="FORMATEX_API_FAILED">‏API‏ FormatEx של Windows נכשל בפירמוט אמצעי האחסון כ-NTFS/exFAT/ReFS.\n\nמצב כשל = %s.</entry>
+    <entry lang="he" key="EXPANDER_WRITING_RANDOM_DATA">כותב נתונים אקראיים לשטח החדש...\n</entry>
+    <entry lang="he" key="EXPANDER_WRITING_ENCRYPTED_BACKUP">כותב כותרת גיבוי מוצפנת מחדש...\n</entry>
+    <entry lang="he" key="EXPANDER_WRITING_ENCRYPTED_PRIMARY">כותב כותרת ראשית מוצפנת מחדש...\n</entry>
+    <entry lang="he" key="EXPANDER_WIPING_OLD_HEADER">מוחק כותרת גיבוי ישנה...\n</entry>
+    <entry lang="he" key="EXPANDER_MOUNTING_VOLUME">מתקין את אמצעי האחסון...\n</entry>
+    <entry lang="he" key="EXPANDER_UNMOUNTING_VOLUME">מסיר את אמצעי האחסון...\n</entry>
+    <entry lang="he" key="EXPANDER_EXTENDING_FILESYSTEM">מרחיב את מערכת הקבצים...\n</entry>
+    <entry lang="he" key="PARTIAL_SYSENC_MOUNT_READONLY">אזהרה: מחיצת המערכת שניסית להתקין לא הוצפנה במלואה. כאמצעי זהירות למניעת השחתה פוטנציאלית או שינויים לא רצויים, אמצעי אחסון '%s' הותקן לקריאה בלבד.</entry>
+    <entry lang="he" key="IDC_LINK_KEYFILES_EXTENSIONS_WARNING">מידע חשוב על שימוש בסיומות קבצים של צד שלישי</entry>
+    <entry lang="he" key="IDC_DISABLE_MEMORY_PROTECTION">השבת הגנת זיכרון לתאימות עם כלי נגישות</entry>
+    <entry lang="he" key="DISABLE_MEMORY_PROTECTION_WARNING">אזהרה: השבתת הגנת הזיכרון מפחיתה משמעותית את האבטחה. אפשר אפשרות זו רק אם אתה מסתמך על כלי נגישות, כמו קוראי מסך, לאינטראקציה עם ממשק המשתמש של VeraCrypt.</entry>
     <entry lang="he" key="LINUX_LANGUAGE">שפה</entry>
-    <entry lang="en" key="LINUX_SELECT_SYS_DEFAULT_LANG">Select system's default language</entry>
-    <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="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="he" key="LINUX_SELECT_SYS_DEFAULT_LANG">בחר את שפת ברירת המחדל של המערכת</entry>
+    <entry lang="he" key="LINUX_RESTART_FOR_LANGUAGE_CHANGE">כדי ששינוי השפה ייכנס לתוקף, יש להפעיל את VeraCrypt מחדש.</entry>
+    <entry lang="he" key="ERR_XTS_MASTERKEY_VULNERABLE">אזהרה: מפתח הראשי של אמצעי האחסון פגיע להתקפה המסכנת את אבטחת הנתונים.\n\nאנא צור אמצעי אחסון חדש והעבר אליו את הנתונים.</entry>
+    <entry lang="he" key="ERR_SYSENC_XTS_MASTERKEY_VULNERABLE">אזהרה: מפתח הראשי של המערכת המוצפנת פגיע להתקפה המסכנת את אבטחת הנתונים.\nאנא פענח את מחיצת/כונן המערכת ולאחר מכן הצפן אותה מחדש.</entry>
+    <entry lang="he" key="ERR_XTS_MASTERKEY_VULNERABLE_SHORT">אזהרה: למפתח הראשי של אמצעי האחסון קיימת חולשת אבטחה.</entry>
+    <entry lang="he" key="MOUNTPOINT_BLOCKED">שגיאה: נתיב הטעינה של אמצעי האחסון חסום מכיוון שהוא דורס ספריית מערכת מוגנת.\n\nאנא בחר נתיב טעינה אחר.</entry>
+    <entry lang="he" key="MOUNTPOINT_NOTALLOWED">שגיאה: נתיב הטעינה של אמצעי האחסון אינו מותר מכיוון שהוא דורס ספרייה שהיא חלק ממשתנה הסביבה PATH.\n\nאנא בחר נתיב טעינה אחר.</entry>
+    <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="hu" key="TC_INSTALLER_IS_RUNNING">A VeraCrypt telepítő jelenleg fut a rendszerben, és végrehajtja vagy előkészíti a VeraCrypt telepítését vagy frissítését. A folytatás előtt várja meg, amíg befejeződik, vagy zárja be. Ha nem tudja bezárni, a folytatás előtt indítsa újra a számítógépet.</entry>
     <entry lang="hu" key="INSTALL_FAILED">A telepítés sikertelen volt.</entry>
     <entry lang="hu" key="UNINSTALL_FAILED">Az eltávolítás sikertelen volt.</entry>
-    <entry lang="hu" key="DIST_PACKAGE_CORRUPTED">Ez a disztribúciós csomag sérült. Próbálja meg újra letölteni (lehetőleg a VeraCrypt hivatalos weboldaláról: https://www.veracrypt.fr).</entry>
+    <entry lang="hu" key="DIST_PACKAGE_CORRUPTED">Ez a disztribúciós csomag sérült. Próbálja meg újra letölteni (lehetőleg a VeraCrypt hivatalos weboldaláról: https://veracrypt.jp).</entry>
     <entry lang="hu" key="CANNOT_WRITE_FILE_X">A(z) %s fájl nem írható</entry>
     <entry lang="hu" key="EXTRACTING_VERB">Kibontás</entry>
     <entry lang="hu" key="CANNOT_READ_FROM_PACKAGE">Nem lehet kiolvasni az adatokat a csomagból.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="hu" key="HIDDEN_OS_CREATION_PREINFO_HELP">A következő lépésekben a VeraCrypt létrehozza a rejtett operációs rendszert a rendszerpartíció tartalmának rejtett kötetre másolásával (az átmásolt adatok menet közben kerülnek titkosításra a csali operációs rendszertől eltérő titkosítókulccsal).\n\nFelhívjuk figyelmét, hogy a folyamat a rendszerindítást megelőző környezetben kerül végrehajtásra (a Windows elindulása előtt), és ez sokáig tarthat; több óra vagy akár több nap (a rendszerpartíció méretétől és a számítógép teljesítményétől függően).\n\nMegszakíthatja a folyamatot, leállíthatja a számítógépet, elindíthatja az operációs rendszert, majd folytathatja a folyamatot. Ha azonban megszakítja, a rendszermásolás teljes folyamatának az elejétől kell kezdődnie (mivel a rendszerpartíció tartalma nem változhat a klónozás során).</entry>
     <entry lang="hu" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Megszakítja a rejtett operációs rendszer létrehozásának teljes folyamatát?\n\nMegjegyzés: Ha most megszakítja, nem tudja folytatni a folyamatot.</entry>
     <entry lang="hu" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Megszakítja a rendszertitkosítási előtesztet?</entry>
-    <entry lang="hu" key="BOOT_PRETEST_FAILED_RETRY">A VeraCrypt rendszertitkosítási előtesztje sikertelen volt. Megpróbálja újra?\n\nHa a 'Nem' lehetőséget választja, a rendszerindítás előtti hitelesítési összetevő eltávolításra kerül.\n\nMegjegyzések:\n\n- Ha a VeraCrypt rendszertöltő nem kérte a jelszó megadását a Windows indítása előtt, akkor lehetséges, hogy az operációs rendszer nem arról a meghajtóról indul, amelyre telepítve van. Ez nem támogatott.\n\n- Ha az AES-től eltérő titkosítási algoritmust használt, és az előzetes tesztelés sikertelen volt (és megadta a jelszót), a hibát valószínűleg egy nem megfelelően megtervezett illesztőprogram okozta. Válassza a 'Nem' lehetőséget, és próbálja meg újra titkosítani a rendszerpartíciót/meghajtót az AES titkosítási algoritmus használatával (amely a legalacsonyabb memória követelménnyel rendelkezik).\n\n- További lehetséges okok és megoldások: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="hu" key="BOOT_PRETEST_FAILED_RETRY">A VeraCrypt rendszertitkosítási előtesztje sikertelen volt. Megpróbálja újra?\n\nHa a 'Nem' lehetőséget választja, a rendszerindítás előtti hitelesítési összetevő eltávolításra kerül.\n\nMegjegyzések:\n\n- Ha a VeraCrypt rendszertöltő nem kérte a jelszó megadását a Windows indítása előtt, akkor lehetséges, hogy az operációs rendszer nem arról a meghajtóról indul, amelyre telepítve van. Ez nem támogatott.\n\n- Ha az AES-től eltérő titkosítási algoritmust használt, és az előzetes tesztelés sikertelen volt (és megadta a jelszót), a hibát valószínűleg egy nem megfelelően megtervezett illesztőprogram okozta. Válassza a 'Nem' lehetőséget, és próbálja meg újra titkosítani a rendszerpartíciót/meghajtót az AES titkosítási algoritmus használatával (amely a legalacsonyabb memória követelménnyel rendelkezik).\n\n- További lehetséges okok és megoldások: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="hu" key="SYS_DRIVE_NOT_ENCRYPTED">Úgy tűnik, hogy a rendszerpartíció/meghajtó nincs titkosítva (sem részben, sem teljesen).</entry>
     <entry lang="hu" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">A rendszerpartíció/meghajtó titkosítva van (részben vagy teljesen).\n\nFolytatás előtt teljesen fejtse vissza a rendszerpartíciót/meghajtót. Ehhez válassza a 'Rendszer' &gt; 'Rendszerpartíció/meghajtó végleges visszafejtése' lehetőséget a VeraCrypt fő ablakának menüsorából.</entry>
     <entry lang="hu" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">Ha a rendszerpartíció/meghajtó titkosítva van (részben vagy teljesen), nem állhat vissza korábbi VeraCrypt verzióra (de frissítheti vagy újratelepítheti ugyanazt a verziót).</entry>
@@ -1523,7 +1523,7 @@
     <entry lang="hu" key="LINUX_NOT_SUPPORTED"> (az aktuális platformon elérhető összetevők nem támogatják).\n</entry>
     <entry lang="hu" key="LINUX_KERNEL_OLD">Rendszere a Linux kernel régi verzióját használja.\n\nA Linux kernel hibája miatt előfordulhat, hogy rendszere nem válaszol, miközben adatokat ír egy VeraCrypt kötetre. Ez a probléma megoldható a kernel 2.6.24-es vagy újabb verziójára történő frissítésével.</entry>
     <entry lang="hu" key="LINUX_VOL_UNMOUNTED">A(z) {0} kötet le van választva.</entry>
-    <entry lang="en" key="LINUX_VOL_MOUNTED">Volume {0} has been mounted.</entry>
+    <entry lang="hu" key="LINUX_VOL_MOUNTED">A(z) {0} kötet csatlakoztatva lett.</entry>
     <entry lang="hu" key="LINUX_OOM">Kevés a memória.</entry>
     <entry lang="hu" key="LINUX_CANT_GET_ADMIN_PRIV">Nem sikerült rendszergazdai jogosultságokat szerezni</entry>
     <entry lang="hu" key="LINUX_COMMAND_GET_ERROR">A(z) {0} parancs {1} hibával tért vissza.</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="hu" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Hiba: A meghajtó 512 bájttól eltérő szektorméretet használ.\n\nA platformon elérhető összetevők korlátai miatt a partíció/eszköz által tárolt kötetek nem hozhatók létre/használhatók a meghajtón.\n\nLehetséges megoldások:\n- Hozzon létre egy fájl által tárolt kötetet (tárolót) a meghajtón.\n- Használjon 512 bájtos szektorokkal rendelkező meghajtót.\n- Használja a VeraCrypt alkalmazást egy másik platformon.</entry>
     <entry lang="hu" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">A gazdafájl/eszköz már használatban van</entry>
     <entry lang="hu" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">A kötettároló nem érhető el.</entry>
-    <entry lang="hu" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">A VeraCrypt OSXFUSE 2.5 vagy újabb verziót igényel.</entry>
+    <entry lang="hu" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">A VeraCrypt macFUSE 2.5 vagy újabb verziót igényel.</entry>
     <entry lang="hu" key="EXCEPTION_OCCURRED">Kivétel történt</entry>
     <entry lang="hu" key="ENTER_PASSWORD">Adja meg a jelszót</entry>
     <entry lang="hu" key="ENTER_TC_VOL_PASSWORD">Adja meg a VeraCrypt kötet jelszavát</entry>
@@ -1568,82 +1568,126 @@
     <entry lang="hu" key="UNKNOWN_OPTION">Ismeretlen opció</entry>
     <entry lang="hu" key="VOLUME_LOCATION">Kötet helye</entry>
     <entry lang="hu" key="VOLUME_HOST_IN_USE">FIGYELEM: A(z) {0} gazdafájl/eszköz már használatban van!\n\nEnnek figyelmen kívül hagyása nemkívánatos eredményekhez vezethet, beleértve a rendszer instabilitását is.\nA kötet csatolása előtt minden olyan alkalmazást le kell állítani, amely a gazdafájlt/eszközt használja.\nFolytatja a csatolást?</entry>
-    <entry lang="en" key="CANT_INSTALL_WITH_EXE_OVER_MSI">VeraCrypt was previously installed using an MSI package and so it can't be updated using the standard installer.\n\nPlease use the MSI package to update your VeraCrypt installation.</entry>
-    <entry lang="en" key="IDC_USE_ALL_FREE_SPACE">Use all available free space</entry>
-    <entry lang="en" key="SYS_ENCRYPTION_UPGRADE_UNSUPPORTED_ALGORITHM">VeraCrypt cannot be upgraded because the system partition/drive was encrypted using an algorithm that is not supported anymore.\nPlease decrypt your system before upgrading VeraCrypt and then encrypt it again.</entry>
-    <entry lang="en" key="LINUX_EX2MSG_TERMINALNOTFOUND">Supported terminal application could not be found, you need either xterm, konsole or gnome-terminal (with dbus-x11).</entry>
-    <entry lang="en" key="IDM_MOUNT_NO_CACHE">Mount Without Cache</entry>
-    <entry lang="en" key="EXPANDER_INFO">:: VeraCrypt Expander ::\n\nExpand a VeraCrypt volume on the fly without reformatting\n\n\nAll kind of volumes (container files, disks and partitions) formatted with NTFS are supported. The only condition is that there must be enough free space on the host drive or host device of the VeraCrypt volume.\n\nDo not use this software to expand an outer volume containing a hidden volume, because this destroys the hidden volume!\n</entry>
-    <entry lang="en" key="IDC_STEPSEXPAND">1. Select the VeraCrypt volume to be expanded\n2. Click the 'Mount' button</entry>
-    <entry lang="en" key="IDT_VOL_NAME">Volume: </entry>
-    <entry lang="en" key="IDT_FILE_SYS">File system: </entry>
-    <entry lang="en" key="IDT_CURRENT_SIZE">Current size: </entry>
-    <entry lang="en" key="IDT_NEW_SIZE">New size: </entry>
-    <entry lang="en" key="IDT_NEW_SIZE_BOX_TITLE">Enter new volume size</entry>
-    <entry lang="en" key="IDC_INIT_NEWSPACE">Fill new space with random data</entry>
-    <entry lang="en" key="IDC_QUICKEXPAND">Quick Expand</entry>
-    <entry lang="en" key="IDT_INIT_SPACE">Fill new space: </entry>
-    <entry lang="en" key="EXPANDER_FREE_SPACE">%s free space available on host drive</entry>
-    <entry lang="en" key="EXPANDER_HELP_DEVICE">This is a device-based VeraCrypt volume.\n\nThe new volume size will be choosen automatically as the size of the host device.</entry>
-    <entry lang="en" key="EXPANDER_HELP_FILE">Please specify the new size of the VeraCrypt volume (must be at least %I64u KB larger than the current size).</entry>
-    <entry lang="en" key="QUICK_EXPAND_WARNING">WARNING: You should use Quick Expand only in the following cases:\n\n1) The device where the file container is located contains no sensitive data and you do not need plausible deniability.\n2) The device where the file container is located has already been securely and fully encrypted.\n\nAre you sure you want to use Quick Expand?</entry>
-    <entry lang="en" key="EXPANDER_STATUS_TEXT">IMPORTANT: Move your mouse as randomly as possible within this window. The longer you move it, the better. This significantly increases the cryptographic strength of the encryption keys. Then click 'Continue' to expand the volume.</entry>
-    <entry lang="en" key="EXPANDER_STATUS_TEXT_LEGACY">Click 'Continue' to expand the volume.</entry>
-    <entry lang="en" key="EXPANDER_FINISH_ERROR">Error: volume expansion failed.</entry>
-    <entry lang="en" key="EXPANDER_FINISH_ABORT">Error: operation aborted by user.</entry>
-    <entry lang="en" key="EXPANDER_FINISH_OK">Finished. Volume successfully expanded.</entry>
-    <entry lang="en" key="EXPANDER_CANCEL_WARNING">Warning: Volume expansion is in progress!\n\nStopping now may result in a damaged volume.\n\nDo you really want to cancel?</entry>
-    <entry lang="en" key="EXPANDER_STARTING_STATUS">Starting volume expansion ...\n</entry>
-    <entry lang="en" key="EXPANDER_HIDDEN_VOLUME_ERROR">An outer volume containing a hidden volume can't be expanded, because this destroys the hidden volume.\n</entry>
-    <entry lang="en" key="EXPANDER_SYSTEM_VOLUME_ERROR">A VeraCrypt system volume can't be expanded.</entry>
-    <entry lang="en" key="EXPANDER_NO_FREE_SPACE">Not enough free space to expand the volume</entry>
-    <entry lang="en" key="EXPANDER_WARNING_FILE_CONTAINER_JUNK">Warning: The container file is larger than the VeraCrypt volume area. The data after the VeraCrypt volume area will be overwritten.\n\nDo you want to continue?</entry>
-    <entry lang="en" key="EXPANDER_WARNING_FAT">Warning: The VeraCrypt volume contains a FAT file system!\n\nOnly the VeraCrypt volume itself will be expanded, but not the file system.\n\nDo you want to continue?</entry>
-    <entry lang="en" key="EXPANDER_WARNING_EXFAT">Warning: The VeraCrypt volume contains an exFAT file system!\n\nOnly the VeraCrypt volume itself will be expanded, but not the file system.\n\nDo you want to continue?</entry>
-    <entry lang="en" key="EXPANDER_WARNING_UNKNOWN_FS">Warning: The VeraCrypt volume contains an unknown or no file system!\n\nOnly the VeraCrypt volume itself will be expanded, the file system remains unchanged.\n\nDo you want to continue?</entry>
-    <entry lang="en" key="EXPANDER_ERROR_VOLUME_SIZE_TOO_SMALL">New volume size too small, must be at least %I64u kB larger than the current size.</entry>
-    <entry lang="en" key="EXPANDER_ERROR_VOLUME_SIZE_TOO_LARGE">New volume size too large, not enough space on host drive.</entry>
-    <entry lang="en" key="EXPANDER_ERROR_MAX_FILE_SIZE_EXCEEDED">Maximum file size of %I64u MB on host drive exceeded.</entry>
-    <entry lang="en" key="EXPANDER_ERROR_QUICKEXPAND_PRIVILEGES">Error: Failed to get necessary privileges to enable Quick Expand!\nPlease uncheck Quick Expand option and try again.</entry>
-    <entry lang="en" key="EXPANDER_ERROR_MAX_VC_VOLUME_SIZE_EXCEEDED">Maximum VeraCrypt volume size of %I64u TB exceeded!\n</entry>
-    <entry lang="en" key="FULL_FORMAT">Full Format</entry>
-    <entry lang="en" key="FAST_CREATE">Fast Create</entry>
-    <entry lang="en" key="WARN_FAST_CREATE">WARNING: You should use Fast Create only in the following cases:\n\n1) The device contains no sensitive data and you do not need plausible deniability.\n2) The device has already been securely and fully encrypted.\n\nAre you sure you want to use Fast Create?</entry>
-    <entry lang="en" key="IDC_ENABLE_EMV_SUPPORT">Enable EMV Support</entry>
-    <entry lang="en" key="COMMAND_APDU_INVALID">The APDU command sent to the card is not valid.</entry>
-    <entry lang="en" key="EXTENDED_APDU_UNSUPPORTED">Extended APDU commands cannot be used with the current token.</entry>
-    <entry lang="en" key="SCARD_MODULE_INIT_FAILED">Error when loading the WinSCard / PCSC library.</entry>
-    <entry lang="en" key="EMV_UNKNOWN_CARD_TYPE">The card in the reader is not a supported EMV card.</entry>
-    <entry lang="en" key="EMV_SELECT_AID_FAILED">The AID of the card in the reader could not be selected.</entry>
-    <entry lang="en" key="EMV_ICC_CERT_NOTFOUND">ICC Public Key Certificate was not found in the card.</entry>
-    <entry lang="en" key="EMV_ISSUER_CERT_NOTFOUND">Issuer Public Key Certificate was not found in the card.</entry>
-    <entry lang="en" key="EMV_CPLC_NOTFOUND">CPLC was not found in the EMV card.</entry>
-    <entry lang="en" key="EMV_PAN_NOTFOUND">No Primary Account Number (PAN) found in the EMV card.</entry>
-    <entry lang="en" key="INVALID_EMV_PATH">EMV path is invalid.</entry>
-    <entry lang="en" key="EMV_KEYFILE_DATA_NOTFOUND">Unable to build a keyfile from the EMV card's data.\n\nOne of the following is missing:\n- ICC Public Key Certificate.\n- Issuer Public Key Certificate.\n- CPLC data.</entry>
-    <entry lang="en" key="SCARD_W_REMOVED_CARD">No card in the reader.\n\nPlease make sure the card is correctly slotted.</entry>
-    <entry lang="en" key="FORMAT_EXTERNAL_FAILED">Windows format.com command failed to format the volume as NTFS/exFAT/ReFS: Error 0x%.8X.\n\nFalling back to using Windows FormatEx API.</entry>
-    <entry lang="en" key="FORMATEX_API_FAILED">Windows FormatEx API failed to format the volume as NTFS/exFAT/ReFS.\n\nFailure status = %s.</entry>
-    <entry lang="en" key="EXPANDER_WRITING_RANDOM_DATA">Writing random data to new space ...\n</entry>
-    <entry lang="en" key="EXPANDER_WRITING_ENCRYPTED_BACKUP">Writing re-encrypted backup header ...\n</entry>
-    <entry lang="en" key="EXPANDER_WRITING_ENCRYPTED_PRIMARY">Writing re-encrypted primary header ...\n</entry>
-    <entry lang="en" key="EXPANDER_WIPING_OLD_HEADER">Wiping old backup header ...\n</entry>
-    <entry lang="en" key="EXPANDER_MOUNTING_VOLUME">Mounting volume ...\n</entry>
-    <entry lang="en" key="EXPANDER_UNMOUNTING_VOLUME">Unmounting volume ...\n</entry>
-    <entry lang="en" key="EXPANDER_EXTENDING_FILESYSTEM">Extending file system ...\n</entry>
-    <entry lang="en" key="PARTIAL_SYSENC_MOUNT_READONLY">Warning: The system partition you attempted to mount was not fully encrypted. As a safety measure to prevent potential corruption or unwanted modifications, volume '%s' was mounted as read-only.</entry>
-    <entry lang="en" key="IDC_LINK_KEYFILES_EXTENSIONS_WARNING">Important information on using third-party file extensions</entry>
-    <entry lang="en" key="IDC_DISABLE_MEMORY_PROTECTION">Disable memory protection for Accessibility tools compatibility</entry>
-    <entry lang="en" key="DISABLE_MEMORY_PROTECTION_WARNING">WARNING: Disabling memory protection significantly reduces security. Enable this option ONLY if you rely on Accessibility tools, like Screen Readers, to interact with VeraCrypt's UI.</entry>
+    <entry lang="hu" key="CANT_INSTALL_WITH_EXE_OVER_MSI">A VeraCrypt korábban MSI csomaggal lett telepítve, ezért nem frissíthető a hagyományos telepítővel.\n\nKérjük, használja az MSI csomagot a VeraCrypt frissítéséhez.</entry>
+    <entry lang="hu" key="IDC_USE_ALL_FREE_SPACE">Az összes rendelkezésre álló szabad hely használata</entry>
+    <entry lang="hu" key="SYS_ENCRYPTION_UPGRADE_UNSUPPORTED_ALGORITHM">A VeraCrypt nem frissíthető, mert a rendszer partíciója/meghajtója olyan algoritmussal lett titkosítva, amely már nem támogatott.\nKérjük, frissítés előtt fejtse vissza a rendszert, majd titkosítsa újra.</entry>
+    <entry lang="hu" key="LINUX_EX2MSG_TERMINALNOTFOUND">Nem található támogatott terminálalkalmazás, szüksége van xterm, konsole vagy gnome-terminal (dbus-x11) programra.</entry>
+    <entry lang="hu" key="IDM_MOUNT_NO_CACHE">Csatolás gyorsítótár nélkül</entry>
+    <entry lang="hu" key="EXPANDER_INFO">:: VeraCrypt Expander ::\n\nVeraCrypt kötet bővítése azonnal, újraformázás nélkül\n\n\nMinden NTFS-re formázott kötet (konténerfájl, lemez, partíció) támogatott. Az egyetlen feltétel, hogy a gazda meghajtón vagy eszközön elegendő szabad hely álljon rendelkezésre.\n\nNe használja ezt a programot olyan külső kötet bővítésére, amely rejtett kötetet tartalmaz, mert ez megsemmisíti a rejtett kötetet!\n</entry>
+    <entry lang="hu" key="IDC_STEPSEXPAND">1. Válassza ki a bővítendő VeraCrypt kötetet\n2. Kattintson a 'Csatolás' gombra</entry>
+    <entry lang="hu" key="IDT_VOL_NAME">Kötet: </entry>
+    <entry lang="hu" key="IDT_FILE_SYS">Fájlrendszer: </entry>
+    <entry lang="hu" key="IDT_CURRENT_SIZE">Jelenlegi méret: </entry>
+    <entry lang="hu" key="IDT_NEW_SIZE">Új méret: </entry>
+    <entry lang="hu" key="IDT_NEW_SIZE_BOX_TITLE">Adja meg az új kötetméretet</entry>
+    <entry lang="hu" key="IDC_INIT_NEWSPACE">Az új terület kitöltése véletlenszerű adatokkal</entry>
+    <entry lang="hu" key="IDC_QUICKEXPAND">Gyorsbővítés</entry>
+    <entry lang="hu" key="IDT_INIT_SPACE">Új terület kitöltése: </entry>
+    <entry lang="hu" key="EXPANDER_FREE_SPACE">%s szabad hely érhető el a gazda meghajtón</entry>
+    <entry lang="hu" key="EXPANDER_HELP_DEVICE">Ez egy eszköz-alapú VeraCrypt kötet.\n\nAz új kötetméret automatikusan a gazdaeszköz méretéhez igazodik.</entry>
+    <entry lang="hu" key="EXPANDER_HELP_FILE">Kérjük, adja meg a VeraCrypt kötet új méretét (legalább %I64u KB-tal nagyobbnak kell lennie, mint a jelenlegi méret).</entry>
+    <entry lang="hu" key="QUICK_EXPAND_WARNING">FIGYELEM: A Gyorsbővítést csak a következő esetekben használja:\n\n1) Az eszköz, amelyen a fájlkonténer található, nem tartalmaz érzékeny adatokat, és nincs szüksége hihető letagadhatóságra.\n2) Az eszköz, amelyen a fájlkonténer található, már teljes egészében és biztonságosan titkosítva van.\n\nBiztosan használni kívánja a Gyorsbővítést?</entry>
+    <entry lang="hu" key="EXPANDER_STATUS_TEXT">FONTOS: Mozgassa az egeret a lehető legvéletlenszerűbben ezen az ablakon belül. Minél tovább mozgatja, annál jobb. Ez jelentősen növeli a titkosítási kulcsok kriptográfiai erősségét. Ezután kattintson a 'Folytatás' gombra a kötet bővítéséhez.</entry>
+    <entry lang="hu" key="EXPANDER_STATUS_TEXT_LEGACY">Kattintson a 'Folytatás' gombra a kötet bővítéséhez.</entry>
+    <entry lang="hu" key="EXPANDER_FINISH_ERROR">Hiba: a kötet bővítése sikertelen volt.</entry>
+    <entry lang="hu" key="EXPANDER_FINISH_ABORT">Hiba: a műveletet a felhasználó megszakította.</entry>
+    <entry lang="hu" key="EXPANDER_FINISH_OK">Kész. A kötet sikeresen kibővült.</entry>
+    <entry lang="hu" key="EXPANDER_CANCEL_WARNING">Figyelem: A kötet bővítése folyamatban van!\n\nA mostani leállítás sérült kötethez vezethet.\n\nValóban megszakítja?</entry>
+    <entry lang="hu" key="EXPANDER_STARTING_STATUS">Kötet bővítésének indítása ...\n</entry>
+    <entry lang="hu" key="EXPANDER_HIDDEN_VOLUME_ERROR">Olyan külső kötet, amely rejtett kötetet tartalmaz, nem bővíthető, mert ez megsemmisíti a rejtett kötetet.\n</entry>
+    <entry lang="hu" key="EXPANDER_SYSTEM_VOLUME_ERROR">A VeraCrypt rendszerkötet nem bővíthető.</entry>
+    <entry lang="hu" key="EXPANDER_NO_FREE_SPACE">Nincs elegendő szabad hely a kötet bővítéséhez</entry>
+    <entry lang="hu" key="EXPANDER_WARNING_FILE_CONTAINER_JUNK">Figyelem: A konténerfájl nagyobb, mint a VeraCrypt kötet területe. A kötetterület után következő adatok felülíródnak.\n\nFolytatja?</entry>
+    <entry lang="hu" key="EXPANDER_WARNING_FAT">Figyelem: A VeraCrypt kötet FAT fájlrendszert tartalmaz!\n\nCsak maga a VeraCrypt kötet lesz kibővítve, a fájlrendszer nem.\n\nFolytatja?</entry>
+    <entry lang="hu" key="EXPANDER_WARNING_EXFAT">Figyelem: A VeraCrypt kötet exFAT fájlrendszert tartalmaz!\n\nCsak maga a VeraCrypt kötet lesz kibővítve, a fájlrendszer nem.\n\nFolytatja?</entry>
+    <entry lang="hu" key="EXPANDER_WARNING_UNKNOWN_FS">Figyelem: A VeraCrypt kötet ismeretlen vagy nem tartalmaz fájlrendszert!\n\nCsak maga a VeraCrypt kötet lesz kibővítve, a fájlrendszer változatlan marad.\n\nFolytatja?</entry>
+    <entry lang="hu" key="EXPANDER_ERROR_VOLUME_SIZE_TOO_SMALL">Az új kötetméret túl kicsi, legalább %I64u KiB-tal nagyobbnak kell lennie a jelenleginél.</entry>
+    <entry lang="hu" key="EXPANDER_ERROR_VOLUME_SIZE_TOO_LARGE">Az új kötetméret túl nagy, nincs elegendő hely a gazda meghajtón.</entry>
+    <entry lang="hu" key="EXPANDER_ERROR_MAX_FILE_SIZE_EXCEEDED">A gazda meghajtó maximális fájlmérete (%I64u MB) túllépve.</entry>
+    <entry lang="hu" key="EXPANDER_ERROR_QUICKEXPAND_PRIVILEGES">Hiba: Nem sikerült megszerezni a Gyorsbővítés engedélyezéséhez szükséges jogosultságokat!\nKérjük, vegye ki a jelölést a Gyorsbővítés opcióból, és próbálja újra.</entry>
+    <entry lang="hu" key="EXPANDER_ERROR_MAX_VC_VOLUME_SIZE_EXCEEDED">A VeraCrypt kötet maximális mérete (%I64u TB) túllépve!\n</entry>
+    <entry lang="hu" key="FULL_FORMAT">Teljes formázás</entry>
+    <entry lang="hu" key="FAST_CREATE">Gyors létrehozás</entry>
+    <entry lang="hu" key="WARN_FAST_CREATE">FIGYELEM: A Gyors létrehozást csak a következő esetekben használja:\n\n1) Az eszköz nem tartalmaz érzékeny adatokat, és nincs szüksége hihető letagadhatóságra.\n2) Az eszköz már teljes egészében és biztonságosan titkosítva van.\n\nBiztosan használni kívánja a Gyors létrehozást?</entry>
+    <entry lang="hu" key="IDC_ENABLE_EMV_SUPPORT">EMV támogatás engedélyezése</entry>
+    <entry lang="hu" key="COMMAND_APDU_INVALID">A kártyára küldött APDU parancs érvénytelen.</entry>
+    <entry lang="hu" key="EXTENDED_APDU_UNSUPPORTED">Kiterjesztett APDU parancsok nem használhatók a jelenlegi tokennel.</entry>
+    <entry lang="hu" key="SCARD_MODULE_INIT_FAILED">Hiba a WinSCard / PCSC könyvtár betöltésekor.</entry>
+    <entry lang="hu" key="EMV_UNKNOWN_CARD_TYPE">A kártya az olvasóban nem támogatott EMV kártya.</entry>
+    <entry lang="hu" key="EMV_SELECT_AID_FAILED">Nem sikerült kiválasztani a kártya AID-jét az olvasóban.</entry>
+    <entry lang="hu" key="EMV_ICC_CERT_NOTFOUND">Az ICC nyilvános kulcstanúsítvány nem található a kártyán.</entry>
+    <entry lang="hu" key="EMV_ISSUER_CERT_NOTFOUND">A kibocsátó nyilvános kulcstanúsítványa nem található a kártyán.</entry>
+    <entry lang="hu" key="EMV_CPLC_NOTFOUND">A CPLC nem található az EMV kártyán.</entry>
+    <entry lang="hu" key="EMV_PAN_NOTFOUND">Az EMV kártyán nem található elsődleges számlaszám (PAN).</entry>
+    <entry lang="hu" key="INVALID_EMV_PATH">Az EMV útvonal érvénytelen.</entry>
+    <entry lang="hu" key="EMV_KEYFILE_DATA_NOTFOUND">Nem lehet kulcsfájlt készíteni az EMV kártya adataiból.\n\nAz alábbiak közül valamelyik hiányzik:\n- ICC nyilvános kulcstanúsítvány.\n- Kibocsátó nyilvános kulcstanúsítvány.\n- CPLC adat.</entry>
+    <entry lang="hu" key="SCARD_W_REMOVED_CARD">Nincs kártya az olvasóban.\n\nKérjük, ellenőrizze, hogy helyesen helyezte-e be a kártyát.</entry>
+    <entry lang="hu" key="FORMAT_EXTERNAL_FAILED">A Windows format.com parancs sikertelen volt az NTFS/exFAT/ReFS kötet formázásánál: Hiba 0x%.8X.\n\nÁtváltás a Windows FormatEx API használatára.</entry>
+    <entry lang="hu" key="FORMATEX_API_FAILED">A Windows FormatEx API nem tudta NTFS/exFAT/ReFS formátumra formázni a kötetet.\n\nSikertelenség állapota = %s.</entry>
+    <entry lang="hu" key="EXPANDER_WRITING_RANDOM_DATA">Véletlenszerű adatok írása az új területre ...\n</entry>
+    <entry lang="hu" key="EXPANDER_WRITING_ENCRYPTED_BACKUP">Újratitkosított biztonsági fejléc írása ...\n</entry>
+    <entry lang="hu" key="EXPANDER_WRITING_ENCRYPTED_PRIMARY">Újratitkosított elsődleges fejléc írása ...\n</entry>
+    <entry lang="hu" key="EXPANDER_WIPING_OLD_HEADER">Régi biztonsági fejléc törlése ...\n</entry>
+    <entry lang="hu" key="EXPANDER_MOUNTING_VOLUME">Kötet csatolása ...\n</entry>
+    <entry lang="hu" key="EXPANDER_UNMOUNTING_VOLUME">Kötet leválasztása ...\n</entry>
+    <entry lang="hu" key="EXPANDER_EXTENDING_FILESYSTEM">Fájlrendszer bővítése ...\n</entry>
+    <entry lang="hu" key="PARTIAL_SYSENC_MOUNT_READONLY">Figyelem: A rendszerpartíció, amelyet csatolni próbált, nem volt teljesen titkosítva. Biztonsági okokból, az esetleges sérülés vagy nem kívánt módosítások elkerülése érdekében a(z) '%s' kötet csak olvasható módban lett csatolva.</entry>
+    <entry lang="hu" key="IDC_LINK_KEYFILES_EXTENSIONS_WARNING">Fontos információk harmadik féltől származó fájlkiterjesztések használatáról</entry>
+    <entry lang="hu" key="IDC_DISABLE_MEMORY_PROTECTION">Memóriavédelem letiltása az akadálymentesítési eszközökkel való kompatibilitás érdekében</entry>
+    <entry lang="hu" key="DISABLE_MEMORY_PROTECTION_WARNING">FIGYELEM: A memóriavédelem letiltása jelentősen csökkenti a biztonságot. Csak akkor engedélyezze ezt a lehetőséget, ha akadálymentesítési eszközökre, például képernyőolvasókra van szüksége a VeraCrypt felületének használatához.</entry>
     <entry lang="hu" key="LINUX_LANGUAGE">Nyelv</entry>
-    <entry lang="en" key="LINUX_SELECT_SYS_DEFAULT_LANG">Select system's default language</entry>
-    <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="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="hu" key="LINUX_SELECT_SYS_DEFAULT_LANG">Rendszer alapértelmezett nyelvének kiválasztása</entry>
+    <entry lang="hu" key="LINUX_RESTART_FOR_LANGUAGE_CHANGE">A nyelvváltoztatás életbe lépéséhez újra kell indítania a VeraCrypt-et.</entry>
+    <entry lang="hu" key="ERR_XTS_MASTERKEY_VULNERABLE">FIGYELEM: A kötet mesterkulcsa sebezhető egy olyan támadással szemben, amely veszélyezteti az adatok biztonságát.\n\nKérjük, hozzon létre új kötetet, és másolja át az adatokat.</entry>
+    <entry lang="hu" key="ERR_SYSENC_XTS_MASTERKEY_VULNERABLE">FIGYELEM: A titkosított rendszer mesterkulcsa sebezhető egy olyan támadással szemben, amely veszélyezteti az adatok biztonságát.\nKérjük, fejtse vissza a rendszer partíciót/meghajtót, majd titkosítsa újra.</entry>
+    <entry lang="hu" key="ERR_XTS_MASTERKEY_VULNERABLE_SHORT">FIGYELEM: A kötet mesterkulcsa biztonsági sérülékenységgel rendelkezik.</entry>
+    <entry lang="hu" key="MOUNTPOINT_BLOCKED">HIBA: A kötet csatolási pontja blokkolva van, mert védett rendszerkönyvtárat írhatna felül.\n\nKérjük, válasszon másik csatolási pontot.</entry>
+    <entry lang="hu" key="MOUNTPOINT_NOTALLOWED">HIBA: A kötet csatolási pontja nem engedélyezett, mert a PATH környezeti változóban szereplő könyvtárat írná felül.\n\nKérjük, válasszon másik csatolási pontot.</entry>
+    <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="id" key="TC_INSTALLER_IS_RUNNING">VeraCrypt Installer saat ini berjalan pada sistem ini dan melakukan atau mempersiapkan instalasi atau update dari VeraCrypt. Sebelum Anda melanjutkan, silakan menunggu untuk menyelesaikan atau menutupnya. Jika Anda tidak dapat menutupnya, silakan restart komputer Anda sebelum melanjutkan.</entry>
     <entry lang="id" key="INSTALL_FAILED">Pemasangan gagal.</entry>
     <entry lang="id" key="UNINSTALL_FAILED">Penghapusan instalasi gagal.</entry>
-    <entry lang="id" key="DIST_PACKAGE_CORRUPTED">Paket distribusi ini rusak. Silakan coba mengunduhnya lagi (sebaiknya dari situs web resmi VeraCrypt di https://www.veracrypt.fr).</entry>
+    <entry lang="id" key="DIST_PACKAGE_CORRUPTED">Paket distribusi ini rusak. Silakan coba mengunduhnya lagi (sebaiknya dari situs web resmi VeraCrypt di https://veracrypt.jp).</entry>
     <entry lang="id" key="CANNOT_WRITE_FILE_X">Tak bisa menulis berkas %s</entry>
     <entry lang="id" key="EXTRACTING_VERB">Mengekstrak</entry>
     <entry lang="id" key="CANNOT_READ_FROM_PACKAGE">Tidak dapat membaca data dari paket.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="id" key="HIDDEN_OS_CREATION_PREINFO_HELP">Pada langkah selanjutnya, VeraCrypt akan membuat sistem operasi tersembunyi dengan menyalin konten partisi sistem ke volume tersembunyi (data yang disalin akan dienkripsi sambil jalan dengan kunci enkripsi yang berbeda dari yang akan digunakan untuk sistem operasi umpan).\n\nHarap perhatikan bahwa proses akan dilaksanakan dalam lingkungan pra boot (sebelum Windows dimulai) dan mungkin makan waktu lama untuk selesai; beberapa jam atau bahkan beberapa hari (tergantung pada ukuran partisi sistem dan kinerja komputer Anda).\n\nAnda akan dapat menginterupsi proses, mematikan komputer Anda, memulai sistem operasi, lalu melanjutkan proses. Namun, jika Anda menginterupsinya, seluruh proses menyalin sistem harus dimulai dari awal (karena konten partisi sistem tidak boleh berubah selama kloning).</entry>
     <entry lang="id" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Apakah Anda ingin membatalkan seluruh proses pembuatan sistem operasi tersembunyi?\n\nNote: Anda TIDAK akan dapat melanjutkan proses jika Anda membatalkannya sekarang.</entry>
     <entry lang="id" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Apakah Anda ingin membatalkan pra-uji enkripsi sistem?</entry>
-    <entry lang="id" key="BOOT_PRETEST_FAILED_RETRY">Pratest enkripsi sistem VeraCrypt gagal. Jika Anda memilih 'Tidak', komponen otentikasi pra-boot akan dihapus.\n\nNotes:\n\n-- Jika VeraCrypt Boot Loader tidak meminta Anda untuk memasukkan kata sandi sebelum Windows dimulai, ada kemungkinan bahwa sistem operasi Anda tidak boot dari drive tempat ia diinstal. Jika Anda menggunakan algoritma enkripsi selain AES dan tes pra-gagal (dan Anda memasukkan kata sandi), itu mungkin disebabkan oleh driver yang dirancang secara tidak tepat. Pilih 'Tidak', dan coba enkripsi partisi / drive sistem lagi, tetapi gunakan algoritma enkripsi AES (yang memiliki persyaratan memori terendah https://www.veracrypt.fr/en/Troubleshooting.html).</entry>
+    <entry lang="id" key="BOOT_PRETEST_FAILED_RETRY">Pratest enkripsi sistem VeraCrypt gagal. Jika Anda memilih 'Tidak', komponen otentikasi pra-boot akan dihapus.\n\nNotes:\n\n-- Jika VeraCrypt Boot Loader tidak meminta Anda untuk memasukkan kata sandi sebelum Windows dimulai, ada kemungkinan bahwa sistem operasi Anda tidak boot dari drive tempat ia diinstal. Jika Anda menggunakan algoritma enkripsi selain AES dan tes pra-gagal (dan Anda memasukkan kata sandi), itu mungkin disebabkan oleh driver yang dirancang secara tidak tepat. Pilih 'Tidak', dan coba enkripsi partisi / drive sistem lagi, tetapi gunakan algoritma enkripsi AES (yang memiliki persyaratan memori terendah https://veracrypt.jp/en/Troubleshooting.html).</entry>
     <entry lang="id" key="SYS_DRIVE_NOT_ENCRYPTED">Partisi / drive sistem tampaknya tidak dienkripsi (tidak sebagian atau seluruhnya).</entry>
     <entry lang="id" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Partisi / drive sistem Anda dienkripsi (sebagian atau seluruhnya). \n \nPlease mendekripsi partisi / drive sistem Anda sepenuhnya sebelum melanjutkan. Untuk melakukannya, pilih 'System' &gt; 'Permanen Decrypt System Partition /Drive' dari bilah menu jendela VeraCrypt utama.</entry>
     <entry lang="id" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">Ketika partisi / drive sistem dienkripsi (sebagian atau seluruhnya), Anda tidak dapat menurunkan VeraCrypt (tetapi Anda dapat meningkatkannya atau menginstal ulang versi yang sama).</entry>
@@ -1523,127 +1523,171 @@
     <entry lang="id" key="LINUX_NOT_SUPPORTED"> (tidak didukung oleh komponen yang tersedia di platform ini).</entry>
     <entry lang="id" key="LINUX_KERNEL_OLD">Sistem Anda menggunakan versi lama dari kernel Linux. Masalah ini dapat diselesaikan dengan memutakhirkan kernel ke versi 2.6.24 atau yang lebih baru.</entry>
     <entry lang="id" key="LINUX_VOL_UNMOUNTED">Volume {0} telah turun.</entry>
-    <entry lang="en" key="LINUX_VOL_MOUNTED">Volume {0} has been mounted.</entry>
+    <entry lang="id" key="LINUX_VOL_MOUNTED">Volume {0} telah dikaitkan.</entry>
     <entry lang="id" key="LINUX_OOM">Kehabisan memori.</entry>
-    <entry lang="id" key="LINUX_CANT_GET_ADMIN_PRIV">Gagal mendapatkan hak administrator</entry>
+    <entry lang="id" key="LINUX_CANT_GET_ADMIN_PRIV">Gagal mendapatkan hak administrator.</entry>
     <entry lang="id" key="LINUX_COMMAND_GET_ERROR">Perintah {0} mengembalikan kesalahan {1}.</entry>
-    <entry lang="id" key="LINUX_CMD_HELP">Bantuan Baris Perintah VeraCrypt</entry>
-    <entry lang="id" key="LINUX_HIDDEN_FILES_PRESENT_IN_KEYFILE_PATH">\n\nWarning: File tersembunyi hadir dalam jalur keyfile. Jika Anda perlu menggunakannya sebagai keyfiles, hapus titik terdepan dari nama file mereka. File tersembunyi hanya terlihat jika diaktifkan dalam opsi sistem.</entry>
-    <entry lang="id" key="LINUX_EX2MSG_DEVICESECTORSIZEMISMATCH">Perangkat penyimpanan dan ketidakcocokan ukuran sektor volume VC</entry>
-    <entry lang="id" key="LINUX_EX2MSG_ENCRYPTEDSYSTEMREQUIRED">Operasi ini harus dilakukan hanya ketika sistem yang dihosting pada volume berjalan.</entry>
+    <entry lang="id" key="LINUX_CMD_HELP">Bantuan Baris Perintah VeraCrypt.</entry>
+    <entry lang="id" key="LINUX_HIDDEN_FILES_PRESENT_IN_KEYFILE_PATH">\n\nPeringatan: Berkas tersembunyi ada di jalur berkas kunci. Jika Anda perlu menggunakannya sebagai berkas kunci, hapus titik di awal nama berkasnya. Berkas tersembunyi hanya terlihat jika diaktifkan pada opsi sistem.</entry>
+    <entry lang="id" key="LINUX_EX2MSG_DEVICESECTORSIZEMISMATCH">Ketidakcocokan ukuran sektor antara perangkat penyimpanan dan volume VC.</entry>
+    <entry lang="id" key="LINUX_EX2MSG_ENCRYPTEDSYSTEMREQUIRED">Operasi ini harus dilakukan hanya ketika sistem yang di-host pada volume tersebut sedang berjalan.</entry>
     <entry lang="id" key="LINUX_EX2MSG_INSUFFICIENTDATA">Tidak cukup data yang tersedia.</entry>
-    <entry lang="id" key="LINUX_EX2MSG_KERNELCRYPTOSERVICETESTFAILED">Uji layanan kriptografi kernel gagal. Layanan kriptografi kernel Anda kemungkinan besar tidak mendukung volume yang lebih besar dari 2 TB.\n\nPossible solutions:\n- Upgrade kernel Linux ke versi 2.6.33 atau yang lebih baru.\n- Nonaktifkan penggunaan layanan kriptografi kernel (Pengaturan &gt; Preferences &gt; System Integration) atau gunakan opsi mount 'nokernelcrypto' pada baris perintah.</entry>
+    <entry lang="id" key="LINUX_EX2MSG_KERNELCRYPTOSERVICETESTFAILED">Uji layanan kriptografi kernel gagal. Layanan kriptografi kernel Anda kemungkinan besar tidak mendukung volume yang lebih besar dari 2 TB.\n\nSolusi yang mungkin:\n- Tingkatkan kernel Linux ke versi 2.6.33 atau yang lebih baru.\n- Nonaktifkan penggunaan layanan kriptografi kernel (Pengaturan &gt; Preferensi &gt; Integrasi Sistem) atau gunakan opsi kait 'nokernelcrypto' pada baris perintah.</entry>
     <entry lang="id" key="LINUX_EX2MSG_LOOPDEVICESETUPFAILED">Gagal menyiapkan perangkat loop.</entry>
-    <entry lang="id" key="LINUX_EX2MSG_MISSINGARGUMENT">Argumen yang diperlukan kurang.</entry>
+    <entry lang="id" key="LINUX_EX2MSG_MISSINGARGUMENT">Argumen yang diperlukan tidak ada.</entry>
     <entry lang="id" key="LINUX_EX2MSG_MISSINGVOLUMEDATA">Data volume hilang.</entry>
-    <entry lang="id" key="LINUX_EX2MSG_MOUNTPOINTREQUIRED">Titik gunung diperlukan.</entry>
-    <entry lang="id" key="LINUX_EX2MSG_MOUNTPOINTUNAVAILABLE">Titik mount sudah digunakan.</entry>
-    <entry lang="id" key="LINUX_EX2MSG_PASSWORDEMPTY">Tidak ada kata sandi atau berkas kunci yang dinyatakan.</entry>
-    <entry lang="id" key="LINUX_EX2MSG_PASSWORDORKEYBOARDLAYOUTINCORRECT">\n\nNote bahwa kata sandi otentikasi pra-boot perlu diketik dalam lingkungan pra-boot di mana tata letak keyboard non-AS tidak tersedia. Oleh karena itu, kata sandi otentikasi pra-boot harus selalu diketik menggunakan tata letak keyboard standar AS (jika tidak, kata sandi akan diketik secara tidak benar dalam banyak kasus). Namun, perhatikan bahwa Anda TIDAK memerlukan keyboard AS yang nyata; Anda hanya perlu mengubah tata letak keyboard di sistem operasi Anda.</entry>
-    <entry lang="id" key="LINUX_EX2MSG_PASSWORDORMOUNTOPTIONSINCORRECT">\n\nNote: Jika Anda mencoba me-mount partisi yang terletak pada drive sistem terenkripsi tanpa otentikasi pra-boot atau untuk me-mount partisi sistem terenkripsi dari sistem operasi yang tidak berjalan, Anda dapat melakukannya dengan memilih 'Options &gt;' &gt; 'Mount partition using system encryption'.</entry>
-    <entry lang="id" key="LINUX_EX2MSG_PASSWORDTOOLONG">Kata sandi lebih panjang dari karakter {0}.</entry>
+    <entry lang="id" key="LINUX_EX2MSG_MOUNTPOINTREQUIRED">Titik kait diperlukan.</entry>
+    <entry lang="id" key="LINUX_EX2MSG_MOUNTPOINTUNAVAILABLE">Titik kait sudah digunakan.</entry>
+    <entry lang="id" key="LINUX_EX2MSG_PASSWORDEMPTY">Tidak ada kata sandi atau berkas kunci yang ditentukan.</entry>
+    <entry lang="id" key="LINUX_EX2MSG_PASSWORDORKEYBOARDLAYOUTINCORRECT">\n\nPerhatikan bahwa kata sandi autentikasi pra-boot perlu diketik dalam lingkungan pra-boot di mana tata letak papan ketik non-AS tidak tersedia. Oleh karena itu, kata sandi autentikasi pra-boot harus selalu diketik menggunakan tata letak papan ketik standar AS (jika tidak, kata sandi akan diketik secara tidak benar dalam banyak kasus). Namun, perhatikan bahwa Anda TIDAK memerlukan papan ketik AS yang nyata; Anda hanya perlu mengubah tata letak papan ketik di sistem operasi Anda.</entry>
+    <entry lang="id" key="LINUX_EX2MSG_PASSWORDORMOUNTOPTIONSINCORRECT">\n\nCatatan: Jika Anda mencoba mengaitkan partisi yang terletak pada drive sistem terenkripsi tanpa autentikasi pra-boot atau untuk mengaitkan partisi sistem terenkripsi dari sistem operasi yang tidak berjalan, Anda dapat melakukannya dengan memilih 'Opsi &gt;' &gt; 'Kaitkan partisi menggunakan enkripsi sistem'.</entry>
+    <entry lang="id" key="LINUX_EX2MSG_PASSWORDTOOLONG">Kata sandi lebih panjang dari {0} karakter.</entry>
     <entry lang="id" key="LINUX_EX2MSG_PARTITIONDEVICEREQUIRED">Perangkat partisi diperlukan.</entry>
-    <entry lang="id" key="LINUX_EX2MSG_PROTECTIONPASSWORDINCORRECT">Kata sandi yang salah untuk volume tersembunyi terproteksi atau volume tersembunyi tidak ada.</entry>
-    <entry lang="id" key="LINUX_EX2MSG_PROTECTIONPASSWORDKEYFILESINCORRECT">Berkas kunci dan/atau kata sandi ke volume tersembunyi terproteksi yang salah atau volume tersembunyi tidak ada.</entry>
+    <entry lang="id" key="LINUX_EX2MSG_PROTECTIONPASSWORDINCORRECT">Kata sandi yang salah untuk volume tersembunyi yang dilindungi atau volume tersembunyi tidak ada.</entry>
+    <entry lang="id" key="LINUX_EX2MSG_PROTECTIONPASSWORDKEYFILESINCORRECT">Berkas kunci dan/atau kata sandi yang salah untuk volume tersembunyi yang dilindungi atau volume tersembunyi tidak ada.</entry>
     <entry lang="id" key="LINUX_EX2MSG_STRINGCONVERSIONFAILED">Karakter yang tidak valid ditemui.</entry>
     <entry lang="id" key="LINUX_EX2MSG_STRINGFORMATTEREXCEPTION">Galat saat mengurai string terformat.</entry>
-    <entry lang="id" key="LINUX_EX2MSG_TEMPORARYDIRECTORYFAILURE">Gagal membuat file atau direktori di direktori sementara.\n\nPlease pastikan bahwa direktori sementara ada, izin keamanannya memungkinkan Anda mengaksesnya, dan ada ruang disk yang cukup.</entry>
-    <entry lang="id" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZEHIDDENVOLUMEPROTECTION">Kesalahan: Drive menggunakan ukuran sektor selain 512 byte.\n\nDue untuk keterbatasan komponen yang tersedia di platform Anda, volume luar yang dihosting pada drive tidak dapat dipasang menggunakan perlindungan volume tersembunyi.\n\n Solusi Yang Dapat diakses:\n- Gunakan drive dengan sektor 512-byte.\n- Buat volume file-hosted (kontainer) pada drive.\n-Backup isi volume tersembunyi dan kemudian perbarui volume luar.</entry>
-    <entry lang="id" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZENOKERNELCRYPTO">Kesalahan: Drive menggunakan ukuran sektor selain 512 byte.\n\nDue untuk keterbatasan komponen yang tersedia di platform Anda, volume partisi / perangkat yang dihosting pada drive hanya dapat dipasang menggunakan layanan kriptografi kernel.\n\n Solusi Yang Dapat diakses:\n- Aktifkan penggunaan layanan kriptografi kernel (Preferensi &gt; Integrasi Sistem).\n- Gunakan drive dengan sektor 512-byte.\n- Buat volume file-hosted (kontainer) pada drive.</entry>
-    <entry lang="id" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Kesalahan: Drive menggunakan ukuran sektor selain 512 byte.\n\nDue untuk keterbatasan komponen yang tersedia di platform Anda, volume partisi / perangkat yang dihosting tidak dapat dibuat / digunakan pada drive.\n\nPossible solutions:\n- Buat volume file-hosted (container) pada drive.\n- Gunakan drive dengan sektor 512-byte.\n- Gunakan VeraCrypt pada platform lain.</entry>
+    <entry lang="id" key="LINUX_EX2MSG_TEMPORARYDIRECTORYFAILURE">Gagal membuat berkas atau direktori di direktori sementara.\n\nHarap pastikan bahwa direktori sementara ada, izin keamanannya memungkinkan Anda mengaksesnya, dan ada ruang disk yang cukup.</entry>
+    <entry lang="id" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZEHIDDENVOLUMEPROTECTION">Kesalahan: Drive menggunakan ukuran sektor selain 512 byte.\n\nKarena keterbatasan komponen yang tersedia di platform Anda, volume luar yang di-host pada drive tidak dapat dikaitkan menggunakan perlindungan volume tersembunyi.\n\nSolusi yang mungkin:\n- Gunakan drive dengan sektor 512-byte.\n- Buat volume berbasis berkas (wadah) pada drive.\n- Cadangkan isi volume tersembunyi dan kemudian perbarui volume luar.</entry>
+    <entry lang="id" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZENOKERNELCRYPTO">Kesalahan: Drive menggunakan ukuran sektor selain 512 byte.\n\nKarena keterbatasan komponen yang tersedia di platform Anda, volume berbasis partisi/perangkat yang di-host pada drive hanya dapat dikaitkan menggunakan layanan kriptografi kernel.\n\nSolusi yang mungkin:\n- Aktifkan penggunaan layanan kriptografi kernel (Preferensi &gt; Integrasi Sistem).\n- Gunakan drive dengan sektor 512-byte.\n- Buat volume berbasis berkas (wadah) pada drive.</entry>
+    <entry lang="id" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Kesalahan: Drive menggunakan ukuran sektor selain 512 byte.\n\nKarena keterbatasan komponen yang tersedia di platform Anda, volume berbasis partisi/perangkat yang di-host tidak dapat dibuat/digunakan pada drive.\n\nSolusi yang mungkin:\n- Buat volume berbasis berkas (wadah) pada drive.\n- Gunakan drive dengan sektor 512-byte.\n- Gunakan VeraCrypt pada platform lain.</entry>
     <entry lang="id" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">Berkas/perangkat host sudah digunakan.</entry>
     <entry lang="id" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Slot volume tidak tersedia.</entry>
-    <entry lang="id" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt membutuhkan OSXFUSE 2.5 atau lebih tinggi.</entry>
-    <entry lang="id" key="EXCEPTION_OCCURRED">Terjadi eksepsi</entry>
-    <entry lang="id" key="ENTER_PASSWORD">Masukkan kata sandi</entry>
-    <entry lang="id" key="ENTER_TC_VOL_PASSWORD">Masukkan Kata Sandi Volume VeraCrypt</entry>
+    <entry lang="id" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt membutuhkan macFUSE 2.5 atau lebih tinggi.</entry>
+    <entry lang="id" key="EXCEPTION_OCCURRED">Terjadi eksepsi.</entry>
+    <entry lang="id" key="ENTER_PASSWORD">Masukkan kata sandi.</entry>
+    <entry lang="id" key="ENTER_TC_VOL_PASSWORD">Masukkan Kata Sandi Volume VeraCrypt.</entry>
     <entry lang="id" key="MOUNT">Kait</entry>
-    <entry lang="id" key="MOUNT_POINT">Kait Direktori"</entry>
-    <entry lang="id" key="NO_VOLUMES_MOUNTED">Tidak ada volume yang dikait.</entry>
-    <entry lang="id" key="OPEN_NEW_VOLUME">Nyatakan Volume VeraCrypt Baru</entry>
-    <entry lang="id" key="PARAMETER_INCORRECT">Parameter salah</entry>
-    <entry lang="id" key="SELECT_KEYFILES">Pilih Berkas Kunci</entry>
-    <entry lang="id" key="START_TC">Mulai VeraCrypt</entry>
-    <entry lang="id" key="VOLUME_ALREADY_MOUNTED">Volume {0} sudah dikait.</entry>
-    <entry lang="id" key="UNKNOWN_OPTION">Opsi tak dikenal</entry>
-    <entry lang="id" key="VOLUME_LOCATION">Lokasi Volume</entry>
-    <entry lang="id" key="VOLUME_HOST_IN_USE">PERINGATAN: File / perangkat host {0} sudah digunakan! \n\nIgnoring ini dapat menyebabkan hasil yang tidak diinginkan termasuk ketidakstabilan sistem. Semua aplikasi yang mungkin menggunakan file / perangkat host harus ditutup sebelum memasang volume.</entry>
-    <entry lang="en" key="CANT_INSTALL_WITH_EXE_OVER_MSI">VeraCrypt was previously installed using an MSI package and so it can't be updated using the standard installer.\n\nPlease use the MSI package to update your VeraCrypt installation.</entry>
-    <entry lang="en" key="IDC_USE_ALL_FREE_SPACE">Use all available free space</entry>
-    <entry lang="en" key="SYS_ENCRYPTION_UPGRADE_UNSUPPORTED_ALGORITHM">VeraCrypt cannot be upgraded because the system partition/drive was encrypted using an algorithm that is not supported anymore.\nPlease decrypt your system before upgrading VeraCrypt and then encrypt it again.</entry>
-    <entry lang="en" key="LINUX_EX2MSG_TERMINALNOTFOUND">Supported terminal application could not be found, you need either xterm, konsole or gnome-terminal (with dbus-x11).</entry>
-    <entry lang="en" key="IDM_MOUNT_NO_CACHE">Mount Without Cache</entry>
-    <entry lang="en" key="EXPANDER_INFO">:: VeraCrypt Expander ::\n\nExpand a VeraCrypt volume on the fly without reformatting\n\n\nAll kind of volumes (container files, disks and partitions) formatted with NTFS are supported. The only condition is that there must be enough free space on the host drive or host device of the VeraCrypt volume.\n\nDo not use this software to expand an outer volume containing a hidden volume, because this destroys the hidden volume!\n</entry>
-    <entry lang="en" key="IDC_STEPSEXPAND">1. Select the VeraCrypt volume to be expanded\n2. Click the 'Mount' button</entry>
-    <entry lang="en" key="IDT_VOL_NAME">Volume: </entry>
-    <entry lang="en" key="IDT_FILE_SYS">File system: </entry>
-    <entry lang="en" key="IDT_CURRENT_SIZE">Current size: </entry>
-    <entry lang="en" key="IDT_NEW_SIZE">New size: </entry>
-    <entry lang="en" key="IDT_NEW_SIZE_BOX_TITLE">Enter new volume size</entry>
-    <entry lang="en" key="IDC_INIT_NEWSPACE">Fill new space with random data</entry>
-    <entry lang="en" key="IDC_QUICKEXPAND">Quick Expand</entry>
-    <entry lang="en" key="IDT_INIT_SPACE">Fill new space: </entry>
-    <entry lang="en" key="EXPANDER_FREE_SPACE">%s free space available on host drive</entry>
-    <entry lang="en" key="EXPANDER_HELP_DEVICE">This is a device-based VeraCrypt volume.\n\nThe new volume size will be choosen automatically as the size of the host device.</entry>
-    <entry lang="en" key="EXPANDER_HELP_FILE">Please specify the new size of the VeraCrypt volume (must be at least %I64u KB larger than the current size).</entry>
-    <entry lang="en" key="QUICK_EXPAND_WARNING">WARNING: You should use Quick Expand only in the following cases:\n\n1) The device where the file container is located contains no sensitive data and you do not need plausible deniability.\n2) The device where the file container is located has already been securely and fully encrypted.\n\nAre you sure you want to use Quick Expand?</entry>
-    <entry lang="en" key="EXPANDER_STATUS_TEXT">IMPORTANT: Move your mouse as randomly as possible within this window. The longer you move it, the better. This significantly increases the cryptographic strength of the encryption keys. Then click 'Continue' to expand the volume.</entry>
-    <entry lang="en" key="EXPANDER_STATUS_TEXT_LEGACY">Click 'Continue' to expand the volume.</entry>
-    <entry lang="en" key="EXPANDER_FINISH_ERROR">Error: volume expansion failed.</entry>
-    <entry lang="en" key="EXPANDER_FINISH_ABORT">Error: operation aborted by user.</entry>
-    <entry lang="en" key="EXPANDER_FINISH_OK">Finished. Volume successfully expanded.</entry>
-    <entry lang="en" key="EXPANDER_CANCEL_WARNING">Warning: Volume expansion is in progress!\n\nStopping now may result in a damaged volume.\n\nDo you really want to cancel?</entry>
-    <entry lang="en" key="EXPANDER_STARTING_STATUS">Starting volume expansion ...\n</entry>
-    <entry lang="en" key="EXPANDER_HIDDEN_VOLUME_ERROR">An outer volume containing a hidden volume can't be expanded, because this destroys the hidden volume.\n</entry>
-    <entry lang="en" key="EXPANDER_SYSTEM_VOLUME_ERROR">A VeraCrypt system volume can't be expanded.</entry>
-    <entry lang="en" key="EXPANDER_NO_FREE_SPACE">Not enough free space to expand the volume</entry>
-    <entry lang="en" key="EXPANDER_WARNING_FILE_CONTAINER_JUNK">Warning: The container file is larger than the VeraCrypt volume area. The data after the VeraCrypt volume area will be overwritten.\n\nDo you want to continue?</entry>
-    <entry lang="en" key="EXPANDER_WARNING_FAT">Warning: The VeraCrypt volume contains a FAT file system!\n\nOnly the VeraCrypt volume itself will be expanded, but not the file system.\n\nDo you want to continue?</entry>
-    <entry lang="en" key="EXPANDER_WARNING_EXFAT">Warning: The VeraCrypt volume contains an exFAT file system!\n\nOnly the VeraCrypt volume itself will be expanded, but not the file system.\n\nDo you want to continue?</entry>
-    <entry lang="en" key="EXPANDER_WARNING_UNKNOWN_FS">Warning: The VeraCrypt volume contains an unknown or no file system!\n\nOnly the VeraCrypt volume itself will be expanded, the file system remains unchanged.\n\nDo you want to continue?</entry>
-    <entry lang="en" key="EXPANDER_ERROR_VOLUME_SIZE_TOO_SMALL">New volume size too small, must be at least %I64u kB larger than the current size.</entry>
-    <entry lang="en" key="EXPANDER_ERROR_VOLUME_SIZE_TOO_LARGE">New volume size too large, not enough space on host drive.</entry>
-    <entry lang="en" key="EXPANDER_ERROR_MAX_FILE_SIZE_EXCEEDED">Maximum file size of %I64u MB on host drive exceeded.</entry>
-    <entry lang="en" key="EXPANDER_ERROR_QUICKEXPAND_PRIVILEGES">Error: Failed to get necessary privileges to enable Quick Expand!\nPlease uncheck Quick Expand option and try again.</entry>
-    <entry lang="en" key="EXPANDER_ERROR_MAX_VC_VOLUME_SIZE_EXCEEDED">Maximum VeraCrypt volume size of %I64u TB exceeded!\n</entry>
-    <entry lang="en" key="FULL_FORMAT">Full Format</entry>
-    <entry lang="en" key="FAST_CREATE">Fast Create</entry>
-    <entry lang="en" key="WARN_FAST_CREATE">WARNING: You should use Fast Create only in the following cases:\n\n1) The device contains no sensitive data and you do not need plausible deniability.\n2) The device has already been securely and fully encrypted.\n\nAre you sure you want to use Fast Create?</entry>
-    <entry lang="en" key="IDC_ENABLE_EMV_SUPPORT">Enable EMV Support</entry>
-    <entry lang="en" key="COMMAND_APDU_INVALID">The APDU command sent to the card is not valid.</entry>
-    <entry lang="en" key="EXTENDED_APDU_UNSUPPORTED">Extended APDU commands cannot be used with the current token.</entry>
-    <entry lang="en" key="SCARD_MODULE_INIT_FAILED">Error when loading the WinSCard / PCSC library.</entry>
-    <entry lang="en" key="EMV_UNKNOWN_CARD_TYPE">The card in the reader is not a supported EMV card.</entry>
-    <entry lang="en" key="EMV_SELECT_AID_FAILED">The AID of the card in the reader could not be selected.</entry>
-    <entry lang="en" key="EMV_ICC_CERT_NOTFOUND">ICC Public Key Certificate was not found in the card.</entry>
-    <entry lang="en" key="EMV_ISSUER_CERT_NOTFOUND">Issuer Public Key Certificate was not found in the card.</entry>
-    <entry lang="en" key="EMV_CPLC_NOTFOUND">CPLC was not found in the EMV card.</entry>
-    <entry lang="en" key="EMV_PAN_NOTFOUND">No Primary Account Number (PAN) found in the EMV card.</entry>
-    <entry lang="en" key="INVALID_EMV_PATH">EMV path is invalid.</entry>
-    <entry lang="en" key="EMV_KEYFILE_DATA_NOTFOUND">Unable to build a keyfile from the EMV card's data.\n\nOne of the following is missing:\n- ICC Public Key Certificate.\n- Issuer Public Key Certificate.\n- CPLC data.</entry>
-    <entry lang="en" key="SCARD_W_REMOVED_CARD">No card in the reader.\n\nPlease make sure the card is correctly slotted.</entry>
-    <entry lang="en" key="FORMAT_EXTERNAL_FAILED">Windows format.com command failed to format the volume as NTFS/exFAT/ReFS: Error 0x%.8X.\n\nFalling back to using Windows FormatEx API.</entry>
-    <entry lang="en" key="FORMATEX_API_FAILED">Windows FormatEx API failed to format the volume as NTFS/exFAT/ReFS.\n\nFailure status = %s.</entry>
-    <entry lang="en" key="EXPANDER_WRITING_RANDOM_DATA">Writing random data to new space ...\n</entry>
-    <entry lang="en" key="EXPANDER_WRITING_ENCRYPTED_BACKUP">Writing re-encrypted backup header ...\n</entry>
-    <entry lang="en" key="EXPANDER_WRITING_ENCRYPTED_PRIMARY">Writing re-encrypted primary header ...\n</entry>
-    <entry lang="en" key="EXPANDER_WIPING_OLD_HEADER">Wiping old backup header ...\n</entry>
-    <entry lang="en" key="EXPANDER_MOUNTING_VOLUME">Mounting volume ...\n</entry>
-    <entry lang="en" key="EXPANDER_UNMOUNTING_VOLUME">Unmounting volume ...\n</entry>
-    <entry lang="en" key="EXPANDER_EXTENDING_FILESYSTEM">Extending file system ...\n</entry>
-    <entry lang="en" key="PARTIAL_SYSENC_MOUNT_READONLY">Warning: The system partition you attempted to mount was not fully encrypted. As a safety measure to prevent potential corruption or unwanted modifications, volume '%s' was mounted as read-only.</entry>
-    <entry lang="en" key="IDC_LINK_KEYFILES_EXTENSIONS_WARNING">Important information on using third-party file extensions</entry>
-    <entry lang="en" key="IDC_DISABLE_MEMORY_PROTECTION">Disable memory protection for Accessibility tools compatibility</entry>
-    <entry lang="en" key="DISABLE_MEMORY_PROTECTION_WARNING">WARNING: Disabling memory protection significantly reduces security. Enable this option ONLY if you rely on Accessibility tools, like Screen Readers, to interact with VeraCrypt's UI.</entry>
+    <entry lang="id" key="MOUNT_POINT">Kait Direktori</entry>
+    <entry lang="id" key="NO_VOLUMES_MOUNTED">Tidak ada volume yang dikaitkan.</entry>
+    <entry lang="id" key="OPEN_NEW_VOLUME">Tentukan Volume VeraCrypt Baru.</entry>
+    <entry lang="id" key="PARAMETER_INCORRECT">Parameter salah.</entry>
+    <entry lang="id" key="SELECT_KEYFILES">Pilih Berkas Kunci.</entry>
+    <entry lang="id" key="START_TC">Mulai VeraCrypt.</entry>
+    <entry lang="id" key="VOLUME_ALREADY_MOUNTED">Volume {0} sudah dikaitkan.</entry>
+    <entry lang="id" key="UNKNOWN_OPTION">Opsi tidak dikenal.</entry>
+    <entry lang="id" key="VOLUME_LOCATION">Lokasi Volume.</entry>
+    <entry lang="id" key="VOLUME_HOST_IN_USE">PERINGATAN: Berkas/perangkat host {0} sudah digunakan!\n\nMengabaikan ini dapat menyebabkan hasil yang tidak diinginkan termasuk ketidakstabilan sistem. Semua aplikasi yang mungkin menggunakan berkas/perangkat host harus ditutup sebelum mengaitkan volume.\n\nLanjutkan mengaitkan?</entry>
+    <entry lang="id" key="CANT_INSTALL_WITH_EXE_OVER_MSI">VeraCrypt sebelumnya diinstal menggunakan paket MSI sehingga tidak dapat diperbarui menggunakan penginstal standar.\n\nSilakan gunakan paket MSI untuk memperbarui instalasi VeraCrypt Anda.</entry>
+    <entry lang="id" key="IDC_USE_ALL_FREE_SPACE">Gunakan semua ruang kosong yang tersedia</entry>
+    <entry lang="id" key="SYS_ENCRYPTION_UPGRADE_UNSUPPORTED_ALGORITHM">VeraCrypt tidak dapat ditingkatkan karena partisi/drive sistem dienkripsi menggunakan algoritme yang tidak lagi didukung.\nSilakan dekripsi sistem Anda sebelum meningkatkan VeraCrypt lalu enkripsi kembali.</entry>
+    <entry lang="id" key="LINUX_EX2MSG_TERMINALNOTFOUND">Aplikasi terminal yang didukung tidak dapat ditemukan, Anda memerlukan xterm, konsole, atau gnome-terminal (dengan dbus-x11).</entry>
+    <entry lang="id" key="IDM_MOUNT_NO_CACHE">Kait Tanpa Cache</entry>
+    <entry lang="id" key="EXPANDER_INFO">:: VeraCrypt Expander ::\n\nPerluas volume VeraCrypt secara langsung tanpa memformat ulang\n\n\nSemua jenis volume (berkas wadah, disk, dan partisi) yang diformat dengan NTFS didukung. Satu-satunya syarat adalah harus ada ruang kosong yang cukup pada drive atau perangkat host volume VeraCrypt.\n\nJangan gunakan perangkat lunak ini untuk memperluas volume luar yang berisi volume tersembunyi, karena ini akan menghancurkan volume tersembunyi!\n</entry>
+    <entry lang="id" key="IDC_STEPSEXPAND">1. Pilih volume VeraCrypt yang akan diperluas\n2. Klik tombol 'Kait'</entry>
+    <entry lang="id" key="IDT_VOL_NAME">Volume: </entry>
+    <entry lang="id" key="IDT_FILE_SYS">Sistem berkas: </entry>
+    <entry lang="id" key="IDT_CURRENT_SIZE">Ukuran saat ini: </entry>
+    <entry lang="id" key="IDT_NEW_SIZE">Ukuran baru: </entry>
+    <entry lang="id" key="IDT_NEW_SIZE_BOX_TITLE">Masukkan ukuran volume baru</entry>
+    <entry lang="id" key="IDC_INIT_NEWSPACE">Isi ruang baru dengan data acak</entry>
+    <entry lang="id" key="IDC_QUICKEXPAND">Perluas Cepat</entry>
+    <entry lang="id" key="IDT_INIT_SPACE">Isi ruang baru: </entry>
+    <entry lang="id" key="EXPANDER_FREE_SPACE">%s ruang kosong tersedia di drive host.</entry>
+    <entry lang="id" key="EXPANDER_HELP_DEVICE">Ini adalah volume VeraCrypt berbasis perangkat.\n\nUkuran volume baru akan dipilih secara otomatis sesuai ukuran perangkat host.</entry>
+    <entry lang="id" key="EXPANDER_HELP_FILE">Silakan tentukan ukuran baru volume VeraCrypt (harus setidaknya %I64u KB lebih besar dari ukuran saat ini).</entry>
+    <entry lang="id" key="QUICK_EXPAND_WARNING">PERINGATAN: Anda sebaiknya hanya menggunakan Perluas Cepat dalam kasus berikut:\n\n1) Perangkat tempat berkas wadah berada tidak berisi data sensitif dan Anda tidak memerlukan penyangkalan yang masuk akal.\n2) Perangkat tempat berkas wadah berada sudah dienkripsi dengan aman dan sepenuhnya.\n\nApakah Anda yakin ingin menggunakan Perluas Cepat?</entry>
+    <entry lang="id" key="EXPANDER_STATUS_TEXT">PENTING: Gerakkan tetikus Anda seacak mungkin di dalam jendela ini. Semakin lama Anda menggerakkannya, semakin baik. Ini secara signifikan meningkatkan kekuatan kriptografi kunci enkripsi. Setelah itu, klik 'Lanjutkan' untuk memperluas volume.</entry>
+    <entry lang="id" key="EXPANDER_STATUS_TEXT_LEGACY">Klik 'Lanjutkan' untuk memperluas volume.</entry>
+    <entry lang="id" key="EXPANDER_FINISH_ERROR">Kesalahan: perluasan volume gagal.</entry>
+    <entry lang="id" key="EXPANDER_FINISH_ABORT">Kesalahan: operasi dibatalkan oleh pengguna.</entry>
+    <entry lang="id" key="EXPANDER_FINISH_OK">Selesai. Volume berhasil diperluas.</entry>
+    <entry lang="id" key="EXPANDER_CANCEL_WARNING">Peringatan: Proses perluasan volume sedang berlangsung!\n\nMenghentikan sekarang dapat menyebabkan volume rusak.\n\nApakah Anda yakin ingin membatalkan?</entry>
+    <entry lang="id" key="EXPANDER_STARTING_STATUS">Memulai perluasan volume ...\n</entry>
+    <entry lang="id" key="EXPANDER_HIDDEN_VOLUME_ERROR">Volume luar yang berisi volume tersembunyi tidak dapat diperluas, karena ini akan menghancurkan volume tersembunyi.\n</entry>
+    <entry lang="id" key="EXPANDER_SYSTEM_VOLUME_ERROR">Volume sistem VeraCrypt tidak dapat diperluas.</entry>
+    <entry lang="id" key="EXPANDER_NO_FREE_SPACE">Ruang kosong tidak cukup untuk memperluas volume.</entry>
+    <entry lang="id" key="EXPANDER_WARNING_FILE_CONTAINER_JUNK">Peringatan: Berkas wadah lebih besar dari area volume VeraCrypt. Data setelah area volume VeraCrypt akan ditimpa.\n\nApakah Anda ingin melanjutkan?</entry>
+    <entry lang="id" key="EXPANDER_WARNING_FAT">Peringatan: Volume VeraCrypt berisi sistem berkas FAT!\n\nHanya volume VeraCrypt itu sendiri yang akan diperluas, bukan sistem berkasnya.\n\nApakah Anda ingin melanjutkan?</entry>
+    <entry lang="id" key="EXPANDER_WARNING_EXFAT">Peringatan: Volume VeraCrypt berisi sistem berkas exFAT!\n\nHanya volume VeraCrypt itu sendiri yang akan diperluas, bukan sistem berkasnya.\n\nApakah Anda ingin melanjutkan?</entry>
+    <entry lang="id" key="EXPANDER_WARNING_UNKNOWN_FS">Peringatan: Volume VeraCrypt berisi sistem berkas yang tidak dikenal atau tidak ada sistem berkas!\n\nHanya volume VeraCrypt itu sendiri yang akan diperluas, sistem berkas tetap tidak berubah.\n\nApakah Anda ingin melanjutkan?</entry>
+    <entry lang="id" key="EXPANDER_ERROR_VOLUME_SIZE_TOO_SMALL">Ukuran volume baru terlalu kecil, harus setidaknya %I64u KiB lebih besar dari ukuran saat ini.</entry>
+    <entry lang="id" key="EXPANDER_ERROR_VOLUME_SIZE_TOO_LARGE">Ukuran volume baru terlalu besar, ruang di drive host tidak mencukupi.</entry>
+    <entry lang="id" key="EXPANDER_ERROR_MAX_FILE_SIZE_EXCEEDED">Ukuran berkas maksimum %I64u MB pada drive host terlampaui.</entry>
+    <entry lang="id" key="EXPANDER_ERROR_QUICKEXPAND_PRIVILEGES">Kesalahan: Gagal mendapatkan hak istimewa yang diperlukan untuk mengaktifkan Perluas Cepat!\nSilakan hapus centang opsi Perluas Cepat dan coba lagi.</entry>
+    <entry lang="id" key="EXPANDER_ERROR_MAX_VC_VOLUME_SIZE_EXCEEDED">Ukuran maksimum volume VeraCrypt sebesar %I64u TB terlampaui!\n</entry>
+    <entry lang="id" key="FULL_FORMAT">Format Penuh</entry>
+    <entry lang="id" key="FAST_CREATE">Buat Cepat</entry>
+    <entry lang="id" key="WARN_FAST_CREATE">PERINGATAN: Anda sebaiknya hanya menggunakan Buat Cepat dalam kasus berikut:\n\n1) Perangkat tidak berisi data sensitif dan Anda tidak memerlukan penyangkalan yang masuk akal.\n2) Perangkat sudah dienkripsi dengan aman dan sepenuhnya.\n\nApakah Anda yakin ingin menggunakan Buat Cepat?</entry>
+    <entry lang="id" key="IDC_ENABLE_EMV_SUPPORT">Aktifkan Dukungan EMV</entry>
+    <entry lang="id" key="COMMAND_APDU_INVALID">Perintah APDU yang dikirim ke kartu tidak valid.</entry>
+    <entry lang="id" key="EXTENDED_APDU_UNSUPPORTED">Perintah APDU diperluas tidak dapat digunakan dengan token saat ini.</entry>
+    <entry lang="id" key="SCARD_MODULE_INIT_FAILED">Kesalahan saat memuat pustaka WinSCard / PCSC.</entry>
+    <entry lang="id" key="EMV_UNKNOWN_CARD_TYPE">Kartu di pembaca bukan kartu EMV yang didukung.</entry>
+    <entry lang="id" key="EMV_SELECT_AID_FAILED">AID dari kartu di pembaca tidak dapat dipilih.</entry>
+    <entry lang="id" key="EMV_ICC_CERT_NOTFOUND">Sertifikat Kunci Publik ICC tidak ditemukan di kartu.</entry>
+    <entry lang="id" key="EMV_ISSUER_CERT_NOTFOUND">Sertifikat Kunci Publik Penerbit tidak ditemukan di kartu.</entry>
+    <entry lang="id" key="EMV_CPLC_NOTFOUND">CPLC tidak ditemukan di kartu EMV.</entry>
+    <entry lang="id" key="EMV_PAN_NOTFOUND">Tidak ditemukan Nomor Rekening Utama (PAN) di kartu EMV.</entry>
+    <entry lang="id" key="INVALID_EMV_PATH">Jalur EMV tidak valid.</entry>
+    <entry lang="id" key="EMV_KEYFILE_DATA_NOTFOUND">Tidak dapat membuat berkas kunci dari data kartu EMV.\n\nSalah satu dari berikut ini hilang:\n- Sertifikat Kunci Publik ICC.\n- Sertifikat Kunci Publik Penerbit.\n- Data CPLC.</entry>
+    <entry lang="id" key="SCARD_W_REMOVED_CARD">Tidak ada kartu di pembaca.\n\nHarap pastikan kartu sudah terpasang dengan benar.</entry>
+    <entry lang="id" key="FORMAT_EXTERNAL_FAILED">Perintah format.com Windows gagal memformat volume sebagai NTFS/exFAT/ReFS: Kesalahan 0x%.8X.\n\nMenggunakan Windows FormatEx API sebagai alternatif.</entry>
+    <entry lang="id" key="FORMATEX_API_FAILED">Windows FormatEx API gagal memformat volume sebagai NTFS/exFAT/ReFS.\n\nStatus kegagalan = %s.</entry>
+    <entry lang="id" key="EXPANDER_WRITING_RANDOM_DATA">Menulis data acak ke ruang baru ...\n</entry>
+    <entry lang="id" key="EXPANDER_WRITING_ENCRYPTED_BACKUP">Menulis header cadangan terenkripsi ulang ...\n</entry>
+    <entry lang="id" key="EXPANDER_WRITING_ENCRYPTED_PRIMARY">Menulis header utama terenkripsi ulang ...\n</entry>
+    <entry lang="id" key="EXPANDER_WIPING_OLD_HEADER">Menghapus header cadangan lama ...\n</entry>
+    <entry lang="id" key="EXPANDER_MOUNTING_VOLUME">Mengaitkan volume ...\n</entry>
+    <entry lang="id" key="EXPANDER_UNMOUNTING_VOLUME">Melepas kait volume ...\n</entry>
+    <entry lang="id" key="EXPANDER_EXTENDING_FILESYSTEM">Memperluas sistem berkas ...\n</entry>
+    <entry lang="id" key="PARTIAL_SYSENC_MOUNT_READONLY">Peringatan: Partisi sistem yang Anda coba kaitkan tidak terenkripsi sepenuhnya. Sebagai langkah pengamanan untuk mencegah potensi kerusakan atau modifikasi yang tidak diinginkan, volume '%s' dikaitkan sebagai hanya-baca.</entry>
+    <entry lang="id" key="IDC_LINK_KEYFILES_EXTENSIONS_WARNING">Informasi penting tentang penggunaan ekstensi berkas pihak ketiga</entry>
+    <entry lang="id" key="IDC_DISABLE_MEMORY_PROTECTION">Nonaktifkan perlindungan memori untuk kompatibilitas alat Aksesibilitas</entry>
+    <entry lang="id" key="DISABLE_MEMORY_PROTECTION_WARNING">PERINGATAN: Menonaktifkan perlindungan memori secara signifikan mengurangi keamanan. Aktifkan opsi ini HANYA jika Anda bergantung pada alat Aksesibilitas, seperti Pembaca Layar, untuk berinteraksi dengan antarmuka VeraCrypt.</entry>
     <entry lang="id" key="LINUX_LANGUAGE">Bahasa</entry>
-    <entry lang="en" key="LINUX_SELECT_SYS_DEFAULT_LANG">Select system's default language</entry>
-    <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="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="id" key="LINUX_SELECT_SYS_DEFAULT_LANG">Pilih bahasa default sistem</entry>
+    <entry lang="id" key="LINUX_RESTART_FOR_LANGUAGE_CHANGE">Agar perubahan bahasa berlaku, VeraCrypt perlu dimulai ulang.</entry>
+    <entry lang="id" key="ERR_XTS_MASTERKEY_VULNERABLE">PERINGATAN: Kunci induk volume rentan terhadap serangan yang mengompromikan keamanan data.\n\nSilakan buat volume baru dan transfer data ke dalamnya.</entry>
+    <entry lang="id" key="ERR_SYSENC_XTS_MASTERKEY_VULNERABLE">PERINGATAN: Kunci induk sistem terenkripsi rentan terhadap serangan yang mengompromikan keamanan data.\nSilakan dekripsi partisi/drive sistem kemudian enkripsi ulang.</entry>
+    <entry lang="id" key="ERR_XTS_MASTERKEY_VULNERABLE_SHORT">PERINGATAN: Kunci induk volume memiliki kerentanan keamanan.</entry>
+    <entry lang="id" key="MOUNTPOINT_BLOCKED">KESALAHAN: Titik kait volume diblokir karena menimpa direktori sistem yang dilindungi.\n\nSilakan pilih titik kait lain.</entry>
+    <entry lang="id" key="MOUNTPOINT_NOTALLOWED">KESALAHAN: Titik kait volume tidak diizinkan karena menimpa direktori yang merupakan bagian dari variabel lingkungan PATH.\n\nSilakan pilih titik kait lain.</entry>
+    <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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" />
@@ -122,7 +122,7 @@
     <entry lang="it" key="IDC_ENABLE_HARDWARE_ENCRYPTION">Accelera la codifica/decodifica AES usando le istruzioni AES del processore (se disponibili)</entry>
     <entry lang="it" key="IDC_ENABLE_KEYFILES">Usa file chiave</entry>
     <entry lang="it" key="IDC_ENABLE_NEW_KEYFILES">Usa file chiave</entry>
-    <entry lang="it" key="IDC_EXIT">Chiudi</entry>
+    <entry lang="it" key="IDC_EXIT">Esci</entry>
     <entry lang="it" key="IDC_FAVORITES_HELP_LINK">Guida sui volumi preferiti</entry>
     <entry lang="it" key="IDC_FAVORITE_DISABLE_HOTKEY">Non montare il volume selezionato quando il tasto di scorciatoia 'Monta volumi preferiti' &amp;viene premuto</entry>
     <entry lang="it" key="IDC_FAVORITE_MOUNT_ON_ARRIVAL">Montare il volume selezionato quando la sua periferica ospite viene &amp;connessa</entry>
@@ -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>
@@ -744,7 +744,7 @@
     <entry lang="it" key="LABEL">Etichetta</entry>
     <entry lang="it" key="CLUSTER_TOO_SMALL">La dimensione del cluster selezionata è troppo piccola per la dimensione di questo volume. Verrà usata una dimensione del cluster maggiore.</entry>
     <entry lang="it" key="CANT_GET_VOLSIZE">ERRORE: impossibile leggere la dimensione del volume!\n\nAssicurarsi che il volume selezionato non sia usato dal sistema o dalle applicazioni.</entry>
-    <entry lang="it" key="HIDDEN_VOL_HOST_SPARSE">I volumi ignoti non devono essere creati all'interno di contenitore dinamici(file sparsi). Per consentire la negabilità plausibile, il volume nascosto deve essere creato in un contenitore non dinamico.</entry>
+    <entry lang="it" key="HIDDEN_VOL_HOST_SPARSE">I volumi ignoti non devono essere creati all'interno di contenitore dinamici(file sparsi). Per consentire la negazione plausibile, il volume nascosto deve essere creato in un contenitore non dinamico.</entry>
     <entry lang="it" key="HIDDEN_VOL_HOST_UNSUPPORTED_FILESYS">La procedura di creazione del volume VeraCrypt può creare un voume nascosto solo all’interno di un volume FAT oppure NTFS.</entry>
     <entry lang="it" key="HIDDEN_VOL_HOST_UNSUPPORTED_FILESYS_WIN2000">In ambiente operativo Windows 2000, la procedura di creazione del volume di VeraCrypt può creare un volume nascosto solamente in un volume FAT.</entry>
     <entry lang="it" key="HIDDEN_VOL_HOST_NTFS">Nota: Il file system FAT è più adeguato per i volumi esterni che il file system NTFS (per esempio, la dimensione massima possibile per il volume nascosto può essere significativamente molto grande se il volume esterno è stato formattato come FAT).</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>
@@ -855,7 +855,7 @@
     <entry lang="it" key="TC_INSTALLER_IS_RUNNING">L’installer di VeraCrypt è attualmente in esecuzione in questo sistema ed esegue o prepara l’installazione oppure aggiornamento di VeraCrypt. Prima di procedere, attendere per finire o chiudere esso. Se non potete chiudere l’installer, riavviare i computer prima di procedere.</entry>
     <entry lang="it" key="INSTALL_FAILED">Installazione fallita.</entry>
     <entry lang="it" key="UNINSTALL_FAILED">Disinstallazione fallita.</entry>
-    <entry lang="it" key="DIST_PACKAGE_CORRUPTED">Questo pacchetto di distribuzione è danneggiato. Provare a scaricarlo nuovamente (preferibilmente dal sito ufficiale di VeraCrypt all’indirizzo https://www.veracrypt.fr).</entry>
+    <entry lang="it" key="DIST_PACKAGE_CORRUPTED">Questo pacchetto di distribuzione è danneggiato. Provare a scaricarlo nuovamente (preferibilmente dal sito ufficiale di VeraCrypt all’indirizzo https://veracrypt.jp).</entry>
     <entry lang="it" key="CANNOT_WRITE_FILE_X">Impossibile scrivere il file %s</entry>
     <entry lang="it" key="EXTRACTING_VERB">Estrazione</entry>
     <entry lang="it" key="CANNOT_READ_FROM_PACKAGE">Impossibile leggere i dati dal pacchetto.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="it" key="HIDDEN_OS_CREATION_PREINFO_HELP">Nei passi successivi, VeraCrypt creerà il sistema operativo nascosto copiando il contenuto della partizione di sistema nel volume nascosto (i dati in copia saranno Codificati al volo con una chiave di codifica differente da quella usata per il sistema operativo di richiamo).\n\nNotate che il processo sarà eseguito in ambiente di pre-boot(prima dell’avvio di Windows) e può impiegare molto tempo per essere completato; diverse ore o anche diversi giorni (a seconda della dimensione della partizione di sistema e dalle prestazioni del vostro computer).\n\nVoi potrete interrompere il processo, spegnere il vostro computer, avviare il sistema operativo e riavviare il processo. Comunque, se interrompete tale processo, l’intera procedura di copia del sistema dovrà ripartire dall’inizio (perché il contenuto della partizione di sistema non deve cambiare durante la clonazione).</entry>
     <entry lang="it" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Volete annullare l’intero processo di creazione del sistema operativo nascosto?\n\nNota: NON potrete ripristinare il processo se lo annullate adesso.</entry>
     <entry lang="it" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Volete annullare il pre-test per la codifica di sistema?</entry>
-    <entry lang="it" key="BOOT_PRETEST_FAILED_RETRY">La richiesta di codifica di sistema VeraCrypt è fallita. Volete ritentare?\n\nSelezionando 'No', il componente di autenticazione in pre-boot sarà disinstallato.\n\nNota:\n\n- Se il Boot Loader di VeraCrypt non vi richiede di digitare la password prima dell'avvio di Windows, è possibile che il vostro sistema operativo non si it is avvia dall'unità nella quale esso è installato. Questo non è supportato.\n\n- Se usate un algoritmo di cifratura diverso di AES e la richiesta è fallita (ed avete digitato la password), questo è stato causato da un driver designato inadeguatamente. Selezionare 'No', e ritentare la cifratura della partizione/unità di sistema, usando l'algoritmo di codifica AES (che ha dei requisiti di memoria inferiori).\n\n- Per più possibili cause e soluzioni, visitare: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="it" key="BOOT_PRETEST_FAILED_RETRY">La richiesta di codifica di sistema VeraCrypt è fallita. Volete ritentare?\n\nSelezionando 'No', il componente di autenticazione in pre-boot sarà disinstallato.\n\nNota:\n\n- Se il Boot Loader di VeraCrypt non vi richiede di digitare la password prima dell'avvio di Windows, è possibile che il vostro sistema operativo non si it is avvia dall'unità nella quale esso è installato. Questo non è supportato.\n\n- Se usate un algoritmo di cifratura diverso di AES e la richiesta è fallita (ed avete digitato la password), questo è stato causato da un driver designato inadeguatamente. Selezionare 'No', e ritentare la cifratura della partizione/unità di sistema, usando l'algoritmo di codifica AES (che ha dei requisiti di memoria inferiori).\n\n- Per più possibili cause e soluzioni, visitare: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="it" key="SYS_DRIVE_NOT_ENCRYPTED">La partizione/disco di sistema non sembra essere criptato (né parzialmente né interamente).</entry>
     <entry lang="it" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">La vostra partizione/disco di sistema è criptato (parzialmente o completamente).\n\nDeCodificate la vostra partizione/disco interamente prima di procedere. Per fare questo, selezionate 'Sistema'&gt;'Decodifica definitivamente la partizione/disco di sistema' dal menu della barra strumenti della finestra principale di VeraCrypt.</entry>
     <entry lang="it" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">Quando la partizione/unità di sistema è crittata (parzialmente o totalmente), non potete tornare ad una precedente versione di VeraCrypt (ma potete aggiornare o reinstallare la stessa versione di esso).</entry>
@@ -1510,7 +1510,7 @@
     <entry lang="it" key="LINUX_DYNAMIC_NOTICE">Tieni presente che se il sistema operativo non alloca i file dall'inizio dello spazio libero, e quindi la dimensione massima possibile del volume nascosto potrebbe essere molto inferiore alla dimensione dello spazio libero sul volume esterno.\nQuesto non è un bug in VeraCrypt ma una limitazione del sistema operativo.</entry>
     <entry lang="it" key="LINUX_MAX_HIDDEN_SIZE">La dimensione massima del volume nascosto possibile per questo volume è {0}.</entry>
     <entry lang="it" key="LINUX_OPEN_OUTER_VOL">Apri il volume esterno</entry>
-    <entry lang="it" key="LINUX_OUTER_VOL_IS_MOUNTED">Il volume esterno è stato creato e montato correttamente come '{0}'.\nIn questo volume dovresti ora copiare alcuni file dall'aspetto sensibile che in realtà NON vuoi nascondere.\nI file saranno lì per chiunque ti costringa a rivelare la tua password.\nRivelerai solo la password per questo volume esterno, non per quello nascosto.\nI file a cui tieni davvero verranno archiviati nel volume nascosto, che verrà creato in seguito.\nAl termine della copia, fare clic su Avanti. Non smontare il volume.\nNota: dopo aver fatto selezionato 'Avanti', il volume esterno verrà analizzato per determinare la dimensione dell'area ininterrotta di spazio libero la cui estremità è allineata con l'estremità del volume.\nQuest'area ospiterà il volume nascosto, quindi limiterà la sua dimensione massima possibile.\nLa procedura garantisce che nessun dato sul volume esterno venga sovrascritto dal volume nascosto.</entry>
+    <entry lang="it" key="LINUX_OUTER_VOL_IS_MOUNTED">Il volume esterno è stato creato e montato correttamente come '{0}'.\nIn questo volume dovresti ora copiare alcuni file dall'aspetto sensibile che in realtà NON vuoi nascondere.\nI file saranno lì per chiunque ti costringa a rivelare la tua password.\nRivelerai solo la password per questo volume esterno, non per quello nascosto.\nI file a cui tieni davvero verranno archiviati nel volume nascosto, che verrà creato in seguito.\nAl termine della copia, fare clic su Avanti. Non smontare il volume.\nNota: dopo aver selezionato 'Avanti', il volume esterno verrà analizzato per determinare la dimensione dell'area ininterrotta di spazio libero la cui estremità è allineata con l'estremità del volume.\nQuest'area ospiterà il volume nascosto, quindi limiterà la sua dimensione massima possibile.\nLa procedura garantisce che nessun dato sul volume esterno venga sovrascritto dal volume nascosto.</entry>
     <entry lang="it" key="LINUX_ERROR_TRY_ENCRYPT_SYSTEM_DRIVE">Errore: stai tentando di crittografare un'unità di sistema.\n\nVeraCrypt può crittografare un'unità di sistema solo in Windows.</entry>
     <entry lang="it" key="LINUX_ERROR_TRY_ENCRYPT_SYSTEM_PARTITION">Errore: stai tentando di crittografare una partizione di sistema.\n\nVeraCrypt può crittografare le partizioni di sistema solo in Windows.</entry>
     <entry lang="it" key="LINUX_WARNING_FORMAT_DESTROY_FS">ATTENZIONE: la formattazione del dispositivo eliminerà tutti i dati sul filesystem '{0}'.\n\nVuoi continuare?</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="it" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Errore: l'unità usa una dimensione del settore diversa da 512 byte.\n\nA causa delle limitazioni dei componenti disponibili nella piattaforma, non è possibile creare/usare volumi ospitati in una partizione/dispositivo nell'unità.\n\nPossibili soluzioni:\n- Creare nell'unità un volume (contenitore) ospitato da un file.\n- Usare un'unità con settori da 512 byte.\n- Usare VeraCrypt in un'altra piattaforma.</entry>
     <entry lang="it" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">Il file/dispositivo host è già in uso.</entry>
     <entry lang="it" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Slot volume non disponibile.</entry>
-    <entry lang="it" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt richiede OSXFUSE 2.5 o superiore.</entry>
+    <entry lang="it" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt richiede macFUSE 2.5 o superiore.</entry>
     <entry lang="it" key="EXCEPTION_OCCURRED">Si è verificata un'eccezione</entry>
     <entry lang="it" key="ENTER_PASSWORD">Inserire password</entry>
     <entry lang="it" key="ENTER_TC_VOL_PASSWORD">Digita la password del volume VeraCrypt</entry>
@@ -1608,7 +1608,7 @@
     <entry lang="it" key="EXPANDER_ERROR_MAX_VC_VOLUME_SIZE_EXCEEDED">Dimensione massima del volume VeraCrypt di %I64u TB superata!\n</entry>
     <entry lang="it" key="FULL_FORMAT">Formato Completo</entry>
     <entry lang="it" key="FAST_CREATE">Creazione Veloce</entry>
-    <entry lang="it" key="WARN_FAST_CREATE">ATTENZIONE: Dovrebbe usare la Creazione Veloce solo nei seguenti casi:\n\n1) Il dispositivo non contiene dati sensibili e non ha bisogno di negazione plausibile.\n2) Il dispositivo è già stato crittografato in modo sicuro e completamente.\n\nÈ sicuro di voler usare la Creazione Veloce?</entry>
+    <entry lang="it" key="WARN_FAST_CREATE">ATTENZIONE: Dovrebbe usare la Creazione Veloce solo nei seguenti casi:\n\n1) Il dispositivo non contiene dati sensibili e non richiede la negazione plausibile.\n2) Il dispositivo è già stato crittografato in modo sicuro e completamente.\n\nSei sicuro di voler usare la Creazione Veloce?</entry>
     <entry lang="it" key="IDC_ENABLE_EMV_SUPPORT">Abilita Supporto EMV</entry>
     <entry lang="it" key="COMMAND_APDU_INVALID">Il comando APDU inviato alla carta non è valido.</entry>
     <entry lang="it" key="EXTENDED_APDU_UNSUPPORTED">I comandi APDU estesi non possono essere utilizzati con il token corrente.</entry>
@@ -1620,10 +1620,10 @@
     <entry lang="it" key="EMV_CPLC_NOTFOUND">CPLC non è stato trovato nella carta EMV.</entry>
     <entry lang="it" key="EMV_PAN_NOTFOUND">Nessun Numero di Conto Primario (PAN) trovato nella carta EMV.</entry>
     <entry lang="it" key="INVALID_EMV_PATH">Il percorso EMV non è valido.</entry>
-    <entry lang="it" key="EMV_KEYFILE_DATA_NOTFOUND">Impossibile creare un file chiave dai dati della carta EMV.\n\nUno dei seguenti è mancante:\n- Certificato di Chiave Pubblica ICC.\n- Certificato di Chiave Pubblica dell'Emittente.\n- Dati CPLC.</entry>
+    <entry lang="it" key="EMV_KEYFILE_DATA_NOTFOUND">Impossibile generare un file chiave dai dati della carta EMV.\n\nUno dei seguenti è mancante:\n- Certificato di Chiave Pubblica ICC.\n- Certificato di Chiave Pubblica dell'Emittente.\n- Dati CPLC.</entry>
     <entry lang="it" key="SCARD_W_REMOVED_CARD">Nessuna carta nel lettore.\n\nAssicurati che la carta sia correttamente inserita.</entry>
-    <entry lang="it" key="FORMAT_EXTERNAL_FAILED">Il comando format.com di Windows non è riuscito a formattare il volume come NTFS/exFAT/ReFS: Errore 0x%.8X.\n\nRitorno all'uso dell'API FormatEx di Windows.</entry>
-    <entry lang="it" key="FORMATEX_API_FAILED">L'API FormatEx di Windows non è riuscita a formattare il volume come NTFS/exFAT/ReFS.\n\nStato di fallimento = %s.</entry>
+    <entry lang="it" key="FORMAT_EXTERNAL_FAILED">Il comando format.com di Windows non è riuscito a formattare il volume come NTFS/exFAT/ReFS: Errore 0x%.8X.\n\nSi passerà all'uso dell'API FormatEx di Windows.</entry>
+    <entry lang="it" key="FORMATEX_API_FAILED">L'API FormatEx di Windows non è riuscita a formattare il volume come NTFS/exFAT/ReFS.\n\nCodice di errore = %s.</entry>
     <entry lang="it" key="EXPANDER_WRITING_RANDOM_DATA">Scrittura di dati casuali nel nuovo spazio ...\n</entry>
     <entry lang="it" key="EXPANDER_WRITING_ENCRYPTED_BACKUP">Scrittura dell'header di backup ricrittografato ...\n</entry>
     <entry lang="it" key="EXPANDER_WRITING_ENCRYPTED_PRIMARY">Scrittura dell'header primario ricrittografato ...\n</entry>
@@ -1631,19 +1631,63 @@
     <entry lang="it" key="EXPANDER_MOUNTING_VOLUME">Montaggio del volume ...\n</entry>
     <entry lang="it" key="EXPANDER_UNMOUNTING_VOLUME">Smontaggio del volume ...\n</entry>
     <entry lang="it" key="EXPANDER_EXTENDING_FILESYSTEM">Estensione del file system ...\n</entry>
-    <entry lang="it" key="PARTIAL_SYSENC_MOUNT_READONLY">Avviso: La partizione di sistema che hai tentato di montare non è stata completamente crittografata. Come misura di sicurezza per prevenire potenziali corruzioni o modifiche indesiderate, il volume '%s' è stato montato come di sola lettura.</entry>
+    <entry lang="it" key="PARTIAL_SYSENC_MOUNT_READONLY">Avviso: La partizione di sistema che hai tentato di montare non è stata completamente crittografata. Come misura di sicurezza per prevenire possibili danneggiamenti o modifiche indesiderate, il volume '%s' è stato montato come di sola lettura.</entry>
     <entry lang="it" key="IDC_LINK_KEYFILES_EXTENSIONS_WARNING">Informazioni importanti sull'uso delle estensioni di file di terze parti</entry>
     <entry lang="it" key="IDC_DISABLE_MEMORY_PROTECTION">Disabilita la protezione della memoria per la compatibilità con gli strumenti di accessibilità</entry>
-    <entry lang="it" key="DISABLE_MEMORY_PROTECTION_WARNING">ATTENZIONE: Disabilitare la protezione della memoria riduce significativamente la sicurezza. Abilita questa opzione SOLO se fai affidamento su strumenti di accessibilità, come Screen Readers, per interagire con l'interfaccia utente di VeraCrypt.</entry>
+    <entry lang="it" key="DISABLE_MEMORY_PROTECTION_WARNING">ATTENZIONE: Disabilitare la protezione della memoria riduce significativamente la sicurezza. Attiva questa opzione SOLO se fai affidamento su strumenti di accessibilità, come Screen Readers, per interagire con l'interfaccia utente di VeraCrypt.</entry>
     <entry lang="it" key="LINUX_LANGUAGE">Lingua</entry>
     <entry lang="it" key="LINUX_SELECT_SYS_DEFAULT_LANG">Seleziona la lingua predefinita del sistema</entry>
     <entry lang="it" key="LINUX_RESTART_FOR_LANGUAGE_CHANGE">Perché il cambio di lingua abbia effetto, VeraCrypt deve essere riavviato.</entry>
-    <entry lang="it" key="ERR_XTS_MASTERKEY_VULNERABLE">ATTENZIONE: La chiave master del volume è vulnerabile a un attacco che compromette la sicurezza dei dati.\n\nSi prega di creare un nuovo volume e trasferire i dati in esso.</entry>
-    <entry lang="it" key="ERR_SYSENC_XTS_MASTERKEY_VULNERABLE">ATTENZIONE: La chiave master del sistema crittografato è vulnerabile a un attacco che compromette la sicurezza dei dati.\nSi prega di decrittografare la partizione/unità di sistema e poi ricrittografarla.</entry>
+    <entry lang="it" key="ERR_XTS_MASTERKEY_VULNERABLE">ATTENZIONE: La chiave master del volume è vulnerabile a un attacco che compromette la sicurezza dei dati.\n\nSi consiglia di creare un nuovo volume e trasferirvi i dati.</entry>
+    <entry lang="it" key="ERR_SYSENC_XTS_MASTERKEY_VULNERABLE">ATTENZIONE: La chiave master del sistema crittografato è vulnerabile a un attacco che compromette la sicurezza dei dati.\nSi prega di decrittografare la partizione/unità di sistema e quindi crittografarla nuovamente.</entry>
     <entry lang="it" key="ERR_XTS_MASTERKEY_VULNERABLE_SHORT">ATTENZIONE: La chiave master del volume ha una vulnerabilità di sicurezza.</entry>
-    <entry lang="it" key="MOUNTPOINT_BLOCKED">ERRORE: Il punto di montaggio del volume è bloccato perché sovrascrive una directory di sistema protetta.\n\nSi prega di scegliere un punto di montaggio diverso.</entry>
-    <entry lang="it" key="MOUNTPOINT_NOTALLOWED">ERRORE: Il punto di montaggio del volume non è consentito perché sovrascrive una directory che fa parte della variabile d'ambiente PATH.\n\nSi prega di scegliere un punto di montaggio diverso.</entry>
+    <entry lang="it" key="MOUNTPOINT_BLOCKED">ERRORE: Il punto di montaggio del volume è bloccato perché sovrascrive una directory di sistema protetta.\n\nScegli un punto di montaggio diverso.</entry>
+    <entry lang="it" key="MOUNTPOINT_NOTALLOWED">ERRORE: Il punto di montaggio del volume non è consentito perché sovrascrive una directory che fa parte della variabile d'ambiente PATH.\n\nScegli un punto di montaggio diverso.</entry>
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="ja" key="TC_INSTALLER_IS_RUNNING">現在VeraCryptインストーラが起動しており、インストールあるいはアップデートの実行中です。インストーラの処理が終わるのを待つか、閉じるかしてください。閉じることができない場合は再起動してください。</entry>
     <entry lang="ja" key="INSTALL_FAILED">インストールに失敗しました。</entry>
     <entry lang="ja" key="UNINSTALL_FAILED">アンインストールに失敗しました。</entry>
-    <entry lang="ja" key="DIST_PACKAGE_CORRUPTED">この配布パッケージは破損しています。（なるべくVeraCryptの公式サイト https://www.veracrypt.fr から）もう一度ダウンロードしてみてください。</entry>
+    <entry lang="ja" key="DIST_PACKAGE_CORRUPTED">この配布パッケージは破損しています。（なるべくVeraCryptの公式サイト https://veracrypt.jp から）もう一度ダウンロードしてみてください。</entry>
     <entry lang="ja" key="CANNOT_WRITE_FILE_X">ファイル %s を書き込めません。</entry>
     <entry lang="ja" key="EXTRACTING_VERB">展開</entry>
     <entry lang="ja" key="CANNOT_READ_FROM_PACKAGE">パッケージからデータを読み込めません。</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="ja" key="HIDDEN_OS_CREATION_PREINFO_HELP">次のステップで、VeraCryptはシステムパーティションから隠しボリュームへファイルをコピーすることで隠しOS領域を作成します（囮OS領域とは別の暗号鍵で即時暗号化しながらコピーします）。\n\nこの処理はWindows起動前の環境で行われ、完了するまでに長時間かかることに注意してください。処理時間はシステムパーティションのサイズやコンピュータの性能にもよりますが、数時間から数日かかることもあります。\n\nこの処理を途中で中断し、コンピュータを再起動した後にあらためて再開することも可能です。ただし、もし処理を中断した場合は、システムのコピー処理からやり直しになります。これはシステムパーティションとコピー先の内容を同一にするために必要です。</entry>
     <entry lang="ja" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">隠しOSの作成をキャンセルしますか？\n\nここで処理をキャンセルした場合、後で処理を再開することはできません。</entry>
     <entry lang="ja" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">システム暗号化の予備検査をキャンセルしますか？</entry>
-    <entry lang="ja" key="BOOT_PRETEST_FAILED_RETRY">VeraCryptのシステム暗号化予備検査に失敗しました。もう一度予備検査をしますか？\n\nもし「いいえ」を選んだ場合、起動前認証用コンポーネントがアンインストールされます。\n\n注：\n\n- もしVeraCryptブートローダーがWindowsが起動する前にパスワードの入力を要求してこなかった場合、ブートローダーがインストールされたのではないドライブからOSが起動している可能性があります。このケースには対応していません。\n\n- もしAES以外の暗号化アルゴリズムを使って予備検査に失敗した（そしてパスワードは入力した）場合、不適切な設計のドライバーに起因している可能性があります。「いいえ」を選択し、システムパーティション/ドライブをAESを使って暗号化しなおしてみてください（メモリ使用量が最少になります）。\n\n- その他に考えられる原因や対処方法については、https://www.veracrypt.fr/en/Troubleshooting.html をご覧ください。</entry>
+    <entry lang="ja" key="BOOT_PRETEST_FAILED_RETRY">VeraCryptのシステム暗号化予備検査に失敗しました。もう一度予備検査をしますか？\n\nもし「いいえ」を選んだ場合、起動前認証用コンポーネントがアンインストールされます。\n\n注：\n\n- もしVeraCryptブートローダーがWindowsが起動する前にパスワードの入力を要求してこなかった場合、ブートローダーがインストールされたのではないドライブからOSが起動している可能性があります。このケースには対応していません。\n\n- もしAES以外の暗号化アルゴリズムを使って予備検査に失敗した（そしてパスワードは入力した）場合、不適切な設計のドライバーに起因している可能性があります。「いいえ」を選択し、システムパーティション/ドライブをAESを使って暗号化しなおしてみてください（メモリ使用量が最少になります）。\n\n- その他に考えられる原因や対処方法については、https://veracrypt.jp/en/Troubleshooting.html をご覧ください。</entry>
     <entry lang="ja" key="SYS_DRIVE_NOT_ENCRYPTED">システムパーティション/ドライブは部分的にも全体的にも暗号化されていないようです。</entry>
     <entry lang="ja" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">システムパーティション/デバイスは暗号化されています（部分的あるいは全体的）。\n\n処理を進める前にシステムパーティション/デバイス全体の暗号化を解除してください。VeraCryptのメインウィンドウのメニューから[システム]-[暗号化の解除]を選択することで解除できます。</entry>
     <entry lang="ja" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">システムパーティション/ドライブが部分的であれ全体であれ暗号化されている場合は、VeraCryptをダウングレードできません。ただしアップグレードあるいは同じバージョンでの再インストールは可能です。</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="ja" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">エラー: ドライブは 512 バイト以外のセクターサイズを使用しています。\n\nプラットフォームで利用可能なコンポーネントの制限により、ドライブ上でパーティション/デバイスホスト型ボリュームを作成/使用できません。\n\n考えられる解決策:\n- ドライブにファイルホスト型ボリューム（コンテナ）を作成します。\n- 512 バイトセクターのドライブを使用します。\n- 別のプラットフォームで VeraCrypt を使用します。</entry>
     <entry lang="ja" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">ホストファイル/デバイスはすでに使用されています。</entry>
     <entry lang="ja" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">ボリュームスロットは使用できません。</entry>
-    <entry lang="ja" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt には OSXFUSE 2.5 以上が必要です。</entry>
+    <entry lang="ja" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt には macFUSE 2.5 以上が必要です。</entry>
     <entry lang="ja" key="EXCEPTION_OCCURRED">例外が発生しました</entry>
     <entry lang="ja" key="ENTER_PASSWORD">パスワードの入力</entry>
     <entry lang="ja" key="ENTER_TC_VOL_PASSWORD">VeraCryptボリュームのパスワードの入力</entry>
@@ -1644,6 +1644,50 @@
     <entry lang="ja" key="MOUNTPOINT_BLOCKED">エラー: ボリュームのマウントポイントは、保護されたシステムディレクトリと競合するためブロックされました。\n\n別のマウントポイントを選択してください。</entry>
     <entry lang="ja" key="MOUNTPOINT_NOTALLOWED">エラー: ボリュームのマウントポイントは、PATH環境変数に含まれるディレクトリを上書きするため使用できません。\n\n別のマウントポイントを選択してください。</entry>
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="en" key="TC_INSTALLER_IS_RUNNING">VeraCrypt Installer is currently running on this system and performing or preparing installation or update of VeraCrypt. Before you proceed, please wait for it to finish or close it. If you cannot close it, please restart your computer before proceeding.</entry>
     <entry lang="ka" key="INSTALL_FAILED">ინსტალაცია ჩაიშალა.</entry>
     <entry lang="ka" key="UNINSTALL_FAILED">დეინსტალაცია ჩაიშალა.</entry>
-    <entry lang="ka" key="DIST_PACKAGE_CORRUPTED">ეს საინსტალაციო პაკეტი დაზიანებულია. გთხოვთ, ხელახლან ჩამოტვირთოთ (უმჯობესია ოფიციალური საიტიდან https://www.veracrypt.fr).</entry>
+    <entry lang="ka" key="DIST_PACKAGE_CORRUPTED">ეს საინსტალაციო პაკეტი დაზიანებულია. გთხოვთ, ხელახლან ჩამოტვირთოთ (უმჯობესია ოფიციალური საიტიდან https://veracrypt.jp).</entry>
     <entry lang="ka" key="CANNOT_WRITE_FILE_X">ფაილის %s ჩაწერა არ ხერხდება</entry>
     <entry lang="ka" key="EXTRACTING_VERB">დეარქივაცია</entry>
     <entry lang="ka" key="CANNOT_READ_FROM_PACKAGE">პაკეტიდან მონაცემთა წაკითხვა არ ხერხდება.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="en" key="HIDDEN_OS_CREATION_PREINFO_HELP">In the next steps, VeraCrypt will create the hidden operating system by copying the content of the system partition to the hidden volume (data being copied will be encrypted on the fly with an encryption key different from the one that will be used for the decoy operating system).\n\nPlease note that the process will be performed in the pre-boot environment (before Windows starts) and it may take a long time to complete; several hours or even several days (depending on the size of the system partition and on the performance of your computer).\n\nYou will be able to interrupt the process, shut down your computer, start the operating system and then resume the process. However, if you interrupt it, the entire process of copying the system will have to start from the beginning (because the content of the system partition must not change during cloning).</entry>
     <entry lang="en" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Do you want to cancel the entire process of creation of the hidden operating system?\n\nNote: You will NOT be able to resume the process if you cancel it now.</entry>
     <entry lang="ka" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">გსურთ სისტემის შიფრაციისწინა ტესტირების შეწყვეტა?</entry>
-    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="ka" key="SYS_DRIVE_NOT_ENCRYPTED">სისტემური განაყოფი/დისკი არ არის დაშიფრული (ნაწილობრივ ან მთლიანად).</entry>
     <entry lang="ka" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">სისტემური განაყოფი/დისკი დაშიფრულია (ნაწილობრივ ან მთლიანად).\n\nგაგრძელებამდე გთხოვთ, დეშიფრაცია გაუკეთოთ მთლიანად სისტემურ განაყოფს/დისკს. ამისათვის, აირჩიეთ პროგრამის მენიუში "სისტემა" &gt; "სისტემური განაყოფის/დისკის სამუდამო დეშიფრაცია".</entry>
     <entry lang="en" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">When the system partition/drive is encrypted (partially or fully), you cannot downgrade VeraCrypt (but you can upgrade it or reinstall the same version).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="en" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Error: The drive uses a sector size other than 512 bytes.\n\nDue to limitations of components available on your platform, partition/device-hosted volumes cannot be created/used on the drive.\n\nPossible solutions:\n- Create a file-hosted volume (container) on the drive.\n- Use a drive with 512-byte sectors.\n- Use VeraCrypt on another platform.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">The host file/device is already in use.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Volume slot unavailable.</entry>
-    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires OSXFUSE 2.5 or above.</entry>
+    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires macFUSE 2.5 or above.</entry>
     <entry lang="en" key="EXCEPTION_OCCURRED">Exception occurred</entry>
     <entry lang="en" key="ENTER_PASSWORD">Enter password</entry>
     <entry lang="en" key="ENTER_TC_VOL_PASSWORD">Enter VeraCrypt Volume Password</entry>
@@ -1644,6 +1644,50 @@
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="ko" key="TC_INSTALLER_IS_RUNNING">VeraCrypt Installer가 현재이 시스템에서 실행 중이며 VeraCrypt의 설치 또는 업데이트를 수행 중이거나 준비 중입니다. 진행하기 전에 끝내거나 닫을 때까지 기다리세요. 컴퓨터를 닫을 수없는 경우 계속하기 전에 컴퓨터를 다시 시작하세요.</entry>
     <entry lang="ko" key="INSTALL_FAILED">설치가 실패했습니다.</entry>
     <entry lang="ko" key="UNINSTALL_FAILED">제거에 실패했습니다.</entry>
-    <entry lang="ko" key="DIST_PACKAGE_CORRUPTED">이 배포 패키지가 손상되었습니다. 다시 VeraCrypt 웹 사이트 (https://www.veracrypt.fr)에서 다운로드하세요.</entry>
+    <entry lang="ko" key="DIST_PACKAGE_CORRUPTED">이 배포 패키지가 손상되었습니다. 다시 VeraCrypt 웹 사이트 (https://veracrypt.jp)에서 다운로드하세요.</entry>
     <entry lang="ko" key="CANNOT_WRITE_FILE_X">%s 파일을 쓸 수 없습니다</entry>
     <entry lang="ko" key="EXTRACTING_VERB">적출</entry>
     <entry lang="ko" key="CANNOT_READ_FROM_PACKAGE">패키지에서 데이터를 읽을 수 없습니다.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="ko" key="HIDDEN_OS_CREATION_PREINFO_HELP">다음 단계에서 VeraCrypt는 시스템 파티션의 내용을 숨겨진 볼륨에 복사하여 숨겨진 운영 체제를 만듭니다(복사되는 데이터는 디코이 운영 체제에 사용될 암호화 키와 다른 암호화 키로 즉시 암호화됩니다).\n\nWindows를 시작하기 전에 사전 부트 환경에서 프로세스가 수행되며 완료하는 데 시간이 오래 걸릴 수 있습니다(시스템 파티션 크기와 컴퓨터의 성능에 따라 다름).\n\n프로세스를 중단하고 컴퓨터를 종료하고 운영 체제를 시작한 다음 프로세스를 다시 시작할 수 있습니다. 그러나 시스템을 중단하면 시스템 파티션의 내용이 복제하는 동안 변경되어서는 안 되기 때문에 전체 복사 프로세스가 처음부터 시작되어야 합니다.</entry>
     <entry lang="ko" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">숨겨진 운영 체제의 전체 생성 프로세스를 취소하시겠습니까?\n\n참고: 지금 취소하면 프로세스를 재개할 수 없습니다.</entry>
     <entry lang="ko" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">시스템 암호화 사전 테스트를 취소하시겠습니까?</entry>
-    <entry lang="ko" key="BOOT_PRETEST_FAILED_RETRY">VeraCrypt 시스템 암호화 사전 테스트에 실패했습니다. 다시 시도 하시겠습니까?\n\n'아니요'를 선택하면 사전 부트 인증 구성 요소가 제거됩니다.\n\n알림:\n\n- VeraCrypt 부트로더가 Windows를 시작하기 전에 암호를 입력하라는 메시지를 표시하지 않은 경우 운영 체제가 설치된 드라이브에서 부팅되지 않을 수 있습니다. 지원되지 않습니다.\n\n- AES 이외의 암호화 알고리즘을 사용했지만 사전 테스트에 실패했으며 암호를 입력했다면 드라이버가 잘못 설계되어 발생한 것일 수 있습니다. '아니요'를 선택하고 다시 시스템 파티션/드라이브 암호화를 시도하지만 메모리 요구 사항이 가장 낮은 AES 암호화 알고리즘을 사용합니다.\n\n- 가능한 원인과 해결 방법은 https://www.veracrypt.fr/en/Troubleshooting.html을 참조합니다.</entry>
+    <entry lang="ko" key="BOOT_PRETEST_FAILED_RETRY">VeraCrypt 시스템 암호화 사전 테스트에 실패했습니다. 다시 시도 하시겠습니까?\n\n'아니요'를 선택하면 사전 부트 인증 구성 요소가 제거됩니다.\n\n알림:\n\n- VeraCrypt 부트로더가 Windows를 시작하기 전에 암호를 입력하라는 메시지를 표시하지 않은 경우 운영 체제가 설치된 드라이브에서 부팅되지 않을 수 있습니다. 지원되지 않습니다.\n\n- AES 이외의 암호화 알고리즘을 사용했지만 사전 테스트에 실패했으며 암호를 입력했다면 드라이버가 잘못 설계되어 발생한 것일 수 있습니다. '아니요'를 선택하고 다시 시스템 파티션/드라이브 암호화를 시도하지만 메모리 요구 사항이 가장 낮은 AES 암호화 알고리즘을 사용합니다.\n\n- 가능한 원인과 해결 방법은 https://veracrypt.jp/en/Troubleshooting.html을 참조합니다.</entry>
     <entry lang="ko" key="SYS_DRIVE_NOT_ENCRYPTED">시스템 파티션/드라이브가 부분적으로 또는 완전히 암호화되지 않은 것 같습니다.</entry>
     <entry lang="ko" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">시스템 파티션/드라이브가 부분적으로 또는 완전히 암호화됩니다.\n\n계속하기 전에 시스템 파티션/드라이브의 암호를 완전히 해독해 주십시오. 이렇게 하려면 기본 VeraCrypt 창의 메뉴 모음에서 '시스템' &gt; '시스템 파티션/드라이브 영구 해독'을 선택합니다.</entry>
     <entry lang="ko" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">시스템 파티션/드라이브가 부분적으로 또는 완전히 암호화되면 VeraCrypt를 다운그레이드할 수 없지만 업그레이드하거나 동일한 버전을 다시 설치할 수 있습니다.</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="ko" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">오류: 드라이브 섹터가 512 바이트가 아닌 크기를 사용합니다.\n\n사용가능한 플랫폼 구성요소의 제한으로 인해 드라이브 혹은 장치에 호스트된 볼륨을 이 장치에서 생성하거나 사용할 수 없습니다.\n\n가능한 해결책:\n- 파일 호스트 볼륨(컨테이너)를 생성합니다.\n- 512 바이트를 섹터 크기로 사용하는 드라이브를 사용하세요.\n- 다른 플랫폼에서 VeraCrypt를 사용하세요.</entry>
     <entry lang="ko" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">호스트 파일이나 장치가 이미 사용 중입니다.</entry>
     <entry lang="ko" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">볼륨 슬롯이 사용가능하지 않습니다.</entry>
-    <entry lang="ko" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt는 OSXFUSE 2.5 혹은 더 높은 버전을 필요로 합니다.</entry>
+    <entry lang="ko" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt는 macFUSE 2.5 혹은 더 높은 버전을 필요로 합니다.</entry>
     <entry lang="ko" key="EXCEPTION_OCCURRED">예외 발생</entry>
     <entry lang="ko" key="ENTER_PASSWORD">비밀번호 입력</entry>
     <entry lang="ko" key="ENTER_TC_VOL_PASSWORD">VeraCrypt 볼륨 비밀번호 입력</entry>
@@ -1644,6 +1644,50 @@
     <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="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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="en" key="TC_INSTALLER_IS_RUNNING">VeraCrypt Installer is currently running on this system and performing or preparing installation or update of VeraCrypt. Before you proceed, please wait for it to finish or close it. If you cannot close it, please restart your computer before proceeding.</entry>
     <entry lang="en" key="INSTALL_FAILED">Installation failed.</entry>
     <entry lang="en" key="UNINSTALL_FAILED">Uninstallation failed.</entry>
-    <entry lang="en" key="DIST_PACKAGE_CORRUPTED">This distribution package is damaged. Please try downloading it again (preferably from the official VeraCrypt website at https://www.veracrypt.fr).</entry>
+    <entry lang="en" key="DIST_PACKAGE_CORRUPTED">This distribution package is damaged. Please try downloading it again (preferably from the official VeraCrypt website at https://veracrypt.jp).</entry>
     <entry lang="en" key="CANNOT_WRITE_FILE_X">Cannot write file %s</entry>
     <entry lang="en" key="EXTRACTING_VERB">Extracting</entry>
     <entry lang="en" key="CANNOT_READ_FROM_PACKAGE">Cannot read data from the package.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="en" key="HIDDEN_OS_CREATION_PREINFO_HELP">In the next steps, VeraCrypt will create the hidden operating system by copying the content of the system partition to the hidden volume (data being copied will be encrypted on the fly with an encryption key different from the one that will be used for the decoy operating system).\n\nPlease note that the process will be performed in the pre-boot environment (before Windows starts) and it may take a long time to complete; several hours or even several days (depending on the size of the system partition and on the performance of your computer).\n\nYou will be able to interrupt the process, shut down your computer, start the operating system and then resume the process. However, if you interrupt it, the entire process of copying the system will have to start from the beginning (because the content of the system partition must not change during cloning).</entry>
     <entry lang="en" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Do you want to cancel the entire process of creation of the hidden operating system?\n\nNote: You will NOT be able to resume the process if you cancel it now.</entry>
     <entry lang="en" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Do you want to cancel the system encryption pretest?</entry>
-    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="en" key="SYS_DRIVE_NOT_ENCRYPTED">The system partition/drive does not appear to be encrypted (neither partially nor fully).</entry>
     <entry lang="en" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Your system partition/drive is encrypted (partially or fully).\n\nPlease decrypt your system partition/drive entirely before proceeding. To do so, select 'System' &gt; 'Permanently Decrypt System Partition/Drive' from the menu bar of the main VeraCrypt window.</entry>
     <entry lang="en" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">When the system partition/drive is encrypted (partially or fully), you cannot downgrade VeraCrypt (but you can upgrade it or reinstall the same version).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="en" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Error: The drive uses a sector size other than 512 bytes.\n\nDue to limitations of components available on your platform, partition/device-hosted volumes cannot be created/used on the drive.\n\nPossible solutions:\n- Create a file-hosted volume (container) on the drive.\n- Use a drive with 512-byte sectors.\n- Use VeraCrypt on another platform.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">The host file/device is already in use.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Volume slot unavailable.</entry>
-    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires OSXFUSE 2.5 or above.</entry>
+    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires macFUSE 2.5 or above.</entry>
     <entry lang="en" key="EXCEPTION_OCCURRED">Exception occurred</entry>
     <entry lang="en" key="ENTER_PASSWORD">Enter password</entry>
     <entry lang="en" key="ENTER_TC_VOL_PASSWORD">Enter VeraCrypt Volume Password</entry>
@@ -1644,6 +1644,50 @@
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -857,7 +857,7 @@
     <entry lang="my" key="TC_INSTALLER_IS_RUNNING">VeraCrypt ဆော့ဗ်ဝဲ ထည့်သွင်းစနစ်သည် လောလောဆယ် ဤစက်ပေါ်၌ အလုပ်လုပ်နေပြီး စက်ထဲ ထည့်သွင်းရန် ပြင်ဆင်နေသည် (သို့) VeraCrypt မွမ်းမံချက်ကို လုပ်ဆောင်နေသည်။ ရှေ့ဆက် မသွားမီ၊ ၄င်းပြီးဆုံးသည့်အထိ စောင့်ဆိုင်းပါ (သို့) ပိတ်လိုက်ပါ။ အကယ်၍ ပိတ် မရပါက ကွန်ပြူတာကို ပြန်ဖွင့်ပါ။</entry>
     <entry lang="my" key="INSTALL_FAILED">စက်ထဲ ထည့်သွင်းမှု မအောင်မြင်ပါ။</entry>
     <entry lang="my" key="UNINSTALL_FAILED">ဖယ်ထုတ်မှု မအောင်မြင်ပါ။</entry>
-    <entry lang="my" key="DIST_PACKAGE_CORRUPTED">ဖြန့်ချီသော ဖိုင်ထုတ် ပျက်စီးနေသည်။ ထပ်မံ၍ ဒေါင်းလုဒ် ဆွဲယူပါ (တရား၀င် VeraCrypt ကွန်ရက် စာမျက်နှာ https://www.veracrypt.fr ၌ ရယူရန် ပိုသင့်လျှော်သည်)။ </entry>
+    <entry lang="my" key="DIST_PACKAGE_CORRUPTED">ဖြန့်ချီသော ဖိုင်ထုတ် ပျက်စီးနေသည်။ ထပ်မံ၍ ဒေါင်းလုဒ် ဆွဲယူပါ (တရား၀င် VeraCrypt ကွန်ရက် စာမျက်နှာ https://veracrypt.jp ၌ ရယူရန် ပိုသင့်လျှော်သည်)။ </entry>
     <entry lang="my" key="CANNOT_WRITE_FILE_X">%s ဖိုင်ကို ရေး၍ မရပါ</entry>
     <entry lang="my" key="EXTRACTING_VERB">ဖြည်ချနေသည်</entry>
     <entry lang="my" key="CANNOT_READ_FROM_PACKAGE">ဒေတာများကို ဖိုင်ထုတ်ထဲမှ ဖတ်၍ မရပါ။</entry>
@@ -1231,7 +1231,7 @@
     <entry lang="my" key="HIDDEN_OS_CREATION_PREINFO_HELP">နောက်အဆင့်များတွင်၊ VeraCrypt သည် ကွန်ပျူတာစနစ် အခန်းကန့်ထဲရှိ အကြောင်းအရာများကို လျှို့ဝှက် volume ထဲ ကော်ပီကူးခြင်းဖြင့် လျှို့ဝှက် OS စနစ်ကို ဖန်တီးသွားမည် ဖြစ်သည် (ကော်ပီးကူးနေသည့် ဒေတာများကို မျက်လှည့် OS စနစ်အတွက် အသုံးပြုမည့် ကီးနှင့် မတူသော စာဝှက်စနစ် ကီးတစ်ခုဖြင့် ချက်ခြင်း စာဝှက်ပေးမည် ဖြစ်သည်)။\n\nစက်မတက်မီ အခြေအနေ (Windows မဖွင့်မီ) တွင် လုပ်ငန်းစဉ်ကို လုပ်ဆောင်သွားမည် ဖြစ်ပြီး ပြီးစီးရန် (ကွန်ပျူတာ အခန်းကန့် အရွယ်အစားနှင့် စွမ်းဆောင်ရည်တို့အပေါ် မူတည်ပြီး) အ​ချိန်အတော်ကြာ ယူမည် ဖြစ်သည် - နာရီ အတော်ကြာ (သို့) ရက်အတန်ကြာ ဖြစ်နိုင်သည်။\n\nဤလုပ်ငန်းစဉ်ကို သင် ရပ်ဆိုင်းနိုင်သည်။ ကွန်ပျူတာကို စက်ပိတ်ထားနိုင်သည်။ OS စနစ်ကို စဖွင့်ပြီး လုပ်ငန်းစဉ်ကို ပြန်စနိုင်သည်။ သို့သော်၊ ၄င်းကို ရပ်ဆိုင်းလိုက်ပါက၊ ကွန်ပျူတာစနစ် ကော်ပီ လုပ်ခြင်း လုပ်ငန်းစဉ် တစ်ခုလုံးကို အစမှ ပြန်လည် စတင်ရမည် ဖြစ်သည် (အဘယ်ကြောင့် ဆိုသော် ကွန်ပျူတာစနစ် အခန်းကန့်ရှိ အကြောင်းအရာသည် ကိုယ်ပွား ပြုလုပ်နေစဉ် ပြောင်းလဲမည် မဟုတ်သောကြောင့် ဖြစ်သည်)</entry>
     <entry lang="my" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">လျှို့ဝှက် OS စနစ် ဖန်တီးမှု လုပ်ငန်းစဉ် တစ်ခုလုံးကို ဖျက်သိမ်းရန် အလိုရှိသလား?\n\nမှတ်ချက် - အကယ်၍ ၄င်းကို ယခု ဖျက်သိမ်းပါက လုပ်ငန်းစဉ်ကို ပြန်စနိုင်မည် မဟုတ်ပါ။</entry>
     <entry lang="my" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">ကွန်ပျူတာစနစ် စာဝှက်ခြင်း အကြို စမ်းသပ်ချက်ကို ဖျက်သိမ်းလိုသလား?</entry>
-    <entry lang="my" key="BOOT_PRETEST_FAILED_RETRY">VeraCrypt စနစ် စာဝှက်ခြင်း အကြို စမ်းသပ်ချက် မအောင်မြင်ပါ။ သင် ထပ်မံ ကြိုးစားလိုသလား?\n\nအကယ်၍ 'မဟုတ်ပါ' ကို ရွေးချယ်ပါက၊ စက်မတင်မီ စစ်ဆေးအတည်ပြုချက် အစိတ်အပိုင်းကို ဖယ်ထုတ်သွားမည် ဖြစ်သည်။\n\nမှတ်ချက်များ - \n\n- အကယ်၍ Windows မတက်မီ VeraCrypt Boot Loader က စကားဝှက် ရေးထည့်ရန် မတောင်းပါက၊ သင့် OS စနစ်သည် ၄င်းကို ထည့်သွင်းထားသော drive မှ boot မတက်၍ ဖြစ်မည်။ ဤအချက်အတွက် ပံ့ပိုးမထားပါ။\n\n- အကယ်၍ သင်သည် AES ကို မသုံးပဲ စာဝှက်စနစ် အယ်လဂိုရီသမ် တစ်ခုကို အသုံးပြုပြီး အကြို စမ်းသပ်ချက် မအောင်မြင်ပါက (စကားဝှက် ရေးထည့်သော်လည်း)၊ စနစ်တကျ စီမံရေးသားခြင်း မပြုသော ဒရိုင်ဘာ တစ်ခုကြောင့် ဖြစ်နိုင်သည်။ 'မဟုတ်ပါ' ကို ရွေးပြီး၊ ကွန်ပျူတာစနစ် အခန်းကန့်/drive ကို ထပ်မံ စာဝှက်ကြည့်ပါ၊ သို့သော် AES စာဝှက်စနစ် အယ်လဂိုရီသမ်ကို အသုံးပြုပါ (၄င်း၌ မှတ်ဉာဏ် လုပ်အပ်ချက် အနိမ့်ဆုံး ရှိသည်)။\n\nဖြစ်နိုင်ချေ အကြောင်းရင်းများနှင့် ဖြေရှင်းချက်များအတွက်၊ https://www.veracrypt.fr/en/Troubleshooting.html ကို လေ့လာပါ။</entry>
+    <entry lang="my" key="BOOT_PRETEST_FAILED_RETRY">VeraCrypt စနစ် စာဝှက်ခြင်း အကြို စမ်းသပ်ချက် မအောင်မြင်ပါ။ သင် ထပ်မံ ကြိုးစားလိုသလား?\n\nအကယ်၍ 'မဟုတ်ပါ' ကို ရွေးချယ်ပါက၊ စက်မတင်မီ စစ်ဆေးအတည်ပြုချက် အစိတ်အပိုင်းကို ဖယ်ထုတ်သွားမည် ဖြစ်သည်။\n\nမှတ်ချက်များ - \n\n- အကယ်၍ Windows မတက်မီ VeraCrypt Boot Loader က စကားဝှက် ရေးထည့်ရန် မတောင်းပါက၊ သင့် OS စနစ်သည် ၄င်းကို ထည့်သွင်းထားသော drive မှ boot မတက်၍ ဖြစ်မည်။ ဤအချက်အတွက် ပံ့ပိုးမထားပါ။\n\n- အကယ်၍ သင်သည် AES ကို မသုံးပဲ စာဝှက်စနစ် အယ်လဂိုရီသမ် တစ်ခုကို အသုံးပြုပြီး အကြို စမ်းသပ်ချက် မအောင်မြင်ပါက (စကားဝှက် ရေးထည့်သော်လည်း)၊ စနစ်တကျ စီမံရေးသားခြင်း မပြုသော ဒရိုင်ဘာ တစ်ခုကြောင့် ဖြစ်နိုင်သည်။ 'မဟုတ်ပါ' ကို ရွေးပြီး၊ ကွန်ပျူတာစနစ် အခန်းကန့်/drive ကို ထပ်မံ စာဝှက်ကြည့်ပါ၊ သို့သော် AES စာဝှက်စနစ် အယ်လဂိုရီသမ်ကို အသုံးပြုပါ (၄င်း၌ မှတ်ဉာဏ် လုပ်အပ်ချက် အနိမ့်ဆုံး ရှိသည်)။\n\nဖြစ်နိုင်ချေ အကြောင်းရင်းများနှင့် ဖြေရှင်းချက်များအတွက်၊ https://veracrypt.jp/en/Troubleshooting.html ကို လေ့လာပါ။</entry>
     <entry lang="my" key="SYS_DRIVE_NOT_ENCRYPTED">ကွန်ပျူတာစနစ် အခန်းကန့်/drive သည် (တစ်၀က်တစ်ပိုင်း ဖြစ်စေ၊ အပြည့်အ၀ ဖြစ်စေ) စာဝှက်ထားပုံ မပေါ်ပါ။</entry>
     <entry lang="my" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">ကွန်ပျူတာစနစ် အခန်းကန့်/drive ကို (တစ်၀က်တစ်ပိုင်း ဖြစ်စေ၊ အပြည့်အ၀ ဖြစ်စေ) စာဝှက်ထားသည်။\n\nဆက်လက် မလုပ်ဆောင်မီ ကွန်ပျူတာစနစ် အခန်းကန့်/drive ကို စာဝှက်ဖြည်ပါ။ ထိုသို့ ပြုလုပ်ရန်၊ ပင်မ VeraCrypt ၀င်းဒိုးရှိ မီနူးဘားမှ 'System' &gt; 'Permanently Decrypt System Partition/Drive' ကို ရွေးပါ။</entry>
     <entry lang="my" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">ကွန်ပျူတာစနစ် အခန်းကန့်/drive ကို (တစ်၀က်တစ်ပိုင်း ဖြစ်စေ၊ အပြည့်အ၀ ဖြစ်စေ) စာဝှက်ပြီးသည့်အခါ၊ VeraCrypt (သို့ရာတွင် ၄င်းကို အဆင့်မြှင့်နိုင်ပြီး အလားတူ ဗားရှင်းကို ပြန်လည် ထည့်သွင်းနိုင်သည်) ကို အဆင့်လျှော့၍ မရပါ။</entry>
@@ -1507,7 +1507,7 @@
     <entry lang="my" key="LINUX_MESSAGE_ON_MOUNT_AGAIN">\n\nနောက်တစ်ကြိမ် ထိုကဲ့သို့ volume ကို သင် အစပျိုးချိန်တွင် ဤမက်ဆေ့ချ်ကို ပြသလိုပါသလား။</entry>
     <entry lang="my" key="LINUX_WARNING">သတိပေးချက်</entry>
     <entry lang="my" key="LINUX_ERROR">ချို့ယွင်းချက်</entry>
-    <entry lang="my" key="LINUX_ONLY_TEXTMODE">ဤအပြင်အဆင်ကို လတ်တလောတွင် စာသားမုဒ်ဖြင့်သာ ပံ့ပိုးထားသည်။</entry>
+<entry lang="my" key="LINUX_ONLY_TEXTMODE">ဤအပြင်အဆင်ကို လတ်တလောတွင် စာသားမုဒ်ဖြင့်သာ ပံ့ပိုးထားသည်။</entry>
     <entry lang="my" key="LINUX_FREE_SPACE_ON_DRIVE">ဒရိုက်(ဗ်) {0}: ရှိ နေရာလွတ်မှာ {1} ဖြစ်သည်။</entry>
     <entry lang="my" key="LINUX_DYNAMIC_NOTICE">သင့်ကွန်ပျူတာလည်ပတ်မှုစနစ်သည် နေရာလွတ်အစကတည်းက ဖိုင်များကို ခွဲဝေသတ်မှတ်မပေးပါက အများဆုံး လျှို့ဝှက် volume အရွယ်အစားသည် ပြင်ပ volume ရှိ နေရာလွတ် အရွယ်အစားထက် များစွာငယ်နိုင်ကြောင်း သတိပြုပါ။ ယင်းသည် VeraCrypt ရှိ ပြဿနာ မဟုတ်ဘဲ ကွန်ပျူတာလည်ပတ်မှုစနစ်၏ ကန့်သတ်ချက်တစ်ခုသာ ဖြစ်သည်။</entry>
     <entry lang="my" key="LINUX_MAX_HIDDEN_SIZE">ဤ volume အတွက် လျှို့ဝှက် volume ၏ အကြီးဆုံး အရွယ်အစားမှာ {0} ဖြစ်သည်။</entry>
@@ -1525,12 +1525,12 @@
     <entry lang="my" key="LINUX_NOT_SUPPORTED">(ဤပလက်ဖောင်းတွင် ရရှိနိုင်သော အစိတ်အပိုင်းများက မပံ့ပိုးပါ)။\n</entry>
     <entry lang="my" key="LINUX_KERNEL_OLD">သင့်စနစ်သည် Linux kernel ၏ ဗားရှင်းဟောင်းကို အသုံးပြုသည်။\n\nLinux kernel ရှိ ပြဿနာတစ်ခုကြောင့် VeraCrypt volume တစ်ခုသို့ ဒေတာရေးစဉ် သင့်စနစ် ရပ်သွားနိုင်သည်။ ဤပြဿနာကို ဖြေရှင်းရန် kernel ကို ဗားရှင်း ၂.၆.၂၄ သို့မဟုတ် နောက်ပိုင်းဗားရှင်းသို့ အဆင့်မြှင့်နိုင်သည်။</entry>
     <entry lang="my" key="LINUX_VOL_UNMOUNTED">Volume {0} ကို အဆုံးသတ်လိုက်ပါပြီ။</entry>
-    <entry lang="en" key="LINUX_VOL_MOUNTED">Volume {0} has been mounted.</entry>
+    <entry lang="my" key="LINUX_VOL_MOUNTED">Volume {0} ကို အစပျိုးလိုက်ပါပြီ။</entry>
     <entry lang="my" key="LINUX_OOM">မမ်မိုရီ မကျန်တော့ပါ။</entry>
     <entry lang="my" key="LINUX_CANT_GET_ADMIN_PRIV">စီမံအုပ်ချုပ်သူ အခွင့်ထူးများကို ရယူခြင်း မအောင်မြင်ပါ</entry>
     <entry lang="my" key="LINUX_COMMAND_GET_ERROR">ညွှန်ကြားချက် {0} က ပြဿနာ {1} ကို ပြန်ပို့ပေးသည်။</entry>
     <entry lang="my" key="LINUX_CMD_HELP">VeraCrypt Command Line အကူအညီ</entry>
-    <entry lang="my" key="LINUX_HIDDEN_FILES_PRESENT_IN_KEYFILE_PATH">\n\nစကားဝှက်သော့ဖိုင် လမ်းကြောင်းတစ်ခုတွင် လျှို့ဝှက်ဖိုင်များ ရှိနေသည်။ သင်သည် ၎င်းတို့ကို စကားဝှက်သော့ဖိုင်များအဖြစ် အသုံးပြုရန် လိုအပ်ပါက ၎င်းတို့၏ ဖိုင်အမည်များ၏ ရှေ့မှလာသော အပြောက်ကို ဖယ်ရှားပါ။ လျှို့ဝှက်ဖိုင်များကို စနစ်ရွေးချယ်မှုများတွင် ဖွင့်ထားမှသာ မြင်နိုင်ပါသည်။</entry>
+    <entry lang="my" key="LINUX_HIDDEN_FILES_PRESENT_IN_KEYFILE_PATH">\n\nသတိပေးချက်- စကားဝှက်သော့ဖိုင် လမ်းကြောင်းတစ်ခုတွင် လျှို့ဝှက်ဖိုင်များ ရှိနေသည်။ သင်သည် ၎င်းတို့ကို စကားဝှက်သော့ဖိုင်များအဖြစ် အသုံးပြုရန် လိုအပ်ပါက ၎င်းတို့၏ ဖိုင်အမည်များ၏ ရှေ့မှလာသော အစက်ကို ဖယ်ရှားပါ။ လျှို့ဝှက်ဖိုင်များကို စနစ်ရွေးချယ်မှုများတွင် ဖွင့်ထားမှသာ မြင်နိုင်ပါသည်။</entry>
     <entry lang="my" key="LINUX_EX2MSG_DEVICESECTORSIZEMISMATCH">သိုလှောင်စက်နှင့် VC volume အပိုင်း အရွယ်အစား လွဲနေသည်</entry>
     <entry lang="my" key="LINUX_EX2MSG_ENCRYPTEDSYSTEMREQUIRED">volume က လက်ခံထားသော စနစ်ကို လည်ပတ်နေစဉ်တွင်သာ ဤလုပ်ဆောင်ချက်ကို ဆောင်ရွက်ရမည်။</entry>
     <entry lang="my" key="LINUX_EX2MSG_INSUFFICIENTDATA">ဒေတာ အလုံအလောက် မရရှိနိုင်ပါ။</entry>
@@ -1555,7 +1555,7 @@
     <entry lang="my" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">ပြဿနာ - ဒရိုက်(ဗ်)သည် ၅၁၂ ဘိုက် မဟုတ်သည့် အပိုင်းအရွယ်အစားကို အသုံးပြုသည်။\n\nသင့်ပလက်ဖောင်းပေါ်တွင် ရရှိနိုင်သော အစိတ်အပိုင်းများ၏ ကန့်သတ်ချက်များကြောင့် ဒရိုက်(ဗ်)တွင် အခန်းကန့်/စက်ပစ္စည်း လက်ခံထားရှိသော volume များကို မဖန်တီးနိုင်ပါ/အသုံးမပြုနိုင်ပါ။\n\nဖြစ်နိုင်ခြေရှိသော ဖြေရှင်းနည်းများ -\n- ဒရိုက်(ဗ်)ပေါ်တွင် ဖိုင်လက်ခံထားရှိသော volume (ထည့်စရာ) တစ်ခုကို ဖန်တီးပါ။\n- 512-byte အပိုင်းများပါသော ဒရိုက်(ဗ်)တစ်ခုကို သုံးပါ။\n- အခြားပလက်ဖောင်းပေါ်တွင် VeraCrypt ကို အသုံးပြုပါ။</entry>
     <entry lang="my" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">လက်ခံဖိုင်/စက်ကို အသုံးပြုထားပြီး ဖြစ်သည်။</entry>
     <entry lang="my" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Volume အပေါက် မရရှိနိုင်ပါ။</entry>
-    <entry lang="my" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt သည် OSXFUSE 2.5 နှင့်အထက် လိုအပ်သည်။</entry>
+    <entry lang="my" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt သည် macFUSE 2.5 နှင့်အထက် လိုအပ်သည်။</entry>
     <entry lang="my" key="EXCEPTION_OCCURRED">ခြွင်းချက် ဖြစ်ပေါ်ခဲ့သည်</entry>
     <entry lang="my" key="ENTER_PASSWORD">စကားဝှက် ရိုက်ထည့်ပါ</entry>
     <entry lang="my" key="ENTER_TC_VOL_PASSWORD">VeraCrypt Volume စကားဝှက် ရေးထည့်ရန်</entry>
@@ -1570,82 +1570,126 @@
     <entry lang="my" key="UNKNOWN_OPTION">အမည်မသိသော ရွေးချယ်မှု</entry>
     <entry lang="my" key="VOLUME_LOCATION">Volume တည်နေရာ</entry>
     <entry lang="my" key="VOLUME_HOST_IN_USE">သတိပေးချက် - Host ဖိုင်/device {0} ကို အသုံးပြုထားပြီးဖြစ်သည်။\n\n ဤအချက်ကို လျစ်လျူရှုခြင်းအားဖြင့် ကွန်ပျူတာစနစ် မတည်ငြိမ်မှု စသော မလိုလားအပ်သည့် ရလဒ်များ ဖြစ်ပေါ်စေနိုင်သည်။ Volume ကို အစမ​ပျိုးခင် host ဖိုင်/device ကို သုံးစွဲနေသည့် အက်ပလီကေးရှင်း အားလုံးကို ပိတ်ထားရမည်။\n\n ဆက်လက် အစပျိုးမလား။</entry>
-    <entry lang="en" key="CANT_INSTALL_WITH_EXE_OVER_MSI">VeraCrypt was previously installed using an MSI package and so it can't be updated using the standard installer.\n\nPlease use the MSI package to update your VeraCrypt installation.</entry>
-    <entry lang="en" key="IDC_USE_ALL_FREE_SPACE">Use all available free space</entry>
-    <entry lang="en" key="SYS_ENCRYPTION_UPGRADE_UNSUPPORTED_ALGORITHM">VeraCrypt cannot be upgraded because the system partition/drive was encrypted using an algorithm that is not supported anymore.\nPlease decrypt your system before upgrading VeraCrypt and then encrypt it again.</entry>
-    <entry lang="en" key="LINUX_EX2MSG_TERMINALNOTFOUND">Supported terminal application could not be found, you need either xterm, konsole or gnome-terminal (with dbus-x11).</entry>
-    <entry lang="en" key="IDM_MOUNT_NO_CACHE">Mount Without Cache</entry>
-    <entry lang="en" key="EXPANDER_INFO">:: VeraCrypt Expander ::\n\nExpand a VeraCrypt volume on the fly without reformatting\n\n\nAll kind of volumes (container files, disks and partitions) formatted with NTFS are supported. The only condition is that there must be enough free space on the host drive or host device of the VeraCrypt volume.\n\nDo not use this software to expand an outer volume containing a hidden volume, because this destroys the hidden volume!\n</entry>
-    <entry lang="en" key="IDC_STEPSEXPAND">1. Select the VeraCrypt volume to be expanded\n2. Click the 'Mount' button</entry>
-    <entry lang="en" key="IDT_VOL_NAME">Volume: </entry>
-    <entry lang="en" key="IDT_FILE_SYS">File system: </entry>
-    <entry lang="en" key="IDT_CURRENT_SIZE">Current size: </entry>
-    <entry lang="en" key="IDT_NEW_SIZE">New size: </entry>
-    <entry lang="en" key="IDT_NEW_SIZE_BOX_TITLE">Enter new volume size</entry>
-    <entry lang="en" key="IDC_INIT_NEWSPACE">Fill new space with random data</entry>
-    <entry lang="en" key="IDC_QUICKEXPAND">Quick Expand</entry>
-    <entry lang="en" key="IDT_INIT_SPACE">Fill new space: </entry>
-    <entry lang="en" key="EXPANDER_FREE_SPACE">%s free space available on host drive</entry>
-    <entry lang="en" key="EXPANDER_HELP_DEVICE">This is a device-based VeraCrypt volume.\n\nThe new volume size will be choosen automatically as the size of the host device.</entry>
-    <entry lang="en" key="EXPANDER_HELP_FILE">Please specify the new size of the VeraCrypt volume (must be at least %I64u KB larger than the current size).</entry>
-    <entry lang="en" key="QUICK_EXPAND_WARNING">WARNING: You should use Quick Expand only in the following cases:\n\n1) The device where the file container is located contains no sensitive data and you do not need plausible deniability.\n2) The device where the file container is located has already been securely and fully encrypted.\n\nAre you sure you want to use Quick Expand?</entry>
-    <entry lang="en" key="EXPANDER_STATUS_TEXT">IMPORTANT: Move your mouse as randomly as possible within this window. The longer you move it, the better. This significantly increases the cryptographic strength of the encryption keys. Then click 'Continue' to expand the volume.</entry>
-    <entry lang="en" key="EXPANDER_STATUS_TEXT_LEGACY">Click 'Continue' to expand the volume.</entry>
-    <entry lang="en" key="EXPANDER_FINISH_ERROR">Error: volume expansion failed.</entry>
-    <entry lang="en" key="EXPANDER_FINISH_ABORT">Error: operation aborted by user.</entry>
-    <entry lang="en" key="EXPANDER_FINISH_OK">Finished. Volume successfully expanded.</entry>
-    <entry lang="en" key="EXPANDER_CANCEL_WARNING">Warning: Volume expansion is in progress!\n\nStopping now may result in a damaged volume.\n\nDo you really want to cancel?</entry>
-    <entry lang="en" key="EXPANDER_STARTING_STATUS">Starting volume expansion ...\n</entry>
-    <entry lang="en" key="EXPANDER_HIDDEN_VOLUME_ERROR">An outer volume containing a hidden volume can't be expanded, because this destroys the hidden volume.\n</entry>
-    <entry lang="en" key="EXPANDER_SYSTEM_VOLUME_ERROR">A VeraCrypt system volume can't be expanded.</entry>
-    <entry lang="en" key="EXPANDER_NO_FREE_SPACE">Not enough free space to expand the volume</entry>
-    <entry lang="en" key="EXPANDER_WARNING_FILE_CONTAINER_JUNK">Warning: The container file is larger than the VeraCrypt volume area. The data after the VeraCrypt volume area will be overwritten.\n\nDo you want to continue?</entry>
-    <entry lang="en" key="EXPANDER_WARNING_FAT">Warning: The VeraCrypt volume contains a FAT file system!\n\nOnly the VeraCrypt volume itself will be expanded, but not the file system.\n\nDo you want to continue?</entry>
-    <entry lang="en" key="EXPANDER_WARNING_EXFAT">Warning: The VeraCrypt volume contains an exFAT file system!\n\nOnly the VeraCrypt volume itself will be expanded, but not the file system.\n\nDo you want to continue?</entry>
-    <entry lang="en" key="EXPANDER_WARNING_UNKNOWN_FS">Warning: The VeraCrypt volume contains an unknown or no file system!\n\nOnly the VeraCrypt volume itself will be expanded, the file system remains unchanged.\n\nDo you want to continue?</entry>
-    <entry lang="en" key="EXPANDER_ERROR_VOLUME_SIZE_TOO_SMALL">New volume size too small, must be at least %I64u kB larger than the current size.</entry>
-    <entry lang="en" key="EXPANDER_ERROR_VOLUME_SIZE_TOO_LARGE">New volume size too large, not enough space on host drive.</entry>
-    <entry lang="en" key="EXPANDER_ERROR_MAX_FILE_SIZE_EXCEEDED">Maximum file size of %I64u MB on host drive exceeded.</entry>
-    <entry lang="en" key="EXPANDER_ERROR_QUICKEXPAND_PRIVILEGES">Error: Failed to get necessary privileges to enable Quick Expand!\nPlease uncheck Quick Expand option and try again.</entry>
-    <entry lang="en" key="EXPANDER_ERROR_MAX_VC_VOLUME_SIZE_EXCEEDED">Maximum VeraCrypt volume size of %I64u TB exceeded!\n</entry>
-    <entry lang="en" key="FULL_FORMAT">Full Format</entry>
-    <entry lang="en" key="FAST_CREATE">Fast Create</entry>
-    <entry lang="en" key="WARN_FAST_CREATE">WARNING: You should use Fast Create only in the following cases:\n\n1) The device contains no sensitive data and you do not need plausible deniability.\n2) The device has already been securely and fully encrypted.\n\nAre you sure you want to use Fast Create?</entry>
-    <entry lang="en" key="IDC_ENABLE_EMV_SUPPORT">Enable EMV Support</entry>
-    <entry lang="en" key="COMMAND_APDU_INVALID">The APDU command sent to the card is not valid.</entry>
-    <entry lang="en" key="EXTENDED_APDU_UNSUPPORTED">Extended APDU commands cannot be used with the current token.</entry>
-    <entry lang="en" key="SCARD_MODULE_INIT_FAILED">Error when loading the WinSCard / PCSC library.</entry>
-    <entry lang="en" key="EMV_UNKNOWN_CARD_TYPE">The card in the reader is not a supported EMV card.</entry>
-    <entry lang="en" key="EMV_SELECT_AID_FAILED">The AID of the card in the reader could not be selected.</entry>
-    <entry lang="en" key="EMV_ICC_CERT_NOTFOUND">ICC Public Key Certificate was not found in the card.</entry>
-    <entry lang="en" key="EMV_ISSUER_CERT_NOTFOUND">Issuer Public Key Certificate was not found in the card.</entry>
-    <entry lang="en" key="EMV_CPLC_NOTFOUND">CPLC was not found in the EMV card.</entry>
-    <entry lang="en" key="EMV_PAN_NOTFOUND">No Primary Account Number (PAN) found in the EMV card.</entry>
-    <entry lang="en" key="INVALID_EMV_PATH">EMV path is invalid.</entry>
-    <entry lang="en" key="EMV_KEYFILE_DATA_NOTFOUND">Unable to build a keyfile from the EMV card's data.\n\nOne of the following is missing:\n- ICC Public Key Certificate.\n- Issuer Public Key Certificate.\n- CPLC data.</entry>
-    <entry lang="en" key="SCARD_W_REMOVED_CARD">No card in the reader.\n\nPlease make sure the card is correctly slotted.</entry>
-    <entry lang="en" key="FORMAT_EXTERNAL_FAILED">Windows format.com command failed to format the volume as NTFS/exFAT/ReFS: Error 0x%.8X.\n\nFalling back to using Windows FormatEx API.</entry>
-    <entry lang="en" key="FORMATEX_API_FAILED">Windows FormatEx API failed to format the volume as NTFS/exFAT/ReFS.\n\nFailure status = %s.</entry>
-    <entry lang="en" key="EXPANDER_WRITING_RANDOM_DATA">Writing random data to new space ...\n</entry>
-    <entry lang="en" key="EXPANDER_WRITING_ENCRYPTED_BACKUP">Writing re-encrypted backup header ...\n</entry>
-    <entry lang="en" key="EXPANDER_WRITING_ENCRYPTED_PRIMARY">Writing re-encrypted primary header ...\n</entry>
-    <entry lang="en" key="EXPANDER_WIPING_OLD_HEADER">Wiping old backup header ...\n</entry>
-    <entry lang="en" key="EXPANDER_MOUNTING_VOLUME">Mounting volume ...\n</entry>
-    <entry lang="en" key="EXPANDER_UNMOUNTING_VOLUME">Unmounting volume ...\n</entry>
-    <entry lang="en" key="EXPANDER_EXTENDING_FILESYSTEM">Extending file system ...\n</entry>
-    <entry lang="en" key="PARTIAL_SYSENC_MOUNT_READONLY">Warning: The system partition you attempted to mount was not fully encrypted. As a safety measure to prevent potential corruption or unwanted modifications, volume '%s' was mounted as read-only.</entry>
-    <entry lang="en" key="IDC_LINK_KEYFILES_EXTENSIONS_WARNING">Important information on using third-party file extensions</entry>
-    <entry lang="en" key="IDC_DISABLE_MEMORY_PROTECTION">Disable memory protection for Accessibility tools compatibility</entry>
-    <entry lang="en" key="DISABLE_MEMORY_PROTECTION_WARNING">WARNING: Disabling memory protection significantly reduces security. Enable this option ONLY if you rely on Accessibility tools, like Screen Readers, to interact with VeraCrypt's UI.</entry>
+    <entry lang="my" key="CANT_INSTALL_WITH_EXE_OVER_MSI">VeraCrypt ကို ယခင်က MSI ပက်ကေ့ချ်ဖြင့် ထည့်သွင်းခဲ့သောကြောင့် ပုံမှန် installer ဖြင့် အပ်ဒိတ်လုပ်၍မရပါ။\n\nသင်၏ VeraCrypt ထည့်သွင်းမှုကို အပ်ဒိတ်လုပ်ရန် MSI ပက်ကေ့ချ်ကို အသုံးပြုပါ။</entry>
+    <entry lang="my" key="IDC_USE_ALL_FREE_SPACE">ရရှိနိုင်သော နေရာလွတ်အားလုံးကို အသုံးပြုပါ</entry>
+    <entry lang="my" key="SYS_ENCRYPTION_UPGRADE_UNSUPPORTED_ALGORITHM">စနစ် partition/drive ကို ယခုအခါ မပံ့ပိုးတော့သော algorithm ဖြင့် ကုဒ်ဝှက်ထားသောကြောင့် VeraCrypt ကို အဆင့်မြှင့်၍မရပါ။\nကျေးဇူးပြု၍ VeraCrypt ကို အဆင့်မမြှင့်မီ သင့်စနစ်ကို ကုဒ်ဝှက်ဖြည်ပြီးနောက် တစ်ကြိမ်ပြန်၍ ကုဒ်ဝှက်ပါ။</entry>
+    <entry lang="my" key="LINUX_EX2MSG_TERMINALNOTFOUND">ပံ့ပိုးထားသော terminal application ကို ရှာမတွေ့ပါ၊ သင်သည် xterm၊ konsole သို့မဟုတ် gnome-terminal (dbus-x11 ဖြင့်) တစ်ခုခု လိုအပ်သည်။</entry>
+    <entry lang="my" key="IDM_MOUNT_NO_CACHE">Cache မပါဘဲ အစပျိုးပါ</entry>
+    <entry lang="my" key="EXPANDER_INFO">:: VeraCrypt Expander ::\n\nဖောမတ်ပြန်မချဘဲ VeraCrypt volume တစ်ခုကို လက်ရှိအခြေအနေမှ တိုးချဲ့ပါ\n\n\nNTFS ဖြင့် ဖောမတ်ချထားသော volume အမျိုးအစားအားလုံး (container ဖိုင်များ၊ disk များနှင့် partition များ) ကို ပံ့ပိုးထားသည်။ တစ်ခုတည်းသော အခြေအနေမှာ VeraCrypt volume ၏ host drive သို့မဟုတ် host device တွင် နေရာလွတ်အလုံအလောက် ရှိရမည်ဖြစ်သည်။\n\nလျှို့ဝှက် volume ပါရှိသော ပြင်ပ volume တစ်ခုကို တိုးချဲ့ရန် ဤဆော့ဖ်ဝဲကို မသုံးပါနှင့်၊ အဘယ်ကြောင့်ဆိုသော် ၎င်းသည် လျှို့ဝှက် volume ကို ဖျက်ဆီးသောကြောင့်ဖြစ်သည်!\n</entry>
+    <entry lang="my" key="IDC_STEPSEXPAND">၁။ တိုးချဲ့ရန် VeraCrypt volume ကို ရွေးချယ်ပါ\n၂။ 'အစပျိုးရန်' ခလုတ်ကို နှိပ်ပါ</entry>
+    <entry lang="my" key="IDT_VOL_NAME">Volume: </entry>
+    <entry lang="my" key="IDT_FILE_SYS">ဖိုင်စနစ်: </entry>
+    <entry lang="my" key="IDT_CURRENT_SIZE">လက်ရှိအရွယ်အစား: </entry>
+    <entry lang="my" key="IDT_NEW_SIZE">အရွယ်အစားအသစ်: </entry>
+    <entry lang="my" key="IDT_NEW_SIZE_BOX_TITLE">Volume အရွယ်အစားအသစ် ထည့်ပါ</entry>
+    <entry lang="my" key="IDC_INIT_NEWSPACE">နေရာအသစ်ကို ကျပန်းဒေတာများဖြင့် ဖြည့်ပါ</entry>
+    <entry lang="my" key="IDC_QUICKEXPAND">အမြန်တိုးချဲ့ပါ</entry>
+    <entry lang="my" key="IDT_INIT_SPACE">နေရာအသစ် ဖြည့်ပါ: </entry>
+    <entry lang="my" key="EXPANDER_FREE_SPACE">Host drive တွင် %s နေရာလွတ် ရရှိနိုင်သည်</entry>
+    <entry lang="my" key="EXPANDER_HELP_DEVICE">ဤသည်မှာ device-based VeraCrypt volume ဖြစ်သည်။\n\nVolume အရွယ်အစားအသစ်ကို host device ၏ အရွယ်အစားအဖြစ် အလိုအလျောက် ရွေးချယ်ပါမည်။</entry>
+    <entry lang="my" key="EXPANDER_HELP_FILE">VeraCrypt volume ၏ အရွယ်အစားအသစ်ကို သတ်မှတ်ပါ (လက်ရှိအရွယ်အစားထက် အနည်းဆုံး %I64u KB ပိုကြီးရမည်)။</entry>
+    <entry lang="my" key="QUICK_EXPAND_WARNING">သတိပေးချက်- အောက်ပါအခြေအနေများတွင်သာ အမြန်တိုးချဲ့ခြင်းကို အသုံးပြုသင့်သည်-\n\n၁) ဖိုင် container တည်ရှိရာ device တွင် ထိလွယ်ရှလွယ်ဒေတာများ မပါဝင်ဘဲ သင်သည် ယုတ္တိတန်သော ငြင်းဆိုနိုင်စွမ်း မလိုအပ်ပါ။\n၂) ဖိုင် container တည်ရှိရာ device ကို လုံခြုံစွာနှင့် အပြည့်အဝ ကုဒ်ဝှက်ထားပြီးဖြစ်သည်။\n\nအမြန်တိုးချဲ့ခြင်းကို အသုံးပြုလိုကြောင်း သေချာပါသလား။</entry>
+    <entry lang="my" key="EXPANDER_STATUS_TEXT">အရေးကြီး- သင်၏မောက်စ်ကို ဤဝင်းဒိုးအတွင်းတွင် တတ်နိုင်သမျှ ကျပန်းရွှေ့ပါ။ ကြာကြာရွှေ့လေ ပိုကောင်းလေဖြစ်သည်။ ၎င်းသည် ကုဒ်ဝှက်သော့များ၏ ကုဒ်ဝှက်ခြင်းဆိုင်ရာ ခိုင်မာမှုကို သိသိသာသာ တိုးမြှင့်ပေးသည်။ ထို့နောက် volume ကို တိုးချဲ့ရန် 'ဆက်လုပ်ရန်' ကို နှိပ်ပါ။</entry>
+    <entry lang="my" key="EXPANDER_STATUS_TEXT_LEGACY">Volume ကို တိုးချဲ့ရန် 'ဆက်လုပ်ရန်' ကို နှိပ်ပါ။</entry>
+    <entry lang="my" key="EXPANDER_FINISH_ERROR">ချို့ယွင်းချက်- volume တိုးချဲ့ခြင်း မအောင်မြင်ပါ။</entry>
+    <entry lang="my" key="EXPANDER_FINISH_ABORT">ချို့ယွင်းချက်- အသုံးပြုသူမှ လုပ်ဆောင်ချက်ကို ပယ်ဖျက်လိုက်သည်။</entry>
+    <entry lang="my" key="EXPANDER_FINISH_OK">ပြီးပါပြီ။ Volume ကို အောင်မြင်စွာ တိုးချဲ့ပြီးဖြစ်သည်။</entry>
+    <entry lang="my" key="EXPANDER_CANCEL_WARNING">သတိပေးချက်- Volume တိုးချဲ့ခြင်း လုပ်ဆောင်နေသည်!\n\nယခုရပ်တန့်ပါက volume ပျက်စီးသွားနိုင်သည်။\n\nတကယ် ပယ်ဖျက်လိုပါသလား။</entry>
+    <entry lang="my" key="EXPANDER_STARTING_STATUS">Volume တိုးချဲ့ခြင်း စတင်နေသည် ...\n</entry>
+    <entry lang="my" key="EXPANDER_HIDDEN_VOLUME_ERROR">လျှို့ဝှက် volume ပါရှိသော ပြင်ပ volume တစ်ခုကို တိုးချဲ့၍မရပါ၊ အဘယ်ကြောင့်ဆိုသော် ၎င်းသည် လျှို့ဝှက် volume ကို ဖျက်ဆီးသောကြောင့်ဖြစ်သည်။\n</entry>
+    <entry lang="my" key="EXPANDER_SYSTEM_VOLUME_ERROR">VeraCrypt စနစ် volume တစ်ခုကို တိုးချဲ့၍မရပါ။</entry>
+    <entry lang="my" key="EXPANDER_NO_FREE_SPACE">Volume ကို တိုးချဲ့ရန် နေရာလွတ်အလုံအလောက် မရှိပါ</entry>
+    <entry lang="my" key="EXPANDER_WARNING_FILE_CONTAINER_JUNK">သတိပေးချက်- Container ဖိုင်သည် VeraCrypt volume ဧရိယာထက် ပိုကြီးနေသည်။ VeraCrypt volume ဧရိယာနောက်ရှိ ဒေတာများကို ထပ်ရေးပါမည်။\n\nဆက်လုပ်လိုပါသလား။</entry>
+    <entry lang="my" key="EXPANDER_WARNING_FAT">သတိပေးချက်- VeraCrypt volume တွင် FAT ဖိုင်စနစ် ပါဝင်သည်!\n\n VeraCrypt volume ကိုယ်တိုင်သာ တိုးချဲ့မည်ဖြစ်ပြီး ဖိုင်စနစ်ကိုမူ တိုးချဲ့မည်မဟုတ်ပါ။\n\nဆက်လုပ်လိုပါသလား။</entry>
+    <entry lang="my" key="EXPANDER_WARNING_EXFAT">သတိပေးချက်- VeraCrypt volume တွင် exFAT ဖိုင်စနစ် ပါဝင်သည်!\n\n VeraCrypt volume ကိုယ်တိုင်သာ တိုးချဲ့မည်ဖြစ်ပြီး ဖိုင်စနစ်ကိုမူ တိုးချဲ့မည်မဟုတ်ပါ။\n\nဆက်လုပ်လိုပါသလား။</entry>
+    <entry lang="my" key="EXPANDER_WARNING_UNKNOWN_FS">သတိပေးချက်- VeraCrypt volume တွင် အမည်မသိ သို့မဟုတ် ဖိုင်စနစ်မရှိသော ဖိုင်စနစ် ပါဝင်သည်!\n\n VeraCrypt volume ကိုယ်တိုင်သာ တိုးချဲ့မည်ဖြစ်ပြီး ဖိုင်စနစ်မှာမူ မပြောင်းလဲဘဲ ကျန်ရှိနေမည်ဖြစ်သည်။\n\nဆက်လုပ်လိုပါသလား။</entry>
+    <entry lang="my" key="EXPANDER_ERROR_VOLUME_SIZE_TOO_SMALL">Volume အရွယ်အစားအသစ်မှာ အလွန်ငယ်နေသည်၊ လက်ရှိအရွယ်အစားထက် အနည်းဆုံး %I64u KB ပိုကြီးရမည်။</entry>
+    <entry lang="my" key="EXPANDER_ERROR_VOLUME_SIZE_TOO_LARGE">Volume အရွယ်အစားအသစ်မှာ အလွန်ကြီးနေသည်၊ host drive တွင် နေရာအလုံအလောက်မရှိပါ။</entry>
+    <entry lang="my" key="EXPANDER_ERROR_MAX_FILE_SIZE_EXCEEDED">Host drive ရှိ အများဆုံးဖိုင်အရွယ်အစား %I64u MB ကို ကျော်လွန်သွားသည်။</entry>
+    <entry lang="my" key="EXPANDER_ERROR_QUICKEXPAND_PRIVILEGES">ချို့ယွင်းချက်- အမြန်တိုးချဲ့ခြင်းကို ဖွင့်ရန် လိုအပ်သော အခွင့်အရေးများ ရယူခြင်း မအောင်မြင်ပါ!\nကျေးဇူးပြု၍ အမြန်တိုးချဲ့ခြင်း ရွေးချယ်မှုကို အမှန်ခြစ်ဖြုတ်ပြီး ထပ်မံကြိုးစားပါ။</entry>
+    <entry lang="my" key="EXPANDER_ERROR_MAX_VC_VOLUME_SIZE_EXCEEDED">အများဆုံး VeraCrypt volume အရွယ်အစား %I64u TB ကို ကျော်လွန်သွားသည်!\n</entry>
+    <entry lang="my" key="FULL_FORMAT">ဖောမတ် အပြည့်အစုံချပါ</entry>
+    <entry lang="my" key="FAST_CREATE">အမြန်ဖန်တီးပါ</entry>
+    <entry lang="my" key="WARN_FAST_CREATE">သတိပေးချက်- အောက်ပါအခြေအနေများတွင်သာ အမြန်ဖန်တီးခြင်းကို အသုံးပြုသင့်သည်-\n\n၁) device တွင် ထိလွယ်ရှလွယ်ဒေတာများ မပါဝင်ဘဲ သင်သည် ယုတ္တိတန်သော ငြင်းဆိုနိုင်စွမ်း မလိုအပ်ပါ။\n၂) device ကို လုံခြုံစွာနှင့် အပြည့်အဝ ကုဒ်ဝှက်ထားပြီးဖြစ်သည်။\n\nအမြန်ဖန်တီးခြင်းကို အသုံးပြုလိုကြောင်း သေချာပါသလား။</entry>
+    <entry lang="my" key="IDC_ENABLE_EMV_SUPPORT">EMV ပံ့ပိုးမှု ဖွင့်ပါ</entry>
+    <entry lang="my" key="COMMAND_APDU_INVALID">ကတ်သို့ ပေးပို့လိုက်သော APDU command သည် မမှန်ကန်ပါ။</entry>
+    <entry lang="my" key="EXTENDED_APDU_UNSUPPORTED">တိုးချဲ့ထားသော APDU command များကို လက်ရှိ token ဖြင့် အသုံးမပြုနိုင်ပါ။</entry>
+    <entry lang="my" key="SCARD_MODULE_INIT_FAILED">WinSCard / PCSC library ကို တင်ရာတွင် ချို့ယွင်းချက်။</entry>
+    <entry lang="my" key="EMV_UNKNOWN_CARD_TYPE">Reader ထဲရှိ ကတ်သည် ပံ့ပိုးထားသော EMV ကတ်မဟုတ်ပါ။</entry>
+    <entry lang="my" key="EMV_SELECT_AID_FAILED">Reader ထဲရှိ ကတ်၏ AID ကို ရွေးချယ်၍မရပါ။</entry>
+    <entry lang="my" key="EMV_ICC_CERT_NOTFOUND">ICC Public Key Certificate ကို ကတ်ထဲတွင် ရှာမတွေ့ပါ။</entry>
+    <entry lang="my" key="EMV_ISSUER_CERT_NOTFOUND">Issuer Public Key Certificate ကို ကတ်ထဲတွင် ရှာမတွေ့ပါ။</entry>
+    <entry lang="my" key="EMV_CPLC_NOTFOUND">CPLC ကို EMV ကတ်ထဲတွင် ရှာမတွေ့ပါ။</entry>
+    <entry lang="my" key="EMV_PAN_NOTFOUND">EMV ကတ်ထဲတွင် Primary Account Number (PAN) ကို ရှာမတွေ့ပါ။</entry>
+    <entry lang="my" key="INVALID_EMV_PATH">EMV လမ်းကြောင်း မမှန်ကန်ပါ။</entry>
+    <entry lang="my" key="EMV_KEYFILE_DATA_NOTFOUND">EMV ကတ်၏ ဒေတာမှ စကားဝှက်သော့ဖိုင် တည်ဆောက်၍မရပါ။\n\nအောက်ပါတို့အနက် တစ်ခုခု ပျောက်ဆုံးနေသည်-\n- ICC Public Key Certificate။\n- Issuer Public Key Certificate။\n- CPLC ဒေတာ။</entry>
+    <entry lang="my" key="SCARD_W_REMOVED_CARD">Reader ထဲတွင် ကတ်မရှိပါ။\n\nကတ်ကို မှန်ကန်စွာ ထည့်သွင်းထားကြောင်း သေချာအောင်လုပ်ပါ။</entry>
+    <entry lang="my" key="FORMAT_EXTERNAL_FAILED">Windows format.com command သည် volume ကို NTFS/exFAT/ReFS အဖြစ် ဖောမတ်ချရန် မအောင်မြင်ပါ- ချို့ယွင်းချက် 0x%.8X။\n\nWindows FormatEx API ကို အသုံးပြုခြင်းသို့ ပြန်သွားနေသည်။</entry>
+    <entry lang="my" key="FORMATEX_API_FAILED">Windows FormatEx API သည် volume ကို NTFS/exFAT/ReFS အဖြစ် ဖောမတ်ချရန် မအောင်မြင်ပါ။\n\nမအောင်မြင်မှု အခြေအနေ = %s။</entry>
+    <entry lang="my" key="EXPANDER_WRITING_RANDOM_DATA">နေရာအသစ်သို့ ကျပန်းဒေတာများ ရေးသားနေသည် ...\n</entry>
+    <entry lang="my" key="EXPANDER_WRITING_ENCRYPTED_BACKUP">ကုဒ်ဝှက်ပြန်လုပ်ထားသော အရန် header ကို ရေးသားနေသည် ...\n</entry>
+    <entry lang="my" key="EXPANDER_WRITING_ENCRYPTED_PRIMARY">ကုဒ်ဝှက်ပြန်လုပ်ထားသော မူလ header ကို ရေးသားနေသည် ...\n</entry>
+    <entry lang="my" key="EXPANDER_WIPING_OLD_HEADER">အရန် header အဟောင်းကို ဖျက်ပစ်နေသည် ...\n</entry>
+    <entry lang="my" key="EXPANDER_MOUNTING_VOLUME">Volume ကို အစပျိုးနေသည် ...\n</entry>
+    <entry lang="my" key="EXPANDER_UNMOUNTING_VOLUME">Volume ကို အဆုံးသတ်နေသည် ...\n</entry>
+    <entry lang="my" key="EXPANDER_EXTENDING_FILESYSTEM">ဖိုင်စနစ်ကို တိုးချဲ့နေသည် ...\n</entry>
+    <entry lang="my" key="PARTIAL_SYSENC_MOUNT_READONLY">သတိပေးချက်- သင် အစပျိုးရန် ကြိုးစားခဲ့သော စနစ် partition ကို အပြည့်အဝ ကုဒ်ဝှက်မထားပါ။ ဖြစ်နိုင်ခြေရှိသော ပျက်စီးမှု သို့မဟုတ် မလိုလားအပ်သော ပြင်ဆင်မှုများကို တားဆီးရန် ဘေးကင်းရေး အစီအမံအနေဖြင့် volume '%s' ကို ဖတ်ရန်သာ အဖြစ် အစပျိုးထားသည်။</entry>
+    <entry lang="my" key="IDC_LINK_KEYFILES_EXTENSIONS_WARNING">ပြင်ပအဖွဲ့အစည်း ဖိုင် extension များ အသုံးပြုခြင်းဆိုင်ရာ အရေးကြီးအချက်အလက်များ</entry>
+    <entry lang="my" key="IDC_DISABLE_MEMORY_PROTECTION">Accessibility ကိရိယာများ လိုက်ဖက်ညီမှုအတွက် မမ်မိုရီကာကွယ်မှုကို ပိတ်ပါ</entry>
+    <entry lang="my" key="DISABLE_MEMORY_PROTECTION_WARNING">သတိပေးချက်- မမ်မိုရီကာကွယ်မှုကို ပိတ်ခြင်းသည် လုံခြုံရေးကို သိသိသာသာ လျှော့ချသည်။ Screen Readers ကဲ့သို့ Accessibility ကိရိယာများကို အားကိုး၍ VeraCrypt ၏ UI နှင့် အပြန်အလှန်ဆက်သွယ်မှသာ ဤရွေးချယ်မှုကို ဖွင့်ပါ။</entry>
     <entry lang="my" key="LINUX_LANGUAGE">ဘာသာစကား</entry>
-    <entry lang="en" key="LINUX_SELECT_SYS_DEFAULT_LANG">Select system's default language</entry>
-    <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="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="my" key="LINUX_SELECT_SYS_DEFAULT_LANG">စနစ်၏ ပုံသေဘာသာစကားကို ရွေးချယ်ပါ</entry>
+    <entry lang="my" key="LINUX_RESTART_FOR_LANGUAGE_CHANGE">ဘာသာစကားပြောင်းလဲမှု အကျိုးသက်ရောက်ရန် VeraCrypt ကို ပြန်လည်စတင်ရန် လိုအပ်သည်။</entry>
+    <entry lang="my" key="ERR_XTS_MASTERKEY_VULNERABLE">သတိပေးချက်- Volume ၏ master key သည် ဒေတာလုံခြုံရေးကို ထိခိုက်စေသော တိုက်ခိုက်မှုတစ်ခုအတွက် အားနည်းချက်ရှိသည်။\n\nကျေးဇူးပြု၍ volume အသစ်တစ်ခု ဖန်တီးပြီး ဒေတာများကို ၎င်းသို့ လွှဲပြောင်းပါ။</entry>
+    <entry lang="my" key="ERR_SYSENC_XTS_MASTERKEY_VULNERABLE">သတိပေးချက်- ကုဒ်ဝှက်ထားသော စနစ်၏ master key သည် ဒေတာလုံခြုံရေးကို ထိခိုက်စေသော တိုက်ခိုက်မှုတစ်ခုအတွက် အားနည်းချက်ရှိသည်။\nကျေးဇူးပြု၍ စနစ် partition/drive ကို ကုဒ်ဝှက်ဖြည်ပြီးနောက် တစ်ကြိမ်ပြန်၍ ကုဒ်ဝှက်ပါ။</entry>
+    <entry lang="my" key="ERR_XTS_MASTERKEY_VULNERABLE_SHORT">သတိပေးချက်- Volume ၏ master key တွင် လုံခြုံရေးအားနည်းချက်တစ်ခု ရှိသည်။</entry>
+    <entry lang="my" key="MOUNTPOINT_BLOCKED">ချို့ယွင်းချက်- Volume အစပျိုးပွိုင့်ကို ပိတ်ဆို့ထားသည်၊ အဘယ်ကြောင့်ဆိုသော် ၎င်းသည် ကာကွယ်ထားသော စနစ်လမ်းညွှန်တစ်ခုကို ထပ်ရေးသောကြောင့်ဖြစ်သည်။\n\nကျေးဇူးပြု၍ မတူညီသော အစပျိုးပွိုင့်တစ်ခုကို ရွေးချယ်ပါ။</entry>
+    <entry lang="my" key="MOUNTPOINT_NOTALLOWED">ချို့ယွင်းချက်- Volume အစပျိုးပွိုင့်ကို ခွင့်မပြုပါ၊ အဘယ်ကြောင့်ဆိုသော် ၎င်းသည် PATH ပတ်ဝန်းကျင် variable ၏ အစိတ်အပိုင်းဖြစ်သော လမ်းညွှန်တစ်ခုကို ထပ်ရေးသောကြောင့်ဖြစ်သည်။\n\nကျေးဇူးပြု၍ မတူညီသော အစပျိုးပွိုင့်တစ်ခုကို ရွေးချယ်ပါ။</entry>
+    <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
-    <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-13" 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>
@@ -632,12 +632,12 @@
     <entry lang="nl" key="PASSWORD_HIDDEN_OS_TITLE">Wachtwoord voor verborgen besturingssysteem</entry>
     <entry lang="nl" key="PASSWORD_LENGTH_WARNING">WAARSCHUWING: korte wachtwoorden zijn gemakkelijk te kraken met behulp van brute-force technieken!\n\nWij raden u aan een wachtwoord te kiezen dat uit 20 of meer tekens bestaat. Weet u zeker dat u een kort wachtwoord wilt gebruiken?</entry>
     <entry lang="nl" key="PASSWORD_TITLE">Volumewachtwoord</entry>
-    <entry lang="nl" key="PASSWORD_WRONG">De bewerking is mislukt door een of meer van de volgende oorzaken:\n - onjuist wachtwoord\n - onjuist volume-PIM-nummer\n - onjuiste PRF (hash)\n - geen geldig volume</entry>
-    <entry lang="nl" key="PASSWORD_OR_KEYFILE_WRONG">De bewerking is mislukt door een of meer van de volgende oorzaken:\n - sleutelbestand(en) onjuist\n - onjuist wachtwoord\n - onjuist volume-PIM-nummer\n - onjuiste PRF (hash)\n - geen geldig volume</entry>
-    <entry lang="nl" key="PASSWORD_OR_MODE_WRONG">De bewerking is mislukt door een of meer van de volgende oorzaken:\n - onjuiste koppelmodus\n - onjuist wachtwoord\n - onjuist volume-PIM-nummer\n - onjuiste PRF (hash)\n - geen geldig volume</entry>
-    <entry lang="nl" key="PASSWORD_OR_KEYFILE_OR_MODE_WRONG">De bewerking is mislukt door een of meer van de volgende oorzaken:\n - onjuiste koppelingsmodus\n - sleutelbestand(en) onjuist\n - onjuist wachtwoord\n - onjuist volume-PIM-nummer\n - onjuiste PRF (hash)\n - geen geldig volume</entry>
-    <entry lang="nl" key="PASSWORD_WRONG_AUTOMOUNT">Automatische koppeling is mislukt door een of meer van de volgende oorzaken:\n - Onjuist wachtwoord.\n - Onjuist volume PIM-nummer.\n - Onjuiste PRF (hash).\n - Geen geldig volume gevonden.</entry>
-    <entry lang="nl" key="PASSWORD_OR_KEYFILE_WRONG_AUTOMOUNT">De automatische koppeling is mislukt door een of meer van de volgende oorzaken:\n - sleutelbestand(en) onjuist\n - onjuist wachtwoord\n - onjuist volume-PIM-nummer\n - onjuiste PRF (hash)\n - geen geldig volume gevonden.</entry>
+    <entry lang="nl" key="PASSWORD_WRONG">De bewerking is mislukt door een of meer van de volgende oorzaken:\n - onjuist wachtwoord\n - onjuist volume-PIM-nummer\n - onjuiste PRF (hash)\n - geen geldig volume.\n - Volume gebruikt een oud algoritme dat werd verwijderd.\n - Volumes in Truecrypt-formaat worden niet langer ondersteund.</entry>
+    <entry lang="nl" key="PASSWORD_OR_KEYFILE_WRONG">De bewerking is mislukt door een of meer van de volgende oorzaken:\n - onjuist(e) sleutelbestand(en).\n - onjuist wachtwoord\n - onjuist volume-PIM-nummer\n - onjuiste PRF (hash)\n - geen geldig volume.\n - Volume gebruikt een oud algoritme dat werd verwijderd.\n - Volumes in Truecrypt-formaat worden niet langer ondersteund.</entry>
+    <entry lang="nl" key="PASSWORD_OR_MODE_WRONG">De bewerking is mislukt door een of meer van de volgende oorzaken:\n - onjuiste koppelingsmodus.\n - onjuist wachtwoord\n - onjuist volume-PIM-nummer\n - onjuiste PRF (hash)\n - geen geldig volume.\n - Volume gebruikt een oud algoritme dat werd verwijderd.\n - Volumes in Truecrypt-formaat worden niet langer ondersteund.</entry>
+    <entry lang="nl" key="PASSWORD_OR_KEYFILE_OR_MODE_WRONG">De bewerking is mislukt door een of meer van de volgende oorzaken:\n - onjuiste koppelingsmodus.\n - onjuist(e) sleutelbestand(en).\n - onjuist wachtwoord\n - onjuist volume-PIM-nummer\n - onjuiste PRF (hash)\n - geen geldig volume.\n - Volume gebruikt een oud algoritme dat werd verwijderd.\n - Volumes in Truecrypt-formaat worden niet langer ondersteund.</entry>
+    <entry lang="nl" key="PASSWORD_WRONG_AUTOMOUNT">Automatisch koppelen is mislukt door een of meer van de volgende oorzaken:\n - onjuist wachtwoord\n - onjuist volume-PIM-nummer\n - onjuiste PRF (hash)\n - geen geldig volume gevonden.\n - Volume gebruikt een oud algoritme dat werd verwijderd.\n - Volumes in Truecrypt-formaat worden niet langer ondersteund.</entry>
+    <entry lang="nl" key="PASSWORD_OR_KEYFILE_WRONG_AUTOMOUNT">Automatisch koppelen is mislukt door een of meer van de volgende oorzaken:\n - onjuist(e) sleutelbestand(en).\n - onjuist wachtwoord\n - onjuist volume-PIM-nummer\n - onjuiste PRF (hash)\n - geen geldig volume gevonden.\n - Volume gebruikt een oud algoritme dat werd verwijderd.\n - Volumes in Truecrypt-formaat worden niet langer ondersteund.</entry>
     <entry lang="nl" key="PASSWORD_WRONG_CAPSLOCK_ON">\n\nWaarschuwing: Caps Lock is aan. Dit kan ertoe leiden dat u uw wachtwoord verkeerd invoert.</entry>
     <entry lang="nl" key="PIM_CHANGE_WARNING">Onthoud het nummer om het volume te koppelen</entry>
     <entry lang="nl" key="PIM_HIDVOL_HOST_TITLE">PIM buitenste volume</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>
@@ -855,7 +855,7 @@
     <entry lang="nl" key="TC_INSTALLER_IS_RUNNING">VeraCrypt Installer draait momenteel op dit systeem en is bezig met het uitvoeren of voorbereiden van de installatie of update van VeraCrypt. Voordat u verder gaat, wacht u tot hij is voltooid of sluit u hem. Als u hem niet kunt sluiten, start uw computer dan opnieuw op voordat u verder gaat.</entry>
     <entry lang="nl" key="INSTALL_FAILED">Installatie mislukt.</entry>
     <entry lang="nl" key="UNINSTALL_FAILED">Het verwijderen is mislukt.</entry>
-    <entry lang="nl" key="DIST_PACKAGE_CORRUPTED">Dit distributiepakket is beschadigd. Probeer het opnieuw te downloaden (bij voorkeur van de officiële VeraCrypt-website op https://www.veracrypt.fr).</entry>
+    <entry lang="nl" key="DIST_PACKAGE_CORRUPTED">Dit distributiepakket is beschadigd. Probeer het opnieuw te downloaden (bij voorkeur van de officiële VeraCrypt-website op https://veracrypt.jp).</entry>
     <entry lang="nl" key="CANNOT_WRITE_FILE_X">Kan bestand %s niet schrijven</entry>
     <entry lang="nl" key="EXTRACTING_VERB">Uitpakken</entry>
     <entry lang="nl" key="CANNOT_READ_FROM_PACKAGE">Kan geen gegevens uit het pakket lezen.</entry>
@@ -997,7 +997,7 @@
     <entry lang="nl" key="UNSUPPORTED_CHARS_IN_PWD">Fout: Wachtwoord mag alleen ASCII-tekens bevatten.\n\nNiet-ASCII-tekens in het wachtwoord kunnen ervoor zorgen dat het volume niet kan worden gekoppeld wanneer uw systeemconfiguratie verandert.\n\nDe volgende tekens zijn toegestaan:\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="nl" key="UNSUPPORTED_CHARS_IN_PWD_RECOM">Waarschuwing: het wachtwoord bevat niet-ASCII-tekens. Dit kan ertoe leiden dat het volume onmogelijk te koppelen is wanneer uw systeemconfiguratie verandert.\n\nU moet alle niet-ASCII-tekens in het wachtwoord vervangen door ASCII-tekens. Klik hiervoor op 'volumes' -&gt; 'volumewachtwoord wijzigen'.\n\nHet volgende zijn ASCII-tekens:\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="nl" key="EXE_FILE_EXTENSION_CONFIRM">WAARSCHUWING: wij raden u ten zeerste aan om bestandsextensies te vermijden die worden gebruikt voor uitvoerbare bestanden (zoals .exe, .sys of .dll) en andere vergelijkbare problematische bestandsextensies. Het gebruik van dergelijke bestandsextensies zorgt ervoor dat Windows en antivirussoftware interfereren met de container, wat de prestaties van het volume negatief beïnvloedt en ook andere ernstige problemen kan veroorzaken.\n\nWij raden u ten zeerste aan de bestandsextensie te verwijderen of te wijzigen (bijv. in '.hc').\n\nWeet u zeker dat u de problematische bestandsextensie wilt gebruiken?</entry>
-    <entry lang="nl" key="EXE_FILE_EXTENSION_MOUNT_WARNING">WAARSCHUWING: deze container heeft een bestandsextensie die wordt gebruikt voor uitvoerbare bestanden (zoals .exe, .sys of .dll) of een andere vergelijkbare problematische bestandsextensie. Het zal er zeer waarschijnlijk voor zorgen dat Windows en antivirussoftware interfereren met de container, wat de prestaties van het volume nadelig zal beïnvloeden en ook andere ernstige problemen kan veroorzaken.\n\nWij raden u sterk aan om de bestandsextensie van de container te verwijderen of te wijzigen (bijv. in '.hc') nadat u het volume hebt losgekoppeld.</entry>
+    <entry lang="nl" key="EXE_FILE_EXTENSION_MOUNT_WARNING">WAARSCHUWING: deze container heeft een bestandsextensie die wordt gebruikt voor uitvoerbare bestanden (zoals .exe, .sys of .dll) of een andere vergelijkbare problematische bestandsextensie. Het zal er zeer waarschijnlijk voor zorgen dat Windows en antivirussoftware interfereren met de container, wat de prestaties van het volume nadelig zal beïnvloeden en ook andere ernstige problemen kan veroorzaken.\n\nWij raden u sterk aan om de bestandsextensie van de container te verwijderen of te wijzigen (bijv. in '.hc') nadat u het volume hebt ontkoppeld.</entry>
     <entry lang="nl" key="HOMEPAGE">Startpagina</entry>
     <entry lang="nl" key="LARGE_IDE_WARNING_XP">WAARSCHUWING: het lijkt erop dat u geen service pack hebt toegepast op uw Windows-installatie. Schrijf niet naar IDE-schijven groter dan 128 GiB onder Windows XP waarop u Service Pack 1 of later niet hebt toegepast! Als u dat wel doet, kunnen gegevens op de schijf (ongeacht of het een VeraCrypt-volume is of niet) beschadigd raken. Merk op dat dit een beperking van Windows is, geen bug in VeraCrypt.</entry>
     <entry lang="nl" key="LARGE_IDE_WARNING_2K">WAARSCHUWING: het lijkt erop dat u Service Pack 3 of later niet hebt toegepast op uw Windows-installatie. Schrijf niet naar IDE-schijven groter dan 128 GiB onder Windows 2000 waarop u Service Pack 3 of later niet hebt toegepast! Als u dat wel doet, kunnen gegevens op de schijf (ongeacht of het een VeraCrypt-volume is of niet) beschadigd raken. Merk op dat dit een beperking van Windows is, geen bug in VeraCrypt.\n\nOpmerking: Het kan ook nodig zijn om de 48-bits LBA-ondersteuning in het register in te schakelen; voor meer informatie raadpleegt u http://support.microsoft.com/kb/305098/EN-US</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="nl" key="HIDDEN_OS_CREATION_PREINFO_HELP">In de volgende stappen zal VeraCrypt het verborgen besturingssysteem aanmaken door de inhoud van de systeempartitie te kopiëren naar het verborgen volume (de gegevens die worden gekopieerd zullen ter plaatse worden versleuteld met een encryptiesleutel die verschilt van de sleutel die voor het afleidingsbesturingssysteem zal worden gebruikt).\n\nMerk op dat het proces zal worden uitgevoerd in de pre-boot omgeving (voordat Windows start) en het kan lang duren; enkele uren of zelfs enkele dagen (afhankelijk van de grootte van de systeempartitie en de prestaties van uw computer).\n\nU kunt het proces onderbreken, uw computer afsluiten, het besturingssysteem starten en vervolgens het proces hervatten. Echter, als u het onderbreekt, zal het hele proces van het kopiëren van het systeem vanaf het begin moeten beginnen (omdat de inhoud van de systeempartitie niet mag veranderen tijdens het klonen).</entry>
     <entry lang="nl" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Wilt u het hele proces van het aanmaken van het verborgen besturingssysteem annuleren?\n\nOpmerking: U kunt het proces NIET hervatten als u het proces nu annuleert.</entry>
     <entry lang="nl" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Wilt u de voorafgaande test van de systeemversleuteling annuleren?</entry>
-    <entry lang="nl" key="BOOT_PRETEST_FAILED_RETRY">De VeraCrypt systeemversleuteling-pretest is mislukt. Wilt u het opnieuw proberen?\n\nAls u 'Nee' selecteert, wordt de pre-boot authenticatiecomponent verwijderd.\n\nOpmerkingen:\n\n- Als de VeraCryp-bootloader u niet heeft gevraagd om het wachtwoord in te voeren voordat Windows is gestart, is het mogelijk dat uw besturingssysteem niet opstart vanaf de schijf waarop het is geïnstalleerd. Dit wordt niet ondersteund.\n\n- Als u een ander versleutelingsalgoritme dan AES hebt gebruikt en de pretest is mislukt (en u hebt het wachtwoord ingevoerd), kan dit zijn veroorzaakt door een onjuist ontworpen stuurprogramma. Selecteer 'Nee' en probeer de systeempartitie/drive opnieuw te versleutelen, maar gebruik het AES-versleutelingsalgoritme (dat de laagste geheugenvereisten heeft).\n\n- Voor meer mogelijke oorzaken en oplossingen, zie: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="nl" key="BOOT_PRETEST_FAILED_RETRY">De VeraCrypt systeemversleuteling-pretest is mislukt. Wilt u het opnieuw proberen?\n\nAls u 'Nee' selecteert, wordt de pre-boot authenticatiecomponent verwijderd.\n\nOpmerkingen:\n\n- Als de VeraCryp-bootloader u niet heeft gevraagd om het wachtwoord in te voeren voordat Windows is gestart, is het mogelijk dat uw besturingssysteem niet opstart vanaf de schijf waarop het is geïnstalleerd. Dit wordt niet ondersteund.\n\n- Als u een ander versleutelingsalgoritme dan AES hebt gebruikt en de pretest is mislukt (en u hebt het wachtwoord ingevoerd), kan dit zijn veroorzaakt door een onjuist ontworpen stuurprogramma. Selecteer 'Nee' en probeer de systeempartitie/drive opnieuw te versleutelen, maar gebruik het AES-versleutelingsalgoritme (dat de laagste geheugenvereisten heeft).\n\n- Voor meer mogelijke oorzaken en oplossingen, zie: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="nl" key="SYS_DRIVE_NOT_ENCRYPTED">De systeempartitie/-schijf lijkt niet versleuteld te zijn (ook niet gedeeltelijk).</entry>
     <entry lang="nl" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Uw systeempartitie/schijf is versleuteld (gedeeltelijk of volledig).\n\nOntsleutel uw systeempartitie/schijf volledig voordat u verder gaat. Selecteer hiervoor 'Systeem' &gt; 'Systeempartitie/schijf permanent ontsleutelen' in de menubalk van het hoofdvenster van VeraCrypt.</entry>
     <entry lang="nl" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">Wanneer de systeempartitie/schijf versleuteld is (gedeeltelijk of volledig), kunt u VeraCrypt niet downgraden (maar u kunt het upgraden of dezelfde versie opnieuw installeren).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="nl" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Fout: de schijf gebruikt een andere sectorgrootte dan 512 bytes.\n\nVanwege de beperkingen van de onderdelen die beschikbaar zijn op uw platform, kunnen er geen partitie-/apparaatgehoste volumes worden aangemaakt/gebruikt op de schijf.\n\nMogelijke oplossingen:\n- Een bestandsgehost volume (container) op de schijf maken.\n- Een schijf met sectoren van 512 bytes gebruiken.\n- VeraCrypt op een ander platform gebruiken.</entry>
     <entry lang="nl" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">Het hostbestand/-apparaat is al in gebruik.</entry>
     <entry lang="nl" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Volumeslot niet beschikbaar.</entry>
-    <entry lang="nl" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt vereist OSXFUSE 2.5 or nieuwer.</entry>
+    <entry lang="nl" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt vereist macFUSE 2.5 or nieuwer.</entry>
     <entry lang="nl" key="EXCEPTION_OCCURRED">Er deed zich een uitzondering voor</entry>
     <entry lang="nl" key="ENTER_PASSWORD">Wachtwoord invoeren</entry>
     <entry lang="nl" key="ENTER_TC_VOL_PASSWORD">Voer het VeraCrypt-volume-wachtwoord in</entry>
@@ -1641,9 +1641,53 @@
     <entry lang="nl" key="ERR_XTS_MASTERKEY_VULNERABLE">WAARSCHUWING: De hoofdsleutel van het volume is kwetsbaar voor een aanval die de gegevensbeveiliging in gevaar brengt.\n\nMaak een nieuw volume aan en zet de gegevens daarnaar over.</entry>
     <entry lang="nl" key="ERR_SYSENC_XTS_MASTERKEY_VULNERABLE">WAARSCHUWING: De hoofdsleutel van het versleutelde systeem is kwetsbaar voor een aanval die de gegevensbeveiliging in gevaar brengt.\nOntsleutel de systeempartitie/-schijf en versleutel deze vervolgens opnieuw.</entry>
     <entry lang="nl" key="ERR_XTS_MASTERKEY_VULNERABLE_SHORT">WAARSCHUWING: De hoofdsleutel van het volume heeft een beveiligingslek.</entry>
-    <entry lang="nl" key="MOUNTPOINT_BLOCKED">FOUT: Het koppelpunt van het volume is geblokkeerd omdat het een beschermde systeemdirectory overschrijft.\n\nKies een ander koppelpunt.</entry>
-    <entry lang="nl" key="MOUNTPOINT_NOTALLOWED">FOUT: Het koppelpunt van het volume is niet toegestaan omdat het een directory overschrijft die deel uitmaakt van de PATH-omgevingsvariabele.\n\nKies een ander koppelpunt.</entry>
+    <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 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="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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="nl" key="MACOSX_APFS_SYNTHESIZED_DEVICE">Het geselecteerde apparaat ‘{0}’ is een door APFS gesynthetiseerde container of een APFS-volume en kan niet worden gebruikt als host voor een onbewerkt VeraCrypt-volume.\n\nSelecteer in plaats daarvan de fysieke APFS-opslagpartitie{1}.</entry>
+    <entry lang="nl" key="MACOSX_DEVICE_SYSTEM_PARTITION">Het geselecteerde apparaat ‘{0}’ is een systeem-/ondersteuningspartitie van macOS en kan niet worden gebruikt als host voor een VeraCrypt-volume.</entry>
+    <entry lang="nl" key="MACOSX_APFS_SYSTEM_STORE">De geselecteerde fysieke APFS-opslag ‘{0}’ bevat het momenteel gekoppelde macOS-systeemvolume en kan niet worden gebruikt als host voor een VeraCrypt-volume.</entry>
+    <entry lang="nl" key="MACOSX_DEVICE_NOT_WRITABLE">macOS meldt dat het geselecteerde apparaat ‘{0}’ alleen-lezen is. Selecteer een fysieke partitie of schijf waarop geschreven kan worden.</entry>
+    <entry lang="nl" key="MACOSX_APFS_EROFS_HINT">macOS geeft aan dat het geselecteerde apparaat alleen-lezen is. Als dit een APFS-schijf is, controleer dan of u de fysieke APFS-opslagpartitie hebt geselecteerd en niet een gesynthetiseerd APFS-volume. Gebruik Schijfhulpprogramma of ‘diskutil list’ om de fysieke partitie te identificeren en probeer het vervolgens opnieuw.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="en" key="TC_INSTALLER_IS_RUNNING">VeraCrypt Installer is currently running on this system and performing or preparing installation or update of VeraCrypt. Before you proceed, please wait for it to finish or close it. If you cannot close it, please restart your computer before proceeding.</entry>
     <entry lang="en" key="INSTALL_FAILED">Installation failed.</entry>
     <entry lang="en" key="UNINSTALL_FAILED">Uninstallation failed.</entry>
-    <entry lang="en" key="DIST_PACKAGE_CORRUPTED">This distribution package is damaged. Please try downloading it again (preferably from the official VeraCrypt website at https://www.veracrypt.fr).</entry>
+    <entry lang="en" key="DIST_PACKAGE_CORRUPTED">This distribution package is damaged. Please try downloading it again (preferably from the official VeraCrypt website at https://veracrypt.jp).</entry>
     <entry lang="en" key="CANNOT_WRITE_FILE_X">Cannot write file %s</entry>
     <entry lang="en" key="EXTRACTING_VERB">Extracting</entry>
     <entry lang="en" key="CANNOT_READ_FROM_PACKAGE">Cannot read data from the package.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="en" key="HIDDEN_OS_CREATION_PREINFO_HELP">In the next steps, VeraCrypt will create the hidden operating system by copying the content of the system partition to the hidden volume (data being copied will be encrypted on the fly with an encryption key different from the one that will be used for the decoy operating system).\n\nPlease note that the process will be performed in the pre-boot environment (before Windows starts) and it may take a long time to complete; several hours or even several days (depending on the size of the system partition and on the performance of your computer).\n\nYou will be able to interrupt the process, shut down your computer, start the operating system and then resume the process. However, if you interrupt it, the entire process of copying the system will have to start from the beginning (because the content of the system partition must not change during cloning).</entry>
     <entry lang="en" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Do you want to cancel the entire process of creation of the hidden operating system?\n\nNote: You will NOT be able to resume the process if you cancel it now.</entry>
     <entry lang="en" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Do you want to cancel the system encryption pretest?</entry>
-    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="en" key="SYS_DRIVE_NOT_ENCRYPTED">The system partition/drive does not appear to be encrypted (neither partially nor fully).</entry>
     <entry lang="en" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Your system partition/drive is encrypted (partially or fully).\n\nPlease decrypt your system partition/drive entirely before proceeding. To do so, select 'System' &gt; 'Permanently Decrypt System Partition/Drive' from the menu bar of the main VeraCrypt window.</entry>
     <entry lang="en" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">When the system partition/drive is encrypted (partially or fully), you cannot downgrade VeraCrypt (but you can upgrade it or reinstall the same version).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="en" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Error: The drive uses a sector size other than 512 bytes.\n\nDue to limitations of components available on your platform, partition/device-hosted volumes cannot be created/used on the drive.\n\nPossible solutions:\n- Create a file-hosted volume (container) on the drive.\n- Use a drive with 512-byte sectors.\n- Use VeraCrypt on another platform.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">The host file/device is already in use.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Volume slot unavailable.</entry>
-    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires OSXFUSE 2.5 or above.</entry>
+    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires macFUSE 2.5 or above.</entry>
     <entry lang="en" key="EXCEPTION_OCCURRED">Exception occurred</entry>
     <entry lang="en" key="ENTER_PASSWORD">Enter password</entry>
     <entry lang="en" key="ENTER_TC_VOL_PASSWORD">Enter VeraCrypt Volume Password</entry>
@@ -1644,6 +1644,50 @@
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="pl" key="TC_INSTALLER_IS_RUNNING">VeraCrypt Installer jest uruchomiony w twoim systemie i przygotowuje lub dokonuje instalacji lub uaktualnienia VeraCrypt. Przed dalszym kontynuowaniem instalacji, proszę poczekać na zakończenie aktualnego działania lub zamknij aplikacje. Jeżeli nie możesz zamknąć, proszę zrestartuj komputer przed uruchomieniem procesu instalacji.</entry>
     <entry lang="pl" key="INSTALL_FAILED">Niepowodzenie instalacji.</entry>
     <entry lang="pl" key="UNINSTALL_FAILED">Niepowodzenie dezinstalacji.</entry>
-    <entry lang="pl" key="DIST_PACKAGE_CORRUPTED">Pakiet dystrybucyjny jest uszkodzony. Pobierz go ponownie (najlepiej z oficjalnej strony programu VeraCrypt po adresem https://www.veracrypt.fr).</entry>
+    <entry lang="pl" key="DIST_PACKAGE_CORRUPTED">Pakiet dystrybucyjny jest uszkodzony. Pobierz go ponownie (najlepiej z oficjalnej strony programu VeraCrypt po adresem https://veracrypt.jp).</entry>
     <entry lang="pl" key="CANNOT_WRITE_FILE_X">Nie można zapisać pliku %s</entry>
     <entry lang="pl" key="EXTRACTING_VERB">Wyodrębnianie</entry>
     <entry lang="pl" key="CANNOT_READ_FROM_PACKAGE">Nie można odczytać danych z tego pakietu.</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>
@@ -1229,7 +1229,7 @@
     <entry lang="pl" key="HIDDEN_OS_CREATION_PREINFO_HELP">W następnym kroku, VeraCrypt będzie tworzył ukryty system operacyjny przez skopiowanie zawartości partycji systemowej do ukrytego wolumenu (kopiowane dane zostaną zaszyfrowane "w locie" z innym kluczem niż został użyty w zwodzącym systemie operacyjnym).\n\nProszę pamiętać, że proces zacznie się od rozruchu wstępnego i może zabrać dość dużo czasu aż skończy; od kilu godzin lub nieraz kliku dni (w zależności od wielkości partycji systemowej i wydajności twojego komputera).\n\nMożesz przerwać proces, wyłączając komputer, a proces wznowi się, gdy włączysz go ponownie. Jednakże, jeżeli przerwiesz proces, cały proces kopiowania zacznie się od początku (ponieważ zawartość systemowej partycji nie może ulec zmianie podczas klonowania).</entry>
     <entry lang="pl" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Czy chcesz anulować cały proces tworzenia ukrytego systemu operacyjnego?\n\nInfo: Nie będziesz mógł wznowić procesu jeżeli go anulujesz teraz.</entry>
     <entry lang="pl" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Chcesz anulować test szyfrowania systemu?</entry>
-    <entry lang="pl" key="BOOT_PRETEST_FAILED_RETRY">Test szyfrowania systemu przez program VeraCrypt nie powiódł się. Czy chcesz spróbować jeszcze raz?\n\nJeśli wybierzesz 'Nie', komponent odpowiedzialny za uwierzytelnienie przed uruchomieniem zostanie odinstalowany.\n\nUwagi: \n\n- Jeśli program startowy VeraCrypt nie pytał o hasło przed uruchomieniem systemu Windows, jest możliwe, że system operacyjny nie startuje z dysku, na którym jest zainstalowany. \n\n- Jeśli używasz algorytmu szyfrującego innego niż AES i test się nie powiódł (po wpisaniu hasła), mogło to być spowodowane przez niepoprawnie przydzielony sterownik. Wybierz 'Nie' i spróbuj zaszyfrować ponownie partycję lub dysk systemowy, jednak przy użyciu algorytmu szyfrowania AES (który ma najmniejsze wymagania co do pamięci).\n\n- Więcej możliwych powodów i rozwiązań na stronie https://www.veracrypt.fr/en/Troubleshooting.html (w języku angielskim).</entry>
+    <entry lang="pl" key="BOOT_PRETEST_FAILED_RETRY">Test szyfrowania systemu przez program VeraCrypt nie powiódł się. Czy chcesz spróbować jeszcze raz?\n\nJeśli wybierzesz 'Nie', komponent odpowiedzialny za uwierzytelnienie przed uruchomieniem zostanie odinstalowany.\n\nUwagi: \n\n- Jeśli program startowy VeraCrypt nie pytał o hasło przed uruchomieniem systemu Windows, jest możliwe, że system operacyjny nie startuje z dysku, na którym jest zainstalowany. \n\n- Jeśli używasz algorytmu szyfrującego innego niż AES i test się nie powiódł (po wpisaniu hasła), mogło to być spowodowane przez niepoprawnie przydzielony sterownik. Wybierz 'Nie' i spróbuj zaszyfrować ponownie partycję lub dysk systemowy, jednak przy użyciu algorytmu szyfrowania AES (który ma najmniejsze wymagania co do pamięci).\n\n- Więcej możliwych powodów i rozwiązań na stronie https://veracrypt.jp/en/Troubleshooting.html (w języku angielskim).</entry>
     <entry lang="pl" key="SYS_DRIVE_NOT_ENCRYPTED">Partycja/dysk systemowy nie jest zaszyfrowany (ani częściowo, ani w pełni).</entry>
     <entry lang="pl" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Partycja/dysk systemowy jest zaszyfrowany (częściowo lub całkowicie).\n\nOdszyfruj partycję lub dysk systemowy przed kontynuowaniem. W tym celu wybierz opcję 'System' &gt; 'Trwale odszyfruj partycję lub dysk systemowy' w menu głównym programu VeraCrypt.</entry>
     <entry lang="pl" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">Kiedy systemowa partycja/dysk jest zaszyfrowany (częściowo lub całkowicie), nie możesz wykonać instalacji wcześniejszej wersji VeraCrypt (ale możesz zrobić aktualizacji lub reinstalację tej samej wersji).</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 OSXFUSE 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>
@@ -1644,6 +1644,50 @@
     <entry lang="pl" key="MOUNTPOINT_BLOCKED">BŁĄD: Punkt podłączania wolumenu jest zablokowany, ponieważ nadpisuje chroniony katalog systemowy.\n\nWybierz inny punkt podłączania.</entry>
     <entry lang="pl" key="MOUNTPOINT_NOTALLOWED">BŁĄD: Punkt podłączania wolumenu nie jest dozwolony, ponieważ nadpisuje katalog, który jest częścią zmiennej środowiskowej PATH.\n\nWybierz inny punkt podłączania.</entry>
     <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_KERNEL_DRIVER">Podłącz wolumeny NTFS za pomocą sterownika systemu Linux w jądrze</entry>
+    <entry lang="pl" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Tylko system Linux. Po włączeniu i braku jawnego typu systemu plików, VeraCrypt skanuje odszyfrowane urządzenie wirtualne za pomocą blkid -p i podłącza wykryte systemy plików NTFS za pomocą dostępnego sterownika NTFS w jądrze, pomijając programy pomocnicze podłączania, takie jak ntfs-3g. VeraCrypt używa ntfs, gdy zostanie on jednoznacznie rozpoznany jako nowoczesny sterownik odczytu/zapisu albo jest oczekiwany w jądrze Linuksa 7.1 lub nowszym, a w przeciwnym razie używa ntfs3. Jeśli wykrycie NTFS się nie powiedzie, VeraCrypt użyje standardowego wyboru automatycznego systemu plików. Jeśli żaden obsługiwany sterownik NTFS w jądrze nie jest dostępny lub możliwy do załadowania, podłączenie kończy się niepowodzeniem. To ustawienie opcjonalne 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_KERNEL_NTFS_DRIVER_UNAVAILABLE">Brak obsługiwanego sterownika NTFS w jądrze lub możliwości załadowania go. Aby użyć domyślnego backendu NTFS w systemie, wyłącz preferencję sterownika NTFS jądra lub jawnie nie żądaj NTFS z jądra.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="pt-br" key="TC_INSTALLER_IS_RUNNING">O instalador do VeraCrypt está atualmente em execução, realizando ou preparando uma instalação ou atualização do VeraCrypt. Antes de continuar, por favor, aguarde o seu término ou feche-o. Se você não puder fechá-lo, por favor, reinicie o computador antes de prosseguir.</entry>
     <entry lang="pt-br" key="INSTALL_FAILED">A instalação falhou.</entry>
     <entry lang="pt-br" key="UNINSTALL_FAILED">A desinstalação falhou.</entry>
-    <entry lang="pt-br" key="DIST_PACKAGE_CORRUPTED">Este pacote de distribuição parece estar danificado. Tente baixá-lo novamente (de preferência a partir do nosso site oficial https://www.veracrypt.fr).</entry>
+    <entry lang="pt-br" key="DIST_PACKAGE_CORRUPTED">Este pacote de distribuição parece estar danificado. Tente baixá-lo novamente (de preferência a partir do nosso site oficial https://veracrypt.jp).</entry>
     <entry lang="pt-br" key="CANNOT_WRITE_FILE_X">Não foi possível gravr o arquivoe %s</entry>
     <entry lang="pt-br" key="EXTRACTING_VERB">Extraindo</entry>
     <entry lang="pt-br" key="CANNOT_READ_FROM_PACKAGE">Não foi possível ler alguns dados do pacote de instalação.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="pt-br" key="HIDDEN_OS_CREATION_PREINFO_HELP">Nas próximas etapas, o VeraCrypt irá criar o sistema operacional oculto copiando o conteúdo da partição do sistema para o volume oculto (os dados a serem copiados serão criptografados on-the-fly com uma chave de criptografia diferente daquele que será utilizada para o sistema isca).\n\nPor favor note que o processo será realizado em ambiente pré-boot (antes do Windows iniciar) e pode levar um longo tempo para concluir; várias horas ou até vários dias (dependendo do tamanho da partição do sistema e do desempenho do seu computador).\n\nVocê poderá interromper o processo, desligar o computador, iniciar o sistema operacional e, em seguida, retomar o processo. No entanto, se você interrompê-lo, todo o processo de cópia do sistema terá que começar desde o início (porque o conteúdo da partição do sistema não deve mudar durante a clonagem).</entry>
     <entry lang="pt-br" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Deseja cancelar todo o processo de criação do sistema operacional oculto?\n\nNota: Você NÃO poderá retomar o processo se cancelá-lo agora.</entry>
     <entry lang="pt-br" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Você deseja cancelar o pré-teste de criptografia de sistema?</entry>
-    <entry lang="pt-br" key="BOOT_PRETEST_FAILED_RETRY">O pré-teste de criptografia do sistema do VeraCrypt falhou. Deseja tentar novamente?\n\nSe você selecionar 'Não', o componente de autenticação de pré-inicialização será desinstalado.\n\nObservações:\n\n- Se o carregador de inicialização do VeraCrypt não solicitou que você digitasse a senha antes de o Windows iniciar, é possível que o seu sistema operacional não esteja inicializando a partir da unidade na qual está instalado. Isso não é suportado.\n\n- Se você usou um algoritmo de criptografia diferente de AES e o pré-teste falhou (e você inseriu a senha), isso pode ter sido causado por um driver projetado de forma inadequada. Selecione 'Não' e tente criptografar novamente a partição/unidade do sistema, mas use o algoritmo de criptografia AES (que possui os menores requisitos de memória).\n\n- Para mais possíveis causas e soluções, veja: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="pt-br" key="BOOT_PRETEST_FAILED_RETRY">O pré-teste de criptografia do sistema do VeraCrypt falhou. Deseja tentar novamente?\n\nSe você selecionar 'Não', o componente de autenticação de pré-inicialização será desinstalado.\n\nObservações:\n\n- Se o carregador de inicialização do VeraCrypt não solicitou que você digitasse a senha antes de o Windows iniciar, é possível que o seu sistema operacional não esteja inicializando a partir da unidade na qual está instalado. Isso não é suportado.\n\n- Se você usou um algoritmo de criptografia diferente de AES e o pré-teste falhou (e você inseriu a senha), isso pode ter sido causado por um driver projetado de forma inadequada. Selecione 'Não' e tente criptografar novamente a partição/unidade do sistema, mas use o algoritmo de criptografia AES (que possui os menores requisitos de memória).\n\n- Para mais possíveis causas e soluções, veja: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="pt-br" key="SYS_DRIVE_NOT_ENCRYPTED">O dispositivo/partição de sistema não parece estar criptografado (nem parcial nem completamente).</entry>
     <entry lang="pt-br" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Seu dispositivo/partição de sistema está criptografado (parcial ou completamente).\n\nFavor descriptografar o dispositivo/partição de sistema completamente antes de continuar. Para isso, clique em 'Sistema' &gt; 'Descriptografar Dispositivo/Partição de Sistema Definitivamente' na barra de menu da janela principal do VeraCrypt.</entry>
     <entry lang="pt-br" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">Quando a partição/unidade do sistema está criptografada (parcial ou totalmente), você não pode fazer o downgrade do VeraCrypt (mas pode atualizá-lo ou reinstalar a mesma versão).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="pt-br" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Erro: O drive usa um tamanho de setor diferente de 512 bytes.\n\nDevido a limitações dos componentes disponíveis na sua plataforma, volumes hospedados em partições/dispositivos não podem ser criados/usados no drive.\n\nPossíveis soluções:\n- Crie um volume hospedado em arquivo (container) no drive.\n- Use um drive com setores de 512 bytes.\n- Use o VeraCrypt em outra plataforma.</entry>
     <entry lang="pt-br" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">O arquivo/dispositivo host já está em uso.</entry>
     <entry lang="pt-br" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Slot de volume indisponível.</entry>
-    <entry lang="pt-br" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">O VeraCrypt requer o OSXFUSE 2.5 ou superior.</entry>
+    <entry lang="pt-br" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">O VeraCrypt requer o macFUSE 2.5 ou superior.</entry>
     <entry lang="pt-br" key="EXCEPTION_OCCURRED">Ocorreu uma exceção.</entry>
     <entry lang="pt-br" key="ENTER_PASSWORD">Digite a senha</entry>
     <entry lang="pt-br" key="ENTER_TC_VOL_PASSWORD">Digitar a Senha do Volume VeraCrypt</entry>
@@ -1644,6 +1644,50 @@
     <entry lang="pt-br" key="MOUNTPOINT_BLOCKED">ERRO: O ponto de montagem do volume está bloqueado porque substitui um diretório protegido do sistema.\n\nPor favor, escolha um ponto de montagem diferente.</entry>
     <entry lang="pt-br" key="MOUNTPOINT_NOTALLOWED">ERRO: O ponto de montagem do volume não é permitido porque substitui um diretório que faz parte da variável de ambiente PATH.\n\nPor favor, escolha um ponto de montagem diferente.</entry>
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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,10 +852,10 @@
     <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 www.idrix.fr).</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>
     <entry lang="ro" key="CANNOT_WRITE_FILE_X">Nu se poate scrie fișierul %s</entry>
     <entry lang="ro" key="EXTRACTING_VERB">Extragere</entry>
     <entry lang="ro" key="CANNOT_READ_FROM_PACKAGE">Nu se pot citi datele din pachet.</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,26 +1222,26 @@
     <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>
     <entry lang="ro" key="HIDDEN_OS_CREATION_PREINFO_HELP">În pașii următori, VeraCrypt va crea sistemul de operare ascuns prin copierea conținutului partiției sistem în volumul ascuns (datele copiate vor fi criptate din mers cu o cheie de criptare diferită de cea folosită pentru sistemul de operare momeală).\n\nRețineți că procesul va fi executat în mediul de prepornire (înainte de pornirea Windows) și ar putea dura mai mult până la finalizare; câteva ore sau zile (în funcție de dimensiunea partiției sistem și de performanțele calculatorului).\n\nVeți putea întrerupe procesul, să închideți calculatorul, să porniți sistemul de operare și apoi să reluați procesul. Totuși, dacă îl întrerupeți, întregul proces de copiere va trebui să fie reluat de la început (deoarece conținutul partiției sistem nu trebuie modificat pe durata clonării).</entry>
     <entry lang="ro" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Doriți să anulați întregul proces de creare a sistemului de operare ascuns?\n\nNotă: NU veți putea continua procesul dacă îl anulați acum.</entry>
     <entry lang="ro" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Doriți să anulați pretestarea criptării sistemului?</entry>
-    <entry lang="ro" key="BOOT_PRETEST_FAILED_RETRY">Pretestul VeraCrypt de criptare a sistemului a eșuat. Doriți să încercați din nou?\n\nDacă selectați «Nu», componenta de autentificare la prepornire va fi dezinstalată.\n\nNotă:\n\n- Dacă programul de pornire VeraCrypt nu v-a solicitat să introduceți parola înainte de a porni Windows, este posibil ca sistemul de operare să nu pornească de pe discul pe care este instalat. Această situație nu e suportată.\n\n- Dacă ați utilizat un algoritm de criptare altul decât AES și testul a eșuat (și ați introdus parola), s-ar putea să fie datorită unui driver impropriu proiectat. Selectați «Nu» și încercați criptarea partiției/discului sistem din nou, dar folosiți algoritmul de criptare AES (care solicită cele mai mici resurse de memorie).\n\n- Pentru mai multe cauze posibile și soluții, vizitați: http://www.idrix.fr</entry>
+    <entry lang="ro" key="BOOT_PRETEST_FAILED_RETRY">Pretestul VeraCrypt de criptare a sistemului a eșuat. Doriți să încercați din nou?\n\nDacă selectați «Nu», componenta de autentificare la prepornire va fi dezinstalată.\n\nNotă:\n\n- Dacă programul de pornire VeraCrypt nu v-a solicitat să introduceți parola înainte de a porni Windows, este posibil ca sistemul de operare să nu pornească de pe discul pe care este instalat. Această situație nu e suportată.\n\n- Dacă ați utilizat un algoritm de criptare altul decât AES și testul a eșuat (și ați introdus parola), s-ar putea să fie datorită unui driver impropriu proiectat. Selectați «Nu» și încercați criptarea partiției/discului sistem din nou, dar folosiți algoritmul de criptare AES (care solicită cele mai mici resurse de memorie).\n\n- Pentru mai multe cauze posibile și soluții, vizitați: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="ro" key="SYS_DRIVE_NOT_ENCRYPTED">Discul/partiția sistem nu pare să fie criptat(ă) (nici parțial nici în întregime).</entry>
     <entry lang="ro" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Discul/partiția sistem este criptat(ă) (complet sau parțial).\n\nDecriptați partiția/discul sistem în întregime înainte de a continua. Pentru aceasta, selectați „Sistem” > „Decriptare permanentă disc/partiție sistem” din bara meniului ferestrei principale VeraCrypt.</entry>
     <entry lang="ro" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">Când partiția/discul sistem este criptată (complet sau parțial), nu puteți reveni la o versiune anterioară VeraCrypt (dar puteți instala una mai nouă sau reinstala aceeași versiune).</entry>
     <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>
@@ -1553,7 +1553,7 @@
     <entry lang="ro" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Eroare: unitatea folosește o dimensiune de sector diferită de 512 de baiți.\n\nDin cauza limitărilor componentelor disponibile pe platformă, volumele partiției/găzduite de dispozitiv nu pot fi create/utilizate pe unitate.\n\nSoluții posibile:\n- Creați un volum găzduit de fișiere (container) pe unitate.\n- Utilizați o unitate cu sectoare de 512 de baiți.\n- Utilizați VeraCrypt pe o altă platformă.</entry>
     <entry lang="ro" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">Fișierul/dispozitivul gazdă este deja în uz.</entry>
     <entry lang="ro" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Slot de volum indisponibil.</entry>
-    <entry lang="ro" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt necesită OSXFUSE 2.5 sau ulterior.</entry>
+    <entry lang="ro" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt necesită macFUSE 2.5 sau ulterior.</entry>
     <entry lang="ro" key="EXCEPTION_OCCURRED">A apărut o excepție.</entry>
     <entry lang="ro" key="ENTER_PASSWORD">Introduceți parola</entry>
     <entry lang="ro" key="ENTER_TC_VOL_PASSWORD">Introduceți parola volumului VeraCrypt</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>
@@ -1644,6 +1644,50 @@
     <entry lang="ro" key="MOUNTPOINT_BLOCKED">EROARE: Punctul de montare al volumului este blocat deoarece suprascrie un director de sistem protejat.\n\nVă rugăm să alegeți un alt punct de montare.</entry>
     <entry lang="ro" key="MOUNTPOINT_NOTALLOWED">EROARE: Punctul de montare al volumului nu este permis deoarece suprascrie un director care face parte din variabila de mediu PATH.\n\nVă rugăm să alegeți un alt punct de montare.</entry>
     <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="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
-    <language langid="ru" name="Русский" en-name="Russian" version="1.26.20" 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>
@@ -855,7 +855,7 @@
     <entry lang="ru" key="TC_INSTALLER_IS_RUNNING">В системе сейчас запущен установщик VeraCrypt. Он выполняет/готовит установку или обновление VeraCrypt. Дождитесь завершения работы или закройте его. Если закрыть установщик не получается, перезагрузите компьютер и лишь потом продолжайте.</entry>
     <entry lang="ru" key="INSTALL_FAILED">Установка не выполнена.</entry>
     <entry lang="ru" key="UNINSTALL_FAILED">Удаление не выполнено.</entry>
-    <entry lang="ru" key="DIST_PACKAGE_CORRUPTED">Этот дистрибутивный пакет повреждён. Загрузите его снова (желательно с официального сайта VeraCrypt - https://www.veracrypt.fr).</entry>
+    <entry lang="ru" key="DIST_PACKAGE_CORRUPTED">Этот дистрибутивный пакет повреждён. Загрузите его снова (желательно с официального сайта VeraCrypt - https://veracrypt.jp).</entry>
     <entry lang="ru" key="CANNOT_WRITE_FILE_X">Невозможно записать файл %s</entry>
     <entry lang="ru" key="EXTRACTING_VERB">Извлечение</entry>
     <entry lang="ru" key="CANNOT_READ_FROM_PACKAGE">Невозможно прочитать данные из дистрибутива.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="ru" key="HIDDEN_OS_CREATION_PREINFO_HELP">На следующих этапах VeraCrypt создаст скрытую ОС, скопировав содержимое системного раздела в скрытый том (копируемые данные шифруются "на лету" с ключом, отличным от используемого для обманной ОС).\n\nУчтите, что процесс выполняется на предзагрузочном этапе (до запуска Windows) и может занять много времени (несколько часов или даже дней, в зависимости от размера системного раздела и быстродействия ПК).\n\nВы сможете прервать этот процесс, выключить ПК, запустить ОС и затем возобновить его. Однако в случае прерывания, копирование системы придётся начать сначала (так как при клонировании содержимое системного раздела не должно изменяться).</entry>
     <entry lang="ru" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Отменить весь процесс создания скрытой операционной системы?\n\nПри отмене вы НЕ сможете затем продолжить процесс.</entry>
     <entry lang="ru" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Отменить пре-тест шифрования системы?</entry>
-    <entry lang="ru" key="BOOT_PRETEST_FAILED_RETRY">Пре-тест шифрования системы не пройден. Повторить попытку?\n\nПри выборе "Нет" компонент предзагрузочной аутентификации будет удалён.\n\nПримечания:\n\n- Если загрузчик VeraCrypt не просил ввести пароль перед стартом Windows, возможно, ОС загружается не с того диска, на котором она установлена. Такая конфигурация не поддерживается.\n\n- Если используется отличный от AES алгоритм шифрования, и пре-тест выдаёт ошибку (и вы ввели пароль), причина может быть в некорректном драйвере. Выберите "Нет" и попробуйте снова зашифровать системный раздел/диск, но используя AES (у этого алгоритма наименьшие требования к памяти).\n\n- Другие причины и решения см. здесь: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="ru" key="BOOT_PRETEST_FAILED_RETRY">Пре-тест шифрования системы не пройден. Повторить попытку?\n\nПри выборе "Нет" компонент предзагрузочной аутентификации будет удалён.\n\nПримечания:\n\n- Если загрузчик VeraCrypt не просил ввести пароль перед стартом Windows, возможно, ОС загружается не с того диска, на котором она установлена. Такая конфигурация не поддерживается.\n\n- Если используется отличный от AES алгоритм шифрования, и пре-тест выдаёт ошибку (и вы ввели пароль), причина может быть в некорректном драйвере. Выберите "Нет" и попробуйте снова зашифровать системный раздел/диск, но используя AES (у этого алгоритма наименьшие требования к памяти).\n\n- Другие причины и решения см. здесь: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="ru" key="SYS_DRIVE_NOT_ENCRYPTED">Похоже, системный раздел/диск не зашифрован\n(ни частично, ни полностью).</entry>
     <entry lang="ru" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Системный раздел/диск зашифрован (частично или полностью).\n\nПрежде чем продолжить, полностью расшифруйте системный раздел/диск. Чтобы это сделать, выберите в главном окне VeraCrypt меню "Система" &gt; "Окончательно расшифровать системный раздел/диск".</entry>
     <entry lang="ru" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">Если системный раздел/диск зашифрован (частично или полностью), нельзя устанавливать VeraCrypt более старой версии (но можно более новую или ту же версию).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="ru" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">ОШИБКА: Диск использует не 512-байтовые сектора.\n\nИз-за ограничений компонентов на вашей платформе, на этом диске нельзя монтировать/использовать тома на основе раздела/устройства.\n\nВозможные решения:\n- Создайте на диске том на основе файла (контейнер).\n- Используйте диск с 512-байтовыми секторами.\n- Используйте VeraCrypt на другой платформе.</entry>
     <entry lang="ru" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">Хост-файл/устройство уже используется.</entry>
     <entry lang="ru" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Слот для тома недоступен.</entry>
-    <entry lang="ru" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">Для VeraCrypt требуется OSXFUSE 2.5 или новее.</entry>
+    <entry lang="ru" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">Для VeraCrypt требуется macFUSE 2.5 или новее.</entry>
     <entry lang="ru" key="EXCEPTION_OCCURRED">Произошло исключение</entry>
     <entry lang="ru" key="ENTER_PASSWORD">Введите пароль</entry>
     <entry lang="ru" key="ENTER_TC_VOL_PASSWORD">Введите пароль тома VeraCrypt</entry>
@@ -1644,6 +1644,50 @@
     <entry lang="ru" key="MOUNTPOINT_BLOCKED">ОШИБКА: Точка монтирования тома заблокирована, так как она переопределяет защищённую системную папку.\n\nВыберите другую точку монтирования.</entry>
     <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. Это может привести к утечке конфиденциальных данных через средства создания скриншотов и записи экрана, такие как 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="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="en" key="TC_INSTALLER_IS_RUNNING">VeraCrypt Installer is currently running on this system and performing or preparing installation or update of VeraCrypt. Before you proceed, please wait for it to finish or close it. If you cannot close it, please restart your computer before proceeding.</entry>
     <entry lang="en" key="INSTALL_FAILED">Installation failed.</entry>
     <entry lang="en" key="UNINSTALL_FAILED">Uninstallation failed.</entry>
-    <entry lang="en" key="DIST_PACKAGE_CORRUPTED">This distribution package is damaged. Please try downloading it again (preferably from the official VeraCrypt website at https://www.veracrypt.fr).</entry>
+    <entry lang="en" key="DIST_PACKAGE_CORRUPTED">This distribution package is damaged. Please try downloading it again (preferably from the official VeraCrypt website at https://veracrypt.jp).</entry>
     <entry lang="en" key="CANNOT_WRITE_FILE_X">Cannot write file %s</entry>
     <entry lang="en" key="EXTRACTING_VERB">Extracting</entry>
     <entry lang="en" key="CANNOT_READ_FROM_PACKAGE">Cannot read data from the package.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="en" key="HIDDEN_OS_CREATION_PREINFO_HELP">In the next steps, VeraCrypt will create the hidden operating system by copying the content of the system partition to the hidden volume (data being copied will be encrypted on the fly with an encryption key different from the one that will be used for the decoy operating system).\n\nPlease note that the process will be performed in the pre-boot environment (before Windows starts) and it may take a long time to complete; several hours or even several days (depending on the size of the system partition and on the performance of your computer).\n\nYou will be able to interrupt the process, shut down your computer, start the operating system and then resume the process. However, if you interrupt it, the entire process of copying the system will have to start from the beginning (because the content of the system partition must not change during cloning).</entry>
     <entry lang="en" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Do you want to cancel the entire process of creation of the hidden operating system?\n\nNote: You will NOT be able to resume the process if you cancel it now.</entry>
     <entry lang="en" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Do you want to cancel the system encryption pretest?</entry>
-    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="en" key="SYS_DRIVE_NOT_ENCRYPTED">The system partition/drive does not appear to be encrypted (neither partially nor fully).</entry>
     <entry lang="en" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Your system partition/drive is encrypted (partially or fully).\n\nPlease decrypt your system partition/drive entirely before proceeding. To do so, select 'System' &gt; 'Permanently Decrypt System Partition/Drive' from the menu bar of the main VeraCrypt window.</entry>
     <entry lang="en" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">When the system partition/drive is encrypted (partially or fully), you cannot downgrade VeraCrypt (but you can upgrade it or reinstall the same version).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="en" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Error: The drive uses a sector size other than 512 bytes.\n\nDue to limitations of components available on your platform, partition/device-hosted volumes cannot be created/used on the drive.\n\nPossible solutions:\n- Create a file-hosted volume (container) on the drive.\n- Use a drive with 512-byte sectors.\n- Use VeraCrypt on another platform.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">The host file/device is already in use.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Volume slot unavailable.</entry>
-    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires OSXFUSE 2.5 or above.</entry>
+    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires macFUSE 2.5 or above.</entry>
     <entry lang="en" key="EXCEPTION_OCCURRED">Exception occurred</entry>
     <entry lang="en" key="ENTER_PASSWORD">Enter password</entry>
     <entry lang="en" key="ENTER_TC_VOL_PASSWORD">Enter VeraCrypt Volume Password</entry>
@@ -1644,6 +1644,50 @@
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="sl" key="TC_INSTALLER_IS_RUNNING">Namestitveni program VeraCrypt Installer se trenutno izvaja v tem sistemu in izvaja ali pripravlja namestitev ali posodobitev VeraCrypt. Preden nadaljuješ, počakaj, da se konča, ali pa ga zapri. Če ga ne moreš zapreti, znova zaženi računalnik, preden nadaljuješ.</entry>
     <entry lang="sl" key="INSTALL_FAILED">Namestitev ni uspela.</entry>
     <entry lang="sl" key="UNINSTALL_FAILED">Odstranitev ni uspela.</entry>
-    <entry lang="sl" key="DIST_PACKAGE_CORRUPTED">Ta distribucijski paket je poškodovan. Poskusi ga znova prenesti (po možnosti z uradne spletne strani VeraCrypt na naslovu https://www.veracrypt.fr).</entry>
+    <entry lang="sl" key="DIST_PACKAGE_CORRUPTED">Ta distribucijski paket je poškodovan. Poskusi ga znova prenesti (po možnosti z uradne spletne strani VeraCrypt na naslovu https://veracrypt.jp).</entry>
     <entry lang="sl" key="CANNOT_WRITE_FILE_X">Ne morem zapisati datoteke %s</entry>
     <entry lang="sl" key="EXTRACTING_VERB">Ekstrakcija</entry>
     <entry lang="sl" key="CANNOT_READ_FROM_PACKAGE">Ne morem brati podatkov iz paketa.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="sl" key="HIDDEN_OS_CREATION_PREINFO_HELP">V naslednjih korakih bo VeraCrypt ustvaril skriti operacijski sistem s kopiranjem vsebine sistemske particije na skriti nosilec (podatki, ki se kopirajo, bodo sproti šifrirani s šifrirnim ključem, ki se razlikuje od tistega, ki se bo uporabljal za operacijo z vabnim sistemom).\n\nUpoštevaj, da bo postopek izveden v predzagonskem okolju (pred zagonom sistema Windows) in lahko traja dolgo časa; več ur ali celo več dni (odvisno od velikosti sistemske particije in zmogljivosti vašega računalnika).\n\nProces boš lahko prekinil, izklopil računalnik, zagnal operacijski sistem in nato nadaljeval s postopkom . Če pa ga prekineš, bo treba celoten proces kopiranja sistema začeti od začetka (ker se vsebina sistemske particije med kloniranjem ne sme spreminjati).</entry>
     <entry lang="sl" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Ali želiš preklicati celoten postopek ustvarjanja skritega operacijskega sistema?\n\nOpomba: Če ga zdaj prekličeš, postopka NE boš mogel nadaljevati.</entry>
     <entry lang="sl" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Ali želiš preklicati predpreizkus šifriranja sistema?</entry>
-    <entry lang="sl" key="BOOT_PRETEST_FAILED_RETRY">Predpreizkus šifriranja sistema VeraCrypt ni uspel. Ali želiš poskusiti znova?\n\nČe izbereš »Ne«, bo komponenta za preverjanje pristnosti pred zagonom odstranjena.\n\nOpombe:\n\n- Če zagonski nalagalnik VeraCrypt ni zahteval vnosa gesla preden se Windows zažene, je možno, da se tvoj operacijski sistem ne zažene s pogona, na katerem je nameščen. To ni podprto.\n\n- Če si uporabil šifrirni algoritem, ki ni AES, in predtestiranje ni uspelo (in si vnesel geslo), je to morda povzročil neustrezno oblikovan gonilnik. Izberi »Ne« in znova poskusi šifrirati sistemsko particijo/pogon, vendar uporabi šifrirni algoritem AES (ki ima najnižje pomnilniške zahteve).\n\n- Za več možnih vzrokov in rešitev glej: https://www. veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="sl" key="BOOT_PRETEST_FAILED_RETRY">Predpreizkus šifriranja sistema VeraCrypt ni uspel. Ali želiš poskusiti znova?\n\nČe izbereš »Ne«, bo komponenta za preverjanje pristnosti pred zagonom odstranjena.\n\nOpombe:\n\n- Če zagonski nalagalnik VeraCrypt ni zahteval vnosa gesla preden se Windows zažene, je možno, da se tvoj operacijski sistem ne zažene s pogona, na katerem je nameščen. To ni podprto.\n\n- Če si uporabil šifrirni algoritem, ki ni AES, in predtestiranje ni uspelo (in si vnesel geslo), je to morda povzročil neustrezno oblikovan gonilnik. Izberi »Ne« in znova poskusi šifrirati sistemsko particijo/pogon, vendar uporabi šifrirni algoritem AES (ki ima najnižje pomnilniške zahteve).\n\n- Za več možnih vzrokov in rešitev glej: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="sl" key="SYS_DRIVE_NOT_ENCRYPTED">Sistemska particija/pogon očitno ni šifrirana (ne deloma ali v celoti).</entry>
     <entry lang="sl" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Tvoja sistemska particija/pogon je šifriran (delno ali v celoti).\n\nPred nadaljevanjem v celoti dešifriraj svojo sistemsko particijo/pogon. To storiš tako, da v menijski vrstici glavnega okna VeraCrypt izbereš 'Sistem' &gt; 'Trajno dešifriraj sistemsko particijo/pogon'.</entry>
     <entry lang="sl" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">Ko je sistemska particija/pogon šifriran (delno ali v celoti), VeraCrypt ne moreš spremeniti v prejšnjo različico (lahko pa ga nadgradiš ali znova namestiš isto različico).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="sl" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Napaka: pogon uporablja velikost sektorja, ki ni 512 bajtov.\n\nZaradi omejitev komponent, ki so na voljo na tvoji platformi, nosilcev, ki gostujejo v particiji/napravi, ni mogoče ustvariti/uporabiti na disku.\n\nMožne rešitve:\n- Na pogonu ustvari nosilec (vsebnik), ki gostuje v datotekah.\n- Uporabi pogon s 512-bajtnimi sektorji.\n- Uporabi VeraCrypt na drugi platformi.</entry>
     <entry lang="sl" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">Gostiteljska datoteka/naprava je že v uporabi.</entry>
     <entry lang="sl" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Reža nosilca ni na voljo.</entry>
-    <entry lang="sl" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt zahteva OSXFUSE 2.5 ali novejši.</entry>
+    <entry lang="sl" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt zahteva macFUSE 2.5 ali novejši.</entry>
     <entry lang="sl" key="EXCEPTION_OCCURRED">Prišlo je do izjeme</entry>
     <entry lang="sl" key="ENTER_PASSWORD">Vnesi geslo</entry>
     <entry lang="sl" key="ENTER_TC_VOL_PASSWORD">Vnesi geslo nosilca VeraCrypt</entry>
@@ -1644,6 +1644,50 @@
     <entry lang="sl" key="MOUNTPOINT_BLOCKED">NAPAKA: Tocka priklopa nosilca je blokirana, ker prekriva zašciteno sistemsko mapo.\n\nIzberite drugo tocko priklopa.</entry>
     <entry lang="sl" key="MOUNTPOINT_NOTALLOWED">NAPAKA: Tocka priklopa nosilca ni dovoljena, ker prekriva mapo, ki je del okoljske spremenljivke PATH.\n\nIzberite drugo tocko priklopa.</entry>
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="sv" key="TC_INSTALLER_IS_RUNNING">VeraCrypts installationsprogram körs för närvarande på detta system och utför eller förbereder installation eller uppdatering av VeraCrypt. Innan du fortsätter, vänta tills den är klar eller stäng den. Om du inte kan stänga den, starta om datorn innan du fortsätter.</entry>
     <entry lang="sv" key="INSTALL_FAILED">Installationen misslyckades.</entry>
     <entry lang="sv" key="UNINSTALL_FAILED">Avinstallationen misslyckades.</entry>
-    <entry lang="sv" key="DIST_PACKAGE_CORRUPTED">Detta distributionspaket är skadat. Försök att hämta den igen (helst från den officiella VeraCrypt-webbplatsen på https://www.veracrypt.fr).</entry>
+    <entry lang="sv" key="DIST_PACKAGE_CORRUPTED">Detta distributionspaket är skadat. Försök att hämta den igen (helst från den officiella VeraCrypt-webbplatsen på https://veracrypt.jp).</entry>
     <entry lang="sv" key="CANNOT_WRITE_FILE_X">Det går inte att skriva filen %s</entry>
     <entry lang="sv" key="EXTRACTING_VERB">Extraherar</entry>
     <entry lang="sv" key="CANNOT_READ_FROM_PACKAGE">Kan inte läsa data från paketet.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="sv" key="HIDDEN_OS_CREATION_PREINFO_HELP">I nästa steg kommer VeraCrypt att skapa det dolda operativsystemet genom att kopiera innehållet i systempartitionen till den dolda volymen (data som kopieras kommer att krypteras i farten med en annan krypteringsnyckel än den som kommer att användas för skenoperativsystemetn\nObservera att processen kommer att utföras i miljön före start (innan Windows startar) och det kan ta lång tid att slutföra; flera timmar eller till och med flera dagar (beroende på storleken på systempartitionen och din dators prestanda).\n\nDu kommer att kunna avbryta processen, stänga av datorn, starta operativsystemet och sedan återuppta processen . Men om du avbryter det måste hela processen med att kopiera systemet börja från början (eftersom innehållet i systempartitionen inte får ändras under kloning).</entry>
     <entry lang="sv" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Vill du avbryta hela processen för att skapa det dolda operativsystemet?\n\nObs: Du kommer INTE att kunna återuppta processen om du avbryter den nu.</entry>
     <entry lang="sv" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Vill du avbryta förtestet av systemkrypteringen?</entry>
-    <entry lang="sv" key="BOOT_PRETEST_FAILED_RETRY">VeraCrypt-systemets krypteringsförtest misslyckades. Vill du försöka igen?\n\nOm du väljer "Nej", kommer autentiseringskomponenten före start avinstalleras.\n\nAnmärkningar:\n\n- Om VeraCrypt-startinläsaren inte bad dig att ange lösenordet innan Windows startade är det möjligt att ditt operativsystem inte startar från den enhet som det är installerat på. Detta stöds inte.\n\n- Om du använde en annan krypteringsalgoritm än AES och förtestet misslyckades (och du angav lösenordet), kan det ha orsakats av en olämpligt utformad drivrutin. Välj "Nej" och försök att kryptera systempartitionen/enheten igen, men använd AES-krypteringsalgoritmen (som har de lägsta minneskraven).\n\n- För fler möjliga orsaker och lösningar, se: https://www. veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="sv" key="BOOT_PRETEST_FAILED_RETRY">VeraCrypt-systemets krypteringsförtest misslyckades. Vill du försöka igen?\n\nOm du väljer "Nej", kommer autentiseringskomponenten före start avinstalleras.\n\nAnmärkningar:\n\n- Om VeraCrypt-startinläsaren inte bad dig att ange lösenordet innan Windows startade är det möjligt att ditt operativsystem inte startar från den enhet som det är installerat på. Detta stöds inte.\n\n- Om du använde en annan krypteringsalgoritm än AES och förtestet misslyckades (och du angav lösenordet), kan det ha orsakats av en olämpligt utformad drivrutin. Välj "Nej" och försök att kryptera systempartitionen/enheten igen, men använd AES-krypteringsalgoritmen (som har de lägsta minneskraven).\n\n- För fler möjliga orsaker och lösningar, se: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="sv" key="SYS_DRIVE_NOT_ENCRYPTED">Systempartitionen/enheten verkar inte vara krypterad (varken delvis eller helt).</entry>
     <entry lang="sv" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Din systempartition/enhet är krypterad (delvis eller helt).\n\nDekryptera din systempartition/enhet helt innan du fortsätter. För att göra det, välj "System" &gt; "Dekryptera systempartition/enhet permanent" från menyraden i huvudfönstret i VeraCrypt.</entry>
     <entry lang="sv" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">När systempartitionen/enheten är krypterad (delvis eller helt) kan du inte nedgradera VeraCrypt (men du kan uppgradera den eller installera om samma version).</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>
@@ -1553,7 +1553,7 @@
     <entry lang="sv" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Fel: Enheten använder en annan sektorstorlek än 512 byte.\n\nPå grund av begränsningar av komponenter som är tillgängliga på din plattform kan partitions-/enhetsvärdade volymer inte skapas/användas på enheten.\n\nMöjliga lösningar:\n- Skapa en filvärdad volym (behållare) på enheten.\n- Använd en enhet med 512-byte sektorer.\n- Använd VeraCrypt på en annan plattform.</entry>
     <entry lang="sv" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">Värdfilen/-enheten används redan.</entry>
     <entry lang="sv" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Volymplatsen är inte tillgänglig.</entry>
-    <entry lang="sv" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt kräver OSXFUSE 2.5 eller högre.</entry>
+    <entry lang="sv" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt kräver macFUSE 2.5 eller högre.</entry>
     <entry lang="sv" key="EXCEPTION_OCCURRED">Undantag inträffade</entry>
     <entry lang="sv" key="ENTER_PASSWORD">Ange lösenord</entry>
     <entry lang="sv" key="ENTER_TC_VOL_PASSWORD">Ange lösenord för VeraCrypt-volym</entry>
@@ -1644,6 +1644,50 @@
     <entry lang="sv" key="MOUNTPOINT_BLOCKED">FEL: Volymens monteringspunkt är blockerad eftersom den skriver över en skyddad systemkatalog.\n\nVar god välj en annan monteringspunkt.</entry>
     <entry lang="sv" key="MOUNTPOINT_NOTALLOWED">FEL: Volymens monteringspunkt är inte tillåten eftersom den skriver över en katalog som är en del av miljövariabeln PATH.\n\nVar god välj en annan monteringspunkt.</entry>
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="th" key="TC_INSTALLER_IS_RUNNING">ตัวติดตั้ง VeraCrypt กำลังทำงานในระบบนี้และกำลังดำเนินการติดตั้งหรือเตรียมการติดตั้ง/อัพเดต VeraCrypt ก่อนที่คุณจะดำเนินการ โปรดรอให้เสร็จสิ้นหรือลองปิดมัน หากคุณไม่สามารถปิดมันได้ โปรดรีสตาร์ทคอมพิวเตอร์ก่อนการดำเนินการ</entry>
     <entry lang="th" key="INSTALL_FAILED">การติดตั้งล้มเหลว</entry>
     <entry lang="th" key="UNINSTALL_FAILED">การถอนการติดตั้งล้มเหลว</entry>
-    <entry lang="th" key="DIST_PACKAGE_CORRUPTED">แพ็คเกจการจัดจำหน่ายนี้เสียหาย โปรดลองดาวน์โหลดใหม่อีกครั้ง (จากเว็บไซต์ทางการของ VeraCrypt ที่ https://www.veracrypt.fr)</entry>
+    <entry lang="th" key="DIST_PACKAGE_CORRUPTED">แพ็คเกจการจัดจำหน่ายนี้เสียหาย โปรดลองดาวน์โหลดใหม่อีกครั้ง (จากเว็บไซต์ทางการของ VeraCrypt ที่ https://veracrypt.jp)</entry>
     <entry lang="th" key="CANNOT_WRITE_FILE_X">ไม่สามารถเขียนไฟล์ %s ได้</entry>
     <entry lang="th" key="EXTRACTING_VERB">กำลังสกัด</entry>
     <entry lang="th" key="CANNOT_READ_FROM_PACKAGE">ไม่สามารถอ่านข้อมูลจากแพ็คเกจได้</entry>
@@ -1096,7 +1096,7 @@
     <entry lang="th" key="RESTRICT_PAGING_FILES_TO_SYS_PARTITION">คุณต้องการกำหนดค่า Windows ให้สร้างไฟล์เพจจิ้งเฉพาะบนพาร์ติชัน Windows ทันทีหรือไม่?\n\nโปรดทราบว่าหากคุณคลิก 'ใช่', คอมพิวเตอร์จะรีสตาร์ท. จากนั้นเริ่มใช้งาน VeraCrypt และลองสร้างระบบที่ถูกแอบซ่อนอีกครั้ง.</entry>
     <entry lang="th" key="LEAKS_OUTSIDE_SYSPART_UNIVERSAL_EXPLANATION"> มิฉะนั้น, การปฏิเสธที่มีเหตุผลของระบบที่ถูกแอบซ่อนอาจถูกกระทบอย่างรุนแรง.\n\nหมายเหตุ: ถ้าคู่แข็งวิเคราะห์เนื้อหาของไฟล์ดังกล่าว (ที่อยู่บนพาร์ติชันที่ไม่ใช่ระบบ), เขาอาจพบว่าคุณใช้วิซาร์ดนี้ในโหมดการสร้างระบบที่ถูกแอบซ่อน (ซึ่งอาจบ่งบอกถึงการมีอยู่ของระบบที่ถูกแอบซ่อนบนคอมพิวเตอร์ของคุณ). นอกจากนี้ โปรดทราบว่าไฟล์ใดๆ ที่เก็บไว้บนพาร์ติชันระบบจะถูกลบอย่างมีความปลอดภัยโดย VeraCrypt ในกระบวนการสร้างระบบที่ถูกแอบซ่อน.</entry>
     <entry lang="th" key="DECOY_OS_REINSTALL_WARNING">คำเตือน: ในกระบวนการสร้างระบบที่ถูกแอบซ่อน, คุณจะต้องติดตั้งระบบที่กำลังทำงานอยู่ตอนนี้ใหม่ทั้งหมด (เพื่อที่จะสร้างระบบเลียนแบบอย่างปลอดภัย).\n\nหมายเหตุ: ระบบปฏิบัติการที่กำลังทำงานอยู่ในตอนนี้และเนื้อหาทั้งหมดของพาร์ติชันจะถูกคัดลอกไปยังห้วงแอบซ่อน (เพื่อสร้างระบบที่ถูกแอบซ่อน).\n\n\nคุณแน่ใจหรือไม่ว่าคุณจะสามารถติดตั้ง Windows โดยใช้สื่อการติดตั้ง Windows (หรือใช้พาร์ติชันบริการ)?</entry>
-    <entry lang="th" key="DECOY_OS_REQUIREMENTS">เพื่อเหตุผลด้านความปลอดภัย, ถ้าระบบปฏิบัติการที่กำลังทำงานอยู่ตอนนี้ต้องการการเปิดใช้งาน, มันต้องถูกเปิดใช้งานก่อนดำเนินการต่อ. โปรดทราบว่าระบบปฏิบัติการที่ถูกแอบซ่อนจะถูกสร้างขึ้นโดยคัดลอกเนื้อหาของพาร์ติชันระบบไปยังห้วงแอบซ่อน (ดังนั้นหากระบบปฏิบัติการนี้ไม่ถูกเปิดใช้งาน, ระบบปฏิบัติการที่ถูกซ่อนจะไม่ถูกเปิดใช้งานเช่นกัน). สำหรับข้อมูลเพิ่มเติม, โปรดดูที่หมวด "ข้อกำหนดและข้อควรระวังด้านความปลอดภัยที่เกี่ยวข้องกับห้วงแอบซ่อน" ในคู่มือผู้ใช้ VeraCrypt.\n\nสำคัญ: ก่อนดำเนินการต่อ, โปรดแน่ใจว่าคุณได้อ่านหมวด "ข้อกำหนดและข้อควรระวังด้านความปลอดภัยที่เกี่ยวข้องกับห้วงแอบซ่อน" ในคู่มือผู้ใช้ VeraCrypt.\n\n\nระบบปฏิบัติการที่กำลังทำงานอยู่ตอนนี้ตรงตามเงื่อนไขข้างต้นหรือไม่?\</entry>
+    <entry lang="th" key="DECOY_OS_REQUIREMENTS">เพื่อเหตุผลด้านความปลอดภัย, ถ้าระบบปฏิบัติการที่กำลังทำงานอยู่ตอนนี้ต้องการการเปิดใช้งาน, มันต้องถูกเปิดใช้งานก่อนดำเนินการต่อ. โปรดทราบว่าระบบปฏิบัติการที่ถูกแอบซ่อนจะถูกสร้างขึ้นโดยคัดลอกเนื้อหาของพาร์ติชันระบบไปยังห้วงแอบซ่อน (ดังนั้นหากระบบปฏิบัติการนี้ไม่ถูกเปิดใช้งาน, ระบบปฏิบัติการที่ถูกซ่อนจะไม่ถูกเปิดใช้งานเช่นกัน). สำหรับข้อมูลเพิ่มเติม, โปรดดูที่หมวด "ข้อกำหนดและข้อควรระวังด้านความปลอดภัยที่เกี่ยวข้องกับห้วงแอบซ่อน" ในคู่มือผู้ใช้ VeraCrypt.\n\nสำคัญ: ก่อนดำเนินการต่อ, โปรดแน่ใจว่าคุณได้อ่านหมวด "ข้อกำหนดและข้อควรระวังด้านความปลอดภัยที่เกี่ยวข้องกับห้วงแอบซ่อน" ในคู่มือผู้ใช้ VeraCrypt.\n\n\nระบบปฏิบัติการที่กำลังทำงานอยู่ตอนนี้ตรงตามเงื่อนไขข้างต้นหรือไม่?</entry>
     <entry lang="th" key="CONFIRM_HIDDEN_OS_EXTRA_BOOT_PARTITION">ระบบของคุณใช้พาร์ติชันบูทเพิ่มเติม. VeraCrypt ไม่รองรับการพักตัวของระบบปฏิบัติการที่ถูกแอบซ่อนที่ใช้พาร์ติชันบูทเพิ่มเติม (ระบบเลียนแบบสามารถพักตัวได้โดยไม่มีปัญหา).\n\nโปรดทราบว่าพาร์ติชันบูทจะถูกใช้ร่วมกันโดยทั้งระบบเลียนแบบและระบบที่ถูกแอบซ่อน. ดังนั้น, เพื่อป้องกันการรั่วไหลของข้อมูลและปัญหาในขณะเรียกคืนจากสถานะการพักตัว, VeraCrypt จำเป็นต้องป้องกันไม่ให้ระบบที่แอบเขียนไปยังพาร์ติชันบูทที่ใช้ร่วมกันและจากการพักตัว.\n\n\nคุณต้องการดำเนินการต่อหรือไม่? ถ้าคุณเลือก 'ไม่', คำแนะนำสำหรับการลบพาร์ติชันบูทเพิ่มเติมจะแสดงขึ้น.</entry>
     <entry lang="th" key="EXTRA_BOOT_PARTITION_REMOVAL_INSTRUCTIONS">\nพาร์ติชันบูทเพิ่มเติมสามารถลบออกก่อติดตั้ง Windows. ทำตามขั้นตอนต่อไปนี้:\n\n1) บูตแผ่นติดตั้ง Windows ของคุณ.\n\n2) ในหน้าจอติดตั้ง Windows, คลิก 'Install now' > 'Custom (advanced)'.\n\n3) คลิก 'Drive Options'.\n\n4) เลือกพาร์ติชันระบบหลักแล้วลบมันโดยคลิก 'Delete' และ 'OK'.\n\n5) เลือกพาร์ติชัน 'System Reserved', คลิก 'Extend', และเพิ่มขนาดมันเพื่อให้สามารถติดตั้งระบบปฏิบัติการลงไปได้.\n\n6) คลิก 'Apply' และ 'OK'.\n\n7) ติดตั้ง Windows บนพาร์ติชัน 'System Reserved'.\n\n\nถ้ามีผู้โจมตีถามว่าทำไมคุณลบพาร์ติชันบูทเพิ่มเติม, คุณสามารถตอบว่าคุณต้องการป้องกันการรั่วไหลข้อมูลใดๆ ไปยังพาร์ติชันบูทที่ไม่ได้เข้ารหัส.\n\nหมายเหตุ: คุณสามารถพิมพ์ข้อความนี้โดยคลิกปุ่ม 'Print' ด้านล่าง. ถ้าคุณบันทึกสำเนาของข้อความนี้หรือพิมพ์มัน (แนะนำอย่างยิ่ง, ยกเว้นว่าปริ้นเตอร์ของคุณเก็บสำเนาของเอกสารที่พิมพ์ลงในฮาร์ดไดรฟ์ภายใน), คุณควรทำลายสำเนานั้นหลังจากลบพาร์ติชันบูทเพิ่มเติม (มิฉะนั้น, หากพบสำเนาดังกล่าว, อาจบ่งบอกถึงการมีอยู่ของระบบปฏิบัติการที่ถูกแอบซ่อนบนคอมพิวเตอร์นี้).</entry>
     <entry lang="th" key="GAP_BETWEEN_SYS_AND_HIDDEN_OS_PARTITION">คำเตือน: มีพื้นที่ที่ไม่ได้จัดสรรระหว่างระบบพาร์ติชันและพาร์ติชันแรกที่อยู่ด้านหลังมัน. หลังจากที่คุณสร้างระบบปฏิบัติการที่ถูกแอบซ่อน, คุณต้องไม่สร้างพาร์ติชันใหม่ในพื้นที่ที่ไม่ได้จัดสรรนั้น. มิฉะนั้น, ระบบปฏิบัติการที่ถูกแอบซ่อนจะไม่สามารถบูทได้ (จนกว่าคุณจะลบพาร์ติชันที่สร้างขึ้นใหม่).</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="th" key="HIDDEN_OS_CREATION_PREINFO_HELP">ในขั้นตอนถัดไป, VeraCrypt จะสร้างระบบปฏิบัติการที่ซ่อนโดยการคัดลอกเนื้อหาของพาร์ติชันระบบไปยังปริมาณที่ซ่อน (ข้อมูลที่ถูกคัดลอกจะถูกเข้ารหัสทันทีโดยใช้คีย์เข้ารหัสที่แตกต่างจากที่ใช้กับระบบปฏิบัติการเลียนแบบ).\n\nโปรดทราบว่ากระบวนการจะถูกดำเนินการในสภาพแวดล้อมก่อนบูท (ก่อนที่ Windows จะเริ่มทำงาน) และอาจใช้เวลานานในการเสร็จสิ้น; หลายชั่วโมงหรือแม้กระทั่งหลายวัน (ขึ้นอยู่กับขนาดของพาร์ติชันระบบและสมรรถนะของคอมพิวเตอร์ของคุณ).\n\nคุณจะสามารถขัดจังหวะกระบวนการ, ปิดคอมพิวเตอร์ของคุณ, เริ่มระบบปฏิบัติการใหม่และจากนั้นกลับมากระบวนการ. อย่างไรก็ตาม, หากคุณขัดจังหวะมัน, กระบวนการทั้งหมดของการคัดลอกระบบจะต้องเริ่มต้นใหม่ตั้งแต่ต้น (เนื่องจากเนื้อหาของพาร์ติชันระบบต้องไม่เปลี่ยนแปลงในระหว่างการโคลนนิ่ง).</entry>
     <entry lang="th" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">คุณต้องการยกเลิกกระบวนการสร้างระบบปฏิบัติการที่ซ่อนทั้งหมดหรือไม่?\n\nหมายเหตุ: คุณจะไม่สามารถกลับมากระบวนการได้หากคุณยกเลิกตอนนี้.</entry>
     <entry lang="th" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">คุณต้องการยกเลิกการทดสอบเข้ารหัสระบบก่อนหรือไม่?</entry>
-    <entry lang="th" key="BOOT_PRETEST_FAILED_RETRY">การทดสอบเข้ารหัสระบบ VeraCrypt ล้มเหลว. คุณต้องการลองอีกครั้งไหม?\n\nถ้าคุณเลือก 'ไม่', ส่วนประกอบการรับรองก่อนบูทจะถูกถอนการติดตั้ง.\n\nหมายเหตุ:\n\n- ถ้าบูทโหลดเดอร์ VeraCrypt ไม่ขอให้คุณป้อนรหัสผ่านก่อนที่ Windows จะเริ่มทำงาน, เป็นไปได้ว่าระบบปฏิบัติการของคุณไม่ได้บูทจากไดรฟ์ที่ติดตั้ง. นี้ไม่รองรับ.\n\n- ถ้าคุณใช้อัลกอริธึมการเข้ารหัสที่ไม่ใช่ AES และการทดสอบล้มเหลว (และคุณป้อนรหัสผ่าน), อาจเกิดจากไดรเวอร์ที่ออกแบบไม่ดี. เลือก 'ไม่', และลองเข้ารหัสพาร์ติชัน/ไดรฟ์ระบบอีกครั้ง, แต่ใช้ AES ซึ่งมีความต้องการหน่วยความจำต่ำสุด.\n\n- สำหรับสาเหตุและวิธีการแก้ไขเพิ่มเติม, ดูที่: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="th" key="BOOT_PRETEST_FAILED_RETRY">การทดสอบเข้ารหัสระบบ VeraCrypt ล้มเหลว. คุณต้องการลองอีกครั้งไหม?\n\nถ้าคุณเลือก 'ไม่', ส่วนประกอบการรับรองก่อนบูทจะถูกถอนการติดตั้ง.\n\nหมายเหตุ:\n\n- ถ้าบูทโหลดเดอร์ VeraCrypt ไม่ขอให้คุณป้อนรหัสผ่านก่อนที่ Windows จะเริ่มทำงาน, เป็นไปได้ว่าระบบปฏิบัติการของคุณไม่ได้บูทจากไดรฟ์ที่ติดตั้ง. นี้ไม่รองรับ.\n\n- ถ้าคุณใช้อัลกอริธึมการเข้ารหัสที่ไม่ใช่ AES และการทดสอบล้มเหลว (และคุณป้อนรหัสผ่าน), อาจเกิดจากไดรเวอร์ที่ออกแบบไม่ดี. เลือก 'ไม่', และลองเข้ารหัสพาร์ติชัน/ไดรฟ์ระบบอีกครั้ง, แต่ใช้ AES ซึ่งมีความต้องการหน่วยความจำต่ำสุด.\n\n- สำหรับสาเหตุและวิธีการแก้ไขเพิ่มเติม, ดูที่: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="th" key="SYS_DRIVE_NOT_ENCRYPTED">พาร์ติชัน/ไดรฟ์ระบบดูเหมือนไม่ได้เข้ารหัส (ไม่ว่าจะบางส่วนหรือทั้งหมด).</entry>
     <entry lang="th" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">พาร์ติชัน/ไดรฟ์ระบบของคุณถูกเข้ารหัส (บางส่วนหรือทั้งหมด).\n\nกรุณาถอดรหัสพาร์ติชัน/ไดรฟ์ระบบของคุณทั้งหมดก่อนดำเนินการต่อ. ทำได้โดยเลือก 'System' &gt; 'Permanently Decrypt System Partition/Drive' จากแถบเมนูของหน้าต่างหลัก VeraCrypt.</entry>
     <entry lang="th" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">เมื่อพาร์ติชัน/ไดรฟ์ระบบถูกเข้ารหัส (บางส่วนหรือทั้งหมด), คุณไม่สามารถลดเวอร์ชัน VeraCrypt (แต่คุณสามารถอัปเกรดหรือติดตั้งเวอร์ชันเดียวกันใหม่ได้).</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>
@@ -1554,7 +1553,7 @@
     <entry lang="th" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">ข้อผิดพลาด: ไดรฟ์ใช้ขนาดเซ็กเตอร์อื่นที่ไม่ใช่ 512 ไบต์.\n\nเนื่องจากข้อจำกัดของส่วนประกอบที่มีในแพลตฟอร์มของคุณ, พาร์ติชัน/อุปกรณ์-โฮสต์ปริมาณไม่สามารถสร้าง/ใช้บนไดรฟ์ได้.\n\nวิธีแก้ปัญหาที่เป็นไปได้:\n- สร้างปริมาณโฮสต์ไฟล์ (ตัวเก็บ) บนไดรฟ์.\n- ใช้ไดรฟ์ที่มีเซ็กเตอร์ 512-ไบต์.\n- ใช้ VeraCrypt บนแพลตฟอร์มอื่น.</entry>
     <entry lang="th" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">ไฟล์/อุปกรณ์โฮสต์ใช้งานอยู่แล้ว.</entry>
     <entry lang="th" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">ช่องปริมาณไม่มีใช้งาน.</entry>
-    <entry lang="th" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt ต้องการ OSXFUSE 2.5 หรือใหม่กว่า.</entry>
+    <entry lang="th" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt ต้องการ macFUSE 2.5 หรือใหม่กว่า.</entry>
     <entry lang="th" key="EXCEPTION_OCCURRED">เกิดข้อยกเว้น</entry>
     <entry lang="th" key="ENTER_PASSWORD">ป้อนรหัสผ่าน</entry>
     <entry lang="th" key="ENTER_TC_VOL_PASSWORD">ป้อนรหัสผ่านปริมาณ VeraCrypt</entry>
@@ -1645,6 +1644,50 @@
     <entry lang="th" key="MOUNTPOINT_BLOCKED">ข้อผิดพลาด: จุดเชื่อมต่อโวลุ่มถูกบล็อกเนื่องจากไปทับซ้อนกับไดเรกทอรีระบบที่ได้รับการป้องกัน\n\nกรุณาเลือกจุดเชื่อมต่ออื่น</entry>
     <entry lang="th" key="MOUNTPOINT_NOTALLOWED">ข้อผิดพลาด: จุดเชื่อมต่อโวลุ่มไม่ได้รับอนุญาตเนื่องจากไปทับซ้อนกับไดเรกทอรีที่เป็นส่วนหนึ่งของตัวแปร PATH\n\nกรุณาเลือกจุดเชื่อมต่ออื่น</entry>
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="tr" key="TC_INSTALLER_IS_RUNNING">VeraCrypt kurucu şu anda bu sistemde çalışıyor ve VeraCrypt kurulumu ya da güncellemesi işlemlerini yapıyor ya da hazırlıyor. İlerlemeden önce lütfen işlemin tamamlanmasını bekleyin ya da kapatın. Uygulamayı kapatamıyorsanız, ilerlemeden önce lütfen bilgisayarınızı yeniden başlatın.</entry>
     <entry lang="tr" key="INSTALL_FAILED">Kurulamadı.</entry>
     <entry lang="tr" key="UNINSTALL_FAILED">Kaldırılamadı.</entry>
-    <entry lang="tr" key="DIST_PACKAGE_CORRUPTED">Dağıtım paketi bozulmuş. Lütfen yeniden indirmeyi deneyin (https://www.veracrypt.fr resmi VeraCrypt sitesini yeğleyin).</entry>
+    <entry lang="tr" key="DIST_PACKAGE_CORRUPTED">Dağıtım paketi bozulmuş. Lütfen yeniden indirmeyi deneyin (https://veracrypt.jp resmi VeraCrypt sitesini yeğleyin).</entry>
     <entry lang="tr" key="CANNOT_WRITE_FILE_X">%s dosyasına yazılamadı</entry>
     <entry lang="tr" key="EXTRACTING_VERB">Ayıklanıyor</entry>
     <entry lang="tr" key="CANNOT_READ_FROM_PACKAGE">Paketten veriler okunamadı.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="tr" key="HIDDEN_OS_CREATION_PREINFO_HELP">Sonraki adımlarda VeraCrypt, sistem bölümünün içeriğini gizli birime kopyalayarak gizli işletim sistemini oluşturacak (kopyalanan veriler, sahte işletim sistemi için kullanılacak olandan farklı bir şifreleme anahtarıyla anında şifrelenecek).\n\nİşlemin başlatma öncesi ortamda (Windows başlamadan önce) gerçekleştirileceğini ve tamamlanmasının uzun sürebileceğini lütfen unutmayın (bilgisayarınızın başarımına ve sistem bölümünün boyutuna bağlı olarak birkaç saat ya da birkaç gün).\n\nİşlemi yarıda kesebilir, bilgisayarınızı kapatabilir, işletim sistemini başlatabilir ve ardından işlemi sürdürebilirsiniz. Ancak işlemi yarıda keserseniz, sistemin tüm kopyalama sürecine en baştan başlaması gerekir (çünkü sistem bölümünün içeriğinin kopyalama sırasında değişmemesi gerekir).</entry>
     <entry lang="tr" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Gizli işletim sisteminin oluşturulma sürecini tümüyle iptal etmek istiyor musunuz?\n\nNot: Şimdi iptal ederseniz işlemi sürdüremeyeceksiniz.</entry>
     <entry lang="tr" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Sistem şifrelemesi için ön sınamayı iptal etmek istiyor musunuz?</entry>
-    <entry lang="tr" key="BOOT_PRETEST_FAILED_RETRY">VeraCrypt sistem şifreleme ön sınaması başarısız oldu. Yeniden denemek ister misiniz?\n\n'Hayır' üzerine tıklarsanız, başlatma öncesi kimlik doğrulama bileşeni kaldırılır.\n\nNotlar:\n\n- VeraCrypt başlatma yükleyicisi Windows başlamadan önce sizden parolayı yazmanızı istemediyse, işletim sisteminiz kurulu olduğu sürücüden başlatılamayabilir. Bu durum desteklenmiyor.\n\n- AES dışında bir şifreleme algoritması kullandıysanız ve ön sınama başarısız olduysa (ve parolayı yazdıysanız), bunun nedeni uygun olmayan şekilde tasarlanmış bir sürücü olabilir. 'Hayır' üzerine tıklayın ve sistem bölümünü ya da sürücüsünü yeniden şifrelemeyi deneyin, ancak (en düşük bellek gereksinimleri olan) AES şifreleme algoritmasını kullanın.\n\n- Diğer olası nedenler ve çözümleri için şu adrese bakabilirsiniz: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="tr" key="BOOT_PRETEST_FAILED_RETRY">VeraCrypt sistem şifreleme ön sınaması başarısız oldu. Yeniden denemek ister misiniz?\n\n'Hayır' üzerine tıklarsanız, başlatma öncesi kimlik doğrulama bileşeni kaldırılır.\n\nNotlar:\n\n- VeraCrypt başlatma yükleyicisi Windows başlamadan önce sizden parolayı yazmanızı istemediyse, işletim sisteminiz kurulu olduğu sürücüden başlatılamayabilir. Bu durum desteklenmiyor.\n\n- AES dışında bir şifreleme algoritması kullandıysanız ve ön sınama başarısız olduysa (ve parolayı yazdıysanız), bunun nedeni uygun olmayan şekilde tasarlanmış bir sürücü olabilir. 'Hayır' üzerine tıklayın ve sistem bölümünü ya da sürücüsünü yeniden şifrelemeyi deneyin, ancak (en düşük bellek gereksinimleri olan) AES şifreleme algoritmasını kullanın.\n\n- Diğer olası nedenler ve çözümleri için şu adrese bakabilirsiniz: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="tr" key="SYS_DRIVE_NOT_ENCRYPTED">Sistem bölümü/sürücüsü şifrelenmiş gibi görünmüyor (bir bölümü ya da tümü).</entry>
     <entry lang="tr" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Sistem bölümünüz ya da sürücünüz şifrelendi (bir bölümü ya da tümü).\n\nİlerlemeden önce lütfen sistem bölümünüzün ya da sürücünüzün şifresini tamamen çözün. Bunu yapmak için, VeraCrypt ana penceresindeki menüden 'Sistem' &gt; 'Sistem bölümünün/sürücüsünün şifresini kalıcı olarak çöz' üzerine tıklayın.</entry>
     <entry lang="tr" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">Sistem bölümü ya da sürücüsü şifrelendiğinde (bir bölümü ya da tümü), VeraCrypt sürümünü düşüremezsiniz (ancak yükseltebilir ya da aynı sürümü yeniden kurabilirsiniz).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="tr" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Hata: Sürücü 512 bayt değerinden farklı bir kesim boyutu kullanıyor.\n\nPlatformunuzda bulunan bileşenlerin sınırlamaları nedeniyle, bölüm ya da aygıt üzerinde barındırılan birimler sürücüde oluşturulamaz ya da kullanılamaz.\n\nOlası çözümler:\n- Sürücüde dosya üzerinde barındırılan bir birim (kapsayıcı) oluşturun.\n- 512 baytlık kesimleri olan bir sürücü kullanın.\n- VeraCrypt uygulamasını başka bir platformda kullanın.</entry>
     <entry lang="tr" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">Barındırılan dosya ya da aygıt zaten kullanılıyor.</entry>
     <entry lang="tr" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Birim konumu kullanılamıyor.</entry>
-    <entry lang="tr" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt için OSXFUSE 2.5 ya da üzeri gereklidir.</entry>
+    <entry lang="tr" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt için macFUSE 2.5 ya da üzeri gereklidir.</entry>
     <entry lang="tr" key="EXCEPTION_OCCURRED">Sorun çıktı</entry>
     <entry lang="tr" key="ENTER_PASSWORD">Parolayı yazın</entry>
     <entry lang="tr" key="ENTER_TC_VOL_PASSWORD">VeraCrypt biriminin parolasını yazın</entry>
@@ -1623,7 +1623,7 @@
     <entry lang="tr" key="EMV_KEYFILE_DATA_NOTFOUND">EMV kartı verilerinden anahtar dosyası oluşturulamadı.\n\nŞunlardan biri eksik:\n- ICC herkese açık anahtar sertifikası.\n- Yayıncının herkese açık anahtar sertifikası.\n- CPLC verileri.</entry>
     <entry lang="tr" key="SCARD_W_REMOVED_CARD">Okuyucuda bir kart yok.\n\nLütfen kartın doğru şekilde yerleştirildiğinden emin olun.</entry>
     <entry lang="tr" key="FORMAT_EXTERNAL_FAILED">Windows format.com komutu, birimi NTFS/exFAT/ReFS olarak biçimlendiremedi: Hata kodu: 0x%.8X.\n\nWindows FormatEx API uygulamasını kullanmaya geri dönülüyor.</entry>
-    <entry lang="en" key="FORMATEX_API_FAILED">Windows FormatEx API uygulaması birimi NTFS/exFAT/ReFS olarak biçimlendiremedi.\n\nHata durumu = %s.</entry>
+    <entry lang="tr" key="FORMATEX_API_FAILED">Windows FormatEx API uygulaması birimi NTFS/exFAT/ReFS olarak biçimlendiremedi.\n\nHata durumu = %s.</entry>
     <entry lang="tr" key="EXPANDER_WRITING_RANDOM_DATA">Yeni alana rastgele veriler yazılıyor...\n</entry>
     <entry lang="tr" key="EXPANDER_WRITING_ENCRYPTED_BACKUP">Yeniden şifrelenmiş yedek üst bilgiler yazılıyor...\n</entry>
     <entry lang="tr" key="EXPANDER_WRITING_ENCRYPTED_PRIMARY">Yeniden şifrelenmiş birincil üst bilgiler yazılıyor...\n</entry>
@@ -1644,6 +1644,50 @@
     <entry lang="tr" key="MOUNTPOINT_BLOCKED">HATA: Birim bağlama noktası, korunan bir sistem dizinini geçersiz kıldığı için engellendi.\n\nLütfen farklı bir bağlama noktası seçin.</entry>
     <entry lang="tr" key="MOUNTPOINT_NOTALLOWED">HATA: Birim bağlama noktası, PATH ortam değişkeninin bir parçası olan bir dizini geçersiz kıldığı için izin verilmiyor.\n\nLütfen farklı bir bağlama noktası seçin.</entry>
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="uk" key="TC_INSTALLER_IS_RUNNING">В этой системе сейчас запущен инсталлятор VeraCrypt. Он выполняет/готовит установку или обновление VeraCrypt. Дождитесь завершения его работы или закройте его. Если закрыть инсталлятор не получается, перезагрузите комп'ютер и лишь потом продолжите.</entry>
     <entry lang="uk" key="INSTALL_FAILED">Невдале встановлювання.</entry>
     <entry lang="uk" key="UNINSTALL_FAILED">Невдале видалення.</entry>
-    <entry lang="uk" key="DIST_PACKAGE_CORRUPTED">Цей файл встановлення пошкоджено. Будь ласка, спробуйте завантажити його знову (рекомендовано з офіційної сторінки VeraCrypt на https://www.veracrypt.fr).</entry>
+    <entry lang="uk" key="DIST_PACKAGE_CORRUPTED">Цей файл встановлення пошкоджено. Будь ласка, спробуйте завантажити його знову (рекомендовано з офіційної сторінки VeraCrypt на https://veracrypt.jp).</entry>
     <entry lang="uk" key="CANNOT_WRITE_FILE_X">Неможливо записати файл %s</entry>
     <entry lang="uk" key="EXTRACTING_VERB">Видобування</entry>
     <entry lang="uk" key="CANNOT_READ_FROM_PACKAGE">Неможливо прочитати дані з файлу встановлювання.</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="uk" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Помилка: диск використовує розмір сектора, відмінний від 512 байт.\n\nЧерез обмеження компонентів, доступних на вашій платформі, томи, що розміщені на розділі/пристрої, не можна створити/використовувати на диску.\n\nМожливі рішення:\n- Створіть том (контейнер) на диску.\n- Використовуйте диск із секторами розміром 512 байт.\n- Використовуйте VeraCrypt на іншій платформі.</entry>
     <entry lang="uk" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">Файл/пристрій, що розміщує том, уже використовується.</entry>
     <entry lang="uk" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Слот тому недоступний.</entry>
-    <entry lang="uk" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt потребує OSXFUSE 2.5 або вище.</entry>
+    <entry lang="uk" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt потребує macFUSE 2.5 або вище.</entry>
     <entry lang="uk" key="EXCEPTION_OCCURRED">Сталася виняткова ситуація</entry>
     <entry lang="uk" key="ENTER_PASSWORD">Введіть пароль</entry>
     <entry lang="uk" key="ENTER_TC_VOL_PASSWORD">Введіть пароль до тому VeraCrypt</entry>
@@ -1644,6 +1644,50 @@
     <entry lang="uk" key="MOUNTPOINT_BLOCKED">ПОМИЛКА: Точка монтування тому заблокована, оскільки вона заміщує захищений системний каталог.\n\nБудь ласка, оберіть іншу точку монтування.</entry>
     <entry lang="uk" key="MOUNTPOINT_NOTALLOWED">ПОМИЛКА: Точка монтування тому не дозволена, оскільки вона заміщує каталог, який є частиною змінної середовища PATH.\n\nБудь ласка, оберіть іншу точку монтування.</entry>
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="uz" key="TC_INSTALLER_IS_RUNNING">В этой системе сейчас запущен инсталлятор VeraCrypt. Он выполняет/готовит установку или обновление VeraCrypt. Дождитесь завершения его работы или закройте его. Если закрыть инсталлятор не получается, перезагрузите компьютер и лишь потом продолжите.</entry>
     <entry lang="uz" key="INSTALL_FAILED">Установка не выполнена.</entry>
     <entry lang="uz" key="UNINSTALL_FAILED">Удаление не выполнено.</entry>
-    <entry lang="uz" key="DIST_PACKAGE_CORRUPTED">Этот дистрибутивный пакет повреждён. Загрузите его снова (желательно с официального сайта VeraCrypt - https://www.veracrypt.fr).</entry>
+    <entry lang="uz" key="DIST_PACKAGE_CORRUPTED">Этот дистрибутивный пакет повреждён. Загрузите его снова (желательно с официального сайта VeraCrypt - https://veracrypt.jp).</entry>
     <entry lang="uz" key="CANNOT_WRITE_FILE_X">Невозможно записать файл %s</entry>
     <entry lang="uz" key="EXTRACTING_VERB">Извлечение</entry>
     <entry lang="uz" key="CANNOT_READ_FROM_PACKAGE">Невозможно прочитать данные из дистрибутива.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="uz" key="HIDDEN_OS_CREATION_PREINFO_HELP">Yf следующих этапах VeraCrypt создаст скрытую ОС, скопировав содержимое системного раздела в скрытый том (копируемые данные шифруются 'на лету' с ключом, отличным от используемого для обманной ОС).\n\nУчтите, что процесс выполняется на предзагрузочной стадии (до запуска Windows) и может занять много времени (несколько часов или даже дней, в зависимости от размера системного раздела и быстродействия ПК).\n\nВы сможете прервать этот процесс, выключить ПК, запустить ОС и затем возобновить его. Однако в случае прерывания, копирование системы придётся начать сначала (так как при клонировании содержимое системного раздела не должно изменяться).</entry>
     <entry lang="uz" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Вы хотите отменить весь процесс создания скрытой операционной системы?\n\nПримечание: в случае отмены вы НЕ сможете возобновить процесс.</entry>
     <entry lang="uz" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Вы хотите отменить пре-тест шифрования системы?</entry>
-    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="uz" key="SYS_DRIVE_NOT_ENCRYPTED">Судя по всему, системный раздел/диск не зашифрован (ни частично, ни полностью).</entry>
     <entry lang="uz" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Системный раздел/диск зашифрован (частично или полностью).\n\nПрежде чем продолжить, полностью дешифруйте системный раздел/диск. Чтобы это сделать, выберите в главном окне VeraCrypt меню 'Система' &gt; 'Permanently Decrypt System Partition/Drive'.</entry>
     <entry lang="en" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">When the system partition/drive is encrypted (partially or fully), you cannot downgrade VeraCrypt (but you can upgrade it or reinstall the same version).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="en" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Error: The drive uses a sector size other than 512 bytes.\n\nDue to limitations of components available on your platform, partition/device-hosted volumes cannot be created/used on the drive.\n\nPossible solutions:\n- Create a file-hosted volume (container) on the drive.\n- Use a drive with 512-byte sectors.\n- Use VeraCrypt on another platform.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">The host file/device is already in use.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Volume slot unavailable.</entry>
-    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires OSXFUSE 2.5 or above.</entry>
+    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires macFUSE 2.5 or above.</entry>
     <entry lang="en" key="EXCEPTION_OCCURRED">Exception occurred</entry>
     <entry lang="en" key="ENTER_PASSWORD">Enter password</entry>
     <entry lang="en" key="ENTER_TC_VOL_PASSWORD">Enter VeraCrypt Volume Password</entry>
@@ -1644,6 +1644,50 @@
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="vi" key="TC_INSTALLER_IS_RUNNING">Bộ cài đặt của VeraCrypt hiện đang chạy trong hệ thống này và đang thi hành hay chuẩn bị việc cài đặt hay cập nhật VeraCrypt. Trước khi bạn tiến hành, xin chờ cho nó chấm dứt hoặc đóng nó lại. Nếu bạn không đóng nó được thì xin bắt đầu máy điện toán của bạn lại trước khi tiến hành.</entry>
     <entry lang="vi" key="INSTALL_FAILED">Không cài đặt được.</entry>
     <entry lang="vi" key="UNINSTALL_FAILED">Không hủy cài đặt được.</entry>
-    <entry lang="vi" key="DIST_PACKAGE_CORRUPTED">Kiện đồ phân phối này bị tổn hại. Xin tải nó xuống lại (tốt hơn là từ trang web chính thức của VeraCrypt tại https://www.veracrypt.fr).</entry>
+    <entry lang="vi" key="DIST_PACKAGE_CORRUPTED">Kiện đồ phân phối này bị tổn hại. Xin tải nó xuống lại (tốt hơn là từ trang web chính thức của VeraCrypt tại https://veracrypt.jp).</entry>
     <entry lang="vi" key="CANNOT_WRITE_FILE_X">Không thể viết vào tập tin %s</entry>
     <entry lang="vi" key="EXTRACTING_VERB">Đang rút ra</entry>
     <entry lang="vi" key="CANNOT_READ_FROM_PACKAGE">Không thể đọc dữ liệu từ kiện đồ được.</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="vi" key="HIDDEN_OS_CREATION_PREINFO_HELP">Trong các bước kế tiếp, VeraCrypt sẽ cấu tạo hệ điều hành ẩn bằng cách sao chép nội dung của phân vùng hệ thống thành tập đĩa ẩn (dữ liệu đã được sao chép sẽ được mã hóa ở bộ phận fly với một khoá mật mã khác với hệ sẽ được sử dụng cho các hệ thống hoạt động nghi trang).\n\nXin lưu ý là quá trình này sẽ được thực hiện trong môi trường tiền khởi động (trước khi bắt đầu Windows) và nó có thể mất một thời gian dài để hoàn thành; vài giờ hoặc thậm chí vài ngày (tùy thuộc vào kích cỡ của hệ thống phân vùng và về hiệu suất của máy điện toán của bạn).\n\n Bạn sẽ có thể làm gián đoạn quá trình,. tắt máy, khởi động hệ điều hành và sau đó tiếp tục lại quá trình. Tuy nhiên, nếu bạn làm gián đoạn nó, toàn bộ quá trình sao chép hệ thống sẽ phải bắt đầu từ đầu (vì nội dung của phân vùng hệ thống không phải thay đổi trong quá trình sao y).</entry>
     <entry lang="vi" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Bạn có muốn hủy bỏ toàn bộ quá trình sáng tạo của hệ điều hành ẩn?\n\nLưu ý: Bạn sẽ không thể tiếp tục lại quá trình nếu bạn hủy bỏ nó ngay bây giờ.</entry>
     <entry lang="vi" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">Bạn có muốn hủy bỏ hệ thống mã hóa thử trước?</entry>
-    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="vi" key="SYS_DRIVE_NOT_ENCRYPTED">Các phân vùng/ổ đĩa hệ thống dường như không được mã hóa (một phần hoặc hoàn toàn).</entry>
     <entry lang="vi" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">Phân vùng/ổ đĩa hệ thống của bạn được mã hóa (một phần hoặc hoàn toàn). \n\nXin giải mã phân vùng/ổ đĩa hệ thống của bạn hoàn toàn trước khi tiến hành. Để làm như vậy, hãy chọn 'Hệ thống'&gt; 'Vĩnh viễn Giải mã Phân vùng/Ổ đĩa Hệ thống' từ thanh trình đơn của cửa sổ VeraCrypt chính.</entry>
     <entry lang="vi" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">Khi phân vùng/ổ đĩa hệ thống được mã hóa (một phần hoặc hoàn toàn), bạn không thể hạ cấp VeraCrypt xuống (nhưng bạn có thể nâng cấp hoặc cài đặt một phiên bản giống vậy lại).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="en" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Error: The drive uses a sector size other than 512 bytes.\n\nDue to limitations of components available on your platform, partition/device-hosted volumes cannot be created/used on the drive.\n\nPossible solutions:\n- Create a file-hosted volume (container) on the drive.\n- Use a drive with 512-byte sectors.\n- Use VeraCrypt on another platform.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">The host file/device is already in use.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Volume slot unavailable.</entry>
-    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires OSXFUSE 2.5 or above.</entry>
+    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires macFUSE 2.5 or above.</entry>
     <entry lang="en" key="EXCEPTION_OCCURRED">Exception occurred</entry>
     <entry lang="vi" key="ENTER_PASSWORD">Điền mật khẩu</entry>
     <entry lang="vi" key="ENTER_TC_VOL_PASSWORD">Nhập vào Mật mã của Tập đĩa VeraCrypt</entry>
@@ -1644,6 +1644,50 @@
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -856,7 +856,7 @@
     <entry lang="zh-cn" key="TC_INSTALLER_IS_RUNNING">VeraCrypt 安装程序正在执行 VeraCrypt 的安装或更新。在您继续进行前，请等待其完成或者关闭它。如果您无法关闭它，请在继续之前重启计算机。</entry>
     <entry lang="zh-cn" key="INSTALL_FAILED">安装失败。</entry>
     <entry lang="zh-cn" key="UNINSTALL_FAILED">卸载失败。</entry>
-    <entry lang="zh-cn" key="DIST_PACKAGE_CORRUPTED">该安装包已经损坏。请尝试重新下载安装包（优先建议从 VeraCrypt 官方网站 https://www.veracrypt.fr 下载）。</entry>
+    <entry lang="zh-cn" key="DIST_PACKAGE_CORRUPTED">该安装包已经损坏。请尝试重新下载安装包（优先建议从 VeraCrypt 官方网站 https://veracrypt.jp 下载）。</entry>
     <entry lang="zh-cn" key="CANNOT_WRITE_FILE_X">不能写入文件 %s</entry>
     <entry lang="zh-cn" key="EXTRACTING_VERB">正在释放</entry>
     <entry lang="zh-cn" key="CANNOT_READ_FROM_PACKAGE">不能从安装包中读取数据</entry>
@@ -1230,7 +1230,7 @@
     <entry lang="zh-cn" key="HIDDEN_OS_CREATION_PREINFO_HELP">在下一步中，VeraCrypt 将会通过复制当前运行系统的内容到隐藏加密卷来创建隐形系统（被复制的数据将会使用与迷惑系统不同的密钥实时加密））。\n\n请注意该过程将会在启动验证环境中执行（在 Windows 启动前），并可能花费较长的时间；可能需要花费几个小时或者几天（依据系统分区容量和计算机性能而定，例如PM1.6GHz加密时大概的速度是0.5GB/分钟左右）。\n\n您可以中断该过程，关机，启动操作系统并在此之后继续该过程。然而，如果您中断该过程，整个复制系统的过程将会不得不从头开始（因为系统分区的内容在克隆期间必须不能被改变）。</entry>
     <entry lang="zh-cn" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">您想要取消整个隐形操作系统的创建过程吗？\n\n注意：如果现在取消，您将无法继续该进程。</entry>
     <entry lang="zh-cn" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">您要取消系统加密预测试吗？</entry>
-    <entry lang="zh-cn" key="BOOT_PRETEST_FAILED_RETRY">VeraCrypt 系统加密预测试失败。您希望再试一次吗？\n\n如果选择“否”，则启动验证组件将会被卸载。\n\n说明：如果 VeraCrypt 启动管理器在 Windows 启动前不要求您输入密码，这很可能是您的操作系统并没有从该系统所安装的驱动器引导的。目前并不支持这种方式。\n\n- 如果您使用了AES 之外的加密算法并且预测试失败了（并且您也输入了密码），这可能由有设计缺陷的驱动导致的。选择“否”，尝试再次加密系统分区/设备，但是要使用 AES 加密算法（该算法所需内存最低）。\n\n- 更多可能导致该错误的原因，请参考：https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="zh-cn" key="BOOT_PRETEST_FAILED_RETRY">VeraCrypt 系统加密预测试失败。您希望再试一次吗？\n\n如果选择“否”，则启动验证组件将会被卸载。\n\n说明：如果 VeraCrypt 启动管理器在 Windows 启动前不要求您输入密码，这很可能是您的操作系统并没有从该系统所安装的驱动器引导的。目前并不支持这种方式。\n\n- 如果您使用了AES 之外的加密算法并且预测试失败了（并且您也输入了密码），这可能由有设计缺陷的驱动导致的。选择“否”，尝试再次加密系统分区/设备，但是要使用 AES 加密算法（该算法所需内存最低）。\n\n- 更多可能导致该错误的原因，请参考：https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="zh-cn" key="SYS_DRIVE_NOT_ENCRYPTED">该系统分区/驱动器看起来没有被加密（或者是没有被完全加密）。</entry>
     <entry lang="zh-cn" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">您的系统分区/驱动器已加密（部分或完全加密）。\n\n请在继续进行前解密该系统分区/驱动器。操作步骤：在 VeraCrypt 主窗口的菜单中，选择“系统”-&gt;“永久解密系统分区/驱动器”。</entry>
     <entry lang="zh-cn" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">当系统分区/驱动器已部份或完全加密时，您不能降级 VeraCrypt 的版本（但是可以更新到新版本或者重新安装同一版本）。</entry>
@@ -1554,7 +1554,7 @@
     <entry lang="zh-cn" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">错误：驱动器使用的扇区大小不是512字节。\n\n由于平台上可用组件的限制，分区/设备托管卷不能在驱动器上创建/使用。\n\n可能的解决方案：\n- 在驱动器上创建以文件为宿主的卷(容器)。\n- 使用512字节扇区的驱动器。\n- 在其它平台上使用VeraCrypt。</entry>
     <entry lang="zh-cn" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">主机文件/设备已经被使用。</entry>
     <entry lang="zh-cn" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">卷位置不可用。</entry>
-    <entry lang="zh-cn" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt需要OSXFUSE 2.5或更高版本。</entry>
+    <entry lang="zh-cn" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt需要macFUSE 2.5或更高版本。</entry>
     <entry lang="zh-cn" key="EXCEPTION_OCCURRED">出现异常</entry>
     <entry lang="zh-cn" key="ENTER_PASSWORD">输入密码</entry>
     <entry lang="zh-cn" key="ENTER_TC_VOL_PASSWORD">输入 VeraCrypt 卷的密码</entry>
@@ -1645,6 +1645,50 @@
     <entry lang="zh-cn" key="MOUNTPOINT_BLOCKED">错误：卷挂载点被阻止，因为它覆盖了受保护的系统目录。\n\n请选择其他挂载点。</entry>
     <entry lang="zh-cn" key="MOUNTPOINT_NOTALLOWED">错误：卷挂载点不允许使用，因为它覆盖了 PATH 环境变量中的目录。\n\n请选择其他挂载点。</entry>
     <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="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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="zh-cn" key="MACOSX_APFS_SYNTHESIZED_DEVICE">所选设备 '{0}' 是 APFS 合成容器或卷，不能作为原始 VeraCrypt 卷的承载设备使用。\n\n请改选物理 APFS 存储分区{1}。</entry>
+    <entry lang="zh-cn" key="MACOSX_DEVICE_SYSTEM_PARTITION">所选设备 '{0}' 是 macOS 系统/支持分区，无法作为 VeraCrypt 卷主机使用。</entry>
+    <entry lang="zh-cn" key="MACOSX_APFS_SYSTEM_STORE">所选 APFS 物理存储 '{0}' 包含当前挂载的 macOS 系统卷，无法作为 VeraCrypt 卷主机使用。</entry>
+    <entry lang="zh-cn" key="MACOSX_DEVICE_NOT_WRITABLE">macOS 报告所选设备 '{0}' 为只读。请选择可写的物理分区或磁盘。</entry>
+    <entry lang="zh-cn" key="MACOSX_APFS_EROFS_HINT">macOS 报告所选设备为只读。如果这是 APFS 磁盘，请确保您选择的是物理 APFS 存储分区，而不是 APFS 合成卷。请使用“磁盘工具”或 'diskutil list' 来识别物理分区，然后重试。</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.20">
+  <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" />
@@ -181,7 +181,7 @@
     <entry lang="zh-hk" key="IDC_TRAVEL_OPEN_EXPLORER">掛載加密區之後用檔案總管開啟(&amp;E)</entry>
     <entry lang="zh-hk" key="IDC_TRAV_CACHE_PASSWORDS">在驅動程式的記憶體中快取密碼(&amp;C)</entry>
     <entry lang="zh-hk" key="IDC_TRUECRYPT_MODE">TrueCrypt 模式(&amp;T)</entry>
-    <entry lang="zh-hk" key="IDC_UNMOUNTALL">全部解除掛載(&amp;S)</entry>
+    <entry lang="zh-hk" key="IDC_UNMOUNTALL">全部解除掛載(&amp;U)</entry>
     <entry lang="zh-hk" key="IDC_VOLUME_PROPERTIES">加密區內容(&amp;V)...</entry>
     <entry lang="zh-hk" key="IDC_VOLUME_TOOLS">加密區工具(&amp;T)...</entry>
     <entry lang="zh-hk" key="IDC_WIPE_CACHE">清除密碼快取(&amp;W)</entry>
@@ -263,7 +263,7 @@
     <entry lang="zh-hk" key="IDM_VOLUME_EXPANDER">加密區擴展工具</entry>
     <entry lang="zh-hk" key="IDM_VOLUME_PROPERTIES">加密區內容</entry>
     <entry lang="zh-hk" key="IDM_VOLUME_WIZARD">加密區建立精靈</entry>
-    <entry lang="zh-hk" key="IDM_WEBSITE">官方網站</entry>
+    <entry lang="zh-hk" key="IDM_WEBSITE">VeraCrypt 網站</entry>
     <entry lang="zh-hk" key="IDM_WIPE_CACHE">清除快取的密碼</entry>
     <entry lang="zh-hk" key="IDOK">確定</entry>
     <entry lang="zh-hk" key="IDT_ACCELERATION_OPTIONS">硬件加速</entry>
@@ -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>
@@ -611,8 +611,8 @@
     <entry lang="zh-hk" key="IDD_PCDM_REMOVE_ALL_KEYFILES_FROM_VOL">從加密區中移除所有加密鑰檔案</entry>
     <entry lang="zh-hk" key="PASSWORD_CHANGED">密碼和/或加密鑰檔案已成功修改。\n\n重要：請確認你已經閱讀了用戶指南內 [Security Requirements and Precautions] 章節中 [Changing Passwords and Keyfiles] 的部分。</entry>
     <entry lang="zh-hk" key="FAVORITE_PIM_CHANGED">此磁碟區已登記成為喜愛的系統磁碟區及其 PIM 已經變更。\n你是否需要 VeraCrypt 自動更新喜愛的系統磁碟區設定 (必須系統管理員權限)?\n\n請注意如你的回應為否，你將需要手動更新喜愛的系統磁碟區。</entry>
-    <entry lang="zh-hk" key="SYS_PASSWORD_CHANGED_ASK_RESCUE_DISK">重要：如果你不銷毀 VeraCrypt 救機光碟，你的系統分割區或磁碟機仍然可以通過使用舊密碼解密(通過 VeraCrypt 救機光碟來開機和輸入舊密碼)。你應該建立一個新的 VeraCrypt 救機光碟，之後銷毀原先的救機光碟。\n\n你希望建立一個新的 VeraCrypt 救機光碟嗎？</entry>
-    <entry lang="zh-hk" key="SYS_HKD_ALGO_CHANGED_ASK_RESCUE_DISK">請注意，VeraCrypt 救機光碟仍然使用著早期的加密演算法。如果你覺的先前的加密演算法不安全，你應該建立一個新的 VeraCrypt 救機光碟，之後銷毀原先的救機光碟。\n\n你希望建立一個新的 VeraCrypt 救機光碟嗎？</entry>
+    <entry lang="zh-hk" key="SYS_PASSWORD_CHANGED_ASK_RESCUE_DISK">重要：如果你不銷毀 VeraCrypt 救機碟，你的系統分割區或磁碟機仍然可以通過使用舊密碼解密(通過 VeraCrypt 救機碟來開機和輸入舊密碼)。你應該建立一個新的 VeraCrypt 救機碟，之後銷毀原先的救機碟。\n\n你希望建立一個新的 VeraCrypt 救機碟嗎？</entry>
+    <entry lang="zh-hk" key="SYS_HKD_ALGO_CHANGED_ASK_RESCUE_DISK">請注意，VeraCrypt 救機碟仍然使用著早期的加密演算法。如果你覺的先前的加密演算法不安全，你應該建立一個新的 VeraCrypt 救機碟，之後銷毀原先的救機碟。\n\n你希望建立一個新的 VeraCrypt 救機碟嗎？</entry>
     <entry lang="zh-hk" key="KEYFILES_NOTE">任何類型的檔案 (例如, .mp3, .jpg, .zip, .avi) 都可以用作 VeraCrypt 加密鑰檔案。注意 VeraCrypt 絕不會修改加密鑰檔案的內容。你可選擇多於一個加密鑰檔案(次序並不重要)。如果你新增一個資料夾，所有內含的非隱藏檔案都會用作加密鑰檔案。選擇 [加入令牌檔案] 以選取儲存在安全性權杖或智能卡 (或者匯入加密鑰檔案到安全性權杖或智能卡)。</entry>
     <entry lang="zh-hk" key="KEYFILE_CHANGED">加密鑰檔案已成功新增/移除。</entry>
     <entry lang="zh-hk" key="KEYFILE_EXPORTED">已匯出加密鑰檔案。</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>
@@ -855,7 +855,7 @@
     <entry lang="zh-hk" key="TC_INSTALLER_IS_RUNNING">VeraCrypt 安裝程式正在執行 VeraCrypt 的安裝或更新。在你繼續進行前，請等待其完成或者關閉它。如果你無法關閉它，請在繼續之前重新啟動電腦。</entry>
     <entry lang="zh-hk" key="INSTALL_FAILED">安裝失敗。</entry>
     <entry lang="zh-hk" key="UNINSTALL_FAILED">解除安裝失敗。</entry>
-    <entry lang="zh-hk" key="DIST_PACKAGE_CORRUPTED">這個安裝程式已經損壞。請嘗試重新下載安裝程式(建議從 VeraCrypt 官方網站 https://www.veracrypt.fr 下載)。</entry>
+    <entry lang="zh-hk" key="DIST_PACKAGE_CORRUPTED">這個安裝程式已經損壞。請嘗試重新下載安裝程式(建議從 VeraCrypt 官方網站 https://veracrypt.jp 下載)。</entry>
     <entry lang="zh-hk" key="CANNOT_WRITE_FILE_X">無法寫入檔案 %s</entry>
     <entry lang="zh-hk" key="EXTRACTING_VERB">正在解壓縮</entry>
     <entry lang="zh-hk" key="CANNOT_READ_FROM_PACKAGE">無法從安裝包中讀取資料</entry>
@@ -960,15 +960,15 @@
     <entry lang="zh-hk" key="VOLUME_HAS_NO_BACKUP_HEADER">加密區中沒有內嵌的備份標頭數據(注意，僅在 TrueCrypt 6.0 和以後的版本才包含內嵌的標頭數據)。</entry>
     <entry lang="zh-hk" key="BACKUP_HEADER_NOT_FOR_SYS_DEVICE">你正在嘗試備份系統分割區/裝置的標頭數據，該功能不被允許。對於系統分割區/裝置標頭數據的備份/還原 只能通過使用 VeraCrypt 救機光碟來進行。\n\n你希望建立 VeraCrypt 救機光碟嗎？</entry>
     <entry lang="zh-hk" key="RESTORE_HEADER_NOT_FOR_SYS_DEVICE">你正在嘗試還原系統分割區/裝置的標頭數據，但是你選擇的是系統分割區/裝置。該功能不被允許。 對於系統分割區/裝置標頭數據的備份/還原 只能通過使用 VeraCrypt 救機光碟來進行。\n\n你希望建立 VeraCrypt 救機光碟嗎？</entry>
-    <entry lang="zh-hk" key="RESCUE_DISK_NON_WIZARD_CREATION_SELECT_PATH">在按 [確定] 後，你將會設定新的 VeraCrypt 救機光碟  鏡像檔的名稱和存放位置。</entry>
+    <entry lang="zh-hk" key="RESCUE_DISK_NON_WIZARD_CREATION_SELECT_PATH">在按 [確定] 後，你將會設定新的 VeraCrypt 救機光碟鏡像檔的名稱和存放位置。</entry>
     <entry lang="zh-hk" key="RESCUE_DISK_NON_WIZARD_CREATION_BURN">救機光碟 ISO 映像檔已經建立並儲存成檔案： %s\n\n現在你需要將救機光碟燒錄到 CD 或 DVD。\n\n重要：檔案必須以 ISO 映像檔方式燒錄到 CD/DVD(不要燒錄成單個的資料檔案)。要獲取更多的關於如何燒錄 ISO 檔的資訊，請參考你的 CD/DVD 燒錄軟件的說明書。\n\n請你在燒錄救機光碟之後，選擇 [系統] &gt;[驗證救機光碟]來驗證救機光碟是否已經成功燒錄。</entry>
-    <entry lang="zh-hk" key="RESCUE_DISK_NON_WIZARD_CREATION_WIN_ISOBURN">救機光碟  ISO 鏡像檔已經建立並儲存成檔案： %s\n\n現在你需要把救機光碟燒錄到 CD 或 DVD。\n\n你想要啟動 Windows 自帶的磁片鏡像燒錄功能嗎？\n\n注意，請你在燒錄救機光碟之後，選擇 [系統] &gt;[驗證救機光碟]來驗證救機光碟是否已經成功燒錄。</entry>
+    <entry lang="zh-hk" key="RESCUE_DISK_NON_WIZARD_CREATION_WIN_ISOBURN">救機光碟 ISO 鏡像檔已經建立並儲存成檔案： %s\n\n現在你需要把救機光碟燒錄到 CD 或 DVD。\n\n你想要啟動 Windows 自帶的磁片鏡像燒錄功能嗎？\n\n注意，請你在燒錄救機光碟之後，選擇 [系統] &gt;[驗證救機光碟]來驗證救機光碟是否已經成功燒錄。</entry>
     <entry lang="zh-hk" key="RESCUE_DISK_NON_WIZARD_CHECK_INSERT">請插入 VeraCrypt 救機光碟到 CD/DVD 光碟機並點 [確定] 按鈕開始驗證。</entry>
     <entry lang="zh-hk" key="RESCUE_DISK_NON_WIZARD_CHECK_PASSED">VeraCrypt 救機光碟已經被成功驗證。</entry>
     <entry lang="zh-hk" key="RESCUE_DISK_NON_WIZARD_CHECK_FAILED">救機光碟驗證失敗。\n\n如果你已經燒錄了救機光碟，請彈出後重新插入救機光碟到 CD/DVD，之後再試一次。如果仍然無效，請嘗試使用其他 CD/DVD 燒錄軟件或燒錄盤。\n\n如果你嘗試驗證一個為不同的主密鑰、密碼、元素等建立的 VeraCrypt 救機光碟，請注意這樣的救機光碟會無法通過驗證。要建立一個新的和當前配置完全相容的救機光碟，請選擇 [系統] &gt; [建立救機光碟]。</entry>
     <entry lang="zh-hk" key="RESCUE_DISK_ISO_IMAGE_CHECK_PASSED">已成功驗證 VeraCrypt 救機光碟映像檔</entry>
-    <entry lang="zh-hk" key="RESCUE_DISK_ISO_IMAGE_CHECK_FAILED">救機碟映像檔驗證失敗。\n\n如你嘗試驗證一個以不同主密鑰、密碼、salt 之類來建立的 VeraCrypt 救機碟映像檔，請注意這樣的救機碟映像檔將總是無法通過此驗證。要建立可完全與現時設定相容的新救機碟映像檔，請選取 [系統] &gt; [建立救機碟]。</entry>
-    <entry lang="zh-hk" key="ERROR_CREATING_RESCUE_DISK">建立 VeraCrypt 救機光碟時失敗。</entry>
+    <entry lang="zh-hk" key="RESCUE_DISK_ISO_IMAGE_CHECK_FAILED">救機光碟映像檔驗證失敗。\n\n如你嘗試驗證一個以不同主密鑰、密碼、salt 之類來建立的 VeraCrypt 救機碟映像檔，請注意這樣的救機碟映像檔將總是無法通過此驗證。要建立可完全與現時設定相容的新救機碟映像檔，請選取 [系統] &gt; [建立救機碟]。</entry>
+    <entry lang="zh-hk" key="ERROR_CREATING_RESCUE_DISK">建立 VeraCrypt 救機碟時失敗。</entry>
     <entry lang="zh-hk" key="CANNOT_CREATE_RESCUE_DISK_ON_HIDDEN_OS">VeraCrypt 救機光碟在隱形作業系統運行時無法建立。\n\n要建立 VeraCrypt 救機光碟，請啟動到偽裝作業系統之後選擇 [系統] &gt; [建立救機光碟]。</entry>
     <entry lang="zh-hk" key="RESCUE_DISK_CHECK_FAILED">不能確定救機光碟是否燒錄成功。\n\n如果你已經燒錄了救機光碟，請彈出後重新插入救機光碟到 CD/DVD，之後再嘗試驗證一次。如果仍然無效，請嘗試使用其他 %s 。\n\n如果你還沒有建立救機光碟，請首先建立一個，然後再點 [下一步] 按鈕。\n\n如果你嘗試驗證一個運行加密盤建立精靈以前建立的救機光碟，則這樣的救機光碟是無法用於當前系統的，這是因為它是使用了不同的主密鑰建立的。你需要燒錄和建立一個新的救機光碟。</entry>
     <entry lang="zh-hk" key="RESCUE_DISK_CHECK_FAILED_SENTENCE_APPENDIX"> 和/或 其他 CD/DVD 燒錄軟件</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="zh-hk" key="HIDDEN_OS_CREATION_PREINFO_HELP">在下一步，VeraCrypt 將會透過複製系統分割區的內容到隱藏加密區來建立隱形系統(被複製的資料將會使用與偽裝作業系統不同的加密鑰即時加密)。\n\n請注意該過程將會在啟動作業系統前的環境下進行(在 Windows 啟動前)，並可能花費較長的時間；可能需要花費幾個小時或者幾天(依據系統分割區容量和電腦性能而定，例如PM1.6GHz加密時大概的速度是0.5GB/分鐘左右)。\n\n你可以中斷該過程，關機，啟動作業系統並在此之後繼續該過程。然而，如果你中斷該過程，整個複製系統的過程將會不得不從頭開始(因為系統分割區的內容在克隆期間必須不能被改變)。</entry>
     <entry lang="zh-hk" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">你想要取消整個隱形作業系統的建立過程嗎？\n\n請注意：如果現在取消，你將無法繼續該過程。</entry>
     <entry lang="zh-hk" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">你要取消系統加密的前置測試嗎？</entry>
-    <entry lang="zh-hk" key="BOOT_PRETEST_FAILED_RETRY">VeraCrypt 系統加密前置測試失敗。你希望再試一次嗎？\n\n如果你選擇 [否]，則啟動驗證元件將會被解除掛載。\n\n說明：如果 VeraCrypt 開機管理程式在 Windows 啟動前不要求你輸入密碼，這很可能是你的作業系統並沒有從該系統所安裝的磁碟機引導的。目前並不支援這種方式。\n\n- 如果你使用了AES 之外的加密演算法並且前置測試失敗了(並且你也輸入了密碼)，這可能由有設計缺陷的驅動導致的。選擇 [否]，嘗試再次加密系統分割區/裝置，但是要使用 AES 加密演算法(該演算法所需記憶體最低)。\n\n- 更多可能導致該錯誤的原因，請參考: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="zh-hk" key="BOOT_PRETEST_FAILED_RETRY">VeraCrypt 系統加密前置測試失敗。你希望再試一次嗎？\n\n如果你選擇 [否]，則啟動驗證元件將會被解除掛載。\n\n說明：如果 VeraCrypt 開機管理程式在 Windows 啟動前不要求你輸入密碼，這很可能是你的作業系統並沒有從該系統所安裝的磁碟機引導的。目前並不支援這種方式。\n\n- 如果你使用了AES 之外的加密演算法並且前置測試失敗了(並且你也輸入了密碼)，這可能由有設計缺陷的驅動導致的。選擇 [否]，嘗試再次加密系統分割區/裝置，但是要使用 AES 加密演算法(該演算法所需記憶體最低)。\n\n- 更多可能導致該錯誤的原因，請參考: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="zh-hk" key="SYS_DRIVE_NOT_ENCRYPTED">該系統分割區或磁碟機似乎沒有被加密(或者是沒有被完全加密)。</entry>
     <entry lang="zh-hk" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">你的系統分割區或磁碟機已加密(部分或完全加密)。\n\n請在繼續進行前解密這個系統分割區或磁碟機。操作步驟：在 VeraCrypt 主視窗的功能表中，選擇 [系統] &gt;[永久解密系統分割區或磁碟機]。</entry>
     <entry lang="zh-hk" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">當系統分割區或磁碟機已被部份或完全加密時，你不能降級 VeraCrypt 的版本(但是可以更新到新版本或者從新安裝同一版本)。</entry>
@@ -1300,13 +1300,13 @@
     <entry lang="zh-hk" key="MOUNTED_CONTAINER_FORCED_READ_ONLY">由於寫入許可權被拒絕，加密區 [%s] 只能以唯讀模式掛載。\n\n請確認加密容器檔案的存取權允許你對其執行寫入操作(右按此容器並選擇 屬性 &gt; 安全性)。\n\n注意，由於 Windows 的原因，你可能在設定成合適的安全屬性後還會看到這個警告，這並非是 VeraCrypt 的程式故障。其中一個解決方法是移動你的加密容器檔案，例如移動到另一個資料資料夾。\n\n如果你確實要保持加密區的唯讀模式，請設定加密區的屬性為唯讀(右鍵單擊加密盤檔並選擇屬性 &gt; 唯讀)，這樣就可以禁止顯示警告了。</entry>
     <entry lang="zh-hk" key="MOUNTED_DEVICE_FORCED_READ_ONLY">由於寫入許可權被拒絕，加密區 [%s] 不得不以唯讀模式掛載。\n\n請確認沒有其他程式(例如，防病毒程式)正在存取加密區所在的分割區/裝置。</entry>
     <entry lang="zh-hk" key="MOUNTED_DEVICE_FORCED_READ_ONLY_WRITE_PROTECTION">加密區 [%s] 已使用唯讀模式掛載，這是因為作業系統報告主裝置為防寫狀態。\n\n請注意，在一些第三方的晶片驅動中，已有錯誤報告指出可能會造成可寫入介質錯誤的被系統報告為防寫。這個問題並不是由 VeraCrypt 造成。這可以通過更新或解除掛載當前系統中的任何第三方晶片組驅動(非微軟認證)。</entry>
-    <entry lang="zh-hk" key="LIMIT_ENC_THREAD_POOL_NOTE">請注意，超執行緒技術讓每個實體核心可提供多個邏輯核心。當超啟用執行緒技術時，以上選擇的數目代表邏輯處理器/核心的數目。</entry>
-    <entry lang="zh-hk" key="NUMBER_OF_THREADS">%d 線程</entry>
-    <entry lang="zh-hk" key="DISABLED_HW_AES_AFFECTS_PERFORMANCE">請注意，硬體加速 AES 已被禁用，這將會影響測試結果(效能更差)。\n\n要啟用硬體加速，請選擇 [設定] &gt; [性能] 並禁用相應選項。</entry>
-    <entry lang="zh-hk" key="LIMITED_THREAD_COUNT_AFFECTS_PERFORMANCE">請注意，線程的數目當前受限，這將會影響測試結果(效能更差)。\n\n要充份發揮中央處理器的潛能，請選擇 [設定] &gt; [性能]並禁用相關選項。</entry>
+    <entry lang="zh-hk" key="LIMIT_ENC_THREAD_POOL_NOTE">請注意，超執行緒技術讓每個實體核心可提供多個邏輯核心。當啟用超執行緒技術時，以上選擇的數目代表邏輯處理器/核心的數目。</entry>
+    <entry lang="zh-hk" key="NUMBER_OF_THREADS">%d 執行緒</entry>
+    <entry lang="zh-hk" key="DISABLED_HW_AES_AFFECTS_PERFORMANCE">請注意硬體加速 AES 已被禁用，這將會影響測試結果 (效能更差)。\n\n要啟用硬體加速，請選擇 [設定] &gt; [性能] 並禁用相應選項。</entry>
+    <entry lang="zh-hk" key="LIMITED_THREAD_COUNT_AFFECTS_PERFORMANCE">請注意現時執行緒的數目受限制，這將會影響測試結果 (效能更差)。\n\n要充份發揮中央處理器的潛能，請選擇 [設定] &gt; [性能] 並停用相關選項。</entry>
     <entry lang="zh-hk" key="ASK_REMOVE_DEVICE_WRITE_PROTECTION">你想要 VeraCrypt 嘗試停用此分割區/裝置的防寫保護嗎？</entry>
     <entry lang="zh-hk" key="CONFIRM_SETTING_DEGRADES_PERFORMANCE">警告：此設定可能會降低效能。\n\n你確認要使用該設定嗎？</entry>
-    <entry lang="zh-hk" key="HOST_DEVICE_REMOVAL_UNMOUNT_WARN_TITLE">警告： VeraCrypt 加密區已經自動卸掛載</entry>
+    <entry lang="zh-hk" key="HOST_DEVICE_REMOVAL_UNMOUNT_WARN_TITLE">警告： VeraCrypt 加密區已被自動解除掛載</entry>
     <entry lang="zh-hk" key="HOST_DEVICE_REMOVAL_UNMOUNT_WARN">已掛載加密區的裝置在實體移除或關閉電源前，應該習慣先將加密區解除掛載。\n\n不預期地自行解除掛載通常由於電線、磁碟機 (外置盒)之類出現間歇性故障所致。</entry>
     <entry lang="zh-hk" key="UNSUPPORTED_TRUECRYPT_FORMAT">這個加密區使用 TrueCrypt %x.%x 建立，但 VeraCrypt 只支援使用 TrueCrypt 6.x/7.x 系列所建立的加密區</entry>
     <entry lang="zh-hk" key="TEST">測試</entry>
@@ -1394,7 +1394,7 @@
     <entry lang="zh-hk" key="IDC_DISABLE_BOOT_LOADER_PIM_PROMPT">不要在啟動前驗證畫面詢問 PIM 數值（PIM 數值會不加密地記錄在磁碟上）</entry>
     <entry lang="zh-hk" key="DISABLE_BOOT_LOADER_PIM_PROMPT">警告：請留意如果你啟用這個選項，PIM 數值會將會不加密地記錄在磁碟上。\n\n你是否確認要啟用這個選項？</entry>
     <entry lang="zh-hk" key="PIM_TOO_BIG">自訂迭代倍數 (PIM) 最大數值為 2147468.</entry>
-    <entry lang="zh-hk" key="IDC_SKIP_RESCUE_VERIFICATION">跳過救機光碟驗證</entry>
+    <entry lang="zh-hk" key="IDC_SKIP_RESCUE_VERIFICATION">跳過救機碟驗證</entry>
     <entry lang="zh-hk" key="IDC_HIDE_WAITING_DIALOG">在進行操作時不要顯示等候訊息畫面</entry>
     <entry lang="zh-hk" key="IDC_DISABLE_BOOT_LOADER_HASH_PROMPT">在啟動前驗證畫面時不要詢問雜湊演算法</entry>
     <entry lang="zh-hk" key="KUZNYECHIK_HELP">Kuznyechik 為區塊加密法，最初發佈於 2015 年並被定義為俄羅斯聯邦的 GOST R 34.12-2015 和 RFC 7801 的國家標準。 256-bit 加密鑰，128-bit 區塊大小。運作模式為 XTS。</entry>
@@ -1418,7 +1418,7 @@
     <entry lang="zh-hk" key="EDIT_DCSPROP_FOR_ADVANCED_ONLY">警告：沒有經驗的使用者不應嘗試自行修改開機載入程式設定。\n\n還要繼續嗎？</entry>
     <entry lang="zh-hk" key="DCSPROP_XML_VALIDATION_FAILED">警告：無法驗證開機程式設定檔的 XML 格式。請檢查你所作出的修改。</entry>
     <entry lang="zh-hk" key="IDT_ADVANCED_OPTIONS">進階選項</entry>
-    <entry lang="zh-hk" key="AFTER_UPGRADE_RESCUE_DISK">強烈建議你透過選取 [系統] &gt; [建立救機光碟] 來建立新的 VeraCrypt 救機光碟(這將會內含新版本的 VeraCrypt 開機程式)。\n你想現在做嗎？</entry>
+    <entry lang="zh-hk" key="AFTER_UPGRADE_RESCUE_DISK">強烈建議你透過選取 [系統] &gt; [建立救機碟] 來建立新的 VeraCrypt 救機碟(這將會內含新版本的 VeraCrypt 開機程式)。\n你想現在做嗎？</entry>
     <entry lang="zh-hk" key="IDC_ALLOW_TRIM_NONSYS_SSD">非系統的 SSD 分割區/磁碟可執行 TRIM 指令</entry>
     <entry lang="zh-hk" key="IDC_BLOCK_SYSENC_TRIM">在系統分割區或磁碟機阻截 TRIM 指令</entry>
     <entry lang="zh-hk" key="WINDOWS_EFI_BOOT_LOADER_MISSING">錯誤：無法在磁碟機上找到 Windows EFI 系統載入程式。操作將會停止。</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="zh-hk" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">錯誤：這個磁碟機使用的磁區大小並非 512 位元組。\n\n由於當前平台可用的元件所限，寄存在分割區或裝置上的加密區無法在磁碟機上建立或使用。\n\n可行的解決方案：\n- 在磁碟機上建立一個寄存在檔案的加密區(容器)。\n- 使用磁區大小為 512 位元組的磁碟機\n- 在另一個平台上使用 VeraCrypt。</entry>
     <entry lang="zh-hk" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">主機的檔案或裝置正在使用中。</entry>
     <entry lang="zh-hk" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">加密區的位置不可用。</entry>
-    <entry lang="zh-hk" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt 需要 OSXFUSE 2.5 或更新版本。</entry>
+    <entry lang="zh-hk" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt 需要 macFUSE 2.5 或更新版本。</entry>
     <entry lang="zh-hk" key="EXCEPTION_OCCURRED">已發生異常情況</entry>
     <entry lang="zh-hk" key="ENTER_PASSWORD">輸入密碼</entry>
     <entry lang="zh-hk" key="ENTER_TC_VOL_PASSWORD">輸入 VeraCrypt 加密區密碼</entry>
@@ -1644,6 +1644,50 @@
     <entry lang="zh-hk" key="MOUNTPOINT_BLOCKED">錯誤：磁碟區掛載點因其覆寫系統受保護的路徑而被阻止。\n\n請選擇另一個掛載點。</entry>
     <entry lang="zh-hk" key="MOUNTPOINT_NOTALLOWED">錯誤： 磁碟區掛載點因其覆寫的路徑屬於 PATH 環境變數的一部份而不被接納。\n\n請選擇另一個掛載點。</entry>
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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.20">
+  <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>
@@ -855,7 +855,7 @@
     <entry lang="en" key="TC_INSTALLER_IS_RUNNING">VeraCrypt Installer is currently running on this system and performing or preparing installation or update of VeraCrypt. Before you proceed, please wait for it to finish or close it. If you cannot close it, please restart your computer before proceeding.</entry>
     <entry lang="zh-tw" key="INSTALL_FAILED">安裝失敗。</entry>
     <entry lang="zh-tw" key="UNINSTALL_FAILED">移除失敗。</entry>
-    <entry lang="zh-tw" key="DIST_PACKAGE_CORRUPTED">這發行包裝檔已經損壞。請試著再下載一次(最好從 VeraCrypt 官方網站 https://www.veracrypt.fr 下載)。</entry>
+    <entry lang="zh-tw" key="DIST_PACKAGE_CORRUPTED">這發行包裝檔已經損壞。請試著再下載一次(最好從 VeraCrypt 官方網站 https://veracrypt.jp 下載)。</entry>
     <entry lang="zh-tw" key="CANNOT_WRITE_FILE_X">不能寫入檔案 %s</entry>
     <entry lang="zh-tw" key="EXTRACTING_VERB">正在解壓縮</entry>
     <entry lang="zh-tw" key="CANNOT_READ_FROM_PACKAGE">不能從包裝檔中讀取資料</entry>
@@ -1229,7 +1229,7 @@
     <entry lang="en" key="HIDDEN_OS_CREATION_PREINFO_HELP">In the next steps, VeraCrypt will create the hidden operating system by copying the content of the system partition to the hidden volume (data being copied will be encrypted on the fly with an encryption key different from the one that will be used for the decoy operating system).\n\nPlease note that the process will be performed in the pre-boot environment (before Windows starts) and it may take a long time to complete; several hours or even several days (depending on the size of the system partition and on the performance of your computer).\n\nYou will be able to interrupt the process, shut down your computer, start the operating system and then resume the process. However, if you interrupt it, the entire process of copying the system will have to start from the beginning (because the content of the system partition must not change during cloning).</entry>
     <entry lang="en" key="CONFIRM_CANCEL_HIDDEN_OS_CREATION">Do you want to cancel the entire process of creation of the hidden operating system?\n\nNote: You will NOT be able to resume the process if you cancel it now.</entry>
     <entry lang="zh-tw" key="CONFIRM_CANCEL_SYS_ENC_PRETEST">您要取消系統加密預先測試嗎？</entry>
-    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://www.veracrypt.fr/en/Troubleshooting.html</entry>
+    <entry lang="en" key="BOOT_PRETEST_FAILED_RETRY">The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://veracrypt.jp/en/Troubleshooting.html</entry>
     <entry lang="zh-tw" key="SYS_DRIVE_NOT_ENCRYPTED">系統分割區/磁碟機看起來並未加密(即沒有部分也沒有完全加密)。</entry>
     <entry lang="zh-tw" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED">您的系統分割區/磁碟機已加密(部分或完全加密)。\n\n請在繼續進行之前解密這個系統分割區/磁碟機。要這樣做，在 VeraCrypt 主視窗的選單中，選擇 "系統" &gt; "永久解密系統分割區/磁碟機"。</entry>
     <entry lang="en" key="SETUP_FAILED_BOOT_DRIVE_ENCRYPTED_DOWNGRADE">When the system partition/drive is encrypted (partially or fully), you cannot downgrade VeraCrypt (but you can upgrade it or reinstall the same version).</entry>
@@ -1553,7 +1553,7 @@
     <entry lang="en" key="LINUX_EX2MSG_UNSUPPORTEDSECTORSIZE">Error: The drive uses a sector size other than 512 bytes.\n\nDue to limitations of components available on your platform, partition/device-hosted volumes cannot be created/used on the drive.\n\nPossible solutions:\n- Create a file-hosted volume (container) on the drive.\n- Use a drive with 512-byte sectors.\n- Use VeraCrypt on another platform.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMEHOSTINUSE">The host file/device is already in use.</entry>
     <entry lang="en" key="LINUX_EX2MSG_VOLUMESLOTUNAVAILABLE">Volume slot unavailable.</entry>
-    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires OSXFUSE 2.5 or above.</entry>
+    <entry lang="en" key="LINUX_EX2MSG_HIGHERFUSEVERSIONREQUIRED">VeraCrypt requires macFUSE 2.5 or above.</entry>
     <entry lang="en" key="EXCEPTION_OCCURRED">Exception occurred</entry>
     <entry lang="en" key="ENTER_PASSWORD">Enter password</entry>
     <entry lang="en" key="ENTER_TC_VOL_PASSWORD">Enter VeraCrypt Volume Password</entry>
@@ -1644,6 +1644,50 @@
     <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_KERNEL_DRIVER">Mount NTFS volumes with an in-kernel Linux driver</entry>
+    <entry lang="en" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux only. When enabled and no explicit filesystem type was supplied, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with an available in-kernel NTFS driver, bypassing mount helpers such as ntfs-3g. VeraCrypt uses ntfs when it is positively identified as a modern read/write driver or expected on Linux 7.1 or later, and otherwise uses ntfs3. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If no supported in-kernel NTFS driver is available or loadable, mounting fails. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems.</entry>
+    <entry lang="en" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No supported in-kernel NTFS driver is available or loadable. To use the system default NTFS backend, disable the NTFS kernel-driver preference or do not request kernel NTFS explicitly.</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

@@ -1,278 +1,444 @@
 <#
 .SYNOPSIS
-This PowerShell script is used to create a VeraCrypt container with minimal size to hold a copy of the given input file or directory.
+    Create a VeraCrypt container just large enough for the supplied file or
+    directory and copy the data into it.
 
 .DESCRIPTION
-This script takes as input a file path or directory path and a container path.
-If the container path is not specified, it defaults to the same as the input path with a ".hc" extension.
-The script calculates the minimal size needed to hold the input file or directory in a VeraCrypt container.
-It then creates a VeraCrypt container with the specified path and the calculated size using exFAT filesystem.
-Finally, the container is mounted, the input file or directory is copied to the container and the container is dismounted.
+    • 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 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.
+    • Enhanced parameterization for safety margins and VeraCrypt overhead.
 
-.PARAMETER inputPath
-The file path or directory path to be encrypted in the VeraCrypt container.
-
-.PARAMETER containerPath
-The desired path for the VeraCrypt container. If not specified, it defaults to the same as the input path with a ".hc" extension.
+.PARAMETER InputPath        File or directory to store in the container.
+.PARAMETER ContainerPath    Dest *.hc* file. Default: InputPath + '.hc'.
+.PARAMETER ClusterSizeKB    4–512 KiB or 'Auto' (default 32).
+.PARAMETER VeraCryptDir     Optional folder containing VeraCrypt *.exe* files.
+.PARAMETER EncryptionAlg    Any algorithm VeraCrypt accepts (default AES).
+.PARAMETER HashAlg          VeraCrypt hash (default SHA512).
+.PARAMETER SafetyPercent    Safety margin as percentage of calculated size (default 1.0 for small, 0.1 for large).
+.PARAMETER VCOverheadMiB    VeraCrypt overhead in MiB (default varies by size).
+.PARAMETER Force            If specified, allows overwriting the output container if it already exists.
+.PARAMETER Password         Optional SecureString password for automation (prompts if not provided).
 
 .EXAMPLE
-.\EncryptData.ps1 -inputPath "C:\MyFolder" -containerPath "D:\MyContainer.hc"
-.\EncryptData.ps1 "C:\MyFolder" "D:\MyContainer.hc"
-.\EncryptData.ps1 "C:\MyFolder"
-
+    .\EncryptData.ps1 -InputPath C:\Data -ContainerPath C:\EncryptedData.hc -ClusterSizeKB Auto
 .NOTES
-Author: Mounir IDRASSI
-Email: mounir.idrassi@idrix.fr
-Date: 26 July 2024
-License: This script is licensed under the Apache License 2.0
+    Author: Mounir IDRASSI
+    Email: mounir.idrassi@amcrypto.jp
+    Date: 30 April 2025
+    License: This script is licensed under the Apache License 2.0
 #>
 
-# parameters
+[CmdletBinding(SupportsShouldProcess)]
 param(
-    [Parameter(Mandatory=$true)]
-    [string]$inputPath,
-    [string]$containerPath
+    [Parameter(Mandatory)][string]$InputPath,
+    [string]$ContainerPath,
+    [ValidateSet('Auto','4','8','16','32','64','128','256','512')]
+    [string]$ClusterSizeKB = '32',
+    [string]$VeraCryptDir,
+    [string]$EncryptionAlg = 'AES',
+    [string]$HashAlg = 'SHA512',
+    # 0 ⇒ use built-in logic; otherwise 0–100 %  
+    [ValidateRange(0.0,100.0)]  
+    [double]$SafetyPercent = 0,  
+    # 0 ⇒ auto. 1-8192 MiB accepted.  
+    [ValidateRange(0,8192)]  
+    [int]$VCOverheadMiB    = 0,
+    [Parameter(ValueFromPipeline = $true)][System.Security.SecureString]$Password,
+    [switch]$Force
 )
-function ConvertTo-AbsolutePath {
-    param (
-        [Parameter(Mandatory=$true)]
-        [string]$Path
-    )
 
+Set-StrictMode -Version Latest
+$ErrorActionPreference = 'Stop'
+
+function Get-AbsolutePath([string]$Path) {
     if ([System.IO.Path]::IsPathRooted($Path)) {
-        return $Path
+        return [System.IO.Path]::GetFullPath($Path)
+    } else {
+        $combined = Join-Path -Path (Get-Location) -ChildPath $Path
+        return [System.IO.Path]::GetFullPath($combined)
     }
-    
-    return Join-Path -Path (Get-Location) -ChildPath $Path
 }
 
-# Convert input path to fully qualified path
-$inputPath = ConvertTo-AbsolutePath -Path $inputPath
-
-# Check if input path exists
-if (-not (Test-Path $inputPath)) {
-    Write-Host "The specified input path does not exist. Please provide a valid input path."
-    exit 1
+# Helper creates a temp file, registers it for secure deletion in finally  
+function New-VcErrFile {  
+    $tmp = [System.IO.Path]::GetTempFileName()  
+    # Pre-allocate 0-byte file; caller overwrites  
+    return $tmp  
 }
 
-$inputPath = (Resolve-Path -Path $inputPath).Path
+# Constants for exFAT sizing
+$EXFAT_MIN_CLUSTERS = 2
+$EXFAT_PRACTICAL_MIN_CLUSTERS = 65533
+$INITIAL_VBR_SIZE = 32KB
+$BACKUP_VBR_SIZE = 32KB
+$RAW_UPCASE_BYTES = 128KB
 
-# Set container path if not specified
-if ([string]::IsNullOrWhiteSpace($containerPath)) {
-    $containerPath = "${inputPath}.hc"
+#----------------------- Locate VeraCrypt executables --------------------------
+if (-not $VeraCryptDir) {
+    $candidates = @(Join-Path $env:ProgramFiles 'VeraCrypt')
+    $VeraCryptDir = $candidates |
+        Where-Object { Test-Path (Join-Path $_ 'VeraCrypt.exe') } |
+        Select-Object -First 1
+    if (-not $VeraCryptDir) {
+        $cmd = Get-Command 'VeraCrypt.exe' -ErrorAction SilentlyContinue
+        if ($cmd) { $VeraCryptDir = Split-Path $cmd.Path }
+    }
+    if (-not $VeraCryptDir) { throw 'VeraCrypt executables not found – specify -VeraCryptDir.' }
+}
+
+$VeraCryptExe = Join-Path $VeraCryptDir 'VeraCrypt.exe'
+$VeraCryptFormatExe = Join-Path $VeraCryptDir 'VeraCrypt Format.exe'
+if (-not (Test-Path $VeraCryptExe) -or -not (Test-Path $VeraCryptFormatExe)) {
+    throw 'VeraCrypt executables missing.'
+}
+
+#--------------------------- Input / Output Paths ------------------------------
+$InputPath = Get-AbsolutePath $InputPath
+if (-not (Test-Path $InputPath)) { throw "InputPath '$InputPath' does not exist." }
+
+if (-not $ContainerPath) {
+    $ContainerPath = ($InputPath.TrimEnd('\') + '.hc')
 } else {
-    $containerPath = ConvertTo-AbsolutePath -Path $containerPath
+    $ContainerPath = Get-AbsolutePath $ContainerPath
 }
-
-# Check if container path already exists
-if (Test-Path $containerPath) {
-    Write-Host "The specified container path already exists. Please provide a unique path for the new container."
-    exit 1
-}
-
-# Full path to VeraCrypt executables
-$veracryptPath = "C:\Program Files\VeraCrypt"  # replace with your actual path
-$veraCryptExe = Join-Path $veracryptPath "VeraCrypt.exe"
-$veraCryptFormatExe = Join-Path $veracryptPath "VeraCrypt Format.exe"
-
-# Constants used to calculate the size of the exFAT filesystem
-$InitialVBRSize = 32KB
-$BackupVBRSize = 32KB
-$InitialFATSize = 128KB
-$ClusterSize = 32KB # TODO : make this configurable
-$UpCaseTableSize = 128KB # Typical size
-
-function Get-ExFATSizeRec {
-    param(
-        [string]$Path,
-        [uint64] $TotalSize
-    )
-
-    # Constants
-    $BaseMetadataSize = 32
-    $DirectoryEntrySize = 32
-
-    try {
-        # Get the item (file or directory) at the provided path
-        $item = Get-Item -Path $Path -ErrorAction Stop
-
-        # Calculate metadata size
-        $fileNameLength = $item.Name.Length
-        $metadataSize = $BaseMetadataSize + ($fileNameLength * 2)
-
-        # Calculate directory entries
-        if ($fileNameLength -gt 15) {
-            $numDirEntries = [math]::Ceiling($fileNameLength / 15) + 1
+if (Test-Path $ContainerPath) {
+    if ($Force) {
+        Write-Verbose "Container '$ContainerPath' already exists and will be overwritten."
+        if ($PSCmdlet.ShouldProcess("File '$ContainerPath'", "Remove existing container")) {
+            Remove-Item $ContainerPath -Force
         } else {
-            $numDirEntries = 2
+            throw "Operation cancelled by user. Cannot overwrite '$ContainerPath'."
         }
-        $dirEntriesSize = $numDirEntries * $DirectoryEntrySize
+    } else {
+        throw "Container '$ContainerPath' already exists. Use -Force to overwrite."
+    }
+}
 
-        # Add metadata, file size, and directory entries size to $TotalSize
-        $TotalSize += $metadataSize + $dirEntriesSize
+#----------------------------- Cluster Size -------------------------------------
+[UInt32]$ClusterSize = if ($ClusterSizeKB -eq 'Auto') { $null } else { [int]$ClusterSizeKB * 1KB }
 
+#--------------------------- exFAT Size Helpers --------------------------------
+function Get-DirectoryStats {
+    param([string]$Path)
 
-        if ($item.PSIsContainer) {
-            # It's a directory
-            $childItems = Get-ChildItem -Path $Path -ErrorAction Stop
+    $fileLengths = [System.Collections.Generic.List[UInt64]]::new()
+    $dirLengths  = [System.Collections.Generic.List[UInt64]]::new()
+    [UInt64]$metaSum = 0
 
-            foreach ($childItem in $childItems) {
-                # Recursively call this function for each child item
-                $TotalSize = Get-ExFATSizeRec -Path $childItem.FullName -TotalSize $TotalSize
+    function WalkDir {
+        param([System.IO.DirectoryInfo]$Dir)
+
+        [UInt64]$thisDirBytes = 0
+
+        # Use -ErrorAction SilentlyContinue for potentially inaccessible items (like system junctions)
+        Get-ChildItem -LiteralPath $Dir.FullName -Force -ErrorAction SilentlyContinue | ForEach-Object {
+
+            $nameLen   = $_.Name.Length
+            $nameSlots = [math]::Ceiling($nameLen / 15)          # name entries
+            $dirSlots  = 2 + $nameSlots                          # File + Stream + Names
+            $entryBytes = $dirSlots * 32
+
+            $metaSum      += $entryBytes
+            $thisDirBytes += $entryBytes
+
+            if ($_.PSIsContainer) {
+                WalkDir $_
+            } else {
+                # Handle potential errors reading length (e.g., locked files)
+                try {
+                    $fileLengths.Add([UInt64]$_.Length)
+                } catch {
+                    Write-Warning "Could not get length for file: $($_.FullName). Error: $($_.Exception.Message)"
+                }
             }
-        } else {
-            # It's a file
-
-            # Calculate actual file size and round it up to the nearest multiple of $ClusterSize
-            $fileSize = $item.Length
-            $totalFileSize = [math]::Ceiling($fileSize / $ClusterSize) * $ClusterSize
-
-            # Add metadata, file size, and directory entries size to $TotalSize
-            $TotalSize += $totalFileSize
         }
-    } catch {
-        Write-Error "Error processing item at path ${Path}: $_"
+
+        # At least one 32-byte entry so the directory is not “empty”
+        if ($thisDirBytes -lt 32) { $thisDirBytes = 32 }
+
+        $dirLengths.Add($thisDirBytes)
     }
 
-    return $TotalSize
+    $startItem = Get-Item -LiteralPath $Path -Force
+    if ($startItem -isnot [System.IO.DirectoryInfo]) {
+        # Handle case where InputPath is a single file
+        $nameLen   = $startItem.Name.Length
+        $nameSlots = [math]::Ceiling($nameLen / 15)
+        $dirSlots  = 2 + $nameSlots
+        $entryBytes = $dirSlots * 32
+        $metaSum = $entryBytes
+        $fileLengths.Add([UInt64]$startItem.Length)
+        $dirLengths.Add(32) # Minimal directory entry size for the root
+    } else {
+        WalkDir $startItem
+    }
+
+    [PSCustomObject]@{
+        MetadataSum = $metaSum      # pure 32-byte entry bytes (used for info, not size calc)
+        FileLengths = $fileLengths  # payload of regular files
+        DirLengths  = $dirLengths   # payload of *directory files* (containing entries)
+    }
 }
 
-function Get-ExFATSize {
+function Compute-ExFatSize {
     param(
-        [string]$Path
+        [Parameter(Mandatory)][UInt64[]] $FileLengths,
+        [Parameter(Mandatory)][UInt64[]] $DirLengths,
+        [Parameter(Mandatory)][UInt32]   $Cluster
     )
 
-    try {
-        # Initialize total size
-        $totalSize = $InitialVBRSize + $BackupVBRSize + $InitialFATSize + $UpCaseTableSize
+    # --- Calculate base size (VBR, UpCase Table, File Payloads, Directory Payloads) ---
+    # These parts don't depend on the total cluster count directly.
+    [UInt64]$baseSize = $INITIAL_VBR_SIZE + $BACKUP_VBR_SIZE
+    $baseSize += [math]::Ceiling($RAW_UPCASE_BYTES / $Cluster) * $Cluster  # up-case tbl aligned
 
-        # Call the recursive function
-        $totalSize = Get-ExFATSizeRec -Path $Path -TotalSize $totalSize
+    foreach ($len in $FileLengths) { $baseSize += [math]::Ceiling($len / $Cluster) * $Cluster }
+    foreach ($len in $DirLengths ) { $baseSize += [math]::Ceiling($len / $Cluster) * $Cluster }
 
-        # Add the root directory to $totalSize
-        $totalSize += $ClusterSize
+    # --- Iterative FAT/Bitmap Calculation ---
+    # The size of FAT and Bitmap depends on the total cluster count, which depends on the total size (including FAT/Bitmap).
+    # We iterate until the calculated total size stabilizes.
 
-        # Calculate the size of the Bitmap Allocation Table
-        $numClusters = [math]::Ceiling($totalSize / $ClusterSize)
-        $bitmapSize = [math]::Ceiling($numClusters / 8)
-        $totalSize += $bitmapSize
+    [UInt64]$currentTotalSize = $baseSize # Initial guess: size without FAT/Bitmap
+    [UInt64]$previousTotalSize = 0
+    $maxIterations = 10 # Safety break to prevent infinite loops
+    $iteration = 0
 
-        # Adjust the size of the FAT
-        $fatSize = $numClusters * 4
-        $totalSize += $fatSize - $InitialFATSize
-		
-        # Add safety factor to account for potential filesystem overhead
-        # For smaller datasets (<100MB), we add 1% or 64KB (whichever is larger)
-        # For larger datasets (>=100MB), we add 0.1% or 1MB (whichever is larger)
-        # This scaled approach ensures adequate extra space without excessive overhead
-        $safetyFactor = if ($totalSize -lt 100MB) {
-            [math]::Max(64KB, $totalSize * 0.01)
-        } else {
-            [math]::Max(1MB, $totalSize * 0.001)
-        }
-        $totalSize += $safetyFactor
+    while ($currentTotalSize -ne $previousTotalSize -and $iteration -lt $maxIterations) {
+        $previousTotalSize = $currentTotalSize
+        $iteration++
+        Write-Verbose "Compute-ExFatSize Iteration '$iteration': Starting size = '$previousTotalSize' bytes"
 
-        # Return the minimum disk size needed to store the exFAT filesystem
-        return $totalSize
+        # Calculate cluster count based on the size from the *start* of this iteration
+        $clusterCount = [math]::Ceiling($previousTotalSize / $Cluster)
+        # Ensure minimum cluster count if needed (exFAT has minimums, though usually covered by VBR etc.)
+        if ($clusterCount -lt $EXFAT_PRACTICAL_MIN_CLUSTERS) { $clusterCount = $EXFAT_PRACTICAL_MIN_CLUSTERS } # Practical minimum for FAT entries > sector size
 
-    } catch {
-        Write-Error "Error calculating exFAT size for path ${Path}: $_"
-        return 0
+        # Allocation bitmap (1 bit per cluster, aligned to cluster size)
+        $bitmapBytes = [math]::Ceiling($clusterCount / 8)
+        $bitmapBytesAligned = [math]::Ceiling($bitmapBytes / $Cluster) * $Cluster
+        Write-Verbose "  Clusters: '$clusterCount', Bitmap Bytes: '$bitmapBytes', Aligned Bitmap: '$bitmapBytesAligned'"
+
+        # FAT (4 bytes per cluster, +2 reserved entries, aligned to cluster size)
+        $fatBytes = ([UInt64]$clusterCount + 2) * 4 # Use UInt64 to avoid overflow on large volumes
+        $fatBytesAligned = [math]::Ceiling($fatBytes / $Cluster) * $Cluster
+        Write-Verbose "  FAT Bytes: '$fatBytes', Aligned FAT: '$fatBytesAligned'"
+
+        # Calculate the new total size estimate including FAT and Bitmap
+        $currentTotalSize = $baseSize + $bitmapBytesAligned + $fatBytesAligned
+        Write-Verbose "  New Estimated Total Size: '$currentTotalSize' bytes"
+    }
+
+    if ($iteration -ge $maxIterations) {
+        Write-Warning "FAT/Bitmap size calculation did not converge after '$maxIterations' iterations. Using last calculated size ('$currentTotalSize' bytes). This might indicate an issue or extremely large dataset."
+    }
+
+    Write-Verbose "Compute-ExFatSize Converged Size: '$currentTotalSize' bytes after '$iteration' iterations."
+    return [PSCustomObject]@{
+        TotalSize = $currentTotalSize
+        ClusterCount = $clusterCount
+        IterationHistory = @()
     }
 }
 
-# Calculate size of the container
-$containerSize = Get-ExFATSize -Path $inputPath
+function Get-RecommendedCluster {
+    param([UInt64]$VolumeBytes)
+    switch ($VolumeBytes) {
+        { $_ -le 256MB } { return 4KB }
+        { $_ -le 32GB } { return 32KB }
+        { $_ -le 256TB } { return 128KB }
+        default { return 512KB }
+    }
+}
 
-# Convert to MB and round up to the nearest MB
-$containerSize = [math]::Ceiling($containerSize / 1MB)
+#----------------------------------------------- Drive the two-pass logic
+Write-Host "Calculating required size for '$InputPath'..."
+$stats = Get-DirectoryStats -Path $InputPath
+Write-Verbose "Stats: $($stats.FileLengths.Count) files, $($stats.DirLengths.Count) directories, Metadata: $($stats.MetadataSum) bytes."
 
-# Add extra space for VeraCrypt headers, reserved areas, and potential alignment requirements
-# We use a sliding scale to balance efficiency for small datasets and adequacy for large ones:
-# - For very small datasets (<10MB), add 1MB
-# - For small to medium datasets (10-100MB), add 2MB
-# - For larger datasets (>100MB), add 1% of the total size
-# This approach ensures sufficient space across a wide range of dataset sizes
-if ($containerSize -lt 10) {
-    $containerSize += 1  # Add 1 MB for very small datasets
-} elseif ($containerSize -lt 100) {
-    $containerSize += 2  # Add 2 MB for small datasets
+if (-not $ClusterSize) {
+    Write-Verbose "Cluster size set to 'Auto'. Performing first pass calculation with 4KB cluster..."
+    $firstPassResult = Compute-ExFatSize -FileLengths $stats.FileLengths -DirLengths $stats.DirLengths -Cluster 4KB
+    $firstPassSize = $firstPassResult.TotalSize
+    Write-Verbose "First pass estimated size: '$firstPassSize' bytes"
+
+    $ClusterSize = Get-RecommendedCluster -VolumeBytes $firstPassSize
+    Write-Host "Auto-selected Cluster size: $($ClusterSize / 1KB) KiB based on estimated size."
+    Write-Verbose "Performing second pass calculation with selected cluster size ($($ClusterSize / 1KB) KiB)..."
+    $sizeResult = Compute-ExFatSize -FileLengths $stats.FileLengths -DirLengths $stats.DirLengths -Cluster $ClusterSize
+    $rawSize = $sizeResult.TotalSize
 } else {
-    $containerSize += [math]::Ceiling($containerSize * 0.01)  # Add 1% for larger datasets
+    Write-Host "Using specified Cluster size: $($ClusterSize / 1KB) KiB."
+    Write-Verbose "Performing calculation with specified cluster size..."
+    $sizeResult = Compute-ExFatSize -FileLengths $stats.FileLengths -DirLengths $stats.DirLengths -Cluster $ClusterSize
+    $rawSize = $sizeResult.TotalSize
 }
 
-# Ensure a minimum container size of 2 MB
-$containerSize = [math]::Max(2, $containerSize)
+#---------------------------- Container Sizing ---------------------------------
+$safetyPercentUsed = if ($SafetyPercent -gt 0.0) { $SafetyPercent } else { if ($rawSize -lt 100MB) { 1.0 } else { 0.1 } }
+$safety = if ($rawSize -lt 100MB) { [math]::Max(64KB, [math]::Ceiling($rawSize * $safetyPercentUsed / 100)) }
+          else { [math]::Max(1MB, [math]::Ceiling($rawSize * $safetyPercentUsed / 100)) }
+$contBytes = $rawSize + [UInt64]$safety
+$contMiB = [int][math]::Ceiling($contBytes / 1MB)
+if ($contMiB -lt 2) { $contMiB = 2 }
 
-# Specify encryption algorithm, and hash algorithm
-$encryption = "AES"
-$hash = "sha512"
+$vcOverheadMiBUsed = if ($VCOverheadMiB -gt 0) { $VCOverheadMiB } else {
+    if ($contMiB -lt 10) { 1 } elseif ($contMiB -lt 100) { 2 } else { [math]::Ceiling($contMiB * 0.01) }
+}
+$finalContMiB = $contMiB + $vcOverheadMiBUsed
 
-# Create a SecureString password
-$password = Read-Host -AsSecureString -Prompt "Enter your password"
+Write-Host ("Cluster Size  : {0} KiB`nCalculated FS: {1:N0} bytes`nSafety Margin: {2:N0} bytes ({3}%)`nVC Overhead  : {4} MiB`nFinal Size   : {5} MiB" -f
+    ($ClusterSize/1KB), $rawSize, $safety, $safetyPercentUsed, $vcOverheadMiBUsed, $finalContMiB)
 
-# Create a PSCredential object
-$cred = New-Object System.Management.Automation.PSCredential ("username", $password)
+#---- Secure Password Prompt ----
+if (-not $Password) {
+    $Password = Read-Host -AsSecureString -Prompt "Enter container password"
+}
+$cred = New-Object System.Management.Automation.PSCredential ("VeraCryptUser", $Password)
+$plainPassword = $cred.GetNetworkCredential().Password
 
-Write-Host "Creating VeraCrypt container `"$containerPath`" ..."
-
-# Create file container using VeraCrypt Format
-# TODO: Add a switch to VeraCrypt Format to allow specifying the cluster size to use for the container
-$veraCryptFormatArgs = "/create `"$containerPath`" /size `"${containerSize}M`" /password $($cred.GetNetworkCredential().Password) /encryption $encryption /hash $hash /filesystem `"exFAT`" /quick /silent"
-Start-Process $veraCryptFormatExe -ArgumentList $veraCryptFormatArgs -NoNewWindow -Wait
-
-# Check that the container was successfully created
-if (-not (Test-Path $containerPath)) {
-    Write-Host "An error occurred while creating the VeraCrypt container."
+if ([string]::IsNullOrWhiteSpace($plainPassword)) {
+    Write-Host "Error: Password cannot be empty. Please provide a non-empty password." -ForegroundColor Red
     exit 1
 }
 
-# Get a list of currently used drive letters
-$driveLetter = Get-Volume | Where-Object { $_.DriveLetter -ne $null } | Select-Object -ExpandProperty DriveLetter
+#---- Main Action ----
+$mounted = $false
+$driveLetter = $null
 
-# Find the first available drive letter
-$unusedDriveLetter = (70..90 | ForEach-Object { [char]$_ } | Where-Object { $_ -notin $driveLetter })[0]
+$errFile   = New-VcErrFile  
+$mountFile = New-VcErrFile
 
-# If no available drive letter was found, print an error message and exit the script
-if ($null -eq $unusedDriveLetter) {
-    # delete the file container that was created
-    Remove-Item -Path $containerPath -Force
-    Write-Error "No available drive letters found. Please free up a drive letter and try again."
-    exit 1
+try {
+    #--- Create Container ----
+    if ($PSCmdlet.ShouldProcess("File '$ContainerPath'", "Create VeraCrypt container ($finalContMiB MiB)")) {
+        $formatArgs = @(
+            '/create', $ContainerPath,
+            '/size', "$($finalContMiB)M",
+            '/password', $plainPassword,
+            '/encryption', $EncryptionAlg,
+            '/hash', $HashAlg,
+            '/filesystem', 'exFAT',
+            '/quick', '/silent',
+            '/force'
+        )
+        $maskedArgs = $formatArgs.Clone()
+        $pwIndex = [array]::IndexOf($maskedArgs, '/password')
+        if ($pwIndex -ge 0 -and $pwIndex + 1 -lt $maskedArgs.Length) { $maskedArgs[$pwIndex+1] = '********' }
+        Write-Verbose "Executing: `"$VeraCryptFormatExe`" $($maskedArgs -join ' ')"
+
+        $proc = Start-Process -FilePath $VeraCryptFormatExe -ArgumentList $formatArgs -NoNewWindow -Wait -PassThru -RedirectStandardError $errFile
+        if ($proc.ExitCode -ne 0) {
+            $errMsg = if (Test-Path $errFile) { Get-Content $errFile -Raw } else { "No error output captured." }
+            throw "VeraCrypt Format failed (code $($proc.ExitCode)). Error: $errMsg"
+        }
+        Write-Verbose "VeraCrypt Format completed successfully."
+    } else {
+        Write-Host "Container creation skipped due to -WhatIf."
+        exit
+    }
+
+    #--- Choose Drive Letter ----
+    $used = (Get-PSDrive -PSProvider FileSystem).Name
+    $driveLetter = (67..90 | ForEach-Object {[char]$_}) |
+        Where-Object { $_ -notin $used } |
+        Select-Object -First 1
+    if (-not $driveLetter) { throw 'No free drive letters found (C-Z).' }
+    Write-Verbose "Selected drive letter: $driveLetter"
+
+    #--- Mount ----
+    if ($PSCmdlet.ShouldProcess("Drive $driveLetter", "Mount VeraCrypt volume '$ContainerPath'")) {
+        $mountArgs = @(
+            '/volume', $ContainerPath,
+            '/letter', $driveLetter,
+            '/m', 'rm',
+            '/password', $plainPassword,
+            '/quit', '/silent'
+        )
+        $maskedArgs = $mountArgs.Clone()
+        $pwIndex = [array]::IndexOf($maskedArgs, '/password')
+        if ($pwIndex -ge 0 -and $pwIndex + 1 -lt $maskedArgs.Length) { $maskedArgs[$pwIndex+1] = '********' }
+        Write-Verbose "Executing: `"$VeraCryptExe`" $($maskedArgs -join ' ')"
+
+        $mountProc = Start-Process -FilePath $VeraCryptExe -ArgumentList $mountArgs -NoNewWindow -Wait -PassThru -RedirectStandardError $mountFile
+        if ($mountProc.ExitCode -ne 0) {
+            $errMsg = if (Test-Path $mountFile) { Get-Content $mountFile -Raw } else { "No error output captured." }
+            throw "VeraCrypt mount failed (code $($mountProc.ExitCode)). Error: $errMsg"
+        }
+
+        $root = "$($driveLetter):\"
+        Write-Verbose "Waiting for drive $root to become available..."
+        $mountTimeoutSeconds = 30
+        $mountCheckInterval = 0.5
+        $elapsed = 0
+        while (-not (Test-Path $root) -and $elapsed -lt $mountTimeoutSeconds) {
+            Start-Sleep -Seconds $mountCheckInterval
+            $elapsed += $mountCheckInterval
+        }
+
+        if (-not (Test-Path $root)) { throw "Drive $driveLetter did not appear within $mountTimeoutSeconds seconds." }
+        $mounted = $true
+        Write-Verbose "Drive $root mounted successfully."
+    } else {
+        Write-Host "Mounting skipped due to -WhatIf."
+        exit
+    }
+
+    #--- Copy Data ----
+    $destinationPath = "$($driveLetter):\"
+    if ($PSCmdlet.ShouldProcess("'$InputPath' -> '$destinationPath'", "Copy input data into container")) {
+        Write-Verbose "Starting data copy..."
+        if (Test-Path $InputPath -PathType Container) {
+            Copy-Item -Path "$InputPath\*" -Destination $destinationPath -Recurse -Force -ErrorAction Stop
+            Write-Verbose "Copied directory contents recursively."
+        } else {
+            Copy-Item -Path $InputPath -Destination $destinationPath -Force -ErrorAction Stop
+            Write-Verbose "Copied single file."
+        }
+        try {
+            $driveInfo = Get-PSDrive $driveLetter -ErrorAction Stop
+            $freeSpace = $driveInfo.Free
+            Write-Verbose "Free space after copy: $freeSpace bytes."
+            if ($freeSpace -lt 0) {
+                Write-Warning 'Reported free space is negative. This might indicate an issue, but the copy might still be okay.'
+            } elseif ($freeSpace -lt 1MB) {
+                Write-Warning "Very low free space remaining ($freeSpace bytes). The container might be too small if data changes slightly."
+            }
+        } catch {
+            Write-Warning "Could not verify free space on drive $driveLetter after copy. Error: $($_.Exception.Message)"
+        }
+        Write-Host "Data copy completed."
+    } else {
+        Write-Host "Data copy skipped due to -WhatIf."
+    }
+} catch {
+    Write-Error "An error occurred: $($_.Exception.Message)"
+} finally {
+    if (Test-Path variable:plainPassword) { Clear-Variable plainPassword -ErrorAction SilentlyContinue }
+    if ($mounted) {
+        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 "Unmount skipped due to -WhatIf."
+        }
+    }
+    foreach($f in @($errFile,$mountFile) | Where-Object { $_ }) {  
+        if(Test-Path $f){  
+            try { Set-Content -Path $f -Value ($null) -Encoding Byte -Force } catch{}  
+            Remove-Item $f -Force -ErrorAction SilentlyContinue  
+        }  
+    }
 }
 
-Write-Host "Mounting the newly created VeraCrypt container..."
-
-# Mount the container to the chosen drive letter as removable media
-Start-Process $veraCryptExe -ArgumentList "/volume `"$containerPath`" /letter $unusedDriveLetter /m rm /password $($cred.GetNetworkCredential().Password) /quit" -NoNewWindow -Wait
-
-# Check if the volume has been mounted successfully
-$mountedDriveRoot = "${unusedDriveLetter}:\"
-if (-not (Test-Path -Path $mountedDriveRoot)) {
-    # Volume mount failed
-    Write-Error "Failed to mount the volume. Please make sure VeraCrypt.exe is working correctly."
-    # delete the file container that was created
-    Remove-Item -Path $containerPath -Force
-    exit 1
-}
-
-Write-Host "Copying data to the mounted VeraCrypt container..."
-
-# Copy the file or directory to the mounted drive
-if (Test-Path -Path $inputPath -PathType Container) {
-    # For directories
-    Copy-Item -Path $inputPath -Destination "$($unusedDriveLetter):\" -Recurse
+if ($PSCmdlet.ShouldProcess("File '$ContainerPath'", "Create VeraCrypt container ($finalContMiB MiB)")) {
+    Write-Host ("Script finished. VeraCrypt container created at '{0}' ({1} MiB)." -f $ContainerPath, $finalContMiB)
 } else {
-    # For files
-    Copy-Item -Path $inputPath -Destination "$($unusedDriveLetter):\"
+    Write-Host ("Script finished (simulation mode).")
 }
-
-Write-Host "Copying completed. Dismounting the VeraCrypt container..."
-
-# give some time for the file system to flush the data to the disk
-Start-Sleep -Seconds 5
-
-# Dismount the volume
-Start-Process $veraCryptExe -ArgumentList "/dismount $unusedDriveLetter /quit" -NoNewWindow -Wait
-
-Write-Host "VeraCrypt container created successfully."

doc/chm/create_chm.bat

@@ -1,11 +1,41 @@
 PATH=%PATH%;C:\Program Files (x86)\HTML Help Workshop
 
 set CHMBUILDPATH=%~dp0
-cd %CHMBUILDPATH%
+cd %CHMBUILDPATH%\en
 
-xcopy /E ..\html\* .
+xcopy /E ..\..\html\en\* .
 
 hhc VeraCrypt.hhp
 
-del /F /Q *.html *.css *.jpg *.gif *.png *.svg
-rmdir /s /Q CompilingGuidelineWin ru
+del /F /Q *.html *.css *.jpg *.gif *.png *.svg *.js
+rmdir /s /Q CompilingGuidelineWin
+
+move /Y "VeraCrypt User Guide.chm" "..\VeraCrypt User Guide.chm"
+
+cd %CHMBUILDPATH%\zh-cn
+
+xcopy /E ..\..\html\zh-cn\* .
+
+hhc VeraCrypt.zh-cn.hhp
+
+del /F /Q *.html *.css *.jpg *.gif *.png *.svg *.js
+rmdir /s /Q CompilingGuidelineWin
+
+move /Y "VeraCrypt User Guide.zh-cn.chm" "..\VeraCrypt User Guide.zh-cn.chm"
+
+cd %CHMBUILDPATH%\ru
+
+xcopy /E ..\..\html\ru\* .
+
+hhc VeraCrypt.ru.hhp
+
+del /F /Q *.html *.css *.jpg *.gif *.png *.svg *.js
+rmdir /s /Q CompilingGuidelineWin
+
+move /Y "VeraCrypt User Guide.ru.chm" "..\VeraCrypt User Guide.ru.chm"
+
+cd %CHMBUILDPATH%
+
+
+
+

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,11 +13,11 @@ 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
 Avoid Third-Party File Extensions.html
-bank_30x30.png
 BC_Logo_30x30.png
 BCH_Logo_30x30.png
 Beginner's Tutorial.html
@@ -51,6 +51,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
@@ -67,18 +69,6 @@ Defragmenting.html
 Digital Signatures.html
 Disclaimers.html
 Documentation.html
-Donation.html
-Donation_donate.gif
-Donation_donate_CHF.gif
-Donation_donate_Dollars.gif
-Donation_donate_Euros.gif
-Donation_donate_GBP.gif
-Donation_donate_PLN.gif
-Donation_donate_YEN.gif
-Donation_VeraCrypt_Bitcoin_small.png
-Donation_VeraCrypt_BitcoinCash.png
-Donation_VeraCrypt_Litecoin.png
-Donation_VeraCrypt_Monero.png
 Encryption Algorithms.html
 Encryption Scheme.html
 FAQ.html
@@ -102,6 +92,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
@@ -112,6 +103,7 @@ liberapay_donate.svg
 LTC_Logo_30x30.png
 Main Program Window.html
 Malware.html
+mastodon_veracrypt.PNG
 Memory Dump Files.html
 Miscellaneous.html
 Modes of Operation.html
@@ -122,6 +114,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
@@ -188,4 +181,3 @@ Wear-Leveling.html
 Whirlpool.html
 
 [INFOTYPES]
-

doc/chm/ru/VeraCrypt.ru.hhc

@@ -0,0 +1,449 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
+<HTML>
+<HEAD>
+<meta name="GENERATOR" content="Microsoft&reg; HTML Help Workshop 4.1">
+<!-- Sitemap 1.0 -->
+</HEAD><BODY>
+<UL>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Äîêóìåíòàöèÿ">
+        <param name="Local" value="Documentation.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Ïðåäèñëîâèå">
+        <param name="Local" value="Preface.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Ââåäåíèå">
+        <param name="Local" value="Introduction.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Ðóêîâîäñòâî äëÿ íà÷èíàþùèõ">
+        <param name="Local" value="Beginner's Tutorial.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Òîì VeraCrypt">
+        <param name="Local" value="VeraCrypt Volume.html">
+        </OBJECT>
+    <UL>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ñîçäàíèå íîâîãî òîìà VeraCrypt">
+            <param name="Local" value="Creating New Volumes.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Èçáðàííûå òîìà">
+            <param name="Local" value="Favorite Volumes.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ñèñòåìíûå èçáðàííûå òîìà">
+            <param name="Local" value="System Favorite Volumes.html">
+            </OBJECT>
+    </UL>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Øèôðîâàíèå ñèñòåìû">
+        <param name="Local" value="System Encryption.html">
+        </OBJECT>
+    <UL>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ñêðûòàÿ îïåðàöèîííàÿ ñèñòåìà">
+            <param name="Local" value="Hidden Operating System.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Îïåðàöèîííûå ñèñòåìû, ïîääåðæèâàþùèå ñèñòåìíîå øèôðîâàíèå">
+            <param name="Local" value="Supported Systems for System Encryption.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Äèñê âîññòàíîâëåíèÿ VeraCrypt (Rescue Disk)">
+            <param name="Local" value="VeraCrypt Rescue Disk.html">
+            </OBJECT>
+    </UL>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Ïðàâäîïîäîáíîå îòðèöàíèå íàëè÷èÿ øèôðîâàíèÿ">
+        <param name="Local" value="Plausible Deniability.html">
+        </OBJECT>
+    <UL>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ñêðûòûé òîì">
+            <param name="Local" value="Hidden Volume.html">
+            </OBJECT>
+        <UL>
+            <LI> <OBJECT type="text/sitemap">
+                <param name="Name" value="Çàùèòà ñêðûòûõ òîìîâ îò ïîâðåæäåíèé">
+                <param name="Local" value="Protection of Hidden Volumes.html">
+                </OBJECT>
+            <LI> <OBJECT type="text/sitemap">
+                <param name="Name" value="Òðåáîâàíèÿ áåçîïàñíîñòè è ìåðû ïðåäîñòîðîæíîñòè, êàñàþùèåñÿ ñêðûòûõ òîìîâ">
+                <param name="Local" value="Security Requirements for Hidden Volumes.html">
+                </OBJECT>
+        </UL>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ñêðûòàÿ îïåðàöèîííàÿ ñèñòåìà">
+            <param name="Local" value="VeraCrypt Hidden Operating System.html">
+            </OBJECT>
+    </UL>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Ãëàâíîå îêíî ïðîãðàììû">
+        <param name="Local" value="Main Program Window.html">
+        </OBJECT>
+    <UL>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ìåíþ ïðîãðàììû">
+            <param name="Local" value="Program Menu.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ìîíòèðîâàíèå òîìîâ">
+            <param name="Local" value="Mounting VeraCrypt Volumes.html">
+            </OBJECT>
+    </UL>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Îáû÷íîå ðàçìîíòèðîâàíèå ïðîòèâ ïðèíóäèòåëüíîãî">
+        <param name="Local" value="Normal Unmount vs Force Unmount.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Î ðèñêàõ, ñâÿçàííûõ ñî ñòîðîííèìè ðàñøèðåíèÿìè ôàéëîâ">
+        <param name="Local" value="Avoid Third-Party File Extensions.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Ðàñïàðàëëåëèâàíèå">
+        <param name="Local" value="Parallelization.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Êîíâåéåðèçàöèÿ">
+        <param name="Local" value="Pipelining.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Àïïàðàòíîå óñêîðåíèå">
+        <param name="Local" value="Hardware Acceleration.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Ãîðÿ÷èå êëàâèøè">
+        <param name="Local" value="Hot Keys.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Êëþ÷åâûå ôàéëû">
+        <param name="Local" value="Keyfiles in VeraCrypt.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Òîêåíû áåçîïàñíîñòè è ñìàðò-êàðòû">
+        <param name="Local" value="Security Tokens & Smart Cards.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Ïîðòàòèâíûé (ïåðåíîñíîé) ðåæèì">
+        <param name="Local" value="Portable Mode.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Ïîääåðæêà TrueCrypt">
+        <param name="Local" value="TrueCrypt Support.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Ïðåîáðàçîâàíèå òîìîâ è ðàçäåëîâ TrueCrypt â ôîðìàò VeraCrypt">
+        <param name="Local" value="Converting TrueCrypt volumes and partitions.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Ðóêîâîäñòâî ïî ïðåîáðàçîâàíèþ òîìîâ äëÿ âåðñèé 1.26 è íîâåå">
+        <param name="Local" value="Conversion_Guide_VeraCrypt_1.26_and_Later.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Ïàðàìåòðû ìîíòèðîâàíèÿ ïî óìîë÷àíèþ">
+        <param name="Local" value="Default Mount Parameters.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="ßçûêîâûå ïàêåòû">
+        <param name="Local" value="Language Packs.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Àëãîðèòìû øèôðîâàíèÿ">
+        <param name="Local" value="Encryption Algorithms.html">
+        </OBJECT>
+    <UL>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="AES">
+            <param name="Local" value="AES.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Camellia">
+            <param name="Local" value="Camellia.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Kuznyechik">
+            <param name="Local" value="Kuznyechik.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Serpent">
+            <param name="Local" value="Serpent.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Twofish">
+            <param name="Local" value="Twofish.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Êàñêàäû øèôðîâ">
+            <param name="Local" value="Cascades.html">
+            </OBJECT>
+    </UL>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Àëãîðèòìû õåøèðîâàíèÿ">
+        <param name="Local" value="Hash Algorithms.html">
+        </OBJECT>
+    <UL>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="BLAKE2s-256">
+            <param name="Local" value="BLAKE2s-256.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="SHA-256">
+            <param name="Local" value="SHA-256.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="SHA-512">
+            <param name="Local" value="SHA-512.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Whirlpool">
+            <param name="Local" value="Whirlpool.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Streebog">
+            <param name="Local" value="Streebog.html">
+            </OBJECT>
+    </UL>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Ïîääåðæèâàåìûå îïåðàöèîííûå ñèñòåìû">
+        <param name="Local" value="Supported Operating Systems.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Èñïîëüçîâàíèå â êîìàíäíîé ñòðîêå">
+        <param name="Local" value="Command Line Usage.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Ìîäåëü áåçîïàñíîñòè">
+        <param name="Local" value="Security Model.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Òðåáîâàíèÿ áåçîïàñíîñòè è ìåðû ïðåäîñòîðîæíîñòè">
+        <param name="Local" value="Security Requirements and Precautions.html">
+        </OBJECT>
+    <UL>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Óòå÷êè äàííûõ">
+            <param name="Local" value="Data Leaks.html">
+            </OBJECT>
+        <UL>
+            <LI> <OBJECT type="text/sitemap">
+                <param name="Name" value="Ôàéë ïîäêà÷êè">
+                <param name="Local" value="Paging File.html">
+                </OBJECT>
+            <LI> <OBJECT type="text/sitemap">
+                <param name="Name" value="Ôàéëû äàìïà ïàìÿòè">
+                <param name="Local" value="Memory Dump Files.html">
+                </OBJECT>
+            <LI> <OBJECT type="text/sitemap">
+                <param name="Name" value="Ôàéë ãèáåðíàöèè">
+                <param name="Local" value="Hibernation File.html">
+                </OBJECT>
+        </UL>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Íåçàøèôðîâàííûå äàííûå â ÎÇÓ">
+            <param name="Local" value="Unencrypted Data in RAM.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Øèôðîâàíèå îïåðàòèâíîé ïàìÿòè â VeraCrypt">
+            <param name="Local" value="VeraCrypt RAM Encryption.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Çàùèòà ïàìÿòè â VeraCrypt">
+            <param name="Local" value="VeraCrypt Memory Protection.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ôèçè÷åñêàÿ áåçîïàñíîñòü">
+            <param name="Local" value="Physical Security.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Âðåäîíîñíîå ÏÎ (malware)">
+            <param name="Local" value="Malware.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ìíîãîïîëüçîâàòåëüñêàÿ ñðåäà">
+            <param name="Local" value="Multi-User Environment.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ïîäëèííîñòü è öåëîñòíîñòü äàííûõ">
+            <param name="Local" value="Authenticity and Integrity.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Âûáîð ïàðîëåé è êëþ÷åâûõ ôàéëîâ">
+            <param name="Local" value="Choosing Passwords and Keyfiles.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Èçìåíåíèå ïàðîëåé è êëþ÷åâûõ ôàéëîâ">
+            <param name="Local" value="Changing Passwords and Keyfiles.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Îïåðàöèÿ Trim">
+            <param name="Local" value="Trim Operation.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ðàñïðåäåëåíèå èçíîñà (Wear-Leveling)">
+            <param name="Local" value="Wear-Leveling.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ïåðåðàñïðåäåë¸ííûå ñåêòîðà">
+            <param name="Local" value="Reallocated Sectors.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Äåôðàãìåíòàöèÿ">
+            <param name="Local" value="Defragmenting.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Æóðíàëèðóåìûå ôàéëîâûå ñèñòåìû">
+            <param name="Local" value="Journaling File Systems.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Êëîíèðîâàíèå òîìîâ">
+            <param name="Local" value="Volume Clones.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Äîïîëíèòåëüíûå òðåáîâàíèÿ áåçîïàñíîñòè è ìåðû ïðåäîñòîðîæíîñòè">
+            <param name="Local" value="Additional Security Requirements and Precautions.html">
+            </OBJECT>
+    </UL>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Î áåçîïàñíîì ðåçåðâíîì êîïèðîâàíèè">
+        <param name="Local" value="How to Back Up Securely.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Ðàçíîå">
+        <param name="Local" value="Miscellaneous.html">
+        </OBJECT>
+    <UL>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Èñïîëüçîâàíèå VeraCrypt áåç ïðàâ àäìèíèñòðàòîðà">
+            <param name="Local" value="Using VeraCrypt Without Administrator Privileges.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Îáùèé äîñòóï ïî ñåòè">
+            <param name="Local" value="Sharing over Network.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ðàáîòà VeraCrypt â ôîíîâîì ðåæèìå">
+            <param name="Local" value="VeraCrypt Background Task.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Òîì, ñìîíòèðîâàííûé êàê ñìåííûé íîñèòåëü">
+            <param name="Local" value="Removable Medium Volume.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ñèñòåìíûå ôàéëû VeraCrypt è ïðîãðàììíûå äàííûå">
+            <param name="Local" value="VeraCrypt System Files.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Êàê óäàëèòü øèôðîâàíèå">
+            <param name="Local" value="Removing Encryption.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Óäàëåíèå VeraCrypt">
+            <param name="Local" value="Uninstalling VeraCrypt.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Öèôðîâûå ïîäïèñè">
+            <param name="Local" value="Digital Signatures.html">
+            </OBJECT>
+    </UL>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Óñòðàíåíèå çàòðóäíåíèé">
+        <param name="Local" value="Troubleshooting.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Íåñîâìåñòèìîñòè">
+        <param name="Local" value="Incompatibilities.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Çàìå÷åííûå ïðîáëåìû è îãðàíè÷åíèÿ">
+        <param name="Local" value="Issues and Limitations.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Âîïðîñû è îòâåòû">
+        <param name="Local" value="FAQ.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Òåõíè÷åñêèå ïîäðîáíîñòè">
+        <param name="Local" value="Technical Details.html">
+        </OBJECT>
+    <UL>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ñèñòåìà îáîçíà÷åíèé">
+            <param name="Local" value="Notation.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ñõåìà øèôðîâàíèÿ">
+            <param name="Local" value="Encryption Scheme.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ðåæèìû ðàáîòû">
+            <param name="Local" value="Modes of Operation.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ôîðìèðîâàíèå êëþ÷à çàãîëîâêà, ñîëü è êîëè÷åñòâî èòåðàöèé">
+            <param name="Local" value="Header Key Derivation.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ãåíåðàòîð ñëó÷àéíûõ ÷èñåë">
+            <param name="Local" value="Random Number Generator.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Êëþ÷åâûå ôàéëû">
+            <param name="Local" value="Keyfiles.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="PIM (Ïåðñîíàëüíûé ìíîæèòåëü èòåðàöèé)">
+            <param name="Local" value="Personal Iterations Multiplier (PIM).html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ñïåöèôèêàöèÿ ôîðìàòà òîìîâ VeraCrypt">
+            <param name="Local" value="VeraCrypt Volume Format Specification.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ñîîòâåòñòâèå ñòàíäàðòàì è ñïåöèôèêàöèÿì">
+            <param name="Local" value="Standard Compliance.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Èñõîäíûé êîä ïðîãðàììû">
+            <param name="Local" value="Source Code.html">
+            </OBJECT>
+        <LI> <OBJECT type="text/sitemap">
+            <param name="Name" value="Ñáîðêà VeraCrypt èç èñõîäíîãî êîäà">
+            <param name="Local" value="CompilingGuidelines.html">
+            </OBJECT>
+        <UL>
+            <LI> <OBJECT type="text/sitemap">
+                <param name="Name" value="Ðóêîâîäñòâî ïî ñáîðêå â Windows">
+                <param name="Local" value="CompilingGuidelineWin.html">
+                </OBJECT>
+            <LI> <OBJECT type="text/sitemap">
+                <param name="Name" value="Ðóêîâîäñòâî ïî ñáîðêå â Linux">
+                <param name="Local" value="CompilingGuidelineLinux.html">
+                </OBJECT>
+        </UL>
+    </UL>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Ñâÿçü ñ àâòîðàìè">
+        <param name="Local" value="Contact.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Ïðàâîâàÿ èíôîðìàöèÿ">
+        <param name="Local" value="Legal Information.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Èñòîðèÿ âåðñèé">
+        <param name="Local" value="Release Notes.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Áëàãîäàðíîñòè">
+        <param name="Local" value="Acknowledgements.html">
+        </OBJECT>
+    <LI> <OBJECT type="text/sitemap">
+        <param name="Name" value="Ññûëêè">
+        <param name="Local" value="References.html">
+        </OBJECT>
+</UL>
+</BODY></HTML>

doc/chm/ru/VeraCrypt.ru.hhk

@@ -0,0 +1,13 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
+<HTML>
+<HEAD>
+<!-- Sitemap 1.0 -->
+</HEAD><BODY>
+<UL>
+<LI> <OBJECT type="text/sitemap">
+     <param name="Name" value="Äîêóìåíòàöèÿ">
+     <param name="Local" value="Documentation.html">
+     </OBJECT>
+
+</UL>
+</BODY></HTML>

doc/chm/ru/VeraCrypt.ru.hhp

@@ -0,0 +1,180 @@
+[OPTIONS]
+Compatibility=1.1 or later
+Compiled file=VeraCrypt User Guide.ru.chm
+Contents file=VeraCrypt.ru.hhc
+Default topic=Documentation.html
+Default Font=Tahoma,9,0
+Display compile progress=No
+Full-text search=Yes
+Index file=VeraCrypt.ru.hhk
+Language=0x419 Ðóññêèé(Ðîññèÿ)
+Title=Ðóêîâîäñòâî ïîëüçîâàòåëÿ VeraCrypt
+
+[FILES]
+Acknowledgements.html
+Additional Security Requirements and Precautions.html
+AES.html
+arrow_right.gif
+Authenticity and Integrity.html
+Authors.html
+Avoid Third-Party File Extensions.html
+BC_Logo_30x30.png
+BCH_Logo_30x30.png
+Beginner's Tutorial.html
+Beginner's Tutorial_Image_001.png
+Beginner's Tutorial_Image_002.png
+Beginner's Tutorial_Image_003.png
+Beginner's Tutorial_Image_004.png
+Beginner's Tutorial_Image_005.png
+Beginner's Tutorial_Image_007.png
+Beginner's Tutorial_Image_008.png
+Beginner's Tutorial_Image_009.png
+Beginner's Tutorial_Image_010.png
+Beginner's Tutorial_Image_011.png
+Beginner's Tutorial_Image_012.png
+Beginner's Tutorial_Image_013.png
+Beginner's Tutorial_Image_014.png
+Beginner's Tutorial_Image_015.png
+Beginner's Tutorial_Image_016.png
+Beginner's Tutorial_Image_017.png
+Beginner's Tutorial_Image_018.png
+Beginner's Tutorial_Image_019.png
+Beginner's Tutorial_Image_020.png
+Beginner's Tutorial_Image_021.png
+Beginner's Tutorial_Image_022.png
+Beginner's Tutorial_Image_023.png
+Beginner's Tutorial_Image_024.png
+Beginner's Tutorial_Image_034.png
+BLAKE2s-256.html
+Camellia.html
+Cascades.html
+Changing Passwords and Keyfiles.html
+Choosing Passwords and Keyfiles.html
+Command Line Usage.html
+CompilingGuidelineLinux.html
+CompilingGuidelines.html
+CompilingGuidelineWin.html
+Contact.html
+Contributed Resources.html
+Conversion_Guide_VeraCrypt_1.26_and_Later.html
+Converting TrueCrypt volumes and partitions.html
+Converting TrueCrypt volumes and partitions_truecrypt_convertion.png
+Creating New Volumes.html
+Data Leaks.html
+Default Mount Parameters.html
+Default Mount Parameters_VeraCrypt_password_using_default_parameters.png
+Defragmenting.html
+Digital Signatures.html
+Disclaimers.html
+Documentation.html
+Encryption Algorithms.html
+Encryption Scheme.html
+FAQ.html
+Favorite Volumes.html
+flattr-badge-large.png
+gf2_mul.gif
+Hardware Acceleration.html
+Hash Algorithms.html
+Header Key Derivation.html
+Hibernation File.html
+Hidden Operating System.html
+Hidden Volume.html
+Home_facebook_veracrypt.png
+Home_reddit.png
+Home_utilities-file-archiver-3.png
+Home_VeraCrypt_Default_Mount_Parameters.png
+Home_VeraCrypt_menu_Default_Mount_Parameters.png
+Hot Keys.html
+How to Back Up Securely.html
+Incompatibilities.html
+Introduction.html
+Issues and Limitations.html
+Journaling File Systems.html
+Keyfiles in VeraCrypt.html
+Keyfiles in VeraCrypt_Image_040.png
+Keyfiles.html
+Kuznyechik.html
+Language Packs.html
+Legal Information.html
+liberapay_donate.svg
+LTC_Logo_30x30.png
+Main Program Window.html
+Malware.html
+mastodon_veracrypt.PNG
+Memory Dump Files.html
+Miscellaneous.html
+Modes of Operation.html
+Monero_Logo_30x30.png
+Mounting VeraCrypt Volumes.html
+Multi-User Environment.html
+Notation.html
+Paging File.html
+Parallelization.html
+paypal_30x30.png
+Personal Iterations Multiplier (PIM).html
+Personal Iterations Multiplier (PIM)_VeraCrypt_ChangePIM_Step1.png
+Personal Iterations Multiplier (PIM)_VeraCrypt_ChangePIM_Step2.png
+Personal Iterations Multiplier (PIM)_VeraCrypt_ChangePIM_System_Step1.png
+Personal Iterations Multiplier (PIM)_VeraCrypt_ChangePIM_System_Step2.png
+Personal Iterations Multiplier (PIM)_VeraCrypt_UsePIM_Step1.png
+Personal Iterations Multiplier (PIM)_VeraCrypt_UsePIM_Step2.png
+Physical Security.html
+Pipelining.html
+Plausible Deniability.html
+Portable Mode.html
+Preface.html
+Program Menu.html
+Protection of Hidden Volumes.html
+Protection of Hidden Volumes_Image_027.png
+Protection of Hidden Volumes_Image_028.png
+Protection of Hidden Volumes_Image_029.png
+Protection of Hidden Volumes_Image_030.png
+Protection of Hidden Volumes_Image_031.png
+Random Number Generator.html
+Reallocated Sectors.html
+References.html
+Release Notes.html
+Removable Medium Volume.html
+Removing Encryption.html
+Security Model.html
+Security Requirements and Precautions.html
+Security Requirements for Hidden Volumes.html
+Security Tokens & Smart Cards.html
+Serpent.html
+SHA-256.html
+SHA-512.html
+Sharing over Network.html
+Source Code.html
+Standard Compliance.html
+Streebog.html
+styles.css
+Supported Operating Systems.html
+Supported Systems for System Encryption.html
+System Encryption.html
+System Favorite Volumes.html
+Technical Details.html
+Trim Operation.html
+Troubleshooting.html
+TrueCrypt Support.html
+TrueCrypt Support_truecrypt_mode_gui.png
+twitter_veracrypt.PNG
+Twofish.html
+Unencrypted Data in RAM.html
+Uninstalling VeraCrypt.html
+Using VeraCrypt Without Administrator Privileges.html
+VeraCrypt Background Task.html
+VeraCrypt Hidden Operating System.html
+VeraCrypt License.html
+VeraCrypt Memory Protection.html
+VeraCrypt RAM Encryption.html
+VeraCrypt Rescue Disk.html
+VeraCrypt System Files.html
+VeraCrypt Volume Format Specification.html
+VeraCrypt Volume.html
+VeraCrypt128x128.png
+Volume Clones.html
+Wear-Leveling.html
+Whirlpool.html
+
+[INFOTYPES]
+

doc/chm/zh-cn/VeraCrypt.zh-cn.hhc

@@ -0,0 +1,449 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
+<HTML>
+<HEAD>
+<meta name="GENERATOR" content="Microsoft&reg; HTML Help Workshop 4.1">
+<!-- Sitemap 1.0 -->
+</HEAD><BODY>
+<UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="目录">
+		<param name="Local" value="Documentation.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="前言">
+		<param name="Local" value="Preface.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="简介">
+		<param name="Local" value="Introduction.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="初学者教程">
+		<param name="Local" value="Beginner's Tutorial.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="VeraCrypt卷">
+		<param name="Local" value="VeraCrypt Volume.html">
+		</OBJECT>
+	<UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="创建新的VeraCrypt卷">
+			<param name="Local" value="Creating New Volumes.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="收藏卷">
+			<param name="Local" value="Favorite Volumes.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="系统收藏卷">
+			<param name="Local" value="System Favorite Volumes.html">
+			</OBJECT>
+	</UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="系统加密">
+		<param name="Local" value="System Encryption.html">
+		</OBJECT>
+	<UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="隐藏操作系统">
+			<param name="Local" value="Hidden Operating System.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="支持系统加密的操作系统">
+			<param name="Local" value="Supported Systems for System Encryption.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="VeraCrypt急救盘">
+			<param name="Local" value="VeraCrypt Rescue Disk.html">
+			</OBJECT>
+	</UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="合理否认">
+		<param name="Local" value="Plausible Deniability.html">
+		</OBJECT>
+	<UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="隐藏卷">
+			<param name="Local" value="Hidden Volume.html">
+			</OBJECT>
+		<UL>
+			<LI> <OBJECT type="text/sitemap">
+				<param name="Name" value="隐藏卷防损坏保护">
+				<param name="Local" value="Protection of Hidden Volumes.html">
+				</OBJECT>
+			<LI> <OBJECT type="text/sitemap">
+				<param name="Name" value="隐藏卷的安全要求和注意事项">
+				<param name="Local" value="Security Requirements for Hidden Volumes.html">
+				</OBJECT>
+		</UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="隐藏操作系统">
+			<param name="Local" value="VeraCrypt Hidden Operating System.html">
+			</OBJECT>
+	</UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="主程序窗口">
+		<param name="Local" value="Main Program Window.html">
+		</OBJECT>
+	<UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="程序菜单">
+			<param name="Local" value="Program Menu.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="挂载卷">
+			<param name="Local" value="Mounting VeraCrypt Volumes.html">
+			</OBJECT>
+	</UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="正常卸载与强制卸载">
+		<param name="Local" value="Normal Unmount vs Force Unmount.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="避免使用第三方文件扩展名">
+		<param name="Local" value="Avoid Third-Party File Extensions.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="并行处理">
+		<param name="Local" value="Parallelization.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="流水线处理">
+		<param name="Local" value="Pipelining.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="硬件加速">
+		<param name="Local" value="Hardware Acceleration.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="热键">
+		<param name="Local" value="Hot Keys.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="密钥文件">
+		<param name="Local" value="Keyfiles in VeraCrypt.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="安全令牌和智能卡">
+		<param name="Local" value="Security Tokens & Smart Cards.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="便携模式">
+		<param name="Local" value="Portable Mode.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="TrueCrypt支持">
+		<param name="Local" value="TrueCrypt Support.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="转换TrueCrypt卷和分区">
+		<param name="Local" value="Converting TrueCrypt volumes and partitions.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="1.26及更高版本转换指南">
+		<param name="Local" value="Conversion_Guide_VeraCrypt_1.26_and_Later.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="默认挂载参数">
+		<param name="Local" value="Default Mount Parameters.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="语言包">
+		<param name="Local" value="Language Packs.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="加密算法">
+		<param name="Local" value="Encryption Algorithms.html">
+		</OBJECT>
+	<UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="AES">
+			<param name="Local" value="AES.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Camellia">
+			<param name="Local" value="Camellia.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Kuznyechik">
+			<param name="Local" value="Kuznyechik.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Serpent">
+			<param name="Local" value="Serpent.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Twofish">
+			<param name="Local" value="Twofish.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="密码级联">
+			<param name="Local" value="Cascades.html">
+			</OBJECT>
+	</UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="哈希算法">
+		<param name="Local" value="Hash Algorithms.html">
+		</OBJECT>
+	<UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="BLAKE2s-256">
+			<param name="Local" value="BLAKE2s-256.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="SHA-256">
+			<param name="Local" value="SHA-256.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="SHA-512">
+			<param name="Local" value="SHA-512.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Whirlpool">
+			<param name="Local" value="Whirlpool.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Streebog">
+			<param name="Local" value="Streebog.html">
+			</OBJECT>
+	</UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="支持的操作系统">
+		<param name="Local" value="Supported Operating Systems.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="命令行用法">
+		<param name="Local" value="Command Line Usage.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="安全模型">
+		<param name="Local" value="Security Model.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="安全要求和注意事项">
+		<param name="Local" value="Security Requirements and Precautions.html">
+		</OBJECT>
+	<UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="数据泄露">
+			<param name="Local" value="Data Leaks.html">
+			</OBJECT>
+		<UL>
+			<LI> <OBJECT type="text/sitemap">
+				<param name="Name" value="分页文件">
+				<param name="Local" value="Paging File.html">
+				</OBJECT>
+			<LI> <OBJECT type="text/sitemap">
+				<param name="Name" value="内存转储文件">
+				<param name="Local" value="Memory Dump Files.html">
+				</OBJECT>
+			<LI> <OBJECT type="text/sitemap">
+				<param name="Name" value="休眠文件">
+				<param name="Local" value="Hibernation File.html">
+				</OBJECT>
+		</UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="RAM中的未加密数据">
+			<param name="Local" value="Unencrypted Data in RAM.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="VeraCrypt RAM加密">
+			<param name="Local" value="VeraCrypt RAM Encryption.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="VeraCrypt内存保护">
+			<param name="Local" value="VeraCrypt Memory Protection.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="物理安全">
+			<param name="Local" value="Physical Security.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="恶意软件">
+			<param name="Local" value="Malware.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="多用户环境">
+			<param name="Local" value="Multi-User Environment.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="真实性和完整性">
+			<param name="Local" value="Authenticity and Integrity.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="选择密码和密钥文件">
+			<param name="Local" value="Choosing Passwords and Keyfiles.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="更改密码和密钥文件">
+			<param name="Local" value="Changing Passwords and Keyfiles.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="Trim操作">
+			<param name="Local" value="Trim Operation.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="磨损均衡">
+			<param name="Local" value="Wear-Leveling.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="重新分配扇区">
+			<param name="Local" value="Reallocated Sectors.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="碎片整理">
+			<param name="Local" value="Defragmenting.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="日志文件系统">
+			<param name="Local" value="Journaling File Systems.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="卷克隆">
+			<param name="Local" value="Volume Clones.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="附加安全要求和注意事项">
+			<param name="Local" value="Additional Security Requirements and Precautions.html">
+			</OBJECT>
+	</UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="如何安全备份">
+		<param name="Local" value="How to Back Up Securely.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="杂项">
+		<param name="Local" value="Miscellaneous.html">
+		</OBJECT>
+	<UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="无需管理员权限使用VeraCrypt">
+			<param name="Local" value="Using VeraCrypt Without Administrator Privileges.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="网络共享">
+			<param name="Local" value="Sharing over Network.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="VeraCrypt后台任务">
+			<param name="Local" value="VeraCrypt Background Task.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="作为可移动介质挂载的卷">
+			<param name="Local" value="Removable Medium Volume.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="VeraCrypt系统文件和应用数据">
+			<param name="Local" value="VeraCrypt System Files.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="如何移除加密">
+			<param name="Local" value="Removing Encryption.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="卸载VeraCrypt">
+			<param name="Local" value="Uninstalling VeraCrypt.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="数字签名">
+			<param name="Local" value="Digital Signatures.html">
+			</OBJECT>
+	</UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="故障排除">
+		<param name="Local" value="Troubleshooting.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="不兼容问题">
+		<param name="Local" value="Incompatibilities.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="已知问题和限制">
+		<param name="Local" value="Issues and Limitations.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="常见问题解答">
+		<param name="Local" value="FAQ.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="技术细节">
+		<param name="Local" value="Technical Details.html">
+		</OBJECT>
+	<UL>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="符号表示">
+			<param name="Local" value="Notation.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="加密方案">
+			<param name="Local" value="Encryption Scheme.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="操作模式">
+			<param name="Local" value="Modes of Operation.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="头部密钥派生、盐和迭代次数">
+			<param name="Local" value="Header Key Derivation.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="随机数生成器">
+			<param name="Local" value="Random Number Generator.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="密钥文件">
+			<param name="Local" value="Keyfiles.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="PIM（个人迭代乘数）">
+			<param name="Local" value="Personal Iterations Multiplier (PIM).html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="VeraCrypt卷格式规范">
+			<param name="Local" value="VeraCrypt Volume Format Specification.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="标准合规性">
+			<param name="Local" value="Standard Compliance.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="源代码">
+			<param name="Local" value="Source Code.html">
+			</OBJECT>
+		<LI> <OBJECT type="text/sitemap">
+			<param name="Name" value="从源代码构建VeraCrypt">
+			<param name="Local" value="CompilingGuidelines.html">
+			</OBJECT>
+		<UL>
+			<LI> <OBJECT type="text/sitemap">
+				<param name="Name" value="Windows构建指南">
+				<param name="Local" value="CompilingGuidelineWin.html">
+				</OBJECT>
+			<LI> <OBJECT type="text/sitemap">
+				<param name="Name" value="Linux构建指南">
+				<param name="Local" value="CompilingGuidelineLinux.html">
+				</OBJECT>
+		</UL>
+	</UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="联系我们">
+		<param name="Local" value="Contact.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="法律信息">
+		<param name="Local" value="Legal Information.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="版本历史">
+		<param name="Local" value="Release Notes.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="致谢">
+		<param name="Local" value="Acknowledgements.html">
+		</OBJECT>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="参考文献">
+		<param name="Local" value="References.html">
+		</OBJECT>
+</UL>
+</BODY></HTML>

doc/chm/zh-cn/VeraCrypt.zh-cn.hhk

@@ -0,0 +1,13 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
+<HTML>
+<HEAD>
+<meta name="GENERATOR" content="Microsoft&reg; HTML Help Workshop 4.1">
+<!-- Sitemap 1.0 -->
+</HEAD><BODY>
+<UL>
+	<LI> <OBJECT type="text/sitemap">
+		<param name="Name" value="Ŀ¼±í">
+		<param name="Local" value="Documentation.html">
+		</OBJECT>
+</UL>
+</BODY></HTML>

doc/chm/zh-cn/VeraCrypt.zh-cn.hhp

@@ -0,0 +1,181 @@
+[OPTIONS]
+Compatibility=1.1 or later
+Compiled file=VeraCrypt User Guide.zh-cn.chm
+Contents file=VeraCrypt.zh-cn.hhc
+Default Font=微软雅黑,9,0
+Default topic=Documentation.html
+Display compile progress=No
+Full-text search=Yes
+Index file=VeraCrypt.zh-cn.hhk
+Language=0x804 中文(简体，中国)
+Title=VeraCrypt用户指南
+
+
+[FILES]
+Acknowledgements.html
+Additional Security Requirements and Precautions.html
+AES.html
+arrow_right.gif
+Authenticity and Integrity.html
+Authors.html
+Avoid Third-Party File Extensions.html
+BC_Logo_30x30.png
+BCH_Logo_30x30.png
+Beginner's Tutorial.html
+Beginner's Tutorial_Image_001.jpg
+Beginner's Tutorial_Image_002.jpg
+Beginner's Tutorial_Image_003.jpg
+Beginner's Tutorial_Image_004.jpg
+Beginner's Tutorial_Image_005.jpg
+Beginner's Tutorial_Image_007.jpg
+Beginner's Tutorial_Image_008.jpg
+Beginner's Tutorial_Image_009.jpg
+Beginner's Tutorial_Image_010.jpg
+Beginner's Tutorial_Image_011.jpg
+Beginner's Tutorial_Image_012.jpg
+Beginner's Tutorial_Image_013.jpg
+Beginner's Tutorial_Image_014.jpg
+Beginner's Tutorial_Image_015.jpg
+Beginner's Tutorial_Image_016.jpg
+Beginner's Tutorial_Image_017.jpg
+Beginner's Tutorial_Image_018.jpg
+Beginner's Tutorial_Image_019.jpg
+Beginner's Tutorial_Image_020.jpg
+Beginner's Tutorial_Image_021.jpg
+Beginner's Tutorial_Image_022.jpg
+Beginner's Tutorial_Image_023.gif
+Beginner's Tutorial_Image_024.gif
+Beginner's Tutorial_Image_034.png
+BLAKE2s-256.html
+Camellia.html
+Cascades.html
+Changing Passwords and Keyfiles.html
+Choosing Passwords and Keyfiles.html
+Command Line Usage.html
+CompilingGuidelineLinux.html
+CompilingGuidelines.html
+CompilingGuidelineWin.html
+Contact.html
+Contributed Resources.html
+Conversion_Guide_VeraCrypt_1.26_and_Later.html
+Converting TrueCrypt volumes and partitions.html
+Converting TrueCrypt volumes and partitions_truecrypt_convertion.jpg
+Creating New Volumes.html
+Data Leaks.html
+Default Mount Parameters.html
+Default Mount Parameters_VeraCrypt_password_using_default_parameters.png
+Defragmenting.html
+Digital Signatures.html
+Disclaimers.html
+Documentation.html
+Encryption Algorithms.html
+Encryption Scheme.html
+FAQ.html
+Favorite Volumes.html
+flattr-badge-large.png
+gf2_mul.gif
+Hardware Acceleration.html
+Hash Algorithms.html
+Header Key Derivation.html
+Hibernation File.html
+Hidden Operating System.html
+Hidden Volume.html
+Home_facebook_veracrypt.png
+Home_reddit.png
+Home_utilities-file-archiver-3.png
+Home_VeraCrypt_Default_Mount_Parameters.png
+Home_VeraCrypt_menu_Default_Mount_Parameters.png
+Hot Keys.html
+How to Back Up Securely.html
+Incompatibilities.html
+Introduction.html
+Issues and Limitations.html
+Journaling File Systems.html
+Keyfiles in VeraCrypt.html
+Keyfiles in VeraCrypt_Image_040.gif
+Keyfiles.html
+Kuznyechik.html
+Language Packs.html
+Legal Information.html
+liberapay_donate.svg
+LTC_Logo_30x30.png
+Main Program Window.html
+Malware.html
+mastodon_veracrypt.PNG
+Memory Dump Files.html
+Miscellaneous.html
+Modes of Operation.html
+Monero_Logo_30x30.png
+Mounting VeraCrypt Volumes.html
+Multi-User Environment.html
+Notation.html
+Paging File.html
+Parallelization.html
+paypal_30x30.png
+Personal Iterations Multiplier (PIM).html
+Personal Iterations Multiplier (PIM)_VeraCrypt_ChangePIM_Step1.png
+Personal Iterations Multiplier (PIM)_VeraCrypt_ChangePIM_Step2.png
+Personal Iterations Multiplier (PIM)_VeraCrypt_ChangePIM_System_Step1.png
+Personal Iterations Multiplier (PIM)_VeraCrypt_ChangePIM_System_Step2.png
+Personal Iterations Multiplier (PIM)_VeraCrypt_UsePIM_Step1.png
+Personal Iterations Multiplier (PIM)_VeraCrypt_UsePIM_Step2.png
+Physical Security.html
+Pipelining.html
+Plausible Deniability.html
+Portable Mode.html
+Preface.html
+Program Menu.html
+Protection of Hidden Volumes.html
+Protection of Hidden Volumes_Image_027.jpg
+Protection of Hidden Volumes_Image_028.jpg
+Protection of Hidden Volumes_Image_029.jpg
+Protection of Hidden Volumes_Image_030.jpg
+Protection of Hidden Volumes_Image_031.jpg
+Random Number Generator.html
+Reallocated Sectors.html
+References.html
+Release Notes.html
+Removable Medium Volume.html
+Removing Encryption.html
+Security Model.html
+Security Requirements and Precautions.html
+Security Requirements for Hidden Volumes.html
+Security Tokens & Smart Cards.html
+Serpent.html
+SHA-256.html
+SHA-512.html
+Sharing over Network.html
+Source Code.html
+Standard Compliance.html
+Streebog.html
+styles.css
+Supported Operating Systems.html
+Supported Systems for System Encryption.html
+System Encryption.html
+System Favorite Volumes.html
+Technical Details.html
+Trim Operation.html
+Troubleshooting.html
+TrueCrypt Support.html
+TrueCrypt Support_truecrypt_mode_gui.jpg
+twitter_veracrypt.PNG
+Twofish.html
+Unencrypted Data in RAM.html
+Uninstalling VeraCrypt.html
+Using VeraCrypt Without Administrator Privileges.html
+VeraCrypt Background Task.html
+VeraCrypt Hidden Operating System.html
+VeraCrypt License.html
+VeraCrypt Memory Protection.html
+VeraCrypt RAM Encryption.html
+VeraCrypt Rescue Disk.html
+VeraCrypt System Files.html
+VeraCrypt Volume Format Specification.html
+VeraCrypt Volume.html
+VeraCrypt128x128.png
+Volume Clones.html
+Wear-Leveling.html
+Whirlpool.html
+
+[INFOTYPES]
+

doc/html/Donation_Bank.html

@@ -1,117 +0,0 @@
-<!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">
-<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/">Source Code</a></li>
-	  <li><a href="Downloads.html">Downloads</a></li>
-	  <li><a href="Documentation.html">Documentation</a></li>
-	  <li><a class="active" href="Donation.html">Donate</a></li>
-	  <li><a href="https://sourceforge.net/p/veracrypt/discussion/" target="_blank">Forums</a></li>
-	</ul>
-</div>
-
-<div class="wikidoc">
-<h1>Donation to VeraCrypt using bank transfer</h1>
-<p>You can support VeraCrypt development through donations using bank transfers to one of IDRIX bank accounts below, depending on the currency used.<br>
-The supported currencies are <a href="#Euro">Euro<img src="flag-eu-small.png" style="vertical-align: top; margin-left: 5px"></a>, <a href="#USD">US Dollar<img src="flag-us-small.png" style="vertical-align: top; margin-left: 5px"></a>, <a href="#GBP">British Pound<img src="flag-gb-small.png" style="vertical-align: top; margin-left: 5px"></a>, <a href="#AUD">Australian Dollar<img src="flag-au-small.png" style="vertical-align: top; margin-left: 5px"></a> and <a href="#NZD">New Zealand Dollar<img src="flag-nz-small.png" style="vertical-align: top; margin-left: 5px"></a>.<br>
-Please <a href="Contact.html" target="_blank.html">contact us</a> if you need an official invoice for your donation.</p>
-<hr>
-<h3 id="Euro"><img src="flag-eu.png" style="vertical-align: middle; margin-right: 5px">Euro SEPA Bank Details</h3>
-<p>Accepted payment types are SEPA bank transferts or SWIFT in Euro only.</p>
-Account Holder: IDRIX SARL<br>
-IBAN: BE16 9670 3707 4574<br>
-Bank code (SWIFT / BIC): TRWIBEB1XXX<br>
-Address: TransferWise Europe SA, Avenue Marnix 13-17, Brussels 1000, Belgium<br>
-Reference: Open Source Donation<br>
-<hr>
-
-<h3 id="USD"><img src="flag-us.png" style="vertical-align: middle; margin-right: 5px">US Dollar Bank Details</h3>
-<p>From within the US, accepted payment types are ACH and Wire.</p>
-Account Holder: IDRIX SARL<br>
-Account number: 8310085792<br>
-ACH and Wire routing number: 026073150<br>
-Account Type: Checking<br>
-Address: Wise, 30 W. 26th Street, Sixth Floor, New York NY 10010, United States<br>
-Reference: Open Source Donation<br>
-
-<p>From outside the US, accepted payment in SWIFT.</p>
-Account Holder: IDRIX SARL<br>
-Account number: 8310085792<br>
-Routing number: 026073150<br>
-Bank code (SWIFT/BIC): CMFGUS33<br>
-Address: Wise, 30 W. 26th Street, Sixth Floor, New York NY 10010, United States<br>
-Reference: Open Source Donation<br>
-<hr>
-
-<h3 id="GBP"><img src="flag-gb.png" style="vertical-align: middle; margin-right: 5px">British Pound Bank Details</h3>
-<p>Accepted payment types are Faster Payments (FPS), BACS and CHAPS from withing the UK only.</p>
-
-Account Holder: IDRIX SARL<br>
-Account number: 56385007<br>
-UK Sort Code: 23-14-70<br>
-IBAN (to receive GBP from UK only): GB18 TRWI 2314 7056 3850 07<br>
-Address: Wise, 56 Shoreditch High Street, London, E1 6JJ, United Kingdom<br>
-Reference: Open Source Donation<br>
-<hr>
-
-<h3 id="AUD"><img src="flag-au.png" style="vertical-align: middle; margin-right: 5px">Australian Dollar Bank Details</h3>
-<p>Accepted payment types to this account are local AUD bank transfers only.</p>
-Account Holder: IDRIX SARL<br>
-Account number: 711714051<br>
-BSB Code: 802-985<br>
-Address: Wise, 36-38 Gipps Street, Collingwood VIC 3066, Autralia.<br>
-Reference: Open Source Donation<br>
-<hr>
-
-<h3 id="NZD"><img src="flag-nz.png" style="vertical-align: middle; margin-right: 5px">New Zealand Dollar Bank Details</h3>
-<p>Accepted payment types to this account are local NZD bank transfers only.</p>
-Account Holder: IDRIX SARL<br>
-Account number: 02-1291-0218919-000<br>
-Address: Wise, 56 Shoreditch High Street, London, E1 6JJ, United Kingdom<br>
-Reference: Open Source Donation<br>
-<hr>
-
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-</div><div class="ClearBoth"></div></body></html>

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>
@@ -17,7 +16,7 @@
 <div id="menu">
 	<ul>
 	  <li><a href="Home.html">Home</a></li>
-	  <li><a href="/code/">Source Code</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>
@@ -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>
@@ -17,7 +16,7 @@
 <div id="menu">
 	<ul>
 	  <li><a href="Home.html">Home</a></li>
-	  <li><a href="/code/">Source Code</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>

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>
@@ -17,7 +16,7 @@
 <div id="menu">
 	<ul>
 	  <li><a href="Home.html">Home</a></li>
-	  <li><a href="/code/">Source Code</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>

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>
@@ -17,7 +16,7 @@
 <div id="menu">
 	<ul>
 	  <li><a href="Home.html">Home</a></li>
-	  <li><a href="/code/">Source Code</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>

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>
@@ -17,7 +16,7 @@
 <div id="menu">
 	<ul>
 	  <li><a href="Home.html">Home</a></li>
-	  <li><a href="/code/">Source Code</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>
@@ -34,8 +33,8 @@
 
 <div class="wikidoc">
 <h2>Authors</h2>
-<p>Mounir IDRASSI (<a href="https://www.idrix.fr" target="_blank">IDRIX</a>, <a href="https://fr.linkedin.com/in/idrassi" target="_blank">
-https://fr.linkedin.com/in/idrassi</a>) is the creator and main developer of VeraCrypt. He managed all development and deployment aspects on all supported platforms (Windows,Linux and OSX).</p>
+<p>Mounir IDRASSI (<a href="https://amcrypto.jp" target="_blank">AM Crypto</a>, <a href="https://www.linkedin.com/in/idrassi" target="_blank">
+https://www.linkedin.com/in/idrassi</a>) is the creator and main developer of VeraCrypt. He managed all development and deployment aspects on all supported platforms (Windows,Linux and OSX).</p>
 <p>Alex Kolotnikov (<a href="https://ru.linkedin.com/in/alex-kolotnikov-6625568b" target="_blank">https://ru.linkedin.com/in/alex-kolotnikov-6625568b</a>) is the author of VeraCrypt EFI bootloader. He manages all aspects of EFI support and his strong expertise
  helps bring new exciting features to VeraCrypt Windows system encryption.</p>
 <p>&nbsp;</p>

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>
@@ -17,7 +16,7 @@
 <div id="menu">
 	<ul>
 	  <li><a href="Home.html">Home</a></li>
-	  <li><a href="/code/">Source Code</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>
@@ -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>
@@ -17,7 +16,7 @@
 <div id="menu">
 	<ul>
 	  <li><a href="Home.html">Home</a></li>
-	  <li><a href="/code/">Source Code</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>
@@ -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>
@@ -17,7 +16,7 @@
 <div id="menu">
 	<ul>
 	  <li><a href="Home.html">Home</a></li>
-	  <li><a href="/code/">Source Code</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>