fveapi.dll.mui Windows BitLocker Drive Encryption API 7141328c73733c4fa41f26800805b9de

File name:	fveapi.dll.mui
Size:	32256 byte
MD5:	7141328c73733c4fa41f26800805b9de
SHA1:	ae3bc245a6e7a2875536640fcd3a5925710dfd00
SHA256:	1ae4835bc66062219c3589fefbf781fe2fcc5bd33e0a6794e00f9a9357d413a6
Operating systems:	Windows 10
Extension:	MUI

If an error occurred or the following message in English (U.S.) language and you cannot find a solution, than check answer in English. Table below helps to know how correctly this phrase sounds in English.

id	English (U.S.)	English
1001	%1 %2 %3	%1 %2 %3
0x201	BitLocker Drive Encryption recovery information was backed up successfully to Active Directory Domain Services.%nProtector GUID: %1%nVolume GUID: %2	BitLocker Drive Encryption recovery information was backed up successfully to Active Directory Domain Services.%nProtector GUID: %1%nVolume GUID: %2
0x202	Failed to backup BitLocker Drive Encryption recovery information to Active Directory Domain Services.%nErrorcode: %2%nProtector GUID: %1%nVolume GUID: %3	Failed to backup BitLocker Drive Encryption recovery information to Active Directory Domain Services.%nErrorcode: %2%nProtector GUID: %1%nVolume GUID: %3
0x203	BitLocker Drive Encryption recovery information for the specified protector is already present in Active Directory Domain Services.%nProtector GUID: %1%nVolume GUID: %2	BitLocker Drive Encryption recovery information for the specified protector is already present in Active Directory Domain Services.%nProtector GUID: %1%nVolume GUID: %2
0x204	A BitLocker certificate data recovery agent was created, because it was missing on the volume or added to the list of data recovery agents.%nCertificate thumbprint: %2%nProtector GUID: %1%nVolume GUID: %3	A BitLocker certificate data recovery agent was created, because it was missing on the volume or added to the list of data recovery agents.%nCertificate thumbprint: %2%nProtector GUID: %1%nVolume GUID: %3
0x205	A BitLocker certificate data recovery agent was removed, because is no longer in the list of data recovery agents.%nCertificate thumbprint: %2%nProtector GUID: %1%nVolume GUID: %3	A BitLocker certificate data recovery agent was removed, because is no longer in the list of data recovery agents.%nCertificate thumbprint: %2%nProtector GUID: %1%nVolume GUID: %3
0x206	The attempt to create a data recovery agent protector on the BitLocker volume failed.%nErrorcode: %1%nCertificate thumbprint: %2%nVolume GUID: %3	The attempt to create a data recovery agent protector on the BitLocker volume failed.%nErrorcode: %1%nCertificate thumbprint: %2%nVolume GUID: %3
0x207	The servicing of the data recovery agents on the volume failed.%nErrorcode: %1%nVolume GUID: %2	The servicing of the data recovery agents on the volume failed.%nErrorcode: %1%nVolume GUID: %2
0x208	The management of the data recovery agents failed on this drive because this feature of BitLocker Drive Encryption is not supported in this edition of the Windows operating system. %nErrorcode: %1%nVolume GUID: %2	The management of the data recovery agents failed on this drive because this feature of BitLocker Drive Encryption is not supported in this edition of the Windows operating system. %nErrorcode: %1%nVolume GUID: %2
0x209	Bootmgr failed to obtain the BitLocker volume master key from the TPM because the PCRs did not match.	Bootmgr failed to obtain the BitLocker volume master key from the TPM because the PCRs did not match.
0x20A	Bootmgr determined that the following boot application has changed: %1	Bootmgr determined that the following boot application has changed: %1
0x20B	Bootmgr determined that the boot configuration data setting %1 has changed for the following boot application: %2	Bootmgr determined that the boot configuration data setting %1 has changed for the following boot application: %2
0x20C	Bootmgr determined that the authorization data for the SRK of the TPM is incompatible with BitLocker.	Bootmgr determined that the authorization data for the SRK of the TPM is incompatible with BitLocker.
0x20D	Bootmgr determined that the TPM is disabled.	Bootmgr determined that the TPM is disabled.
0x20E	Bootmgr determined that the TPM is not accessible.	Bootmgr determined that the TPM is not accessible.
0x20F	The partition size specified in the partition table is smaller than the size of the file system contained by that partition. BitLocker TPM based keys cannot be used until the size of the partition calculated from the partition table is consistent with the size of the file system calculated from the bytes per sector and number of sectors fields in the boot sector.	The partition size specified in the partition table is smaller than the size of the file system contained by that partition. BitLocker TPM based keys cannot be used until the size of the partition calculated from the partition table is consistent with the size of the file system calculated from the bytes per sector and number of sectors fields in the boot sector.
0x210	Boot debugging is enabled on Bootmgr so TPM based keys cannot be obtained.	Boot debugging is enabled on Bootmgr so TPM based keys cannot be obtained.
0x211	Bootmgr determined that driver signature enforcement has been disabled.	Bootmgr determined that driver signature enforcement has been disabled.
0x212	Bootmgr determined that the device was locked out due to too many failed password attempts.	Bootmgr determined that the device was locked out due to too many failed password attempts.
0x213	Bootmgr determined that the device was locked out due to Device Lockout state validation failure.	Bootmgr determined that the device was locked out due to Device Lockout state validation failure.
0x337	Bootmgr failed to obtain the BitLocker volume master key from the TPM because Secure Boot was disabled.	Bootmgr failed to obtain the BitLocker volume master key from the TPM because Secure Boot was disabled.
0x338	Bootmgr failed to obtain the BitLocker volume master key from the TPM because Secure Boot configuration changed unexpectedly.	Bootmgr failed to obtain the BitLocker volume master key from the TPM because Secure Boot configuration changed unexpectedly.
0x30000001	Start	Start
0x30000002	Stop	Stop
0x50000002	Error	Error
0x50000003	Warning	Warning
0x50000004	Information	Information
0x70000064	BitLocker PIN Modification Task	BitLocker PIN Modification Task
0x70000065	BitLocker Password Modification Task	BitLocker Password Modification Task
0x90000001	Microsoft-Windows-BitLocker-API	Microsoft-Windows-BitLocker-API
0x90000002	System	System
0x90000003	Management	Management
0x90000004	Operational	Operational
0xB0000300	BitLocker encryption was started for volume %3.	BitLocker encryption was started for volume %3.
0xB0000301	BitLocker encryption will occur for volume %3 when the computer is restarted.	BitLocker encryption will occur for volume %3 when the computer is restarted.
0xB0000302	BitLocker decryption was started for volume %3.	BitLocker decryption was started for volume %3.
0xB0000303	BitLocker encryption was stopped for volume %3.	BitLocker encryption was stopped for volume %3.
0xB0000304	BitLocker encryption was restarted for volume %3.	BitLocker encryption was restarted for volume %3.
0xB0000305	BitLocker was suspended for volume %3.	BitLocker was suspended for volume %3.
0xB0000306	BitLocker was resumed for volume %3.	BitLocker was resumed for volume %3.
0xB0000307	A BitLocker key protector was created.%nProtector GUID: %4%nIdentification GUID: %1	A BitLocker key protector was created.%nProtector GUID: %4%nIdentification GUID: %1
0xB0000308	A BitLocker key protector was removed.%nProtector GUID: %4%nIdentification GUID: %1	A BitLocker key protector was removed.%nProtector GUID: %4%nIdentification GUID: %1
0xB0000309	The PIN was updated for the operating system volume.%nProtector GUID: %4%nIdentification GUID: %1	The PIN was updated for the operating system volume.%nProtector GUID: %4%nIdentification GUID: %1
0xB000030A	The BitLocker volume %3 was reverted to an unprotected state.	The BitLocker volume %3 was reverted to an unprotected state.
0xB000030B	The BitLocker volume %3 was erased.	The BitLocker volume %3 was erased.
0xB000030C	The identification field was changed. %nIdentification GUID: %1	The identification field was changed. %nIdentification GUID: %1
0xB000030D	The BitLocker protected volume %3 was locked. %nIdentification GUID: %1	The BitLocker protected volume %3 was locked. %nIdentification GUID: %1
0xB000030E	The BitLocker protected volume %3 was unlocked.%nProtector GUID: %4%nIdentification GUID: %1	The BitLocker protected volume %3 was unlocked.%nProtector GUID: %4%nIdentification GUID: %1
0xB000030F	BitLocker Drive Encryption recovery information for the specified protector is already present in Active Directory Domain Services.%nProtector GUID: %4%nIdentification GUID: %1	BitLocker Drive Encryption recovery information for the specified protector is already present in Active Directory Domain Services.%nProtector GUID: %4%nIdentification GUID: %1
0xB0000310	BitLocker Drive Encryption recovery information was backed up successfully to Active Directory Domain Services.%nProtector GUID: %4%nIdentification GUID: %1	BitLocker Drive Encryption recovery information was backed up successfully to Active Directory Domain Services.%nProtector GUID: %4%nIdentification GUID: %1
0xB0000311	Failed to backup BitLocker Drive Encryption recovery information to Active Directory Domain Services.%nProtector GUID: %4%nIdentification GUID: %1	Failed to backup BitLocker Drive Encryption recovery information to Active Directory Domain Services.%nProtector GUID: %4%nIdentification GUID: %1
0xB0000312	BitLocker free space wiping was started for volume %3.	BitLocker free space wiping was started for volume %3.
0xB0000313	BitLocker free space wiping was stopped for volume %3.	BitLocker free space wiping was stopped for volume %3.
0xB0000314	BitLocker free space wiping was restarted for volume %3.	BitLocker free space wiping was restarted for volume %3.
0xB0000315	The PIN was changed.	The PIN was changed.
0xB0000316	A PIN change attempt failed.%nError message: %1	A PIN change attempt failed.%nError message: %1
0xB0000317	The BitLocker Service (BdeSvc) PIN and password change facility is locked out due to too many failed PIN or password change attempts.	The BitLocker Service (BdeSvc) PIN and password change facility is locked out due to too many failed PIN or password change attempts.
0xB0000318	BitLocker encountered a failure to commit metadata changes for volume %3.	BitLocker encountered a failure to commit metadata changes for volume %3.
0xB0000319	BitLocker resealed boot settings to the TPM for volume %3.	BitLocker resealed boot settings to the TPM for volume %3.
0xB000031A	BitLocker failed to reseal boot settings to the TPM.%nError message: %1.	BitLocker failed to reseal boot settings to the TPM.%nError message: %1.
0xB000031B	BitLocker failed to initialize hardware encryption for volume %3 due to group policy.	BitLocker failed to initialize hardware encryption for volume %3 due to group policy.
0xB000031C	BitLocker Drive Encryption is using software-based encryption to protect volume %3.	BitLocker Drive Encryption is using software-based encryption to protect volume %3.
0xB000031D	Group Policy settings prevented BitLocker Drive Encryption from reverting to BitLocker software-based encryption. Volume %3 is not protected by BitLocker.	Group Policy settings prevented BitLocker Drive Encryption from reverting to BitLocker software-based encryption. Volume %3 is not protected by BitLocker.
0xB000031E	BitLocker failed to initialize hardware encryption for volume %3.%nDrive is not provisioned for use with BitLocker hardware encryption:%nHardware-based encryption is not activated on this drive.	BitLocker failed to initialize hardware encryption for volume %3.%nDrive is not provisioned for use with BitLocker hardware encryption:%nHardware-based encryption is not activated on this drive.
0xB000031F	BitLocker failed to initialize hardware encryption for volume %3.%nDrive is not provisioned for use with BitLocker hardware encryption:%nThe hardware-based encryption of this drive does not allow BitLocker to cryptographically protect the drive's media encryption key.	BitLocker failed to initialize hardware encryption for volume %3.%nDrive is not provisioned for use with BitLocker hardware encryption:%nThe hardware-based encryption of this drive does not allow BitLocker to cryptographically protect the drive's media encryption key.
0xB0000320	BitLocker failed to initialize hardware encryption for volume %3.%nDrive is not provisioned for use with BitLocker hardware encryption:%nHardware-based encryption is either not configured or has been configured improperly on this volume.	BitLocker failed to initialize hardware encryption for volume %3.%nDrive is not provisioned for use with BitLocker hardware encryption:%nHardware-based encryption is either not configured or has been configured improperly on this volume.
0xB0000321	BitLocker failed to initialize hardware encryption for volume %3.%nDrive is not provisioned for use with BitLocker hardware encryption:%nHardware-based encryption cannot be used with this drive because the hardware encryption method used by this drive does not comply with the Group Policy requirement for drive encryption.	BitLocker failed to initialize hardware encryption for volume %3.%nDrive is not provisioned for use with BitLocker hardware encryption:%nHardware-based encryption cannot be used with this drive because the hardware encryption method used by this drive does not comply with the Group Policy requirement for drive encryption.
0xB0000322	BitLocker failed to initialize hardware encryption for volume %3.%nDrive is not provisioned for use with BitLocker hardware encryption:%nThe key length, %5 bits, required to enable hardware-based encryption is below the minimum key length supported by the drive: %4.	BitLocker failed to initialize hardware encryption for volume %3.%nDrive is not provisioned for use with BitLocker hardware encryption:%nThe key length, %5 bits, required to enable hardware-based encryption is below the minimum key length supported by the drive: %4.
0xB0000323	BitLocker failed to initialize hardware encryption for volume %3.%nDrive is not provisioned for use with BitLocker hardware encryption:%nThe key length, %5 bits, required to enable hardware-based encryption is above the maximum key length supported by the drive: %4.	BitLocker failed to initialize hardware encryption for volume %3.%nDrive is not provisioned for use with BitLocker hardware encryption:%nThe key length, %5 bits, required to enable hardware-based encryption is above the maximum key length supported by the drive: %4.
0xB0000324	The target drive (%3) cannot be managed by BitLocker because the drive's hardware encryption feature is already in use.	The target drive (%3) cannot be managed by BitLocker because the drive's hardware encryption feature is already in use.
0xB0000325	The BitLocker protected volume was unlocked in the Windows Recovery Environment.%nProtector GUID: %2%nIdentification GUID: %1%nUnlock time: %4	The BitLocker protected volume was unlocked in the Windows Recovery Environment.%nProtector GUID: %2%nIdentification GUID: %1%nUnlock time: %4
0xB0000326	BitLocker resealed boot settings to the TPM in the Windows Recovery Environment.%nReseal time: %2	BitLocker resealed boot settings to the TPM in the Windows Recovery Environment.%nReseal time: %2
0xB0000327	BitLocker free space wiping was canceled for volume %3.	BitLocker free space wiping was canceled for volume %3.
0xB0000328	BitLocker failed to initialize hardware encryption for volume %3.%nDrive is not provisioned for use with BitLocker hardware encryption:%nSID authority is not disabled on this drive.	BitLocker failed to initialize hardware encryption for volume %3.%nDrive is not provisioned for use with BitLocker hardware encryption:%nSID authority is not disabled on this drive.
0xB0000329	BitLocker cannot use Secure Boot for integrity because it is disabled in Group Policy.	BitLocker cannot use Secure Boot for integrity because it is disabled in Group Policy.
0xB000032A	BitLocker cannot use Secure Boot for integrity because it is disabled.	BitLocker cannot use Secure Boot for integrity because it is disabled.
0xB000032B	BitLocker cannot use Secure Boot for integrity because the required UEFI variable '%1' is not present.	BitLocker cannot use Secure Boot for integrity because the required UEFI variable '%1' is not present.
0xB000032C	BitLocker cannot use Secure Boot for integrity because the UEFI variable '%1' could not be read.%n%nError Message: %2	BitLocker cannot use Secure Boot for integrity because the UEFI variable '%1' could not be read.%n%nError Message: %2
0xB000032D	BitLocker cannot use Secure Boot for integrity because the expected TCG Log entry for variable '%1' is missing or invalid.	BitLocker cannot use Secure Boot for integrity because the expected TCG Log entry for variable '%1' is missing or invalid.
0xB000032E	BitLocker cannot use Secure Boot for integrity because the expected TCG Log entry for the OS Loader Authority is missing or invalid.	BitLocker cannot use Secure Boot for integrity because the expected TCG Log entry for the OS Loader Authority is missing or invalid.
0xB000032F	BitLocker cannot use Secure Boot for integrity because the expected TCG Log separator entry is missing or invalid.	BitLocker cannot use Secure Boot for integrity because the expected TCG Log separator entry is missing or invalid.
0xB0000330	BitLocker cannot use Secure Boot for integrity because the TCG Log for PCR [7] contains invalid entries.	BitLocker cannot use Secure Boot for integrity because the TCG Log for PCR [7] contains invalid entries.
0xB0000331	BitLocker successfully sealed a key to the TPM.%n%nPCRs measured include [%1].%n%nThe source for these PCRs was: %2.	BitLocker successfully sealed a key to the TPM.%n%nPCRs measured include [%1].%n%nThe source for these PCRs was: %2.
0xB0000332	BitLocker encountered a failure attempting to configure network unlock for volume %3.	BitLocker encountered a failure attempting to configure network unlock for volume %3.
0xB0000333	The BitLocker service could not resume protection on the OS volume %3, due to the following error: Bootable media in the drive.	The BitLocker service could not resume protection on the OS volume %3, due to the following error: Bootable media in the drive.
0xB0000334	The BitLocker service could not resume protection on the OS volume %3, due to the following error: TPM is locked out.	The BitLocker service could not resume protection on the OS volume %3, due to the following error: TPM is locked out.
0xB0000335	The BitLocker service could not resume protection on the OS volume %3, due to the following error: Group policy conflict.	The BitLocker service could not resume protection on the OS volume %3, due to the following error: Group policy conflict.
0xB0000336	The BitLocker service could not resume protection on the OS volume %3, due to the following error code: %4.	The BitLocker service could not resume protection on the OS volume %3, due to the following error code: %4.
0xB0000339	BitLocker failed to initialize hardware encryption for volume %3.%nThis PC's firmware is not capable of supporting hardware encryption.	BitLocker failed to initialize hardware encryption for volume %3.%nThis PC's firmware is not capable of supporting hardware encryption.
0xB000033A	The password was changed.	The password was changed.
0xB000033B	A password change attempt failed.%nError message: %1	A password change attempt failed.%nError message: %1
0xB000033C	BitLocker Drive Encryption recovery information for volume %3 was backed up successfully to your Microsoft account.%nProtector GUID: %4	BitLocker Drive Encryption recovery information for volume %3 was backed up successfully to your Microsoft account.%nProtector GUID: %4
0xB000033D	Failed to backup BitLocker Drive Encryption recovery information for volume %3 to your Microsoft account.%n%nError: %4	Failed to backup BitLocker Drive Encryption recovery information for volume %3 to your Microsoft account.%n%nError: %4
0xB000033E	The BitLocker Drive Encryption recovery information already exists in your Microsoft account.	The BitLocker Drive Encryption recovery information already exists in your Microsoft account.
0xB000033F	Failed to save BitLocker Drive Encryption recovery information to your Microsoft account due to an error.%n%nError Code: %1%nLocalized Error Message: %2	Failed to save BitLocker Drive Encryption recovery information to your Microsoft account due to an error.%n%nError Code: %1%nLocalized Error Message: %2
0xB0000340	TCG Log parsing failure.%n%nError: %1.	TCG Log parsing failure.%n%nError: %1.
0xB0000341	BitLocker detected that custom Secure Boot policy is installed, and will seal to this configuration. Sealing to a custom policy may reduce the integrity provided by Secure Boot.	BitLocker detected that custom Secure Boot policy is installed, and will seal to this configuration. Sealing to a custom policy may reduce the integrity provided by Secure Boot.
0xB0000342	BitLocker determined that the TCG log is invalid for use of Secure Boot. The filtered TCG log for PCR[7] is included in this event.	BitLocker determined that the TCG log is invalid for use of Secure Boot. The filtered TCG log for PCR[7] is included in this event.
0xB0000343	BitLocker cannot use Secure Boot for integrity because the expected TCG Log entry for the OS Loader Authority has invalid structure.%n%nThe event is expected to be an EV_EFI_VARIABLE_AUTHORITY event. The event data must be formatted as an EFI_VARIABLE_DATA structure with VariableName set to EFI_IMAGE_SECURITY_DATABASEGUID and UnicodeName set to 'db'.	BitLocker cannot use Secure Boot for integrity because the expected TCG Log entry for the OS Loader Authority has invalid structure.%n%nThe event is expected to be an EV_EFI_VARIABLE_AUTHORITY event. The event data must be formatted as an EFI_VARIABLE_DATA structure with VariableName set to EFI_IMAGE_SECURITY_DATABASEGUID and UnicodeName set to 'db'.
0xB0000344	BitLocker cannot use Secure Boot for integrity because the expected TCG Log entry for the OS Loader Authority is invalid.%n%nThe contents of the EFI_VARIABLE_DATA.VariableData field should be an EFI_SIGNATURE_DATA structure with SignatureOwner set to the GUID {77fa9abd-0359-4d32-bd60-28f4e78f784b} (Microsoft).	BitLocker cannot use Secure Boot for integrity because the expected TCG Log entry for the OS Loader Authority is invalid.%n%nThe contents of the EFI_VARIABLE_DATA.VariableData field should be an EFI_SIGNATURE_DATA structure with SignatureOwner set to the GUID {77fa9abd-0359-4d32-bd60-28f4e78f784b} (Microsoft).
0xB0000345	BitLocker cannot use Secure Boot for integrity because the expected TCG Log entry for the OS Loader Authority is invalid.%n%nThe EFI_SIGNATURE_DATA structure contained in the OS authority event could not be found in the Secure Boot 'db' signature database.	BitLocker cannot use Secure Boot for integrity because the expected TCG Log entry for the OS Loader Authority is invalid.%n%nThe EFI_SIGNATURE_DATA structure contained in the OS authority event could not be found in the Secure Boot 'db' signature database.
0xB0000346	BitLocker cannot use Secure Boot for integrity because the signature of the boot loader could not be validated as a Windows signature chained to a trusted Microsoft root certificate.	BitLocker cannot use Secure Boot for integrity because the signature of the boot loader could not be validated as a Windows signature chained to a trusted Microsoft root certificate.
0xB0000347	BitLocker cannot use Secure Boot for integrity because the TCG Log entry for the OS Loader Authority is invalid.%n%nThe signature contained in the EFI_SIGNATURE_DATA structure from the OS authority event could not be found in the verified certificate chain for the boot loader.	BitLocker cannot use Secure Boot for integrity because the TCG Log entry for the OS Loader Authority is invalid.%n%nThe signature contained in the EFI_SIGNATURE_DATA structure from the OS authority event could not be found in the verified certificate chain for the boot loader.
0xB0000348	A trusted WIM file has been added for volume %3.%nThe SHA-256 hash of the WIM file is: %5	A trusted WIM file has been added for volume %3.%nThe SHA-256 hash of the WIM file is: %5
0xB0000349	BitLocker was unable to update a key for volume %3 due to the following error: %4	BitLocker was unable to update a key for volume %3 due to the following error: %4
0xB000034A	BitLocker was unable to reseal boot settings to the TPM in the Windows Recovery Environment.%n%nError: %1%n%nProtection has been temporarily suspended.	BitLocker was unable to reseal boot settings to the TPM in the Windows Recovery Environment.%n%nError: %1%n%nProtection has been temporarily suspended.
0xB000034B	BitLocker was suspended from within the Windows Recovery Environment.%nSuspend time: %2	BitLocker was suspended from within the Windows Recovery Environment.%nSuspend time: %2
0xB000034C	BitLocker was unable to recover from device lock in the Windows Recovery Environment.%n%nError: %1%n%nProtection has been temporarily suspended.	BitLocker was unable to recover from device lock in the Windows Recovery Environment.%n%nError: %1%n%nProtection has been temporarily suspended.
0xB000034D	BitLocker Drive Encryption recovery information for volume %1 was backed up successfully to your Azure AD.%nProtector GUID: %2.%nTraceId: %3	BitLocker Drive Encryption recovery information for volume %1 was backed up successfully to your Azure AD.%nProtector GUID: %2.%nTraceId: %3
0xB000034E	Failed to backup BitLocker Drive Encryption recovery information for volume %1 to your Azure AD.%nTraceId: %2%n%nError: %3	Failed to backup BitLocker Drive Encryption recovery information for volume %1 to your Azure AD.%nTraceId: %2%n%nError: %3
0xB000034F	Failed to save BitLocker Drive Encryption recovery information to your Azure AD due to an error.%n%nError Code: %1%nLocalized Error Message: %2	Failed to save BitLocker Drive Encryption recovery information to your Azure AD due to an error.%n%nError Code: %1%nLocalized Error Message: %2
0xB0001000	Device Encryption could not be initialized.%n%nError: %1.	Device Encryption could not be initialized.%n%nError: %1.
0xB0001001	Device Encryption initialization start.	Device Encryption initialization start.
0xB0001002	Device Encryption initialization stop.	Device Encryption initialization stop.
0xB0001003	Device Encryption failed to process user logon event.%n%nError: %1.	Device Encryption failed to process user logon event.%n%nError: %1.
0xB0001004	Beginning Device Encryption user logon processing.	Beginning Device Encryption user logon processing.
0xB0001005	Ending Device Encryption user logon processing.	Ending Device Encryption user logon processing.
0xB0001006	BitLocker failed to recover after Device Lock.%nError message: %1.	BitLocker failed to recover after Device Lock.%nError message: %1.
0xB0001007	Failed to automatically enable Device Encryption.%n%nError Message: %1	Failed to automatically enable Device Encryption.%n%nError Message: %1
0xB0001008	Begin Enable Protection.	Begin Enable Protection.
0xB0001009	End Enable Protection.	End Enable Protection.
0xB000100A	Failed to automatically back up recovery password to your Microsoft account.%n%nError Message: %1	Failed to automatically back up recovery password to your Microsoft account.%n%nError Message: %1
0xB000100B	Begin Recovery Password Backup.	Begin Recovery Password Backup.
0xB000100C	End Recovery Password Backup.	End Recovery Password Backup.
0xB000100D	Begin Query Protection Status.	Begin Query Protection Status.
0xB000100E	End Query Protection Status.	End Query Protection Status.
0xB000100F	Device Lock recovery event initiated for volume %3.	Device Lock recovery event initiated for volume %3.
0xB0001010	MaxPasswordRetry policy enforced with TPM-based hardening for volume %3.	MaxPasswordRetry policy enforced with TPM-based hardening for volume %3.
0xB0001011	MaxPasswordRetry policy enforced without hardware based hardening for volume %3.	MaxPasswordRetry policy enforced without hardware based hardening for volume %3.
0xB0001012	Device Lock recovery event initiated due to protected state mismatch for volume %3.	Device Lock recovery event initiated due to protected state mismatch for volume %3.
0xB0001014	Device Encryption initialization for volume %3 start.	Device Encryption initialization for volume %3 start.
0xB0001015	Device Encryption initialization for volume %3 stop.	Device Encryption initialization for volume %3 stop.
0xB0001016	Volume %3 could not be initialized for Device Encryption.%n%nError: %4.	Volume %3 could not be initialized for Device Encryption.%n%nError: %4.
0xB0001017	Windows RE is not correctly configured for device encryption. Make sure that Windows RE is enabled and is not installed on the OS drive.	Windows RE is not correctly configured for device encryption. Make sure that Windows RE is enabled and is not installed on the OS drive.
0xB0001018	The TPM is not provisioned for device encryption. To set up the TPM use the TPM management console (Start-tpm.msc) and use the action to make the TPM ready.	The TPM is not provisioned for device encryption. To set up the TPM use the TPM management console (Start-tpm.msc) and use the action to make the TPM ready.
0xB0001019	Sign in with a Microsoft account to finish provisioning device encryption.	Sign in with a Microsoft account to finish provisioning device encryption.
0xD0000001	Group Policy	Group Policy
0xD0000002	Caller Supplied	Caller Supplied
0xD0000003	Secure Boot	Secure Boot
0xD0000004	Existing Protector	Existing Protector
0xD0000005	Default for PCs with UEFI firmware	Default for PCs with UEFI firmware
0xD0000006	Default for PCs with BIOS firmware	Default for PCs with BIOS firmware
0xF0000001	0	0
0xF0000002	1	1
0xF0000003	2	2
0xF0000004	3	3
0xF0000005	4	4
0xF0000006	5	5
0xF0000007	6	6
0xF0000008	7	7
0xF0000009	8	8
0xF000000A	9	9
0xF000000B	10	10
0xF000000C	11	11

File Name:	fveapi.dll.mui
Directory:	%WINDIR%\WinSxS\amd64_microsoft-windows-s..rtup-core.resources_31bf3856ad364e35_10.0.15063.0_en-us_66352f4f666a80d3\
File Size:	32 kB
File Permissions:	rw-rw-rw-
File Type:	Win32 DLL
File Type Extension:	dll
MIME Type:	application/octet-stream
Machine Type:	Intel 386 or later, and compatibles
Time Stamp:	0000:00:00 00:00:00
PE Type:	PE32
Linker Version:	14.10
Code Size:	0
Initialized Data Size:	31744
Uninitialized Data Size:	0
Entry Point:	0x0000
OS Version:	10.0
Image Version:	10.0
Subsystem Version:	6.0
Subsystem:	Windows GUI
File Version Number:	10.0.15063.0
Product Version Number:	10.0.15063.0
File Flags Mask:	0x003f
File Flags:	(none)
File OS:	Windows NT 32-bit
Object File Type:	Dynamic link library
File Subtype:	0
Language Code:	English (U.S.)
Character Set:	Unicode
Company Name:	Microsoft Corporation
File Description:	Windows BitLocker Drive Encryption API
File Version:	10.0.15063.0 (WinBuild.160101.0800)
Internal Name:	FVEAPI.DLL
Legal Copyright:	© Microsoft Corporation. All rights reserved.
Original File Name:	FVEAPI.DLL.MUI
Product Name:	Microsoft® Windows® Operating System
Product Version:	10.0.15063.0

fveapi.dll.mui is Multilingual User Interface resource file that contain English (U.S.) language for file fveapi.dll (Windows BitLocker Drive Encryption API).

File Description:	Windows BitLocker Drive Encryption API
File Version:	10.0.15063.0 (WinBuild.160101.0800)
Company Name:	Microsoft Corporation
Internal Name:	FVEAPI.DLL
Legal Copyright:	© Microsoft Corporation. All rights reserved.
Original Filename:	FVEAPI.DLL.MUI
Product Name:	Microsoft® Windows® Operating System
Product Version:	10.0.15063.0
Translation:	0x409, 1200