Skip to content

Ulysses Neves

Microsoft Entra ID, authentication, and hybrid identity troubleshooting.

Menu
  • Início
  • Microsoft Azure
  • Microsoft AD FS
  • Microsoft 365
  • Contact
Menu

WHfB – Fixing error message 0xCAA20064 during windows hello for business certificate trust enrollment

Posted on 28 de July de 2022

Hi mates. Today, I will cover how to identify and fix the error message 0xCAA20064 during Windows Hello sign-in certificate enrollment. 

Scenario: During Hybrid and OnPrem Windows Hello deployments using certificate trust, AD FS is used as a registration authority to request a certificate against the CA on behalf of the user. If there is a missing requirement or broken communication between the Client » AD FS » CA, you might face an error message in the Event Viewer » Microsoft/Windows-HelloForBusiness/Operational as below:

During WHfB enrollment, to get more information on the error message above, you can enable AD FS Tracing logs.

On AD FS Tracing logs, you might see error message below looking on event ID 1021:

Microsoft.IdentityServer.Web.Protocols.OAuth.Exceptions.OAuthLogonCertCreationException: MSIS9400: Unable to create the certificate. Error: System.Runtime.InteropServices.COMException (0x800706BA): CertEnroll::CX509Enrollment::Enroll: The certificate request could not be submitted to the certification authority. A certificate could not be issued by the certification authority.: The RPC server is unavailable. 0x800706ba (WIN32: 1722 RPC_S_SERVER_UNAVAILABLE) at Microsoft.CertificateServices.Certenroll.Interop.CX509EnrollmentClass.Enroll() at Microsoft.IdentityServer.WebHost.Configuration.CertificateAuthorityUtility.BuildUserCertificateWithExternalCA(IX509CertificateRequestPkcs10 incomingRequest, String upn, String distinguishedName, String windowsAccountName, String logonTemplateName, X509Certificate2 enrollmentCertificate, Boolean machineContext, X509Certificate2& issuedCert)

You might also see event below:

EXIT: ConvertPKCS10EncodedStringToObject
Obtained enroll certificate private key successfully. enrollCertKey: CNGKey
ENTER: BuildUserCertificateWithExternalCA
EXIT: BuildUserCertificateWithExternalCA
Error happened while generating the enrollment Certificate
EXIT: BuildUserLogonCertificate

Detailed error message:

An OAuth Win Hello Cert could not be issued: to client ‘dd762716-544d-4aeb-a526-687b73838a22’ for resource ‘urn:microsoft:winhello:cert:prov:server’. The client IP is ‘10.0.0.XX’ . The user is ‘user1@contoso.com’ .The Exception encountered: ‘Microsoft.IdentityServer.Web.Protocols.OAuth.Exceptions.OAuthLogonCertCreationException: MSIS9400: Unable to create the certificate. Error: System.Runtime.InteropServices.COMException (0x800706BA): CertEnroll::CX509Enrollment::Enroll:

REASON/ISSUE

To investigate this issue, you should start checking the connectivity between AD FS and Root CA to guarantee AD FS is able to request a certificate on behalf of the user.

To have a proper certificate request, make sure the required ports for Active Directory Certificate Services are properly configured using this Microsoft official public document.

On success WHfB deployments, event ID 8066 can be observed in the client and one authentication certificate issued by a CA can be found in the user’s my store as below:

Checking the user’s certificate store, we can identify two certificates, one self-signed and one generated by the CA for Client Authentication.

On a Windows Hello for Business Certificate Trust deployment, the certificate used to authenticate the user will be the certificate generated by the trusted Certification Authority.

Summary

In this article, we covered how to identify and fix the error message 0xCAA20064 during Windows Hello sign-in certificate enrollment.

I hope you have enjoyed reading this article, and it helps you manage your Windows Hello for Business environment.

Enjoyed the article? Like and share. 🙂

Note: I do not represent the organization I work for, all the opinions expressed here, are my own. This post is provided AS IS with no warranties or guarantees and confers no rights.

In case you have any suggestions or feedback, please leave a comment.

[ ]’s
Ulysses Neves

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Microsoft Authenticator Will Block Jailbroken Devices in 2026 — What You Need to Know 17 de March de 2026
  • Enhancing Azure role activation security with FIDO2/Passkeys 23 de September de 2024
  • Microsoft Entra ID CAP | Enforcing WHfB using Authentication Strength 21 de April de 2024
  • Troubleshooting Error Code ‘0x000005e’ in WHfB: PIN Authentication Woes 11 de February de 2024
  • WHfB: Fixing Windows Hello for Business error ‘LogoncertTemplateReady: NO (StateNoTemplate)’ 29 de December de 2023

Archives

  • March 2026
  • September 2024
  • April 2024
  • February 2024
  • December 2023
  • September 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019

Tags

#aaddownleveldevice #aadhybridjoin #adfs #adfsonsql #azuread #azureauth #azureCA #azuredevice #azurehybridjoin #azuremfa #azuresecurity #capolicy #cloudkerberostrust #conditionalaccess #conditionalaccesspolicy #deviceregistration #gmsaaccount #gopasswordless #hybridaadjoin #mfaserver #msadfs #msazure #msidentity #namedlocation #sslcertificatevalidation #tshootadfs #tshoothybridjoin #tshootwaptrust #waptrust #WHFBcerttrust #whfbdeployment #WHfBhybridsetup #widdatabase adconnect authenticationcontext authenticationstrength az500 azuread azuremfa azurepim azuresecurity cloudsecurity microsoft365 msazure WHfB
©2026 Ulysses Neves | Design: Newspaperly WordPress Theme
Ulysses Neves
Gerenciar Consentimento de Cookies
Para fornecer as melhores experiências, usamos tecnologias como cookies para armazenar e/ou acessar informações do dispositivo. O consentimento para essas tecnologias nos permitirá processar dados como comportamento de navegação ou IDs exclusivos neste site. Não consentir ou retirar o consentimento pode afetar negativamente certos recursos e funções.
Funcional Always active
O armazenamento ou acesso técnico é estritamente necessário para a finalidade legítima de permitir a utilização de um serviço específico explicitamente solicitado pelo assinante ou utilizador, ou com a finalidade exclusiva de efetuar a transmissão de uma comunicação através de uma rede de comunicações eletrónicas.
Preferências
O armazenamento ou acesso técnico é necessário para o propósito legítimo de armazenar preferências que não são solicitadas pelo assinante ou usuário.
Estatísticas
O armazenamento ou acesso técnico que é usado exclusivamente para fins estatísticos. O armazenamento técnico ou acesso que é usado exclusivamente para fins estatísticos anônimos. Sem uma intimação, conformidade voluntária por parte de seu provedor de serviços de Internet ou registros adicionais de terceiros, as informações armazenadas ou recuperadas apenas para esse fim geralmente não podem ser usadas para identificá-lo.
Marketing
O armazenamento ou acesso técnico é necessário para criar perfis de usuário para enviar publicidade ou para rastrear o usuário em um site ou em vários sites para fins de marketing semelhantes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
Ver preferências
  • {title}
  • {title}
  • {title}