Forum Discussion

Laurie_Aldam's avatar
Laurie_Aldam
Brass Contributor
Jul 21, 2025
Solved

Windows Hello for Business 0x80090010 NTE_PERM

Hi all, I'm encountering an issue with Windows Hello for Business on the latest version of Windows (July 2025 update). The setup process fails during initialisation, and no biometric or PIN options ...
Authentication
Identity
Modern authentication
multi-factor authentication
  • Matthew Miles's avatar
    Matthew Miles
    Jul 30, 2025

    Microsoft has a service health bulletin for this issue now - https://admin.cloud.microsoft/?#/windowsreleasehealth/knownissues/:/issue/WI1121302

Barg308's avatar
Barg308
Copper Contributor
Jul 29, 2025

I ran into the same issue today while enrolling a client running the latest July 2025 update.

To investigate further, I tested the scenario in my lab with two VMs configured identically. Both used the same Windows Hello for Business deployment via OMA-URI settings:

./Device/Vendor/MSFT/PassportForWork/Biometrics/UseBiometrics,true ./Device/Vendor/MSFT/PassportForWork/Biometrics/FacialFeaturesUseEnhancedAntiSpoofing,true ./Device/Vendor/MSFT/PassportForWork/Biometrics/EnableESSwithSupportedPeripherals,1 ./Device/Vendor/MSFT/PassportForWork/SecurityKey/UseSecurityKeyForSignin,1 ./Device/Vendor/MSFT/PassportForWork/{TenantId}/Policies/DisablePostLogonProvisioning,true ./Device/Vendor/MSFT/PassportForWork/{TenantId}/Policies/UseCloudTrustForOnPremAuth,true ./Device/Vendor/MSFT/PassportForWork/{TenantId}/Policies/Remote/UseRemotePassport,true ./User/Vendor/MSFT/PassportForWork/{TenantId}/Policies/UsePassportForWork,true ./User/Vendor/MSFT/PassportForWork/{TenantId}/Policies/RequireSecurityDevice,true ./User/Vendor/MSFT/PassportForWork/{TenantId}/Policies/PINComplexity/SpecialCharacters,2 ./User/Vendor/MSFT/PassportForWork/{TenantId}/Policies/PINComplexity/UppercaseLetters,2 ./User/Vendor/MSFT/PassportForWork/{TenantId}/Policies/PINComplexity/LowercaseLetters,2

One VM had the June 24H2 update, the other the July 24H2 update.

Here’s what I observed:

- On the July update, error 0x80090010 occurred when attempting to register Windows Hello for Business.
- On the June update, registration completed successfully without any issues.

I also tested the workaround shared by Matthew Miles and can confirm that it works.

What I did:

1. Applied the suggested registry change.
2. Registered the WHfB PIN successfully.
3. Deleted the registry key afterward.

Even after a reboot, Windows Hello remained functional. It’s not an ideal fix, but it works for now. Hopefully, Microsoft addresses this properly in the next update.

Resources