CryptNgc.dll
Associated Error Codes
Below lists error codes and symbolic names found for this module.
| Code | Found in | Description |
|---|---|---|
| 0x3000000a | 1011 | Start |
| 0x3000000b | 1011 | Stop |
| 0x3000000c | 1011 | Informational |
| 0x50000002 | 1011 | Error |
| 0x50000003 | 1011 | Warning |
| 0x50000004 | 1011 | Information |
| 0x50000010 | 1011 | Success |
| 0x70000006 | 1011 | Service Start |
| 0x70000007 | 1011 | Container Load |
| 0x70000008 | 1011 | Container Creation |
| 0x70000009 | 1011 | Key Creation |
| 0x7000000a | 1011 | Key Deletion |
| 0x7000000b | 1011 | Certificate Enrollment |
| 0x7000000c | 1011 | Prerequisites Check |
| 0x7000000d | 1011 | Key Registration |
| 0x7000000e | 1011 | PIN Recovery |
| 0x7000000f | 10 | Device Unlock |
| 0x70000010 | 1011 | Hello Provisioning |
| 0x70000011 | 1011 | Key Use |
| 0x70000012 | 1011 | BiometricEnrollment |
| 0x70000013 | 1011 | Container Deletion |
| 0x70000014 | 1011 | Query Policy |
| 0x70000015 | 10 | Key Update |
| 0x90000001 | 1011 | Microsoft-Windows-HelloForBusiness |
| 0xb0000be5 | 1011 | Windows Hello processing started. Scenario type: %1 |
| 0xb0000bec | 1011 | The key pre-generation pool received a request for a new key. |
| 0xb0000bed | 1011 | The key pre-generation pool needs to pre-generate a key. |
| 0xb0000bee | 1011 | Windows Hello for Business prerequisites check started. |
| 0xb0000bef | 1011 | Windows Hello container provisioning started. |
| 0xb0000bf4 | 1011 | Windows Hello is creating a PIN recovery key for user %1. |
| 0xb0000bf9 | 1011 | The cloud experience host started. Scenario type: %1 |
| 0xb0000bfa | 1011 | Windows Hello sign-in certificate enrollment started. |
| 0xb0000c3a | 1011 | Windows Hello PIN Recovery is attempting to change user's PIN. PIN recovery type: %1. |
| 0xb0000c99 | 1011 | Windows Hello key creation started. |
| 0xb0000db6 | 1011 | Windows Hello key registration started. |
| 0xb0000dc0 | 10 | Attempting device unlock using provider %1. The list of acceptable providers are: Group A: %2 Group B: %3 |
| 0xb0000dc5 | 1011 | AD/Azure AD plugin request started. |
| 0xb0000de3 | 1011 | Windows Hello container creation started. |
| 0xb0000e11 | 1011 | Windows Hello container deletion started in response to a policy change. |
| 0xb0000e1b | 10 | Windows Hello container deletion started. |
| 0xb0001388 | 10 | TPM Manufacturer: %1 Version: %2 Status: %3 |
| 0xb0001389 | 10 | The current user signed in to the computer using %1 |
| 0xb00013ba | 1011 | The key pre-generation pool received a request. Result: %1 Number of available keys: %2 Elapsed time: %3 seconds |
| 0xb00013c4 | 1011 | Windows Hello is checking the PIN recovery policy. The policy is %1 for user %2. |
| 0xb00013c5 | 1011 | Windows Hello is downloading the public encryption key from the PIN recovery service. |
| 0xb00013c6 | 1011 | Windows Hello found a PIN recovery key for user %1. |
| 0xb00013c7 | 1011 | Windows Hello is updating the PIN recovery key for user %1. |
| 0xb00013c8 | 1011 | Windows Hello is uploading the encrypted PIN recovery key to the PIN recovery service. |
| 0xb0001454 | 1011 | Windows Hello for Business certificate enrollment configurations: Certificate Enrollment Method: %1 Certificate Required for On-Premise Auth: %2 |
| 0xb0001455 | 1011 | Windows Hello for Business On-Premise authentication configurations: Certificate Enrollment Method: %1 Certificate Required for On-Premise Auth: %2 Use Cloud Trust for On-Premise Auth: %3 Account has Cloud TGT: %4 |
| 0xb0001469 | 1011 | Creating a %1 Windows Hello key with result %2. |
| 0xb0001590 | 10 | Device unlock policy is not configured on this device. |
| 0xb00015b3 | 1011 | Windows Hello is validating that the device can satisfy all applicable policies. TPM Supported: %1 Hardware Policy: %2 Exclude TPM 1.2: %3 TPM Version: %4 TPM FIPS: %5 TPM Locked Out: %6 Satisfactory Key Pregeneration Pool: %7 Key Storage Provider: %8 Result: %9 |
| 0xb00015e1 | 1011 | Windows Hello detected and ignored a policy change to delete the container at the user's next sign out because the user is configured to have no password on this device. |
| 0xb00015e2 | 1011 | Windows Hello was unable to check if there was a policy change that would trigger container deletion. |
| 0xb0001609 | 1011 | Windows Hello successfully updated a %1 %2 key from the Windows Hello container. Key Name: %3 |
| 0xb000177a | 1011 | A key credential was unavailable for use by an application because it did not meet all the requirements for use. Key name: %1 Reason: %2 |
| 0xb000179d | 1011 | Windows Hello processing stopped with warning %1. Processing time: %2 seconds |
| 0xb00017a7 | 1011 | Windows Hello container provisioning stopped with warning %1. Processing time: %2 seconds |
| 0xb00017b1 | 1011 | The cloud experience host scenario stopped with warning %1. Processing time: %2 seconds |
| 0xb00017b2 | 1011 | Windows Hello sign-in certificate enrollment was unable to enroll for a logon certificate. Automatic certificate enrollment will retry at regular intervals. Error: %1 Processing time: %2 seconds |
| 0xb0001841 | 1011 | Windows Hello for Business was unable to evaluate the presence of a certificate payload for the sign-in certificate. |
| 0xb0001842 | 1011 | Windows Hello for Business was unable to detect whether the user is running in a remote desktop session. |
| 0xb0001929 | 1011 | Windows Hello for Business certificate trust and cloud trust policies are both enabled. Certificate trust policy will be enforced. |
| 0xb0001978 | 1011 | Provider is not in the acceptable provider list. |
| 0xb000197d | 1011 | AD/Azure AD plugin request stopped with warning %1. Processing time: %2 seconds |
| 0xb00019d3 | 1011 | Windows Hello could not delete the container as no container currently exists for the user. |
| 0xb0001b5a | 1011 | Failed to load an existing Windows Hello container. ID: %1 Error: %2 |
| 0xb0001b71 | 1011 | The %1 service failed to start. Error: %2. |
| 0xb0001b76 | 1011 | Windows Hello failed to create the sign-in certificate request. Error: %1 |
| 0xb0001b77 | 1011 | Windows Hello failed to install the sign-in certificate. Error: %1 |
| 0xb0001b78 | 1011 | Windows Hello failed to roll back from an unsuccessful sign-in certificate enrollment. Error: %1 |
| 0xb0001b85 | 1011 | Windows Hello processing failed with %1. Processing time: %2 seconds |
| 0xb0001b8c | 1011 | The new key request from the key pre-generation pool failed. Error: %1 Processing time: %2 seconds. |
| 0xb0001b8d | 1011 | The key pre-generation pool failed to pre-generate a key. Error: %1 Processing time: %2 seconds. |
| 0xb0001b8e | 1011 | Windows Hello for Business prerequisites check failed. Error: %1 |
| 0xb0001b8f | 1011 | Windows Hello container provisioning failed with %1. Processing time: %2 seconds |
| 0xb0001b94 | 1011 | Windows Hello failed to create a PIN recovery key for user %1. Error: %2 (%3) Correlation vector: %4 Processing time: %5 seconds. |
| 0xb0001b99 | 1011 | The cloud experience host scenario failed with %1. Processing time: %2 seconds |
| 0xb0001b9a | 1011 | Windows Hello sign-in certificate enrollment failed. Error: %1 Processing time: %2 seconds |
| 0xb0001b9b | 1011 | Windows Hello failed to set a certificate property on a Windows Hello key. Error: %1 Key name: %2 Certificate type: %3 |
| 0xb0001bda | 1011 | Windows Hello PIN Recovery failed to change the user's PIN. Error: %1 (%2) Correlation vector: %3 Processing time: %4 seconds. |
| 0xb0001c20 | 1011 | The device registration prerequisite check failed. |
| 0xb0001c21 | 1011 | The Primary Account Primary Refresh Token prerequisite check failed. |
| 0xb0001c22 | 1011 | The device failed to meet the Windows Hello for Business hardware requirements. |
| 0xb0001c23 | 1011 | Windows Hello for Business is not enabled. |
| 0xb0001c24 | 1011 | Windows Hello for Business post-logon provisioning is not enabled. |
| 0xb0001c25 | 1011 | Windows Hello for Business failed to locate a usable sign-in certificate template. Error: %1 |
| 0xb0001c26 | 1011 | Windows Hello for Business failed to locate a certificate registration authority. |
| 0xb0001c27 | 1011 | Windows Hello for Business failed to locate an enterprise management client. |
| 0xb0001c28 | 1011 | Windows Hello for Business failed to locate a sign-in certificate profile. |
| 0xb0001c29 | 1011 | Windows Hello for Business failed to locate a certificate payload for the sign-in certificate. The SCEP Request is not available. |
| 0xb0001c2a | 1011 | Windows Hello for Business detected the user running in a remote desktop session. |
| 0xb0001c2b | 1011 | The Secondary Account Primary Refresh Token prerequisite check failed. |
| 0xb0001c39 | 1011 | Windows Hello key creation failed with %1. Processing time: %2 seconds |
| 0xb0001c3a | 1011 | Windows Hello failed to delete the %1 key. Key Name: %2 Error: %3 |
| 0xb0001d56 | 1011 | Windows Hello key registration failed. Error: %1 |
| 0xb0001d60 | 1011 | Failed to authenticate the user's credential. Error: %1 (%2) Correlation vector: %3 Processing time: %4 milliseconds. |
| 0xb0001d65 | 1011 | AD/Azure AD plugin request failed with %1. Processing time: %2 seconds |
| 0xb0001d83 | 1011 | Windows Hello container creation failed. Error: %1 Processing time: %2 seconds |
| 0xb0001db1 | 1011 | Windows Hello failed to delete the container in response to a policy change. Error: %1 Processing time: %2 milliseconds. |
| 0xb0001dbb | 1011 | Windows Hello failed to delete the container. Error: %1. |
| 0xb0001dc5 | 1011 | Windows Hello failed to delete the user's Windows Hello certificates. Error: %1. |
| 0xb0001dcf | 1011 | Windows Hello failed to delete the user's biometric enrollments. Error: %1. |
| 0xb0001f42 | 1011 | Successfully loaded an existing %3 Windows Hello container. ID: %1 Version: %2 Has Cached Logon Key: %4 State: %5 |
| 0xb0001f59 | 1011 | The %1 service started successfully. |
| 0xb0001f5e | 1011 | Windows Hello created the sign-in certificate request successfully. |
| 0xb0001f5f | 1011 | Windows Hello installed the sign-in certificate successfully. |
| 0xb0001f60 | 1011 | Windows Hello successfully rolled back from an unsuccessful sign-in certificate enrollment. |
| 0xb0001f6d | 1011 | Windows Hello processing completed successfully. Processing time: %1 seconds |
| 0xb0001f74 | 1011 | The new key request from the key pre-generation pool completed successfully. Processing time: %1 seconds. |
| 0xb0001f75 | 1011 | The key pre-generation pool successfully pre-generated a key. Processing time: %1 seconds. |
| 0xb0001f76 | 1011 | Windows Hello for Business prerequisites check completed successfully. |
| 0xb0001f77 | 1011 | Windows Hello container provisioning completed successfully. Processing time: %1 seconds Existing container: %2 |
| 0xb0001f7c | 1011 | Windows Hello successfully created a PIN recovery key for user %1. Processing time: %2 seconds |
| 0xb0001f81 | 1011 | The cloud experience host completed successfully. Processing time: %1 seconds |
| 0xb0001f82 | 1011 | Windows Hello sign-in certificate enrollment completed successfully. Processing time: %1 seconds |
| 0xb0001f83 | 1011 | Windows Hello set a certificate property on a Windows Hello key. Key name: %1 Certificate type: %2 |
| 0xb0001fc2 | 1011 | Windows Hello PIN Recovery successfully changed the user's PIN. Processing time: %1 seconds. |
| 0xb0002008 | 1011 | The device registration prerequisite check completed successfully. |
| 0xb0002009 | 1011 | The Primary Account Primary Refresh Token prerequisite check completed successfully. |
| 0xb000200a | 1011 | The device meets Windows Hello for Business hardware requirements. |
| 0xb000200b | 1011 | Windows Hello for Business is enabled. |
| 0xb000200c | 1011 | Windows Hello for Business post-logon provisioning is enabled. |
| 0xb000200d | 1011 | Windows Hello for Business successfully located a usable sign-on certificate template. |
| 0xb000200e | 1011 | Windows Hello for Business successfully located a certificate registration authority. |
| 0xb000200f | 1011 | Windows Hello for Business successfully located an enterprise management client. |
| 0xb0002010 | 1011 | Windows Hello for Business successfully located a sign-in certificate profile. |
| 0xb0002011 | 1011 | Windows Hello for Business successfully located a certificate payload for the sign-in certificate. The SCEP Request is available. |
| 0xb0002012 | 1011 | Windows Hello for Business successfully completed the remote desktop prerequisite check. |
| 0xb0002013 | 1011 | The Secondary Account Primary Refresh Token prerequisite check completed successfully. |
| 0xb0002021 | 1011 | Windows Hello key creation completed successfully. Processing time: %1 seconds |
| 0xb0002022 | 1011 | Windows Hello successfully deleted a %1 %2 key from the Windows Hello container. Key Name: %3 |
| 0xb000213e | 1011 | Windows Hello key registration completed successfully. |
| 0xb0002148 | 1011 | Successfully authenticated the user's credential. Processing time: %1 milliseconds. |
| 0xb000214d | 1011 | AD/Azure AD plugin request completed successfully. Processing time: %1 seconds |
| 0xb000216b | 1011 | The Windows Hello container creation completed successfully. Processing time: %1 seconds |
| 0xb0002199 | 1011 | Windows Hello successfully deleted the container in response to a policy change. Processing time: %1 milliseconds. |
| 0xb00021a3 | 1011 | Windows Hello successfully deleted the container. |
| 0xb00021ad | 1011 | Windows Hello successfully deleted the user's Windows Hello certificates. |
| 0xb00021b7 | 1011 | Windows Hello successfully deleted the user's biometric enrollments. |
| 0xd0000001 | 1011 | No TPM |
| 0xd0000002 | 1011 | TPM 1.2 |
| 0xd0000003 | 1011 | TPM 2.0 |
| 0xd0000004 | 10 | Password |
| 0xd0000005 | 10 | Pin |
| 0xd0000006 | 10 | Biometric |
| 0xd0000007 | 10 | Other |
| 0xd0000008 | 10 | hardware |
| 0xd0000009 | 10 | software |
| 0xd000000a | 10 | Default Decryption |
| 0xd000000b | 10 | Cached Logon |
| 0xd000000c | 10 | User ID |
| 0xd000000d | 10 | Key-trust |
| 0xd000000e | 10 | Certificate-trust |
| 0xd000000f | 10 | None |
| 0xd0000010 | 10 | MDM |
| 0xd0000011 | 10 | RA |
| 0xd0000012 | 10 | Self-service |
| 0xd0000013 | 10 | Remote |
| 0xd0000014 | 10 | Destructive |
| 0xd0000015 | 10 | Non-destructive |
| 0xd0000016 | 10 | Force Software |
| 0xd0000017 | 10 | Any TPM |
| 0xd0000018 | 10 | TPM 2.0 or Software |
| 0xd0000019 | 10 | Hardware Preferred |
| 0xd000001a | 10 | Hardware Required |
| 0xd000001b | 10 | Uninitialized |
| 0xd000001c | 10 | Unloaded |
| 0xd000001d | 10 | Okay |
| 0xd000001e | 10 | Unknown Failure |
| 0xd000001f | 10 | TPM Cleared |
| 0xd0000020 | 10 | TPM Unavailable |
| 0xd0000021 | 10 | VSM Unavailable |
| 0xd0000022 | 10 | Self-signed |
| 0xd0000023 | 10 | CA signed |
| 0xd0000024 | 10 | Unknown |
| 0xd0000025 | 10 | disabled |
| 0xd0000026 | 10 | enabled |
| 0xd0000027 | 10 | Enrollment |
| 0xd0000028 | 10 | Reset |
| 0xd0000029 | 10 | Fix Me |
| 0xd000002a | 10 | Smart card emulation is disabled. |
| 0xd000002b | 10 | The certificate is unavailable. |
| 0xd000002c | 10 | The certificate is self-signed. |
| 0xd000002d | 10 | The certificate is expired or not yet valid. |
| 0xd000002e | 10 | The certificate does not contain required key use properties. |
| 0xd000002f | 10 | The certificate information could not be validated. |
| 0x7000000f | 11 | Multi-Factor Unlock |
| 0x70000015 | 11 | Windows Hello Username/SID Cache |
| 0x70000016 | 11 | PIN Change |
| 0x70000017 | 11 | Policy Enforcement |
| 0x70000018 | 11 | Key Update |
| 0x70000019 | 11 | Protector Use |
| 0x7000001a | 11 | Protector Disk IO |
| 0xb0000dc0 | 11 | Attempting multi-factor unlock using provider %1. The list of acceptable providers are: Group A: %2 Group B: %3 |
| 0xb0000e1b | 11 | Windows Hello container deletion started from %1. |
| 0xb0001388 | 11 | TPM Manufacturer: %1 Version: %2 Firmware Version: %3 Is Ready: %4 |
| 0xb0001389 | 11 | A user signed into the device with the following information: Username: %1 User SID: %2 Credential Type: %3 Deployment Type: %4 |
| 0xb000138a | 11 | A user is signing into the device with the following gesture information: Type: %1 Subtype: %2 |
| 0xb000138b | 11 | Windows Hello for Business Policy Enforcement Information for the user %1: Use Windows Hello for Business Policy State: %2 Use Windows Hello for Business Policy Source: %3 Deployment Type: %4 Credential Type: %5 PIN Min Length: %6 PIN Max Length: %7 PIN Uppercase: %8 PIN Lowercase: %9 PIN Digits: %10 PIN Special Characters: %11 PIN Allow Sequences: %12 PIN History: %13 PIN Expiration: %14 PIN Recovery Policy State: %15 TPM Required: %16 Hardware Policy: %17 Multifactor Unlock: %18 |
| 0xb000138c | 11 | Windows Hello for Business Enabled Policy successfully enforced for the user %1: Use Windows Hello for Business Policy State: %2 |
| 0xb000138d | 11 | Enforcing the following Windows Hello for Business Enable Policies for the user %1: Use Windows Hello for Business Policy State: %2 Use Windows Hello for Business Policy Source: %3 Deployment Type: %4 |
| 0xb0001392 | 11 | Hello unlock factor used. User: %1 Is Unlock: %2 PIN enrolled: %3 Face enrolled: %4 Fingerprint enrolled: %5 Factor used: %6 ESS modality used: %7 Result: %8 |
| 0xb0001590 | 11 | Multi-factor unlock policy is not configured on this device. |
| 0xb0001645 | 11 | Windows Hello read following protector properties from disk: HResult = %1, PIN protector = %2, Bio protector = %3, Secure Bio Protector = %4, Recovery protector = %5, Preboot protector = %6 |
| 0xb0001646 | 11 | Windows Hello wrote following protector properties to disk: HResult = %1, PIN protector = %2, Bio protector = %3, Secure Bio Protector = %4, Recovery protector = %5, Preboot protector = %6 |
| 0xb0001b59 | 11 | A user failed to sign into the device with the following information: Username: %1 User SID: %2 Credential Type: %3 Deployment Type: %4 Software Lockout Counter: %5 Authentication Error Status: %6 Authentication Error Substatus: %7 |
| 0xb0001b62 | 11 | Hello unlock factor used (failure). User: %1 Is Unlock: %2 PIN enrolled: %3 Face enrolled: %4 Fingerprint enrolled: %5 Factor used: %6 ESS modality used: %7 Result: %8 |
| 0xb0001e15 | 11 | Windows Hello failed to use secure biometrics protector due to secret encryption key loss. |
| 0xb00021b8 | 11 | Windows Hello for Business successfully added a user entry to the Username/SID cache with the following information: Username: %1 User SID: %2 Domain: %3 User-Entered: %4 |
| 0xb00021b9 | 11 | Windows Hello for Business successfully removed a user entry to the Username/SID cache with the following information: User SID: %1 |
| 0xb00021ba | 11 | Windows Hello for Business found a user entry with a duplicate SID and successfully removed the unused username from the Username/SID cache: User SID: %1 Username: %2 Unused Username: %3 |
| 0xb00021bb | 11 | Windows Hello for Business found a user entry with a duplicate username and successfully removed the unused SID from the Username/SID cache: Username: %1 User SID: %2 Unused User SID: %3 |
| 0xb00021bc | 11 | Windows Hello for Business found a stale SID in the Username/SID cache: Username: %1 User SID: %2 Stale User SID: %3 |
| 0xb00021bd | 11 | Windows Hello for Business found a stale username in the Username/SID cache: User SID: %1 Username: %2 Stale Username: %3 |
| 0xb00021be | 11 | Windows Hello for Business removed a stale SID from the Username/SID cache: Stale User SID: %1 |
| 0xb00021bf | 11 | Windows Hello for Business removed a stale username from the Username/SID cache: User SID: %1 Stale Username: %2 |
| 0xb00021c0 | 11 | Windows Hello for Business PIN was changed by a user with the following information: User SID: %1 |
| 0xd0000004 | 11 | No logon cred |
| 0xd0000005 | 11 | Software Key |
| 0xd0000006 | 11 | Hardware Key |
| 0xd0000007 | 11 | Password Stuffer |
| 0xd0000008 | 11 | Hello ISO |
| 0xd0000009 | 11 | Key Trust |
| 0xd000000a | 11 | Certificate Trust |
| 0xd000000b | 11 | Cloud Trust |
| 0xd000000c | 11 | Invalid |
| 0xd000000d | 11 | PIN |
| 0xd000000e | 11 | Biometrics |
| 0xd000000f | 11 | Preboot |
| 0xd0000010 | 11 | CompanionDevice |
| 0xd0000011 | 11 | Recovery |
| 0xd0000012 | 11 | AuthTicket |
| 0xd0000013 | 11 | No Bio |
| 0xd0000014 | 11 | Face |
| 0xd0000015 | 11 | Fingerprint |
| 0xd0000016 | 11 | Iris |
| 0xd0000017 | 11 | hardware |
| 0xd0000018 | 11 | software |
| 0xd0000019 | 11 | Default Decryption |
| 0xd000001a | 11 | Cached Logon |
| 0xd000001b | 11 | User ID |
| 0xd000001c | 11 | None |
| 0xd000001d | 11 | MDM |
| 0xd000001e | 11 | RA |
| 0xd000001f | 11 | Self-service |
| 0xd0000020 | 11 | Remote |
| 0xd0000021 | 11 | Destructive |
| 0xd0000022 | 11 | Non-destructive |
| 0xd0000023 | 11 | Force Software |
| 0xd0000024 | 11 | Any TPM |
| 0xd0000025 | 11 | TPM 2.0 or Software |
| 0xd0000026 | 11 | Hardware Preferred |
| 0xd0000027 | 11 | Hardware Required |
| 0xd0000028 | 11 | Uninitialized |
| 0xd0000029 | 11 | Unloaded |
| 0xd000002a | 11 | Okay |
| 0xd000002b | 11 | Unknown Failure |
| 0xd000002c | 11 | TPM Cleared |
| 0xd000002d | 11 | TPM Unavailable |
| 0xd000002e | 11 | VSM Unavailable |
| 0xd000002f | 11 | Self-signed |
| 0xd0000030 | 11 | CA signed |
| 0xd0000031 | 11 | Unknown |
| 0xd0000032 | 11 | disabled |
| 0xd0000033 | 11 | enabled |
| 0xd0000034 | 11 | Enrollment |
| 0xd0000035 | 11 | Reset |
| 0xd0000036 | 11 | Fix Me |
| 0xd0000037 | 11 | Smart card emulation is disabled. |
| 0xd0000038 | 11 | The certificate is unavailable. |
| 0xd0000039 | 11 | The certificate is self-signed. |
| 0xd000003a | 11 | The certificate is expired or not yet valid. |
| 0xd000003b | 11 | The certificate does not contain required key use properties. |
| 0xd000003c | 11 | The certificate information could not be validated. |
| 0xd000003d | 11 | Ngc Policy Disabled |
| 0xd000003e | 11 | Ngc Policy Enabled |
| 0xd000003f | 11 | Ngc Policy Not Configured |
| 0xd0000040 | 11 | Policy Not Configured |
| 0xd0000041 | 11 | Group Policy Source |
| 0xd0000042 | 11 | MDM Policy Source |
| 0xd0000043 | 11 | Convenient PIN |
| 0xd0000044 | 11 | Allowed |
| 0xd0000045 | 11 | Required At Least One |
| 0xd0000046 | 11 | Disallowed |
| 0xd0000047 | 11 | PIN |
| 0xd0000048 | 11 | Face |
| 0xd0000049 | 11 | Fingerprint |
| 289 entries | ||