Update translations

Translations/Language.cs.xml

@@ -295,7 +295,7 @@
     <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>
+    <entry lang="cs" key="IDT_EMV_OPTIONS">Možnosti EMV</entry>
     <entry lang="cs" key="IDT_TASKBAR_ICON">VeraCrypt služba na pozadí</entry>
     <entry lang="cs" key="IDT_TRAVELER_MOUNT">Svazek VeraCryptu, který chcete připojit (relativní ke kořenovému adresáři):</entry>
     <entry lang="cs" key="IDT_TRAVEL_INSERTION">Po připojení přenosného disku:</entry>
@@ -390,7 +390,7 @@
     <entry lang="cs" key="ADMINISTRATOR">Správce</entry>
     <entry lang="cs" key="ADMIN_PRIVILEGES_DRIVER">Pro nahrání ovladače VeraCrypt musíte být přihlášeni jako správce systému.</entry>
     <entry lang="cs" key="ADMIN_PRIVILEGES_WARN_DEVICES">Pro šifrování/formátování diskového oddílu/zařízení musíte být přihlášeni s oprávněním správce.\n\nTo se netýká svazků, které jsou vytvořeny ze souborů.</entry>
-    <entry lang="en" key="ADMIN_PRIVILEGES_WARN_MANAGE_VOLUME">Unable to activate fast file creation: Administrator privileges required.\nPlease relaunch the program as an Administrator to enable this feature.\n\nWould you like to proceed without fast file creation?</entry>
+    <entry lang="cs" key="ADMIN_PRIVILEGES_WARN_MANAGE_VOLUME">Nelze aktivovat rychlé vytvoření souboru: jsou vyžadována oprávnění správce.\nPro povolení této funkce spusťte program znovu jako správce.\n\nChcete pokračovat bez rychlého vytvoření souboru?</entry>
     <entry lang="cs" key="ADMIN_PRIVILEGES_WARN_HIDVOL">Pro vytvoření skrytého svazku musíte být přihlášeni s oprávněním správce.\n\nPokračovat?</entry>
     <entry lang="cs" key="ADMIN_PRIVILEGES_WARN_NTFS">Pro zformátování svazku systémem NTFS musíte být přihlášeni s oprávněním správce.\n\nBez oprávnění správce můžete svazek zformátovat systémem souborů FAT.</entry>
     <entry lang="cs" key="AES_HELP">Šifra povolená FIPS (Rijndael, zveřejněno v roce 1998) kterou mohou používat úřady a agentury vlády Spojených států k ochraně utajovaných informací až k úrovni přísně tajné. 256-bitový klíč, 128-bitové  bloky, 14 iterací (AES-256). Operační režim je XTS.</entry>
@@ -940,7 +940,7 @@
     <entry lang="cs" key="ENTER_HEADER_BACKUP_PASSWORD">Zadejte heslo pro hlavičku uloženou v záložním souboru</entry>
     <entry lang="cs" key="KEYFILE_CREATED">Souborový klíč byl úspěšně vytvořen.</entry>
     <entry lang="cs" key="KEYFILE_INCORRECT_NUMBER">Počet poskytnutých souborových klíčů je neplatný.</entry>
-    <entry lang="en" key="KEYFILE_INCORRECT_SIZE">The keyfile size must be at least 64 bytes.</entry>
+    <entry lang="cs" key="KEYFILE_INCORRECT_SIZE">Velikost souborového klíče musí být alespoň 64 bajtů.</entry>
     <entry lang="cs" key="KEYFILE_EMPTY_BASE_NAME">Prosím, zadejte název pro vygenerovaný souborový klíč</entry>
     <entry lang="cs" key="KEYFILE_INVALID_BASE_NAME">Základní název souborového klíče je neplatný</entry>
     <entry lang="cs" key="KEYFILE_ALREADY_EXISTS">Souborový klíč '%s' již existuje.\nPřejete si ho přepsat? Jeho vygenerování bude zastaveno, odpovíte-li „Ne”.</entry>
@@ -1519,7 +1519,7 @@
     <entry lang="cs" key="LINUX_NOT_FAT_HINT">Upozorňujeme, že svazek nebude naformátován systémem souborů FAT, a proto může být nutné na jiných platformách než {0} nainstalovat další ovladače souborového systému, jenž umožní připojení svazku.</entry>
     <entry lang="cs" key="LINUX_KERNEL_OLD">Váš systém používá starou verzi linuxového jádra.\n\nV důsledku chyby v linuxovém jádře může systém přestat reagovat při zápisu dat na svazek VeraCryptu. Tento problém lze vyřešit aktualizací jádra na verzi 2.6.24 nebo novější.</entry>
     <entry lang="cs" key="LINUX_VOL_UNMOUNTED">Svazek {0} byl odpojen.</entry>
-    <entry lang="en" key="LINUX_VOL_MOUNTED">Volume {0} has been mounted.</entry>
+    <entry lang="cs" key="LINUX_VOL_MOUNTED">Svazek {0} byl připojen.</entry>
     <entry lang="cs" key="LINUX_OOM">Nedostatek paměti.</entry>
     <entry lang="cs" key="LINUX_CANT_GET_ADMIN_PRIV">Nepodařilo se získat oprávnění správce systému</entry>
     <entry lang="cs" key="LINUX_COMMAND_GET_ERROR">Příkaz {0} vrátil chybu {1}.</entry>
@@ -1643,47 +1643,47 @@
     <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>
+    <entry lang="cs" key="IDT_KDF_ALGO">Algoritmus KDF</entry>
+    <entry lang="cs" key="IDD_PREFERENCES_TAB_GENERAL">Obecné</entry>
+    <entry lang="cs" key="IDD_PREFERENCES_TAB_ACTIONS">Akce</entry>
+    <entry lang="cs" key="IDD_PREFERENCES_TAB_PASSWORD">Heslo</entry>
+    <entry lang="cs" key="IDC_SECURE_DESKTOP_ENABLE_IME">Povolit editor vstupní metody (IME) na zabezpečené ploše</entry>
+    <entry lang="cs" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">UPOZORNĚNÍ: tuto možnost povolte pouze v případě, že máte potíže při výběru souborových klíčů/tokenů na zabezpečené ploše.</entry>
+    <entry lang="cs" key="ERR_KEY_DERIVATION_FAILED">Odvození klíče se nezdařilo. Příčinou může být nedostatek paměti nebo přerušená operace.</entry>
+    <entry lang="cs" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">Systémový diskový oddíl/disk je již dešifrován, ale cesta k zavaděči EFI od Microsoftu nebyla obnovena do Správce zavaděče Windows. Je třeba opravit pouze spouštěcí soubory EFI. Použijte možnost opravy záchranného disku VeraCryptu, nebo spusťte médium pro obnovení Windows a spusťte příkaz 'bcdboot W:\\Windows /s S: /f UEFI' poté, co nahradíte W: písmenem jednotky svazku Windows a S: písmenem jednotky systémového diskového oddílu EFI. Cesta:</entry>
+    <entry lang="cs" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">Systémový diskový oddíl/disk je již dešifrován, ale náhradní cesta zavaděče EFI stále obsahuje zavaděč VeraCryptu. Je třeba opravit pouze spouštěcí soubory EFI. Použijte možnost opravy záchranného disku VeraCryptu, nebo spusťte médium pro obnovení Windows a spusťte příkaz 'bcdboot W:\\Windows /s S: /f UEFI' poté, co nahradíte W: písmenem jednotky svazku Windows a S: písmenem jednotky systémového diskového oddílu EFI. Cesta:</entry>
+    <entry lang="cs" key="IDM_REPAIR_EFI_BOOT_LOADER">Opravit zavaděč EFI...</entry>
+    <entry lang="cs" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt obnoví cesty zavaděče EFI systému Windows a odstraní položky a soubory zavaděče EFI VeraCryptu.\n\nPoužijte tuto možnost pouze poté, co je systémový diskový oddíl/disk plně dešifrován a Windows lze spustit bez šifrování systému.\n\nChcete pokračovat?</entry>
+    <entry lang="cs" key="EFI_BOOT_LOADER_FILE_READ_FAILED">Soubor zavaděče EFI nebylo možné načíst úplně:</entry>
+    <entry lang="cs" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">Soubor zavaděče EFI je neočekávaně velký a nebyl zkontrolován:</entry>
+    <entry lang="cs" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">Systémový diskový oddíl/disk je již dešifrován a soubory zavaděče EFI byly obnoveny, ale VeraCrypt nemohl odstranit jednu nebo více položek zavaděče VeraCryptu ve firmwaru. Soubory EFI VeraCryptu byly ponechány na místě, aby zbývající položky firmwaru stále odkazovaly na existující zavaděč. Zkuste to znovu jako správce nebo odstraňte položku zavaděče VeraCryptu z nastavení firmwaru poté, co ověříte, že se Správce zavaděče Windows spouští normálně.</entry>
+    <entry lang="cs" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">Zavaděč EFI nelze opravit, dokud je šifrování nebo dešifrování systému aktivní či nedokončené. Dokončete nebo obnovte čekající proces šifrování/dešifrování systému a zkuste to znovu.</entry>
+    <entry lang="cs" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">Tato oprava je dostupná pouze na systémech, které se spouštějí v režimu UEFI ze systémového diskového oddílu GPT.</entry>
+    <entry lang="cs" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">Zavaděč EFI byl úspěšně opraven.</entry>
+    <entry lang="cs" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) reguluje paměťovou a časovou náročnost použitou při odvození klíče hlavičky pomocí Argon2id následovně:\n      Paměť = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterace = 3 + ((PIM - 1) / 3) pro PIM 31 nebo nižší, poté 13 + (PIM - 31)\n\nZanecháte-li prázdné, nebo nastavíte 0, VeraCrypt použije výchozí Argon2 PIM (12), který používá 416 MiB paměti a 6 iterací.\n\nJe-li heslo kratší než 20 znaků, Argon2 PIM nesmí být menší než 12, aby byla zachována alespoň minimální úroveň zabezpečení.\nMá-li heslo minimálně 20 znaků, Argon2 PIM může obsahovat jakoukoliv hodnotu.\n\nHodnota Argon2 PIM větší než 12 zvyšuje využití paměti až na 1024 MiB a poté zvyšuje počet iterací. To povede k pomalejšímu připojení. Malá hodnota Argon2 PIM (menší než 12) povede k rychlejšímu připojení, ale může snížit zabezpečení, není-li heslo dostatečně silné.</entry>
+    <entry lang="cs" key="PIM_ARGON2_LARGE_WARNING">Byla vybrána hodnota Argon2 PIM, která je větší než výchozí hodnota VeraCryptu.\nUvědomte si, že to může vyžadovat více paměti a vést k výrazně pomalejšímu připojení.</entry>
+    <entry lang="cs" key="PIM_ARGON2_SMALL_WARNING">Byla vybrána hodnota Argon2 PIM, která je menší než výchozí hodnota VeraCryptu. Uvědomte si, že není-li vaše heslo dostatečně silné, může to vést ke slabšímu zabezpečení.\n\nPotvrzujete, že používáte silné heslo?</entry>
+    <entry lang="cs" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Heslo musí obsahovat 20 nebo více znaků, aby bylo možné použít zadaný Argon2 PIM.\nKratší hesla lze použít pouze v případě, že Argon2 PIM je 12 nebo vyšší.</entry>
+    <entry lang="cs" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER">Připojovat svazky NTFS pomocí ovladače v linuxovém jádře</entry>
+    <entry lang="cs" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Pouze Linux. Je-li tato možnost povolena a nebyl zadán explicitní typ systému souborů, VeraCrypt prověří dešifrované virtuální zařízení pomocí blkid -p a připojí zjištěné systémy souborů NTFS pomocí dostupného ovladače NTFS v jádře, přičemž obejde pomocné nástroje pro připojení, jako je ntfs-3g. VeraCrypt použije ntfs, pokud je jednoznačně rozpoznán jako moderní ovladač pro čtení/zápis nebo očekáván v Linuxu 7.1 či novějším, jinak použije ntfs3. Pokud zjištění NTFS selže, VeraCrypt použije běžný automatický výběr systému souborů. Není-li podporovaný ovladač NTFS v jádře dostupný nebo ho nelze načíst, připojení selže. Tato volitelná možnost může zabránit zaseknutí při uspání nebo hibernaci způsobenému zamrzlými systémy souborů FUSE v uživatelském prostoru.</entry>
+    <entry lang="cs" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">Není dostupný žádný podporovaný ovladač NTFS v jádře nebo jej nelze načíst. Chcete-li použít výchozí systémovou podporu NTFS, zakažte nastavení ovladače NTFS v jádře nebo nepožadujte NTFS v jádře explicitně.</entry>
+    <entry lang="cs" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Běžné odpojení svazku {0} selhalo. To se může stát, pokud aplikace mají na svazku stále otevřené soubory nebo adresáře, nebo pokud bylo hostitelské zařízení odpojeno a připojení je neplatné.\n\nJe-li zařízení stále připojeno, vyberte „Ne”, zavřete aplikace používající svazek a zkuste svazek odpojit znovu.\n\nBylo-li zařízení odpojeno nebo je připojení neplatné, VeraCrypt se může pokusit o nouzové vyčištění odpojením systému souborů metodou lazy a odstraněním objektů VeraCryptu v jádře nebo naplánováním jejich odstranění. Čekající zápisy mohly selhat, data mohla být ztracena a čištění může zůstat nedokončené, dokud aplikace nezavřou otevřené soubory. Před dalším použitím zkontrolujte systém souborů pomocí fsck nebo příslušného opravného nástroje.\n\nPokračovat?</entry>
+    <entry lang="cs" key="LINUX_EMERGENCY_UNMOUNTED">Bylo zahájeno nouzové vyčištění svazku {0}. Pokud bylo zařízení odpojeno, připojení bylo neplatné nebo existovaly čekající zápisy, před dalším použitím zkontrolujte systém souborů pomocí fsck nebo příslušného opravného nástroje.</entry>
+    <entry lang="cs" key="FORMAT_STAGE_WRITING_DATA">Vytváření dat svazku. Čekejte prosím.</entry>
+    <entry lang="cs" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Dokončování vytváření svazku: zápis záložní hlavičky.</entry>
+    <entry lang="cs" key="FORMAT_STAGE_FLUSHING_DATA">Dokončování vytváření svazku: zápis dat na disk. U velkých svazků nebo pomalých/USB úložišť to může trvat několik minut.</entry>
+    <entry lang="cs" key="FORMAT_STAGE_FINISHED">Dokončování vytváření svazku.</entry>
+    <entry lang="cs" key="FORMAT_STAGE_ABORTED">Vytváření svazku bylo přerušeno.</entry>
+    <entry lang="cs" key="FORMAT_STAGE_ERROR">Vytváření svazku selhalo.</entry>
+    <entry lang="cs" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Dokončování vytváření svazku: připojení dočasného svazku.</entry>
+    <entry lang="cs" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Dokončování vytváření svazku: příprava dočasného zařízení.</entry>
+    <entry lang="cs" key="FORMAT_STAGE_CREATING_FILESYSTEM">Dokončování vytváření svazku: vytváření systému souborů pomocí {0}.</entry>
+    <entry lang="cs" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Dokončování vytváření svazku: odpojení dočasného svazku.</entry>
+    <entry lang="cs" key="MACOSX_APFS_SYNTHESIZED_DEVICE">Vybrané zařízení '{0}' je syntetizovaný kontejner nebo svazek APFS a nelze jej použít jako hostitele pro raw svazek VeraCryptu.\n\nMísto toho vyberte fyzický diskový oddíl úložiště APFS{1}.</entry>
+    <entry lang="cs" key="MACOSX_DEVICE_SYSTEM_PARTITION">Vybrané zařízení '{0}' je systémový/podpůrný diskový oddíl macOS a nelze jej použít jako hostitele svazku VeraCryptu.</entry>
+    <entry lang="cs" key="MACOSX_APFS_SYSTEM_STORE">Vybrané fyzické úložiště APFS '{0}' obsahuje aktuálně připojený systémový svazek macOS a nelze jej použít jako hostitele svazku VeraCryptu.</entry>
+    <entry lang="cs" key="MACOSX_DEVICE_NOT_WRITABLE">macOS hlásí vybrané zařízení '{0}' jako pouze pro čtení. Vyberte zapisovatelný fyzický diskový oddíl nebo disk.</entry>
+    <entry lang="cs" key="MACOSX_APFS_EROFS_HINT">macOS oznámil, že vybrané zařízení je pouze pro čtení. Jde-li o disk APFS, ujistěte se, že jste vybrali fyzický diskový oddíl úložiště APFS, nikoli syntetizovaný svazek APFS. Pomocí Diskové utility nebo příkazu 'diskutil list' určete fyzický diskový oddíl a zkuste to znovu.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.es.xml

@@ -1649,41 +1649,41 @@
     <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>
+    <entry lang="es" key="ERR_KEY_DERIVATION_FAILED">La derivación de clave ha fallado. Esto puede deberse a memoria insuficiente o a una operación interrumpida.</entry>
+    <entry lang="es" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">La partición/unidad del sistema ya está descifrada, pero la ruta del cargador de arranque EFI de Microsoft no se restauró en el Administrador de arranque de Windows. Sólo es necesario reparar los archivos de arranque EFI. Use la opción de reparación del Disco de Rescate de VeraCrypt, o arranque un medio de recuperación de Windows y ejecute 'bcdboot W:\\Windows /s S: /f UEFI' después de reemplazar W: por la letra de unidad del volumen de Windows y S: por la letra de unidad de la partición del sistema EFI. Ruta:</entry>
+    <entry lang="es" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">La partición/unidad del sistema ya está descifrada, pero la ruta alternativa del cargador de arranque EFI todavía contiene el Cargador de Arranque de VeraCrypt. Sólo es necesario reparar los archivos de arranque EFI. Use la opción de reparación del Disco de Rescate de VeraCrypt, o arranque un medio de recuperación de Windows y ejecute 'bcdboot W:\\Windows /s S: /f UEFI' después de reemplazar W: por la letra de unidad del volumen de Windows y S: por la letra de unidad de la partición del sistema EFI. Ruta:</entry>
+    <entry lang="es" key="IDM_REPAIR_EFI_BOOT_LOADER">Reparar Cargador de Arranque EFI...</entry>
+    <entry lang="es" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt restaurará las rutas del cargador de arranque EFI de Windows y eliminará las entradas y archivos de arranque EFI de VeraCrypt.\n\nUse esta opción sólo después de que la partición/unidad del sistema esté completamente descifrada y Windows pueda arrancar sin cifrado del sistema.\n\n¿Desea continuar?</entry>
+    <entry lang="es" key="EFI_BOOT_LOADER_FILE_READ_FAILED">El fichero del cargador de arranque EFI no pudo leerse por completo:</entry>
+    <entry lang="es" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">El fichero del cargador de arranque EFI es inesperadamente grande y no fue inspeccionado:</entry>
+    <entry lang="es" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">La partición/unidad del sistema ya está descifrada y los archivos del cargador de arranque EFI han sido restaurados, pero VeraCrypt no pudo eliminar una o más entradas de arranque VeraCrypt del firmware. Los archivos EFI de VeraCrypt se dejaron en su lugar para que cualquier entrada de firmware restante siga apuntando a un cargador existente. Reinténtelo como administrador o elimine la entrada de arranque de VeraCrypt desde la configuración del firmware después de confirmar que el Administrador de arranque de Windows se inicia normalmente.</entry>
+    <entry lang="es" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">El cargador de arranque EFI no puede repararse mientras el cifrado o descifrado del sistema esté activo o incompleto. Complete o reanude el proceso pendiente de cifrado/descifrado del sistema antes de reintentarlo.</entry>
+    <entry lang="es" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">Esta acción de reparación sólo está disponible en sistemas que arrancan en modo UEFI desde una partición del sistema en un disco GPT.</entry>
+    <entry lang="es" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">El cargador de arranque EFI ha sido reparado con éxito.</entry>
+    <entry lang="es" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) controla los costes de memoria y tiempo usados por la derivación de la clave de cabecera Argon2id de la siguiente forma:\n      Memoria = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iteraciones = 3 + ((PIM - 1) / 3) para PIM 31 o inferior, y luego 13 + (PIM - 31)\n\nCuando se deja en blanco o se pone a 0, VeraCrypt usará el PIM Argon2 predeterminado (12), que utiliza 416 MiB de memoria y 6 iteraciones.\n\nCuando la contraseña es de menos de 20 caracteres, el PIM Argon2 no puede ser inferior a 12 con el fin de mantener un nivel de seguridad mínimo.\nCuando la contraseña es de 20 ó más caracteres, se puede usar cualquier valor de PIM Argon2.\n\nUn PIM Argon2 superior a 12 incrementa el uso de memoria hasta 1024 MiB y luego incrementa las iteraciones. Esto conllevará un proceso de montaje más lento. Un PIM Argon2 pequeño (menor de 12) conllevará un proceso de montaje más rápido, pero podría reducir la seguridad si la contraseña no es suficientemente fuerte.</entry>
+    <entry lang="es" key="PIM_ARGON2_LARGE_WARNING">Ha elegido un valor de PIM Argon2 superior al valor por defecto de VeraCrypt.\nPor favor, sea consciente que esto puede requerir más memoria y conllevar un montaje mucho más lento.</entry>
+    <entry lang="es" key="PIM_ARGON2_SMALL_WARNING">Ha elegido un valor de PIM Argon2 inferior al valor por defecto de VeraCrypt. Por favor, sea consciente que si su contraseña no es lo suficientemente fuerte, podría ver reducido el nivel de seguridad.\n\n¿Está seguro que usa una contraseña fuerte?</entry>
+    <entry lang="es" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">La contraseña debe contener 20 caracteres o más para usar el PIM Argon2 especificado.\nSólo se pueden usar contraseñas de menor longitud si el PIM Argon2 es 12 ó más.</entry>
+    <entry lang="es" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER">Montar volúmenes NTFS con un controlador integrado en el kernel de Linux</entry>
+    <entry lang="es" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Sólo Linux. Cuando está habilitado y no se ha suministrado ningún tipo explícito de sistema de archivos, VeraCrypt sondea el dispositivo virtual descifrado con blkid -p y monta los sistemas de archivos NTFS detectados con un controlador NTFS integrado en el kernel disponible, evitando herramientas auxiliares de montaje como ntfs-3g. VeraCrypt usa ntfs cuando se identifica positivamente como un controlador moderno de lectura/escritura o esperado en Linux 7.1 o posterior, y en caso contrario usa ntfs3. Si la detección de NTFS falla, VeraCrypt usa la selección automática normal del sistema de archivos. Si no hay ningún controlador NTFS integrado en el kernel soportado disponible o cargable, el montaje falla. Esta opción, que debe activarse explícitamente, puede evitar bloqueos de suspensión o hibernación causados por sistemas de archivos FUSE de espacio de usuario congelados.</entry>
+    <entry lang="es" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">No hay disponible ni se puede cargar ningún controlador NTFS integrado en el kernel que esté soportado. Para usar el soporte NTFS predeterminado del sistema, desactive la preferencia del controlador NTFS del kernel o no solicite NTFS del kernel explícitamente.</entry>
+    <entry lang="es" key="LINUX_EMERGENCY_UNMOUNT_WARNING">El desmontaje normal del volumen {0} falló. Esto puede ocurrir cuando todavía hay aplicaciones con archivos o directorios abiertos en el volumen, o cuando el dispositivo subyacente fue desconectado y el montaje quedó obsoleto.\n\nSi el dispositivo sigue conectado, elija No, cierre las aplicaciones que estén usando el volumen e intente desmontarlo de nuevo.\n\nSi el dispositivo fue desconectado o el montaje quedó obsoleto, VeraCrypt puede intentar una limpieza de emergencia mediante el desmontaje diferido del sistema de archivos y eliminando o programando la eliminación de objetos del kernel de VeraCrypt. Las escrituras pendientes pueden haber fallado, pueden haberse perdido datos y la limpieza puede permanecer pendiente hasta que las aplicaciones cierren los archivos abiertos. Compruebe el sistema de archivos con fsck o con la herramienta de reparación apropiada antes de usarlo de nuevo.\n\n¿Continuar?</entry>
+    <entry lang="es" key="LINUX_EMERGENCY_UNMOUNTED">Se ha iniciado la limpieza de emergencia del volumen {0}. Si el volumen fue desconectado, el montaje quedó obsoleto o había escrituras pendientes, compruebe el sistema de archivos con fsck o con la herramienta de reparación apropiada antes de usarlo de nuevo.</entry>
+    <entry lang="es" key="FORMAT_STAGE_WRITING_DATA">Creando datos del volumen. Por favor, espere.</entry>
+    <entry lang="es" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizando la creación del volumen: escribiendo la copia de seguridad de la cabecera.</entry>
+    <entry lang="es" key="FORMAT_STAGE_FLUSHING_DATA">Finalizando la creación del volumen: sincronizando los datos con el disco. Esto puede tardar varios minutos en volúmenes grandes o almacenamiento lento/USB.</entry>
+    <entry lang="es" key="FORMAT_STAGE_FINISHED">Finalizando la creación del volumen.</entry>
+    <entry lang="es" key="FORMAT_STAGE_ABORTED">La creación del volumen ha sido abortada.</entry>
+    <entry lang="es" key="FORMAT_STAGE_ERROR">La creación del volumen falló.</entry>
+    <entry lang="es" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizando la creación del volumen: montando el volumen temporal.</entry>
+    <entry lang="es" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizando la creación del volumen: preparando el dispositivo temporal.</entry>
+    <entry lang="es" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizando la creación del volumen: creando el sistema de archivos usando {0}.</entry>
+    <entry lang="es" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizando la creación del volumen: desmontando el volumen temporal.</entry>
+    <entry lang="es" key="MACOSX_APFS_SYNTHESIZED_DEVICE">El dispositivo seleccionado '{0}' es un contenedor o volumen APFS sintetizado y no puede usarse como dispositivo anfitrión sin procesar de un volumen VeraCrypt.\n\nSeleccione en su lugar la partición física de almacenamiento APFS{1}.</entry>
+    <entry lang="es" key="MACOSX_DEVICE_SYSTEM_PARTITION">El dispositivo seleccionado '{0}' es una partición de sistema o soporte de macOS y no puede usarse como host de volumen VeraCrypt.</entry>
+    <entry lang="es" key="MACOSX_APFS_SYSTEM_STORE">El almacenamiento físico APFS seleccionado '{0}' contiene el volumen de sistema macOS actualmente montado y no puede usarse como host de volumen VeraCrypt.</entry>
+    <entry lang="es" key="MACOSX_DEVICE_NOT_WRITABLE">macOS informa que el dispositivo seleccionado '{0}' es de sólo lectura. Seleccione una partición física o disco con permiso de escritura.</entry>
+    <entry lang="es" key="MACOSX_APFS_EROFS_HINT">macOS informó que el dispositivo seleccionado es de sólo lectura. Si se trata de un disco APFS, asegúrese de haber seleccionado la partición física de almacenamiento APFS, no un volumen APFS sintetizado. Use la Utilidad de Discos o 'diskutil list' para identificar la partición física y luego reinténtelo.</entry>
 </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.fi.xml

@@ -1643,47 +1643,47 @@
     <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>
+    <entry lang="fi" key="IDT_KDF_ALGO">KDF-algoritmi</entry>
+    <entry lang="fi" key="IDD_PREFERENCES_TAB_GENERAL">Yleiset</entry>
+    <entry lang="fi" key="IDD_PREFERENCES_TAB_ACTIONS">Toiminnot</entry>
+    <entry lang="fi" key="IDD_PREFERENCES_TAB_PASSWORD">Salasana</entry>
+    <entry lang="fi" key="IDC_SECURE_DESKTOP_ENABLE_IME">Ota syöttömenetelmäeditori (IME) käyttöön Secure Desktop -tilassa</entry>
+    <entry lang="fi" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">VAROITUS: Ota tämä asetus käyttöön vain, jos avaintiedostojen/turvallisuustunnisteiden valinnassa Secure Desktop -tilassa ilmenee ongelmia.</entry>
+    <entry lang="fi" key="ERR_KEY_DERIVATION_FAILED">Avaimen johtaminen epäonnistui. Tämä voi johtua riittämättömästä muistista tai keskeytyneestä toiminnosta.</entry>
+    <entry lang="fi" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">Järjestelmäosio/-asema on jo purettu salauksesta, mutta Microsoftin EFI-käynnistysohjelman polkua ei palautettu Windows Boot Manageriin. Vain EFI-käynnistystiedostot on korjattava. Käytä VeraCryptin pelastuslevyn korjaustoimintoa tai käynnistä Windowsin palautusvälineeltä ja suorita 'bcdboot W:\\Windows /s S: /f UEFI' sen jälkeen, kun olet korvannut W: Windows-taltion asemakirjaimella ja S: EFI-järjestelmäosion asemakirjaimella. Polku:</entry>
+    <entry lang="fi" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">Järjestelmäosio/-asema on jo purettu salauksesta, mutta EFI-varakäynnistysohjelman polku sisältää yhä VeraCryptin käynnistysohjelman. Vain EFI-käynnistystiedostot on korjattava. Käytä VeraCryptin pelastuslevyn korjaustoimintoa tai käynnistä Windowsin palautusvälineeltä ja suorita 'bcdboot W:\\Windows /s S: /f UEFI' sen jälkeen, kun olet korvannut W: Windows-taltion asemakirjaimella ja S: EFI-järjestelmäosion asemakirjaimella. Polku:</entry>
+    <entry lang="fi" key="IDM_REPAIR_EFI_BOOT_LOADER">Korjaa EFI-käynnistysohjelma...</entry>
+    <entry lang="fi" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt palauttaa Windowsin EFI-käynnistysohjelman polut ja poistaa VeraCryptin EFI-käynnistysmerkinnät ja -tiedostot.\n\nKäytä tätä vain sen jälkeen, kun järjestelmäosio/-asema on kokonaan purettu salauksesta ja Windows käynnistyy ilman järjestelmäsalausta.\n\nHaluatko jatkaa?</entry>
+    <entry lang="fi" key="EFI_BOOT_LOADER_FILE_READ_FAILED">EFI-käynnistysohjelman tiedostoa ei voitu lukea kokonaan:</entry>
+    <entry lang="fi" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">EFI-käynnistysohjelman tiedosto on odottamattoman suuri, eikä sitä tarkistettu:</entry>
+    <entry lang="fi" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">Järjestelmäosio/-asema on jo purettu salauksesta ja EFI-käynnistysohjelman tiedostot palautettiin, mutta VeraCrypt ei voinut poistaa yhtä tai useampaa laiteohjelmistossa olevaa VeraCrypt-käynnistysmerkintää. VeraCryptin EFI-tiedostot jätettiin paikalleen, jotta jäljellä olevat laiteohjelmiston merkinnät osoittavat yhä olemassa olevaan käynnistysohjelmaan. Yritä uudelleen järjestelmänvalvojana tai poista VeraCryptin käynnistysmerkintä laiteohjelmiston asetuksista varmistettuasi, että Windows Boot Manager käynnistyy normaalisti.</entry>
+    <entry lang="fi" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">EFI-käynnistysohjelmaa ei voi korjata, kun järjestelmän salaus tai salauksen purku on käynnissä tai keskeneräinen. Suorita tai jatka kesken oleva järjestelmän salaus-/salauksenpurkuprosessi loppuun ennen uudelleen yrittämistä.</entry>
+    <entry lang="fi" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">Tämä korjaustoiminto on käytettävissä vain järjestelmissä, jotka käynnistyvät UEFI-tilassa GPT-järjestelmäosiolta.</entry>
+    <entry lang="fi" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">EFI-käynnistysohjelma on korjattu onnistuneesti.</entry>
+    <entry lang="fi" key="PIM_ARGON2_HELP">PIM (henkilökohtainen iteraatiokerroin) säätää Argon2id-otsikkoavaimen johtamisessa käytettäviä muisti- ja aikakustannuksia seuraavasti:\n      Muisti = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iteraatiot = 3 + ((PIM - 1) / 3), kun PIM on 31 tai pienempi, sen jälkeen 13 + (PIM - 31)\n\nKun kenttä jätetään tyhjäksi tai asetetaan arvoon 0, VeraCrypt käyttää Argon2:n oletus-PIM-arvoa (12), joka käyttää 416 MiB muistia ja 6 iteraatiota.\n\nKun salasana on alle 20 merkkiä pitkä, Argon2-PIM ei voi olla pienempi kuin 12, jotta vähimmäisturvataso säilyy.\nKun salasana on vähintään 20 merkkiä pitkä, Argon2-PIM voidaan asettaa mihin tahansa arvoon.\n\nYli 12:n Argon2-PIM lisää muistin käyttöä 1024 MiB:iin asti ja kasvattaa sen jälkeen iteraatioiden määrää. Tämä hidastaa liittämistä. Pieni Argon2-PIM (alle 12) nopeuttaa liittämistä, mutta se voi heikentää turvallisuutta, jos salasana ei ole tarpeeksi vahva.</entry>
+    <entry lang="fi" key="PIM_ARGON2_LARGE_WARNING">Valitsit Argon2-PIM-arvon, joka on suurempi kuin VeraCryptin oletusarvo.\nHuomioi, että tämä voi vaatia enemmän muistia ja hidastaa liittämistä huomattavasti.</entry>
+    <entry lang="fi" key="PIM_ARGON2_SMALL_WARNING">Valitsit Argon2-PIM-arvon, joka on pienempi kuin VeraCryptin oletusarvo. Huomioi, että jos salasanasi ei ole tarpeeksi vahva, tämä voi heikentää turvallisuutta.\n\nVahvistatko käyttäväsi vahvaa salasanaa?</entry>
+    <entry lang="fi" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Salasanan tulee sisältää vähintään 20 merkkiä, jotta määritettyä Argon2-PIM-arvoa voidaan käyttää.\nLyhyempiä salasanoja voidaan käyttää vain, jos Argon2-PIM on 12 tai suurempi.</entry>
+    <entry lang="fi" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER">Liitä NTFS-taltiot Linux-ytimen sisäisellä ajurilla</entry>
+    <entry lang="fi" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Vain Linux. Kun tämä asetus on käytössä eikä tiedostojärjestelmän tyyppiä ole annettu erikseen, VeraCrypt tutkii salauksen puretun virtuaalilaitteen komennolla blkid -p ja liittää havaitut NTFS-tiedostojärjestelmät käytettävissä olevalla ytimen sisäisellä NTFS-ajurilla ohittaen liittämisapureiden, kuten ntfs-3g:n, käytön. VeraCrypt käyttää ntfs-ajuria, kun se tunnistetaan varmasti moderniksi luku-/kirjoitusajuriksi tai kun sitä odotetaan Linux-versiossa 7.1 tai uudemmassa, ja muulloin ntfs3-ajuria. Jos NTFS-tunnistus epäonnistuu, VeraCrypt käyttää normaalia automaattista tiedostojärjestelmän valintaa. Jos tuettua ytimen sisäistä NTFS-ajuria ei ole käytettävissä tai ladattavissa, liittäminen epäonnistuu. Tämä erikseen valittava asetus voi välttää virransäästö- tai horrostilaan siirtymisen jumittumisen, jonka jäätyneet käyttäjätilan FUSE-tiedostojärjestelmät aiheuttavat.</entry>
+    <entry lang="fi" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">Tuettua ytimen sisäistä NTFS-ajuria ei ole käytettävissä tai ladattavissa. Jos haluat käyttää järjestelmän oletusarvoista NTFS-taustajärjestelmää, poista NTFS-ydinajurin asetus käytöstä tai älä pyydä ytimen NTFS-ajuria erikseen.</entry>
+    <entry lang="fi" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Taltion {0} normaali irrotus epäonnistui. Näin voi tapahtua, kun sovelluksilla on yhä tiedostoja tai hakemistoja avoinna taltiolla, tai kun isäntälaite irrotettiin ja liitos vanheni.\n\nJos laite on edelleen kytkettynä, valitse Ei, sulje taltiota käyttävät sovellukset ja yritä irrottaa taltio uudelleen.\n\nJos laite irrotettiin tai liitos on vanhentunut, VeraCrypt voi yrittää hätätilanteen puhdistusta käyttämällä tiedostojärjestelmän lazy-irrotusta ja poistamalla VeraCryptin ytimen objektit tai ajoittamalla niiden poiston. Odottavat kirjoitukset ovat saattaneet epäonnistua, tietoja on voinut kadota ja puhdistus voi pysyä odottavana, kunnes sovellukset sulkevat avoimet tiedostot. Tarkista tiedostojärjestelmä fsck:lla tai sopivalla korjaustyökalulla ennen kuin käytät sitä uudelleen.\n\nJatketaanko?</entry>
+    <entry lang="fi" key="LINUX_EMERGENCY_UNMOUNTED">Taltion {0} hätätilanteen puhdistus on aloitettu. Jos taltio irrotettiin, liitos oli vanhentunut tai odottavia kirjoituksia oli, tarkista tiedostojärjestelmä fsck:lla tai sopivalla korjaustyökalulla ennen kuin käytät sitä uudelleen.</entry>
+    <entry lang="fi" key="FORMAT_STAGE_WRITING_DATA">Luodaan taltion dataa. Odota.</entry>
+    <entry lang="fi" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Viimeistellään taltion luontia: kirjoitetaan varaotsikkoa.</entry>
+    <entry lang="fi" key="FORMAT_STAGE_FLUSHING_DATA">Viimeistellään taltion luontia: varmistetaan datan kirjoitus levylle. Tämä voi kestää useita minuutteja suurilla taltioilla tai hitaalla/USB-tallennusvälineellä.</entry>
+    <entry lang="fi" key="FORMAT_STAGE_FINISHED">Viimeistellään taltion luontia.</entry>
+    <entry lang="fi" key="FORMAT_STAGE_ABORTED">Taltion luonti on keskeytetty.</entry>
+    <entry lang="fi" key="FORMAT_STAGE_ERROR">Taltion luonti epäonnistui.</entry>
+    <entry lang="fi" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Viimeistellään taltion luontia: liitetään väliaikainen taltio.</entry>
+    <entry lang="fi" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Viimeistellään taltion luontia: valmistellaan väliaikaista laitetta.</entry>
+    <entry lang="fi" key="FORMAT_STAGE_CREATING_FILESYSTEM">Viimeistellään taltion luontia: luodaan tiedostojärjestelmä käyttäen {0}.</entry>
+    <entry lang="fi" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Viimeistellään taltion luontia: irrotetaan väliaikainen taltio.</entry>
+    <entry lang="fi" key="MACOSX_APFS_SYNTHESIZED_DEVICE">Valittu laite '{0}' on APFS:n syntetisoitu säilö tai taltio, eikä sitä voi käyttää raakamuotoisen VeraCrypt-taltion isäntänä.\n\nValitse sen sijaan fyysinen APFS-tallennusosio{1}.</entry>
+    <entry lang="fi" key="MACOSX_DEVICE_SYSTEM_PARTITION">Valittu laite '{0}' on macOS-järjestelmä- tai tukiosio, eikä sitä voi käyttää VeraCrypt-taltion isäntänä.</entry>
+    <entry lang="fi" key="MACOSX_APFS_SYSTEM_STORE">Valittu fyysinen APFS-tallennusosio '{0}' sisältää parhaillaan liitetyn macOS-järjestelmätaltion, eikä sitä voi käyttää VeraCrypt-taltion isäntänä.</entry>
+    <entry lang="fi" key="MACOSX_DEVICE_NOT_WRITABLE">macOS ilmoittaa valitun laitteen '{0}' olevan vain luku -tilassa. Valitse kirjoituskelpoinen fyysinen osio tai levy.</entry>
+    <entry lang="fi" key="MACOSX_APFS_EROFS_HINT">macOS ilmoitti valitun laitteen olevan vain luku -tilassa. Jos kyseessä on APFS-levy, varmista, että valitsit fyysisen APFS-tallennusosion etkä APFS:n syntetisoitua taltiota. Käytä Levytyökalua tai komentoa 'diskutil list' fyysisen osion tunnistamiseen ja yritä sitten uudelleen.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.fr.xml

@@ -1649,41 +1649,41 @@
     <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>
+    <entry lang="fr" key="ERR_KEY_DERIVATION_FAILED">La dérivation de la clé a échoué. Cela peut être dû à une mémoire insuffisante ou à une opération interrompue.</entry>
+    <entry lang="fr" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">La partition/le disque système est déjà déchiffré, mais le chemin du chargeur de démarrage EFI de Microsoft n’a pas été restauré vers le Gestionnaire de démarrage Windows. Seuls les fichiers de démarrage EFI doivent être réparés. Utilisez l’option de réparation du disque de secours VeraCrypt ou démarrez sur un média de récupération Windows et exécutez 'bcdboot W:\\Windows /s S: /f UEFI' après avoir remplacé W: par la lettre du volume Windows et S: par la lettre de la partition système EFI. Chemin :</entry>
+    <entry lang="fr" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">La partition/le disque système est déjà déchiffré, mais le chemin du chargeur de démarrage EFI de secours contient encore le chargeur de démarrage VeraCrypt. Seuls les fichiers de démarrage EFI doivent être réparés. Utilisez l’option de réparation du disque de secours VeraCrypt ou démarrez sur un média de récupération Windows et exécutez 'bcdboot W:\\Windows /s S: /f UEFI' après avoir remplacé W: par la lettre du volume Windows et S: par la lettre de la partition système EFI. Chemin :</entry>
+    <entry lang="fr" key="IDM_REPAIR_EFI_BOOT_LOADER">Réparer le chargeur de démarrage EFI...</entry>
+    <entry lang="fr" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt va restaurer les chemins du chargeur de démarrage EFI de Windows et supprimer les entrées et fichiers de démarrage EFI de VeraCrypt.\n\nUtilisez cette option uniquement après que la partition/le disque système a été entièrement déchiffré et que Windows peut démarrer sans chiffrement système.\n\nVoulez-vous continuer ?</entry>
+    <entry lang="fr" key="EFI_BOOT_LOADER_FILE_READ_FAILED">Le fichier du chargeur de démarrage EFI n’a pas pu être lu entièrement :</entry>
+    <entry lang="fr" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">Le fichier du chargeur de démarrage EFI est anormalement volumineux et n’a pas été inspecté :</entry>
+    <entry lang="fr" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">La partition/le disque système est déjà déchiffré et les fichiers du chargeur de démarrage EFI ont été restaurés, mais VeraCrypt n’a pas pu supprimer une ou plusieurs entrées de démarrage VeraCrypt du firmware. Les fichiers EFI de VeraCrypt ont été laissés en place afin que toute entrée restante du firmware pointe toujours vers un chargeur existant. Réessayez en tant qu’administrateur ou supprimez l’entrée de démarrage VeraCrypt depuis la configuration du firmware après avoir confirmé que le Gestionnaire de démarrage Windows démarre normalement.</entry>
+    <entry lang="fr" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">Le chargeur de démarrage EFI ne peut pas être réparé tant qu’un chiffrement ou déchiffrement du système est actif ou incomplet. Terminez ou reprenez le processus de chiffrement/déchiffrement du système en attente avant de réessayer.</entry>
+    <entry lang="fr" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">Cette action de réparation est disponible uniquement sur les systèmes démarrant en mode UEFI depuis une partition système GPT.</entry>
+    <entry lang="fr" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">Le chargeur de démarrage EFI a été réparé avec succès.</entry>
+    <entry lang="fr" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) contrôle les coûts en mémoire et en temps utilisés par la dérivation de la clé d’en-tête Argon2id comme suit:\n      Mémoire = min(64 Mo + ((PIM - 1) x 32 Mo), 1024 Mo)\n      Itérations = 3 + ((PIM - 1) / 3) pour un PIM inférieur ou égal à 31, puis 13 + (PIM - 31)\n\nLorsque ce champ est laissé vide ou défini à 0, VeraCrypt utilisera le PIM Argon2 par défaut (12), qui utilise 416 Mo de mémoire et 6 itérations.\n\nLorsque le mot de passe contient moins de 20 caractères, le PIM Argon2 ne peut pas être inférieur à 12 afin de maintenir un niveau minimal de sécurité.\nLorsque le mot de passe contient 20 caractères ou plus, le PIM Argon2 peut être défini à n’importe quelle valeur.\n\nUn PIM Argon2 supérieur à 12 augmente l’utilisation de la mémoire jusqu’à 1024 Mo puis augmente le nombre d’itérations. Cela aboutira à un montage plus lent. Un PIM Argon2 faible (inférieur à 12) conduira à un montage plus rapide mais cela peut réduire la sécurité si le mot de passe n’est pas assez fort.</entry>
+    <entry lang="fr" key="PIM_ARGON2_LARGE_WARNING">Vous avez choisi une valeur de PIM Argon2 supérieure à la valeur par défaut de VeraCrypt.\nNotez que cela peut nécessiter plus de mémoire et aboutir à un montage beaucoup plus lent.</entry>
+    <entry lang="fr" key="PIM_ARGON2_SMALL_WARNING">Vous avez choisi une valeur de PIM Argon2 inférieure à la valeur par défaut de VeraCrypt. Notez que si votre mot de passe n’est pas assez fort, cela pourrait réduire la sécurité.\n\nConfirmez-vous que vous utilisez un mot de passe fort ?</entry>
+    <entry lang="fr" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Le mot de passe doit contenir 20 caractères ou plus afin d’utiliser le PIM Argon2 spécifié.\nLes mots de passe plus courts ne peuvent être utilisés que si le PIM Argon2 est supérieur ou égal à 12.</entry>
+    <entry lang="fr" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER">Monter les volumes NTFS avec un pilote intégré au noyau Linux</entry>
+    <entry lang="fr" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux uniquement. Lorsque cette option est activée et qu’aucun type explicite de système de fichiers n’a été fourni, VeraCrypt sonde le périphérique virtuel déchiffré avec blkid -p et monte les systèmes de fichiers NTFS détectés avec un pilote NTFS intégré au noyau disponible, en contournant les utilitaires de montage tels que ntfs-3g. VeraCrypt utilise ntfs lorsqu’il est identifié avec certitude comme un pilote moderne en lecture/écriture ou attendu sous Linux 7.1 ou ultérieur, et utilise ntfs3 dans les autres cas. Si la détection NTFS échoue, VeraCrypt utilise la sélection automatique normale du système de fichiers. Si aucun pilote NTFS intégré au noyau pris en charge n’est disponible ou chargeable, le montage échoue. Cette option facultative peut éviter les blocages de mise en veille ou d’hibernation causés par des systèmes de fichiers FUSE en espace utilisateur figés.</entry>
+    <entry lang="fr" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">Aucun pilote NTFS intégré au noyau pris en charge n’est disponible ou chargeable. Pour utiliser le mécanisme NTFS par défaut du système, désactivez la préférence de pilote NTFS intégré au noyau ou ne demandez pas explicitement le NTFS du noyau.</entry>
+    <entry lang="fr" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Le démontage normal du volume {0} a échoué. Cela peut arriver lorsque des applications ont encore des fichiers ou des répertoires ouverts sur le volume, ou lorsque le périphérique hôte a été déconnecté et que le montage est devenu périmé.\n\nSi le périphérique est toujours connecté, choisissez Non, fermez les applications utilisant le volume, puis essayez de le démonter à nouveau.\n\nSi le périphérique a été déconnecté ou si le montage est périmé, VeraCrypt peut tenter un nettoyage d’urgence en détachant de manière différée le système de fichiers et en supprimant ou en programmant la suppression des objets du noyau VeraCrypt. Les écritures en attente peuvent avoir échoué, des données peuvent être perdues, et le nettoyage peut rester en attente jusqu’à ce que les applications ferment les fichiers ouverts. Vérifiez le système de fichiers avec fsck ou l’outil de réparation approprié avant de l’utiliser à nouveau.\n\nContinuer ?</entry>
+    <entry lang="fr" key="LINUX_EMERGENCY_UNMOUNTED">Le nettoyage d’urgence du volume {0} a été lancé. Si le volume a été déconnecté, si le montage était périmé ou s’il y avait des écritures en attente, vérifiez le système de fichiers avec fsck ou l’outil de réparation approprié avant de l’utiliser à nouveau.</entry>
+    <entry lang="fr" key="FORMAT_STAGE_WRITING_DATA">Création des données du volume. Merci de patienter.</entry>
+    <entry lang="fr" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalisation de la création du volume : écriture de l’en-tête de sauvegarde.</entry>
+    <entry lang="fr" key="FORMAT_STAGE_FLUSHING_DATA">Finalisation de la création du volume : synchronisation des données sur le disque. Cela peut prendre plusieurs minutes sur les grands volumes ou les supports lents/USB.</entry>
+    <entry lang="fr" key="FORMAT_STAGE_FINISHED">Finalisation de la création du volume.</entry>
+    <entry lang="fr" key="FORMAT_STAGE_ABORTED">La création du volume a été abandonnée.</entry>
+    <entry lang="fr" key="FORMAT_STAGE_ERROR">La création du volume a échoué.</entry>
+    <entry lang="fr" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalisation de la création du volume : montage du volume temporaire.</entry>
+    <entry lang="fr" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalisation de la création du volume : préparation du périphérique temporaire.</entry>
+    <entry lang="fr" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalisation de la création du volume : création du système de fichiers avec {0}.</entry>
+    <entry lang="fr" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalisation de la création du volume : démontage du volume temporaire.</entry>
+    <entry lang="fr" key="MACOSX_APFS_SYNTHESIZED_DEVICE">Le périphérique sélectionné '{0}' est un conteneur ou volume APFS synthétisé et ne peut pas être utilisé comme hôte brut de volume VeraCrypt.\n\nSélectionnez plutôt la partition physique de stockage APFS{1}.</entry>
+    <entry lang="fr" key="MACOSX_DEVICE_SYSTEM_PARTITION">Le périphérique sélectionné '{0}' est une partition système ou de support macOS et ne peut pas être utilisé comme hôte de volume VeraCrypt.</entry>
+    <entry lang="fr" key="MACOSX_APFS_SYSTEM_STORE">Le support physique APFS sélectionné '{0}' contient le volume système macOS actuellement monté et ne peut pas être utilisé comme hôte de volume VeraCrypt.</entry>
+    <entry lang="fr" key="MACOSX_DEVICE_NOT_WRITABLE">macOS signale que le périphérique sélectionné '{0}' est en lecture seule. Sélectionnez une partition physique ou un disque accessible en écriture.</entry>
+    <entry lang="fr" key="MACOSX_APFS_EROFS_HINT">macOS a signalé que le périphérique sélectionné est en lecture seule. S’il s’agit d’un disque APFS, assurez-vous d’avoir sélectionné la partition physique de stockage APFS et non un volume APFS synthétisé. Utilisez l’Utilitaire de disque ou 'diskutil list' pour identifier la partition physique, puis réessayez.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.it.xml

@@ -295,7 +295,7 @@
     <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>
+    <entry lang="it" key="IDT_EMV_OPTIONS">Opzioni EMV</entry>
     <entry lang="it" key="IDT_TASKBAR_ICON">Esecuzione di VeraCrypt in background</entry>
     <entry lang="it" key="IDT_TRAVELER_MOUNT">Volume VeraCrypt da montare (relativo alla radice del Traveler Disk):</entry>
     <entry lang="it" key="IDT_TRAVEL_INSERTION">Sull'inserimento del Traveler Disk:</entry>
@@ -390,7 +390,7 @@
     <entry lang="it" key="ADMINISTRATOR">Amministratore</entry>
     <entry lang="it" key="ADMIN_PRIVILEGES_DRIVER">Per caricare il driver VeraCrypt è necessario accedere come utente con privilegi di amministratore.</entry>
     <entry lang="it" key="ADMIN_PRIVILEGES_WARN_DEVICES">Per codificare/decodificare/formattare un unità/partizione è necessario accedere come utente con privilegi di amministratore.\n\nQuesta restrizione non si applica ai volumi basati su file.</entry>
-    <entry lang="en" key="ADMIN_PRIVILEGES_WARN_MANAGE_VOLUME">Unable to activate fast file creation: Administrator privileges required.\nPlease relaunch the program as an Administrator to enable this feature.\n\nWould you like to proceed without fast file creation?</entry>
+    <entry lang="it" key="ADMIN_PRIVILEGES_WARN_MANAGE_VOLUME">Impossibile attivare la Creazione Veloce: sono richiesti privilegi di amministratore.\nRiavvia il programma come Amministratore per abilitare questa funzione.\n\nVuoi procedere senza Creazione Veloce?</entry>
     <entry lang="it" key="ADMIN_PRIVILEGES_WARN_HIDVOL">Per creare un volume nascosto è necessario accedere come utente con privilegi di amministratore.\n\nContinuare?</entry>
     <entry lang="it" key="ADMIN_PRIVILEGES_WARN_NTFS">Per formattare il volume come NTFS è necessario accedere come utente con privilegi di amministratore.\n\nSenza i privilegi di amministrazione si può formattare il volume come FAT.</entry>
     <entry lang="it" key="AES_HELP">Algoritmo di codifica (Rijndael, pubblicato nel 1998) approvato per la FIPS, che può essere usato dai dipartimenti ed agenzie federali U.S.A. per proteggere le informazioni Top Secret.\nChiave a 256-bit, blocco a 128-bit, 14 passaggi (AES-256).\nModo operativo XTS.</entry>
@@ -940,7 +940,7 @@
     <entry lang="it" key="ENTER_HEADER_BACKUP_PASSWORD">Digitare la password per la testa memorizzata nel file di backup</entry>
     <entry lang="it" key="KEYFILE_CREATED">Il file chiave è stato creato correttamente.</entry>
     <entry lang="it" key="KEYFILE_INCORRECT_NUMBER">Il numero di file chiavi che hai fornito non è valido.</entry>
-    <entry lang="en" key="KEYFILE_INCORRECT_SIZE">The keyfile size must be at least 64 bytes.</entry>
+    <entry lang="it" key="KEYFILE_INCORRECT_SIZE">La dimensione del file chiave deve essere almeno 64 byte.</entry>
     <entry lang="it" key="KEYFILE_EMPTY_BASE_NAME">Per favore inserisci un nome per il/i file chiave per essere generato/i.</entry>
     <entry lang="it" key="KEYFILE_INVALID_BASE_NAME">Il nome del(dei) file chiave di base non è valido</entry>
     <entry lang="it" key="KEYFILE_ALREADY_EXISTS">Il file chiave '%s' esiste già.\nVuoi sovrascriverlo? Il processo di generazione sarà interrotto se rispondi No.</entry>
@@ -1519,7 +1519,7 @@
     <entry lang="it" key="LINUX_NOT_FAT_HINT">Tieni presente che il volume non verrà formattato con un filesystem FAT e, pertanto, potrebbe essere necessario installare un driver del filesystem aggiuntivo in piattaforme diverse da {0}, che ti consentiranno di montare il volume.</entry>
     <entry lang="it" key="LINUX_KERNEL_OLD">Il sistema usa una vecchia versione del kernel Linux.\n\nA causa di un bug nel kernel Linux, il sistema potrebbe smettere di rispondere quando scrivi dati su un volume VeraCrypt.\nQuesto problema può essere risolto aggiornando il kernel alla versione 2.6.24 o successiva.</entry>
     <entry lang="it" key="LINUX_VOL_UNMOUNTED">Il volume {0} è stato smontato.</entry>
-    <entry lang="en" key="LINUX_VOL_MOUNTED">Volume {0} has been mounted.</entry>
+    <entry lang="it" key="LINUX_VOL_MOUNTED">Il volume {0} è stato montato.</entry>
     <entry lang="it" key="LINUX_OOM">Memoria esaurita.</entry>
     <entry lang="it" key="LINUX_CANT_GET_ADMIN_PRIV">Impossibile ottenere i privilegi di amministratore</entry>
     <entry lang="it" key="LINUX_COMMAND_GET_ERROR">Il comando {0} ha restituito un errore {1}.</entry>
@@ -1649,41 +1649,41 @@
     <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>
+    <entry lang="it" key="ERR_KEY_DERIVATION_FAILED">Derivazione della chiave non riuscita. La causa potrebbe essere memoria insufficiente o un'operazione interrotta.</entry>
+    <entry lang="it" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">La partizione/unità di sistema è già stata decrittografata, ma il percorso del boot loader EFI Microsoft non è stato ripristinato nel Windows Boot Manager. Solo i file di avvio EFI devono essere riparati. Usa l'opzione di riparazione del VeraCrypt Rescue Disk, oppure avvia un supporto di ripristino di Windows ed esegui 'bcdboot W:\\Windows /s S: /f UEFI' dopo aver sostituito W: con la lettera dell'unità del volume Windows e S: con la lettera dell'unità della partizione di sistema EFI. Percorso:</entry>
+    <entry lang="it" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">La partizione/unità di sistema è già stata decrittografata, ma il percorso del boot loader EFI di fallback contiene ancora il VeraCrypt Boot Loader. Solo i file di avvio EFI devono essere riparati. Usa l'opzione di riparazione del VeraCrypt Rescue Disk, oppure avvia un supporto di ripristino di Windows ed esegui 'bcdboot W:\\Windows /s S: /f UEFI' dopo aver sostituito W: con la lettera dell'unità del volume Windows e S: con la lettera dell'unità della partizione di sistema EFI. Percorso:</entry>
+    <entry lang="it" key="IDM_REPAIR_EFI_BOOT_LOADER">Ripara boot loader EFI...</entry>
+    <entry lang="it" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt ripristinerà i percorsi del boot loader EFI di Windows e rimuoverà le voci e i file di avvio EFI di VeraCrypt.\n\nUsa questa opzione solo dopo che la partizione/unità di sistema è stata completamente decrittografata e Windows può avviarsi senza crittografia di sistema.\n\nVuoi continuare?</entry>
+    <entry lang="it" key="EFI_BOOT_LOADER_FILE_READ_FAILED">Il file del boot loader EFI non può essere letto completamente:</entry>
+    <entry lang="it" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">Il file del boot loader EFI è insolitamente grande e non è stato ispezionato:</entry>
+    <entry lang="it" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">La partizione/unità di sistema è già stata decrittografata e i file del boot loader EFI sono stati ripristinati, ma VeraCrypt non è riuscito a rimuovere una o più voci di avvio VeraCrypt dal firmware. I file EFI di VeraCrypt sono stati lasciati al loro posto in modo che eventuali voci firmware rimanenti puntino ancora a un loader esistente. Riprova come Amministratore oppure rimuovi la voce di avvio VeraCrypt dalle impostazioni del firmware dopo aver confermato che Windows Boot Manager si avvia normalmente.</entry>
+    <entry lang="it" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">Il boot loader EFI non può essere riparato mentre la crittografia o decrittografia di sistema è attiva o incompleta. Completa o riprendi il processo di crittografia/decrittografia di sistema in sospeso prima di riprovare.</entry>
+    <entry lang="it" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">Questa azione di riparazione è disponibile solo su sistemi avviati in modalità UEFI da una partizione di sistema GPT.</entry>
+    <entry lang="it" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">Il boot loader EFI è stato riparato correttamente.</entry>
+    <entry lang="it" key="PIM_ARGON2_HELP">Il PIM (Moltiplicatore delle Iterazioni Personali) controlla i costi di memoria e di tempo usati dalla derivazione Argon2id della chiave di intestazione come segue:\n      Memoria = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterazioni = 3 + ((PIM - 1) / 3) per PIM 31 o inferiore, quindi 13 + (PIM - 31)\n\nQuando viene lasciato vuoto o impostato a 0, VeraCrypt userà il PIM Argon2 predefinito (12), che usa 416 MiB di memoria e 6 iterazioni.\n\nQuando la password contiene meno di 20 caratteri, il PIM Argon2 non può essere inferiore a 12 per mantenere un livello minimo di sicurezza.\nQuando la password contiene 20 o più caratteri, il PIM Argon2 può essere impostato a qualsiasi valore.\n\nUn PIM Argon2 maggiore di 12 aumenta l'uso della memoria fino a 1024 MiB e poi aumenta le iterazioni. Questo porterà a un montaggio più lento. Un PIM Argon2 basso (inferiore a 12) porterà a un montaggio più rapido ma può ridurre la sicurezza se la password non è abbastanza forte.</entry>
+    <entry lang="it" key="PIM_ARGON2_LARGE_WARNING">Hai scelto un valore PIM Argon2 maggiore del valore predefinito di VeraCrypt.\nNota che questo può richiedere più memoria e portare a un montaggio molto più lento.</entry>
+    <entry lang="it" key="PIM_ARGON2_SMALL_WARNING">Hai scelto un valore PIM Argon2 inferiore al valore predefinito di VeraCrypt. Nota che se la password non è abbastanza forte, questo potrebbe portare a una sicurezza più debole.\n\nConfermi di usare una password forte?</entry>
+    <entry lang="it" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">La password deve contenere 20 o più caratteri per usare il PIM Argon2 specificato.\nPassword più brevi possono essere usate solo se il PIM Argon2 è 12 o maggiore.</entry>
+    <entry lang="it" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER">Monta volumi NTFS con un driver Linux interno al kernel</entry>
+    <entry lang="it" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Solo Linux. Quando questa opzione è abilitata e non è stato fornito alcun tipo di filesystem esplicito, VeraCrypt esamina il dispositivo virtuale decrittografato con 'blkid -p' e monta i filesystem NTFS rilevati con un driver NTFS disponibile nel kernel, evitando helper di montaggio come 'ntfs-3g'. VeraCrypt usa 'ntfs' quando viene identificato positivamente come driver moderno in lettura/scrittura o previsto sul kernel Linux 7.1 o successivo, altrimenti usa 'ntfs3'. Se il rilevamento NTFS fallisce, VeraCrypt usa la normale selezione automatica del filesystem. Se nessun driver NTFS nel kernel supportato è disponibile o caricabile, il montaggio fallisce. Questa opzione facoltativa può evitare blocchi durante sospensione o ibernazione causati da filesystem FUSE in spazio utente bloccati.</entry>
+    <entry lang="it" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">Nessun driver NTFS supportato nel kernel è disponibile o caricabile. Per usare il backend NTFS predefinito del sistema, disabilita la preferenza del driver NTFS del kernel o non richiedere esplicitamente NTFS del kernel.</entry>
+    <entry lang="it" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Lo smontaggio normale del volume {0} è fallito. Questo può accadere quando applicazioni hanno ancora file o directory aperti sul volume, oppure quando il dispositivo sottostante è stato scollegato e il montaggio è diventato non valido.\n\nSe il dispositivo è ancora connesso, scegli No, chiudi le applicazioni che usano il volume e prova di nuovo a smontarlo.\n\nSe il dispositivo è stato scollegato o il montaggio non è più valido, VeraCrypt può tentare una pulizia di emergenza distaccando il filesystem in modalità lazy e rimuovendo, o pianificando la rimozione, degli oggetti kernel di VeraCrypt. Le scritture in sospeso potrebbero essere fallite, i dati potrebbero essere persi e la pulizia potrebbe restare in sospeso finché le applicazioni non chiudono i file aperti. Controlla il filesystem con 'fsck' o con lo strumento di riparazione appropriato prima di usarlo di nuovo.\n\nContinuare?</entry>
+    <entry lang="it" key="LINUX_EMERGENCY_UNMOUNTED">La pulizia di emergenza per il volume {0} è stata avviata. Se il volume è stato scollegato, il montaggio non era più valido o c'erano scritture in sospeso, controlla il filesystem con 'fsck' o con lo strumento di riparazione appropriato prima di usarlo di nuovo.</entry>
+    <entry lang="it" key="FORMAT_STAGE_WRITING_DATA">Creazione dei dati del volume. Attendere.</entry>
+    <entry lang="it" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizzazione della creazione del volume: scrittura dell'header di backup.</entry>
+    <entry lang="it" key="FORMAT_STAGE_FLUSHING_DATA">Finalizzazione della creazione del volume: sincronizzazione dei dati su disco. Questa operazione può richiedere diversi minuti su volumi grandi o supporti lenti/USB.</entry>
+    <entry lang="it" key="FORMAT_STAGE_FINISHED">Finalizzazione della creazione del volume.</entry>
+    <entry lang="it" key="FORMAT_STAGE_ABORTED">La creazione del volume è stata interrotta.</entry>
+    <entry lang="it" key="FORMAT_STAGE_ERROR">Creazione del volume fallita.</entry>
+    <entry lang="it" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizzazione della creazione del volume: montaggio del volume temporaneo.</entry>
+    <entry lang="it" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizzazione della creazione del volume: preparazione del dispositivo temporaneo.</entry>
+    <entry lang="it" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizzazione della creazione del volume: creazione del filesystem usando {0}.</entry>
+    <entry lang="it" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizzazione della creazione del volume: smontaggio del volume temporaneo.</entry>
+    <entry lang="it" key="MACOSX_APFS_SYNTHESIZED_DEVICE">Il dispositivo selezionato '{0}' è un contenitore o volume APFS sintetizzato e non può essere usato come host di un volume VeraCrypt raw.\n\nSeleziona invece la partizione{1} dello store fisico APFS.</entry>
+    <entry lang="it" key="MACOSX_DEVICE_SYSTEM_PARTITION">Il dispositivo selezionato '{0}' è una partizione di sistema/supporto macOS e non può essere usato come host di un volume VeraCrypt.</entry>
+    <entry lang="it" key="MACOSX_APFS_SYSTEM_STORE">Lo store fisico APFS selezionato '{0}' contiene il volume di sistema macOS attualmente montato e non può essere usato come host di un volume VeraCrypt.</entry>
+    <entry lang="it" key="MACOSX_DEVICE_NOT_WRITABLE">macOS segnala il dispositivo selezionato '{0}' come di sola lettura. Seleziona una partizione fisica o un disco scrivibile.</entry>
+    <entry lang="it" key="MACOSX_APFS_EROFS_HINT">macOS ha segnalato il dispositivo selezionato come di sola lettura. Se questo è un disco APFS, assicurati di aver selezionato la partizione dello store fisico APFS, non un volume APFS sintetizzato. Usa Utility Disco o 'diskutil list' per identificare la partizione fisica, quindi riprova.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.ja.xml

@@ -1649,41 +1649,41 @@
     <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>
+    <entry lang="ja" key="ERR_KEY_DERIVATION_FAILED">キー導出に失敗しました。メモリ不足または操作の中断が原因である可能性があります。</entry>
+    <entry lang="ja" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">システムパーティション/ドライブはすでに復号されていますが、EFI Microsoft ブートローダーのパスが Windows Boot Manager に復元されていません。修復が必要なのは EFI ブートファイルのみです。VeraCrypt レスキューディスクの修復オプションを使用するか、Windows 回復メディアから起動し、W: を Windows ボリュームのドライブレターに、S: を EFI システムパーティションのドライブレターに置き換えてから 'bcdboot W:\\Windows /s S: /f UEFI' を実行してください。パス:</entry>
+    <entry lang="ja" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">システムパーティション/ドライブはすでに復号されていますが、EFI フォールバックブートローダーのパスに VeraCrypt ブートローダーがまだ含まれています。修復が必要なのは EFI ブートファイルのみです。VeraCrypt レスキューディスクの修復オプションを使用するか、Windows 回復メディアから起動し、W: を Windows ボリュームのドライブレターに、S: を EFI システムパーティションのドライブレターに置き換えてから 'bcdboot W:\\Windows /s S: /f UEFI' を実行してください。パス:</entry>
+    <entry lang="ja" key="IDM_REPAIR_EFI_BOOT_LOADER">EFI ブートローダーを修復...</entry>
+    <entry lang="ja" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt は Windows EFI ブートローダーのパスを復元し、VeraCrypt EFI ブートエントリおよびファイルを削除します。\n\nこの操作は、システムパーティション/ドライブが完全に復号され、Windows がシステム暗号化なしで起動できる場合にのみ使用してください。\n\n続行しますか？</entry>
+    <entry lang="ja" key="EFI_BOOT_LOADER_FILE_READ_FAILED">EFI ブートローダーファイルを完全に読み取ることができませんでした:</entry>
+    <entry lang="ja" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">EFI ブートローダーファイルが予期せず大きいため、検査されませんでした:</entry>
+    <entry lang="ja" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">システムパーティション/ドライブはすでに復号され、EFI ブートローダーファイルは復元されましたが、VeraCrypt は 1 つ以上の VeraCrypt ファームウェアブートエントリを削除できませんでした。残っているファームウェアエントリが既存のローダーを指し続けるよう、VeraCrypt EFI ファイルはそのまま残されました。管理者として再試行するか、Windows Boot Manager が正常に起動することを確認した後、ファームウェア設定から VeraCrypt ブートエントリを削除してください。</entry>
+    <entry lang="ja" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">システム暗号化または復号が実行中、あるいは未完了の場合、EFI ブートローダーは修復できません。再試行する前に、保留中のシステム暗号化/復号処理を完了または再開してください。</entry>
+    <entry lang="ja" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">この修復操作は、GPT システムパーティションから UEFI モードで起動しているシステムでのみ利用できます。</entry>
+    <entry lang="ja" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">EFI ブートローダーは正常に修復されました。</entry>
+    <entry lang="ja" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) は、Argon2id ヘッダーキーの導出で使用されるメモリコストと時間コストを次のように制御します:\n      メモリ = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      反復回数 = PIM が 31 以下の場合は 3 + ((PIM - 1) / 3)、それを超える場合は 13 + (PIM - 31)\n\n空欄のままにするか 0 に設定すると、VeraCrypt はデフォルトの Argon2 PIM (12) を使用します。この設定では 416 MiB のメモリと 6 回の反復を使用します。\n\nパスワードが 20 文字未満の場合、最小限のセキュリティレベルを維持するために Argon2 PIM を 12 未満にすることはできません。\nパスワードが 20 文字以上の場合、Argon2 PIM は任意の値に設定できます。\n\n12 より大きい Argon2 PIM は、メモリ使用量を最大 1024 MiB まで増やし、その後は反復回数を増やします。これによりマウントは遅くなります。小さい Argon2 PIM (12 未満) はマウントを速くしますが、パスワードが十分に強力でない場合、セキュリティが低下する可能性があります。</entry>
+    <entry lang="ja" key="PIM_ARGON2_LARGE_WARNING">VeraCrypt のデフォルト値より大きい Argon2 PIM 値が選択されています。\nこれにより、より多くのメモリが必要になり、マウントが大幅に遅くなる可能性があることに注意してください。</entry>
+    <entry lang="ja" key="PIM_ARGON2_SMALL_WARNING">VeraCrypt のデフォルト値より小さい Argon2 PIM 値が選択されています。パスワードが十分に強力でない場合、セキュリティが低下する可能性があることに注意してください。\n\n強力なパスワードを使用していることを確認しますか？</entry>
+    <entry lang="ja" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">指定した Argon2 PIM を使用するには、パスワードは 20 文字以上である必要があります。\nそれより短いパスワードは、Argon2 PIM が 12 以上の場合にのみ使用できます。</entry>
+    <entry lang="ja" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER">Linux カーネル内ドライバで NTFS ボリュームをマウントする</entry>
+    <entry lang="ja" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux のみ。これを有効にし、明示的なファイルシステムタイプが指定されていない場合、VeraCrypt は復号済みの仮想デバイスを blkid -p で検査し、検出された NTFS ファイルシステムを利用可能なカーネル内 NTFS ドライバでマウントします。これにより ntfs-3g などのマウントヘルパーは迂回されます。VeraCrypt は、ntfs が現行の読み書き対応ドライバであると明確に識別された場合、または Linux 7.1 以降で期待される場合には ntfs を使用し、それ以外の場合は ntfs3 を使用します。NTFS の検出に失敗した場合、VeraCrypt は通常の自動ファイルシステム選択を使用します。サポートされているカーネル内 NTFS ドライバが利用できない、または読み込めない場合、マウントは失敗します。このオプトインオプションにより、ユーザースペース FUSE ファイルシステムのフリーズが原因でサスペンドまたは休止状態への移行時にハングする問題を回避できる場合があります。</entry>
+    <entry lang="ja" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">サポートされているカーネル内 NTFS ドライバが利用できないか、読み込めません。システムのデフォルト NTFS バックエンドを使用するには、NTFS カーネルドライバ設定を無効にするか、カーネル NTFS を明示的に要求しないでください。</entry>
+    <entry lang="ja" key="LINUX_EMERGENCY_UNMOUNT_WARNING">ボリューム {0} の通常のマウント解除に失敗しました。これは、アプリケーションがまだボリューム上のファイルまたはディレクトリを開いている場合や、背後のデバイスが切断されてマウント状態が無効になった場合に発生することがあります。\n\nデバイスがまだ接続されている場合は、「いいえ」を選択し、そのボリュームを使用しているアプリケーションを閉じてから、もう一度マウント解除を試してください。\n\nデバイスが切断された、またはマウント状態が無効になっている場合、VeraCrypt はファイルシステムを遅延デタッチし、VeraCrypt カーネルオブジェクトを削除または削除予約することで、緊急クリーンアップを試行できます。保留中の書き込みが失敗している可能性があり、データが失われることがあります。また、開いているファイルをアプリケーションが閉じるまで、クリーンアップが保留のままになることがあります。再度使用する前に、fsck または適切な修復ツールでファイルシステムを確認してください。\n\n続行しますか？</entry>
+    <entry lang="ja" key="LINUX_EMERGENCY_UNMOUNTED">ボリューム {0} の緊急クリーンアップを開始しました。ボリュームが切断されていた場合、マウント状態が無効になっていた場合、または保留中の書き込みがあった場合は、再度使用する前に fsck または適切な修復ツールでファイルシステムを確認してください。</entry>
+    <entry lang="ja" key="FORMAT_STAGE_WRITING_DATA">ボリュームデータを作成しています。お待ちください。</entry>
+    <entry lang="ja" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">ボリューム作成を完了しています: バックアップヘッダを書き込んでいます。</entry>
+    <entry lang="ja" key="FORMAT_STAGE_FLUSHING_DATA">ボリューム作成を完了しています: データをディスクにフラッシュしています。大きなボリュームや低速/USB ストレージでは数分かかることがあります。</entry>
+    <entry lang="ja" key="FORMAT_STAGE_FINISHED">ボリューム作成を完了しています。</entry>
+    <entry lang="ja" key="FORMAT_STAGE_ABORTED">ボリュームの作成は中止されました。</entry>
+    <entry lang="ja" key="FORMAT_STAGE_ERROR">ボリュームの作成に失敗しました。</entry>
+    <entry lang="ja" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">ボリューム作成を完了しています: 一時ボリュームをマウントしています。</entry>
+    <entry lang="ja" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">ボリューム作成を完了しています: 一時デバイスを準備しています。</entry>
+    <entry lang="ja" key="FORMAT_STAGE_CREATING_FILESYSTEM">ボリューム作成を完了しています: {0} を使用してファイルシステムを作成しています。</entry>
+    <entry lang="ja" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">ボリューム作成を完了しています: 一時ボリュームをマウント解除しています。</entry>
+    <entry lang="ja" key="MACOSX_APFS_SYNTHESIZED_DEVICE">選択されたデバイス '{0}' は APFS 合成コンテナまたはボリュームであり、raw デバイス型 VeraCrypt ボリュームのホストとして使用できません。\n\n代わりに物理 APFS ストアパーティション{1}を選択してください。</entry>
+    <entry lang="ja" key="MACOSX_DEVICE_SYSTEM_PARTITION">選択されたデバイス '{0}' は macOS システム/サポートパーティションであり、VeraCrypt ボリュームホストとして使用できません。</entry>
+    <entry lang="ja" key="MACOSX_APFS_SYSTEM_STORE">選択された APFS 物理ストア '{0}' には現在マウントされている macOS システムボリュームが含まれているため、VeraCrypt ボリュームホストとして使用できません。</entry>
+    <entry lang="ja" key="MACOSX_DEVICE_NOT_WRITABLE">macOS は、選択されたデバイス '{0}' を読み取り専用として報告しています。書き込み可能な物理パーティションまたはディスクを選択してください。</entry>
+    <entry lang="ja" 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.ko.xml

@@ -137,10 +137,10 @@
     <entry lang="ko" key="IDC_FAV_VOL_OPTIONS_GLOBAL_SETTINGS_BOX">전역 설정</entry>
     <entry lang="ko" key="IDC_HK_UNMOUNT_BALLOON_TOOLTIP">단축키 분리 성공 후 말풍선 툴팁 표시</entry>
     <entry lang="ko" key="IDC_HK_UNMOUNT_PLAY_SOUND">단축키 분리 성공 후 시스템 알림 소리 재생</entry>
-    <entry lang="en" key="IDC_HK_MOD_ALT">ALT</entry>
-    <entry lang="en" key="IDC_HK_MOD_CTRL">Ctrl</entry>
-    <entry lang="en" key="IDC_HK_MOD_SHIFT">SHIFT</entry>
-    <entry lang="en" key="IDC_HK_MOD_WIN">Win</entry>
+    <entry lang="ko" key="IDC_HK_MOD_ALT">Alt</entry>
+    <entry lang="ko" key="IDC_HK_MOD_CTRL">Ctrl</entry>
+    <entry lang="ko" key="IDC_HK_MOD_SHIFT">Shift</entry>
+    <entry lang="ko" key="IDC_HK_MOD_WIN">Win</entry>
     <entry lang="ko" key="IDC_HOTKEY_ASSIGN">할당</entry>
     <entry lang="ko" key="IDC_HOTKEY_REMOVE">제거</entry>
     <entry lang="ko" key="IDC_KEYFILES">키 파일...</entry>
@@ -470,10 +470,10 @@
     <entry lang="ko" key="PERMANENTLY_DECRYPT">영구 복호화</entry>
     <entry lang="ko" key="EXIT">종료</entry>
     <entry lang="ko" key="EXT_PARTITION">이 확장 파티션에 대한 논리 드라이브를 생성한 다음 다시 시도하세요.</entry>
-    <entry lang="ko" key="FILE_HELP">VeraCrypt 볼륨은 파일(VeraCrypt 컨테이너라고 함)에 있을 수 있으며, 이 컨테이너는 하드 디스크, USB 플래시 드라이브 등에 있을 수 있습니다. VeraCrypt 컨테이너는 일반 파일과 동일합니다(예: 일반 파일로 이동하거나 삭제할 수 있음). '파일 선택'을 클릭하여 컨테이너의 파일 이름을 선택하고 컨테이너를 만들 위치를 선택합니다.\n\nWARNING: 기존 파일을 선택하면 VeraCrypt가 파일을 암호화하지 않습니다. 파일이 삭제되고 새로 생성된 VeraCrypt 컨테이너로 대체됩니다. 지금 생성하려는 VeraCrypt 컨테이너로 파일을 이동하여 기존 파일을 암호화할 수 있습니다.</entry>
+    <entry lang="ko" key="FILE_HELP">VeraCrypt 볼륨은 파일(VeraCrypt 컨테이너라고 함)에 있을 수 있으며, 이 컨테이너는 하드 디스크, USB 플래시 드라이브 등에 있을 수 있습니다. VeraCrypt 컨테이너는 일반 파일과 동일합니다(예: 일반 파일로 이동하거나 삭제할 수 있음). '파일 선택'을 클릭하여 컨테이너의 파일 이름을 선택하고 컨테이너를 만들 위치를 선택합니다.\n\n경고: 기존 파일을 선택하면 VeraCrypt가 파일을 암호화하지 않습니다. 파일이 삭제되고 새로 생성된 VeraCrypt 컨테이너로 대체됩니다. 지금 생성하려는 VeraCrypt 컨테이너로 파일을 이동하여 기존 파일을 암호화할 수 있습니다.</entry>
     <entry lang="ko" key="FILE_HELP_HIDDEN_HOST_VOL">생성할 외부 볼륨의 위치를 선택합니다(이 볼륨 내에서 숨겨진 볼륨은 나중에 생성됩니다).\n\nVeraCrypt 볼륨은 파일(VeraCrypt 컨테이너)에 있을 수 있으며, 파일(VeraCrypt 컨테이너)은 하드 디스크, USB 플래시 드라이브 등에 있을 수 있습니다. VeraCrypt 컨테이너는 일반 파일로 이동하거나 삭제할 수 있습니다. '파일 선택'을 클릭하여 컨테이너의 파일 이름을 선택하고 컨테이너를 만들 위치를 선택합니다. 기존 파일을 선택하면 VeraCrypt가 파일을 암호화하지 않고 삭제되어 새로 생성된 컨테이너로 대체됩니다. 지금 생성하려는 VeraCrypt 컨테이너로 파일을 이동하여 기존 파일을 암호화할 수 있습니다.</entry>
     <entry lang="ko" key="DEVICE_HELP">암호화된 디바이스 호스팅된 VeraCrypt 볼륨은 하드 디스크, 솔리드 스테이트 드라이브, USB 메모리 스틱 및 지원되는 다른 저장 장치의 파티션 내에 생성할 수 있습니다. 파티션은 제자리에 암호화될 수도 있습니다.\n\n또한 암호화된 디바이스 호스팅된 VeraCrypt 볼륨을 파티션이 포함되지 않은 장치(HDD 및 SSD 포함) 내에서 생성할 수 있습니다.\n\n참고: 파티션이 포함된 장치는 Windows가 설치되어 있고 부팅되는 드라이브인 경우에만 단일 키를 사용하여 완전히 암호화될 수 있습니다.</entry>
