HEX

File: C:/Windows/System32/en-US/fveapi.dll.mui

MZ����@��� �!�L�!This program cannot be run in DOS mode.

$5�<�q�R�q�R�q�R�e���p�R�e�P�p�R�Richq�R�PEL�!�

��@ 4�8.rdata�@@.rsrc� �@@S�h7
T88S�h7$��8.rdata8x.rdata$zzzdbg @.rsrc$01@!�.rsrc$02 �<��z�s���� /'��2���yS�h70�0�H�`�x���?������ � 8!���!0� "T��t���MUI����V)�6j�݀�����;¥4O����(���#����MUIen-US%1 %2 %3�78�wxd00�PP�dpep�����6�89�m��Kp�v��}y�{�x�����8�������<�*�1�t���d���4BitLocker Drive Encryption recovery information was backed up successfully to Active Directory Domain Services.%nProtector GUID: %1%nVolume GUID: %2

<Failed to backup BitLocker Drive Encryption recovery information to Active Directory Domain Services.%nErrorcode: %2%nProtector GUID: %1%nVolume GUID: %3

\BitLocker Drive Encryption recovery information for the specified protector is already present in Active Directory Domain Services.%nProtector GUID: %1%nVolume GUID: %2

�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

pA 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

,The attempt to create a data recovery agent protector on the BitLocker volume failed.%nErrorcode: %1%nCertificate thumbprint: %2%nVolume GUID: %3

�The servicing of the data recovery agents on the volume failed.%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

�Bootmgr failed to obtain the BitLocker volume master key from the TPM because the PCRs did not match.

�Bootmgr determined that the following boot application has changed: %1

�Bootmgr determined that the boot configuration data setting %1 has changed for the following boot application: %2

�Bootmgr determined that the authorization data for the SRK of the TPM is incompatible with BitLocker.

dBootmgr determined that the TPM is disabled.

pBootmgr determined that the TPM is not accessible.

�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.

�Boot debugging is enabled on Bootmgr so TPM based keys cannot be obtained.

�Bootmgr determined that driver signature enforcement has been disabled.

�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 Device Lockout state validation failure.

�Bootmgr determined that the TPM is not present or recognized.

�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 configuration changed unexpectedly.

xThere was a problem communicating with the TPM at boot.

�BitLocker failed to obtain the key from the TPM due to an unforseen TPM failure.

Start

Stop

Error

Warning

Information

HBitLocker PIN Modification Task

TBitLocker Password Modification Task

HMicrosoft-Windows-BitLocker-API

System

Management

Operational

�BitLocker encryption was started for volume %3 using %4 algorithm.

�BitLocker encryption will occur for volume %3 when the computer is restarted using %4 algorithm.

hBitLocker decryption was started for volume %3.

hBitLocker encryption was stopped for volume %3.

�BitLocker encryption was restarted for volume %3 using %4 algorithm.

XBitLocker was suspended for volume %3.

TBitLocker was resumed for volume %3.

�A BitLocker key protector was created.%nProtector GUID: %4%nIdentification GUID: %1

�A BitLocker key protector was removed.%nProtector GUID: %4%nIdentification GUID: %1

�The PIN was updated for the operating system volume.%nProtector GUID: %4%nIdentification GUID: %1

�The BitLocker volume %3 was reverted to an unprotected state.

PThe BitLocker volume %3 was erased.

�The identification field was changed. %nIdentification GUID: %1

�The BitLocker protected volume %3 was locked. %nIdentification GUID: %1

�The BitLocker protected volume %3 was unlocked.%nProtector GUID: %4%nIdentification GUID: %1

lBitLocker Drive Encryption recovery information for the specified protector is already present in Active Directory Domain Services.%nProtector GUID: %4%nIdentification GUID: %1

DBitLocker Drive Encryption recovery information was backed up successfully to Active Directory Domain Services.%nProtector GUID: %4%nIdentification GUID: %1

0Failed to backup BitLocker Drive Encryption recovery information to Active Directory Domain Services.%nProtector GUID: %4%nIdentification GUID: %1

xBitLocker free space wiping was started for volume %3.

xBitLocker free space wiping was stopped for volume %3.

|BitLocker free space wiping was restarted for volume %3.

4The PIN was changed.

hA PIN change attempt failed.%nError message: %1

The BitLocker Service (BdeSvc) PIN and password change facility is locked out due to too many failed PIN or password change attempts.

�BitLocker encountered a failure to commit metadata changes for volume %3.

�BitLocker resealed boot settings to the TPM for volume %3.

�BitLocker failed to reseal boot settings to the TPM.%nError message: %1.

�BitLocker failed to initialize hardware encryption for volume %3 due to group policy.

�BitLocker Drive Encryption is using software-based encryption to protect volume %3.

@Group Policy settings prevented BitLocker Drive Encryption from reverting to BitLocker software-based encryption. Volume %3 is not protected by BitLocker.

�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:%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:%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 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:%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 above the maximum key length supported by the drive: %4.

�The target drive (%3) cannot be managed by BitLocker because the drive's hardware encryption feature is already in use.

(The BitLocker protected volume was unlocked in the Windows Recovery Environment.%nProtector GUID: %2%nIdentification GUID: %1%nUnlock time: %4

�BitLocker resealed boot settings to the TPM in the Windows Recovery Environment.%nReseal time: %2

xBitLocker free space wiping was canceled for volume %3.

tBitLocker 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 cannot use Secure Boot for integrity because it is disabled in Group Policy.

�BitLocker cannot use Secure Boot for integrity because it is disabled.

�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 UEFI variable '%1' could not be read.%n%nError Message: %2

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 the OS Loader Authority is missing or invalid.

�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 TCG Log for PCR [7] contains invalid entries.

�BitLocker successfully sealed a key to the TPM.%n%nPCRs measured include [%1].%n%nThe source for these PCRs was: %2.

�BitLocker encountered a failure attempting to configure network unlock for volume %3.

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: TPM is locked out.

�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 code: %4.

BitLocker failed to initialize hardware encryption for volume %3.%nThis PC's firmware is not capable of supporting hardware encryption.

<The password was changed.

tA password change attempt failed.%nError message: %1

BitLocker Drive Encryption recovery information for volume %3 was backed up successfully to your Microsoft account.%nProtector GUID: %4

�Failed to backup BitLocker Drive Encryption recovery information for volume %3 to your Microsoft account.%n%nError: %4

�The BitLocker Drive Encryption recovery information already exists in your Microsoft account.

<Failed to save BitLocker Drive Encryption recovery information to your Microsoft account due to an error.%n%nError Code: %1%nLocalized Error Message: %2

XTCG Log parsing failure.%n%nError: %1.

lBitLocker 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 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 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'.

xBitLocker 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 EFI_SIGNATURE_DATA structure contained in the OS authority event could not be found in the Secure Boot 'db' signature database.

xBitLocker cannot use Secure Boot for integrity because the signature of the boot manager could not be validated as a Windows signature chained to a trusted Microsoft root certificate.

8BitLocker 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 manager.

�A trusted WIM file has been added for volume %3.%nThe SHA-256 hash of the WIM file is: %5

�BitLocker was unable to update a key for volume %3 due to the following error: %4

8BitLocker 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 suspended from within the Windows Recovery Environment.%nSuspend time: %2

,BitLocker was unable to recover from device lock in the Windows Recovery Environment.%n%nError: %1%n%nProtection has been temporarily suspended.

$BitLocker Drive Encryption recovery information for volume %1 was backed up successfully to your Azure AD.%nProtector GUID: %2.%nTraceId: %3

Failed to backup BitLocker Drive Encryption recovery information for volume %1 to your Azure AD.%nTraceId: %2%n%nError: %3

(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 update BCD store with the Recovery URL for OS volume.%n%nError: %1

�Failed to set the TPM dictionary attack parameters to the legacy behavior.%n%nError: %1.

�Successfully set the TPM dictionary attack parameters to the legacy behavior.

pFailed to enable Silent Encryption. %n%nError: %1.

�Failed to enable Silent Encryption. Device is not AAD joined. %n%nError: %1.

�Failed to enable Silent Encryption. TPM is not available. %n%nError: %1.

�Failed to enable Silent Encryption. WinRe is not configured. %n%nError: %1.

TRecovery Password Rotation initiated.

�Failed to initiate the Recovery Password Rotation %n%nError:%1.

dRecovery Passwords Rotation done successfully

lRecovery Password Rotation failed. %n%nError: %1.

�Recovery Password Rotation failed.%nVolume: %1%nMount: %2%nReqID: %3%nError:%4.

xFailed to delete recovery password from AAD.%nError:%1.

�Failed to create clinet recovery password rotation request. %nvolume: %1%nMount: %2%nReqId: %3%nError: %4.

�Failed to Create AAD recovery Password Delete request.%nVolume: %1%nMount: %2%nReqID: %3%nError:%4.

�Failed to initiate the Recovery Password Rotation and AAD Deletion requests processing %n%nError:%1.

�Recovery Passwords Rotation and AAD Deletion requests processing initiated successfully

�BitLocker was unable to verify if TPM protector resealing is possible for volume %3 due to the following error: %4

�A BitLocker key protector which uses PBKDF2 was created.%nProtector GUID: %4%nIdentification GUID: %1%nProtector Type: %5

Failed to delete BitLocker Drive Encryption recovery information for volume %1 from Azure AD. %nProtector GUID: %2.%nTraceId: %3

�Failed while attempting to get BitLocker Drive Encryption recovery information from Azure AD.%nError code: %1

�An operating system volume BitLocker recovery key password for the currently signed in user has not been backed up.

�Failed to register information for reverted volume. %nVolume: %1%nMount: %2%nReqID: %3%nError:%4.

�Failed to register timer for recovery password cleanup. Error Code: %1

�Failed to save request. Protector ID: %1 , RequestType: %2, VolumeName: %3, Error: %4

`Server reported a failure while attempting to backup a recovery password.%nError: %1 %nHTTP Status Code: %2 %nRetryRequest: %3 %nDidSetRetryHint: %4 %nRetryHintSeconds: %5

tServer reported a failure while attempting to delete recovery password(s) from AAD.%nError: %1 %nHTTP Status Code: %2 %nRetryRequest: %3 %nDidSetRetryHint: %4 %nRetryHintSeconds: %5

�Server reported a failure while attempting to retrieve recovery password information from AAD.%nError: %1 %nHTTP Status Code: %2 %nRetryRequest: %3 %nDidSetRetryHint: %4 %nRetryHintSeconds: %5

�Failed to delete BitLocker Drive Encryption recovery information from Azure AD.%nError: %1

|Not all privileges requested are assigned to the caller.

$BitLocker is unable to predict PCR7 value and will attempt to seal to current TPM PCR7 value as required by policy %nPolicy PCR profile: %1.

lThe signature contained in the EFI_SIGNATURE_DATA structure from the TCG Log OS Loader Authority event could not be found in the verified certificate chain for the boot manager.

,BitLocker cannot use Secure Boot for integrity because hash of the boot manager for the TCG Log OS Loader Authority event could not be predicted.

DBitLocker 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. Signature database type: %1

xBitLocker cannot use Secure Boot for integrity because the signature in a TCG Log Authority event was not found in the Secure Boot 'db' signature database. Signature database type: %1

|BitLocker cannot use Secure Boot for integrity because the signature predicted for the boot manager was not found in the Secure Boot 'db' signature database. Signature database type: %1

�BitLocker removed an orphaned TPM digest datum with identifier %2.

PBitLocker is attempting to seal to a PCR which is known to have events extended into the TPM after the BitLocker TPM cap event. This may cause BitLocker recovery.

\BitLocker conducted a TPM binding census.

BitLocker updated its TPM bindings in response to a PCR Prediction Framework callback. USN: %2, Scenario: %3, Volume: %4, Error: %1.

BitLocker is currently excluding PCRs %1 from its TPM protector PCR profile (%2) as required by a firmware update installation.

�BitLocker is reading the TPM to calculate the PCR %1 value.

|Device Encryption could not be initialized.%n%nError: %1.

XDevice Encryption initialization start.

XDevice Encryption initialization stop.

�Device Encryption failed to process user logon event.%n%nError: %1.

pBeginning Device Encryption user logon processing.

hEnding Device Encryption user logon processing.

�BitLocker failed to recover after Device Lock.%nError message: %1.

�Failed to automatically enable Device Encryption.%n%nError Message: %1

<Begin Enable Protection.

8End Enable Protection.

�Failed to automatically back up recovery password to your Microsoft account.%n%nError Message: %1

HBegin Recovery Password Backup.

DEnd Recovery Password Backup.

HBegin Query Protection Status.

DEnd Query Protection Status.

pDevice Lock recovery event initiated for volume %3.

�MaxPasswordRetry policy enforced with TPM-based hardening for volume %3.

�MaxPasswordRetry policy enforced without hardware based hardening for volume %3.

�Device Lock recovery event initiated due to protected state mismatch for volume %3.

tDevice Encryption initialization for volume %3 start.

tDevice Encryption initialization for volume %3 stop.

�Volume %3 could not be initialized for Device Encryption.%n%nError: %4.

Windows RE is not correctly configured for device encryption. Make sure that Windows RE is enabled and is not installed on the OS drive.

DThe 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.

�Sign in with a Microsoft account to finish provisioning device encryption.

�The following DMA (Direct Memory Access) capable devices are not declared as protected from external access, which can block security features such as BitLocker automatic device encryption:%n%n%1%n

$BitLocker Drive Encryption recovery information for volume %1 was deleted successfully from your Azure AD.%nProtector GUID: %2.%nTraceId: %3

TSuccessfully setup TPM API callback.

lFailed to setup TPM API callback. Error Code: %1

`Successfully added predicted TPM protector.

xFailed to add predicted TPM protector. Error Code: %4.

�Predicted PCR4 value for TPM info based protector. Predicted Value: %5.

�Failed to evaluate PCR4 predicted value from TPM info. Error Code: %1

�Predicted PCR7 value for TPM info based protector. Predicted Value: %5.

�Failed to evaluate PCR7 predicted value from TPM info. Error Code: %1

$Group Policy

(Caller Supplied

Secure Boot

0Existing Protector

PDefault for PCs with UEFI firmware

PDefault for PCs with BIOS firmware

TPM info

(Secure Boot V2

default

<AES-CBC 128 with Diffuser

<AES-CBC 256 with Diffuser

AES-CBC 128

AES-CBC 256

XTS-AES 128

XTS-AES 256

unknown

Current

Measured

Unspecified

TcgLog

PpfEventLog

$TpmStateInfo

�4VS_VERSION_INFO��
{aJ
{aJ? StringFileInfo�040904B0LCompanyNameMicrosoft Corporationv'FileDescriptionWindows BitLocker Drive Encryption APIn'FileVersion10.0.19041.7291 (WinBuild.160101.0800)6InternalNameFVEAPI.DLL�.LegalCopyright� Microsoft Corporation. All rights reserved.FOriginalFilenameFVEAPI.DLL.MUIj%ProductNameMicrosoft� Windows� Operating SystemDProductVersion10.0.19041.7291DVarFileInfo$Translation �PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPAD