KGRKJGETMRETU895U-589TY5MIGM5JGB5SDFESFREWTGR54TY
Server : Apache/2.4.58 (Win64) OpenSSL/3.1.3 PHP/8.2.12
System : Windows NT SERVER-PC 10.0 build 26200 (Windows 11) AMD64
User : ServerPC ( 0)
PHP Version : 8.2.12
Disable Function : NONE
Directory :  C:/Windows/System32/en-US/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Current File : C:/Windows/System32/en-US/autopilotdiag.dll.mui
MZ����@���	�!�L�!This program cannot be run in DOS mode.

$�X=��9S��9S��9S������9S���Q��9S�Rich�9S�PEL%�U��!&�

b�@ ,�8.rdata�@@.rsrc,� �@@%�U�
lPP%�U�$����8.rdata8.rdata$voltmdP�.rdata$zzzdbg  .rsrc$01 ! �.rsrc$02 3l(�I����L8�ۊ��u*�A�T��%�U��(�@�`�x�������	�	�	�	 !���!t��D�D�\��MUI���h���9a����-�1�����r���{��#���MUIen-USPP���@d���H��������������,����H2�����:�/��=6�A��J^�e�0S�����W���� i�����n����xy����|}L�U�Ȃ������������#�x�Error

Warning

 Information

xMicrosoft-Windows-ModernDeployment-Diagnostics-Provider

Admin

Autopilot

Debug

,ManagementService

 Diagnostics

LAutopilot policy [%1] not found.

�AutopilotGetPolicyDwordByName succeeded:  policy name = %1; policy value = %2.

�AutopilotGetPolicyDwordByName error:  policy name = %2; HRESULT = %1.

�AutopilotGetPolicyStringByName succeeded:  policy name = %1; policy value = %2.

�AutopilotGetPolicyStringByName error:  policy name = %2; HRESULT = %1.

@AutopilotDisable succeeded.

XAutopilotDisable error:  HRESULT = %1.

4Autopilot state = %1.

\AutopilotIsDisabled error:  HRESULT = %1.

�AutopilotGetOobeSettingsOverride succeeded:  OOBE setting = %1; state = %2.

�AutopilotGetOobeSettingsOverride error:  OOBE setting = %2; HRESULT = %1.

TAutopilotRetrieveSettings succeeded.

hAutopilotRetrieveSettings error:  HRESULT = %1.

�Autopilot reported the DLL was unloaded while there were %1 outstanding calls.

�AutopilotRetrieveSettings was skipped because this version of Windows does not support Azure Active Directory join.

4Autopilot discovery failed to find a valid MDM.  Confirm that the AAD tenant is properly provisioned and licensed for exactly one MDM.  HRESULT = %1

�Autopilot Device ESP Domain Controller override was not set.

�Autopilot Device ESP Domain Controller override was set by state %1

�Autopilot task to detect hardware change started. Task argument: %1

�Autopilot task to detect hardware change finished successfully. Task argument: %1

�Autopilot task to detect hardware change failed. Result: %1%nTask argument: %2

�Autopilot task to detect hardware change finished successfully. No change was detected.

�Autopilot task to detect hardware change finished successfully. A change was detected and reported.

�Autopilot task to detect hardware change was aborted or cancelled before completion. Task: %1

XAutopilot starting to disable task: %1

\Autopilot successfully disabled task: %1

xAutopilot failed to disable task. HRESULT: %1%nTask: %2

TAutopilot starting to enable task: %1

XAutopilot successfully enabled task: %1

xAutopilot failed to enable task. HRESULT: %1%nTask: %2

|Autopilot hardware remediation report failed. HRESULT: %1

�Autopilot hardware remediation must wait before reporting again. Delay in minutes: %1

�Autopilot hardware remediation failed to process response. HRESULT = %1%nStage: %2

�Autopilot hardware remediation failed to read cached hardware. HRESULT = %1%nHardware location: %2

�Autopilot hardware remediation failed to write cached hardware. HRESULT = %1%nHardware location: %2

�AutopilotManager started the MSA service for TPM attestation identity.

�AutopilotManager started the TPM maintenance task to update TPM attestation.

�AutopilotManager reported TPM maintenance task is complete.

�AutopilotManager reported the state changed from %1 to %2.

�AutopilotManager failed to start MSA service.  HRESULT = %1.

|AutopilotManager failed to start TPM task.  HRESULT = %1.

PAutopilotManager reported that MSA TPM is not configured for hardware TPM attestation even though the profile indicates it is required.  Autopilot cannot proceed.

�AutopilotManager reported that TPM attestation lasted %1 microseconds.

�AutopilotManager reported that TPM enhanced diagnostics logging was enabled for %1 providers.

lAutopilotRetrieveSettings beginning acquisition.

dAutopilotManager retrieve settings succeeded.

AutopilotManager determined download is not required and the device is not provisioned.  Clean or reset the device to change this.

AutopilotManager determined download is not required and the device is already provisioned.  Clean or reset the device to change this.

�AutopilotManager determined Internet is available to attempt policy download.

�AutopilotManager determined Internet is not available; policy download will queue when available.

tAutopilotManager reported Internet is now available.

�AutopilotManager reported Internet is still not available.

�AutopilotManager reported MSA TPM device identity was updated.

dAutopilotManager set TPM identity confirmed.

�AutopilotManager reported that Autopilot profile download is now complete.

�AutopilotManager failed to set TPM identity confirmed.  HRESULT = %1.

�AutopilotManager failed to set Autopilot profile as available.  HRESULT = %1.

�AutopilotManager failed to register for network availability.  HRESULT = %1.

�AutopilotManager failed to register for device identity availability.  HRESULT = %1

�AutopilotManager failed to register for device identity task update.  HRESULT = %1

�MSA TPM keystate has been updated.  New server state = %1, new client state = %2

�Configuring TPM for attestation.  Current attempt %1 of %2 maximum.

�AutopilotManager began device enrollment with internal state %1.

pAutopilotManager began device enrollment phase %1.

�AutopilotManager failed during device enrollment phase %1.  HRESULT = %2

�AutopilotManager completed device enrollment phase %1.  HRESULT = %2

�AutopilotManager reported that the retry timer event was set to %1 milliseconds.

�AutopilotManager reported that the retry timer event occurred

�AutopilotManager failed to register for MSA keystate update availability.  HRESULT = %1

�AutopilotManager failed to retrieve settings.  HRESULT = %1

xAutopilotManager TPM configuration already in progress.

�AutopilotManager TPM configuration occurred before retry timer ready.

tConfiguring TPM exceeded maximum number of attempts.

xWindows AIK certificate enrollment task was triggered.

�Windows TPM maintenance task is being skipped since AIK certificate is already present.

Autopilot device enrollment failed with error HRESULT = %1. Waiting %2 milliseconds then retrying.%nCurrent attempt %3 of %4.

�Autopilot manager is attempting profile download retry.  Current attempt %1 of %2.

�Autopilot manager will re-attempt the download after %1 milliseconds.

`AutopilotManager began device unenrollment

�AutopilotManager completed device unenrollment.  HRESULT = %1

�AutopilotManager failed device unenrollment.  HRESULT = %1

tWindows AIK object could not be loaded.  HRESULT = %1

PWindows AIK key not found by name.

tWindows AIK certificate download failed. HRESULT = %1

lWindows AIK alternative load failed. HRESULT = %1

�Windows AIK certificate request did not result in a new certificate.

�Windows AIK certificate request succeeded and a new certificate is available.

lWindows AIK key could not be opened. HRESULT = %1

|Windows AIK key failed certificate request. HRESULT = %1

PWindows EK certificate is present.

XWindows EK certificate is not present.

Windows AIK key was found even though the Windows EK certificate is not present. Attempting to re-initialize the TPM task.

�AutopilotManager reported that a TPM was required but the TPM failed an attestation capability check.  HRESULT = %1

,AutopilotManager reported the TPM returned the following for known vulnerabilities: HRESULT = %1%nHasVulnerability = %2%nVulnerabilityFlags = %3

�AutopilotManager reported the TPM returned the following for Key attestation capability: HRESULT = %1%nKey flags = %2

�AutopilotManager started AIK certificate acquisition task.

DAutopilotManager reported AIK certificate acquisition task returned HRESULT = %1.%nElapsed time: %2 microseconds (maximum allowed time was %3 milliseconds).

hAutopilotManager reported AIK key was located.

xAutopilotManager reported AIK certificate was located.

�AutopilotManager reported AIK certificate was not located.

�AutopilotManager is determining whether device has internet access.

�AutopilotManager is determining Autopilot profile availability.

�Tracking resource type %1. Starting installation of policy provider '%2'.

�Tracking resource type %1. Policy provider '%2' installation completed successfully.

�Tracking resource type %1. Policy provider '%2' installation timed out after %3 minutes.

�Tracking resource type %1. An error occured while installing policy provider '%2'. Error: %3

�Tracking resource type %1. Installation of policy provider '%2' not required.

�Tracking resource type %1. Retrieving tracking list from policy provider '%2'.

�Tracking resource type %1. Policy provider '%2' provided a list of %3 policies to track.

Tracking resource type %1. Policy provider '%2' encountered an error and the tracking list could not be completed. Error: %3

�Tracking resource type %1. Policy provider '%2' provided an empty list of policies.

�Tracking resource type %1. App '%2' installation completed successfully. 

�Tracking resource type %1. Starting installation tracking app '%2'.

�Tracking resource type %1. An error occurred while installing app '%2'.  HRESULT = %3

�Tracking resource type %1. Reboot required to complete installation of app '%2'.

�AutopilotManager device enrollment reported an initialization failure.  HRESULT = %1.

�AutopilotManager device enrollment reported a blocking failure.  Overall error %2, last reported stage %1.

�AutopilotManager device enrollment failed during stage %1 with error %2.

�AutopilotManager device enrollment succeeded.  Last valid stage: %1.

|Autopilot configuration file path: %1 %nExpanded path:%2

�Failed to load Autopilot configuration file, HRESULT = %1.

�Failed to parse Autopilot configuration file, HRESULT = %1.

�Invalid ZtdCorrelationId found in Autopilot configuration file, HRESULT = %1. ZtdCorrelationId: '%2'.

HAutopilotManager reported that the Autopilot profile data could not be downloaded. Any Autopilot settings will not be used and the device will not be managed.

�AutopilotManager failed to record the setting for Autopilot device not managed, HRESULT = %1.

xAutopilotSync: Starting sync sessions for SyncType: %1.

tAutopilotSync: Ending sync sessions for SyncType: %1.

�AutopilotSync: Attempted sync session. Result: %1, EnrollmentId: %2, SyncType: %3, SyncSessionId: %4.

�AutopilotSync: Skipped sync session. Result: %1, EnrollmentId: %2, SyncType: %3, PreviousSessionCompleted: %4.

PAutopilotSync: Using user SID: %1.

AutopilotSync: Current sync session. IsCompleted: %1, SessionState: %2, SyncSessionId: %3, EnrollmentId: %4, SyncType: %5.

�Autopilot for Surface Hub encountered bad override data. HRESULT = %1%nPolicy name=%2

dAutopilot for Surface Hub override succeeded.

�Autopilot for Surface Hub failed to configure properties. HRESULT = %1

�Autopilot for Surface Hub failed to apply properties. HRESULT = %1

|Autopilot for Surface Hub applied properties successfully

�Autopilot for Surface Hub failed to validate a property. %nHRESULT = %1%nProperty name:%2

�Autopilot for Surface Hub failed to execute the Csp successfully. HRESULT = %1

�Autopilot for Surface Hub validated and applied properties successfully

(Autopilot Initial Provisioning reported a change in connection status.%nChange type: %1%nHost result: %2%nAgent result: %3%nOverall result: %4

@Autopilot Initial Provisioning heartbeat occurred.%nHost result: %1%nAgent result: %2%nOverall result: %3%nHost failure count: %4%nAgent failure count: %5

�Autopilot Initial Provisioning detected a network state change. New value: %1

�Autopilot Provisioning change. Session Id: %1, sequence number: %4.%nSource:%2Details: %3

�Autopilot Provisioning change started. Session Id: %1, Context Id: %2, sequence number: %4.%nSource:%3

$Autopilot Provisioning change succeeded. Session Id: %1, Context Id: %2, sequence number: %5.%nSource:%3%nAdditional Details: %4%nResult: %6

Autopilot Provisioning change failed. Session Id: %1, Context Id: %2, sequence number: %5.%nSource:%3Additional Details: %4%nResult: %6

LAutopilot Provisioning change failed with unspecified error. Session Id: %1, Context Id: %2, sequence number: %5.%nSource:%3%nAdditional Details: %4%nResult: %6

8Autopilot Provisioning reported a warning occurred. Session Id: %1, Context Id: %2, sequence number: %5.%nSource:%3%nAdditional Details: %4%nResult: %6

Unexpected error: device preparation page settings are not configured or are invalid. Default values will be used. Result: %1

�Device preparation page settings were loaded successfully.

�Unexpected error: a device preparation page setting value could not be loaded/converted. Setting name: %2, result: %1

lAgent download completed. Notification state: %1

pAgent download notification complete. HRESULT = %1

�Agent download notification handler changed. Callback was added.

�Agent download notification handler changed. Callback was removed.

DAgent download was triggered.

�A duplicate deployment workload with this id already exists. This may indicate bad logic. Id: %1, current count: %2

�A duplicate deployment workload batch with this id already exists. This may indicate bad logic. Id: %1, current count: %2

8Runtime activation of a device preparation class failed due to invalid mode. Device must be in OOBE and under DPP provisioning to succeed. HRESULT = %1

�Invalid data specified in Autopilot policy override configuration.%nHRESULT = %1%nPolicy name: %2.

�AutopilotManager failed to load Json for %2.%nHRESULT = %1%nPath: %3.

�AutopilotManager failed to clear for %2.%nHRESULT = %1%nPath: %3.

�AutopilotManager failed to delete Json for %2.%nHRESULT = %1%nPath: %3.

hAutopilotManager deleted configuration file %1.

hAutopilotManager loaded configuration file %1.

�AutopilotManager failed to expand path for %2.%nHRESULT = %1.

�AutopilotManager explictly disabled TPM required due to registry setting.

�AutopilotManager explictly enabled TPM required due to registry setting.

�AutopilotManager enabled TPM requirement due to WhiteGlove policy value %1

�Autopilot downloader failed to load override registsry data for %2.%nHRESULT = %1.

�Autopilot downloader did not save new profile information because the new profile was empty.

lAutopilot downloader saved the new profile to %1.

tAutopilot downloader retrieved a new profile for %1.

xAutopilot downloader retrieved an empty profile for %1.

xAutopilot downloader cleared the local profile for %1.

�Autopilot downloader failed to download profile for %2.%nHRESULT = %1.%nCorrelation vector: %3

�Autopilot downloader failed to download profile for %2.%nHRESULT = %1.%nCorrelation vector: %3

Autopilot downloader failed to extract additional error details from response. Response data: %2.%nExtraction failure HRESULT = %1.

�Autopilot failed to download data.  Response code: %1%nDetail message:%n%2

�Autopilot failed to acquire a device ticket for target URL %2.%nHRESULT = %1.

tAutopilot downloader failed to parse target URL:%n%1

�Autopilot downloader failed to convert time %2%nHRESULT = %1.

(Autopilot downloader will use MSA Pre-production environment. This will result in Autopilot failures if production device identities were used.

\Autopilot downloader reported a failure acquiring the MSA device ticket. This most likely occurred because MSA and CXH environments do not match (production versus PPE).

�Autopilot downloader reported a failure acquiring the MSA device ticket due to certificate errors. This may be caused by the wrong clock time on the machine so a forced time sync will be attempted.

pAutopilot downloader reported time sync succeeded.

�Autopilot downloader reported time sync failed with error = %1.

xAutopilot downloader reported that the machine clock is too far off the server time and a forced time sync will be attempted.%nServer time: %1%nClient time: %2%nSync attempt %3 of %4

DManagement service starting.

@Management service started.

lManagement service failed to start.  HRESULT = %1

XManagement service failed to register.

DManagement service shutdown.

�Management service WIL error was reported.%nHRESULT: %1%nFile: %2, line %3%nMessage: %4

\Management service call %1 is deprecated!

�Management service cleared the local Autopilot cached state.

�Management service failed to clear the local Autopilot cached state.  HRESULT = %1

�Management InProc Objects WIL error was reported.%nHRESULT: %1%nFile: %2, line %3%nMessage: %4

�Autopilot.dll WIL error was reported.%nHRESULT: %1%nFile: %2, line %3%nMessage: %4

tManagement service will use %1 for persisted storage

�Management service did not find %1.  Attempting to create it.

HManagement service created %1.

�Management service found ProcMon.exe for startup profiling.

�Management service determined ProcMon.exe startup profiling is not enabled in the registry.

�Management service determined ProcMon.exe startup profiling is enabled in the registry.

�Management service is beginning ProcMon.exe startup profiling.

�Management service is began ProcMon.exe startup profiling.

�Management service is stopping ProcMon.exe startup profiling.

�Management service has stopped ProcMon.exe startup profiling.

\[Unit Tests] This is a test event string.

d[Unit Tests] This is a test CXH event string.

p[Unit Tests] This is a test Resource event string.

�Failed to export logs for ETW channel '%2'. [Error Code: %1]

lETW decoder failed to read next block of events.

`Abstraction of exported ETW record failed.

�An error occurred while extracting the registry value for diagnostic data '%2'. [Error Code: %1]

�Expected channel '%1' could not be found in the EtwProcessingData JSON object.

�Expected EtwProcessingData entry corresponding to event '%1' could not be found.

lExpected diagnostic data '%1' could not be found.

TCXH event was malformed. [Name: '%1']

�Expected required diagnostic data '%1' from the extracted data list was missing some expected data.

`The API executed all actions successfully.

�The API encountered an error at state '%3'. [Error Code: %1]

tThe expected key '%1' was not found in the '%2' map.

hThe expected diagnostic data '%1' was missing.

�Resource event was malformed. [Event ID: %1, Channel: '%2']

|CXH event was missing data. [Event ID: %1, Channel: '%2']

PThe API is entering the '%1' state.

hThe API completed the '%1' state successfully.

�The API successfully retrieved the serialized JSON from the '%1' file.

�The API successfully deserialized the '%1' file JSON string.

lThe API successfully aggregated the source data.

TThe '%1' concurrent worker has begun.

pThe '%1' concurrent worker completed successfully.

�An exception occurred while processing diagnostic data. Error code: %1%nTrace:%2

pDiagnostic extraction failed. Error: %1, State: %2

pThe localized string for '%1' could not be loaded.

�MDM Alert sync session: FeatureName: %1, IsCompleted: %2, SessionState: %3, SyncSessionId: %4, EnrollmentId: %5.

4ProfileState_Unknown

@ProfileState_NotProvisioned

<ProfileState_TpmAttesting

8ProfileState_Available

DProfileState_TpmNotAvailable

Completed

Initial

$AADConfigure

AADEnroll

(DeviceDiscovery

AADTicket

$MDMEnrolling

Completed

no key

 invalid key

$software key

(unattested key

$attested key

revoked

disabled

no key

@machine has no capable TPM

<machine has a capable TPM

@unknown attestation status

<no attestation capability

Dtemporary attestation failure

Dlong-term attestation failure

$attested key

`DeploymentSessionConnectionChange NoChange

tDeploymentSessionConnectionChange HostConnectionLost

|DeploymentSessionConnectionChange HostConnectionRestored

tDeploymentSessionConnectionChange AgentConnectionLost

|DeploymentSessionConnectionChange AgentConnectionRestored

|DeploymentSessionConnectionChange InternetConnectionLost

�DeploymentSessionConnectionChange InternetConnectionRestored

eAeA��A�A`�A�A�e�e�\Y��\��b��b���l��r���v��y���
�������������H�������!��"���&��0��|4��8��0$������(����, ��%��-�����1�����4�����9lAutopilot Error: Base message of the error range.

�Autopilot DDS server reported no error. RequestErrorCode: None

tAutopilot TPM Error: Base message of the error range.

HAutopilot Error: No valid MDM configuration was found for the enrollment.  Either no MDM is specified/licensed, or more than one is specified for the account.

lAutopilot Error: Application installation failed.

�Autopilot DDS server reported invalid S2S ticket. RequestErrorCode: InvalidS2STicket

�Autopilot DDS server reported server access denied. RequestErrorCode: ServerAccessDenied

�Autopilot DDS server reported user access denied. RequestErrorCode: UserAccessDenied

�Autopilot DDS server reported device access denied. RequestErrorCode: DeviceAccessDenied

�Autopilot DDS server reported max devices reached. RequestErrorCode: MaxDevicesReached

�Autopilot DDS server reported max added per month reached. RequestErrorCode: MaxAddedPerMonthReached

�Autopilot DDS server reported max removed per month reached. RequestErrorCode: MaxRemovedPerMonthReached

�Autopilot DDS server reported max users per device reached. RequestErrorCode: MaxUsersPerDeviceReached

�Autopilot DDS server reported max added per period reached. RequestErrorCode: MaxAddedPerPeriodReached

�Autopilot DDS server reported max removed per period reached. RequestErrorCode: MaxRemovedPerPeriodReached

�Autopilot DDS server reported onetime implict add already happened. RequestErrorCode: OnetimeImplictAddAlreadyHappened

�Autopilot DDS server reported unable to infer operation type. RequestErrorCode: UnableToInferOperationType

�Autopilot DDS server reported user has no relationship with device. RequestErrorCode: UserHasNoRelationshipWithDevice

�Autopilot DDS server reported user is not administrator. RequestErrorCode: UserIsNotAdministrator

�Autopilot DDS server reported no Hbi ticket. RequestErrorCode: NoHbiTicket

�Autopilot DDS server reported user Id not supported. RequestErrorCode: UserIdNotSupported

�Autopilot DDS server reported storage error. RequestErrorCode: StorageError

�Autopilot DDS server reported storage throttling error. RequestErrorCode: StorageThrottlingError

�Autopilot DDS server reported recovery key mismatch. RequestErrorCode: RecoveryKeyMismatch

�Autopilot DDS server reported user is not protected PUID. RequestErrorCode: UserIsNotProtectedPuid

�Autopilot DDS server reported device is protected. RequestErrorCode: DeviceIsProtected

�Autopilot DDS server reported device is lost. RequestErrorCode: DeviceIsLost

�Autopilot DDS server reported consent is required. RequestErrorCode: ConsentIsRequired

�Autopilot DDS server reported gwp access denied. RequestErrorCode: GwpAccessDenied

�Autopilot DDS server reported authentication failed. RequestErrorCode: AuthenticationFailed

�Autopilot DDS server reported device platform does not match. RequestErrorCode: DevicePlatformDoesNotMatch

�Autopilot DDS server reported no HWID in ticket. RequestErrorCode: NoHwidInTicket

�Autopilot DDS server reported invalid ZTD request body. RequestErrorCode: InvalidZtdRequestBody

�Autopilot DDS server reported invalid ZTD hardware hash. RequestErrorCode: InvalidZtdHardwareHash

�Autopilot DDS server reported ZTD device already assigned. RequestErrorCode: ZtdDeviceAlreadyAssigned

�Autopilot DDS server reported ZTD device is not registered. RequestErrorCode: ZtdDeviceIsNotRegistered

�Autopilot DDS server reported ZTD device assigned to other tenant. RequestErrorCode: ZtdDeviceAssignedToOtherTenant

�Autopilot DDS server reported ZTD profile is not registered. RequestErrorCode: ZtdProfileIsNotRegistered

�Autopilot DDS server reported ZTD profile assigned to other tenant. RequestErrorCode: ZtdProfileAssignedToOtherTenant

�Autopilot DDS server reported ZTD device registered by other tenant. RequestErrorCode: ZtdDeviceRegisteredByOtherTenant

�Autopilot DDS server reported ZTD device not found. RequestErrorCode: ZtdDeviceNotFound

�Autopilot DDS server reported ZTD device is not unique. RequestErrorCode: ZtdDeviceIsNotUnique

�Autopilot DDS server reported ZTD device already aad registered. RequestErrorCode: ZtdDeviceAlreadyAadRegistered

�Autopilot DDS server reported ZTD device has no assigned profile. RequestErrorCode: ZtdDeviceHasNoAssignedProfile

�Autopilot DDS server reported ZTD profile limit per tenant exceeded. RequestErrorCode: ZtdProfileLimitPerTenantExceeded

�Autopilot DDS server reported invalid ZTD tenant Id. RequestErrorCode: InvalidZtdTenantId

�Autopilot DDS server reported invalid ZTD tenant domain. RequestErrorCode: InvalidZtdTenantDomain

�Autopilot DDS server reported ZTD tenant mismatch. RequestErrorCode: ZtdTenantMismatch

�Autopilot DDS server reported invalid ZTD order Id. RequestErrorCode: InvalidZtdOrderId

�Autopilot DDS server reported invalid ZTD purchase order Id. RequestErrorCode: InvalidZtdPurchaseOrderId

�Autopilot DDS server reported OOBE session access denied. RequestErrorCode: OobeSessionAccessDenied

�Autopilot DDS server reported invalid post processing request body. RequestErrorCode: InvalidPostProcessingRequestBody

�Autopilot DDS server reported invalid device Id. RequestErrorCode: InvalidDeviceId

�Autopilot DDS server reported unsupported operation. RequestErrorCode: UnsupportedOperation

�Autopilot DDS server reported failed post processing. RequestErrorCode: FailedPostProcessing

Autopilot TPM Error: a TPM was required but attempts to perform TPM key attestation have exceeded the maximum retry count.

�Autopilot TPM Error: a TPM was required but could not found.

�Autopilot TPM Error: a TPM was requried but the TPM is not currently enabled.

�Autopilot TPM Error: a TPM was required but the TPM reports that it is not TPM 2.0 capable.

�Autopilot TPM Error: a TPM was required but the TPM reports it does not support attestation.

�Autopilot TPM Error: a TPM was required but the TPM reports it is affected by a known vulnerability and must be updated.

�Diagnostic Analysis Framework API Error: an error occurred in the API that did not have a known HRESULT.

�Autopilot for Surface Hub failed to configure SurfaceHub CSP.

�Autopilot for Surface Hub failed to find a valid Device Account UPN configured in the SurfaceHub CSP.

�Autopilot for Surface Hub failed to find a valid Device Account Password configured in the SurfaceHub CSP.

�Autopilot for Surface Hub failed to find a valid Device Friendly Name configured in the SurfaceHub CSP.

�Autopilot for Surface Hub CSP execution failed - baseline (not used).

�Autopilot for Surface Hub CSP execution failed with command state 1 - Unknown error.

�Autopilot for Surface Hub CSP execution failed with command state 2 - Populating Account.

�Autopilot for Surface Hub CSP execution failed with command state 3 - Populating Exchange server address.

�Autopilot for Surface Hub CSP execution failed with command state 4 - Validating Exchange server address.

�Autopilot for Surface Hub CSP execution failed with command state 5 - Saving Account information.

�Autopilot for Surface Hub CSP execution failed with command state 6 - Validating EAS policies.

TAutopilot Device Provisioning failed.

�Autopilot Device Provisioning failed because the primary session was already marked active.

�Autopilot Device Provisioning failed because the primary session was not active.

�Autopilot Device Provisioning failed because the primary session was active with a different session id.

�Autopilot Device Provisioning failed because the underlying device preparation orchestrator has changed.

�Autopilot Device Provisioning failed because the underlying machine provisioning progress reported has changed.

�Autopilot Device Provisioning failed because the machine provisioning progress context is not registered.

�Autopilot Device Provisioning failed because the activation scheme could not find a registered agent.

�Autopilot Device Provisioning failed because the activation scheme could not launch the registered agent.

�Autopilot Device Provisioning failed because the activation scheme is not registered correctly.

�Autopilot Device Provisioning failed because the provisioning agent specified an invalid launch URI.

�Autopilot Device Provisioning object creation failed because the device is not in OOBE.

�Autopilot Device Provisioning object creation failed because the device is not actively in device provisioning mode.

�4VS_VERSION_INFO��
�e
�e?.StringFileInfo
040904B0LCompanyNameMicrosoft CorporationdFileDescriptionETW for Autopilot Diagnosticsh$FileVersion10.0.26100.1 (WinBuild.160101.0800)\InternalNameETW for Autopilot Diagnostics�.LegalCopyright� Microsoft Corporation. All rights reserved.TOriginalFilenameautopilotdiag.dll.muij%ProductNameMicrosoft� Windows� Operating System>
ProductVersion10.0.26100.1DVarFileInfo$Translation	�PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADD

Anon7 - 2021