Windows / Modules / TpmCoreProvisioning.dll

TpmCoreProvisioning.dll

Associated Error Codes

Below lists error codes and symbolic names found for this module.

CodeFound inDescription
0x2011011TPM Owner Authorization information was backed up successfully to Active Directory Domain Services.
0x2021011Failed to backup TPM Owner Authorization information to Active Directory Domain Services. Errorcode: %1 Check 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.
0x2031011The Trusted Platform Module (TPM) hardware on this computer has failed to set its Dictionary Attack Parameters to legacy mode.
0x2041011Successfully sent physical presence request to clear the Trusted Platform Module(TPM).
0x2051011Failed to send physical presence request to clear the Trusted Platform Module(TPM).
0x2061011Failed to get isOwned status from Trusted Platform Module(TPM), proceeding to clear TPM assuming that TPM is owned. Error code:%1
0x2071011The TPM has been cleared. Reason: %1.
0x3011011TPM Owner Authorization configuration changed from '%1' to '%2'.
0x4011011The TPM was successfully provisioned and is now ready for use.
0x4021011The 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. Error: %1 Additional Information: %2
0x4031011The Ownership of the Trusted Platform Module (TPM) hardware on this computer was successfully taken (TPM TakeOwnership command) by the system.
0x4041011The NGC key generation task was successfully triggered.
0x4051011The triggering of the NGC key generation task failed.
0x4061011The NGC certificate enrollment task was successfully triggered.
0x4071011The triggering of the NGC certificate enrollment task failed.
0x40810The Secure Boot update was not applied due to a known incompatibility with the current BitLocker configuration.
0x4091011Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
0x40a1011Secure Boot Dbx update applied successfully
0x40b1011Secure Boot Dbx update applied successfully
0x40c1011Secure Boot Db update applied successfully
0x40d1011Secure Boot Dbx update to revoke Microsoft Windows Production PCA 2011 is applied successfully
0x4121011Secure Boot Dbx update to revoke older Boot Manager SVNs is applied successfully
0x4131011Secure Boot KEK update applied successfully
0x4141011Secure Boot DB update to install Microsoft Option ROM UEFI CA 2023 certificate applied successfully
0x4151011Secure Boot DB update to install Microsoft UEFI CA 2023 certificate applied successfully
0x5011011This event triggers the TBS device identifier generation.
0x5021011The TBS device identifier has been generated.
0x6011011The Device Health Certificate was successfully provisioned from %1.
0x6021011The Device Health Certificate provisioning could not connect to %1. %2
0x6031011The Device Health Certificate could not be provisioned from %1. HTTP status code %2: %3
0x7011011The Trusted Platform Module (TPM) hardware on this computer is scheduled to be cleared by the system.
0x7021011The 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
0x7031011The system firmware returned an error %1 when attempting to update a Secure Boot variable %2. This device signature information is included here. DeviceAttributes: %3 BucketId: %4 BucketConfidenceLevel: %5. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
0x70410The 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
0x7051011The Secure Boot update failed as the Windows UEFI CA 2023 certificate is not present in Db
0x7061011The Secure Boot Dbx update failed as boot manager is not signed with the Windows UEFI CA 2023 certificate
0x7071011Boot Manager signed with Windows UEFI CA 2023 was installed successfully
0x7081011A reboot is required before installing the Secure Boot update. Reason: %1
0x70910Secure Boot CA/keys need to be updated. This device signature information is included here. DeviceAttributes: %1 BucketId: %2 BucketConfidenceLevel: %3 UpdateType: %4 HResult: %5
0x71010This device has updated Secure Boot CA/keys. This device signature information is included here. DeviceAttributes: %1 BucketId: %2 BucketConfidenceLevel: %3 UpdateType: %4 HResult: %5
0x500000021011Error
0x500000031011Warning
0x500000041011Information
0x900000011011Microsoft-Windows-TPM-WMI
0x900000021011System
0xb00107031011The 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
0xd00000011011Legacy
0xd00000021011ResetLockPlusUser
0xd00000031011Balanced
0xd00000041011FullOwnerAuth
0xd00000051011Full
0xd00000061011LevelCount
0xd00000071011NullBitValue
0xd00000081011Null
0xd00000091011Lockout
0xd000000a1011Invalid
0xf00000011011TpmAutoProvisioningDisabled
0xf00000021011ShutdownRequired
0xf00000031011RebootRequired
0xf00000041011TpmForceClearOrImportOwnerAuthRequired
0xf00000051011TpmPhysicalPresenceRequired
0xf00000061011TpmActivate
0xf00000071011TpmTakeOwnership
0xf00000081011TpmCreateEk
0xf00000091011TpmDelegationSync
0xf000000a1011TpmSrkAuthInvalid
0xf000000b1011TpmDisableOwnerClearFlagNotSet
0xf000000c1011TpmSrkPubNotCurrentInRegistry
0xf000000d1011TpmReadSrkPubFlagNotSet
0xf000000e1011TpmBootCounterNotCreated
0xf000000f1011TpmAdBackupOfOwnerAuthNotDone
0xf00000101011TpmAdBackupInProgressPhaseI
0xf00000111011TpmAdBackupInProgressPhaseII
0xf00000121011NoProvisioningDueToLegacyConfigurationOfOwnerAuth
0xf00000131011EkProvisioningNotComplete
0xf00000141011TcgEventLogUnreadableOrEmpty
0xf00000151011MinimalFunctionalityNotAchieved
0xf00000161011NonTaskSpecificErrorOccurred
0xf00000171011DeviceLockCounterNotCreated
0x40811The Secure Boot update %1 was not applied due to a known incompatibility with the current BitLocker configuration.
0x40e11Pre-attestation health checks confirm that the device is expected to pass attestation. Please see %1 for detailed information on what checks were made.
0x40f11Pre-attestation health checks confirm that the device meets most attestation criteria, but failing is still possible. Please see %1 for detailed information on what checks were made.
0x41011Pre-attestation health checks confirm a critical component has failed, and the device is not expected to pass attestation. Please see %1 for detailed information on what checks were made.
0x41111Pre-attestation health check detailed information: %1
0x41611Measured boot files deleted successfully. The following %1 files were deleted: %2
0x41711Measured boot file %1 was not deleted successfully due to error %2.
0x50311EK Certificate tool started.
0x50411EK Certificate tool succeeded in %1 milliseconds.
0x50511EK Certificate tool failed in %1 milliseconds with error %2.
0x70411The Secure Boot update failed to update %1 with error %2. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
0x70911Updated Secure Boot certificates are available on this device but have not yet been applied to the firmware. Review the published guidance to complete the update and maintain full protection. This device signature information is included here. DeviceAttributes: %1 BucketId: %2 BucketConfidenceLevel: %3 UpdateType: %4 For more information, please see https://go.microsoft.com/fwlink/?linkid=2301018.
0x70a11The Secure Boot update %1 was blocked due to a known firmware issue on the device. Check with your device vendor for a firmware update that addresses the issue. This device signature information is included here. DeviceAttributes: %2 BucketId: %3 BucketConfidenceLevel: %4 SkipReason: %5. For more information, please see https://go.microsoft.com/fwlink/?linkid=2339472
0x70b11A PK-signed Key Exchange Key (KEK) cannot be found for this device. Check with the device manufacturer for proper key provisioning. This device signature information is included here. DeviceAttributes: %1 BucketId: %2 BucketConfidenceLevel: %3. For more information, please see https://go.microsoft.com/fwlink/?linkid=2339472
0x71011This device has updated Secure Boot CA/keys. This device signature information is included here. DeviceAttributes: %1 BucketId: %2 BucketConfidenceLevel: %3 UpdateType: %4 For more information, please see https://go.microsoft.com/fwlink/?linkid=2301018.
0xb000040811The Secure Boot update was not applied due to a known incompatibility with the current BitLocker configuration.
0xb001070411The 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
96 entries