Mini Kabibi Habibi

Current Path : C:/Windows/SysWOW64/en-US/
Current File : C:/Windows/SysWOW64/en-US/dsreg.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�!�

��@ ��8.rdata�@@.rsrc� �@@Q;�	
T88Q;�	$��8.rdata8x.rdata$zzzdbg @.rsrc$01@!��.rsrc$02 �z�h�3�r�
��h���� ���Zy��Q;�	0�0�H�`�x���������	�			 8!���!B�4%��H���MUI���mQ]5�����p���M�oerss .v.L�i�>�����MUIen-US�Your device is having problems with your work or school account. Sign in again to access your organization s resources.

Learn more at
https://aka.ms/accountrecovery�Your device is having problems with your work or school account. Contact your IT admin to get access to your organization's resources.

Learn more at
https://aka.ms/accountrecoverySign inNot nowCloseSign in requiredContact your IT adminPA@ !&{��� fPP��%1

%1

%1

tThe discovery request send operation was successful.

�The discovery request send operation failed with exit code: %1. Inputs:%n Domain: %2

�The discovery operation callback was successful. %nServer response was: %1

The discovery operation callback failed with exit code: %1. The server returned HTTP status: %2. %nServer response was:%n%3

�The initialization of the join request was successful. Inputs:%n JoinRequest: %1 (%2)%n Domain: %3

�The initialization of the join request failed with exit code: %1. Inputs:%n JoinRequest: %2 (%3)%n Domain: %4

�The join request was successfully sent to server. Inputs:%n AuthToken: %1

�The send join request operation failed with exit code: %1. Inputs:%n AuthToken: %2

�The get join response operation callback was successful. %nActivity Id: %2 %nServer response was: %1

4The get join response operation callback failed with exit code: %1. %nActivity Id: %2 %nThe server returned HTTP status: %3 %nServer response was: %4

tThe complete join response operation was successful.

�The complete join response operation failed with exit code: %1. 

�The post join tasks for the AAD Authentication Package completed successfully.

�The post join tasks for the AAD Authentication Package failed with exit code: %1

�The Microsoft Passport key was successfully registered with Azure AD.

%nKey ID: %1

%nUPN: %2

%nAttestation: %3

%nClient request ID: %4

%nServer request ID: %5

%nServer response: %6

�NGC key registration failed.

%nExit code: %1

%nClient request ID: %2

%nServer request ID: %3

%nError code: %4

%nServer error message: %5

%nRecommended client response: %6

%nServer response: %7

�The NGC key registration request was successfully sent. User email: %1.%nAuth token: %2.

�The NGC key registration initialization operation failed. Exit code: %1. User email: %2.%nAuth token: %3.

4Automatic registration failed at join phase.

%nExit code: %1

%nServer error: %2

%nTenant type: %3

%nRegistration type: %4

%nDebug Output:

%n%5

LAutomatic registration Succeeded.

TAutomatic registration failed at authentication phase. Unable to acquire access token.

%nExit code: %1

%nTenant Name: %4

%nTenant Type: %3

%nServer error:

%n%2

dAutomatic registration failed. Failed to lookup the registration service information from Active Directory. Exit code: %1. See http://go.microsoft.com/fwlink/?LinkId=623042

�The existing NGC user ID key was successfully deleted. Key name: %1.

DThis Device is joined to Azure AD, however, the user did not sign-in with an Azure AD account. Microsoft Passport provisioning will not be enabled. User: %1.

�Failed to discover the Azure AD DRS service. Exit code: %1.

%1

%1

�The parameter value should not be NULL or empty. Function: %1; Parameter: %2.

tUnable to remove account %2 from group %1. Error: %3

�Unable to convert the string-format security identifier (SID) %1 to a functional SID. Error: %2

�Unable to retrieve account information for security identifier (SID) %1. Error: %2

hUnable to add account %2 to group %1. Error: %3

�Error happened while accessing registry: %1. Operation: %2. Path: %3.

�Unable to connect to Local Security Authority (LSA) server. Error: %1

�Unable to lookup Local Security Authority (LSA) authentication package. Package name: %1. Error: %2

,Local Security Authority (LSA) authentication failed.

%nAuthentication package identifier: %1.

%nAuthentication package name: %2.

%nError: %3

�The security identifier (SID) is invalid. Function name: %1. Parameter name: %2.

xUnable to copy security identifier (SID) %1. Error: %2

`The string %1 is not a valid email address.

�Unable to retrieve the Active Directory domain join status information of the computer. Error: %1

�Unable to retrieve the local computer's name in the specified format %1. Error: %2

�Unable to connect to the LDAP server %1:%2 using authentication method %3. Error: %4

�Unable to convert the SID structure to its string-format. Error: %1

`Unable to set WinHTTP option %1. Error: %2

dUnable to query WinHTTP option %1. Error: %2

(Unable to initialize WinHTTP.

%nUser agent: %1

%nAccess type: %2

%nProxy name: %3

%nProxy bypass address list: %4

%nFlags: %5

%nError: %6

�Unable to connect to server %1:%2 through WinHTTP. Error: %3

xUnable to open WinHTTP %1 request. Flags: %2. Error: %3

�Unable to set WinHTTP call back function. Notification flags: %1. Error: %2

�Unable to retrieve WinHTTP header information. Flags: %1. Name: %2. Error: %3

\Unable to send WinHTTP request. Error: %1

DOne or more errors were encountered while retrieving a Secure Sockets Layer (SSL) certificate from the server. 

%nError code: %1

%nWinHTTP status: %2 (%3)

�The WinHTTP callback function was cancelled. WINHTTP_STATUS_CALLBACK status code: %1 (%2)

�The WinHTTP callback function failed. WINHTTP_STATUS_CALLBACK status code: %1 (%3). Error: %2

�Unalbed to query the amount of data available to read through WinHTTP. Error: %1

TWinHTTP read data failure. Error: %1

TWinHTTP write data failure. Error: %1

�Unable to setup a certificate from the given encoded string. Error: %1

\Unable to save the certificate. Error: %1

�Unable to retrieve the NGC user ID key with name %1. Error: %2

The NGC create container operation failed.

%nUser SID: %1

%nIDP domain: %2

%nTenant domain: %3

%nFlags: %4

%nError: %5

�The existing NGC container was successfully deleted.

%nUser SID: %1

%nIDP domain: %2

%nTenant domain: %3

�The NGC container was successfully created.

%nUser SID: %1

%nIDP domain: %2

%nTenant domain: %3

%nFlags: %4

�Unable to delete NGC container.

%nUser SID: %1

%nIDP domain: %2

%nTenant domain: %3

%nError: %4

Unable to create NGC user ID key.

%nUser SID: %1

%nIDP domain: %2

%nTenant domain: %3

%nUser ID: %4

%nFlags: %5

%nError: %6

Unable to retrieve the specified NGC user ID key.

%nUser SID: %1

%nIDP domain: %2

%nTenant domain: %3

%nUser ID: %4

%nError: %5

|Unable to delete NGC user ID key. Key name: %1. Error: %2

0Unable to create NGC transport key.

%nUser SID: %1

%nIDP domain: %2

%nTenant domain: %3

%nUser ID: %4

%nKey type: %5

%nFlags: %6

%nError: %7

Unable to delete NGC transport key.

%nUser SID: %1

%nIDP domain: %2

%nTenant domain: %3

%nUser ID: %4

%nFlags: %6

%nError: %5

�Unable to parse the NGC registration server response.

%nHTTP status: %1

%nServer response body: %2

%nError: %3

hFailed to enable the device lock PIN. Error: %1

�The application does not have the permission to perform this operation. Application SID: %1

XPreparing to send a request to the Web Account Manager.

%nAccount provider ID: %1

%nScope: %2

%nClient ID: %3

%nAuthority: %4

%nResource: %5

%nCorrelationId: %6

|Unable to get a token using the Web Account Manager. Error: %5

%nRequest status code: %1 (%2)

%nToken provider error code: %3

%nToken provider error message: %4

%nCorrelationId: %6

�Successfully obtained a token for the current user via token broker.

%nCorrelationId: %1

xUnable to get the application's core window. Error: %1

PAzure DRS and Enterprise DRS are configured for this device. Only one DRS instance can be configured for an environment. AzureADTenantName:%1 EnterpriseDrsName:%2

The NGC user ID key was successfully created.

%nUser SID: %1

%nIDP domain: %2

%nTenant domain: %3

%nUser ID: %4

%nFlags: %5

Unable to check whether a PIN has been created to use in place of the current user's logon password.

%nUser SID: %1

%nError: %2

�Preparing to send a request to the Web Account Manager silently (no UI mode).

%nAccount provider ID: %1

%nScope: %2

%nClient ID: %3

%nAuthority: %4

%nResource: %5

%nCorrelationId: %6

�Automatic device join pre-check tasks completed. Debug output:\r\n %1

TAutomatic device join pre-check tasks found that this device is joined, however, it is missing some required state. The device will be removed and then joined again.

Automatic device join pre-check tasks completed. The device can NOT be joined. The process MUST run as NT AUTHORITY\SYSTEM.

�Automatic device join pre-check tasks completed. The device can NOT be joined because a domain controller could not be located. The device must be connected to a network with connectivity to an Active Directory domain controller.

�Automatic device join pre-check tasks completed. The device is already joined.

�The Web Proxy Autodiscovery Protocol (WPAD) did NOT locate the URL of a configuration file using DHCP and/or DNS discovery methods. The request will be sent directly to the server.

%nWINHTTP_STATUS_CALLBACK dwInternetStatus is %1 (%4)

%nWINHTTP_ASYNC_RESULT dwResult is %2 (%5)

%nWINHTTP_ASYNC_RESULT dwError is %3

�The Web Proxy Autodiscovery Protocol (WPAD) located the URL of a configuration file using DHCP and/or DNS discovery methods. %1 configuration entries were found in the configuration file.

hThe following out-bound proxy information was set for this request.

%nWINHTTP_PROXY_RESULT_ENTRY fProxy is: %1

%nWINHTTP_PROXY_RESULT_ENTRY fBypass is: %2

%nWINHTTP_PROXY_RESULT_ENTRY INTERNET_SCHEME is: %3

%nWINHTTP_PROXY_RESULT_ENTRY pwszProxy is: %4

%nWINHTTP_PROXY_RESULT_ENTRY ProxyPort is: %5

XThe request was sent to the server through the out-bound proxy and failed with the following information. A fail-over proxy server will be used if available.

%nWINHTTP_STATUS_CALLBACK dwInternetStatus is %1 (%4)

%nWINHTTP_ASYNC_RESULT dwResult is %2 (%5)

%nWINHTTP_ASYNC_RESULT dwError is %3

The Web Proxy Autodiscovery Protocol (WPAD) encountered an unexpected error. The request may not have been sent to the server.

%nWINHTTP_STATUS_CALLBACK dwInternetStatus is %1 (%4)

%nWINHTTP_ASYNC_RESULT dwResult is %2 (%5)

%nWINHTTP_ASYNC_RESULT dwError is %3

XThis request will NOT fail over to a proxy server. The end of the proxy configuration discovered by Web Proxy Autodiscovery Protocol (WPAD) has been reached. Error %1

0Device Identity Key

DIdentifies the device with Active Directory or Azure Active Directory to access resources and applications. This key is created at device registration time.

�Unable to query Passport for Work policies.

%nUser SID: %1

%nIDP domain: %2

%nTenant domain: %3

%nError: %4

�Unable to enumerate Passport for Work containers.

%nUser SID: %1

%nError: %2

�Failed to access the device key. If you have a TPM, it might be locked out or in an unknown state.

%nError: %1

�Failed to access the device key. The device key has likely been removed.

%nError: %1

hThe Microsoft Passport key was successfully removed from Azure AD.

%nKey ID (encoded): %1

%nUPN: %2

%nClient request ID: %3

%nServer request ID: %4

%nServer response: %5

Failed to remove the Microsoft Passport key from Azure AD.

%nError: %2

%nKey ID (encoded): %1

%nClient request ID: %3

%nServer request ID: %4

%nServer error code: %5

%nServer error message: %6

%nRecommended client response: %7

%nServer response: %8

The Microsoft Passport delete key registration request was successfully sent. User email: %1. Tenant ID: %2. Auth token: %3.

 Failed to initialize the Microsoft Passport delete key registration request. Exit code: %1. User email: %2. Tenant ID: %3. Auth token: %4.

�The Microsoft Passport key information was successfully saved.

%nKey ID: %1

%nAttestation level: %2

%nAIK status: %3

%nKey type: %4

%nKey name: %5

%nIDP domain: %6

%nTenant ID: %7

%nUser email: %8

�Failed to save the Microsoft Passport key information.

%nError: %1

%nKey ID: %2

%nAttestation level: %3

%nAIK status: %4

%nKey type: %5

%nKey name: %6

%nIDP domain: %7

%nTenant ID: %8

%nUser email: %9

�The Microsoft Passport key information was successfully deleted.

%nKey ID: %1

%nUser SID: %2

�Failed to delete the Microsoft Passport key information.

%nError: %1

%nKey ID: %2

%nUser SID: %3

�Json Request Failed. Exit code: %1. httpStatus: %2 Server response: %3.

<Successfully enrolled for a logon certificate using a Registration Authority.

%nUpn: %1

%nTenantId: %2

%nAuthority: %3

%nResource: %4

%nExitCode: %5

�Failed to enroll for a logon certificate using a Registration Authority.

%nUPN: %1

%nTenantId: %2

%nExitCode: %3

�Group Policy indicates the user must enroll for a logon certificate along with their work PIN.

%nSid: %1

%nTenantId: %2

tThe Microsoft Passport key is missing.

%nKey ID: %1

%nAttestation level: %2

%nAIK status: %3

%nKey type: %4

%nKey name: %5

%nIDP domain: %6

%nTenant ID: %7

%nUser email: %8

HThe saved Microsoft Passport information does not match the key.

%nSaved information:

%n  Key ID: %1

%n  Key name: %2

%n  IDP domain: %3

%n  Tenant ID: %4

%n  User email: %5

%nThe Microsoft Passport key:

%n  Key name: %6

%n  IDP domain: %7

%n  Tenant ID: %8

%n  User email: %9

�%1

%nDevice is AAD joined ( AADJ or DJ++ ): %2

%nUser has logged on with AAD credentials: %3

%nWindows Hello for Business policy is enabled: %4

%nWindows Hello for Business post-logon provisioning is enabled: %5

%nLocal computer meets Windows hello for business hardware requirements: %6

%nUser is not connected to the machine via Remote Desktop: %7

%nUser certificate for on premise auth policy is enabled: %8

%nMachine is governed by %9 policy.

%nCloud trust for on premise auth policy is enabled: %10

%nUser account has Cloud TGT: %11

%nSee https://go.microsoft.com/fwlink/?linkid=832647 for more details.

�%1

%nDevice is AAD joined ( AADJ or DJ++ ): %2

%nUser has logged on with AAD credentials: %3

%nWindows Hello for Business policy is enabled: %4

%nWindows Hello for Business post-logon provisioning is enabled: %5

%nLocal computer meets Windows hello for business hardware requirements: %6

%nUser is not connected to the machine via Remote Desktop: %7

%nUser certificate for on premise auth policy is enabled: %8

%nEnterprise user logon certificate enrollment endpoint is ready: %9

%nEnterprise user logon certificate template is : %10

%nUser has successfully authenticated to the enterprise STS: %11

%nCertificate enrollment method: %12

%nSee https://go.microsoft.com/fwlink/?linkid=832647 for more details.

�%1

%nDevice is AAD joined ( AADJ or DJ++ ): %2

%nUser has logged on with AAD credentials: %3

%nWindows Hello for Business policy is enabled: %4

%nWindows Hello for Business post-logon provisioning is enabled: %5

%nLocal computer meets Windows hello for business hardware requirements: %6

%nUser is not connected to the machine via Remote Desktop: %7

%nUser certificate for on premise auth policy is enabled: %8

%nMDM user certificate enrollment is ready: %9

%nCertificate enrollment method: %10

%nSee https://go.microsoft.com/fwlink/?linkid=832647 for more details

|Windows Hello for Business provisioning will be launched.

�Windows Hello for Business provisioning will not be launched.

�Windows Hello for Business provisioning has encountered an error during policy evaluation.

%nExitCode: %1

%nMethod: %2

%nSee https://go.microsoft.com/fwlink/?linkid=832647 for more details

tUnable to enroll for a logon certificate using a Registration Authority. Automatic certificate enrollment will retry at regular intervals.

%nUPN: %1

%nTenantId: %2

%nExitCode: %3

�Unable to enroll for a logon certificate using a Registration Authority.

%nResource: %1

%nExitCode: %2

�Added following properties to the Web Account Manager access token request.

%nProperties:

%n%1

�The following token properties were recieved from the Web Account Manager:

%nProperties: %1

|The automatic device registration task will be triggered.

�The Workstation Service logged a device registration message.

%nMessage: %1



`The automatic device registration task failed to unregister device.

%nExit code: %1

%nServer error: %2

%nTenant type: %3

%nRegistration type: %4

%nDebug Output:

%n%5

�The automatic device registration task successfully unregistered device.

0The FIDO credential was successfully registered with Azure AD.

%nCredential ID: %1

%nUPN: %2

%nRequest ID: %3

%nTime: %4

%nServer response: %5

�FIDO credential registration failed.

%nExit code: %1

%nRequest ID: %2

%nTime: %3

%nHTTP status: %4

%nError code: %5

%nError subcode: %6

%nServer error message: %7

%nServer response: %8

�The FIDO credential registration request was successfully sent.

%nRPID: %1

%nUPN: %2

%nCredential display name: %3

%nUser display name: %4

%nUser image URL: %5

%nKey algorithm: %6

%nAuth token: %7

%nRequest ID: %8

%nFlags: %9

The FIDO credential registration initialization operation failed.

%nExit code: %1

%nRPID: %2

%nUPN: %3

%nCredential display name: %4

%nUser display name: %5

%nUser image URL: %6

%nKey algorithm: %7

%nAuth token: %8

%nRequest ID: %9

%nFlags: %10

�The FIDO credential was successfully created.

%nUPN: %1

%nCredential display name: %2

%nUser display name: %3

%nUser image URL: %4