-    <entry lang="ko" key="DEVICE_HELP_NO_INPLACE">디바이스 호스팅된 VeraCrypt 볼륨은 HDD, SSD, USB 메모리 스틱 및 기타 저장 장치 내에 생성할 수 있습니다.\n\nWARNING: 파티션/디바이스가 포맷되고 파티션에 현재 저장된 모든 데이터가 손실됩니다.</entry>
+    <entry lang="ko" key="DEVICE_HELP_NO_INPLACE">디바이스 호스팅된 VeraCrypt 볼륨은 HDD, SSD, USB 메모리 스틱 및 기타 저장 장치 내에 생성할 수 있습니다.\n\n경고: 파티션/디바이스가 포맷되고 파티션에 현재 저장된 모든 데이터가 손실됩니다.</entry>
     <entry lang="ko" key="DEVICE_HELP_HIDDEN_HOST_VOL">\n생성될 “외부 볼륨”의 위치를 선택합니다. 나중에 외부 볼륨 안에 “숨긴 볼륨”이 만들어집니다.\n\n외부 볼륨은 하드 디스크 파티션, SSD, USB 메모리 스틱 및 기타 지원되는 저장 장치 안에 만들어질 수 있습니다. 외부 볼륨은 파티션을 포함하고 있지 않은 장치(* 하드 디스크 및 SSD 포함) 내에도 만들어질 수 있습니다.\n\n주의: 파티션/장치가 포맷되고 현재 이곳에 저장된 모든 데이터를 잃게 됩니다.</entry>
     <entry lang="ko" key="FILE_HELP_HIDDEN_HOST_VOL_DIRECT">\n숨겨진 볼륨을 만들 VeraCrypt 볼륨의 위치를 선택합니다.</entry>
     <entry lang="ko" key="FILE_IN_USE">경고: 호스트 파일/장치가 이미 사용 중입니다!\n\n이(가) 이러한 결과를 예상하지 못할 경우 시스템이 불안정해질 수 있습니다. 볼륨을 마운트하기 전에 호스트 파일/장치(예: 바이러스 백신 또는 백업 프로그램)를 사용할 수 있는 모든 프로그램을 닫아야 합니다.\n\n계속 진행하시겠습니까?</entry>
@@ -525,18 +525,18 @@
     <entry lang="ko" key="HIDVOL_FORMAT_FINISHED_TITLE">숨겨진 볼륨이 생성되었습니다.</entry>
     <entry lang="ko" key="HIDVOL_FORMAT_FINISHED_HELP">숨겨진 VeraCrypt 볼륨이 생성되었으며 사용할 준비가 되었습니다. 모든 지침을 따르고 VeraCrypt 사용자 설명서의 "숨겨진 볼륨에 대한 보안 요구 사항 및 주의 사항" 섹션에 나열된 주의 사항과 요구 사항을 준수하는 경우, 외부 볼륨이 장착되어 있더라도 숨겨진 볼륨이 존재한다는 것을 증명할 수 없습니다.\n\n경고: 숨겨진 볼륨을 보호하지 않으면 (VERACRYPT 사용 설명서의 "숨겨진 볼륨 보호"절을 참조하십시오), 볼륨을 쓰지 마세요. 그렇지 않으면 숨겨진 볼륨을 초과하여 손상시킬 수 있습니다!</entry>
     <entry lang="ko" key="FIRST_HIDDEN_OS_BOOT_INFO">숨겨진 운영 체제를 시작했습니다. 숨겨진 운영 체제가 원래 운영 체제와 동일한 파티션에 설치된 것으로 나타납니다. 그러나 실제로는 숨겨진 볼륨에 있는 파티션 내에 설치됩니다. 모든 읽기 및 쓰기 작업은 원래 시스템 파티션에서 숨겨진 볼륨으로 투명하게 리디렉션됩니다.\n운영 체제나 애플리케이션 중 어느 것도 시스템 파티션에서 읽고 쓴 데이터가 실제로 뒤의 파티션(숨겨진 볼륨에서/로)에 쓰여지는 것을 알지 못합니다. 이러한 데이터는 평상시와 같이 즉시 암호화 및 암호 해독됩니다(디코이 운영 체제에 사용될 암호화 키와 다른 암호화 키 사용).계속하려면 다음을 클릭합니다.</entry>
-    <entry lang="ko" key="HIDVOL_HOST_FILLING_HELP_SYSENC">외부 볼륨이 생성되어 %hc: 드라이브로 마운트되었습니다. 이제 실제로 숨기려 하지 않는 중요해 보이는 파일을 이 외부 볼륨에 복사해야 합니다. 시스템 파티션 뒤에 있는 첫 번째 파티션의 암호를 강제로 공개해야 하는 모든 사용자가 외부 볼륨과 숨겨진 볼륨(숨겨진 운영 체제 포함)이 모두 있을 수 있습니다. 이 외부 볼륨의 암호를 표시할 수 있으며 숨겨진 볼륨(및 숨겨진 운영 체제)의 존재는 비밀로 유지됩니다.\n\nIMPORTANT: 외부 볼륨에 복사하는 파일은 %s 이상 차지하면 안 됩니다. 그렇지 않으면 숨겨진 볼륨을 위한 외부 볼륨의 사용 가능한 공간이 부족할 수 있습니다(계속하지 못할 수도 있습니다). 복사를 마친 후 다음을 클릭합니다(볼륨을 마운트 해제하지 않음).</entry>
+    <entry lang="ko" key="HIDVOL_HOST_FILLING_HELP_SYSENC">외부 볼륨이 생성되어 %hc: 드라이브로 마운트되었습니다. 이제 실제로 숨기려 하지 않는 중요해 보이는 파일을 이 외부 볼륨에 복사해야 합니다. 시스템 파티션 뒤에 있는 첫 번째 파티션의 암호를 강제로 공개해야 하는 모든 사용자가 외부 볼륨과 숨겨진 볼륨(숨겨진 운영 체제 포함)이 모두 있을 수 있습니다. 이 외부 볼륨의 암호를 표시할 수 있으며 숨겨진 볼륨(및 숨겨진 운영 체제)의 존재는 비밀로 유지됩니다.\n\n중요: 외부 볼륨에 복사하는 파일은 %s 이상 차지하면 안 됩니다. 그렇지 않으면 숨겨진 볼륨을 위한 외부 볼륨의 사용 가능한 공간이 부족할 수 있습니다(계속하지 못할 수도 있습니다). 복사를 마친 후 다음을 클릭합니다(볼륨을 마운트 해제하지 않음).</entry>
     <entry lang="ko" key="HIDVOL_HOST_FILLING_HELP">외부 볼륨이 생성되어 %hc: 드라이브로 마운트되었습니다. 이제 실제로 숨기지 않을 중요해 보이는 파일을 이 볼륨에 복사해야 합니다. 이 파일은 암호를 공개하도록 강요하는 모든 사용자를 위해 제공됩니다. 숨겨진 볼륨이 아닌 이 외부 볼륨의 암호만 표시됩니다. 사용자가 정말 신경 쓰는 파일은 나중에 생성되는 숨겨진 볼륨에 저장됩니다. 복사를 마치면 다음을 클릭합니다. 볼륨을 마운트 해제하지 않습니다.\n\n참고: 다음을 클릭하면 외부 볼륨의 클러스터 비트맵이 스캔되어 끝단이 볼륨의 끝과 정렬된 사용 가능한 공간의 중단 없는 영역 크기를 결정합니다. 이 영역은 숨겨진 볼륨을 수용하므로 가능한 최대 크기를 제한합니다. 클러스터 비트맵 검색은 숨겨진 볼륨에 의해 외부 볼륨의 데이터를 덮어쓰지 않도록 합니다.</entry>
     <entry lang="ko" key="HIDVOL_HOST_FILLING_TITLE">외부 볼륨 내용</entry>
     <entry lang="ko" key="HIDVOL_HOST_PRE_CIPHER_HELP">\n\n다음 단계에서는 숨겨진 볼륨이 나중에 생성될 외부 볼륨에 대한 옵션을 설정합니다.</entry>
     <entry lang="ko" key="HIDVOL_HOST_PRE_CIPHER_HELP_SYSENC">\n\n다음 단계에서는 시스템 파티션 뒤의 첫 번째 파티션에 이른바 외부 VeraCrypt 볼륨을 생성합니다(이전 단계 중 하나에서 설명됨).</entry>
     <entry lang="ko" key="HIDVOL_HOST_PRE_CIPHER_TITLE">외부 볼륨</entry>
-    <entry lang="ko" key="HIDDEN_OS_PRE_CIPHER_HELP">다음 단계에서는 숨겨진 운영 체제를 포함하는 숨겨진 볼륨의 옵션과 암호를 설정합니다.\n\nRemark: 외부 볼륨의 클러스터 비트맵을 검색하여 끝단이 외부 볼륨의 끝과 정렬된 사용 가능한 공간의 크기를 결정합니다. 이 영역은 숨겨진 볼륨을 수용하므로 가능한 최대 크기를 제한합니다. 숨겨진 볼륨의 가능한 최대 크기가 시스템 파티션 크기보다 큰 것으로 확인되었습니다(시스템 파티션의 전체 내용을 숨겨진 볼륨에 복사해야 하기 때문에 필요). 이렇게 하면 현재 외부 볼륨에 저장된 데이터가 숨겨진 볼륨 영역에 기록된 데이터로 덮어쓰지 않습니다.</entry>
+    <entry lang="ko" key="HIDDEN_OS_PRE_CIPHER_HELP">다음 단계에서는 숨겨진 운영 체제를 포함하는 숨겨진 볼륨의 옵션과 암호를 설정합니다.\n\n참고: 외부 볼륨의 클러스터 비트맵을 검색하여 끝단이 외부 볼륨의 끝과 정렬된 사용 가능한 공간의 크기를 결정합니다. 이 영역은 숨겨진 볼륨을 수용하므로 가능한 최대 크기를 제한합니다. 숨겨진 볼륨의 가능한 최대 크기가 시스템 파티션 크기보다 큰 것으로 확인되었습니다(시스템 파티션의 전체 내용을 숨겨진 볼륨에 복사해야 하기 때문에 필요). 이렇게 하면 현재 외부 볼륨에 저장된 데이터가 숨겨진 볼륨 영역에 기록된 데이터로 덮어쓰지 않습니다.</entry>
     <entry lang="ko" key="HIDDEN_OS_PRE_CIPHER_WARNING">중요: 이 단계에서 선택한 알고리즘을 기억하시기 바랍니다. 디코이 시스템에 대해 동일한 알고리즘을 선택해야 합니다. 그렇지 않으면 숨겨진 시스템에 액세스할 수 없게 됩니다. (암호화 시스템은 숨겨진 시스템과 동일한 암호화 알고리즘으로 암호화되어야 합니다.)\n\n참고: 그 이유는 디코이 시스템과 은닉 시스템이 사용자가 선택한 단일 알고리즘만 지원하는 단일 부트 로더를 공유하기 때문입니다(각 알고리즘에 대해 VeraCrypt Boot Loader의 특수 버전이 있음).</entry>
     <entry lang="ko" key="HIDVOL_PRE_CIPHER_HELP">\n\n볼륨 클러스터 비트맵이 검색되었으며 숨겨진 볼륨의 최대 크기가 확인되었습니다. 다음 단계에서는 숨겨진 볼륨의 옵션, 크기 및 암호를 설정합니다.</entry>
     <entry lang="ko" key="HIDVOL_PRE_CIPHER_TITLE">숨겨진 볼륨</entry>
-    <entry lang="ko" key="HIDVOL_PROT_WARN_AFTER_MOUNT">이제 외부 볼륨이 분리될 때까지 숨겨진 볼륨이 손상되지 않도록 보호됩니다.\n\nWARNING: 숨겨진 볼륨 영역에 데이터를 저장하려고 하면 VeraCrypt는 전체 볼륨(외부 및 숨겨진 부분 모두)이 마운트 해제될 때까지 쓰기 보호 기능을 시작합니다. 이로 인해 외부 볼륨의 파일 시스템이 손상될 수 있으며, 이 경우 숨겨진 볼륨의 신뢰할 수 있는 부인성에 부정적인 영향을 미칠 수 있습니다. 따라서 숨겨진 볼륨 영역에 쓰지 않도록 모든 노력을 기울여야 합니다. 숨겨진 볼륨 영역에 저장되는 데이터는 저장되지 않고 손실됩니다. Windows에서 이 오류를 쓰기 오류("쓰기 지연 실패" 또는 "파라미터가 올바르지 않습니다")로 보고할 수 있습니다.</entry>
-    <entry lang="ko" key="HIDVOL_PROT_WARN_AFTER_MOUNT_PLURAL">이제 새로 마운트된 볼륨 내의 숨겨진 각 볼륨이 마운트 해제될 때까지 손상으로부터 보호됩니다.\n\nWARNING: 이러한 볼륨의 보호되는 숨겨진 볼륨 영역에 데이터를 저장하려고 하면 VeraCrypt는 전체 볼륨(외부 및 숨겨진 부분 모두)이 마운트 해제될 때까지 쓰기 보호를 시작합니다. 이로 인해 외부 볼륨의 파일 시스템이 손상될 수 있으며, 이 경우 숨겨진 볼륨의 신뢰할 수 있는 부인성에 부정적인 영향을 미칠 수 있습니다. 따라서 숨겨진 볼륨 영역에 쓰지 않도록 모든 노력을 기울여야 합니다. 보호되는 숨겨진 볼륨 영역에 저장되는 데이터는 저장되지 않고 손실됩니다. Windows에서 이 오류를 쓰기 오류("쓰기 지연 실패" 또는 "파라미터가 올바르지 않습니다")로 보고할 수 있습니다.</entry>
+    <entry lang="ko" key="HIDVOL_PROT_WARN_AFTER_MOUNT">이제 외부 볼륨이 분리될 때까지 숨겨진 볼륨이 손상되지 않도록 보호됩니다.\n\n경고: 숨겨진 볼륨 영역에 데이터를 저장하려고 하면 VeraCrypt는 전체 볼륨(외부 및 숨겨진 부분 모두)이 마운트 해제될 때까지 쓰기 보호 기능을 시작합니다. 이로 인해 외부 볼륨의 파일 시스템이 손상될 수 있으며, 이 경우 숨겨진 볼륨의 신뢰할 수 있는 부인성에 부정적인 영향을 미칠 수 있습니다. 따라서 숨겨진 볼륨 영역에 쓰지 않도록 모든 노력을 기울여야 합니다. 숨겨진 볼륨 영역에 저장되는 데이터는 저장되지 않고 손실됩니다. Windows에서 이 오류를 쓰기 오류("쓰기 지연 실패" 또는 "파라미터가 올바르지 않습니다")로 보고할 수 있습니다.</entry>
+    <entry lang="ko" key="HIDVOL_PROT_WARN_AFTER_MOUNT_PLURAL">이제 새로 마운트된 볼륨 내의 숨겨진 각 볼륨이 마운트 해제될 때까지 손상으로부터 보호됩니다.\n\n경고: 이러한 볼륨의 보호되는 숨겨진 볼륨 영역에 데이터를 저장하려고 하면 VeraCrypt는 전체 볼륨(외부 및 숨겨진 부분 모두)이 마운트 해제될 때까지 쓰기 보호를 시작합니다. 이로 인해 외부 볼륨의 파일 시스템이 손상될 수 있으며, 이 경우 숨겨진 볼륨의 신뢰할 수 있는 부인성에 부정적인 영향을 미칠 수 있습니다. 따라서 숨겨진 볼륨 영역에 쓰지 않도록 모든 노력을 기울여야 합니다. 보호되는 숨겨진 볼륨 영역에 저장되는 데이터는 저장되지 않고 손실됩니다. Windows에서 이 오류를 쓰기 오류("쓰기 지연 실패" 또는 "파라미터가 올바르지 않습니다")로 보고할 수 있습니다.</entry>
     <entry lang="ko" key="DAMAGE_TO_HIDDEN_VOLUME_PREVENTED">경고: %c:로 마운트된 볼륨의 숨겨진 볼륨 영역에 데이터를 저장하려고 했습니다. VeraCrypt는 숨겨진 볼륨을 보호하기 위해 이러한 데이터를 저장하지 못하도록 했습니다. 이로 인해 외부 볼륨에서 파일 시스템이 손상되었을 수 있으며 Windows(윈도우)에서 쓰기 오류("쓰기 지연 실패" 또는 "파라미터가 올바르지 않습니다")를 보고했을 수 있습니다. 전체 볼륨(외부 및 숨겨진 부분 모두)이 마운트 해제될 때까지 쓰기 보호됩니다. VeraCrypt가 이 볼륨의 숨겨진 볼륨 영역에 데이터를 저장하지 못하게 한 것이 이번이 처음이 아닌 경우, 이 숨겨진 볼륨의 그럴듯한 부인성에 부정적인 영향을 미칠 수 있습니다(외부 볼륨 파일 시스템 내에서 비정상적인 상관 불일치가 발생할 수 있음). 따라서 빠른 포맷을 사용하지 않도록 설정한 상태에서 새 VeraCrypt 볼륨을 생성하고 이 볼륨에서 새 볼륨으로 파일을 이동하는 것이 좋습니다. 이 볼륨은 외부 및 숨겨진 부분 모두 안전하게 삭제해야 합니다. 지금 운영 체제를 다시 시작하는 것이 좋습니다.</entry>
     <entry lang="ko" key="CANNOT_SATISFY_OVER_4G_FILE_SIZE_REQ">4GB보다 큰 파일을 볼륨에 저장할 의도를 표시했습니다. 이렇게 하려면 볼륨을 NTFS/exFAT/ReFS로 포맷해야 합니다. 그러나 이 포맷 형식은 지원하지 않습니다.</entry>
     <entry lang="ko" key="CANNOT_CREATE_NON_HIDDEN_NTFS_VOLUMES_UNDER_HIDDEN_OS">숨겨진 운영 체제가 실행 중일 때는 숨김이 없는 VeraCrypt 볼륨을 NTFS/exFAT/ReFS로 포맷할 수 없습니다. 그 이유는 운영 체제가 NTFS로 포맷할 수 있도록 하려면 볼륨을 쓰기 보호 없이 일시적으로 마운트해야 하기 때문입니다(여기서 FAT로 포맷하는 것은 운영 체제가 아니라 VeraCrypt에서 수행되며 볼륨을 마운트하지 않습니다). 자세한 기술 정보는 아래를 참조하세요. 디코이 운영 체제 내에서 숨겨진 NTFS/exFAT/ReFS 볼륨을 생성할 수 있습니다.</entry>
@@ -617,7 +617,7 @@
     <entry lang="ko" key="KEYFILE_CHANGED">키 파일이 성공적으로 추가/제거되었습니다.</entry>
     <entry lang="ko" key="KEYFILE_EXPORTED">키 파일을 내보냄.</entry>
     <entry lang="ko" key="PKCS5_PRF_CHANGED">헤더 키 유도 알고리즘이 성공적으로 설정되었습니다.</entry>
-    <entry lang="ko" key="NONSYS_INPLACE_ENC_RESUME_PASSWORD_PAGE_HELP">내부 암호화/암호 해독 프로세스를 다시 시작할 비시스템 볼륨의 암호 및/또는 키 파일을 입력해 주십시오.\n\nRemark: 다음을 클릭하면 VeraCrypt가 암호화/암호 해독 프로세스가 중단되고 제공된 암호 및/또는 키 파일을 사용하여 VeraCrypt 볼륨 헤더를 해독할 수 있는 모든 비시스템 볼륨을 찾으려고 시도합니다. 이러한 볼륨이 두 개 이상 있는 경우 다음 단계에서 해당 볼륨 중 하나를 선택해야 합니다.</entry>
+    <entry lang="ko" key="NONSYS_INPLACE_ENC_RESUME_PASSWORD_PAGE_HELP">내부 암호화/암호 해독 프로세스를 다시 시작할 비시스템 볼륨의 암호 및/또는 키 파일을 입력해 주십시오.\n\n참고: 다음을 클릭하면 VeraCrypt가 암호화/암호 해독 프로세스가 중단되고 제공된 암호 및/또는 키 파일을 사용하여 VeraCrypt 볼륨 헤더를 해독할 수 있는 모든 비시스템 볼륨을 찾으려고 시도합니다. 이러한 볼륨이 두 개 이상 있는 경우 다음 단계에서 해당 볼륨 중 하나를 선택해야 합니다.</entry>
     <entry lang="ko" key="NONSYS_INPLACE_ENC_RESUME_VOL_SELECT_HELP">나열된 볼륨 중 하나를 선택하세요. 목록에는 암호화/암호 해독 프로세스가 중단되고 제공된 암호 및/또는 키 파일을 사용하여 볼륨 헤더의 암호 해독이 성공한 액세스 가능한 각 비시스템 볼륨 볼륨이 포함됩니다</entry>
     <entry lang="ko" key="NONSYS_INPLACE_DEC_PASSWORD_PAGE_HELP">암호를 해독할 비시스템 VeraCrypt 볼륨의 암호 및/또는 키 파일을 입력해 주십시오.</entry>
     <entry lang="ko" key="PASSWORD_HELP">올바른 암호를 선택하는 것이 매우 중요합니다. 사전에서 찾을 수 있는 단어의 하나(또는 그러한 단어의 2, 3 또는 4의 조합)만 포함하는 단어의 선택을 피해야 합니다. 이름이나 생년월일을 포함해서는 안 됩니다. 추측하기가 쉽지 않을 거예요. 좋은 암호는 대문자, 소문자, 숫자 및 특수 문자의 임의 조합(예: @^ = $ * + 등)입니다. 20자 이상으로 구성된 암호를 선택하는 것이 좋습니다(길수록 좋습니다). 가능한 최대 길이는 128자입니다.</entry>
@@ -658,7 +658,7 @@
     <entry lang="ko" key="SYSENC_MOUNT_WITHOUT_PBA_NOTE">\n\n참고: 부팅 전 인증없이 암호화 된 시스템 드라이브에있는 파티션을 마운트하거나 실행되고 있지 않은 운영 체제의 암호화 된 시스템 파티션을 마운트하려는 경우 '시스템'> '사전 부팅 인증없이 마운트'.</entry>
     <entry lang="ko" key="MOUNT_WITHOUT_PBA_VOL_ON_ACTIVE_SYSENC_DRIVE">이 모드에서는 활성 시스템 암호화의 주요 범위 내에있는 드라이브에있는 파티션을 마운트 할 수 없습니다.\n\n이 모드로이 파티션을 마운트하기 전에 다른 파티션에 설치된 운영 체제를 부팅하거나 드라이브 (암호화 또는 비 암호화) 또는 암호화되지 않은 운영 체제 부팅.</entry>
     <entry lang="ko" key="CANT_DECRYPT_PARTITION_ON_ENTIRELY_ENCRYPTED_SYS_DRIVE">VeraCrypt는 완전히 암호화 된 시스템 드라이브의 개별 파티션을 해독 할 수 없습니다(전체 시스템 드라이브 만 해독 할 수 있음).</entry>
-    <entry lang="ko" key="CANT_DECRYPT_PARTITION_ON_ENTIRELY_ENCRYPTED_SYS_DRIVE_UNSURE">경고: 드라이브에 VeraCrypt 부트 로더가 포함되어 있기 때문에 완전히 암호화 된 시스템 드라이브 일 수 있습니다. 그렇다면 VeraCrypt는 완전히 암호화 된 시스템 드라이브의 개별 파티션을 해독 할 수 없습니다(전체 시스템 드라이브 만 해독 할 수 있음). 이 경우 나중에 계속 진행할 수 있지만 나중에 'Incorrect password'오류 메시지가 나타납니다.</entry>
+    <entry lang="ko" key="CANT_DECRYPT_PARTITION_ON_ENTIRELY_ENCRYPTED_SYS_DRIVE_UNSURE">경고: 드라이브에 VeraCrypt 부트 로더가 포함되어 있기 때문에 완전히 암호화 된 시스템 드라이브 일 수 있습니다. 그렇다면 VeraCrypt는 완전히 암호화 된 시스템 드라이브의 개별 파티션을 해독 할 수 없습니다(전체 시스템 드라이브 만 해독 할 수 있음). 이 경우 지금은 계속 진행할 수 있지만 나중에 '잘못된 암호' 오류 메시지가 나타납니다.</entry>
     <entry lang="ko" key="PREV">&lt;뒤로</entry>
     <entry lang="ko" key="RAWDEVICES">시스템에 설치된 원시 장치를 나열 할 수 없습니다!</entry>
     <entry lang="ko" key="READONLYPROMPT">볼륨 '%s'이 (가) 있으며 읽기 전용입니다. 대체 하시겠습니까?</entry>
@@ -944,12 +944,12 @@
     <entry lang="ko" key="KEYFILE_EMPTY_BASE_NAME">생성 할 키 파일의 이름을 입력하세요.</entry>
     <entry lang="ko" key="KEYFILE_INVALID_BASE_NAME">키 파일의 기본 이름이 유효하지 않습니다.</entry>
     <entry lang="ko" key="KEYFILE_ALREADY_EXISTS">키 파일 '%s'이 (가) 이미 존재합니다.\n덮어 쓰시겠습니까? 대답을하지 않으면 생성 프로세스가 중지됩니다.</entry>
