diff --git a/Translations/Language.ar.xml b/Translations/Language.ar.xml index 5b4f8a0f..26937c52 100644 --- a/Translations/Language.ar.xml +++ b/Translations/Language.ar.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.be.xml b/Translations/Language.be.xml index db1ef18e..33473d68 100644 --- a/Translations/Language.be.xml +++ b/Translations/Language.be.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.bg.xml b/Translations/Language.bg.xml index 7011fb4d..9a3a7e17 100644 --- a/Translations/Language.bg.xml +++ b/Translations/Language.bg.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.ca.xml b/Translations/Language.ca.xml index ab8aab11..fbc52d9d 100644 --- a/Translations/Language.ca.xml +++ b/Translations/Language.ca.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.co.xml b/Translations/Language.co.xml index ae670488..b9a578c2 100644 --- a/Translations/Language.co.xml +++ b/Translations/Language.co.xml @@ -1678,6 +1678,16 @@ Information about Corsican localization: Attivà l’editore di metoda di stampittera (IME) in u scagnu sicuru AVERTIMENTU : Attivà st’ozzione solu s’è vo scuntrate prublemi quandu si selezziuneghja schedarii chjave o gettoni in u casu d’un scagnu sicuru. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.cs.xml b/Translations/Language.cs.xml index e7e604c9..d5179600 100644 --- a/Translations/Language.cs.xml +++ b/Translations/Language.cs.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.da.xml b/Translations/Language.da.xml index 33b3e857..5f27fa80 100644 --- a/Translations/Language.da.xml +++ b/Translations/Language.da.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.de.xml b/Translations/Language.de.xml index d9a3a9bc..38329b84 100644 --- a/Translations/Language.de.xml +++ b/Translations/Language.de.xml @@ -1661,6 +1661,16 @@ Eingabemethoden-Editor (IME) im Secure Desktop verwenden WARNUNG: Verwenden Sie diese Option nur, wenn Probleme bei der Auswahl von Schlüsseldateien/Tokens unter dem Secure Desktop auftreten. Die Schlüsselableitung ist fehlgeschlagen. Dies kann durch unzureichenden Speicherplatz oder einen unterbrochenen Vorgang verursacht worden sein. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.el.xml b/Translations/Language.el.xml index 2644e95c..eac2ef20 100644 --- a/Translations/Language.el.xml +++ b/Translations/Language.el.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.es.xml b/Translations/Language.es.xml index b4d90357..a502b33f 100644 --- a/Translations/Language.es.xml +++ b/Translations/Language.es.xml @@ -1658,6 +1658,16 @@ Habilitar el editor de métodos de entrada (IME) en el Escritorio seguro ADVERTENCIA: Habilite esta opción SOLO si encuentra problemas al seleccionar archivos clave (Keyfiles) o tokens en el Escritorio seguro. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.et.xml b/Translations/Language.et.xml index 5feb47cb..e2988c82 100644 --- a/Translations/Language.et.xml +++ b/Translations/Language.et.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.eu.xml b/Translations/Language.eu.xml index a42b7498..e204fe1c 100644 --- a/Translations/Language.eu.xml +++ b/Translations/Language.eu.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.fa.xml b/Translations/Language.fa.xml index 3906e271..99cb0d97 100644 --- a/Translations/Language.fa.xml +++ b/Translations/Language.fa.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.fi.xml b/Translations/Language.fi.xml index 6973fe23..eb3f9a06 100644 --- a/Translations/Language.fi.xml +++ b/Translations/Language.fi.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.fr.xml b/Translations/Language.fr.xml index a77e5850..fa59bee6 100644 --- a/Translations/Language.fr.xml +++ b/Translations/Language.fr.xml @@ -1658,6 +1658,16 @@ Activer l'éditeur de méthode de saisie (IME) dans le bureau sécurisé AVERTISSEMENT : Activez cette option uniquement si vous rencontrez des problèmes lors de la sélection de fichiers clés/tokens dans le bureau sécurisé. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.he.xml b/Translations/Language.he.xml index 4405c54f..daa4e530 100644 --- a/Translations/Language.he.xml +++ b/Translations/Language.he.xml @@ -1659,6 +1659,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.hu.xml b/Translations/Language.hu.xml index 1d90c7aa..10d0b09a 100644 --- a/Translations/Language.hu.xml +++ b/Translations/Language.hu.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.id.xml b/Translations/Language.id.xml index 6678121c..45cba292 100644 --- a/Translations/Language.id.xml +++ b/Translations/Language.id.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.it.xml b/Translations/Language.it.xml index 42ab832f..730cc66d 100644 --- a/Translations/Language.it.xml +++ b/Translations/Language.it.xml @@ -1658,6 +1658,16 @@ Abilita l'editor del metodo di input (IME) nel Desktop sicuro ATTENZIONE: Abilita questa opzione SOLO se riscontri problemi durante la selezione di file chiave o token nel Desktop sicuro. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.ja.xml b/Translations/Language.ja.xml index e3a553fa..7eea59c5 100644 --- a/Translations/Language.ja.xml +++ b/Translations/Language.ja.xml @@ -1658,6 +1658,16 @@ セキュアデスクトップでIMEを有効にする 警告: セキュアデスクトップでキーファイルやトークンを選択する際に問題が発生する場合にのみ、このオプションを有効にしてください。 Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.ka.xml b/Translations/Language.ka.xml index b6d54c03..770931a9 100644 --- a/Translations/Language.ka.xml +++ b/Translations/Language.ka.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.ko.xml b/Translations/Language.ko.xml index 55eb1cf2..de452c3a 100644 --- a/Translations/Language.ko.xml +++ b/Translations/Language.ko.xml @@ -1658,6 +1658,16 @@ 보안 데스크톱에서 입력기(IME) 활성화하기 경고: 보안 데스크톱에서 키 파일/토큰 선택 시 문제가 발생하는 경우에만 이 옵션을 활성화하세요. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.lv.xml b/Translations/Language.lv.xml index f5518488..1009e078 100644 --- a/Translations/Language.lv.xml +++ b/Translations/Language.lv.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.my.xml b/Translations/Language.my.xml index 86fe2e95..162da9b4 100644 --- a/Translations/Language.my.xml +++ b/Translations/Language.my.xml @@ -1660,6 +1660,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.nb.xml b/Translations/Language.nb.xml index 19589a16..a27ae7b2 100644 --- a/Translations/Language.nb.xml +++ b/Translations/Language.nb.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.nl.xml b/Translations/Language.nl.xml index 6d75434f..2925fa61 100644 --- a/Translations/Language.nl.xml +++ b/Translations/Language.nl.xml @@ -1658,6 +1658,16 @@ De invoermethode-editor (IME) inschakelen in Secure Desktop WAARSCHUWING: schakel deze optie alleen in als u problemen ondervindt bij het selecteren van sleutelbestanden/tokens onder Secure Desktop. Het afleiden van de sleutel is mislukt. Dit kan worden veroorzaakt door onvoldoende geheugen of een onderbroken bewerking. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.nn.xml b/Translations/Language.nn.xml index 9441dad9..34fa9805 100644 --- a/Translations/Language.nn.xml +++ b/Translations/Language.nn.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.pl.xml b/Translations/Language.pl.xml index 2e1fe4f6..9b84182b 100644 --- a/Translations/Language.pl.xml +++ b/Translations/Language.pl.xml @@ -1658,6 +1658,16 @@ Włącz edytor metody wprowadzania (IME) na bezpiecznym pulpicie OSTRZEŻENIE: Włącz tę opcję tylko wtedy, gdy napotykasz problemy przy wybieraniu plików-kluczy/tokenów na bezpiecznym pulpicie. Nie powiodła się derywacja klucza. Przyczyną może być niewystarczająca ilość pamięci lub przerwanie operacji. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.pt-br.xml b/Translations/Language.pt-br.xml index f30f134d..1ee6d29f 100644 --- a/Translations/Language.pt-br.xml +++ b/Translations/Language.pt-br.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.ro.xml b/Translations/Language.ro.xml index 1e4bb8f2..94f6d34b 100644 --- a/Translations/Language.ro.xml +++ b/Translations/Language.ro.xml @@ -1658,6 +1658,16 @@ Activare editor metodă de intrare (IME) în Desktop securizat AVERTIZARE: Activați această opțiune doar dacă aveți probleme în a selecta token-uri/fișiere cheie când folosiți Desktop securizat. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.ru.xml b/Translations/Language.ru.xml index 925bcb62..ea6d754d 100644 --- a/Translations/Language.ru.xml +++ b/Translations/Language.ru.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.sk.xml b/Translations/Language.sk.xml index a08dc5ef..27f14087 100644 --- a/Translations/Language.sk.xml +++ b/Translations/Language.sk.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.sl.xml b/Translations/Language.sl.xml index de03f212..4e395bb9 100644 --- a/Translations/Language.sl.xml +++ b/Translations/Language.sl.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.sv.xml b/Translations/Language.sv.xml index f0e719fd..a88fa599 100644 --- a/Translations/Language.sv.xml +++ b/Translations/Language.sv.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.th.xml b/Translations/Language.th.xml index 5e73158b..fb6c7adb 100644 --- a/Translations/Language.th.xml +++ b/Translations/Language.th.xml @@ -1659,6 +1659,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.tr.xml b/Translations/Language.tr.xml index ac356a75..dc3f7f1b 100644 --- a/Translations/Language.tr.xml +++ b/Translations/Language.tr.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.uk.xml b/Translations/Language.uk.xml index 545f8136..d8bbcc40 100644 --- a/Translations/Language.uk.xml +++ b/Translations/Language.uk.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.uz.xml b/Translations/Language.uz.xml index 3b014edf..9b71a939 100644 --- a/Translations/Language.uz.xml +++ b/Translations/Language.uz.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.vi.xml b/Translations/Language.vi.xml index 4990a64d..82c93657 100644 --- a/Translations/Language.vi.xml +++ b/Translations/Language.vi.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.zh-cn.xml b/Translations/Language.zh-cn.xml index 02a3cba4..68aae450 100644 --- a/Translations/Language.zh-cn.xml +++ b/Translations/Language.zh-cn.xml @@ -1659,6 +1659,16 @@ 在安全桌面中启用输入法编辑器（IME） 警告：仅当您在安全桌面下选择密钥文件/令牌时遇到问题时，才启用此选项。 Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.zh-hk.xml b/Translations/Language.zh-hk.xml index 52ada92a..6a9c3c05 100644 --- a/Translations/Language.zh-hk.xml +++ b/Translations/Language.zh-hk.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/Translations/Language.zh-tw.xml b/Translations/Language.zh-tw.xml index 4086fada..7471a780 100644 --- a/Translations/Language.zh-tw.xml +++ b/Translations/Language.zh-tw.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/src/Common/BootEncryption.cpp b/src/Common/BootEncryption.cpp index 215b1f86..872d6206 100644 --- a/src/Common/BootEncryption.cpp +++ b/src/Common/BootEncryption.cpp @@ -2660,8 +2660,11 @@ namespace VeraCrypt return (BootOrderLen != 0) || (GetLastError() != ERROR_INVALID_FUNCTION); } - void EfiBoot::DeleteStartExec(uint16 statrtOrderNum, wchar_t* type) { + static const unsigned __int64 TC_MAX_EFI_BOOT_LOADER_FILE_SIZE = 16ULL * 1024 * 1024; + + bool EfiBoot::DeleteStartExec(uint16 statrtOrderNum, wchar_t* type) { DWORD dwLastError; + bool bRet = true; BOOL bPrivilegesSet = IsPrivilegeEnabled (SE_SYSTEM_ENVIRONMENT_NAME); if (!bPrivilegesSet && !SetPrivilege(SE_SYSTEM_ENVIRONMENT_NAME, TRUE)) { @@ -2678,11 +2681,22 @@ namespace VeraCrypt } wchar_t varName[256]; StringCchPrintfW(varName, ARRAYSIZE (varName), L"%s%04X", type == NULL ? L"Boot" : type, statrtOrderNum); - SetFirmwareEnvironmentVariable(varName, EfiVarGuid, NULL, 0); + if (!SetFirmwareEnvironmentVariable(varName, EfiVarGuid, NULL, 0)) + { + dwLastError = GetLastError(); + if (dwLastError != ERROR_ENVVAR_NOT_FOUND) + bRet = false; + } wstring order = L"Order"; order.insert(0, type == NULL ? L"Boot" : type); uint32 startOrderLen = GetFirmwareEnvironmentVariable(order.c_str(), EfiVarGuid, tempBuf, sizeof(tempBuf)); + if (startOrderLen == 0) + { + dwLastError = GetLastError(); + if (dwLastError != ERROR_ENVVAR_NOT_FOUND) + bRet = false; + } uint32 startOrderNumPos = UINT_MAX; bool startOrderUpdate = false; uint16* startOrder = (uint16*)tempBuf; @@ -2703,7 +2717,8 @@ namespace VeraCrypt } if (startOrderUpdate) { - SetFirmwareEnvironmentVariable(order.c_str(), EfiVarGuid, startOrder, startOrderLen); + if (!SetFirmwareEnvironmentVariable(order.c_str(), EfiVarGuid, startOrder, startOrderLen)) + bRet = false; // remove ourselves from BootNext value uint16 bootNextValue = 0; @@ -2714,12 +2729,19 @@ namespace VeraCrypt && (bootNextValue == statrtOrderNum) ) { - SetFirmwareEnvironmentVariable(next.c_str(), EfiVarGuid, startOrder, 0); + if (!SetFirmwareEnvironmentVariable(next.c_str(), EfiVarGuid, NULL, 0)) + { + dwLastError = GetLastError(); + if (dwLastError != ERROR_ENVVAR_NOT_FOUND) + bRet = false; + } } } if (!bPrivilegesSet) SetPrivilege(SE_SYSTEM_ENVIRONMENT_NAME, FALSE); + + return bRet; } void EfiBoot::SetStartExec(wstring description, wstring execPath, bool setBootEntry, bool forceFirstBootEntry, bool setBootNext, uint16 statrtOrderNum , wchar_t* type, uint32 attr) { @@ -3019,6 +3041,32 @@ namespace VeraCrypt return bRet; } + bool EfiBoot::FileHasPattern (const wchar_t* name, const void* pattern, size_t patternLen) + { + std::vector fileContent; + if (!ReadFileToBuffer (name, fileContent)) + return false; + + return BufferHasPattern (fileContent.data (), fileContent.size (), pattern, patternLen); + } + + bool EfiBoot::IsVeraCryptBootLoader (const wchar_t* name) + { + std::vector fileContent; + if (!ReadFileToBuffer (name, fileContent)) + return false; + + const wchar_t* appName = _T(TC_APP_NAME); + return BufferHasPattern (fileContent.data (), fileContent.size (), appName, wcslen (appName) * sizeof (wchar_t)) + || BufferHasPattern (fileContent.data (), fileContent.size (), TC_APP_NAME, strlen (TC_APP_NAME)); + } + + bool EfiBoot::IsWindowsBootLoader (const wchar_t* name) + { + const char* g_szMsBootString = "bootmgfw.pdb"; + return FileHasPattern (name, g_szMsBootString, strlen (g_szMsBootString)); + } + void EfiBoot::SaveFile(const wchar_t* name, uint8* data, DWORD size) { wstring path = EfiBootPartPath; path += name; @@ -3056,6 +3104,47 @@ namespace VeraCrypt f.Close(); } + bool EfiBoot::ReadFileToBuffer (const wchar_t* name, std::vector& fileContent) + { + fileContent.clear (); + wstring path = EfiBootPartPath; + path += name; + + File f(path, true); + if (!f.IsOpened ()) + { + f.Close (); + return false; + } + + unsigned __int64 fileSize = 0; + f.GetFileSize (fileSize); + if (fileSize == 0) + { + f.Close (); + return false; + } + + if (fileSize > TC_MAX_EFI_BOOT_LOADER_FILE_SIZE || fileSize > UINT_MAX) + { + f.Close (); + throw ErrorException (wstring (GetString ("EFI_BOOT_LOADER_FILE_TOO_LARGE")) + + L"\n" + name, SRC_POS); + } + + DWORD fileSize32 = (DWORD) fileSize; + fileContent.resize ((size_t) fileSize32); + if (f.Read (fileContent.data (), fileSize32) != fileSize32) + { + f.Close (); + throw ErrorException (wstring (GetString ("EFI_BOOT_LOADER_FILE_READ_FAILED")) + + L"\n" + name, SRC_POS); + } + + f.Close (); + return true; + } + void EfiBoot::CopyFile(const wchar_t* name, const wchar_t* targetName) { wstring path = EfiBootPartPath; path += name; @@ -4502,11 +4591,15 @@ namespace VeraCrypt EfiBootInst.PrepareBootPartition(); - EfiBootInst.DeleteStartExec(); - EfiBootInst.DeleteStartExec(0xDC5B, L"Driver"); // remove DcsBml boot driver it was installed - EfiBootInst.RenameFile(L"\\EFI\\Boot\\original_bootx64.vc_backup", L"\\EFI\\Boot\\bootx64.efi", TRUE); + const wchar_t * szStdMsBootloader = L"\\EFI\\Microsoft\\Boot\\bootmgfw.efi"; + const wchar_t * szBackupMsBootloader = L"\\EFI\\Microsoft\\Boot\\bootmgfw_ms.vc"; + // EFI system encryption currently ships x64 EFI loaders and the UEFI fallback path is bootx64.efi + const wchar_t * szStdEfiBootloader = L"\\EFI\\Boot\\bootx64.efi"; + const wchar_t * szBackupEfiBootloader = L"\\EFI\\Boot\\original_bootx64.vc_backup"; - if (!EfiBootInst.RenameFile(L"\\EFI\\Microsoft\\Boot\\bootmgfw_ms.vc", L"\\EFI\\Microsoft\\Boot\\bootmgfw.efi", TRUE)) + EfiBootInst.RenameFile(szBackupEfiBootloader, szStdEfiBootloader, TRUE); + + if (!EfiBootInst.RenameFile(szBackupMsBootloader, szStdMsBootloader, TRUE)) { EfiBootConf conf; if (EfiBootInst.ReadConfig (L"\\EFI\\VeraCrypt\\DcsProp", conf) && strlen (conf.actionSuccessValue.c_str())) @@ -4515,8 +4608,9 @@ namespace VeraCrypt if (EfiBootConf::IsPostExecFileField (conf.actionSuccessValue, loaderPath)) { // check that it is not bootmgfw_ms.vc or bootmgfw.efi - if ( (0 != _wcsicmp (loaderPath.c_str(), L"\\EFI\\Microsoft\\Boot\\bootmgfw_ms.vc")) - && (0 != _wcsicmp (loaderPath.c_str(), L"\\EFI\\Microsoft\\Boot\\bootmgfw.efi")) + if ( (0 != _wcsicmp (loaderPath.c_str(), szBackupMsBootloader)) + && (0 != _wcsicmp (loaderPath.c_str(), szStdMsBootloader)) + && EfiBootInst.FileExists (loaderPath.c_str()) ) { const char* g_szMsBootString = "bootmgfw.pdb"; @@ -4529,13 +4623,48 @@ namespace VeraCrypt // look for bootmgfw.efi identifiant string if (BufferHasPattern (bootLoaderBuf.data (), (size_t) loaderSize, g_szMsBootString, strlen (g_szMsBootString))) { - EfiBootInst.RenameFile(loaderPath.c_str(), L"\\EFI\\Microsoft\\Boot\\bootmgfw.efi", TRUE); + EfiBootInst.RenameFile(loaderPath.c_str(), szStdMsBootloader, TRUE); } } } } } + bool bMsBootloaderRestored = EfiBootInst.FileExists (szStdMsBootloader) && EfiBootInst.IsWindowsBootLoader (szStdMsBootloader); + if (!bMsBootloaderRestored + && EfiBootInst.FileExists (szStdEfiBootloader) + && EfiBootInst.IsWindowsBootLoader (szStdEfiBootloader)) + { + EfiBootInst.CopyFile (szStdEfiBootloader, szStdMsBootloader); + bMsBootloaderRestored = EfiBootInst.FileExists (szStdMsBootloader) && EfiBootInst.IsWindowsBootLoader (szStdMsBootloader); + } + + if (!bMsBootloaderRestored) + { + throw ErrorException (wstring (GetString ("SYS_LOADER_RESTORE_FAILED")) + + L"\n\n" + GetString ("EFI_MS_BOOT_LOADER_RESTORE_FAILED") + L"\n" + + szStdMsBootloader, SRC_POS); + } + + if (EfiBootInst.FileExists (szStdEfiBootloader) && EfiBootInst.IsVeraCryptBootLoader (szStdEfiBootloader)) + { + EfiBootInst.CopyFile (szStdMsBootloader, szStdEfiBootloader); + if (EfiBootInst.IsVeraCryptBootLoader (szStdEfiBootloader) || !EfiBootInst.IsWindowsBootLoader (szStdEfiBootloader)) + { + throw ErrorException (wstring (GetString ("SYS_LOADER_RESTORE_FAILED")) + + L"\n\n" + GetString ("EFI_FALLBACK_BOOT_LOADER_STILL_VERACRYPT") + L"\n" + + szStdEfiBootloader, SRC_POS); + } + } + + bool bBootEntryRemoved = EfiBootInst.DeleteStartExec(); + bool bBmlDriverEntryRemoved = EfiBootInst.DeleteStartExec(0xDC5B, L"Driver"); // remove DcsBml boot driver if it was installed + if (!bBootEntryRemoved || !bBmlDriverEntryRemoved) + { + // Keep VeraCrypt EFI files in place if firmware entries may still point to them. + throw ErrorException (wstring (GetString ("SYS_LOADER_RESTORE_FAILED")) + + L"\n\n" + GetString ("EFI_BOOT_LOADER_NVRAM_CLEANUP_FAILED"), SRC_POS); + } EfiBootInst.DelFile(L"\\DcsBoot.efi"); EfiBootInst.DelFile(L"\\DcsInt.efi"); @@ -5311,6 +5440,14 @@ namespace VeraCrypt RestoreSystemLoader (); } + catch (ErrorException &e) + { + if (!e.ErrMsg.empty()) + throw; + + e.Show (ParentWindow); + throw ErrorException ("SYS_LOADER_RESTORE_FAILED", SRC_POS); + } catch (Exception &e) { e.Show (ParentWindow); diff --git a/src/Common/BootEncryption.h b/src/Common/BootEncryption.h index b868f80c..543316aa 100644 --- a/src/Common/BootEncryption.h +++ b/src/Common/BootEncryption.h @@ -198,15 +198,19 @@ namespace VeraCrypt void PrepareBootPartition(bool bDisableException = false); bool IsEfiBoot(); - void DeleteStartExec(uint16 statrtOrderNum = 0xDC5B, wchar_t* type = NULL); + bool DeleteStartExec(uint16 statrtOrderNum = 0xDC5B, wchar_t* type = NULL); void SetStartExec(wstring description, wstring execPath, bool setBootEntry = true, bool forceFirstBootEntry = true, bool setBootNext = true, uint16 statrtOrderNum = 0xDC5B, wchar_t* type = NULL, uint32 attr = 1); void SaveFile(const wchar_t* name, uint8* data, DWORD size); void GetFileSize(const wchar_t* name, unsigned __int64& size); void ReadFile(const wchar_t* name, uint8* data, DWORD size); + bool ReadFileToBuffer (const wchar_t* name, std::vector& fileContent); void CopyFile(const wchar_t* name, const wchar_t* targetName); bool FileExists(const wchar_t* name); static bool CompareFiles (const wchar_t* fileName1, const wchar_t* fileName2); static bool CompareFileData (const wchar_t* fileName, const uint8* data, DWORD size); + bool FileHasPattern (const wchar_t* name, const void* pattern, size_t patternLen); + bool IsVeraCryptBootLoader (const wchar_t* name); + bool IsWindowsBootLoader (const wchar_t* name); BOOL RenameFile(const wchar_t* name, const wchar_t* nameNew, BOOL bForce); BOOL DelFile(const wchar_t* name); diff --git a/src/Common/Language.xml b/src/Common/Language.xml index cf9d0078..2ec36d0b 100644 --- a/src/Common/Language.xml +++ b/src/Common/Language.xml @@ -1658,6 +1658,16 @@ Enable Input Method Editor (IME) in Secure Desktop WARNING: Enable this option only if you are encountering issues when selecting Keyfiles/Tokens under Secure Desktop. Key derivation failed. This may be caused by insufficient memory or an interrupted operation. + The system partition/drive is already decrypted, but the EFI Microsoft boot loader path was not restored to the Windows Boot Manager. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + The system partition/drive is already decrypted, but the EFI fallback boot loader path still contains the VeraCrypt Boot Loader. Only the EFI boot files need repair. Use the VeraCrypt Rescue Disk repair option, or boot Windows recovery media and run 'bcdboot W:\\Windows /s S: /f UEFI' after replacing W: with the Windows volume drive letter and S: with the EFI System Partition drive letter. Path: + Repair EFI Boot Loader... + VeraCrypt will restore the Windows EFI boot loader paths and remove VeraCrypt EFI boot entries and files.\n\nUse this only after the system partition/drive is fully decrypted and Windows can boot without system encryption.\n\nDo you want to continue? + The EFI boot loader file could not be read completely: + The EFI boot loader file is unexpectedly large and was not inspected: + The system partition/drive is already decrypted and the EFI boot loader files were restored, but VeraCrypt could not remove one or more VeraCrypt firmware boot entries. The VeraCrypt EFI files were left in place so any remaining firmware entry still points to an existing loader. Retry as Administrator or remove the VeraCrypt boot entry from firmware setup after confirming Windows Boot Manager starts normally. + The EFI boot loader cannot be repaired while system encryption or decryption is active or incomplete. If decryption has just completed, reboot Windows and try again. + This repair action is available only on systems booting in UEFI mode from a GPT system partition. + The EFI boot loader has been repaired successfully. diff --git a/src/Format/Tcformat.c b/src/Format/Tcformat.c index c4bc71b8..1d8055ad 100644 --- a/src/Format/Tcformat.c +++ b/src/Format/Tcformat.c @@ -6677,6 +6677,7 @@ BOOL CALLBACK MainDialogProc (HWND hwndDlg, UINT uMsg, WPARAM wParam, LPARAM lPa catch (Exception &e) { e.Show (hwndDlg); + return 1; } ManageStartupSeqWiz (TRUE, L""); @@ -10782,4 +10783,4 @@ int WINAPI wWinMain (HINSTANCE hInstance, HINSTANCE hPrevInstance, wchar_t *lpsz return 0; } -#endif \ No newline at end of file +#endif diff --git a/src/Mount/Mount.c b/src/Mount/Mount.c index 2e882685..a9d2d054 100644 --- a/src/Mount/Mount.c +++ b/src/Mount/Mount.c @@ -663,6 +663,10 @@ static void InitMainDialog (HWND hwndDlg) { EnableMenuItem (GetMenu (hwndDlg), IDM_CREATE_HIDDEN_OS, MF_GRAYED); } + else + { + EnableMenuItem (GetMenu (hwndDlg), IDM_REPAIR_EFI_BOOT_LOADER, MF_GRAYED); + } } // Disable menu item for changing system header key derivation algorithm until it's implemented @@ -1464,10 +1468,12 @@ unsigned __int64 GetSysEncDeviceEncryptedPartSize (BOOL bSilent) static void PopulateSysEncContextMenu (HMENU popup, BOOL bToolsOnly) { SystemDriveConfiguration config; + BOOL bRepairEfiBootLoaderApplicable = FALSE; try { BootEncStatus = BootEncObj->GetStatus(); config = BootEncObj->GetSystemDriveConfiguration(); + bRepairEfiBootLoaderApplicable = config.SystemPartition.IsGPT; } catch (Exception &e) { @@ -1501,6 +1507,8 @@ static void PopulateSysEncContextMenu (HMENU popup, BOOL bToolsOnly) AppendMenuW (popup, MF_STRING, IDM_CREATE_RESCUE_DISK, GetString ("IDM_CREATE_RESCUE_DISK")); AppendMenuW (popup, MF_STRING, IDM_VERIFY_RESCUE_DISK, GetString ("IDM_VERIFY_RESCUE_DISK")); AppendMenuW (popup, MF_STRING, IDM_VERIFY_RESCUE_DISK_ISO, GetString ("IDM_VERIFY_RESCUE_DISK_ISO")); + if (bRepairEfiBootLoaderApplicable) + AppendMenuW (popup, MF_STRING, IDM_REPAIR_EFI_BOOT_LOADER, GetString ("IDM_REPAIR_EFI_BOOT_LOADER")); } if (!bToolsOnly) @@ -6454,6 +6462,63 @@ static void DecryptSystemDevice (HWND hwndDlg) Warning ("SYSTEM_ENCRYPTION_IN_PROGRESS_ELSEWHERE", hwndDlg); } +static void RepairEfiBootLoader (HWND hwndDlg) +{ + SystemDriveConfiguration config; + try + { + BootEncStatus = BootEncObj->GetStatus(); + config = BootEncObj->GetSystemDriveConfiguration (); + } + catch (Exception &e) + { + e.Show (hwndDlg); + return; + } + + if (!config.SystemPartition.IsGPT) + { + Warning ("EFI_BOOT_LOADER_REPAIR_NOT_APPLICABLE", hwndDlg); + return; + } + + if (IsHiddenOSRunning() + || BootEncStatus.SetupInProgress + || BootEncStatus.DriveEncrypted + || BootEncStatus.DriveMounted + || SysEncryptionOrDecryptionRequired ()) + { + Warning ("EFI_BOOT_LOADER_REPAIR_BLOCKED", hwndDlg); + return; + } + + if (AskWarnNoYes ("CONFIRM_REPAIR_EFI_BOOT_LOADER", hwndDlg) == IDNO) + return; + + if (!CreateSysEncMutex ()) + { + Warning ("SYSTEM_ENCRYPTION_IN_PROGRESS_ELSEWHERE", hwndDlg); + return; + } + + WaitCursor (); + try + { + BootEncObj->RestoreSystemLoader (); + } + catch (Exception &e) + { + NormalCursor (); + CloseSysEncMutex (); + e.Show (hwndDlg); + return; + } + + NormalCursor (); + CloseSysEncMutex (); + Info ("EFI_BOOT_LOADER_REPAIR_SUCCESS", hwndDlg); +} + // Initiates the process of creation of a hidden operating system static void CreateHiddenOS (HWND hwndDlg) { @@ -8519,6 +8584,9 @@ BOOL CALLBACK MainDialogProc (HWND hwndDlg, UINT uMsg, WPARAM wParam, LPARAM lPa case IDM_VERIFY_RESCUE_DISK_ISO: VerifyRescueDisk (hwndDlg, true); break; + case IDM_REPAIR_EFI_BOOT_LOADER: + RepairEfiBootLoader (hwndDlg); + break; case IDM_MOUNT_SYSENC_PART_WITHOUT_PBA: if (CheckSysEncMountWithoutPBA (hwndDlg, L"", FALSE)) diff --git a/src/Mount/Mount.rc b/src/Mount/Mount.rc index 927ae937..fcef7693 100644 --- a/src/Mount/Mount.rc +++ b/src/Mount/Mount.rc @@ -699,6 +699,7 @@ BEGIN MENUITEM "Create Rescue Disk...", IDM_CREATE_RESCUE_DISK MENUITEM "Verify Rescue Disk", IDM_VERIFY_RESCUE_DISK MENUITEM "Verify Rescue Disk Image", IDM_VERIFY_RESCUE_DISK_ISO + MENUITEM "Repair EFI Boot Loader...", IDM_REPAIR_EFI_BOOT_LOADER MENUITEM SEPARATOR MENUITEM "Mount Without Pre-Boot &Authentication...", IDM_MOUNT_SYSENC_PART_WITHOUT_PBA MENUITEM SEPARATOR diff --git a/src/Mount/Resource.h b/src/Mount/Resource.h index 0f2ce5b3..444fbc42 100644 --- a/src/Mount/Resource.h +++ b/src/Mount/Resource.h @@ -275,6 +275,7 @@ #define IDM_DECRYPT_NONSYS_VOL 40067 #define IDM_VERIFY_RESCUE_DISK_ISO 40068 #define IDM_MOUNIT_NO_CACHE 40069 +#define IDM_REPAIR_EFI_BOOT_LOADER 40070 // Next default values for new objects // @@ -282,7 +283,7 @@ #ifndef APSTUDIO_READONLY_SYMBOLS #define _APS_NO_MFC 1 #define _APS_NEXT_RESOURCE_VALUE 123 -#define _APS_NEXT_COMMAND_VALUE 40070 +#define _APS_NEXT_COMMAND_VALUE 40071 #define _APS_NEXT_CONTROL_VALUE 1184 #define _APS_NEXT_SYMED_VALUE 101 #endif