????

Your IP : 216.73.216.152

Current Path : C:/Windows/System32/en-US/
Upload File :
Current File : C:/Windows/System32/en-US/TpmCoreProvisioning.dll.mui

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

$��<߱�R���R���R�U�����R�U�P���R�Rich��R�PEL�!0

P|�@ @-8.rdata�@@.rsrc0 .@@ߦ~
T88ߦ~$��8.rdata8x.rdata$zzzdbg �.rsrc$01� X,.rsrc$02 �[t]�B�Z-w.Swͬly���n�&P�$�ߦ~��(�@�X�p�����	�	�	�� ���!�'�dI��MUI���i�g��AD%׶qu�~�-0� �[v́9?�tʱ���MUIen-US��

(��|\PP� ��� �
�4!��T"�TPM Owner Authorization information was backed up successfully to Active Directory Domain Services.

tFailed to backup TPM Owner Authorization information to Active Directory Domain Services.%nErrorcode: %1%nCheck that your computer is connected to the domain.  If your computer is connected to the domain, have your Domain Administrator check that the Active Directory schema is appropriate for backup of Windows 8 TPM Owner Authorization information and that the current Computer object has write permission to the TPM object.  Installations of Windows Server 2008 R2 or before need a schema extension in order to be ready for backup of Windows 8 TPM Owner Authorization information.  Consult online documentation for more information about setting up Active Directory Domain Services for TPM.

The Trusted Platform Module (TPM) hardware on this computer has failed to set its Dictionary Attack Parameters to legacy mode.

�Successfully sent physical presence request to clear the Trusted Platform Module(TPM).

�Failed to send physical presence request to clear the Trusted Platform Module(TPM).

Failed to get isOwned status from Trusted Platform Module(TPM), proceeding to clear TPM assuming that TPM is owned. Error code:%1

TThe TPM has been cleared. Reason: %1.

�TPM Owner Authorization configuration changed from '%1' to '%2'.

�The TPM was successfully provisioned and is now ready for use.

$The Trusted Platform Module (TPM) hardware on this computer cannot be provisioned for use automatically.  To set up the TPM interactively use the TPM management console (Start->tpm.msc) and use the action to make the TPM ready.%n%nError: %1%nAdditional Information: %2

(The Ownership of the Trusted Platform Module (TPM) hardware on this computer was successfully taken (TPM TakeOwnership command) by the system.

xThe NGC key generation task was successfully triggered.

tThe triggering of the NGC key generation task failed.

�The NGC certificate enrollment task was successfully triggered.

�The triggering of the NGC certificate enrollment task failed.

�The Secure Boot update was not applied due to a known incompatibility with the current BitLocker configuration.

,Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931

`Secure Boot Dbx update applied successfully

`Secure Boot Dbx update applied successfully

`Secure Boot Db update applied successfully

�Secure Boot Dbx update to revoke Microsoft Windows Production PCA 2011 is applied successfully

�Secure Boot Dbx update to revoke older Boot Manager SVNs is applied successfully

|This event triggers the TBS device identifier generation.

dThe TBS device identifier has been generated.

�The Device Health Certificate was successfully provisioned from %1.

�The Device Health Certificate provisioning could not connect to %1. %2

�The Device Health Certificate could not be provisioned from %1. HTTP status code %2: %3

�The Trusted Platform Module (TPM) hardware on this computer is scheduled to be cleared by the system.

�The Trusted Platform Module (TPM) firmware on this PC has a known security problem. Please contact your PC manufacturer to find out if an update is available. For more information please go to https://go.microsoft.com/fwlink/?linkid=852572

`The system firmware returned an error %1 when attempting to update a Secure Boot variable. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931

HThe Secure Boot update failed to update a Secure Boot variable with error %1. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931

�The Secure Boot update failed as the Windows UEFI CA 2023 certificate is not present in Db

�The Secure Boot Dbx update failed as boot manager is not signed with the Windows UEFI CA 2023 certificate

�Boot Manager signed with Windows UEFI CA 2023 was installed successfully

�A reboot is required before installing the Secure Boot update. Reason: %1

Error

Warning

 Information

<Microsoft-Windows-TPM-WMI

System

Legacy

,ResetLockPlusUser

Balanced

$FullOwnerAuth

Full

 LevelCount

$NullBitValue

Null

Lockout

Invalid

@TpmAutoProvisioningDisabled

,ShutdownRequired

(RebootRequired

XTpmForceClearOrImportOwnerAuthRequired

@TpmPhysicalPresenceRequired

 TpmActivate

,TpmTakeOwnership

 TpmCreateEk

,TpmDelegationSync

,TpmSrkAuthInvalid

HTpmDisableOwnerClearFlagNotSet

DTpmSrkPubNotCurrentInRegistry

8TpmReadSrkPubFlagNotSet

<TpmBootCounterNotCreated

DTpmAdBackupOfOwnerAuthNotDone

@TpmAdBackupInProgressPhaseI

DTpmAdBackupInProgressPhaseII

lNoProvisioningDueToLegacyConfigurationOfOwnerAuth

<EkProvisioningNotComplete

DTcgEventLogUnreadableOrEmpty

HMinimalFunctionalityNotAchieved

DNonTaskSpecificErrorOccurred

@DeviceLockCounterNotCreated

�4VS_VERSION_INFO��
!|O
!|O?<StringFileInfo040904B0LCompanyNameMicrosoft CorporationdFileDescriptionTPM Core Provisioning Libraryn'FileVersion10.0.20348.2849 (WinBuild.160101.0800)PInternalNameTpmCoreProvisioning.dll�.LegalCopyright� Microsoft Corporation. All rights reserved.`OriginalFilenameTpmCoreProvisioning.dll.muij%ProductNameMicrosoft� Windows� Operating SystemDProductVersion10.0.20348.2849DVarFileInfo$Translation	�PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDING