Mini Kabibi Habibi

Current Path : C:/Windows/System32/en-US/

Current File : C:/Windows/System32/en-US/CryptNgc.dll.mui

MZ����@��� �!�L�!This program cannot be run in DOS mode.

$5�<�q�R�q�R�q�R�e���p�R�e�P�p�R�Richq�R�PEL�!h

�z�@ le8.rdata�@@.rsrcp f@@��L�
T88��L�$��8.rdata8x.rdata$zzzdbg @.rsrc$01@!@d.rsrc$02 ����
��2�Y�{4�?�!���"�&`�ޘ�L�0�0�H�`�x��������� � 8!���!B�4"�_�ā��MUI����dn/Ѻ�������}FϘ9/!��%� h
���MUIen-US%1!s! says: %2!s!PAH
00dPP�PP�pp������������d����@ ����� :�:��
����X�
��
���
��
��
��
���
��
�0
���
��(���������X����HT�U�Pi�i�H���������(����T � ��z�z�P����t���������A�B�,!)�)��"x�x�$}�}�|$����(%Z�Z��%q�q��&v�x��&�����(����t)����T,����h-�����/ �+��09�:��8V�V��9`�`� :e�e�;�����;����`<����d=�����=�����>B�B�<?Y�Y�4@^�`��@m�m�\Bt�w�C|�|�(F�����F����<I � �J! �" ��Q>!�>!�hSH!�H!��SM!�M!��Tk!�k!�<U�!��!��U�!��!��V�!��!�XW�!��!��W�/ЈXStart

Stop

$Informational

Error

Warning

Information

Success

$Service Start

(Container Load

0Container Creation

$Key Creation

$Key Deletion

8Certificate Enrollment

0Prerequisites Check

,Key Registration

$PIN Recovery

$Device Unlock

0Hello Provisioning

Key Use

0BiometricEnrollment

0Container Deletion

$Query Policy

Key Update

PMicrosoft-Windows-HelloForBusiness

tWindows Hello processing started.%nScenario type: %1

�The key pre-generation pool received a request for a new key.

|The key pre-generation pool needs to pre-generate a key.

xWindows Hello for Business prerequisites check started.

dWindows Hello container provisioning started.

|Windows Hello is creating a PIN recovery key for user %1.

tThe cloud experience host started.%nScenario type: %1

tWindows Hello sign-in certificate enrollment started.

�Windows Hello PIN Recovery is attempting to change user's PIN. PIN recovery type: %1.

PWindows Hello key creation started.

XWindows Hello key registration started.

�Attempting device unlock using provider %1. The list of acceptable providers are:%nGroup A: %2%nGroup B: %3

PAD/Azure AD plugin request started.

\Windows Hello container creation started.

�Windows Hello container deletion started in response to a policy change.

\Windows Hello container deletion started.

dTPM Manufacturer: %1%nVersion: %2%nStatus: %3

pThe current user signed in to the computer using %1

�The key pre-generation pool received a request.%nResult: %1%nNumber of available keys: %2%nElapsed time: %3 seconds

�Windows Hello is checking the PIN recovery policy. The policy is %1 for user %2.

�Windows Hello is downloading the public encryption key from the PIN recovery service.

pWindows Hello found a PIN recovery key for user %1.

�Windows Hello is updating the PIN recovery key for user %1.

�Windows Hello is uploading the encrypted PIN recovery key to the PIN recovery service.

4Windows Hello for Business certificate enrollment configurations: %n%nCertificate Enrollment Method: %1%nCertificate Required for On-Premise Auth: %2

�Windows Hello for Business On-Premise authentication configurations: %n%nCertificate Enrollment Method: %1%nCertificate Required for On-Premise Auth: %2%nUse Cloud Trust for On-Premise Auth: %3%nAccount has Cloud TGT: %4

hCreating a %1 Windows Hello key with result %2.

xDevice unlock policy is not configured on this device.

,Windows Hello is validating that the device can satisfy all applicable policies.%n%nTPM Supported: %1%nHardware Policy: %2%nExclude TPM 1.2: %3%nTPM Version: %4%nTPM FIPS: %5%nTPM Locked Out: %6%nSatisfactory Key Pregeneration Pool: %7%nKey Storage Provider: %8%nResult: %9

\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.

�Windows Hello was unable to check if there was a policy change that would trigger container deletion.

�Windows Hello successfully updated a %1 %2 key from the Windows Hello container.%n%nKey Name: %3

$A key credential was unavailable for use by an application because it did not meet all the requirements for use.%n%nKey name: %1%nReason: %2

�Windows Hello processing stopped with warning %1.%nProcessing time: %2 seconds

�Windows Hello container provisioning stopped with warning %1.%nProcessing time: %2 seconds

�The cloud experience host scenario stopped with warning %1.%nProcessing time: %2 seconds

�Windows Hello sign-in certificate enrollment was unable to enroll for a logon certificate. Automatic certificate enrollment will retry at regular intervals.%nError: %1%nProcessing time: %2 seconds

�Windows Hello for Business was unable to evaluate the presence of a certificate payload for the sign-in certificate.

�Windows Hello for Business was unable to detect whether the user is running in a remote desktop session.

Windows Hello for Business certificate trust and cloud trust policies are both enabled.%n%nCertificate trust policy will be enforced.

lProvider is not in the acceptable provider list.

�AD/Azure AD plugin request stopped with warning %1.%nProcessing time: %2 seconds

�Windows Hello could not delete the container as no container currently exists for the user.

�Failed to load an existing Windows Hello container.%n%nID: %1%nError: %2

`The %1 service failed to start.%nError: %2.

�Windows Hello failed to create the sign-in certificate request.%nError: %1

�Windows Hello failed to install the sign-in certificate.%nError: %1

�Windows Hello failed to roll back from an unsuccessful sign-in certificate enrollment.%nError: %1

�Windows Hello processing failed with %1.%nProcessing time: %2 seconds

�The new key request from the key pre-generation pool failed.%nError: %1%nProcessing time: %2 seconds.

�The key pre-generation pool failed to pre-generate a key.%nError: %1%nProcessing time: %2 seconds.

�Windows Hello for Business prerequisites check failed.%n%nError: %1

�Windows Hello container provisioning failed with %1.%nProcessing time: %2 seconds

Windows Hello failed to create a PIN recovery key for user %1.%nError: %2 (%3)%nCorrelation vector: %4%nProcessing time: %5 seconds.

�The cloud experience host scenario failed with %1.%nProcessing time: %2 seconds

�Windows Hello sign-in certificate enrollment failed.%nError: %1%nProcessing time: %2 seconds

Windows Hello failed to set a certificate property on a Windows Hello key.%n%nError: %1%nKey name: %2%nCertificate type: %3

Windows Hello PIN Recovery failed to change the user's PIN.%nError: %1 (%2)%nCorrelation vector: %3%nProcessing time: %4 seconds.

pThe device registration prerequisite check failed.

�The Primary Account Primary Refresh Token prerequisite check failed.

�The device failed to meet the Windows Hello for Business hardware requirements.

`Windows Hello for Business is not enabled.

�Windows Hello for Business post-logon provisioning is not enabled.

�Windows Hello for Business failed to locate a usable sign-in certificate template.%n%nError: %1

�Windows Hello for Business failed to locate a certificate registration authority.

�Windows Hello for Business failed to locate an enterprise management client.

�Windows Hello for Business failed to locate a sign-in certificate profile.

Windows Hello for Business failed to locate a certificate payload for the sign-in certificate. The SCEP Request is not available.

�Windows Hello for Business detected the user running in a remote desktop session.

�The Secondary Account Primary Refresh Token prerequisite check failed.

�Windows Hello key creation failed with %1.%nProcessing time: %2 seconds

�Windows Hello failed to delete the %1 key.%n%nKey Name: %2%nError: %3

pWindows Hello key registration failed.%n%nError: %1

�Failed to authenticate the user's credential.%nError: %1 (%2)%nCorrelation vector: %3%nProcessing time: %4 milliseconds.

�AD/Azure AD plugin request failed with %1.%nProcessing time: %2 seconds

�Windows Hello container creation failed.%nError: %1%nProcessing time: %2 seconds

Windows Hello failed to delete the container in response to a policy change.%n%nError: %1%nProcessing time: %2 milliseconds.

�Windows Hello failed to delete the container.%n%nError: %1.

�Windows Hello failed to delete the user's Windows Hello certificates.%n%nError: %1.

�Windows Hello failed to delete the user's biometric enrollments.%n%nError: %1.

�Successfully loaded an existing %3 Windows Hello container.%n%nID: %1%nVersion: %2%nHas Cached Logon Key: %4%nState: %5

TThe %1 service started successfully.

�Windows Hello created the sign-in certificate request successfully.

�Windows Hello installed the sign-in certificate successfully.

�Windows Hello successfully rolled back from an unsuccessful sign-in certificate enrollment.

�Windows Hello processing completed successfully.%nProcessing time: %1 seconds

�The new key request from the key pre-generation pool completed successfully.%nProcessing time: %1 seconds.

�The key pre-generation pool successfully pre-generated a key. %nProcessing time: %1 seconds.

�Windows Hello for Business prerequisites check completed successfully.

�Windows Hello container provisioning completed successfully.%nProcessing time: %1 seconds%nExisting container: %2

�Windows Hello successfully created a PIN recovery key for user %1.%nProcessing time: %2 seconds

�The cloud experience host completed successfully.%nProcessing time: %1 seconds

�Windows Hello sign-in certificate enrollment completed successfully.%nProcessing time: %1 seconds

�Windows Hello set a certificate property on a Windows Hello key.%n%nKey name: %1%nCertificate type: %2

�Windows Hello PIN Recovery successfully changed the user's PIN.%nProcessing time: %1 seconds.

�The device registration prerequisite check completed successfully.

�The Primary Account Primary Refresh Token prerequisite check completed successfully.

�The device meets Windows Hello for Business hardware requirements.

XWindows Hello for Business is enabled.

�Windows Hello for Business post-logon provisioning is enabled.

�Windows Hello for Business successfully located a usable sign-on certificate template.

�Windows Hello for Business successfully located a certificate registration authority.

�Windows Hello for Business successfully located an enterprise management client.

�Windows Hello for Business successfully located a sign-in certificate profile.

Windows Hello for Business successfully located a certificate payload for the sign-in certificate. The SCEP Request is available.

�Windows Hello for Business successfully completed the remote desktop prerequisite check.

�The Secondary Account Primary Refresh Token prerequisite check completed successfully.

�Windows Hello key creation completed successfully.%nProcessing time: %1 seconds

�Windows Hello successfully deleted a %1 %2 key from the Windows Hello container.%n%nKey Name: %3

xWindows Hello key registration completed successfully.

�Successfully authenticated the user's credential.%nProcessing time: %1 milliseconds.

�AD/Azure AD plugin request completed successfully.%nProcessing time: %1 seconds

�The Windows Hello container creation completed successfully.%nProcessing time: %1 seconds

�Windows Hello successfully deleted the container in response to a policy change.%n%nProcessing time: %1 milliseconds.

lWindows Hello successfully deleted the container.

�Windows Hello successfully deleted the user's Windows Hello certificates.

�Windows Hello successfully deleted the user's biometric enrollments.

No TPM

TPM 1.2

TPM 2.0

Password

Biometric

Other

hardware

software

0Default Decryption

$Cached Logon

User ID

Key-trust

,Certificate-trust

None

MDM

$Self-service

Remote

Destructive

(Non-destructive

(Force Software

Any TPM

0TPM 2.0 or Software

0Hardware Preferred

,Hardware Required

$Uninitialized

Unloaded

Okay

(Unknown Failure

TPM Cleared

(TPM Unavailable

(VSM Unavailable

Self-signed

CA signed

Unknown

disabled

enabled

Enrollment

Reset

Fix Me

LSmart card emulation is disabled.

HThe certificate is unavailable.

HThe certificate is self-signed.

dThe certificate is expired or not yet valid.

�The certificate does not contain required key use properties.

pThe certificate information could not be validated.

�4VS_VERSION_INFO��
iaJ
iaJ?StringFileInfo�040904B0LCompanyNameMicrosoft CorporationVFileDescriptionMicrosoft Passport APIn'FileVersion10.0.19041.5737 (WinBuild.160101.0800):
InternalNamecryptngc.dll�.LegalCopyright� Microsoft Corporation. All rights reserved.JOriginalFilenamecryptngc.dll.muij%ProductNameMicrosoft� Windows� Operating SystemDProductVersion10.0.19041.5737DVarFileInfo$Translation �PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADD