From 4f0d1c02bdf4adf56caf48de967c41d2d4d9ff2d Mon Sep 17 00:00:00 2001
From: Mounir IDRASSI <mounir.idrassi@idrix.fr>
Date: Mon, 23 Apr 2018 12:56:02 +0200
Subject: Windows: Don't start EFI system encryption process if SecureBoot is
 enabled and VeraCrypt-DCS custom keys were not loaded in the machine
 firmware.

---
 src/Common/Language.xml | 1 +
 1 file changed, 1 insertion(+)

(limited to 'src/Common/Language.xml')

diff --git a/src/Common/Language.xml b/src/Common/Language.xml
index 0562ee37..8c1b3ca5 100644
--- a/src/Common/Language.xml
+++ b/src/Common/Language.xml
@@ -1420,6 +1420,7 @@
     <entry lang="en" key="IDC_ALLOW_TRIM_NONSYS_SSD">Allow TRIM command for non-system SSD partition/drive</entry>
     <entry lang="en" key="IDC_BLOCK_SYSENC_TRIM">Block TRIM command on system partition/drive</entry>
     <entry lang="en" key="WINDOWS_EFI_BOOT_LOADER_MISSING">ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted.</entry>
+    <entry lang="en" key="SYSENC_EFI_UNSUPPORTED_SECUREBOOT">It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed.</entry>
   </localization>
   <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="VeraCrypt">
-- 
cgit v1.2.3