%nKey algorithm: %5

%nAuth token: %6

%nRequest ID: %7

%nFlags: %8

�Unable to create FIDO credential.

%nExit code: %1

%nUPN: %2

%nCredential display name: %3

%nUser display name: %4

%nUser image URL: %5

%nKey algorithm: %6

%nAuth token: %7

%nRequest ID: %8

%nFlags: %9

@The FIDO credentials were successfully deleted from Azure AD.

%nNumber of credentials: %1

%nUPN: %3

%nRequest ID: %4

%nTime: %5

%nServer response: %6

�FIDO credential deletion failed.

%nExit code: %1

%nRequest ID: %2

%nTime: %3

%nHTTP status: %4

%nError code: %5

%nError subcode: %6

%nServer error message: %7

%nServer response: %8

The FIDO credential deletion request was successfully sent.

%nUPN: %1

%nCredential ID: %2

%nAuth token: %3

%nRequest ID: %4

0The FIDO credential deletion initialization operation failed.

%nExit code: %1

%nUPN: %2

%nCredential ID: %3

%nAuth token: %4

%nRequest ID: %5

�Unable to parse the FIDO registration server response.

%nHTTP status: %1

%nServer response body: %2

%nError: %3

\The PIN has been successfully recovered.

tThe PIN recover operation failed with exit code: %1.

�Unable to get attestation statement for Microsoft Passport key. Key name: %1,  KeyStatus: %2 (%3), Error: %4.

�Successfully got attestation statement for Microsoft Passport key. Key name: %1, KeyStatus: %2 (%3). 

pUnable to reset registry recovery flags. Error: %1

LRecovery API %1 called. Error: %2

�The registration status has been successfully cleared from the device.

%nJoin type: %1 (%2)

%nTenant ID: %3

%nUPN: %4

Unable to clear the registration status from the device.

%nExit code: %1

%nJoin type: %2 (%3)

%nTenant ID: %4

%nUPN: %5

�The registration status has been successfully flushed to disk.

%nJoin type: %1 (%2)

�Unable to flush the registration status to disk.

%nExit code: %1

%nJoin type: %2 (%3)

0KSP session ID: %1

Unable to remove the PIN that has been created to use in place of the current user's logon password.

%nUser SID: %1

%nError: %2

LAccount %2 was added to group %1.

TAccount %2 was removed from group %1.

�Unable to sign authentication data for managed automatic registration. Exit code: %1.

�Unable to verify or update the signing certificate for automatic registration. Exit code: %1.

\Automatic Azure SecureVM Join Succeeded.

Unable to get persisted state location.

%nExit code: %1

%nResource ID: %2

%nDefault location: %3

%nLocation type: %4 (%5)

Unable to remove Microsoft Passport key registration for all local Active Directory and Azure Active Directory users.

%nExit code: %1

�Resource account certificate does not match device ceritificate.

%nMismatch in: %1

%nResource account certificate's value: %2

%nDevice certificate's value: %3

%nRequest ID: %4

%nServer time: %5

�Unable to get the NGC user ID key container state.

%nSID: %1

%nKey name: %2

%nError: %3

�The NGC user ID key container is in a bad state.

%nSID: %1

%nKey name: %2

%nContainer status: %3

�NGC logon certificate could not be renewed due to device ID flip.

�Unable to set registry value for device ID flip.

%nExit code: %1

�Unable to unset registry value for device ID flip.

%nExit code: %1

\Unable to check whether the attribute value of the device object is up to date.

%nExit code: %1

%nAttribute: %2

%nTenant ID: %3

%nDevice ID: %4

%nJoin type: %5 (%6)

`Unable to start updating attribute value of the device object.

%nExit code: %1

%nAttribute: %2

%nTenant ID: %3

%nDevice ID: %4

%nJoin type: %5 (%6)

%nRequest ID: %7

HUpdating attribute value of the device object started successfully.

%nAttribute: %1

%nTenant ID: %2

%nDevice ID: %3

%nJoin type: %4 (%5)

%nRequest ID: %6

�The attribute value of the device object was updated successfully.

%nAttribute: %1

%nTenant ID: %2

%nDevice ID: %3

%nJoin type: %4 (%5)

%nRequest ID: %6

%nHTTP status: %7

%nTime: %8

%nServer message: %9

%nServer response body: %10

PUnable to update the attribute value of the device object.

%nExit code: %1

%nAttribute: %2

%nTenant ID: %3

%nDevice ID: %4

%nJoin type: %5 (%6)

%nRequest ID: %7

%nHTTP status: %8

%nTime: %9

%nError Code: %12

%nError Subcode: %13

%nServer message: %10

%nServer response body: %11

�Unable to parse the device attribute update server response.

%nHTTP status: %1

%nServer response body: %2

%nError: %3

�Unable to check MDM enrollment status of the device.

%nError: %1

�Unable to trigger update task for this device.

%nError: %1

%nJoin type: %2 (%3)

%nTenant ID: %4

�The update task for this device was successfully triggered.

%nJoin type: %1 (%2)

%nTenant ID: %3

�Key policy in registry is set to unsupported value %1. Default key policy will be used.

\The task %1\%2 was successfully enabled.

XFailed to enable task %2\%3. Error: %1

\The task %1\%2 was successfully disabled.

XFailed to disable task %2\%3. Error: %1

The repair join information operation failed.

%nExit code: %1

%nTenant ID: %2

%nDevice ID: %3

%nJoin Type: %4 (%5)

%nRequest Id: %6

%nTime: %7

%nHttp Status: %8

%nError Code: %9

%nError Subcode: %10

%nServer Message: %11

%nServer Operation: %12

xThe repair join information operation completed successfully.

%nTenant ID: %1

%nDevice ID: %2

%nJoin UPN: %3

%nJoin Type: %4 (%5)

%nRequest Id: %6

%nTime: %7

%nHttp Status: %8

\The repair join information operation failed to start.

%nExit code: %1

%nTenant ID: %2

%nJoin Type: %3 (%4)

%nInput UPN: %5

%nInput UPN Count: %6

%nRequest ID: %7

dThe repair join information operation started successfully.

%nTenant ID: %1

%nDevice ID: %2

%nJoin UPN: %5

%nInput UPN Count: %6

%nJoin Type: %3 (%4)

%nRequest Id: %7

�MDM enrollment for Azure SecureVM succeeded.

%nMDM Enrollment URL: %1

�MDM enrollment for Azure SecureVM failed. The device will be unjoined from Azure AD.

%nMDM Enrollment URL: %1

�Attempt to discover enrollment URL for MDM auto-enrollment failed. AAD logs may contains additional details about the failure. Another attempt to discover MDM enrollment URL will be made later.

%nCorrelationId: %1

%nAdditional information: %2

�All attempts to discover enrollment URL for MDM auto-enrollment failed.

No MDM enrollment URL was discoverered for MDM auto-enrollment. Verify MDM auto-enrollment configuration in the AAD tenant is correct and the specified MDM application ID is successfully resolved by AAD server.

%nCorrelationId: %1

%nMDM application ID: %2

�Attempt to discover enrollment URL for MDM auto-enrollment failed. AAD logs may contains additional details about the failure.

%nError: %1

%nCorrelationId: %2

%nAdditional information: %3

�Attempt to get token for MDM auto-enrollment failed. AAD logs may contains additional details about the failure. Another attempt to get token for MDM auto-enrollment will be made later.

%nCorrelationId: %1

%nAdditional information: %2

�All attempts to get WAM token for MDM auto-enrollment failed.

`Requsting token for MDM auto-enrollment failed. AAD logs may contains additional details about the failure.

%nError: %1

%nCorrelationId: %2

%nAdditional information: %3

Unenrolling from MDM failed. MDM logs may contains additional details about the failure.

%nError: %1

%nMDM enrollment ID: %2

�Successfully unenrolled from MDM.

%nMDM enrollment ID: %1

Critical

Error

Warning

 Information

Verbose

�4VS_VERSION_INFO��
4aJ
4aJ?StringFileInfo�040904B0LCompanyNameMicrosoft Corporationh FileDescriptionAD/AAD User Device Registrationn'FileVersion10.0.19041.3636 (WinBuild.160101.0800)4
InternalNamedsreg.dll�.LegalCopyright� Microsoft Corporation. All rights reserved.DOriginalFilenamedsreg.dll.muij%ProductNameMicrosoft� Windows� Operating SystemDProductVersion10.0.19041.3636DVarFileInfo$Translation	�PADDINGXXPADDING