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:      Application
Source:        Application Error
Date:          25.08.2025 9:09:22
Event ID:      1000
Task Category: Application Crashing Events
Level:         Error
Description:
Faulting application name: BioEnrollmentHost.exe, version: 10.0.26100.4484, time stamp: 0x3a2c5e36
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.26100.4946, time stamp: 0x4374ba0f
Exception code: 0xc000027b
Fault offset: 0x0000000000903d13
Faulting process id: 0x3B10
Faulting application start time: 0x1DC158F2982572A
Faulting application path: C:\Windows\SystemApps\Microsoft.BioEnrollment_cw5n1h2txyewy\BioEnrollmentHost.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: da35663e-a5e8-4638-b202-5afed9fd901c
Faulting package full name: Microsoft.BioEnrollment_10.0.19587.1000_neutral__cw5n1h2txyewy
Faulting package-relative application ID: App

 

There is no problem with OS integrity >

 

PS C:\WINDOWS\system32> DISM.exe /Online /Cleanup-image /Scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.26100.1150

Image Version: 10.0.26100.4946

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.
PS C:\WINDOWS\system32>
PS C:\WINDOWS\system32> DISM.exe /Online /Cleanup-image /Restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.26100.1150

Image Version: 10.0.26100.4946

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
PS C:\WINDOWS\system32>
PS C:\WINDOWS\system32> sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
PS C:\WINDOWS\system32> chkdsk c: /scan /perf
The type of the file system is NTFS.

...

Windows has scanned the file system and found no problems.
No further action is required.

...
PS C:\WINDOWS\system32>
PS C:\WINDOWS\system32> systeminfo | findstr /B /C:"OS Name" /B /C:"OS Version"
OS Name:                       Microsoft Windows 11 Enterprise LTSC
OS Version:                    10.0.26100 N/A Build 26100
PS C:\WINDOWS\system32>

 

Any ideas?

 

Account Management
Authentication
Error
windows 11

4 Replies

  • 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

         

Resources