-    <entry lang="ko" key="HEADER_DAMAGED_AUTO_USED_HEADER_BAK">경고 :이 볼륨의 헤더가 손상되었습니다! VeraCrypt는 볼륨에 포함 된 볼륨 헤더의 백업을 자동으로 사용했습니다.\n\n'Tools'> 'Restore Volume Header'를 선택하여 볼륨 헤더를 복구해야합니다.</entry>
+    <entry lang="ko" key="HEADER_DAMAGED_AUTO_USED_HEADER_BAK">경고 :이 볼륨의 헤더가 손상되었습니다! VeraCrypt는 볼륨에 포함 된 볼륨 헤더의 백업을 자동으로 사용했습니다.\n\n'도구' > '볼륨 헤더 복원'을 선택하여 볼륨 헤더를 복구해야합니다.</entry>
     <entry lang="ko" key="VOL_HEADER_BACKED_UP">볼륨 헤더 백업이 성공적으로 완료되었습니다.\n\n중요 :이 백업을 사용하여 볼륨 헤더를 복원하면 현재 볼륨 비밀번호도 복원됩니다. 또한 키 파일이 볼륨을 마운트하는 데 필요하다면 볼륨 헤더가 복원 될 때 볼륨을 다시 마운트하는 데 동일한 키 파일이 필요합니다.\n\n주의 :이 볼륨 헤더 백업은 이 특정 볼륨의 헤더 만 복원하세요. 이 헤더 백업을 사용하여 다른 볼륨의 헤더를 복원하는 경우 볼륨을 마운트 할 수는 있지만 볼륨에 저장된 데이터는 해독 할 수 없습니다(마스터 키를 변경하기 때문에).</entry>
     <entry lang="ko" key="VOL_HEADER_RESTORED">볼륨 헤더가 성공적으로 복원되었습니다.\n\n중요: 이전 암호도 복원되었을 수 있습니다. 또한 백업을 만들 때 키 파일을 마운트해야하는 경우 볼륨을 다시 마운트하려면 동일한 키 파일이 필요합니다.</entry>
     <entry lang="ko" key="EXTERNAL_VOL_HEADER_BAK_FIRST_INFO">보안상의 이유로 볼륨에 올바른 비밀번호를 입력하거나 올바른 키 파일을 제공해야합니다.\n\n참고: 볼륨에 숨겨진 볼륨이 포함되어 있으면 올바른 비밀번호를 입력해야합니다(및/또는 올바른 볼륨의 키 파일을 제공하세요. 나중에 숨긴 볼륨의 헤더를 백업하도록 선택하면 숨겨진 볼륨에 대해 올바른 암호를 입력하거나 올바른 키 파일을 제공해야합니다.</entry>
     <entry lang="ko" key="CONFIRM_VOL_HEADER_BAK">%s의 볼륨 헤더 백업을 만드시겠습니까?\n\n예를 클릭하면 헤더 백업의 파일 이름을 묻는 메시지가 나타납니다.\n\n참고: 표준 볼륨과 숨겨진 볼륨 헤더는 모두 다시 새로운 소금으로 암호화되어 백업 파일에 저장됩니다. 이 볼륨에 숨긴 볼륨이 없으면 백업 파일의 숨겨진 볼륨 헤더 용으로 예약 된 영역이 임의의 데이터로 채워집니다(그럴듯한 거부 가능성을 유지하기 위해). 백업 파일에서 볼륨 헤더를 복원 할 때 볼륨 헤더 백업을 만들 때 유효했던/올바른 암호를 입력해야합니다(그리고/또는 올바른 키 파일을 제공해야합니다). 암호 (및/또는 키 파일)는 복원 할 볼륨 헤더 유형 (예: 표준 또는 숨김)을 자동으로 결정합니다(VeraCrypt는 시행 착오를 거쳐 유형을 결정합니다).</entry>
-    <entry lang="ko" key="CONFIRM_VOL_HEADER_RESTORE">%s의 볼륨 헤더를 복원 하시겠습니까?\n\nWARNING: 볼륨 헤더를 복원하면 백업을 만들 때 유효한 볼륨 암호도 복원됩니다. 또한 백업을 만들 때 키 파일을 마운트해야하는 경우 볼륨 헤더를 복원 한 후에 동일한 키 파일을 다시 마운트해야합니다.\n\n예를 클릭 한 후, 헤더 백업 파일을 선택합니다.</entry>
+    <entry lang="ko" key="CONFIRM_VOL_HEADER_RESTORE">%s의 볼륨 헤더를 복원 하시겠습니까?\n\n경고: 볼륨 헤더를 복원하면 백업을 만들 때 유효한 볼륨 암호도 복원됩니다. 또한 백업을 만들 때 키 파일을 마운트해야하는 경우 볼륨 헤더를 복원 한 후에 동일한 키 파일을 다시 마운트해야합니다.\n\n예를 클릭 한 후, 헤더 백업 파일을 선택합니다.</entry>
     <entry lang="ko" key="DOES_VOLUME_CONTAIN_HIDDEN">볼륨에 숨겨진 볼륨이 있습니까?</entry>
     <entry lang="ko" key="VOLUME_CONTAINS_HIDDEN">볼륨에 숨겨진 볼륨이 있습니다.</entry>
     <entry lang="ko" key="VOLUME_DOES_NOT_CONTAIN_HIDDEN">볼륨에 숨긴 볼륨이 없습니다.</entry>
@@ -994,8 +994,8 @@
     <entry lang="ko" key="SIZE_ITEM">크기:</entry>
     <entry lang="ko" key="PATH_ITEM">통로:</entry>
     <entry lang="ko" key="DRIVE_LETTER_ITEM">드라이브 문자 :</entry>
-    <entry lang="ko" key="UNSUPPORTED_CHARS_IN_PWD">오류: 암호에는 ASCII 문자 만 포함되어야합니다.\n\n암호에 ASCII가 아닌 문자로 인해 시스템 구성이 변경 될 때 볼륨을 마운트 할 수 없게 될 수 있습니다.\n\n다음 문자는 허용됩니다.\n\n! 1 2 3 4 5 6 7 8 9 :; () () * +, -./0 1 2 3 4 5 6 7 8 9: ;;;; ~ ~</entry>
-    <entry lang="ko" key="UNSUPPORTED_CHARS_IN_PWD_RECOM">경고: 암호에 비 ASCII 문자가 포함되어 있습니다. 이로 인해 시스템 구성이 변경 될 때 볼륨을 마운트 할 수 없게 될 수 있습니다.\n\n비밀번호의 비 ASCII 문자를 모두 ASCII 문자로 바꿔야합니다. 그렇게하려면 'Volumes'- &gt;'Change Volume Password'.\n\n다음은 ASCII 문자입니다 :\n\n! 1 2 3 4 5 6 7 8 9 :; () () * +, -./0 1 2 3 4 5 6 7 8 9: ;;;; ~ ~</entry>
+    <entry lang="ko" key="UNSUPPORTED_CHARS_IN_PWD">오류: 암호에는 ASCII 문자만 포함되어야합니다.\n\n암호에 ASCII가 아닌 문자가 포함되면 시스템 구성이 변경될 때 볼륨을 마운트할 수 없게 될 수 있습니다.\n\n다음 문자는 허용됩니다:\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="ko" key="UNSUPPORTED_CHARS_IN_PWD_RECOM">경고: 암호에 비 ASCII 문자가 포함되어 있습니다. 이로 인해 시스템 구성이 변경될 때 볼륨을 마운트할 수 없게 될 수 있습니다.\n\n암호의 비 ASCII 문자를 모두 ASCII 문자로 바꿔야합니다. 그렇게 하려면 '볼륨' > '볼륨 비밀번호 변경'을 선택하세요.\n\n다음은 ASCII 문자입니다:\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="ko" key="EXE_FILE_EXTENSION_CONFIRM">경고: 실행 파일 (예 :.exe,.sys 또는.dll) 및 기타 유사한 문제가되는 파일 확장명에 사용되는 파일 확장명은 사용하지 않는 것이 좋습니다. 이러한 파일 확장명을 사용하면 Windows 및 바이러스 백신 소프트웨어가 컨테이너를 방해하여 볼륨 성능에 부정적인 영향을 미치고 다른 심각한 문제가 발생할 수 있습니다.\n\n파일 확장명을 제거하거나 변경하는 것이 좋습니다(예: '.hc').\n\n문제가되는 파일 확장자를 사용 하시겠습니까?</entry>
     <entry lang="ko" key="EXE_FILE_EXTENSION_MOUNT_WARNING">경고 :이 컨테이너에는 실행 파일 (예 :.exe,.sys 또는.dll) 또는 비슷한 문제가있는 다른 파일 확장명에 사용되는 파일 확장명이 있습니다. Windows 및 바이러스 백신 소프트웨어가 컨테이너를 방해하게되어 볼륨 성능에 좋지 않은 영향을 미치고 다른 심각한 문제가 발생할 수 있습니다.\n\n컨테이너의 파일 확장자를 제거하거나 변경하는 것이 좋습니다(예: '.hc'로) 볼륨을 마운트 해제하세요.</entry>
     <entry lang="ko" key="HOMEPAGE">홈페이지</entry>
@@ -1103,8 +1103,8 @@
     <entry lang="ko" key="ALGO_NOT_SUPPORTED_FOR_SYS_ENCRYPTION">이 알고리즘은 현재 시스템 암호화에 지원되지 않습니다.</entry>
     <entry lang="ko" key="ALGO_NOT_SUPPORTED_FOR_TRUECRYPT_MODE">이 알고리즘은 TrueCrypt 모드에서는 지원되지 않습니다.</entry>
     <entry lang="ko" key="PIM_NOT_SUPPORTED_FOR_TRUECRYPT_MODE">TrueCrypt 모드에서는 PIM(개인 반복 다중 경로)이 지원되지 않습니다.</entry>
-    <entry lang="ko" key="PIM_REQUIRE_LONG_PASSWORD">지정된 PIM을 사용하려면 암호가 20자 이상이어야 합니다.\nSorter 암호는 PIM이 485 이상인 경우에만 사용할 수 있습니다.</entry>
-    <entry lang="ko" key="BOOT_PIM_REQUIRE_LONG_PASSWORD">지정된 PIM을 사용하려면 사전 부트 인증 암호가 20자 이상이어야 합니다.\nSorter 암호는 PIM이 98 이상인 경우에만 사용할 수 있습니다.</entry>
+    <entry lang="ko" key="PIM_REQUIRE_LONG_PASSWORD">지정된 PIM을 사용하려면 암호가 20자 이상이어야 합니다.\n더 짧은 암호는 PIM이 485 이상인 경우에만 사용할 수 있습니다.</entry>
+    <entry lang="ko" key="BOOT_PIM_REQUIRE_LONG_PASSWORD">지정된 PIM을 사용하려면 사전 부트 인증 암호가 20자 이상이어야 합니다.\n더 짧은 암호는 PIM이 98 이상인 경우에만 사용할 수 있습니다.</entry>
     <entry lang="ko" key="KEYFILES_NOT_SUPPORTED_FOR_SYS_ENCRYPTION">키 파일은 현재 시스템 암호화에 지원되지 않습니다.</entry>
     <entry lang="ko" key="CANNOT_RESTORE_KEYBOARD_LAYOUT">경고: VeraCrypt가 원래 키보드 레이아웃을 복원할 수 없습니다. 이로 인해 암호를 잘못 입력할 수 있습니다.</entry>
     <entry lang="ko" key="CANT_CHANGE_KEYB_LAYOUT_FOR_SYS_ENCRYPTION">오류: VeraCrypt에 대한 키보드 레이아웃을 표준 미국 키보드 레이아웃으로 설정할 수 없습니다.\n\n참고 미국 이외의 Windows 키보드 레이아웃을 사용할 수 없는 사전 부트 환경(Windows가 시작되기 전)에 암호를 입력해야 합니다. 따라서 항상 표준 미국 키보드 레이아웃을 사용하여 암호를 입력해야 합니다.</entry>
@@ -1405,10 +1405,10 @@
     <entry lang="ko" key="RESCUE_DISK_EFI_INFO">파티션을 암호화하려면 먼저 VRD(VeraCrypt 복구 디스크)를 생성해야 합니다. VRD(VeraCrypt 부트로더, 마스터 키 또는 기타 중요 데이터가 손상된 경우 VRD에서 복원할 수 있습니다(그러나 올바른 암호를 입력해야 함).\n\n- Windows가 손상되어 시작할 수 없는 경우 VRD를 사용하여 Windows가 시작되기 전에 영구적으로 파티션을 해독할 수 있습니다.\n\n- VRD에는 현재 EFI 부트 로더의 백업이 포함되어 있으며 필요한 경우 복원할 수 있습니다.\n\nVeraCrypt 복구 디스크 ZIP 이미지가 아래에 지정된 위치에 생성됩니다.</entry>
     <entry lang="ko" key="RESCUE_DISK_EFI_EXTRACT_INFO">복구 디스크 ZIP 이미지가 생성되어 이 파일에 저장되었습니다.\n%s\n이제 FAT/FAT32로 포맷된 USB 스틱으로 추출해야 합니다.\n\n%ls 복구 디스크를 생성한 후 다음을 클릭하여 디스크가 올바르게 생성되었는지 확인합니다.</entry>
     <entry lang="ko" key="RESCUE_DISK_EFI_EXTRACT_INFO_NO_CHECK">s\n\n응급 복구 디스크 ZIP 이미지가 생성되어 이 파일에 저장되었습니다 :\n%s\n\n이제 FAT/FAT32로 포맷 된 USB 스틱에 이미지를 추출하거나 나중에 사용할 수 있도록 안전한 위치로 옮겨야합니다.\n\n계속하려면 다음을 클릭하세요.</entry>
-    <entry lang="ko" key="RESCUE_DISK_EFI_EXTRACT_INFO_NOTE">중요: zip 파일을 USB 스틱의 루트에 직접 추출해야 합니다. 예를 들어 USB 스틱의 드라이브 문자가 E:인 경우 zip 파일을 추출하면 E:\\ 폴더가 생성됩니다.USB 스틱에 EFI가 있습니다.\n\n</entry>
+    <entry lang="ko" key="RESCUE_DISK_EFI_EXTRACT_INFO_NOTE">중요: zip 파일은 USB 스틱의 루트에 직접 추출해야 합니다. 예를 들어 USB 스틱의 드라이브 문자가 E:인 경우 zip 파일을 추출하면 USB 스틱에 E:\\EFI 폴더가 생성되어야 합니다.\n\n</entry>
     <entry lang="ko" key="RESCUE_DISK_EFI_CHECK_FAILED">복구 디스크가 올바르게 추출되었는지 확인할 수 없습니다.\n\n복구 디스크를 추출한 경우 USB 스틱을 꺼내고 다시 삽입한 후 다음을 클릭하여 다시 시도합니다. 도움이 되지 않는 경우 다른 USB 스틱 및/또는 다른 ZIP 소프트웨어를 사용해 주십시오.아직 복구 디스크를 추출하지 않은 경우 압축을 풀고 다음을 클릭합니다.\n\n이 마법사를 시작하기 전에 생성된 VeraCrypt 복구 디스크를 확인하려고 하면 다른 마스터 키에 대해 생성되었기 때문에 해당 복구 디스크를 사용할 수 없습니다. 새로 생성된 복구 디스크 ZIP 이미지를 추출해야 합니다.</entry>
     <entry lang="ko" key="RESCUE_DISK_EFI_NON_WIZARD_CHECK_FAILED">복구 디스크가 올바르게 추출되었는지 확인할 수 없습니다.\n\nUSB 스틱에 복구 디스크 이미지를 추출한 경우 꺼내고 다시 삽입한 다음 다시 시도합니다. 도움이 되지 않는 경우 다른 ZIP 소프트웨어 및/또는 매체를 사용해 주십시오.\n\n다른 마스터 키, 암호, 소금 등에 대해 생성된 VeraCrypt 복구 디스크를 확인하려고 하면 해당 복구 디스크가 항상 이 확인에 실패합니다. 현재 구성과 완전히 호환되는 새 복구 디스크를 생성하려면 '시스템' > '복구 디스크 생성'를 선택합니다.</entry>
-    <entry lang="ko" key="RESCUE_DISK_EFI_NON_WIZARD_CREATION">복구 디스크 이미지가 생성되어 이 파일에 저장되었습니다.\n%s\n이제 FAT/FAT32로 포맷된 USB 스틱에 복구 디스크 이미지를 추출해야 합니다.\n\nIMPORTANT: zip 파일을 USB 스틱의 루트로 직접 추출해야 합니다. 예를 들어 USB 스틱의 드라이브 문자가 E:인 경우 zip 파일을 추출하면 E:\\ 폴더가 생성됩니다.USB 스틱에 EFI가 있습니다.\n\n복구 디스크를 생성한 후 '시스템' > 'Verify 복구 디스크'를 선택하여 올바르게 생성되었는지 확인합니다.</entry>
+    <entry lang="ko" key="RESCUE_DISK_EFI_NON_WIZARD_CREATION">복구 디스크 이미지가 생성되어 다음 파일에 저장되었습니다:\n%s\n\n이제 FAT/FAT32로 포맷된 USB 스틱에 복구 디스크 이미지를 추출해야 합니다.\n\n중요: zip 파일은 USB 스틱의 루트에 직접 추출해야 합니다. 예를 들어 USB 스틱의 드라이브 문자가 E:인 경우 zip 파일을 추출하면 USB 스틱에 E:\\EFI 폴더가 생성되어야 합니다.\n\n복구 디스크를 만든 후 '시스템' > '복구 디스크 검증'을 선택하여 올바르게 생성되었는지 확인하세요.</entry>
     <entry lang="ko" key="IDC_SECURE_DESKTOP_PASSWORD_ENTRY">암호 입력에 보안 데스크톱을 사용합니다.</entry>
     <entry lang="ko" key="ERR_REFS_INVALID_VOLUME_SIZE">명령줄에 지정된 볼륨 파일 크기가 선택한 ReFS 파일 시스템과 호환되지 않습니다.</entry>
     <entry lang="ko" key="IDC_EDIT_DCSPROP">부트 로더 구성을 편집</entry>
@@ -1498,7 +1498,7 @@
     <entry lang="ko" key="LINUX_KERNEL_CRYPT_OPTION_CHANGE_MOUNTED_HINT">이 설정을 비활성화해도 커널 암호화 서비스를 통해 마운트된 볼륨에는 효과가 없을 수 있습니다.</entry>
     <entry lang="ko" key="LINUX_REMOUNT_BECAUSEOF_SETTING">현재 설정을 적용하려면 현재 마운트된 볼륨들을 다시 마운트해야 합니다.</entry>
     <entry lang="ko" key="LINUX_UNKNOWN_EXC_OCCURRED">알 수 없는 오류가 발생했습니다.</entry>
-    <entry lang="ko" key="LINUX_FIRST_AID">"'확인'을 누르면 디스크 유틸리티가 실행될 것입니다\n\n디스크 유틸리티 창에서 당신의 볼륨을 선택하고 'First Aid' 페이지에서 '디스크 확인' 혹은 '디스크 수리' 버튼을 누르십시오.</entry>
+    <entry lang="ko" key="LINUX_FIRST_AID">"'확인'을 누르면 디스크 유틸리티가 실행될 것입니다\n\n디스크 유틸리티 창에서 볼륨을 선택하고 '응급 처치' 페이지에서 '디스크 확인' 또는 '디스크 수리' 버튼을 누르십시오.</entry>
     <entry lang="ko" key="LINUX_MOUNT_ALL_DEV">모든 장치 마운트</entry>
     <entry lang="ko" key="LINUX_ERROR_LOADING_CONFIG">특정 위치의 설정 파일 불러오기 실패: </entry>
     <entry lang="ko" key="LINUX_SELECT_FREE_SLOT">리스트에서 빈 드라이브 자리를 선택하세요.</entry>
@@ -1515,7 +1515,7 @@
     <entry lang="ko" key="LINUX_ERROR_TRY_ENCRYPT_SYSTEM_PARTITION">오류: 지금 시스템 파티션을 암호화하려고 시도하고 있습니다.\n\nVeraCrypt는 Windows에서만 시스템 파티션을 암호화할 수 있습니다.</entry>
     <entry lang="ko" key="LINUX_WARNING_FORMAT_DESTROY_FS">경고: 장치를 포맷하면 '{0}'에 있는 모든 데이터가 지워집니다.\n\n계속하시겠습니까?</entry>
     <entry lang="ko" key="LINUX_MOUNTET_HINT">선택된 장치의 파일 시스템이 현재 마운트되어 있습니다. 계속하기 전에 '{0}'을 마운트 해제하십시오.</entry>
-    <entry lang="ko" key="LINUX_HIDDEN_PASS_NO_DIFF">숨겨진 볼륨은 외부 볼륨과 같은 비밀번호 혹은 PIM, 키 파일 가질 수 없습니다.The Hidden volume can't have the same password, PIM and keyfiles as the Outer volume</entry>
+    <entry lang="ko" key="LINUX_HIDDEN_PASS_NO_DIFF">숨겨진 볼륨은 외부 볼륨과 같은 비밀번호, PIM 또는 키 파일을 사용할 수 없습니다.</entry>
     <entry lang="ko" key="LINUX_NOT_FAT_HINT">모든 볼륨이 FAT 파일시스템으로 포맷되지 않고 마운트하려는 볼륨에 대해 {0}가 아닌 다른 플랫폼에서 추가로 파일 시스템 드라이브를 설치해야 할 수도 있습니다.</entry>
     <entry lang="ko" key="LINUX_KERNEL_OLD">시스템이 오래된 Linux 커널을 사용하고 있습니다.\n\nLinux 커널의 버그로 인해, VeraCrypt 볼륨으로 데이터 작성 중에 시스템이 응답을 중단할 수도 있습니다. 이 문제는 커널을 2.6.24 혹은 더 높은 버전으로 업그레이드하면 해결됩니다.</entry>
     <entry lang="ko" key="LINUX_VOL_UNMOUNTED">{0} 볼륨이 마운트 해제되었습니다.</entry>
@@ -1649,41 +1649,41 @@
     <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>
+    <entry lang="ko" key="ERR_KEY_DERIVATION_FAILED">키 파생에 실패했습니다. 메모리 부족 또는 중단된 작업으로 인해 발생했을 수 있습니다.</entry>
+    <entry lang="ko" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">시스템 파티션/드라이브는 이미 복호화되었지만 EFI Microsoft 부트 로더 경로가 Windows 부팅 관리자에 복원되지 않았습니다. EFI 부트 파일만 복구하면 됩니다. VeraCrypt 복구 디스크의 복구 옵션을 사용하거나, Windows 복구 미디어로 부팅한 뒤 W:를 Windows 볼륨의 드라이브 문자로, S:를 EFI 시스템 파티션의 드라이브 문자로 바꾸어 'bcdboot W:\\Windows /s S: /f UEFI'를 실행하세요. 경로:</entry>
+    <entry lang="ko" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">시스템 파티션/드라이브는 이미 복호화되었지만 EFI 대체 부트 로더 경로에 여전히 VeraCrypt 부트 로더가 포함되어 있습니다. EFI 부트 파일만 복구하면 됩니다. VeraCrypt 복구 디스크의 복구 옵션을 사용하거나, Windows 복구 미디어로 부팅한 뒤 W:를 Windows 볼륨의 드라이브 문자로, S:를 EFI 시스템 파티션의 드라이브 문자로 바꾸어 'bcdboot W:\\Windows /s S: /f UEFI'를 실행하세요. 경로:</entry>
+    <entry lang="ko" key="IDM_REPAIR_EFI_BOOT_LOADER">EFI 부트 로더 복구...</entry>
+    <entry lang="ko" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt는 Windows EFI 부트 로더 경로를 복원하고 VeraCrypt EFI 부트 항목과 파일을 제거합니다.\n\n시스템 파티션/드라이브가 완전히 복호화되었고 Windows가 시스템 암호화 없이 부팅될 수 있는 경우에만 사용하세요.\n\n계속하시겠습니까?</entry>
+    <entry lang="ko" key="EFI_BOOT_LOADER_FILE_READ_FAILED">EFI 부트 로더 파일을 완전히 읽을 수 없습니다:</entry>
+    <entry lang="ko" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">EFI 부트 로더 파일이 예상보다 커서 검사하지 않았습니다:</entry>
+    <entry lang="ko" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">시스템 파티션/드라이브는 이미 복호화되었고 EFI 부트 로더 파일도 복원되었지만, VeraCrypt가 하나 이상의 VeraCrypt 펌웨어 부트 항목을 제거하지 못했습니다. 남아 있는 펌웨어 항목이 여전히 존재하는 로더를 가리키도록 VeraCrypt EFI 파일은 그대로 두었습니다. 관리자 권한으로 다시 시도하거나 Windows 부팅 관리자가 정상적으로 시작되는지 확인한 후 펌웨어 설정에서 VeraCrypt 부트 항목을 제거하세요.</entry>
+    <entry lang="ko" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">시스템 암호화 또는 복호화가 진행 중이거나 완료되지 않은 동안에는 EFI 부트 로더를 복구할 수 없습니다. 다시 시도하기 전에 보류 중인 시스템 암호화/복호화 프로세스를 완료하거나 재개하세요.</entry>
+    <entry lang="ko" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">이 복구 작업은 GPT 시스템 파티션에서 UEFI 모드로 부팅하는 시스템에서만 사용할 수 있습니다.</entry>
+    <entry lang="ko" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">EFI 부트 로더가 성공적으로 복구되었습니다.</entry>
+    <entry lang="ko" key="PIM_ARGON2_HELP">PIM(Personal Iterations Multiplier)은 Argon2id 헤더 키 파생에 사용되는 메모리 및 시간 비용을 다음과 같이 제어합니다:\n      메모리 = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      반복 = PIM이 31 이하인 경우 3 + ((PIM - 1) / 3), 31보다 큰 경우 13 + (PIM - 31)\n\n비어 두거나 0으로 설정한 경우 VeraCrypt는 416 MiB의 메모리와 6회 반복을 사용하는 기본 Argon2 PIM(12)을 사용합니다.\n\n암호가 20자 미만인 경우 최소 보안 수준을 유지하기 위해 Argon2 PIM은 12보다 작으면 안 됩니다.\n암호가 20자 이상인 경우 Argon2 PIM을 임의의 값으로 설정할 수 있습니다.\n\nArgon2 PIM 값이 12보다 크면 메모리 사용량이 최대 1024 MiB까지 증가한 다음 반복 횟수가 증가합니다. 이로 인해 마운트 속도가 느려집니다. Argon2 PIM 값이 작으면(12 미만) 마운트 속도가 빨라지지만 암호의 강도가 충분하지 않으면 보안을 줄일 수 있습니다.</entry>
+    <entry lang="ko" key="PIM_ARGON2_LARGE_WARNING">VeraCrypt 기본값보다 큰 Argon2 PIM 값을 선택했습니다.\n이 설정은 더 많은 메모리를 필요로 하고 마운트 속도를 훨씬 느리게 할 수 있습니다.</entry>
+    <entry lang="ko" key="PIM_ARGON2_SMALL_WARNING">VeraCrypt 기본값보다 작은 Argon2 PIM 값을 선택했습니다. 암호의 강도가 충분하지 않으면 보안이 약해질 수 있습니다.\n\n강력한 암호를 사용하고 있는지 확인하시겠습니까?</entry>
+    <entry lang="ko" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">지정한 Argon2 PIM을 사용하려면 암호가 20자 이상이어야 합니다.\n더 짧은 암호는 Argon2 PIM이 12 이상인 경우에만 사용할 수 있습니다.</entry>
+    <entry lang="ko" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER">Linux 커널 내 드라이버로 NTFS 볼륨 마운트</entry>
+    <entry lang="ko" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Linux 전용. 활성화되어 있고 명시적인 파일 시스템 유형이 제공되지 않은 경우, VeraCrypt는 blkid -p로 복호화된 가상 장치를 검사하고 사용 가능한 커널 내 NTFS 드라이버로 감지된 NTFS 파일 시스템을 마운트하여 ntfs-3g 같은 마운트 도우미를 우회합니다. VeraCrypt는 최신 읽기/쓰기 드라이버로 확실히 식별되거나 Linux 커널 7.1 이상에서 예상되는 경우 ntfs를 사용하고, 그 외에는 ntfs3를 사용합니다. NTFS 감지에 실패하면 VeraCrypt는 일반 자동 파일 시스템 선택을 사용합니다. 지원되는 커널 내 NTFS 드라이버가 없거나 로드할 수 없으면 마운트가 실패합니다. 이 선택 옵션은 동결된 사용자 공간 FUSE 파일 시스템으로 인한 절전 또는 최대 절전 모드 멈춤 현상을 피할 수 있습니다.</entry>
+    <entry lang="ko" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">지원되는 커널 내 NTFS 드라이버가 없거나 로드할 수 없습니다. 시스템 기본 NTFS 백엔드를 사용하려면 NTFS 커널 드라이버 설정을 비활성화하거나 커널 NTFS를 명시적으로 요청하지 마세요.</entry>
+    <entry lang="ko" key="LINUX_EMERGENCY_UNMOUNT_WARNING">볼륨 {0}의 일반 마운트 해제에 실패했습니다. 애플리케이션이 아직 볼륨의 파일 또는 디렉터리를 열어 두었거나, 기반 장치가 연결 해제되어 마운트 상태가 유효하지 않게 된 경우에 발생할 수 있습니다.\n\n장치가 아직 연결되어 있으면 '아니요'를 선택하고, 볼륨을 사용하는 애플리케이션을 닫은 다음 다시 마운트 해제를 시도하세요.\n\n장치가 연결 해제되었거나 마운트 상태가 유효하지 않으면 VeraCrypt가 파일 시스템을 지연 분리하고 VeraCrypt 커널 객체를 제거하거나 제거 예약하여 긴급 정리를 시도할 수 있습니다. 보류 중인 쓰기가 실패했을 수 있고, 데이터가 손실될 수 있으며, 애플리케이션이 열린 파일을 닫을 때까지 정리가 보류 상태로 남을 수 있습니다. 다시 사용하기 전에 fsck 또는 적절한 복구 도구로 파일 시스템을 확인하세요.\n\n계속하시겠습니까?</entry>
+    <entry lang="ko" key="LINUX_EMERGENCY_UNMOUNTED">볼륨 {0}에 대한 긴급 정리가 시작되었습니다. 장치가 연결 해제되었거나 마운트 상태가 유효하지 않았거나 보류 중인 쓰기가 있었다면, 다시 사용하기 전에 fsck 또는 적절한 복구 도구로 파일 시스템을 확인하세요.</entry>
+    <entry lang="ko" key="FORMAT_STAGE_WRITING_DATA">볼륨 데이터를 생성 중입니다. 기다려 주세요.</entry>
+    <entry lang="ko" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">볼륨 생성 마무리 중: 백업 헤더를 쓰는 중입니다.</entry>
+    <entry lang="ko" key="FORMAT_STAGE_FLUSHING_DATA">볼륨 생성 마무리 중: 데이터를 디스크로 플러시하는 중입니다. 대용량 볼륨 또는 느린/USB 저장소에서는 몇 분이 걸릴 수 있습니다.</entry>
+    <entry lang="ko" key="FORMAT_STAGE_FINISHED">볼륨 생성을 마무리하는 중입니다.</entry>
+    <entry lang="ko" key="FORMAT_STAGE_ABORTED">볼륨 생성이 중단되었습니다.</entry>
+    <entry lang="ko" key="FORMAT_STAGE_ERROR">볼륨 생성에 실패했습니다.</entry>
+    <entry lang="ko" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">볼륨 생성 마무리 중: 임시 볼륨을 마운트하는 중입니다.</entry>
+    <entry lang="ko" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">볼륨 생성 마무리 중: 임시 장치를 준비하는 중입니다.</entry>
+    <entry lang="ko" key="FORMAT_STAGE_CREATING_FILESYSTEM">볼륨 생성 마무리 중: {0}을(를) 사용하여 파일 시스템을 생성하는 중입니다.</entry>
+    <entry lang="ko" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">볼륨 생성 마무리 중: 임시 볼륨을 마운트 해제하는 중입니다.</entry>
+    <entry lang="ko" key="MACOSX_APFS_SYNTHESIZED_DEVICE">선택한 장치 '{0}'은 APFS 합성 컨테이너 또는 볼륨이므로 원시 VeraCrypt 볼륨 호스트로 사용할 수 없습니다.\n\n대신 물리적 APFS 저장소 파티션{1}을 선택하세요.</entry>
+    <entry lang="ko" key="MACOSX_DEVICE_SYSTEM_PARTITION">선택한 장치 '{0}'은 macOS 시스템/지원 파티션이므로 VeraCrypt 볼륨 호스트로 사용할 수 없습니다.</entry>
+    <entry lang="ko" key="MACOSX_APFS_SYSTEM_STORE">선택한 APFS 물리적 저장소 '{0}'에는 현재 마운트된 macOS 시스템 볼륨이 포함되어 있으므로 VeraCrypt 볼륨 호스트로 사용할 수 없습니다.</entry>
+    <entry lang="ko" key="MACOSX_DEVICE_NOT_WRITABLE">macOS에서 선택한 장치 '{0}'을 읽기 전용으로 보고했습니다. 쓰기 가능한 물리적 파티션 또는 디스크를 선택하세요.</entry>
+    <entry lang="ko" 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.pt-br.xml

@@ -1643,47 +1643,47 @@
     <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>
+    <entry lang="pt-br" key="IDT_KDF_ALGO">Algoritmo KDF</entry>
+    <entry lang="pt-br" key="IDD_PREFERENCES_TAB_GENERAL">Geral</entry>
+    <entry lang="pt-br" key="IDD_PREFERENCES_TAB_ACTIONS">Ações</entry>
+    <entry lang="pt-br" key="IDD_PREFERENCES_TAB_PASSWORD">Senha</entry>
+    <entry lang="pt-br" key="IDC_SECURE_DESKTOP_ENABLE_IME">Ativar Editor de Método de Entrada (IME) na Área de Trabalho Segura</entry>
+    <entry lang="pt-br" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">AVISO: Ative esta opção somente se você estiver encontrando problemas ao selecionar Arquivos-chave/Tokens na Área de Trabalho Segura.</entry>
+    <entry lang="pt-br" key="ERR_KEY_DERIVATION_FAILED">Falha na derivação da chave. Isso pode ser causado por memória insuficiente ou por uma operação interrompida.</entry>
+    <entry lang="pt-br" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">A partição/unidade do sistema já está descriptografada, mas o caminho do carregador de inicialização EFI da Microsoft não foi restaurado para o Gerenciador de Inicialização do Windows. Apenas os arquivos de inicialização EFI precisam ser reparados. Use a opção de reparo do Disco de Resgate VeraCrypt ou inicialize uma mídia de recuperação do Windows e execute 'bcdboot W:\\Windows /s S: /f UEFI' depois de substituir W: pela letra da unidade do volume do Windows e S: pela letra da unidade da Partição do Sistema EFI. Caminho:</entry>
+    <entry lang="pt-br" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">A partição/unidade do sistema já está descriptografada, mas o caminho do carregador de inicialização EFI de fallback ainda contém o Carregador de Inicialização do VeraCrypt. Apenas os arquivos de inicialização EFI precisam ser reparados. Use a opção de reparo do Disco de Resgate VeraCrypt ou inicialize uma mídia de recuperação do Windows e execute 'bcdboot W:\\Windows /s S: /f UEFI' depois de substituir W: pela letra da unidade do volume do Windows e S: pela letra da unidade da Partição do Sistema EFI. Caminho:</entry>
+    <entry lang="pt-br" key="IDM_REPAIR_EFI_BOOT_LOADER">Reparar Carregador de Inicialização EFI...</entry>
+    <entry lang="pt-br" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">O VeraCrypt restaurará os caminhos do carregador de inicialização EFI do Windows e removerá as entradas e arquivos de inicialização EFI do VeraCrypt.\n\nUse isto somente depois que a partição/unidade do sistema estiver totalmente descriptografada e o Windows puder inicializar sem criptografia do sistema.\n\nDeseja continuar?</entry>
+    <entry lang="pt-br" key="EFI_BOOT_LOADER_FILE_READ_FAILED">O arquivo do carregador de inicialização EFI não pôde ser lido completamente:</entry>
+    <entry lang="pt-br" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">O arquivo do carregador de inicialização EFI é inesperadamente grande e não foi inspecionado:</entry>
+    <entry lang="pt-br" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">A partição/unidade do sistema já está descriptografada e os arquivos do carregador de inicialização EFI foram restaurados, mas o VeraCrypt não pôde remover uma ou mais entradas de inicialização do firmware do VeraCrypt. Os arquivos EFI do VeraCrypt foram deixados no lugar para que qualquer entrada de firmware restante ainda aponte para um carregador existente. Tente novamente como Administrador ou remova a entrada de inicialização do VeraCrypt na configuração do firmware depois de confirmar que o Gerenciador de Inicialização do Windows inicia normalmente.</entry>
+    <entry lang="pt-br" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">O carregador de inicialização EFI não pode ser reparado enquanto a criptografia ou descriptografia do sistema estiver ativa ou incompleta. Conclua ou retome o processo pendente de criptografia/descriptografia do sistema antes de tentar novamente.</entry>
+    <entry lang="pt-br" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">Esta ação de reparo está disponível apenas em sistemas que inicializam em modo UEFI a partir de uma partição de sistema GPT.</entry>
+    <entry lang="pt-br" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">O carregador de inicialização EFI foi reparado com sucesso.</entry>
+    <entry lang="pt-br" key="PIM_ARGON2_HELP">PIM (Multiplicador de Iterações Pessoais) controla os custos de memória e tempo usados pela derivação da chave de cabeçalho Argon2id da seguinte forma:\n      Memória = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iterações = 3 + ((PIM - 1) / 3) para PIM 31 ou menor; depois, 13 + (PIM - 31)\n\nQuando deixado vazio ou definido como 0, o VeraCrypt usará o PIM Argon2 padrão (12), que usa 416 MiB de memória e 6 iterações.\n\nQuando a senha tiver menos de 20 caracteres, o PIM Argon2 não pode ser menor que 12 para manter um nível mínimo de segurança.\nQuando a senha tiver 20 caracteres ou mais, o PIM Argon2 pode ser definido como qualquer valor.\n\nUm PIM Argon2 maior que 12 aumenta o uso de memória até 1024 MiB e depois aumenta as iterações. Isso resultará em uma montagem mais lenta. Um PIM Argon2 pequeno (menor que 12) resultará em uma montagem mais rápida, mas poderá reduzir a segurança caso a senha não seja suficientemente forte.</entry>
+    <entry lang="pt-br" key="PIM_ARGON2_LARGE_WARNING">Você escolheu um valor de PIM Argon2 maior que o valor padrão do VeraCrypt.\nObserve que isso pode exigir mais memória e resultar em montagem muito mais lenta.</entry>
+    <entry lang="pt-br" key="PIM_ARGON2_SMALL_WARNING">Você escolheu um valor de PIM Argon2 menor que o valor padrão do VeraCrypt. Observe que, se sua senha não for suficientemente forte, isso poderá reduzir a segurança.\n\nVocê confirma que está usando uma senha forte?</entry>
+    <entry lang="pt-br" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">A senha deve conter 20 caracteres ou mais para usar o PIM Argon2 especificado.\nSenhas mais curtas só podem ser usadas se o PIM Argon2 for 12 ou maior.</entry>
+    <entry lang="pt-br" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER">Montar volumes NTFS com um driver Linux integrado ao kernel</entry>
+    <entry lang="pt-br" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Somente Linux. Quando ativada e nenhum tipo explícito de sistema de arquivos tiver sido fornecido, o VeraCrypt examina o dispositivo virtual descriptografado com blkid -p e monta sistemas de arquivos NTFS detectados com um driver NTFS disponível integrado ao kernel, contornando auxiliares de montagem como ntfs-3g. O VeraCrypt usa ntfs quando ele é identificado positivamente como um driver moderno de leitura/gravação ou esperado no Linux 7.1 ou posterior; caso contrário, usa ntfs3. Se a detecção de NTFS falhar, o VeraCrypt usa a seleção automática normal do sistema de arquivos. Se nenhum driver NTFS integrado ao kernel suportado estiver disponível ou puder ser carregado, a montagem falhará. Esta opção, que deve ser ativada explicitamente, pode evitar travamentos ao suspender ou hibernar causados por sistemas de arquivos FUSE congelados em espaço de usuário.</entry>
+    <entry lang="pt-br" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">Nenhum driver NTFS integrado ao kernel suportado está disponível ou pode ser carregado. Para usar o mecanismo NTFS padrão do sistema, desative a preferência de driver NTFS do kernel ou não solicite explicitamente o uso de NTFS pelo kernel.</entry>
+    <entry lang="pt-br" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Falha na desmontagem normal do volume {0}. Isso pode acontecer quando aplicativos ainda têm arquivos ou diretórios abertos no volume, ou quando o dispositivo subjacente foi desconectado e a montagem ficou inválida.\n\nSe o dispositivo ainda estiver conectado, escolha Não, feche os aplicativos que estejam usando o volume e tente desmontá-lo novamente.\n\nSe o dispositivo foi desconectado ou a montagem está inválida, o VeraCrypt pode tentar uma limpeza de emergência por meio da desmontagem diferida do sistema de arquivos e da remoção ou agendamento de remoção de objetos do kernel do VeraCrypt. Gravações pendentes podem ter falhado, dados podem ser perdidos, e a limpeza pode permanecer pendente até que os aplicativos fechem os arquivos abertos. Verifique o sistema de arquivos com fsck ou a ferramenta de reparo apropriada antes de usá-lo novamente.\n\nContinuar?</entry>
+    <entry lang="pt-br" key="LINUX_EMERGENCY_UNMOUNTED">A limpeza de emergência do volume {0} foi iniciada. Se o volume foi desconectado, a montagem ficou inválida ou havia gravações pendentes, verifique o sistema de arquivos com fsck ou a ferramenta de reparo apropriada antes de usá-lo novamente.</entry>
+    <entry lang="pt-br" key="FORMAT_STAGE_WRITING_DATA">Criando dados do volume. Por favor, aguarde.</entry>
+    <entry lang="pt-br" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Finalizando a criação do volume: gravando cabeçalho de backup.</entry>
+    <entry lang="pt-br" key="FORMAT_STAGE_FLUSHING_DATA">Finalizando a criação do volume: sincronizando dados no disco. Isso pode levar vários minutos em volumes grandes ou em armazenamento lento ou USB.</entry>
+    <entry lang="pt-br" key="FORMAT_STAGE_FINISHED">Finalizando a criação do volume.</entry>
+    <entry lang="pt-br" key="FORMAT_STAGE_ABORTED">A criação do volume foi abortada.</entry>
+    <entry lang="pt-br" key="FORMAT_STAGE_ERROR">Falha na criação do volume.</entry>
+    <entry lang="pt-br" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Finalizando a criação do volume: montando volume temporário.</entry>
+    <entry lang="pt-br" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Finalizando a criação do volume: preparando dispositivo temporário.</entry>
+    <entry lang="pt-br" key="FORMAT_STAGE_CREATING_FILESYSTEM">Finalizando a criação do volume: criando sistema de arquivos usando {0}.</entry>
+    <entry lang="pt-br" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Finalizando a criação do volume: desmontando volume temporário.</entry>
+    <entry lang="pt-br" key="MACOSX_APFS_SYNTHESIZED_DEVICE">O dispositivo selecionado '{0}' é um contêiner ou volume APFS sintetizado e não pode ser usado como host de volume VeraCrypt em modo bruto.\n\nSelecione a partição física de armazenamento APFS{1} em vez disso.</entry>
+    <entry lang="pt-br" key="MACOSX_DEVICE_SYSTEM_PARTITION">O dispositivo selecionado '{0}' é uma partição de sistema/suporte do macOS e não pode ser usado como host de volume VeraCrypt.</entry>
+    <entry lang="pt-br" key="MACOSX_APFS_SYSTEM_STORE">O armazenamento físico APFS selecionado '{0}' contém o volume de sistema macOS atualmente montado e não pode ser usado como host de volume VeraCrypt.</entry>
+    <entry lang="pt-br" key="MACOSX_DEVICE_NOT_WRITABLE">O macOS informa que o dispositivo selecionado '{0}' é somente leitura. Selecione uma partição física ou disco gravável.</entry>
+    <entry lang="pt-br" key="MACOSX_APFS_EROFS_HINT">O macOS informou que o dispositivo selecionado é somente leitura. Se for um disco APFS, certifique-se de ter selecionado a partição física de armazenamento APFS, não um volume APFS sintetizado. Use o Utilitário de Disco ou 'diskutil list' para identificar a partição física e tente novamente.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.sl.xml

@@ -703,7 +703,7 @@
     <entry lang="sl" key="VOL_MOUNT_FAILED">Prišlo je do napake pri poskusu priklopa nosilca.</entry>
     <entry lang="sl" key="VOL_SEEKING">Napaka pri iskanju lokacije v nosilcu.</entry>
     <entry lang="sl" key="VOL_SIZE_WRONG">Napaka: Napačna velikost nosilca.</entry>
-    <entry lang="sl" key="WARN_QUICK_FORMAT">OPOZORILO: Hitro formatiranje uporabljaj le v naslednjih primerih:\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 Quick Format?</entry>
+    <entry lang="sl" key="WARN_QUICK_FORMAT">OPOZORILO: Hitro formatiranje uporabljaj le v naslednjih primerih:\n\n1) Naprava ne vsebuje občutljivih podatkov in ne potrebuješ verjetnega zanikanja.\n2) Naprava je že varno in v celoti šifrirana.\n\nAli si prepričan, da želiš uporabiti hitro formatiranje?</entry>
     <entry lang="sl" key="CONFIRM_SPARSE_FILE">Dinamični vsebnik je vnaprej dodeljena redka datoteka NTFS, katere fizična velikost (dejanski uporabljen prostor na disku) raste z dodajanjem novih podatkov.\n\nOPOZORILO: Zmogljivost nosilcev, ki gostujejo v redkih datotekah, je znatno slabša od zmogljivosti običajnih nosilcev. Nosilci, ki gostujejo v redkih datotekah, so tudi manj varni, saj je mogoče ugotoviti, kateri sektorji nosilcev so neuporabljeni. Poleg tega nosilci, ki gostujejo v redkih datotekah, ne morejo zagotoviti verjetnega zanikanja (gostujejo skriti nosilec). Upoštevaj tudi, da če se podatki zapišejo v vsebnik redke datoteke, ko v gostiteljskem datotečnem sistemu ni dovolj prostega prostora, se lahko šifrirani datotečni sistem poškoduje.\n\nAli si prepričan, da želiš ustvariti nosilec, ki gostuje v redki datoteki ?</entry>
     <entry lang="sl" key="SPARSE_FILE_SIZE_NOTE">Upoštevaj, da bo velikost dinamičnega vsebnika, ki jo poročata Windows in VeraCrypt, vedno enaka njegovi največji velikosti. Če želiš izvedeti trenutno fizično velikost vsebnika (dejanski prostor na disku, ki ga uporablja), z desno miškino tipko klikni datoteko vsebnika (v oknu Windows Raziskovalca, ne v VeraCryptu), nato izberi 'Lastnosti' in si oglej vrednost 'Velikost na disku'. \n\nUpoštevaj tudi, da če premakneš dinamični vsebnik na drug nosilec ali pogon, bo fizična velikost vsebnika povečana do maksimuma. (To lahko preprečiš tako, da ustvariš nov dinamični vsebnik na ciljni lokaciji, ga namestiš in nato premakneš datoteke iz starega vsebnika v novega.)</entry>
     <entry lang="sl" key="PASSWORD_CACHE_WIPED_SHORT">Predpomnilnik gesla je zbrisan</entry>
@@ -1076,7 +1076,7 @@
     <entry lang="sl" key="FEATURE_REQUIRES_INSTALLATION">Napaka: Ta funkcija zahteva, da je VeraCrypt nameščen v sistemu (VeraCrypt uporabljaš v prenosnem načinu).\n\nProsimo, namesti VeraCrypt in poskusi znova.</entry>
     <entry lang="sl" key="WINDOWS_NOT_ON_BOOT_DRIVE_ERROR">OPOZORILO: Zdi se, da Windows ni nameščen na pogonu, s katerega se zažene. To ni podprto.\n\nNadaljuj samo, če si prepričan, da je Windows nameščen na pogonu, s katerega se zaganja.\n\nAli želiš nadaljevati?</entry>
     <entry lang="sl" key="TC_BOOT_LOADER_ALREADY_INSTALLED">POZOR: Zagonski nalagalnik VeraCrypt je že nameščen na tvojem sistemskem pogonu!\n\nMožno je, da je drug sistem v vašem računalniku že šifriran.\n\nOPOZORILO: NADALJEVANJE ŠIFRIRANJA TRENUTNO TEKOČEGA SISTEMA LAHKO ONEMOGOČI ZAGON DRUGIH SISTEMOV IN POVEZANI PODATKI SO LAHKO NEDOSTOPNI.\n\nSi prepričan, da želiš nadaljevati?</entry>
-    <entry lang="sl" key="SYS_LOADER_RESTORE_FAILED">Obnovitev izvirnega sistemskega nalagalnika ni uspela.\n\nUporabi svoj reševalni disk VeraCrypt ('Možnosti popravila' &gt; 'Obnovi izvirni sistemski nalagalnik') ali namestitveni medij Windows, da zamenjaš zagonski nalagalnik VeraCrypt s sistemskim nalagalnikom Windows.</entry>
+    <entry lang="sl" key="SYS_LOADER_RESTORE_FAILED">Obnovitev izvirnega sistemskega nalagalnika ni uspela.\n\nUporabi svoj reševalni disk VeraCrypt ('Repair Options' &gt; 'Restore original system loader') ali namestitveni medij Windows, da zamenjaš zagonski nalagalnik VeraCrypt s sistemskim nalagalnikom Windows.</entry>
     <entry lang="sl" key="SYS_LOADER_UNAVAILABLE_FOR_RESCUE_DISK">Izvirni nalagalnik sistema ne bo shranjen na reševalni disk (verjeten vzrok: manjkajoča varnostna kopija).</entry>
     <entry lang="sl" key="ERROR_MBR_PROTECTED">Zapis v sektor MBR ni uspel.\n\nTvoj BIOS je morda konfiguriran za zaščito sektorja MBR. Preveri nastavitve BIOSa za MBR/protivirusno zaščito (pritisni F2, Delete ali Esc po vklopu računalnika).</entry>
     <entry lang="sl" key="BOOT_LOADER_FINGERPRINT_CHECK_FAILED">OPOZORILO: Preverjanje prstnega odtisa zagonskega nalagalnika VeraCrypt ni uspelo!\nV tvoj disk je morda posegel napadalec (napad »Evil Maid«).\n\nTo opozorilo se lahko sproži tudi, če si obnovil zagonski nalagalnik VeraCrypt z uporabo reševalnega diska, ustvarjenega z drugo različico VeraCrypt.\n\nSvetujemo ti, da takoj spremeniš svoje geslo, s čimer boš obnovil tudi pravilen zagonski nalagalnik VeraCrypt. Priporočljivo je, da znova namestiš VeraCrypt in sprejmeš ukrepe za preprečitev dostopa do tega računalnika s strani subjektov, ki jim ne zaupaš.</entry>
@@ -1153,7 +1153,7 @@
     <entry lang="sl" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Ali je v glavnem zagonskem zapisu (MBR) nameščen zagonski nalagalnik (ali upravnik zagona), ki ni Windows?\n\nOpomba: Če na primer prva steza zagonskega pogona vsebuje GRUB, LILO, XOSL ali kakšen drug  upravnik zagona (zagonski nalagalnik) ki ni od Windows, izberi »Da«.</entry>
     <entry lang="sl" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Zagon po izboru</entry>
     <entry lang="sl" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt trenutno ne podpira konfiguracij z več zagoni, kjer je v glavnem zagonskem zapisu nameščen zagonski nalagalnik, ki ni sistem Windows.\n\nMožne rešitve:\n\n- Če za zagon Windows in Linux uporabljaš upravnik zagona, premakni zagon upravnika (običajno GRUB) iz glavnega zagonskega zapisa v particijo. Nato znova zaženi ta čarovnik in šifriraj sistemsko particijo/pogon. Upoštevaj, da bo zagonski nalagalnik VeraCrypt postal tvoj primarni zagonski upravnik in ti bo omogočil zagon prvotnega zagonskega upravnika (npr. GRUB) kot sekundarnega zagonskega upravnika (s pritiskom Esc na zaslonu zagonskega nalagalnika VeraCrypt) in tako boš lahko zagnal Linux.</entry>
-    <entry lang="sl" key="WINDOWS_BOOT_LOADER_HINTS">Če je operacijski sistem, ki se trenutno izvaja, nameščen na zagonski particiji, boš moral vnesti pravilno geslo, potem ko ga šifriraš, tudi če želiš zagnati kateri koli drugi nešifrirani sistem(-e) Windows (saj si bodo delili en šifriran Zagonski nalagalnik/upravljalnik Windows).\n\nV nasprotju s tem, če trenutno delujoči operacijski sistem ni nameščen na zagonski particiji (ali če zagonskega nalagalnika/upravljalnika Windows ne uporablja noben drug sistem), potem, ko šifriraš ta sistem, ti ne bo treba vnesti pravilnega gesla za zagon drugih nešifriranih sistemov -- za zagon nešifriranega sistema boš moral samo pritisniti tipko Esc (če obstaja več nešifriranih sistemov, boš moral tudi izbrati v meniju VeraCrypt Boot Manager, kateri sistem želiš zagnati).\n\nOpomba: Običajno je na zagonsko particijo nameščen prvi nameščen sistem Windows.</entry>
+    <entry lang="sl" key="WINDOWS_BOOT_LOADER_HINTS">Če je operacijski sistem, ki se trenutno izvaja, nameščen na zagonski particiji, boš moral vnesti pravilno geslo, potem ko ga šifriraš, tudi če želiš zagnati kateri koli drugi nešifrirani sistem(-e) Windows (saj si bodo delili en šifriran zagonski nalagalnik/upravljalnik Windows).\n\nV nasprotju s tem, če trenutno delujoči operacijski sistem ni nameščen na zagonski particiji (ali če zagonskega nalagalnika/upravljalnika Windows ne uporablja noben drug sistem), potem, ko šifriraš ta sistem, ti ne bo treba vnesti pravilnega gesla za zagon drugih nešifriranih sistemov -- za zagon nešifriranega sistema boš moral samo pritisniti tipko Esc (če obstaja več nešifriranih sistemov, boš moral tudi izbrati v meniju upravitelja zagona VeraCrypt, kateri sistem želiš zagnati).\n\nOpomba: Običajno je na zagonsko particijo nameščen prvi nameščen sistem Windows.</entry>
     <entry lang="sl" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Šifriranje zaščitenega področja na gostitelju</entry>
     <entry lang="sl" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">Na koncu mnogih pogonov je območje, ki je običajno skrito pred operacijskim sistemom (takšna območja se običajno imenujejo zaščitena območja gostitelja). Nekateri programi pa lahko berejo in zapisujejo podatke iz/na taka področja.\n\nOPOZORILO: Nekateri proizvajalci računalnikov lahko uporabljajo taka področja za shranjevanje orodij in podatkov za RAID, obnovitev sistema, nastavitev sistema, diagnostiko ali druge namene. Če morajo biti takšna orodja ali podatki dostopni pred zagonom, skrito območje NE sme biti šifrirano (zgoraj izberi »Ne«).\n\nAli želiš, da VeraCrypt zazna in šifrira tako skrito območje (če obstaja) na koncu sistemski pogon?</entry>
     <entry lang="sl" key="SYSENC_TYPE_PAGE_TITLE">Tip sistemskega šifriranja</entry>
@@ -1165,7 +1165,7 @@
     <entry lang="sl" key="SYSENC_DRIVE_ANALYSIS_TITLE">Odkrivanje skritih sektorjev</entry>
     <entry lang="sl" key="SYSENC_DRIVE_ANALYSIS_INFO">Počakaj, da VeraCrypt zazna morebitne skrite sektorje na koncu sistemskega pogona. Upoštevaj, da lahko traja dolgo časa, da se dokonča.\n\nOpomba: V zelo redkih primerih se lahko na nekaterih računalnikih sistem med tem postopkom zaznavanja neha odzivati. Če se to zgodi, znova zaženi računalnik, zaženi VeraCrypt, ponovi prejšnje korake, vendar preskoči ta postopek zaznavanja. Upoštevaj, da te težave ne povzroča napaka v VeraCryptu.</entry>
     <entry lang="sl" key="SYS_ENCRYPTION_SPAN_TITLE">Področje za šifriranje</entry>
-    <entry lang="sl" key="SYS_ENCRYPTION_SPAN_WHOLE_SYS_DRIVE_HELP">Izberi to možnost, če želiš šifrirati celoten pogon, na katerem je nameščen trenutno delujoč sistem Windows. Celoten pogon, vključno z vsemi njegovimi particijami, bo šifriran, razen prve steze, kjer bo VeraCrypt Boot Loader. Vsakdo, ki želi dostopati do sistema, nameščenega na disku, ali datotek, shranjenih na disku, bo moral vsakič pred zagonom sistema vnesti pravilno geslo. Te možnosti ni mogoče uporabiti za šifriranje sekundarnega ali zunanjega pogona, če Windows ni nameščen na njem in se ne zažene z njega.</entry>
+    <entry lang="sl" key="SYS_ENCRYPTION_SPAN_WHOLE_SYS_DRIVE_HELP">Izberi to možnost, če želiš šifrirati celoten pogon, na katerem je nameščen trenutno delujoč sistem Windows. Celoten pogon, vključno z vsemi njegovimi particijami, bo šifriran, razen prve steze, kjer bo zagonski nalagalnik VeraCrypt. Vsakdo, ki želi dostopati do sistema, nameščenega na disku, ali datotek, shranjenih na disku, bo moral vsakič pred zagonom sistema vnesti pravilno geslo. Te možnosti ni mogoče uporabiti za šifriranje sekundarnega ali zunanjega pogona, če Windows ni nameščen na njem in se ne zažene z njega.</entry>
     <entry lang="sl" key="COLLECTING_RANDOM_DATA_TITLE">Zbiranje naključnih podatkov</entry>
     <entry lang="sl" key="KEYS_GEN_TITLE">Ključi proizvedeni</entry>
     <entry lang="sl" key="CD_BURNER_NOT_PRESENT">VeraCrypt ni našel zapisovalnika CD-jev/DVD-jev, priključenega na tvoj računalnik. VeraCrypt potrebuje zapisovalnik CD/DVD za zapisovanje zagonskega reševalnega diska VeraCrypt, ki vsebuje varnostno kopijo šifrirnih ključev, zagonskega nalagalnika VeraCrypt, izvirnega sistemskega nalagalnika itd.\n\nMočno priporočamo, da zapišeš reševalni disk VeraCrypt.</entry>
@@ -1183,7 +1183,7 @@
     <entry lang="sl" key="SYS_ENCRYPTION_PRETEST_INFO">Preden šifrira vašo sistemsko particijo ali pogon, mora VeraCrypt preveriti, ali vse deluje pravilno.\n\nKo klikneš "Preizkus", bodo vse potrebne komponente (na primer komponenta za preverjanje pristnosti pred zagonom, tj. zagonski nalagalnik VeraCrypt) nameščene in tvoj računalnik se bo znova zagnal. Nato boš moral vnesti svoje geslo na zaslon zagonskega nalagalnika VeraCrypt, ki se prikaže pred zagonom sistema Windows. Ko se Windows zažene, boš samodejno obveščen o rezultatu tega predtestiranja.\n\nNaslednja naprava bo spremenjena: pogon #%d\n\n\nČe zdaj klikneš 'Prekliči', se nič ne namesti in predtest ne bo izveden.</entry>
     <entry lang="sl" key="SYS_ENCRYPTION_PRETEST_INFO2_PORTION_1">POMEMBNE OPOMBE -- PROSIMO, PREBERI ALI NATISNI (klikni 'Natisni'):\n\nUpoštevaj, da nobena od tvojih datotek ne bo šifrirana, preden uspešno znova zaženeš računalnik in zaženeš Windows. Torej, če karkoli ne uspe, tvoji podatki NE bodo izgubljeni. Če pa gre kaj narobe, lahko naletiš na težave pri zagonu sistema Windows. Zato preberi (in, če je možno, natisni) naslednje smernice o tem, kaj storiti, če se Windows ne more zagnati po ponovnem zagonu računalnika.\n\n</entry>
     <entry lang="sl" key="SYS_ENCRYPTION_PRETEST_INFO2_PORTION_2">Kaj storiti, če se Windows ne more zagnati\n---------------------------------------- -------\n\nOpomba: Ta navodila so veljavna samo, če še nisi začel šifrirati.\n\n- Če se Windows ne zažene, ko vneseš pravilno geslo (ali če večkrat vneseš pravilno geslo, vendar VeraCrypt pravi, da geslo ni pravilno), brez panike. Znova zaženi (izklopi in vklopi) računalnik in na zaslonu Zagonskega nalagalnika VeraCrypt pritisni tipko Esc na tipkovnici (in če imaš več sistemov, izberi, katerega želiš zagnati). Nato bi se moral zagnati Windows (pod pogojem, da ni šifriran) in VeraCrypt te bo samodejno vprašal, ali želiš odstraniti komponento za preverjanje pristnosti pred zagonom. Upoštevaj, da prejšnji koraki NE delujejo, če je sistemska particija/pogon šifriran (nihče ne more zagnati sistema Windows ali dostopati do šifriranih podatkov na pogonu brez pravilnega gesla, tudi če sledi prejšnjim korakom).\n\n</entry>
-    <entry lang="sl" key="SYS_ENCRYPTION_PRETEST_INFO2_PORTION_3">- Če prejšnji koraki ne pomagajo ali če se zaslon zagonskega nalagalnika VeraCrypt ne prikaže (pred zagonom sistema Windows), vstavi reševalni disk VeraCrypt v pogon CD/DVD in znova zaženi računalnik. Če se zaslon reševalnega diska VeraCrypt ne prikaže (ali če ne vidiš elementa 'Repair Options' v razdelku 'Keyboard Controls' na zaslonu reševalnega diska VeraCrypt), je možno, da je tvoj BIOS konfiguriran za poskus zagona iz trdega diska pred pogoni CD/DVD. V tem primeru znova zaženi računalnik, pritisni F2 ali Delete (takoj, ko vidiš zaslon za zagon BIOS-a) in počakaj, da se prikaže zaslon za konfiguracijo BIOS-a. Če se ne prikaže zaslon za konfiguracijo BIOS-a, znova zaženi (ponastavi) računalnik in začni večkrat pritiskati F2 ali Delete, takoj ko znova zaženeš (ponastaviš) računalnik. Ko se prikaže zaslon za konfiguracijo BIOS-a, najprej konfiguriraj svoj BIOS za zagon s pogona CD/DVD (za informacije o tem, kako to storiš, glej dokumentacijo za tvoj BIOS/matično ploščo ali se za pomoč obrni na ekipo za tehnično podporo prodajalca tvojega računalnika). Nato znova zaženi računalnik. Zdaj bi se moral prikazati zaslon reševalnega diska VeraCrypt. Na zaslonu izberite 'Repair Options' s pritiskom na F8 na tipkovnici. V meniju »Možnosti popravila« izberi »Obnovi izvirni nalagalnik sistema«. Nato odstrani reševalni disk iz pogona CD/DVD in znova zaženi računalnik. Windows bi se moral zagnati normalno (pod pogojem, da ni šifriran).\n\n</entry>
+    <entry lang="sl" key="SYS_ENCRYPTION_PRETEST_INFO2_PORTION_3">- Če prejšnji koraki ne pomagajo ali če se zaslon zagonskega nalagalnika VeraCrypt ne prikaže (pred zagonom sistema Windows), vstavi reševalni disk VeraCrypt v pogon CD/DVD in znova zaženi računalnik. Če se zaslon reševalnega diska VeraCrypt ne prikaže (ali če ne vidiš elementa 'Repair Options' v razdelku 'Keyboard Controls' na zaslonu reševalnega diska VeraCrypt), je možno, da je tvoj BIOS konfiguriran za poskus zagona iz trdega diska pred pogoni CD/DVD. V tem primeru znova zaženi računalnik, pritisni F2 ali Delete (takoj, ko vidiš zaslon za zagon BIOS-a) in počakaj, da se prikaže zaslon za konfiguracijo BIOS-a. Če se ne prikaže zaslon za konfiguracijo BIOS-a, znova zaženi (ponastavi) računalnik in začni večkrat pritiskati F2 ali Delete, takoj ko znova zaženeš (ponastaviš) računalnik. Ko se prikaže zaslon za konfiguracijo BIOS-a, najprej konfiguriraj svoj BIOS za zagon s pogona CD/DVD (za informacije o tem, kako to storiš, glej dokumentacijo za tvoj BIOS/matično ploščo ali se za pomoč obrni na ekipo za tehnično podporo prodajalca tvojega računalnika). Nato znova zaženi računalnik. Zdaj bi se moral prikazati zaslon reševalnega diska VeraCrypt. Na zaslonu izberi 'Repair Options' s pritiskom na F8 na tipkovnici. V meniju 'Repair Options' izberi 'Restore original system loader'. Nato odstrani reševalni disk iz pogona CD/DVD in znova zaženi računalnik. Windows bi se moral zagnati normalno (pod pogojem, da ni šifriran).\n\n</entry>
     <entry lang="sl" key="SYS_ENCRYPTION_PRETEST_INFO2_PORTION_4">Prejšnji koraki NE delujejo, če je sistemska particija/pogon šifriran (nihče ne more zagnati sistema Windows ali dostopati do šifriranih podatkov na pogonu brez pravilnega gesla, tudi če sledi prejšnjim korakom).\n\n\nTudi če izgubiš svoj rešilni disk VeraCrypt in ga napadalec najde, NE bo mogel dešifrirati sistemske particije ali pogona brez pravilnega gesla.</entry>
     <entry lang="sl" key="SYS_ENCRYPTION_PRETEST_RESULT_TITLE">Preverjanjew končano</entry>
     <entry lang="sl" key="SYS_ENCRYPTION_PRETEST_RESULT_INFO">Predhodni preizkus je bil uspešno zaključen.\n\nOPOZORILO: Če med šifriranjem obstoječih podatkov na mestu pride do nenadne prekinitve napajanja ali ko se operacijski sistem zruši zaradi programske napake ali okvare strojne opreme, medtem ko VeraCrypt šifrira obstoječe podatke na mestu , bodo deli podatkov poškodovani ali izgubljeni. Zato se pred začetkom šifriranja prepričaj, da imaš varnostne kopije datotek, ki jih želiš šifrirati. Če tega ne storiš, varnostno kopiraj datoteke zdaj (lahko klikneš 'Odloži', varnostno kopiraš datoteke, nato kadar koli znova zaženeš VeraCrypt in izbereš 'Sistem' &gt; 'Nadaljuj prekinjen proces', da začneš šifriranje).\n\nKo si pripravljen , klikni 'Šifriraj', da začneš šifrirati.</entry>
@@ -1199,12 +1199,12 @@
     <entry lang="sl" key="HIDDEN_OS_CREATION_NOT_FINISHED_CHOICE_TERMINATE">Trajno prekini postopek ustvarjanja skritega operacijskega sistema</entry>
     <entry lang="sl" key="HIDDEN_OS_CREATION_NOT_FINISHED_CHOICE_ASK_LATER">Zdaj ne stori ničesar in vprašaj znova pozneje</entry>
     <entry lang="sl" key="RESCUE_DISK_HELP_PORTION_1">\nČE JE MOŽNO, NATISNI TO BESEDILO (spodaj klikni 'Natisni').\n\n\nKako in kdaj uporabiti reševalni disk VeraCrypt (po šifriranju)\n--------------- -------------------------------------------------- ------------------\n\n</entry>
-    <entry lang="sl" key="RESCUE_DISK_HELP_PORTION_2">I. Kako zagnati reševalni disk VeraCrypt\n\nČe želiš zagnati reševalni disk VeraCrypt, ga vstavi v pogon CD/DVD in znova zaženi računalnik. Če se zaslon VeraCrypt Rescue Disk ne prikaže (ali če ne vidiš elementa 'Repair Options' v razdelku 'Keyboard Controls' na zaslonu), je možno, da je tvoj BIOS konfiguriran za poskus zagona s trdih diskov, pred CD/DVD pogoni. V tem primeru znova zaženi računalnik, pritisni F2 ali Delete (takoj, ko vidiš zaslon za zagon BIOS-a) in počakaj, da se prikaže zaslon za konfiguracijo BIOS-a. Če se ne prikaže zaslon za konfiguracijo BIOS-a, znova zaženi (ponastavi) računalnik in začni večkrat pritiskati F2 ali Delete, takoj ko znova zaženeš (ponastaviš) računalnik. Ko se prikaže zaslon za konfiguracijo BIOS-a, najprej konfiguriraj svoj BIOS za zagon s pogona CD/DVD (za informacije o tem, kako to storiš, glej dokumentacijo za tvoj BIOS/matično ploščo ali se za pomoč obrni na ekipo za tehnično podporo prodajalca tvojega računalnika). Nato znova zaženi računalnik. Zdaj bi se moral prikazati zaslon VeraCrypt Rescue Disk. Opomba: Na zaslonu reševalnega diska VeraCrypt lahko izbereš 'Možnosti popravila' s pritiskom na F8 na tipkovnici.\n\n\n</entry>
+    <entry lang="sl" key="RESCUE_DISK_HELP_PORTION_2">I. Kako zagnati reševalni disk VeraCrypt\n\nČe želiš zagnati reševalni disk VeraCrypt, ga vstavi v pogon CD/DVD in znova zaženi računalnik. Če se zaslon reševalnega diska VeraCrypt ne prikaže (ali če ne vidiš elementa 'Repair Options' v razdelku 'Keyboard Controls' na zaslonu), je možno, da je tvoj BIOS konfiguriran za poskus zagona s trdih diskov, pred CD/DVD pogoni. V tem primeru znova zaženi računalnik, pritisni F2 ali Delete (takoj, ko vidiš zaslon za zagon BIOS-a) in počakaj, da se prikaže zaslon za konfiguracijo BIOS-a. Če se ne prikaže zaslon za konfiguracijo BIOS-a, znova zaženi (ponastavi) računalnik in začni večkrat pritiskati F2 ali Delete, takoj ko znova zaženeš (ponastaviš) računalnik. Ko se prikaže zaslon za konfiguracijo BIOS-a, najprej konfiguriraj svoj BIOS za zagon s pogona CD/DVD (za informacije o tem, kako to storiš, glej dokumentacijo za tvoj BIOS/matično ploščo ali se za pomoč obrni na ekipo za tehnično podporo prodajalca tvojega računalnika). Nato znova zaženi računalnik. Zdaj bi se moral prikazati zaslon reševalnega diska VeraCrypt. Opomba: Na zaslonu reševalnega diska VeraCrypt lahko izbereš 'Repair Options' s pritiskom na F8 na tipkovnici.\n\n\n</entry>
     <entry lang="sl" key="RESCUE_DISK_HELP_PORTION_3">II. Kdaj in kako uporabiti reševalni disk VeraCrypt (po šifriranju)\n\n</entry>
-    <entry lang="sl" key="RESCUE_DISK_HELP_PORTION_4">1) Če se zaslon zagonskega nalagalnika VeraCrypt ne prikaže, ko zaženeš računalnik (ali če se Windows ne zažene), je zagonski nalagalnik VeraCrypt morda poškodovan. Reševalni disk VeraCrypt  omogoča, da ga obnoviš in s tem ponovno pridobiš dostop do šifriranega sistema in podatkov (vendar upoštevaj, da boš takrat še vedno moral vnesti pravilno geslo). Na zaslonu reševalnega diska izberit 'Repair Options' &gt; 'Obnovi zagonski nalagalnik VeraCrypt'. Nato pritisni 'Y', da potrdiš dejanje, odstrani reševalni disk iz pogona CD/DVD in znova zaženi računalnik.\n\n</entry>
-    <entry lang="sl" key="RESCUE_DISK_HELP_PORTION_5">2) Če večkrat vneseš pravilno geslo, vendar VeraCrypt sporoči, da je geslo napačno, so lahko glavni ključ ali drugi kritični podatki poškodovani. Reševalni disk VeraCrypt omogoča, da jih obnoviš in s tem ponovno pridobiš dostop do šifriranega sistema in podatkov (vendar upoštevaj, da boš takrat še vedno moral vnesti pravilno geslo). Na zaslonu reševalnega diska izberi 'Repair Options' &gt; 'Obnovi ključne podatke'. Nato vnesi svoje geslo, pritisni 'Y' za potrditev dejanja, odstrani reševalni disk iz pogona CD/DVD in znova zaženi računalnik.\n\n</entry>
+    <entry lang="sl" key="RESCUE_DISK_HELP_PORTION_4">1) Če se zaslon zagonskega nalagalnika VeraCrypt ne prikaže, ko zaženeš računalnik (ali če se Windows ne zažene), je zagonski nalagalnik VeraCrypt morda poškodovan. Reševalni disk VeraCrypt  omogoča, da ga obnoviš in s tem ponovno pridobiš dostop do šifriranega sistema in podatkov (vendar upoštevaj, da boš takrat še vedno moral vnesti pravilno geslo). Na zaslonu reševalnega diska izberi 'Repair Options' &gt; 'Restore VeraCrypt Boot Loader'. Nato pritisni 'Y', da potrdiš dejanje, odstrani reševalni disk iz pogona CD/DVD in znova zaženi računalnik.\n\n</entry>
+    <entry lang="sl" key="RESCUE_DISK_HELP_PORTION_5">2) Če večkrat vneseš pravilno geslo, vendar VeraCrypt sporoči, da je geslo napačno, so lahko glavni ključ ali drugi kritični podatki poškodovani. Reševalni disk VeraCrypt omogoča, da jih obnoviš in s tem ponovno pridobiš dostop do šifriranega sistema in podatkov (vendar upoštevaj, da boš takrat še vedno moral vnesti pravilno geslo). Na zaslonu reševalnega diska izberi 'Repair Options' &gt; 'Restore key data'. Nato vnesi svoje geslo, pritisni 'Y' za potrditev dejanja, odstrani reševalni disk iz pogona CD/DVD in znova zaženi računalnik.\n\n</entry>
     <entry lang="sl" key="RESCUE_DISK_HELP_PORTION_6">3) Če je zagonski nalagalnik VeraCrypt poškodovan, se mu lahko izogneš tako, da se zaženeš neposredno z reševalnega diska VeraCrypt. Vstavi svoj reševalni disk v pogon CD/DVD in nato vnesi svoje geslo na zaslonu reševalnega diska.\n\n</entry>
-    <entry lang="sl" key="RESCUE_DISK_HELP_PORTION_7">4) Če je Windows poškodovan in se ne more zagnati, omogoča reševalni disk  VeraCrypt trajno dešifriranje particije/pogona, preden se Windows zažene. Na zaslonu reševalnega diska izberi 'Repair Options' &gt; 'Trajno dešifriraj sistemsko particijo/pogon'. Vnesi pravilno geslo in počakaj, da se dešifriranje konča. Potem lahko npr. zaženeš namestitveni CD/DVD MS Windows, da popraviš namestitev sistema Windows.\n\n</entry>
+    <entry lang="sl" key="RESCUE_DISK_HELP_PORTION_7">4) Če je Windows poškodovan in se ne more zagnati, omogoča reševalni disk  VeraCrypt trajno dešifriranje particije/pogona, preden se Windows zažene. Na zaslonu reševalnega diska izberi 'Repair Options' &gt; 'Permanently decrypt system partition/drive'. Vnesi pravilno geslo in počakaj, da se dešifriranje konča. Potem lahko npr. zaženeš namestitveni CD/DVD MS Windows, da popraviš namestitev sistema Windows.\n\n</entry>
     <entry lang="sl" key="RESCUE_DISK_HELP_PORTION_8">Opomba: Če je sistem Windows poškodovan (se ne more zagnati) in ga moraš popraviti (ali dostopati do datotek v njem), se lahko izogneš dešifriranju sistemske particije/pogona tako, da slediš tem korakom: Če imaš v računalniku nameščenih več operacijskih sistemov , zaženi tistega, ki ne zahteva preverjanja pristnosti pred zagonom. Če v računalniku nimaš nameščenih več operacijskih sistemov, lahko zaženeš CD/DVD WinPE ali BartPE ali pa povežeš sistemski pogon kot sekundarni ali zunanji pogon z drugim računalnikom in nato zaženeteš operacijski sistem, nameščen v računalniku. Ko zaženeš sistem, zaženi VeraCrypt, klikni »Izberi napravo«, izberi prizadeto sistemsko particijo, klikni »V redu«, izberi »Sistem« &gt; »Namesti brez preverjanja pristnosti pred zagonom«, vnesi geslo za preverjanje pristnosti pred zagonom in klikni »V redu«. Particija bo nameščena kot običajni nosilec VeraCrypt (podatki bodo ob dostopu sproti dešifrirani/šifrirani v RAM-u, kot običajno).\n\n\n</entry>
     <entry lang="sl" key="RESCUE_DISK_HELP_PORTION_9">Tudi če izgubiš svoj reševalni disk VeraCrypt in ga napadalec najde, NE bo mogel dešifrirati sistemske particije ali pogona brez pravilnega gesla.</entry>
     <entry lang="sl" key="DECOY_OS_INSTRUCTIONS_PORTION_1">\n\nPOMEMBNO -- ČE JE MOŽNO, NATISNI TO BESEDILO (spodaj klikni 'Natisni').\n\n\nOpomba: To besedilo bo samodejno prikazano vsakič, ko zaženeš skriti sistem, dokler ne začneš ustvarjati sistema za vabo.\n\n\n</entry>
@@ -1312,18 +1312,18 @@
     <entry lang="sl" key="TEST">Test</entry>
     <entry lang="sl" key="KEYFILE">Ključna datoteka</entry>
     <entry lang="sl" key="VKEY_08">Brisalka</entry>
-    <entry lang="en" key="VKEY_09">Tab</entry>
-    <entry lang="en" key="VKEY_0C">Clear</entry>
-    <entry lang="en" key="VKEY_0D">Enter</entry>
-    <entry lang="en" key="VKEY_13">Pause</entry>
+    <entry lang="sl" key="VKEY_09">Tabulator</entry>
+    <entry lang="sl" key="VKEY_0C">Počisti</entry>
+    <entry lang="sl" key="VKEY_0D">Vnašalka</entry>
+    <entry lang="sl" key="VKEY_13">Pavza</entry>
     <entry lang="sl" key="VKEY_14">Caps Lock</entry>
     <entry lang="sl" key="VKEY_20">Preslednica</entry>
     <entry lang="sl" key="VKEY_21">Stran gor</entry>
     <entry lang="sl" key="VKEY_22">Stran dol</entry>
-    <entry lang="en" key="VKEY_23">End</entry>
+    <entry lang="sl" key="VKEY_23">Konec</entry>
     <entry lang="sl" key="VKEY_24">Domov</entry>
     <entry lang="sl" key="VKEY_25">Puščica levo</entry>
-    <entry lang="en" key="VKEY_26">Puščica gor</entry>
+    <entry lang="sl" key="VKEY_26">Puščica gor</entry>
     <entry lang="sl" key="VKEY_27">Puščica desno</entry>
     <entry lang="sl" key="VKEY_28">Puščica dol</entry>
     <entry lang="sl" key="VKEY_29">Tipka izberi</entry>
@@ -1354,11 +1354,11 @@
     <entry lang="sl" key="VKEY_B5">Tipka Izberi Medij</entry>
     <entry lang="sl" key="VKEY_B6">Applikacija 1</entry>
     <entry lang="sl" key="VKEY_B7">Applikacija 2</entry>
-    <entry lang="en" key="VKEY_F6">Attn</entry>
-    <entry lang="en" key="VKEY_F7">CrSel</entry>
-    <entry lang="en" key="VKEY_F8">ExSel</entry>
+    <entry lang="sl" key="VKEY_F6">Attn</entry>
+    <entry lang="sl" key="VKEY_F7">CrSel</entry>
+    <entry lang="sl" key="VKEY_F8">ExSel</entry>
     <entry lang="sl" key="VKEY_FA">Izvajaj</entry>
-    <entry lang="en" key="VKEY_FB">Zoom</entry>
+    <entry lang="sl" key="VKEY_FB">Povečava</entry>
     <entry lang="sl" key="VK_NUMPAD">NumPad</entry>
     <entry lang="sl" key="VK_SHIFT">Shift</entry>
     <entry lang="sl" key="VK_CONTROL">Control</entry>
@@ -1582,7 +1582,7 @@
     <entry lang="sl" key="EXPANDER_FREE_SPACE">%s prostora na voljo na gostiteljskem pogonu</entry>
     <entry lang="sl" key="EXPANDER_HELP_DEVICE">To je nosilec VeraCrypt, ki temelji na napravi.\n\nNova velikost nosilca bo samodejno izbrana kot velikost gostiteljske naprave.</entry>
     <entry lang="sl" key="EXPANDER_HELP_FILE">Določi novo velikost nosilca VeraCrypt (mora biti vsaj %I64u KB večja od trenutne velikosti).</entry>
-    <entry lang="sl" key="QUICK_EXPAND_WARNING">OPOZORILO: Quick Expand uporabi samo v naslednjih primerih:\n\n1) Naprava, v kateri je vsebnik datotek, ne vsebuje občutljivih podatkov in ne potrebuješ možnosti zanikanja.\n2) Naprava, v kateri je vsebnik datotek, je že varno in popolnoma šifrirana.\n\nAli si prepričan, da želiš uporabiti hitro razširitev?</entry>
+    <entry lang="sl" key="QUICK_EXPAND_WARNING">OPOZORILO: Hitro razširitev uporabljaj le v naslednjih primerih:\n\n1) Naprava, v kateri je vsebnik datotek, ne vsebuje občutljivih podatkov in ne potrebuješ verjetnega zanikanja.\n2) Naprava, v kateri je vsebnik datotek, je že varno in v celoti šifrirana.\n\nAli si prepričan, da želiš uporabiti hitro razširitev?</entry>
     <entry lang="sl" key="EXPANDER_STATUS_TEXT">POMEMBNO: Znotraj tega okna premikaj miško čim bolj naključno. Dlje ko jo premikaš, bolje je. To bistveno poveča kriptografsko moč šifrirnih ključev. Nato klikni »Nadaljuj«, da razširiš nosilec.</entry>
     <entry lang="sl" key="EXPANDER_STATUS_TEXT_LEGACY">Za širitev nosilca klikni 'Nadaljuj'.</entry>
     <entry lang="sl" key="EXPANDER_FINISH_ERROR">Napaka: širitev nosilca ni uspela.</entry>
@@ -1643,47 +1643,47 @@
     <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>
+    <entry lang="sl" key="IDT_KDF_ALGO">Algoritem KDF</entry>
+    <entry lang="sl" key="IDD_PREFERENCES_TAB_GENERAL">Splošno</entry>
+    <entry lang="sl" key="IDD_PREFERENCES_TAB_ACTIONS">Dejanja</entry>
+    <entry lang="sl" key="IDD_PREFERENCES_TAB_PASSWORD">Geslo</entry>
+    <entry lang="sl" key="IDC_SECURE_DESKTOP_ENABLE_IME">Omogoči urejevalnik vnosnih metod (IME) v Secure Desktop</entry>
+    <entry lang="sl" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">OPOZORILO: To možnost omogoči samo, če naletiš na težave pri izbiri ključnih datotek/žetonov v Secure Desktop.</entry>
+    <entry lang="sl" key="ERR_KEY_DERIVATION_FAILED">Izpeljava ključa ni uspela. Vzrok je lahko premalo pomnilnika ali prekinjeno opravilo.</entry>
+    <entry lang="sl" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">Sistemska particija oziroma pogon je že dešifriran, vendar pot Microsoftovega zagonskega nalagalnika EFI ni bila obnovljena v Upravitelju zagona Windows. Popraviti je treba samo zagonske datoteke EFI. Uporabi možnost popravila na reševalnem disku VeraCrypt ali zaženi obnovitveni medij Windows in izvedi 'bcdboot W:\\Windows /s S: /f UEFI', potem ko W: zamenjaš s črko pogona nosilca Windows, S: pa s črko pogona sistemske particije EFI. Pot:</entry>
+    <entry lang="sl" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">Sistemska particija oziroma pogon je že dešifriran, vendar rezervna pot zagonskega nalagalnika EFI še vedno vsebuje zagonski nalagalnik VeraCrypt. Popraviti je treba samo zagonske datoteke EFI. Uporabi možnost popravila na reševalnem disku VeraCrypt ali zaženi obnovitveni medij Windows in izvedi 'bcdboot W:\\Windows /s S: /f UEFI', potem ko W: zamenjaš s črko pogona nosilca Windows, S: pa s črko pogona sistemske particije EFI. Pot:</entry>
+    <entry lang="sl" key="IDM_REPAIR_EFI_BOOT_LOADER">Popravi zagonski nalagalnik EFI...</entry>
+    <entry lang="sl" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt bo obnovil poti zagonskega nalagalnika EFI za Windows ter odstranil zagonske vnose in datoteke VeraCrypt EFI.\n\nTo uporabi samo po tem, ko je sistemska particija oziroma pogon v celoti dešifriran in se Windows lahko zažene brez sistemskega šifriranja.\n\nAli želiš nadaljevati?</entry>
+    <entry lang="sl" key="EFI_BOOT_LOADER_FILE_READ_FAILED">Datoteke zagonskega nalagalnika EFI ni bilo mogoče prebrati v celoti:</entry>
+    <entry lang="sl" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">Datoteka zagonskega nalagalnika EFI je nepričakovano velika in ni bila pregledana:</entry>
+    <entry lang="sl" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">Sistemska particija oziroma pogon je že dešifriran in datoteke zagonskega nalagalnika EFI so bile obnovljene, vendar VeraCrypt ni mogel odstraniti enega ali več zagonskih vnosov VeraCrypt iz vdelane programske opreme. Datoteke VeraCrypt EFI so ostale na mestu, da vsak preostali vnos vdelane programske opreme še vedno kaže na obstoječi nalagalnik. Poskusi znova kot skrbnik ali odstrani zagonski vnos VeraCrypt iz nastavitev vdelane programske opreme, potem ko potrdiš, da se Upravitelj zagona Windows zažene normalno.</entry>
+    <entry lang="sl" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">Zagonskega nalagalnika EFI ni mogoče popraviti, dokler je sistemsko šifriranje ali dešifriranje aktivno ali nedokončano. Dokončaj ali nadaljuj čakajoči postopek sistemskega šifriranja/dešifriranja in nato poskusi znova.</entry>
+    <entry lang="sl" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">To popravilo je na voljo samo v sistemih, ki se zaganjajo v načinu UEFI s sistemske particije GPT.</entry>
+    <entry lang="sl" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">Zagonski nalagalnik EFI je bil uspešno popravljen.</entry>
+    <entry lang="sl" key="PIM_ARGON2_HELP">PIM (Personal Iterations Multiplier) nadzira stroške pomnilnika in časa, ki jih uporablja izpeljava ključa glave z Argon2id, kot sledi:\n      Pomnilnik = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Iteracije = 3 + ((PIM - 1) / 3) za PIM 31 ali manj, nato 13 + (PIM - 31)\n\nČe ostane prazno ali nastavljeno na 0, bo VeraCrypt uporabil privzeti PIM Argon2 (12), ki uporablja 416 MiB pomnilnika in 6 iteracij.\n\nČe ima geslo manj kot 20 znakov, PIM Argon2 ne sme biti manjši od 12, da se ohrani minimalna raven varnosti.\nČe ima geslo 20 ali več znakov, lahko PIM Argon2 nastaviš na poljubno vrednost.\n\nPIM Argon2, večji od 12, poveča uporabo pomnilnika do 1024 MiB in nato poveča število iteracij. To povzroči počasnejši priklop. Majhen PIM Argon2 (manj kot 12) povzroči hitrejši priklop, vendar lahko zmanjša varnost, če geslo ni dovolj močno.</entry>
+    <entry lang="sl" key="PIM_ARGON2_LARGE_WARNING">Izbral si vrednost PIM Argon2, ki je večja od privzete vrednosti VeraCrypt.\nUpoštevaj, da lahko to zahteva več pomnilnika in povzroči precej počasnejši priklop.</entry>
+    <entry lang="sl" key="PIM_ARGON2_SMALL_WARNING">Izbral si vrednost PIM Argon2, ki je manjša od privzete vrednosti VeraCrypt. Upoštevaj, da lahko to pri premalo močnem geslu povzroči šibkejšo varnost.\n\nAli potrjuješ, da uporabljaš močno geslo?</entry>
+    <entry lang="sl" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Geslo mora vsebovati 20 ali več znakov, če želiš uporabiti navedeni PIM Argon2.\nKrajša gesla je mogoče uporabiti samo, če je PIM Argon2 12 ali večji.</entry>
+    <entry lang="sl" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER">Priklapljaj nosilce NTFS z gonilnikom v jedru Linuxa</entry>
+    <entry lang="sl" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Samo Linux. Ko je omogočeno in ni izrecno navedena vrsta datotečnega sistema, VeraCrypt z blkid -p pregleda dešifrirano navidezno napravo in zaznane datotečne sisteme NTFS priklopi z razpoložljivim gonilnikom NTFS v jedru, pri čemer obide pomočnike za priklop, kot je ntfs-3g. VeraCrypt uporabi ntfs, ko je zanesljivo prepoznan kot sodoben gonilnik za branje/pisanje ali pričakovan v Linuxu 7.1 ali novejšem, sicer pa uporabi ntfs3. Če zaznavanje NTFS ne uspe, VeraCrypt uporabi običajno samodejno izbiro datotečnega sistema. Če podprt gonilnik NTFS v jedru ni na voljo ali ga ni mogoče naložiti, priklop ne uspe. Ta izbirna možnost lahko prepreči zastoje ob prehodu v spanje ali mirovanje, ki jih povzročijo zamrznjeni datotečni sistemi FUSE v uporabniškem prostoru.</entry>
+    <entry lang="sl" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">Ni na voljo ali ni mogoče naložiti nobenega podprtega gonilnika NTFS v jedru. Če želiš uporabiti privzeti sistemski mehanizem NTFS, onemogoči nastavitev jedrnega gonilnika NTFS ali ne zahtevaj izrecno jedrnega NTFS.</entry>
+    <entry lang="sl" key="LINUX_EMERGENCY_UNMOUNT_WARNING">Običajen odklop nosilca {0} ni uspel. To se lahko zgodi, ko imajo aplikacije še vedno odprte datoteke ali imenike na nosilcu ali ko je bila gostiteljska naprava odklopljena in je priklop postal zastarel.\n\nČe je naprava še vedno povezana, izberi Ne, zapri aplikacije, ki uporabljajo nosilec, in znova poskusi odklopiti.\n\nČe je bila naprava odklopljena ali je priklop zastarel, lahko VeraCrypt poskusi izvesti nujno čiščenje z lenim odklopom datotečnega sistema in odstranitvijo ali načrtovanjem odstranitve objektov jedra VeraCrypt. Čakajoči zapisi morda niso uspeli, podatki so lahko izgubljeni in čiščenje lahko ostane nedokončano, dokler aplikacije ne zaprejo odprtih datotek. Pred ponovno uporabo preveri datotečni sistem z fsck ali ustreznim orodjem za popravilo.\n\nNadaljujem?</entry>
+    <entry lang="sl" key="LINUX_EMERGENCY_UNMOUNTED">Začelo se je nujno čiščenje nosilca {0}. Če je bila naprava odklopljena, je priklop zastarel ali so obstajali čakajoči zapisi, pred ponovno uporabo preveri datotečni sistem z fsck ali ustreznim orodjem za popravilo.</entry>
+    <entry lang="sl" key="FORMAT_STAGE_WRITING_DATA">Ustvarjanje podatkov nosilca. Počakaj.</entry>
+    <entry lang="sl" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Zaključevanje ustvarjanja nosilca: zapisovanje pomožne glave nosilca.</entry>
+    <entry lang="sl" key="FORMAT_STAGE_FLUSHING_DATA">Zaključevanje ustvarjanja nosilca: zapisovanje podatkov na disk. To lahko pri velikih nosilcih ali počasnih/USB napravah za shranjevanje traja več minut.</entry>
+    <entry lang="sl" key="FORMAT_STAGE_FINISHED">Zaključevanje ustvarjanja nosilca.</entry>
+    <entry lang="sl" key="FORMAT_STAGE_ABORTED">Ustvarjanje nosilca je bilo prekinjeno.</entry>
+    <entry lang="sl" key="FORMAT_STAGE_ERROR">Ustvarjanje nosilca ni uspelo.</entry>
+    <entry lang="sl" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Zaključevanje ustvarjanja nosilca: priklapljanje začasnega nosilca.</entry>
+    <entry lang="sl" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Zaključevanje ustvarjanja nosilca: pripravljanje začasne naprave.</entry>
+    <entry lang="sl" key="FORMAT_STAGE_CREATING_FILESYSTEM">Zaključevanje ustvarjanja nosilca: ustvarjanje datotečnega sistema z uporabo {0}.</entry>
+    <entry lang="sl" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Zaključevanje ustvarjanja nosilca: odklapljanje začasnega nosilca.</entry>
+    <entry lang="sl" key="MACOSX_APFS_SYNTHESIZED_DEVICE">Izbrana naprava '{0}' je sintetiziran vsebnik ali nosilec APFS in je ni mogoče uporabiti kot neobdelanega gostitelja nosilca VeraCrypt.\n\nNamesto tega izberi fizično particijo shrambe APFS{1}.</entry>
+    <entry lang="sl" key="MACOSX_DEVICE_SYSTEM_PARTITION">Izbrana naprava '{0}' je sistemska/podporna particija macOS in je ni mogoče uporabiti kot gostitelja nosilca VeraCrypt.</entry>
+    <entry lang="sl" key="MACOSX_APFS_SYSTEM_STORE">Izbrana fizična shramba APFS '{0}' vsebuje trenutno priklopljen sistemski nosilec macOS in je ni mogoče uporabiti kot gostitelja nosilca VeraCrypt.</entry>
+    <entry lang="sl" key="MACOSX_DEVICE_NOT_WRITABLE">macOS poroča, da je izbrana naprava '{0}' samo za branje. Izberi zapisljivo fizično particijo ali disk.</entry>
+    <entry lang="sl" key="MACOSX_APFS_EROFS_HINT">macOS je poročal, da je izbrana naprava samo za branje. Če je to disk APFS, se prepričaj, da si izbral fizično particijo shrambe APFS, ne sintetiziranega nosilca APFS. S programom Disk Utility ali ukazom 'diskutil list' poišči fizično particijo in poskusi znova.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">

Translations/Language.tr.xml

@@ -1643,47 +1643,47 @@
     <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>
+    <entry lang="tr" key="IDT_KDF_ALGO">KDF algoritması</entry>
+    <entry lang="tr" key="IDD_PREFERENCES_TAB_GENERAL">Genel</entry>
+    <entry lang="tr" key="IDD_PREFERENCES_TAB_ACTIONS">İşlemler</entry>
+    <entry lang="tr" key="IDD_PREFERENCES_TAB_PASSWORD">Parola</entry>
+    <entry lang="tr" key="IDC_SECURE_DESKTOP_ENABLE_IME">Güvenli masaüstünde giriş yöntemi düzenleyicisi (IME) kullanılsın</entry>
+    <entry lang="tr" key="ENABLE_IME_IN_SECURE_DESKTOP_WARNING">UYARI: Bu seçeneği YALNIZCA güvenli masaüstünde anahtar dosyalarını/güvenlik kodlarını seçerken sorun yaşıyorsanız etkinleştirin.</entry>
+    <entry lang="tr" key="ERR_KEY_DERIVATION_FAILED">Anahtar türetilemedi. Bunun nedeni yetersiz bellek ya da yarıda kesilmiş bir işlem olabilir.</entry>
+    <entry lang="tr" key="EFI_MS_BOOT_LOADER_RESTORE_FAILED">Sistem bölümünün/sürücüsünün şifresi zaten çözülmüş, ancak Microsoft EFI başlatma yükleyicisi yolu Windows Başlatma Yöneticisine geri yüklenemedi. Yalnızca EFI başlatma dosyalarının onarılması gerekir. VeraCrypt kurtarma diski onarım seçeneğini kullanın ya da Windows kurtarma ortamından başlatıp W: yerine Windows biriminin sürücü harfini, S: yerine EFI Sistem Bölümünün sürücü harfini yazarak 'bcdboot W:\\Windows /s S: /f UEFI' komutunu çalıştırın. Yol:</entry>
+    <entry lang="tr" key="EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT">Sistem bölümünün/sürücüsünün şifresi zaten çözülmüş, ancak EFI geri dönüş başlatma yükleyicisi yolu hala VeraCrypt başlatma yükleyicisini içeriyor. Yalnızca EFI başlatma dosyalarının onarılması gerekir. VeraCrypt kurtarma diski onarım seçeneğini kullanın ya da Windows kurtarma ortamından başlatıp W: yerine Windows biriminin sürücü harfini, S: yerine EFI Sistem Bölümünün sürücü harfini yazarak 'bcdboot W:\\Windows /s S: /f UEFI' komutunu çalıştırın. Yol:</entry>
+    <entry lang="tr" key="IDM_REPAIR_EFI_BOOT_LOADER">EFI başlatma yükleyicisini onar...</entry>
+    <entry lang="tr" key="CONFIRM_REPAIR_EFI_BOOT_LOADER">VeraCrypt, Windows EFI başlatma yükleyicisi yollarını geri yükleyecek ve VeraCrypt EFI başlatma kayıtlarını ve dosyalarını kaldıracak.\n\nBunu yalnızca sistem bölümünün/sürücüsünün şifresi tümüyle çözüldükten ve Windows sistem şifrelemesi olmadan başlatılabildikten sonra kullanın.\n\nİlerlemek istiyor musunuz?</entry>
+    <entry lang="tr" key="EFI_BOOT_LOADER_FILE_READ_FAILED">EFI başlatma yükleyicisi dosyası tümüyle okunamadı:</entry>
+    <entry lang="tr" key="EFI_BOOT_LOADER_FILE_TOO_LARGE">EFI başlatma yükleyicisi dosyası beklenmedik şekilde büyük ve incelenmedi:</entry>
+    <entry lang="tr" key="EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED">Sistem bölümünün/sürücüsünün şifresi zaten çözülmüş ve EFI başlatma yükleyicisi dosyaları geri yüklenmiş, ancak VeraCrypt bir ya da daha fazla VeraCrypt makine yazılımı başlatma kaydını kaldıramadı. Kalan makine yazılımı kayıtlarının var olan bir yükleyiciyi göstermeyi sürdürmesi için VeraCrypt EFI dosyaları yerinde bırakıldı. Yönetici olarak yeniden deneyin ya da Windows Başlatma Yöneticisinin normal şekilde başladığını doğruladıktan sonra VeraCrypt başlatma kaydını makine yazılımı ayarlarından kaldırın.</entry>
+    <entry lang="tr" key="EFI_BOOT_LOADER_REPAIR_BLOCKED">Sistem şifrelemesi ya da şifre çözme işlemi etkin veya tamamlanmamışken EFI başlatma yükleyicisi onarılamaz. Yeniden denemeden önce bekleyen sistem şifreleme/şifre çözme işlemini tamamlayın ya da sürdürün.</entry>
+    <entry lang="tr" key="EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE">Bu onarım işlemi yalnızca GPT sistem bölümünden UEFI kipinde başlatılan sistemlerde kullanılabilir.</entry>
+    <entry lang="tr" key="EFI_BOOT_LOADER_REPAIR_SUCCESS">EFI başlatma yükleyicisi başarıyla onarıldı.</entry>
+    <entry lang="tr" key="PIM_ARGON2_HELP">Kişisel çevrim çarpanı (PIM) değeri, Argon2id üst bilgi anahtar türetmesi tarafından kullanılan bellek ve süre maliyetlerini şu şekilde kontrol eder:\n      Bellek = min(64 MiB + ((PIM - 1) x 32 MiB), 1024 MiB)\n      Çevrim = PIM 31 ya da daha düşükse 3 + ((PIM - 1) / 3), daha yüksekse 13 + (PIM - 31)\n\nBoş bırakıldığında ya da 0 olarak ayarlandığında, VeraCrypt varsayılan Argon2 PIM değerini (12) kullanır. Bu değer 416 MiB bellek ve 6 çevrim kullanır.\n\nParola 20 karakterden kısaysa, en düşük güvenlik düzeyini korumak için Argon2 PIM 12 değerinden küçük olamaz.\nParola 20 karakter ya da daha uzunsa, Argon2 PIM herhangi bir değere ayarlanabilir.\n\n12 değerinden büyük bir Argon2 PIM bellek kullanımını 1024 MiB değerine kadar artırır ve ardından çevrimleri artırır. Bu, bağlanmanın yavaşlamasına neden olur. Küçük bir Argon2 PIM (12 değerinden küçük) daha hızlı bağlanma sağlar ancak parola yeterince güçlü değilse güvenliği azaltabilir.</entry>
+    <entry lang="tr" key="PIM_ARGON2_LARGE_WARNING">Varsayılan VeraCrypt değerinden daha büyük bir Argon2 PIM değeri seçtiniz.\nLütfen bunun daha fazla bellek gerektirebileceğini ve bağlanmanın çok daha yavaş olmasına yol açabileceğini unutmayın.</entry>
+    <entry lang="tr" key="PIM_ARGON2_SMALL_WARNING">Varsayılan VeraCrypt değerinden daha küçük bir Argon2 PIM değeri seçtiniz. Lütfen parolanız yeterince güçlü değilse bunun güvenliği zayıflatabileceğini unutmayın.\n\nGüçlü bir parola kullandığınızı onaylıyor musunuz?</entry>
+    <entry lang="tr" key="PIM_ARGON2_REQUIRE_LONG_PASSWORD">Belirtilen Argon2 PIM değerinin kullanılabilmesi için parola 20 ya da daha fazla karakterden oluşmalıdır.\nDaha kısa parolalar için Argon2 PIM değeri 12 ya da daha büyük olmalıdır.</entry>
+    <entry lang="tr" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER">NTFS birimleri çekirdek içi Linux sürücüsüyle bağlansın</entry>
+    <entry lang="tr" key="LINUX_PREF_MOUNT_NTFS_WITH_KERNEL_DRIVER_HELP">Yalnızca Linux. Etkinleştirildiğinde ve dosya sistemi türü açıkça belirtilmediğinde, VeraCrypt şifresi çözülmüş sanal aygıtı blkid -p ile inceler ve algılanan NTFS dosya sistemlerini, ntfs-3g gibi bağlama yardımcılarını atlayarak kullanılabilir bir çekirdek içi NTFS sürücüsüyle bağlar. VeraCrypt, ntfs sürücüsü modern bir okuma/yazma sürücüsü olarak kesin şekilde tanımlandığında ya da Linux 7.1 veya üzerindeki sürümlerde bekleniyorsa ntfs kullanır; diğer durumlarda ntfs3 kullanır. NTFS algılaması başarısız olursa, VeraCrypt normal otomatik dosya sistemi seçimini kullanır. Desteklenen bir çekirdek içi NTFS sürücüsü yoksa ya da yüklenemiyorsa bağlama başarısız olur. Bu isteğe bağlı seçenek, donmuş kullanıcı alanı FUSE dosya sistemlerinin neden olduğu askıya alma veya hazırda bekletme takılmalarını önleyebilir.</entry>
+    <entry lang="tr" key="LINUX_KERNEL_NTFS_DRIVER_UNAVAILABLE">Desteklenen bir çekirdek içi NTFS sürücüsü yok ya da yüklenemiyor. Sistemin varsayılan NTFS altyapısını kullanmak için NTFS çekirdek sürücüsü tercihini kapatın ya da çekirdek NTFS kullanımını açıkça istemeyin.</entry>
+    <entry lang="tr" key="LINUX_EMERGENCY_UNMOUNT_WARNING">{0} biriminin normal bağlantı kesme işlemi başarısız oldu. Bu durum, uygulamaların birimde hala açık dosya ya da klasörleri olduğunda veya barındırma aygıtının bağlantısı kesilip bağlantı geçersiz kaldığında olabilir.\n\nAygıt hala bağlıysa, 'Hayır' seçeneğini seçin, birimi kullanan uygulamaları kapatın ve bağlantıyı kesmeyi yeniden deneyin.\n\nAygıtın bağlantısı kesildiyse ya da bağlantı geçersiz kaldıysa, VeraCrypt dosya sistemini gecikmeli olarak ayırıp VeraCrypt çekirdek nesnelerini kaldırarak veya kaldırılmak üzere zamanlayarak acil temizleme yapmayı deneyebilir. Bekleyen yazma işlemleri başarısız olmuş, veriler kaybolmuş olabilir ve uygulamalar açık dosyaları kapatana kadar temizleme beklemede kalabilir. Yeniden kullanmadan önce dosya sistemini fsck ya da uygun onarım aracıyla denetleyin.\n\nİlerlemek istiyor musunuz?</entry>
+    <entry lang="tr" key="LINUX_EMERGENCY_UNMOUNTED">{0} birimi için acil temizleme başlatıldı. Birimin bağlantısı kesildiyse, bağlantı geçersiz kaldıysa ya da bekleyen yazma işlemleri varsa, yeniden kullanmadan önce dosya sistemini fsck ya da uygun onarım aracıyla denetleyin.</entry>
+    <entry lang="tr" key="FORMAT_STAGE_WRITING_DATA">Birim verileri oluşturuluyor. Lütfen bekleyin.</entry>
+    <entry lang="tr" key="FORMAT_STAGE_WRITING_BACKUP_HEADER">Birim oluşturma tamamlanıyor: yedek üst bilgi yazılıyor.</entry>
+    <entry lang="tr" key="FORMAT_STAGE_FLUSHING_DATA">Birim oluşturma tamamlanıyor: veriler diske aktarılıyor. Bu işlem büyük birimlerde veya yavaş/USB depolamada birkaç dakika sürebilir.</entry>
+    <entry lang="tr" key="FORMAT_STAGE_FINISHED">Birim oluşturma tamamlanıyor.</entry>
+    <entry lang="tr" key="FORMAT_STAGE_ABORTED">Birim oluşturma iptal edildi.</entry>
+    <entry lang="tr" key="FORMAT_STAGE_ERROR">Birim oluşturma başarısız oldu.</entry>
+    <entry lang="tr" key="FORMAT_STAGE_PREPARING_TEMP_VOLUME">Birim oluşturma tamamlanıyor: geçici birim bağlanıyor.</entry>
+    <entry lang="tr" key="FORMAT_STAGE_PREPARING_TEMP_DEVICE">Birim oluşturma tamamlanıyor: geçici aygıt hazırlanıyor.</entry>
+    <entry lang="tr" key="FORMAT_STAGE_CREATING_FILESYSTEM">Birim oluşturma tamamlanıyor: {0} kullanılarak dosya sistemi oluşturuluyor.</entry>
+    <entry lang="tr" key="FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME">Birim oluşturma tamamlanıyor: geçici birimin bağlantısı kesiliyor.</entry>
+    <entry lang="tr" key="MACOSX_APFS_SYNTHESIZED_DEVICE">Seçilmiş aygıt '{0}' sentezlenmiş bir APFS kapsayıcısı ya da birimidir ve ham VeraCrypt birimi barındırmak için kullanılamaz.\n\nBunun yerine fiziksel APFS depolama bölümünü{1} seçin.</entry>
+    <entry lang="tr" key="MACOSX_DEVICE_SYSTEM_PARTITION">Seçilmiş aygıt '{0}' bir macOS sistem/destek bölümüdür ve VeraCrypt birimi barındırmak için kullanılamaz.</entry>
+    <entry lang="tr" key="MACOSX_APFS_SYSTEM_STORE">Seçilmiş fiziksel APFS deposu '{0}', şu anda bağlı olan macOS sistem birimini içeriyor ve VeraCrypt birimi barındırmak için kullanılamaz.</entry>
+    <entry lang="tr" key="MACOSX_DEVICE_NOT_WRITABLE">macOS, seçilmiş aygıtı '{0}' salt okunur olarak bildiriyor. Yazılabilir bir fiziksel bölüm ya da disk seçin.</entry>
+    <entry lang="tr" key="MACOSX_APFS_EROFS_HINT">macOS, seçilmiş aygıtı salt okunur olarak bildirdi. Bu bir APFS diskiyse, APFS sentezlenmiş birimi değil fiziksel APFS depolama bölümünü seçtiğinizden emin olun. Fiziksel bölümü belirlemek için Disk İzlencesi ya da 'diskutil list' komutunu kullanıp yeniden deneyin.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">