Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | WHfBPre-Provisioning certificate enrollment failure (0x801C03ED) | Windows Event Viewer > Microsoft > Windows > User Device Registration > Admin - Event ID 307 or 360 | -> |
| Affected build range | Windows 10, Windows 11, Azure AD, Entra ID | ||
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Policies\Microsoft\WindowsHelloForBusiness | Registry Editor | -> |
| Relevant service/endpoint URL | https://ndes.example.com/certsrv/mscep/mscep.dll | ||
| Log line signature | Event ID 307 or 360 with error 0x801C03ED | Windows Event Viewer > Microsoft > Windows > User Device Registration > Admin | -> |
Log Files to Check
C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\NGC logsC:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log
What This Error Actually Means
The error code 0x801C03ED, specifically "WHfBPre-Provisioning certificate enrollment failure," is raised by the Windows Hello for Business (WHfB) component during the provisioning process when it fails to obtain a necessary certificate from an on-premises or hybrid Certificate Authority (CA). This error indicates that there's a problem with either the network connectivity between the device and the CA, or with the configuration of the certificate template used by the CA. The failure can prevent users from setting up Windows Hello for Business authentication, leading to issues in accessing corporate resources securely.Affected Versions and Scope
This error is relevant across multiple versions of Windows operating systems including Windows 10 and Windows 11, as well as environments utilizing Azure Active Directory (Azure AD) or Microsoft Entra ID. The issue can occur both for on-premises deployments where an NDES server is used to manage certificates and in hybrid scenarios where devices are enrolled with Azure AD but still rely on an internal CA for certificate issuance. It's important to note that this error does not affect standalone Windows installations without a corporate enrollment mechanism or when using cloud-managed certificates exclusively through Microsoft Intune.Where To Look First: Logs and Event IDs
To diagnose the issue, start by examining the following logs: - **Windows Event Viewer**: Navigate to `Applications and Services Logs > Microsoft > Windows > User Device Registration > Admin`. Look for events with ID 307 or 360 that contain the error code 0x801C03ED. These entries will provide detailed information about why the certificate enrollment failed. - **NGC logs**: The path to these logs is `C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\NGC`. Accessing this directory requires SYSTEM-level privileges, as it contains sensitive data regarding NGC operations and certificate management processes. - **Intune Management Extension Logs**: If the device is managed via Intune, check the log file located at `C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log` for any related errors or warnings.Root Causes
Network Connectivity Issues to NDES Server
One common cause is a network issue preventing the device from reaching the Network Device Enrollment Service (NDES) endpoint. This could be due to firewall rules blocking port 443, which is necessary for HTTPS communication with the NDES server.Certificate Template Configuration Errors
Another frequent root cause involves misconfiguration of the certificate template used by the CA for Windows Hello certificates. Specifically, the 'Windows Hello for Business Authentication' template must be correctly set up to include Key Usage attributes such as Key Encipherment and Digital Signature. Additionally, ensure that the NDES service account has Enroll permissions on this template.Device Registration Status in Azure AD/Entra ID
If the device is part of an environment integrated with Azure AD or Entra ID, it must be properly registered within these services for WHfB to function correctly. A stale or missing device object can lead to certificate issuance failures.Fix Procedure
To resolve this issue, follow these steps: 1. **Verify NDES Connectivity**: From the affected device, use PowerShell to test connectivity to the NDES endpoint:Invoke-WebRequest https://ndes.example.com/certsrv/mscep/mscep.dll -UseBasicParsing | Select-Object StatusDescription
2. **Check Certificate Template Configuration**:
- Open the Certification Authority MMC snap-in and review the 'Windows Hello for Business Authentication' template.
- Ensure that Key Usage includes both Key Encipherment and Digital Signature, and that the NDES service account has Enroll permissions.
3. **Re-enroll Device in Azure AD/Entra ID**:
If the device object is stale or missing, re-register it using PowerShell cmdlets such as `Connect-MsolService` followed by `New-MsolDevice`.
4. **Update Group Policy and Intune Settings**: Ensure that WHfB Group Policy settings target the correct Organizational Unit (OU) where the affected devices reside. Similarly, verify that the appropriate certificate profile is assigned to the device group in Microsoft Intune.
5. **Review Event Logs for Additional Clues**:
Use PowerShell cmdlets like `Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 10` to inspect recent events and identify any additional errors or warnings that might provide insight into the problem.
Warning: Re-enrolling a device in Azure AD/Entra ID can disrupt existing user sessions. Ensure you communicate with users beforehand.
Error Code Variants
| Error Code | Description |
|---|---|
| 0x801C03E9 | WHfB certificate enrollment failure due to incorrect template configuration. |
| 0x801C0402 | WHfB certificate renewal failed because the device is not registered in Azure AD/Entra ID. |
Verification
After implementing the fixes, verify that the issue has been resolved by checking: - The event logs for Event IDs 307 or 360 without error codes. - Intune Management Extension logs to confirm successful certificate enrollment. - WHfB status via `dsregcmd /status` command output showing 'WorkplaceJoined' and 'AzureAdJoined' as YES.Prevention
To prevent recurrence of this issue, ensure that: - Network policies allow outbound HTTPS traffic on port 443 to the NDES server. - Certificate templates are correctly configured with necessary permissions and attributes. - Regularly audit device registration status in Azure AD/Entra ID and re-enroll devices as needed.
Tip: Use `Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'"` to quickly identify devices enrolled via Intune that may require attention.
By following these guidelines, you can effectively diagnose and resolve the WHfBPre-Provisioning certificate enrollment failure error in your environment.