From 8b2a3ca9bde898e1ae4ce3d99abdb181b18d7209 Mon Sep 17 00:00:00 2001 From: Matt Van Horn <455140+mvanhorn@users.noreply.github.com> Date: Mon, 29 Jun 2026 07:31:46 -0700 Subject: [PATCH 1/4] fix: clarify outer-vs-hidden credentials in hidden volume protection UI Fixes #1673 --- src/Common/Language.xml | 6 ++++-- src/Mount/Mount.c | 11 ++++++++++- 2 files changed, 14 insertions(+), 3 deletions(-) diff --git a/src/Common/Language.xml b/src/Common/Language.xml index b981636fc5..e84d20d294 100644 --- a/src/Common/Language.xml +++ b/src/Common/Language.xml @@ -89,6 +89,7 @@ Current pool content (partial) Pass Password: + Outer p&assword: Volume PIM: Volume PIM: Progress: @@ -350,8 +351,8 @@ Speed is affected by CPU load and storage device characteristics.\n\nThese tests take place in RAM. Buffer Size: Cipher: - P&assword to hidden volume:\n(if empty, cache is used) - Hidden Volume Protection + Hidden volume p&assword:\n(if empty, cache is used) + Hidden Volume Protection (Hidden Credentials) Key size: IMPORTANT: Move your mouse as randomly as possible within this window. The longer you move it, the better. This significantly increases the cryptographic strength of the keyfile. WARNING: If you lose a keyfile or if any bit of its first 1024 kilobytes changes, it will be impossible to mount volumes that use the keyfile! @@ -637,6 +638,7 @@ Operation failed due to one or more of the following:\n - Wrong mount mode.\n - Incorrect keyfile(s).\n - Incorrect password.\n - Incorrect Volume PIM number.\n - Incorrect PRF (hash).\n - Not a valid volume.\n - Volume uses an old algorithm that has been removed.\n - TrueCrypt format volumes are no longer supported. Auto-mount failed due to one or more of the following:\n - Incorrect password.\n - Incorrect Volume PIM number.\n - Incorrect PRF (hash).\n - No valid volume found.\n - Volume uses an old algorithm that has been removed.\n - TrueCrypt format volumes are no longer supported. Auto-mount failed due to one or more of the following:\n - Incorrect keyfile(s).\n - Incorrect password.\n - Incorrect Volume PIM number.\n - Incorrect PRF (hash).\n - No valid volume found.\n - Volume uses an old algorithm that has been removed.\n - TrueCrypt format volumes are no longer supported. + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER (decoy) volume password, PIM, PRF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, PRF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the selected volume may be invalid or unsupported. \n\nWarning: Caps Lock is on. This may cause you to enter your password incorrectly. Remember Number to Mount Volume Outer Volume PIM diff --git a/src/Mount/Mount.c b/src/Mount/Mount.c index 88a720334f..ac3c350f5b 100644 --- a/src/Mount/Mount.c +++ b/src/Mount/Mount.c @@ -3572,6 +3572,12 @@ static wchar_t PasswordDlgVolume[MAX_PATH + 1]; static BOOL PasswordDialogDisableMountOptions; static char *PasswordDialogTitleStringId; +static void UpdatePasswordDlgPasswordLabel (HWND hwndDlg) +{ + SetDlgItemTextW (hwndDlg, IDT_PASSWORD, + GetString (!PasswordDialogDisableMountOptions && mountOptions.ProtectHiddenVolume ? "IDT_OUTER_VOL_PASSWORD" : "IDT_PASSWORD")); +} + /* Except in response to the WM_INITDIALOG message, the dialog box procedure should return nonzero if it processes the message, and zero if it does not. - see DialogProc */ @@ -3591,6 +3597,7 @@ BOOL CALLBACK PasswordDlgProc (HWND hwndDlg, UINT msg, WPARAM wParam, LPARAM lPa pkcs5 = ((PasswordDlgParam *) lParam) -> pkcs5; pim = ((PasswordDlgParam *) lParam) -> pim; LocalizeDialog (hwndDlg, "IDD_PASSWORD_DLG"); + UpdatePasswordDlgPasswordLabel (hwndDlg); DragAcceptFiles (hwndDlg, TRUE); if (PasswordDialogTitleStringId) @@ -3842,6 +3849,7 @@ BOOL CALLBACK PasswordDlgProc (HWND hwndDlg, UINT msg, WPARAM wParam, LPARAM lPa DialogBoxParamW (hInst, MAKEINTRESOURCEW (IDD_MOUNT_OPTIONS), hwndDlg, (DLGPROC) MountOptionsDlgProc, (LPARAM) &mountOptions); + UpdatePasswordDlgPasswordLabel (hwndDlg); if (!bPrebootPasswordDlgMode && mountOptions.PartitionInInactiveSysEncScope) SendMessage (hwndDlg, TC_APPMSG_PREBOOT_PASSWORD_MODE, 0, 0); @@ -6618,7 +6626,8 @@ static BOOL MountAllDevicesThreadCode (HWND hwndDlg, MountAllDevicesThreadParam* { WCHAR szTmp[4096]; - StringCbPrintfW (szTmp, sizeof(szTmp), GetString (KeyFilesEnable || FirstCmdKeyFile ? "PASSWORD_OR_KEYFILE_WRONG_AUTOMOUNT" : "PASSWORD_WRONG_AUTOMOUNT")); + StringCbPrintfW (szTmp, sizeof(szTmp), + GetString (mountOptions.ProtectHiddenVolume ? "HIDVOL_PROT_PASSWORD_OR_KEYFILE_WRONG" : (KeyFilesEnable || FirstCmdKeyFile ? "PASSWORD_OR_KEYFILE_WRONG_AUTOMOUNT" : "PASSWORD_WRONG_AUTOMOUNT"))); if (CheckCapsLock (hwndDlg, TRUE)) StringCbCatW (szTmp, sizeof(szTmp), GetString ("PASSWORD_WRONG_CAPSLOCK_ON")); From 55ce763f718d2be434ae9438c5a97002e0fe5f77 Mon Sep 17 00:00:00 2001 From: mvanhorn Date: Mon, 6 Jul 2026 07:38:47 -0700 Subject: [PATCH 2/4] Address @idrassi review: clarify hidden-vol-protection credentials - Single-volume mount failures under hidden volume protection now show the clarified HIDVOL_PROT_PASSWORD_OR_KEYFILE_WRONG guidance (via a new GetWrongPasswordErrorMessageEx with a hiddenVolumeProtection flag), not just the Auto-Mount path. The block is reached only for ERR_PASSWORD_WRONG. - Main password dialog now shows an info balloon (HIDVOL_PROT_OUTER_CREDENTIALS_NOTE) noting the dialog expects OUTER volume credentials (password, PIM, PRF/KDF, keyfiles) when hidden volume protection is enabled, covering the PIM/PRF/keyfile ambiguity, not just the password label. - Move the newly added Language.xml entries to the end of the en block so translators can track new strings. --- src/Common/Dlgcode.c | 44 +++++++++++++++++++++++++++-------------- src/Common/Language.xml | 9 +++++---- src/Mount/Mount.c | 15 +++++++++++++- 3 files changed, 48 insertions(+), 20 deletions(-) diff --git a/src/Common/Dlgcode.c b/src/Common/Dlgcode.c index ed03e5b4df..42d427492b 100644 --- a/src/Common/Dlgcode.c +++ b/src/Common/Dlgcode.c @@ -5748,11 +5748,11 @@ BOOL BrowseDirectories(HWND hwndDlg, char *lpszDlgTitle, wchar_t *dirName, const return bOK; } -std::wstring GetWrongPasswordErrorMessage (HWND hwndDlg) +static std::wstring GetWrongPasswordErrorMessageEx (HWND hwndDlg, BOOL hiddenVolumeProtection) { WCHAR szTmp[8192]; - StringCbPrintfW (szTmp, sizeof(szTmp), GetString (KeyFilesEnable ? "PASSWORD_OR_KEYFILE_WRONG" : "PASSWORD_WRONG")); + StringCbPrintfW (szTmp, sizeof(szTmp), GetString (hiddenVolumeProtection ? "HIDVOL_PROT_PASSWORD_OR_KEYFILE_WRONG" : (KeyFilesEnable ? "PASSWORD_OR_KEYFILE_WRONG" : "PASSWORD_WRONG"))); if (CheckCapsLock (hwndDlg, TRUE)) StringCbCatW (szTmp, sizeof(szTmp), GetString ("PASSWORD_WRONG_CAPSLOCK_ON")); @@ -5760,7 +5760,7 @@ std::wstring GetWrongPasswordErrorMessage (HWND hwndDlg) wchar_t szDevicePath [TC_MAX_PATH+1] = {0}; GetWindowText (GetDlgItem (MainDlg, IDC_VOLUME), szDevicePath, ARRAYSIZE (szDevicePath)); - if (TCBootLoaderOnInactiveSysEncDrive (szDevicePath)) + if (!hiddenVolumeProtection && TCBootLoaderOnInactiveSysEncDrive (szDevicePath)) { StringCbPrintfW (szTmp, sizeof(szTmp), GetString (KeyFilesEnable ? "PASSWORD_OR_KEYFILE_OR_MODE_WRONG" : "PASSWORD_OR_MODE_WRONG")); @@ -5784,6 +5784,11 @@ std::wstring GetWrongPasswordErrorMessage (HWND hwndDlg) return msg; } +std::wstring GetWrongPasswordErrorMessage (HWND hwndDlg) +{ + return GetWrongPasswordErrorMessageEx (hwndDlg, FALSE); +} + void handleError (HWND hwndDlg, int code, const char* srcPos) { @@ -9577,24 +9582,33 @@ int MountVolume (HWND hwndDlg, goto retry; } - if (bDevice && mount.bProtectHiddenVolume) + if (mount.bProtectHiddenVolume) { - int diskNo; + BOOL passwordErrorMessageShown = FALSE; - if (swscanf (volumePath, L"\\Device\\Harddisk%d\\Partition", &diskNo) == 1) + if (bDevice) { - OPEN_TEST_STRUCT openTestStruct; - memset (&openTestStruct, 0, sizeof (openTestStruct)); + int diskNo; + + if (swscanf (volumePath, L"\\Device\\Harddisk%d\\Partition", &diskNo) == 1) + { + OPEN_TEST_STRUCT openTestStruct; + memset (&openTestStruct, 0, sizeof (openTestStruct)); - openTestStruct.bDetectTCBootLoader = TRUE; - StringCchPrintfW ((wchar_t *) openTestStruct.wszFileName, array_capacity (openTestStruct.wszFileName), L"\\Device\\Harddisk%d\\Partition0", diskNo); + openTestStruct.bDetectTCBootLoader = TRUE; + StringCchPrintfW ((wchar_t *) openTestStruct.wszFileName, array_capacity (openTestStruct.wszFileName), L"\\Device\\Harddisk%d\\Partition0", diskNo); - DWORD cbBytesReturned; - if (DeviceIoControl (hDriver, TC_IOCTL_OPEN_TEST, &openTestStruct, sizeof (OPEN_TEST_STRUCT), &openTestStruct, sizeof (OPEN_TEST_STRUCT), &cbBytesReturned, NULL) && openTestStruct.TCBootLoaderDetected) - WarningDirect ((GetWrongPasswordErrorMessage (hwndDlg) + L"\n\n" + GetString ("HIDDEN_VOL_PROT_PASSWORD_US_KEYB_LAYOUT")).c_str(), hwndDlg); - else - handleError (hwndDlg, mount.nReturnCode, SRC_POS); + DWORD cbBytesReturned; + if (DeviceIoControl (hDriver, TC_IOCTL_OPEN_TEST, &openTestStruct, sizeof (OPEN_TEST_STRUCT), &openTestStruct, sizeof (OPEN_TEST_STRUCT), &cbBytesReturned, NULL) && openTestStruct.TCBootLoaderDetected) + { + WarningDirect ((GetWrongPasswordErrorMessageEx (hwndDlg, TRUE) + L"\n\n" + GetString ("HIDDEN_VOL_PROT_PASSWORD_US_KEYB_LAYOUT")).c_str(), hwndDlg); + passwordErrorMessageShown = TRUE; + } + } } + + if (!passwordErrorMessageShown) + MessageBoxW (hwndDlg, AppendSrcPos (GetWrongPasswordErrorMessageEx (hwndDlg, TRUE).c_str(), SRC_POS).c_str(), lpszTitle, MB_ICONWARNING); } else handleError (hwndDlg, mount.nReturnCode, SRC_POS); diff --git a/src/Common/Language.xml b/src/Common/Language.xml index e84d20d294..35b72a8e1b 100644 --- a/src/Common/Language.xml +++ b/src/Common/Language.xml @@ -89,7 +89,6 @@ Current pool content (partial) Pass Password: - Outer p&assword: Volume PIM: Volume PIM: Progress: @@ -351,8 +350,6 @@ Speed is affected by CPU load and storage device characteristics.\n\nThese tests take place in RAM. Buffer Size: Cipher: - Hidden volume p&assword:\n(if empty, cache is used) - Hidden Volume Protection (Hidden Credentials) Key size: IMPORTANT: Move your mouse as randomly as possible within this window. The longer you move it, the better. This significantly increases the cryptographic strength of the keyfile. WARNING: If you lose a keyfile or if any bit of its first 1024 kilobytes changes, it will be impossible to mount volumes that use the keyfile! @@ -638,7 +635,6 @@ Operation failed due to one or more of the following:\n - Wrong mount mode.\n - Incorrect keyfile(s).\n - Incorrect password.\n - Incorrect Volume PIM number.\n - Incorrect PRF (hash).\n - Not a valid volume.\n - Volume uses an old algorithm that has been removed.\n - TrueCrypt format volumes are no longer supported. Auto-mount failed due to one or more of the following:\n - Incorrect password.\n - Incorrect Volume PIM number.\n - Incorrect PRF (hash).\n - No valid volume found.\n - Volume uses an old algorithm that has been removed.\n - TrueCrypt format volumes are no longer supported. Auto-mount failed due to one or more of the following:\n - Incorrect keyfile(s).\n - Incorrect password.\n - Incorrect Volume PIM number.\n - Incorrect PRF (hash).\n - No valid volume found.\n - Volume uses an old algorithm that has been removed.\n - TrueCrypt format volumes are no longer supported. - Operation failed while hidden volume protection was enabled.\n\nUse the OUTER (decoy) volume password, PIM, PRF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, PRF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the selected volume may be invalid or unsupported. \n\nWarning: Caps Lock is on. This may cause you to enter your password incorrectly. Remember Number to Mount Volume Outer Volume PIM @@ -1692,6 +1688,11 @@ A Terminal window will open after you press 'OK' and attempt to repair the file system on the selected VeraCrypt volume using 'diskutil'. The result will be shown in that window.\n\nIf the repair cannot be started, Disk Utility will be launched instead. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Hidden volume p&assword:\n(if empty, cache is used) + Hidden Volume Protection (Hidden Credentials) + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER (decoy) volume password, PIM, PRF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, PRF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the selected volume may be invalid or unsupported. + Use OUTER (decoy) volume password, PIM, PRF/KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/src/Mount/Mount.c b/src/Mount/Mount.c index ac3c350f5b..b0e0416f62 100644 --- a/src/Mount/Mount.c +++ b/src/Mount/Mount.c @@ -3576,6 +3576,19 @@ static void UpdatePasswordDlgPasswordLabel (HWND hwndDlg) { SetDlgItemTextW (hwndDlg, IDT_PASSWORD, GetString (!PasswordDialogDisableMountOptions && mountOptions.ProtectHiddenVolume ? "IDT_OUTER_VOL_PASSWORD" : "IDT_PASSWORD")); + + if (!PasswordDialogDisableMountOptions && mountOptions.ProtectHiddenVolume) + { + EDITBALLOONTIP ebt; + ebt.cbStruct = sizeof (EDITBALLOONTIP); + ebt.pszText = GetString ("HIDVOL_PROT_OUTER_CREDENTIALS_NOTE"); + ebt.pszTitle = GetString ("IDT_HIDDEN_VOL_PROTECTION"); + ebt.ttiIcon = TTI_INFO_LARGE; + + SendMessage (GetDlgItem (hwndDlg, IDC_PASSWORD), EM_SHOWBALLOONTIP, 0, (LPARAM) &ebt); + } + else + SendMessage (GetDlgItem (hwndDlg, IDC_PASSWORD), EM_HIDEBALLOONTIP, 0, 0); } /* Except in response to the WM_INITDIALOG message, the dialog box procedure @@ -3597,7 +3610,6 @@ BOOL CALLBACK PasswordDlgProc (HWND hwndDlg, UINT msg, WPARAM wParam, LPARAM lPa pkcs5 = ((PasswordDlgParam *) lParam) -> pkcs5; pim = ((PasswordDlgParam *) lParam) -> pim; LocalizeDialog (hwndDlg, "IDD_PASSWORD_DLG"); - UpdatePasswordDlgPasswordLabel (hwndDlg); DragAcceptFiles (hwndDlg, TRUE); if (PasswordDialogTitleStringId) @@ -3646,6 +3658,7 @@ BOOL CALLBACK PasswordDlgProc (HWND hwndDlg, UINT msg, WPARAM wParam, LPARAM lPa SendMessage (hComboBox, CB_SETCURSEL, defaultPrfIndex, 0); ToNormalPwdField (hwndDlg, IDC_PASSWORD); + UpdatePasswordDlgPasswordLabel (hwndDlg); SendMessage (GetDlgItem (hwndDlg, IDC_CACHE), BM_SETCHECK, bCacheInDriver ? BST_CHECKED:BST_UNCHECKED, 0); SendMessage (GetDlgItem (hwndDlg, IDC_PIM), EM_LIMITTEXT, MAX_PIM, 0); From 890c264fd15842d97dc8c4e848fc448b40d88cc4 Mon Sep 17 00:00:00 2001 From: Matt Van Horn <455140+mvanhorn@users.noreply.github.com> Date: Thu, 16 Jul 2026 21:16:45 -0700 Subject: [PATCH 3/4] Address review: restore entries, combine SysEnc note, common message path, translations - Language.xml: restore IDT_HIDDEN_PROT_PASSWD and IDT_HIDDEN_VOL_PROTECTION to their original position and text; use 'outer volume' (not 'decoy'), 'KDF' consistently, and drop 'selected volume' from the wrong-credentials message. - GetWrongPasswordErrorMessageEx: append SYSENC_MOUNT_WITHOUT_PBA_NOTE for the hidden-volume-protection path too (previously skipped), keeping the wrong-mode message for the non-hidden path only. - Route the hidden-protection wrong-password message through WarningDirect instead of a direct MessageBoxW so Silent handling is respected. - Add the three new string keys to all 42 translation files so XML validation passes (English placeholder pending localization). --- Translations/Language.ar.xml | 3 +++ Translations/Language.be.xml | 3 +++ Translations/Language.bg.xml | 3 +++ Translations/Language.ca.xml | 3 +++ Translations/Language.co.xml | 3 +++ Translations/Language.cs.xml | 3 +++ Translations/Language.da.xml | 3 +++ Translations/Language.de.xml | 3 +++ Translations/Language.el.xml | 3 +++ Translations/Language.es.xml | 3 +++ Translations/Language.et.xml | 3 +++ Translations/Language.eu.xml | 3 +++ Translations/Language.fa.xml | 3 +++ Translations/Language.fi.xml | 3 +++ Translations/Language.fr.xml | 3 +++ Translations/Language.he.xml | 3 +++ Translations/Language.hu.xml | 3 +++ Translations/Language.id.xml | 3 +++ Translations/Language.it.xml | 3 +++ Translations/Language.ja.xml | 3 +++ Translations/Language.ka.xml | 3 +++ Translations/Language.ko.xml | 3 +++ Translations/Language.lv.xml | 3 +++ Translations/Language.my.xml | 3 +++ Translations/Language.nb.xml | 3 +++ Translations/Language.nl.xml | 3 +++ Translations/Language.nn.xml | 3 +++ Translations/Language.pl.xml | 3 +++ Translations/Language.pt-br.xml | 3 +++ Translations/Language.ro.xml | 3 +++ Translations/Language.ru.xml | 3 +++ Translations/Language.sk.xml | 3 +++ Translations/Language.sl.xml | 3 +++ Translations/Language.sv.xml | 3 +++ Translations/Language.th.xml | 3 +++ Translations/Language.tr.xml | 3 +++ Translations/Language.uk.xml | 3 +++ Translations/Language.uz.xml | 3 +++ Translations/Language.vi.xml | 3 +++ Translations/Language.zh-cn.xml | 3 +++ Translations/Language.zh-hk.xml | 3 +++ Translations/Language.zh-tw.xml | 3 +++ src/Common/Dlgcode.c | 13 ++++++++----- src/Common/Language.xml | 8 ++++---- 44 files changed, 138 insertions(+), 9 deletions(-) diff --git a/Translations/Language.ar.xml b/Translations/Language.ar.xml index be3de3d5fc..e9901404fa 100644 --- a/Translations/Language.ar.xml +++ b/Translations/Language.ar.xml @@ -1690,6 +1690,9 @@ ‮ستفتح نافذة الطرفية بعد الضغط على 'موافق' وستحاول إصلاح نظام الملفات على مجلد ڤيراكربت المحدد باستخدام 'diskutil'. ستُعرض النتيجة في تلك النافذة.\n\nإذا تعذر بدء الإصلاح، فسيتم تشغيل أداة القرص بدلاً من ذلك. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.be.xml b/Translations/Language.be.xml index 090ac4c97e..09a373d887 100644 --- a/Translations/Language.be.xml +++ b/Translations/Language.be.xml @@ -1690,6 +1690,9 @@ Пасля націску 'OK' адкрыецца акно Тэрмінала, у якім будзе выканана спроба аднавіць файлавую сістэму выбранага тома VeraCrypt з дапамогай 'diskutil'. Вынік будзе паказаны ў гэтым акне.\n\nКалі аднаўленне немагчыма запусціць, замест гэтага будзе запушчана Дыскавая ўтыліта. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.bg.xml b/Translations/Language.bg.xml index df7fd2a231..feedbb691e 100644 --- a/Translations/Language.bg.xml +++ b/Translations/Language.bg.xml @@ -1690,6 +1690,9 @@ След като натиснете 'OK', ще се отвори прозорец на Терминал и ще се опита да поправи файловата система на избрания том VeraCrypt чрез 'diskutil'. Резултатът ще бъде показан в този прозорец.\n\nАко поправката не може да бъде стартирана, вместо това ще бъде стартирана Дискова помощна програма. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.ca.xml b/Translations/Language.ca.xml index d9eea51256..aa0399d7f4 100644 --- a/Translations/Language.ca.xml +++ b/Translations/Language.ca.xml @@ -1690,6 +1690,9 @@ Després de prémer 'OK', s'obrirà una finestra del Terminal i s'intentarà reparar el sistema de fitxers del volum VeraCrypt seleccionat amb 'diskutil'. El resultat es mostrarà en aquesta finestra.\n\nSi no es pot iniciar la reparació, s'obrirà la Utilitat de Discos. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.co.xml b/Translations/Language.co.xml index 254f439e70..dfd2b4ab95 100644 --- a/Translations/Language.co.xml +++ b/Translations/Language.co.xml @@ -1712,6 +1712,9 @@ Information about Corsican localization: Una finestra di terminale s’aprerà dopu avè appughjatu nant’à « Vai » è ci serà un tentativu di riparà u sistema di schedariu nant’à u vulume VeraCrypt selezziunatu impieghendu « diskutil ». U risultatu serà affissatu in quella finestra.\n\nS’è a riparazione ùn pò principià, « Disk Utility » serà lanciatu in rimpiazzamentu. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.cs.xml b/Translations/Language.cs.xml index fbc7558482..8889f54983 100644 --- a/Translations/Language.cs.xml +++ b/Translations/Language.cs.xml @@ -1690,6 +1690,9 @@ Po stisknutí tlačítka „OK” se otevře okno Terminálu, ve kterém bude pomocí příkazu 'diskutil' proveden pokus o opravu systému souborů vybraného svazku VeraCryptu. Výsledek se zobrazí v tomto okně.\n\nPokud opravu nelze spustit, bude místo toho spuštěna Disková utilita. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.da.xml b/Translations/Language.da.xml index 71ef369e3f..82493c44ce 100644 --- a/Translations/Language.da.xml +++ b/Translations/Language.da.xml @@ -1690,6 +1690,9 @@ Et Terminal-vindue åbnes, når du trykker på 'OK', og forsøger at reparere filsystemet på det valgte VeraCrypt-bind med 'diskutil'. Resultatet vises i det vindue.\n\nHvis reparationen ikke kan startes, startes Diskværktøj i stedet. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.de.xml b/Translations/Language.de.xml index b384b15d56..80cee1ffb9 100644 --- a/Translations/Language.de.xml +++ b/Translations/Language.de.xml @@ -1693,6 +1693,9 @@ A Terminal window will open after you press 'OK' and attempt to repair the file system on the selected VeraCrypt volume using 'diskutil'. The result will be shown in that window.\n\nIf the repair cannot be started, Disk Utility will be launched instead. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.el.xml b/Translations/Language.el.xml index 02bd23ec17..aa7d3e0f6e 100644 --- a/Translations/Language.el.xml +++ b/Translations/Language.el.xml @@ -1690,6 +1690,9 @@ Αφού πατήσετε 'OK', θα ανοίξει ένα παράθυρο Τερματικού και θα γίνει προσπάθεια επιδιόρθωσης του συστήματος αρχείων στον επιλεγμένο τόμο VeraCrypt χρησιμοποιώντας το 'diskutil'. Το αποτέλεσμα θα εμφανιστεί σε αυτό το παράθυρο.\n\nΕάν η επιδιόρθωση δεν μπορεί να ξεκινήσει, θα εκκινηθεί αντ' αυτού το Βοήθημα Δίσκων. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.es.xml b/Translations/Language.es.xml index 89da701d0b..38ff0e4200 100644 --- a/Translations/Language.es.xml +++ b/Translations/Language.es.xml @@ -1690,6 +1690,9 @@ Después de pulsar 'Aceptar', se abrirá una ventana de Terminal para intentar reparar el sistema de archivos del volumen VeraCrypt seleccionado usando 'diskutil'. El resultado se mostrará en esa ventana.\n\nSi no se puede iniciar la reparación, se iniciará en su lugar la Utilidad de Discos. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.et.xml b/Translations/Language.et.xml index a100cd2940..13c431c4ad 100644 --- a/Translations/Language.et.xml +++ b/Translations/Language.et.xml @@ -1690,6 +1690,9 @@ Pärast nupu 'Olgu' vajutamist avaneb Terminali aken ja valitud VeraCrypti köite failisüsteemi üritatakse parandada käsuga 'diskutil'. Tulemus kuvatakse selles aknas.\n\nKui parandust ei saa käivitada, käivitatakse selle asemel Kettautiliit. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.eu.xml b/Translations/Language.eu.xml index 6cdfcc5404..dc7c97f469 100644 --- a/Translations/Language.eu.xml +++ b/Translations/Language.eu.xml @@ -1690,6 +1690,9 @@ 'Ados' sakatu ondoren Terminal leiho bat irekiko da eta hautatutako VeraCrypt bolumenaren fitxategi sistema konpontzen saiatuko da 'diskutil' erabiliz. Emaitza leiho horretan erakutsiko da.\n\nKonponketa ezin bada hasi, Disko-utilitatea abiaraziko da horren ordez. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.fa.xml b/Translations/Language.fa.xml index fe360be01a..a72919d306 100644 --- a/Translations/Language.fa.xml +++ b/Translations/Language.fa.xml @@ -1690,6 +1690,9 @@ پس از فشار دادن 'قبول'، یک پنجره Terminal باز می‌شود و تلاش می‌کند فایل سیستم حجم VeraCrypt انتخاب‌شده را با استفاده از 'diskutil' تعمیر کند. نتیجه در همان پنجره نمایش داده می‌شود.\n\nاگر تعمیر قابل شروع نباشد، به‌جای آن Disk Utility اجرا خواهد شد. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.fi.xml b/Translations/Language.fi.xml index e72babfe5d..fe2c6d3ffe 100644 --- a/Translations/Language.fi.xml +++ b/Translations/Language.fi.xml @@ -1690,6 +1690,9 @@ Kun painat 'OK', Pääte-ikkuna avautuu ja siinä yritetään korjata valitun VeraCrypt-taltion tiedostojärjestelmä komennolla 'diskutil'. Tulos näytetään kyseisessä ikkunassa.\n\nJos korjausta ei voida käynnistää, Levytyökalu käynnistetään sen sijaan. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.fr.xml b/Translations/Language.fr.xml index f7a445501a..bac8e69157 100644 --- a/Translations/Language.fr.xml +++ b/Translations/Language.fr.xml @@ -1690,6 +1690,9 @@ Après avoir cliqué sur 'OK', une fenêtre Terminal s’ouvrira pour tenter de réparer le système de fichiers du volume VeraCrypt sélectionné à l’aide de 'diskutil'. Le résultat sera affiché dans cette fenêtre.\n\nSi la réparation ne peut pas être lancée, l’Utilitaire de disque sera lancé à la place. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.he.xml b/Translations/Language.he.xml index fac73669b2..58500d9b72 100644 --- a/Translations/Language.he.xml +++ b/Translations/Language.he.xml @@ -1690,6 +1690,9 @@ לאחר שתלחץ על 'אישור', ייפתח חלון Terminal וייעשה ניסיון לתקן את מערכת הקבצים באמצעי האחסון VeraCrypt שנבחר באמצעות 'diskutil'. התוצאה תוצג בחלון זה.\n\nאם לא ניתן להתחיל את התיקון, יופעל במקום זאת כלי העזר לכוננים. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.hu.xml b/Translations/Language.hu.xml index 953dab23e7..094eb4605b 100644 --- a/Translations/Language.hu.xml +++ b/Translations/Language.hu.xml @@ -1690,6 +1690,9 @@ Az 'OK' megnyomása után megnyílik egy Terminál ablak, és megkísérli kijavítani a kiválasztott VeraCrypt kötet fájlrendszerét a 'diskutil' segítségével. Az eredmény ebben az ablakban jelenik meg.\n\nHa a javítás nem indítható el, helyette a Lemezkezelő indul el. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.id.xml b/Translations/Language.id.xml index 7fd25dc77b..243154900d 100644 --- a/Translations/Language.id.xml +++ b/Translations/Language.id.xml @@ -1690,6 +1690,9 @@ Sebuah jendela Terminal akan terbuka setelah Anda menekan 'Ok' dan mencoba memperbaiki sistem berkas pada volume VeraCrypt yang dipilih menggunakan 'diskutil'. Hasilnya akan ditampilkan di jendela tersebut.\n\nJika perbaikan tidak dapat dimulai, Utilitas Disk akan dijalankan sebagai gantinya. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.it.xml b/Translations/Language.it.xml index 786a8d6422..7139ac386b 100644 --- a/Translations/Language.it.xml +++ b/Translations/Language.it.xml @@ -1690,6 +1690,9 @@ Dopo aver premuto 'OK' si aprirà una finestra del Terminale che tenterà di riparare il file system del volume VeraCrypt selezionato usando 'diskutil'. Il risultato sarà mostrato in quella finestra.\n\nSe la riparazione non può essere avviata, verrà avviata Utility Disco al suo posto. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.ja.xml b/Translations/Language.ja.xml index 80f4521826..76cb51eb42 100644 --- a/Translations/Language.ja.xml +++ b/Translations/Language.ja.xml @@ -1690,6 +1690,9 @@ [OK] を押すとターミナルウィンドウが開き、'diskutil' を使用して選択された VeraCrypt ボリュームのファイルシステムの修復を試みます。結果はそのウィンドウに表示されます。\n\n修復を開始できない場合は、代わりにディスクユーティリティが起動します。 Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.ka.xml b/Translations/Language.ka.xml index 403ffcda09..14523317e8 100644 --- a/Translations/Language.ka.xml +++ b/Translations/Language.ka.xml @@ -1690,6 +1690,9 @@ 'დიახ' ღილაკზე დაჭერის შემდეგ გაიხსნება ტერმინალის ფანჯარა და 'diskutil'-ის გამოყენებით მოხდება არჩეული VeraCrypt ტომის ფაილური სისტემის შეკეთების მცდელობა. შედეგი გამოჩნდება ამ ფანჯარაში.\n\nთუ შეკეთება ვერ დაიწყება, მის ნაცვლად გაეშვება დისკის უტილიტა. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.ko.xml b/Translations/Language.ko.xml index 0330c03318..8788313e6f 100644 --- a/Translations/Language.ko.xml +++ b/Translations/Language.ko.xml @@ -1690,6 +1690,9 @@ '확인'을 누르면 터미널 창이 열리고 'diskutil'을 사용하여 선택한 VeraCrypt 볼륨의 파일 시스템 복구를 시도합니다. 결과는 해당 창에 표시됩니다.\n\n복구를 시작할 수 없으면 대신 디스크 유틸리티가 실행됩니다. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.lv.xml b/Translations/Language.lv.xml index eb2d202853..707a9ce58a 100644 --- a/Translations/Language.lv.xml +++ b/Translations/Language.lv.xml @@ -1690,6 +1690,9 @@ Pēc pogas 'Labi' nospiešanas tiks atvērts Termināļa logs un, izmantojot 'diskutil', tiks mēģināts salabot atlasītā VeraCrypt sējuma datņu sistēmu. Rezultāts tiks parādīts šajā logā.\n\nJa labošanu nevarēs sākt, tās vietā tiks palaista Diska utilīta. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.my.xml b/Translations/Language.my.xml index 399f9085eb..dd195b0b73 100644 --- a/Translations/Language.my.xml +++ b/Translations/Language.my.xml @@ -1692,6 +1692,9 @@ 'ကောင်းပြီ' ကို နှိပ်ပြီးနောက် Terminal ဝင်းဒိုးတစ်ခု ဖွင့်လာမည်ဖြစ်ပြီး ရွေးချယ်ထားသော VeraCrypt volume ပေါ်ရှိ ဖိုင်စနစ်ကို 'diskutil' ဖြင့် ပြင်ဆင်ရန် ကြိုးစားမည်။ ရလဒ်ကို ထိုဝင်းဒိုးတွင် ပြသမည်။\n\nပြင်ဆင်မှုကို စတင်၍ မရပါက Disk Utility ကို အစားထိုး ဖွင့်ပါမည်။ Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.nb.xml b/Translations/Language.nb.xml index d2463ebe4b..fcd163071d 100644 --- a/Translations/Language.nb.xml +++ b/Translations/Language.nb.xml @@ -1690,6 +1690,9 @@ Et terminalvindu åpnes etter at du har trykket på «OK», og det forsøkes å reparere filsystemet på det valgte VeraCrypt-volumet ved hjelp av «diskutil». Resultatet vises i det vinduet.\n\nHvis reparasjonen ikke kan startes, åpnes Diskverktøy i stedet. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.nl.xml b/Translations/Language.nl.xml index b33066b90e..1c8e4afde1 100644 --- a/Translations/Language.nl.xml +++ b/Translations/Language.nl.xml @@ -1690,6 +1690,9 @@ Nadat u op 'OK' hebt geklikt, wordt er een terminalvenster geopend en wordt er geprobeerd om het bestandssysteem op het geselecteerde VeraCrypt-volume te herstellen met behulp van 'diskutil'. Het resultaat wordt in dat venster weergegeven.\n\nAls het herstel niet kan worden gestart, wordt in plaats daarvan Schijfhulpprogramma gestart. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.nn.xml b/Translations/Language.nn.xml index 59c5ff2280..64448aa46e 100644 --- a/Translations/Language.nn.xml +++ b/Translations/Language.nn.xml @@ -1690,6 +1690,9 @@ Eit Terminal-vindauge blir opna etter at du trykkjer på 'OK', og det blir prøvd å reparera filsystemet på det valde VeraCrypt-volumet med 'diskutil'. Resultatet blir vist i det vindauget.\n\nOm reparasjonen ikkje kan startast, blir Diskverktøy starta i staden. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.pl.xml b/Translations/Language.pl.xml index 0021d6da52..52a19d0e03 100644 --- a/Translations/Language.pl.xml +++ b/Translations/Language.pl.xml @@ -1690,6 +1690,9 @@ Po kliknięciu przycisku „OK” otworzy się okno Terminala, w którym zostanie podjęta próba naprawy systemu plików na wybranym wolumenie VeraCrypt za pomocą polecenia „diskutil”. Wynik zostanie wyświetlony w tym oknie.\n\nJeśli nie uda się uruchomić naprawy, zamiast tego uruchomi się Narzędzie dyskowe. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.pt-br.xml b/Translations/Language.pt-br.xml index d24f3588fe..5c2f01ccd0 100644 --- a/Translations/Language.pt-br.xml +++ b/Translations/Language.pt-br.xml @@ -1690,6 +1690,9 @@ Após você pressionar 'OK', uma janela do Terminal será aberta para tentar reparar o sistema de arquivos do volume VeraCrypt selecionado usando 'diskutil'. O resultado será mostrado nessa janela.\n\nSe o reparo não puder ser iniciado, o Utilitário de Disco será iniciado em seu lugar. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.ro.xml b/Translations/Language.ro.xml index 5bf7372081..befe96360a 100644 --- a/Translations/Language.ro.xml +++ b/Translations/Language.ro.xml @@ -1690,6 +1690,9 @@ După ce apăsați pe „OK”, se va deschide o fereastră a aplicației Terminal, iar folosind „diskutil” se va încerca repararea sistemului de fișiere de pe volumul VeraCrypt selectat. Rezultatul va fi afișat în acea fereastră.\n\nDacă repararea nu poate fi pornită, se va lansa în schimb „Utilitar disc”. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.ru.xml b/Translations/Language.ru.xml index e6d6c9cc17..b5d67caf2f 100644 --- a/Translations/Language.ru.xml +++ b/Translations/Language.ru.xml @@ -1690,6 +1690,9 @@ После нажатия 'OK' откроется окно Терминала, в котором с помощью 'diskutil' будет выполнена попытка исправить файловую систему выбранного тома VeraCrypt. Результат будет показан в этом окне.\n\nЕсли исправление не удастся запустить, вместо него будет запущена Дисковая утилита. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.sk.xml b/Translations/Language.sk.xml index a021e6788a..eeac220a7b 100644 --- a/Translations/Language.sk.xml +++ b/Translations/Language.sk.xml @@ -1690,6 +1690,9 @@ Po stlačení tlačidla 'OK' sa otvorí okno Terminálu a pomocou 'diskutil' sa vykoná pokus o opravu systému súborov na vybranom zväzku VeraCrypt. Výsledok sa zobrazí v tomto okne.\n\nAk opravu nemožno spustiť, namiesto toho sa spustí Disková utilita. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.sl.xml b/Translations/Language.sl.xml index f9600ea570..5333568dff 100644 --- a/Translations/Language.sl.xml +++ b/Translations/Language.sl.xml @@ -1690,6 +1690,9 @@ Ko pritisneš 'V redu', se bo odprlo okno Terminala, v katerem se bo z ukazom 'diskutil' poskusilo popraviti datotečni sistem izbranega nosilca VeraCrypt. Rezultat bo prikazan v tem oknu.\n\nČe popravila ni mogoče zagnati, se bo namesto tega zagnal Disk Utility. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.sv.xml b/Translations/Language.sv.xml index f0dcbe2013..25ef26fe04 100644 --- a/Translations/Language.sv.xml +++ b/Translations/Language.sv.xml @@ -1690,6 +1690,9 @@ Ett Terminal-fönster öppnas när du trycker på "OK" och försöker reparera filsystemet på den valda VeraCrypt-volymen med "diskutil". Resultatet visas i fönstret.\n\nOm reparationen inte kan startas öppnas Skivverktyg i stället. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.th.xml b/Translations/Language.th.xml index 125d6fa168..21839f07ab 100644 --- a/Translations/Language.th.xml +++ b/Translations/Language.th.xml @@ -1690,6 +1690,9 @@ หน้าต่าง Terminal จะเปิดขึ้นหลังจากคุณกด 'ตกลง' และจะพยายามซ่อมแซมระบบไฟล์บนวอลุ่ม VeraCrypt ที่เลือกโดยใช้ 'diskutil' ผลลัพธ์จะแสดงในหน้าต่างนั้น\n\nหากไม่สามารถเริ่มการซ่อมแซมได้ Disk Utility จะถูกเปิดแทน Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.tr.xml b/Translations/Language.tr.xml index f63ba959e9..a050ebc5ae 100644 --- a/Translations/Language.tr.xml +++ b/Translations/Language.tr.xml @@ -1690,6 +1690,9 @@ 'Tamam' üzerine tıkladıktan sonra bir Terminal penceresi açılacak ve 'diskutil' kullanılarak seçilmiş VeraCrypt biriminin dosya sistemi onarılmaya çalışılacak. Sonuç bu pencerede görüntülenecek.\n\nOnarım başlatılamazsa, bunun yerine Disk İzlencesi başlatılacak. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.uk.xml b/Translations/Language.uk.xml index 53af8abba0..9f76454827 100644 --- a/Translations/Language.uk.xml +++ b/Translations/Language.uk.xml @@ -1690,6 +1690,9 @@ Після натискання 'Гаразд' відкриється вікно Термінала, у якому за допомогою 'diskutil' буде виконано спробу виправити файлову систему вибраного тому VeraCrypt. Результат буде показано в цьому вікні.\n\nЯкщо виправлення неможливо запустити, натомість буде запущено Дискову утиліту. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.uz.xml b/Translations/Language.uz.xml index ad896f3940..7b0fb335bd 100644 --- a/Translations/Language.uz.xml +++ b/Translations/Language.uz.xml @@ -1690,6 +1690,9 @@ 'OK' тугмасини босганингиздан сўнг Терминал ойнаси очилади ва танланган VeraCrypt томидаги файл тизимини 'diskutil' ёрдамида тузатишга уриниб кўрилади. Натижа шу ойнада кўрсатилади.\n\nАгар тузатишни бошлаб бўлмаса, унинг ўрнига Диск утилитаси ишга туширилади. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.vi.xml b/Translations/Language.vi.xml index f7c02a8619..420d0897b1 100644 --- a/Translations/Language.vi.xml +++ b/Translations/Language.vi.xml @@ -1690,6 +1690,9 @@ Một cửa sổ Terminal sẽ mở sau khi bạn bấm 'Đồng ý' và thử sửa chữa hệ thống tập tin trên tập đĩa VeraCrypt đã chọn bằng 'diskutil'. Kết quả sẽ được hiển thị trong cửa sổ đó.\n\nNếu không thể bắt đầu sửa chữa, Tiện ích Ổ đĩa sẽ được khởi chạy thay thế. Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.zh-cn.xml b/Translations/Language.zh-cn.xml index e7c4d945b0..7658ec9c49 100644 --- a/Translations/Language.zh-cn.xml +++ b/Translations/Language.zh-cn.xml @@ -1691,6 +1691,9 @@ 按下“确定”后，将打开“终端”窗口，并尝试使用 'diskutil' 修复所选 VeraCrypt 卷上的文件系统。结果将显示在该窗口中。\n\n如果无法开始修复，则将改为启动“磁盘工具”。 Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.zh-hk.xml b/Translations/Language.zh-hk.xml index bf73522f94..72aaf20376 100644 --- a/Translations/Language.zh-hk.xml +++ b/Translations/Language.zh-hk.xml @@ -1690,6 +1690,9 @@ 按下 [確定] 後，將會開啟「終端機」視窗，並使用 'diskutil' 嘗試修復所選 VeraCrypt 加密區上的檔案系統。結果會顯示在該視窗中。\n\n如果無法開始修復，將會改為啟動「磁碟工具程式」。 Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/Translations/Language.zh-tw.xml b/Translations/Language.zh-tw.xml index da0391eecd..da3a72d15e 100644 --- a/Translations/Language.zh-tw.xml +++ b/Translations/Language.zh-tw.xml @@ -1690,6 +1690,9 @@ 按下「確定」後，將會開啟「終端機」視窗，並使用「diskutil」嘗試修復所選 VeraCrypt 加密區上的檔案系統。結果會顯示在該視窗中。\n\n如果無法開始修復，將會改為啟動「磁碟工具程式」。 Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. + Outer p&assword: + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. diff --git a/src/Common/Dlgcode.c b/src/Common/Dlgcode.c index 42d427492b..11ed51f27b 100644 --- a/src/Common/Dlgcode.c +++ b/src/Common/Dlgcode.c @@ -5760,12 +5760,15 @@ static std::wstring GetWrongPasswordErrorMessageEx (HWND hwndDlg, BOOL hiddenVol wchar_t szDevicePath [TC_MAX_PATH+1] = {0}; GetWindowText (GetDlgItem (MainDlg, IDC_VOLUME), szDevicePath, ARRAYSIZE (szDevicePath)); - if (!hiddenVolumeProtection && TCBootLoaderOnInactiveSysEncDrive (szDevicePath)) + if (TCBootLoaderOnInactiveSysEncDrive (szDevicePath)) { - StringCbPrintfW (szTmp, sizeof(szTmp), GetString (KeyFilesEnable ? "PASSWORD_OR_KEYFILE_OR_MODE_WRONG" : "PASSWORD_OR_MODE_WRONG")); + if (!hiddenVolumeProtection) + { + StringCbPrintfW (szTmp, sizeof(szTmp), GetString (KeyFilesEnable ? "PASSWORD_OR_KEYFILE_OR_MODE_WRONG" : "PASSWORD_OR_MODE_WRONG")); - if (CheckCapsLock (hwndDlg, TRUE)) - StringCbCatW (szTmp, sizeof(szTmp), GetString ("PASSWORD_WRONG_CAPSLOCK_ON")); + if (CheckCapsLock (hwndDlg, TRUE)) + StringCbCatW (szTmp, sizeof(szTmp), GetString ("PASSWORD_WRONG_CAPSLOCK_ON")); + } StringCbCatW (szTmp, sizeof(szTmp), GetString ("SYSENC_MOUNT_WITHOUT_PBA_NOTE")); } @@ -9608,7 +9611,7 @@ int MountVolume (HWND hwndDlg, } if (!passwordErrorMessageShown) - MessageBoxW (hwndDlg, AppendSrcPos (GetWrongPasswordErrorMessageEx (hwndDlg, TRUE).c_str(), SRC_POS).c_str(), lpszTitle, MB_ICONWARNING); + WarningDirect (AppendSrcPos (GetWrongPasswordErrorMessageEx (hwndDlg, TRUE).c_str(), SRC_POS).c_str(), hwndDlg); } else handleError (hwndDlg, mount.nReturnCode, SRC_POS); diff --git a/src/Common/Language.xml b/src/Common/Language.xml index 35b72a8e1b..2c81af0d80 100644 --- a/src/Common/Language.xml +++ b/src/Common/Language.xml @@ -350,6 +350,8 @@ Speed is affected by CPU load and storage device characteristics.\n\nThese tests take place in RAM. Buffer Size: Cipher: + P&assword to hidden volume:\n(if empty, cache is used) + Hidden Volume Protection Key size: IMPORTANT: Move your mouse as randomly as possible within this window. The longer you move it, the better. This significantly increases the cryptographic strength of the keyfile. WARNING: If you lose a keyfile or if any bit of its first 1024 kilobytes changes, it will be impossible to mount volumes that use the keyfile! @@ -1689,10 +1691,8 @@ Warning: Secure Boot is enabled, but the Microsoft UEFI CA that signs the installed VeraCrypt EFI bootloader was not found in the firmware Secure Boot database (db). The firmware may refuse to start VeraCrypt at the next reboot, so Windows will not start until Secure Boot is disabled or the trusted certificates/loader set are repaired.\n\nBefore restarting this computer, do not disable or remove Microsoft Corporation UEFI CA 2011 unless the firmware db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and VeraCrypt has been repaired/reinstalled so the 2023-signed loader set is installed. Enable the required Microsoft certificates in the BIOS/UEFI settings if needed, then run VeraCrypt Repair/Reinstall. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: - Hidden volume p&assword:\n(if empty, cache is used) - Hidden Volume Protection (Hidden Credentials) - Operation failed while hidden volume protection was enabled.\n\nUse the OUTER (decoy) volume password, PIM, PRF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, PRF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the selected volume may be invalid or unsupported. - Use OUTER (decoy) volume password, PIM, PRF/KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. + Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. From 3c0f42ac2781ae31137513cd6fc122d1b0de49c4 Mon Sep 17 00:00:00 2001 From: Matt Van Horn <455140+mvanhorn@users.noreply.github.com> Date: Mon, 20 Jul 2026 08:46:19 -0700 Subject: [PATCH 4/4] docs(i18n): address review issues across language XML files Fix the issues listed in review: key completeness against the 1687-key set, escape validation, and the five review invariants, across all 43 language files. --- Translations/Language.ar.xml | 2 +- Translations/Language.be.xml | 2 +- Translations/Language.bg.xml | 2 +- Translations/Language.ca.xml | 2 +- Translations/Language.co.xml | 2 +- Translations/Language.cs.xml | 2 +- Translations/Language.da.xml | 2 +- Translations/Language.de.xml | 2 +- Translations/Language.el.xml | 2 +- Translations/Language.es.xml | 2 +- Translations/Language.et.xml | 2 +- Translations/Language.eu.xml | 2 +- Translations/Language.fa.xml | 2 +- Translations/Language.fi.xml | 2 +- Translations/Language.fr.xml | 2 +- Translations/Language.he.xml | 2 +- Translations/Language.hu.xml | 2 +- Translations/Language.id.xml | 2 +- Translations/Language.it.xml | 2 +- Translations/Language.ja.xml | 2 +- Translations/Language.ka.xml | 2 +- Translations/Language.ko.xml | 2 +- Translations/Language.lv.xml | 2 +- Translations/Language.my.xml | 2 +- Translations/Language.nb.xml | 2 +- Translations/Language.nl.xml | 2 +- Translations/Language.nn.xml | 2 +- Translations/Language.pl.xml | 2 +- Translations/Language.pt-br.xml | 2 +- Translations/Language.ro.xml | 2 +- Translations/Language.ru.xml | 2 +- Translations/Language.sk.xml | 2 +- Translations/Language.sl.xml | 2 +- Translations/Language.sv.xml | 2 +- Translations/Language.th.xml | 2 +- Translations/Language.tr.xml | 2 +- Translations/Language.uk.xml | 2 +- Translations/Language.uz.xml | 2 +- Translations/Language.vi.xml | 2 +- Translations/Language.zh-cn.xml | 2 +- Translations/Language.zh-hk.xml | 2 +- Translations/Language.zh-tw.xml | 2 +- src/Common/Language.xml | 2 +- src/Mount/Mount.c | 26 +++++++++++++++----------- src/Mount/Mount.rc | 5 +++-- src/Mount/Resource.h | 3 ++- 46 files changed, 63 insertions(+), 57 deletions(-) diff --git a/Translations/Language.ar.xml b/Translations/Language.ar.xml index e9901404fa..6a8cf17f96 100644 --- a/Translations/Language.ar.xml +++ b/Translations/Language.ar.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.be.xml b/Translations/Language.be.xml index 09a373d887..fa0a74d448 100644 --- a/Translations/Language.be.xml +++ b/Translations/Language.be.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.bg.xml b/Translations/Language.bg.xml index feedbb691e..add4942b11 100644 --- a/Translations/Language.bg.xml +++ b/Translations/Language.bg.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.ca.xml b/Translations/Language.ca.xml index aa0399d7f4..66086d99a2 100644 --- a/Translations/Language.ca.xml +++ b/Translations/Language.ca.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.co.xml b/Translations/Language.co.xml index dfd2b4ab95..9c05786b0c 100644 --- a/Translations/Language.co.xml +++ b/Translations/Language.co.xml @@ -1714,7 +1714,7 @@ Information about Corsican localization: Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.cs.xml b/Translations/Language.cs.xml index 8889f54983..feb9acc481 100644 --- a/Translations/Language.cs.xml +++ b/Translations/Language.cs.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.da.xml b/Translations/Language.da.xml index 82493c44ce..60e55474f5 100644 --- a/Translations/Language.da.xml +++ b/Translations/Language.da.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.de.xml b/Translations/Language.de.xml index 80cee1ffb9..1355407cd3 100644 --- a/Translations/Language.de.xml +++ b/Translations/Language.de.xml @@ -1695,7 +1695,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.el.xml b/Translations/Language.el.xml index aa7d3e0f6e..e5727b25fe 100644 --- a/Translations/Language.el.xml +++ b/Translations/Language.el.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.es.xml b/Translations/Language.es.xml index 38ff0e4200..a05b41b652 100644 --- a/Translations/Language.es.xml +++ b/Translations/Language.es.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.et.xml b/Translations/Language.et.xml index 13c431c4ad..47b39a91dc 100644 --- a/Translations/Language.et.xml +++ b/Translations/Language.et.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.eu.xml b/Translations/Language.eu.xml index dc7c97f469..eba5173f89 100644 --- a/Translations/Language.eu.xml +++ b/Translations/Language.eu.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.fa.xml b/Translations/Language.fa.xml index a72919d306..c2b6ec5777 100644 --- a/Translations/Language.fa.xml +++ b/Translations/Language.fa.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.fi.xml b/Translations/Language.fi.xml index fe2c6d3ffe..476bd9668e 100644 --- a/Translations/Language.fi.xml +++ b/Translations/Language.fi.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.fr.xml b/Translations/Language.fr.xml index bac8e69157..5304fe7ea5 100644 --- a/Translations/Language.fr.xml +++ b/Translations/Language.fr.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.he.xml b/Translations/Language.he.xml index 58500d9b72..fc9b98c9d9 100644 --- a/Translations/Language.he.xml +++ b/Translations/Language.he.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.hu.xml b/Translations/Language.hu.xml index 094eb4605b..bd4046e2bf 100644 --- a/Translations/Language.hu.xml +++ b/Translations/Language.hu.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.id.xml b/Translations/Language.id.xml index 243154900d..5abd75ef0a 100644 --- a/Translations/Language.id.xml +++ b/Translations/Language.id.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.it.xml b/Translations/Language.it.xml index 7139ac386b..52e6a64468 100644 --- a/Translations/Language.it.xml +++ b/Translations/Language.it.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.ja.xml b/Translations/Language.ja.xml index 76cb51eb42..8e0465817c 100644 --- a/Translations/Language.ja.xml +++ b/Translations/Language.ja.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.ka.xml b/Translations/Language.ka.xml index 14523317e8..0e875f1b7d 100644 --- a/Translations/Language.ka.xml +++ b/Translations/Language.ka.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.ko.xml b/Translations/Language.ko.xml index 8788313e6f..a1d02294f4 100644 --- a/Translations/Language.ko.xml +++ b/Translations/Language.ko.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.lv.xml b/Translations/Language.lv.xml index 707a9ce58a..b7aa0dd2d8 100644 --- a/Translations/Language.lv.xml +++ b/Translations/Language.lv.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.my.xml b/Translations/Language.my.xml index dd195b0b73..4c11982f03 100644 --- a/Translations/Language.my.xml +++ b/Translations/Language.my.xml @@ -1694,7 +1694,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.nb.xml b/Translations/Language.nb.xml index fcd163071d..6b29b6a82f 100644 --- a/Translations/Language.nb.xml +++ b/Translations/Language.nb.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.nl.xml b/Translations/Language.nl.xml index 1c8e4afde1..954f10fcb5 100644 --- a/Translations/Language.nl.xml +++ b/Translations/Language.nl.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.nn.xml b/Translations/Language.nn.xml index 64448aa46e..d27f374cdd 100644 --- a/Translations/Language.nn.xml +++ b/Translations/Language.nn.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.pl.xml b/Translations/Language.pl.xml index 52a19d0e03..d6cdc5c418 100644 --- a/Translations/Language.pl.xml +++ b/Translations/Language.pl.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.pt-br.xml b/Translations/Language.pt-br.xml index 5c2f01ccd0..7b1f4c4d82 100644 --- a/Translations/Language.pt-br.xml +++ b/Translations/Language.pt-br.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.ro.xml b/Translations/Language.ro.xml index befe96360a..97913147c4 100644 --- a/Translations/Language.ro.xml +++ b/Translations/Language.ro.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.ru.xml b/Translations/Language.ru.xml index b5d67caf2f..9e9a30dedd 100644 --- a/Translations/Language.ru.xml +++ b/Translations/Language.ru.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.sk.xml b/Translations/Language.sk.xml index eeac220a7b..6a80a30d71 100644 --- a/Translations/Language.sk.xml +++ b/Translations/Language.sk.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.sl.xml b/Translations/Language.sl.xml index 5333568dff..ee9c51a917 100644 --- a/Translations/Language.sl.xml +++ b/Translations/Language.sl.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.sv.xml b/Translations/Language.sv.xml index 25ef26fe04..32a318ad4e 100644 --- a/Translations/Language.sv.xml +++ b/Translations/Language.sv.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.th.xml b/Translations/Language.th.xml index 21839f07ab..d52822cf4d 100644 --- a/Translations/Language.th.xml +++ b/Translations/Language.th.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.tr.xml b/Translations/Language.tr.xml index a050ebc5ae..255cd2d051 100644 --- a/Translations/Language.tr.xml +++ b/Translations/Language.tr.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.uk.xml b/Translations/Language.uk.xml index 9f76454827..a147a2d595 100644 --- a/Translations/Language.uk.xml +++ b/Translations/Language.uk.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.uz.xml b/Translations/Language.uz.xml index 7b0fb335bd..576e79988d 100644 --- a/Translations/Language.uz.xml +++ b/Translations/Language.uz.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.vi.xml b/Translations/Language.vi.xml index 420d0897b1..32c2ce0e31 100644 --- a/Translations/Language.vi.xml +++ b/Translations/Language.vi.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.zh-cn.xml b/Translations/Language.zh-cn.xml index 7658ec9c49..9cd62075f5 100644 --- a/Translations/Language.zh-cn.xml +++ b/Translations/Language.zh-cn.xml @@ -1693,7 +1693,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.zh-hk.xml b/Translations/Language.zh-hk.xml index 72aaf20376..25d65ea757 100644 --- a/Translations/Language.zh-hk.xml +++ b/Translations/Language.zh-hk.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/Translations/Language.zh-tw.xml b/Translations/Language.zh-tw.xml index da3a72d15e..ec2e63951d 100644 --- a/Translations/Language.zh-tw.xml +++ b/Translations/Language.zh-tw.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/src/Common/Language.xml b/src/Common/Language.xml index 2c81af0d80..88a8675679 100644 --- a/src/Common/Language.xml +++ b/src/Common/Language.xml @@ -1692,7 +1692,7 @@ Warning: Secure Boot is enabled, but the Microsoft CA that signs the Windows Boot Manager copy used by VeraCrypt (bootmgfw_ms.vc) was not found in the firmware Secure Boot database (db). After successful pre-boot authentication, the handoff to Windows may fail and the computer may return to the VeraCrypt password prompt.\n\nBefore restarting this computer, do not disable or revoke Microsoft Windows Production PCA 2011 unless Windows Boot Manager has migrated to a Windows UEFI CA 2023-signed version and the firmware db contains Windows UEFI CA 2023. Apply the Windows Secure Boot certificate updates, then run VeraCrypt Repair/Reinstall if needed. Make sure you have an up-to-date VeraCrypt Rescue Disk before restarting. Outer p&assword: Operation failed while hidden volume protection was enabled.\n\nUse the OUTER volume password, PIM, KDF, and keyfile(s), if any, in the main password dialog. Use the HIDDEN volume password, PIM, KDF, and keyfile(s), if any, in Mount Options > Hidden Volume Protection.\n\nOne or more credentials may be incorrect, or the volume may be invalid or unsupported. - Use OUTER volume password, PIM, KDF, and keyfile(s) here. Use HIDDEN credentials in Mount Options > Hidden Volume Protection. + OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s). diff --git a/src/Mount/Mount.c b/src/Mount/Mount.c index b0e0416f62..09095b0779 100644 --- a/src/Mount/Mount.c +++ b/src/Mount/Mount.c @@ -3574,21 +3574,25 @@ static char *PasswordDialogTitleStringId; static void UpdatePasswordDlgPasswordLabel (HWND hwndDlg) { - SetDlgItemTextW (hwndDlg, IDT_PASSWORD, - GetString (!PasswordDialogDisableMountOptions && mountOptions.ProtectHiddenVolume ? "IDT_OUTER_VOL_PASSWORD" : "IDT_PASSWORD")); + BOOL hiddenVolumeProtection = !PasswordDialogDisableMountOptions && mountOptions.ProtectHiddenVolume; + HWND credentialsNote = GetDlgItem (hwndDlg, HIDVOL_PROT_OUTER_CREDENTIALS_NOTE); + BOOL credentialsNoteVisible = (GetWindowLongPtr (credentialsNote, GWL_STYLE) & WS_VISIBLE) != 0; - if (!PasswordDialogDisableMountOptions && mountOptions.ProtectHiddenVolume) + SetDlgItemTextW (hwndDlg, IDT_PASSWORD, GetString (hiddenVolumeProtection ? "IDT_OUTER_VOL_PASSWORD" : "IDT_PASSWORD")); + + if (hiddenVolumeProtection != credentialsNoteVisible) { - EDITBALLOONTIP ebt; - ebt.cbStruct = sizeof (EDITBALLOONTIP); - ebt.pszText = GetString ("HIDVOL_PROT_OUTER_CREDENTIALS_NOTE"); - ebt.pszTitle = GetString ("IDT_HIDDEN_VOL_PROTECTION"); - ebt.ttiIcon = TTI_INFO_LARGE; + RECT dialogRect; + RECT sizeChange = { 0, 0, 0, 23 }; + MapDialogRect (hwndDlg, &sizeChange); + GetWindowRect (hwndDlg, &dialogRect); - SendMessage (GetDlgItem (hwndDlg, IDC_PASSWORD), EM_SHOWBALLOONTIP, 0, (LPARAM) &ebt); + ShowWindow (credentialsNote, hiddenVolumeProtection ? SW_SHOW : SW_HIDE); + SetWindowPos (hwndDlg, NULL, + dialogRect.left, dialogRect.top + (hiddenVolumeProtection ? -sizeChange.bottom / 2 : sizeChange.bottom / 2), + dialogRect.right - dialogRect.left, dialogRect.bottom - dialogRect.top + (hiddenVolumeProtection ? sizeChange.bottom : -sizeChange.bottom), + SWP_NOACTIVATE | SWP_NOZORDER); } - else - SendMessage (GetDlgItem (hwndDlg, IDC_PASSWORD), EM_HIDEBALLOONTIP, 0, 0); } /* Except in response to the WM_INITDIALOG message, the dialog box procedure diff --git a/src/Mount/Mount.rc b/src/Mount/Mount.rc index 09c7501c06..cf6a1fb602 100644 --- a/src/Mount/Mount.rc +++ b/src/Mount/Mount.rc @@ -207,7 +207,7 @@ BEGIN CONTROL "",IDC_LOWER_BOX,"Static",SS_ETCHEDFRAME,2,151,372,119 END -IDD_PASSWORD_DLG DIALOGEX 0, 0, 330, 103 +IDD_PASSWORD_DLG DIALOGEX 0, 0, 330, 126 STYLE DS_SETFONT | DS_MODALFRAME | DS_3DLOOK | DS_FIXEDSYS | DS_CENTER | WS_POPUP | WS_VISIBLE | WS_CAPTION CAPTION "Enter VeraCrypt Volume Password" FONT 8, "MS Shell Dlg", 0, 0, 0x0 @@ -228,6 +228,7 @@ BEGIN RTEXT "Password:",IDT_PASSWORD,0,10,65,13 RTEXT "KDF:",IDT_KDF,0,27,65,11 RTEXT "Volume PIM:",IDT_PIM,0,46,65,8,NOT WS_VISIBLE + LTEXT "OUTER volume (this dialog): password, PIM, KDF, and keyfile(s).\nHIDDEN volume (Mount Options): password, PIM, KDF, and keyfile(s).",HIDVOL_PROT_OUTER_CREDENTIALS_NOTE,7,103,316,18 END IDD_TRAVELER_DLG DIALOGEX 0, 0, 300, 299 @@ -511,7 +512,7 @@ BEGIN IDD_PASSWORD_DLG, DIALOG BEGIN RIGHTMARGIN, 321 - BOTTOMMARGIN, 98 + BOTTOMMARGIN, 121 END IDD_TRAVELER_DLG, DIALOG diff --git a/src/Mount/Resource.h b/src/Mount/Resource.h index 444fbc42d8..bb212ba88c 100644 --- a/src/Mount/Resource.h +++ b/src/Mount/Resource.h @@ -206,6 +206,7 @@ #define IDC_DISABLE_SCREEN_PROTECTION 1181 #define IDC_PREF_TAB 1182 #define IDC_SECURE_DESKTOP_ENABLE_IME 1183 +#define HIDVOL_PROT_OUTER_CREDENTIALS_NOTE 1184 #define IDM_HELP 40001 #define IDM_ABOUT 40002 #define IDM_UNMOUNT_VOLUME 40003 @@ -284,7 +285,7 @@ #define _APS_NO_MFC 1 #define _APS_NEXT_RESOURCE_VALUE 123 #define _APS_NEXT_COMMAND_VALUE 40071 -#define _APS_NEXT_CONTROL_VALUE 1184 +#define _APS_NEXT_CONTROL_VALUE 1185 #define _APS_NEXT_SYMED_VALUE 101 #endif #endif