Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | Windows Hello for Business provisioning failed. Device cannot create key material. Error code: 0x80090016 | Event Viewer > Microsoft-Windows-HelloForBusiness/Operational log | -> Event ID 1002 or 1003 |
| Affected build range | Windows 10 and Windows 11 | | |
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TPM | Registry Editor | -> Check TPM ownership status |
| Relevant service/endpoint URL | https://device.login.microsoftonline.com/ | | -> Verify device registration status |
| Log line signature | <Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'><System><Provider Name='Microsoft-Windows-HelloForBusiness'/></System><EventData><Data Name='ErrorCode'>80090016</Data></EventData></Event> | | -> Event ID 1002 or 1003 |
Log Files to Check
C:\Windows\System32\winevt\Logs\Microsoft-Windows-HelloForBusiness%4Operational.evtxC:\Users\Public\Documents\MDMDiagnostics\MDM-DiagnosticReport.html
What This Error Actually Means
The error code `0x80090016` is a cryptographic provider error indicating that the keyset does not exist, which means Windows Hello for Business (WHfB) cannot create or access its asymmetric key pair used for passwordless sign-in. The error occurs when the TPM (Trusted Platform Module) or virtual secure environment has been cleared, corrupted, or was never properly initialized to store WHfB keys. This issue is raised by the Microsoft-Windows-HelloForBusiness component and can be found in Event Viewer logs under the Operational log.
Affected Versions and Scope
This error affects Windows 10 and Windows 11 devices that are hybrid Azure AD joined, meaning they are both domain-joined and Azure Active Directory (AAD) registered. The issue is particularly prevalent on devices where TPM or virtual secure module management has been altered through system resets, firmware updates, or migration processes involving Hyper-V VMs.
Where To Look First: Logs and Event IDs
To diagnose this error, start by examining the following logs:
-
C:\Windows\System32\winevt\Logs\Microsoft-Windows-HelloForBusiness%4Operational.evtx
-
C:\Users\Public\Documents\MDMDiagnostics\MDM-DiagnosticReport.html
In Event Viewer, navigate to the following path:
Applications and Services Logs > Microsoft > Windows > HelloForBusiness > Operational log
Look for events with IDs 1002 or 1003. The exact error string is "Windows Hello for Business provisioning failed. Device cannot create key material. Error code: 0x80090016". Additionally, you can use the following PowerShell cmdlet to filter these logs:
Get-WinEvent -LogName 'Microsoft-Windows-HelloForBusiness/Operational' | Where-Object { $_.Id -eq 1002 -or $_.Id -eq 1003 }
Root Causes
Troubled TPM Ownership or State
When the TPM is cleared, reset, or its ownership status changes unexpectedly due to system resets or firmware updates, WHfB keys may be lost or become inaccessible. To identify this issue, check if the TPM is owned by Windows using:
Get-Tpm | Select-Object TpmPresent, TpmReady, TpmOwned
If
TpmOwned returns False, it indicates that the TPM needs to be re-owned.
Migrated or Restored Hyper-V VMs with vTPM
Virtual secure modules (vTPMs) in Hyper-V VMs are snapshot-bound. If a snapshot is restored after provisioning WHfB keys, these keys become invalid and inaccessible. To confirm if this applies to your scenario, check the virtual machine settings for TPM status.
Policy Changes Affecting TPM Ownership
Group Policy or Intune policies can alter TPM owner authorizations, potentially orphaning existing key containers. Review recent changes in policy management systems like Microsoft Endpoint Manager (MEM) to identify if any such alterations occurred around the time of the error.
Fix Procedure
- Delete stale WHfB keys from Entra ID: In the Entra admin center, navigate to Identity > Devices > All devices. Select the affected device and go to Authentication methods or Properties tab. Delete any 'Blocked' or 'Stale' keys.
- Re-enable TPM in BIOS/UEFI settings if it was disabled. Ensure that the TPM is ready for use by running:
tpm.msc
- If TPM reinitialization is required, run PowerShell as Administrator and execute:
This step will clear all TPM data.
Initialize-Tpm -AllowClear. Save BitLocker recovery keys before proceeding.
- Rejoin the device to Entra ID after clearing TPM or re-enabling it. Use Settings > Accounts > Access work or school > Connect and follow prompts for re-enrollment.
- If dealing with a vTPM VM, restore from a snapshot taken before provisioning WHfB keys or recreate the vTPM configuration in Hyper-V Manager under Security settings.
Error Code Variants
| Code |
Description |
Distinguishing Factors |
0x80090017 |
Keyset does not exist (similar to 0x80090016) |
This error often occurs due to a corrupted or missing key container, whereas 0x80090016 specifically indicates that the TPM is unresponsive. |
0x80072325 |
Device not compatible with WHfB (different from 0x80090016) |
This error is raised when the device hardware does not meet minimum requirements for WHfB, while 0x80090016 pertains to TPM state and key management issues. |
Verification
After re-provisioning, verify that the issue is resolved by checking:
- Event ID 1001 in
Microsoft-Windows-HelloForBusiness/Operational log to ensure provisioning was successful.
- Run
dsregcmd /status and confirm 'NgcSet: YES' under the Ngc Prerequisite Check section.
Prevention
To prevent recurrence, consider implementing the following measures:
- Ensure TPM is enabled in BIOS/UEFI settings before deploying devices.
- Configure Intune to enforce TPM key attestation requirements by navigating to Devices > Configuration and creating an Endpoint Protection profile for Windows 10/11 with WHfB enabled.
- Regularly review and document policy changes affecting TPM ownership and management.
A quick diagnostic shortcut is to use the Get-Tpm cmdlet in PowerShell to check TPM status directly without navigating through Event Viewer logs.
This guide provides a comprehensive approach for troubleshooting and resolving Windows Hello for Business provisioning errors due to TPM-related issues on hybrid Azure AD joined devices.