Forum Discussion

lukval's avatar
lukval
Occasional Reader
Aug 25, 2025

BioEnrollmentHost.exe failes setting up Windows Hello (August 2025)

Hello, when trying to add another fingerprint, there is a failure. The editing interface does not open - it disappears without displaying an error message.  The eventlog shows the error: Log Name:...
Account Management
Authentication
Error
windows 11
Kidd_Ip's avatar
Kidd_Ip
MVP
Aug 26, 2025

Take this:

 

  1. Re-register the BioEnrollment App

Sometimes the biometric enrollment app becomes misregistered. Try re-registering it:

Get-AppxPackage Microsoft.BioEnrollment | Foreach {
    Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"
}

Then reboot and try fingerprint enrollment again.

 

  1. Check for Biometric Driver Updates

Even if the OS is clean, biometric drivers may be outdated or incompatible with the latest LTSC build:

  • Open Device Manager > Biometric Devices
  • Right-click your fingerprint sensor > Update driver
  • Or download the latest driver directly from the OEM (e.g., Synaptics, Goodix, Elan)

 

  1. Test in a New User Profile

Sometimes user-specific settings or cached biometric data can cause UI crashes:

  • Create a new local user account
  • Try enrolling a fingerprint from that profile
  • If it works, the issue may be tied to your user profile’s biometric cache

 

  1. Check App Permissions

Ensure the BioEnrollment app has access to biometric hardware:

Get-AppxPackage -Name Microsoft.BioEnrollment | Select Name, PackageFullName

Then verify in Settings > Privacy > Biometrics that access is enabled.

 

  1. Roll Back Recent Updates

If this started after a recent cumulative update, consider rolling it back:

  • Go to Settings > Windows Update > Update History
  • Uninstall the most recent update and test again
mherman9918's avatar
mherman9918
Copper Contributor
Aug 26, 2025

hello i have tried your steps with no success.

 

i see the same problem and error codes when trying to change the PIN on a yubikey biometric FIDO2 security key. i see this issue on domain and non-domain joined devices so GPO is not at play.

  • RGU35's avatar
    RGU35
    Copper Contributor
    Sep 02, 2025

    Microsoft a publié en preview le patch:

    2025-08 Aperçu de la mise à jour cumulative pour Windows 11 Version 24H2 pour les systèmes x64 (KB5064081) (26100.5074)

     

    Ce patch permet côté sécurité, à Windows Hello de se doter d’une interface modernisée pour une connexion plus fluide et une meilleure intégration des clés d’accès et options biométriques.

    Ce correctif, permet entre autre de résoudre la défaillance constaté avec la gestion des clés de sécurité Yubikey FIDO2 de YUBICO

     

    Lien vers le patch msu à installer:

    https://catalog.sf.dl.delivery.mp.microsoft.com/filestreamingservice/files/b986f1b3-b24f-4302-85d4-baa913ed3a26/public/windows11.0-kb5064081-x64_a1096145ded3adfc26f8f23442281533429f0e38.msu

    (SHA1: oQlhRd7Trfwm+PI0QigVM0KfDjg=) (SHA256: xL16/AeD7N1dQ4hqkJSPO17NCz8Y/PAKZ9FX5E/UJEA=)

     

    le patch msu est accessible uniquement que depuis le catalogue Microsoft

     

    le fichier windows11.0-kb5064081-x64_a1096145ded3adfc26f8f23442281533429f0e38.msu est a installer sur le poste, et doit être redémarré pour que les modifications soient prises en compte

     

  • RGU35's avatar
    RGU35
    Copper Contributor
    Sep 02, 2025

    Hi, 

    Microsoft has published on 2025/08/29 the latest preview of this KB5064081 msu patch only distributed by Microsoft Catalog Portal:

    Example for my:

    2025-08 Cumulative update overview for Windows 11 Version 24H2 for x64 systems (KB5064081) (26100.5074)
    ​
    This patch allows on the security side, Windows Hello to have a modernized interface for a smoother connection and better integration of access keys and biometric options.
    This fix, among other things, allows to resolve the observed failure with the management of Yubikey FIDO2 security keys from YUBICO

    Reboot needed to apply modifications

     

    For my case, and for x64 platform, (be carreful: 2 files exists), only this file had been installed successfull:

    https://catalog.sf.dl.delivery.mp.microsoft.com/filestreamingservice/files/b986f1b3-b24f-4302-85d4-baa913ed3a26/public/windows11.0-kb5064081-x64_a1096145ded3adfc26f8f23442281533429f0e38.msu

    (SHA1: oQlhRd7Trfwm+PI0QigVM0KfDjg=) (SHA256: xL16/AeD7N1dQ4hqkJSPO17NCz8Y/PAKZ9FX5E/UJEA=)

     

    Best regards

Resources