Microsoft-Windows-Provisioning-Diagnostics-Provider

114 events across 5 channels

Event IDTitleChannel
10Configuring ProvXML with category '.Admin
11ProvXML category '.Admin
12ProvXML category '.Admin
13Setting %1 was ignored because it was not available on this OS build.Admin
20Applying package '.Admin
21Package '.Admin
22Package '.Admin
23Skipping package '.Admin
30Initiating provisioning turn '.Admin
31Provisioning turn '.Admin
32Provisioning turn '.Admin
40Registry specified search path is invalid.Admin
41InitiateSystemShutdownEx succeeded.Admin
42InitiateSystemShutdownEx failed.Admin
43Start RebootSystem.Admin
44InitiateSystemShutdownEx succeeded.Admin
45InitiateSystemShutdownEx failed.Admin
60AddPackage initiated, pathCount = %1.Admin
61AddPackage succeeded, targetPath = %1.Admin
62AddPackage failed.Admin
63RemovePackage initiated, package id = %1.Admin
64RemovePackage succeeded, package id = %1.Admin
65RemovePackage failed.Admin
66RemovePackageMetadata succeeded, package id = %1.Admin
67RemovePackageMetadata failed.Admin
68RemoveResourceManagerPackageMetadataForCsp succeeded, package id = %1.Admin
69RemoveResourceManagerPackageMetadataForCsp failed.Admin
70ApplyKnownPackages initiated, turn = %1.Admin
71ApplyKnownPackages succeeded, turn = %1.Admin
72ApplyKnownPackages failed.Admin
73Operational
73PublishDeviceProvisioningLogs failed.Admin
74Operational
74PublishDeviceProvisioningLogs succeeded.Admin
75Operational
75CleanupOOBEProvisioningLogs failed.Admin
76Operational
76CleanupOOBEProvisioningLogs succeeded.Admin
80GetLastProvisioningResultsAsync succeeded, resultCount = %1.Admin
81GetLastProvisioningResultsAsync failed.Admin
82GetLastProvisioningCommandResultsAsync succeeded, resultCount = %1.Admin
83GetLastProvisioningCommandResultsAsync.Admin
90Settings detail.Admin
91RegisterForCspAlerts succeeded.Admin
92RegisterForCspAlerts Failed.Admin
93UpdatePendingResultInternal succeeded.Admin
94UpdatePendingResultInternal Failed.Admin
100AutoPilot policy [.AutoPilot
101AutoPilotGetPolicyDwordByName succeeded: policy name = %1; policy value = %2.AutoPilot
102AutoPilotGetPolicyDwordByName error: policy name = %2; HRESULT = %1.AutoPilot
103AutoPilotGetPolicyStringByName succeeded: policy name = %1; policy value = %2.AutoPilot
104AutoPilotGetPolicyStringByName error: policy name = %2; HRESULT = %1.AutoPilot
105AutoPilotDisable succeeded.AutoPilot
106AutoPilotDisable error: HRESULT = %1.AutoPilot
107AutoPilot state = %1.AutoPilot
108AutoPilotIsDisabled error: HRESULT = %1.AutoPilot
109AutoPilotGetOobeSettingsOverride succeeded: OOBE setting = %1; state = %2.AutoPilot
110AutoPilotGetOobeSettingsOverride error: OOBE setting = %2; HRESULT = %1.AutoPilot
111AutoPilotRetrieveSettings succeeded.AutoPilot
112AutoPilotRetrieveSettings error: HRESULT = %1.AutoPilot
113AutoPilot reported the DLL was unloaded while there were %1 outstanding calls.AutoPilot
114AutoPilotRetrieveSettings was skipped because this version of Windows does not …AutoPilot
115Autopilot discovery failed to find a valid MDM.AutoPilot
150AutoPilotManager started the MSA service for TPM attestation identity.AutoPilot
151AutoPilotManager started the TPM task to update TPM attestation.AutoPilot
152AutoPilotManager reported TPM task is complete.AutoPilot
153AutoPilotManager reported the state changed from %1 to %2.AutoPilot
154AutoPilotManager failed to start MSA service.AutoPilot
155AutoPilotManager failed to start TPM task.AutoPilot
156AutoPilotManager reported that MSA TPM is not configured for hardware TPM …AutoPilot
157AutoPilotManager reported that TPM attestation lasted %1 microseconds.AutoPilot
160AutoPilotRetrieveSettings beginning acquisition.AutoPilot
161AutoPilotManager retrieve settings succeeded.AutoPilot
162AutoPilotManager determined download is not required and the device is not …AutoPilot
163AutoPilotManager determined download is not required and the device is already …AutoPilot
164AutoPilotManager determined Internet is available to attempt policy download.AutoPilot
165AutoPilotManager determined Internet is not available; policy download will …AutoPilot
166AutoPilotManager reported Internet is now available.AutoPilot
167AutoPilotManager reported Internet is still not available.AutoPilot
168AutoPilotManager reported MSA TPM device identity was updated.AutoPilot
169AutoPilotManager set TPM identity confirmed.AutoPilot
170AutoPilotManager set AutoPilot profile as available.AutoPilot
171AutoPilotManager failed to set TPM identity confirmed.AutoPilot
172AutoPilotManager failed to set AutoPilot profile as available.AutoPilot
173AutoPilotManager failed to register for network availability.AutoPilot
174AutoPilotManager failed to register for device identity availability.AutoPilot
175AutoPilotManager failed to register for device identity task update.AutoPilot
176MSA TPM keystate has been updated.AutoPilot
177TPM attestation retry is being attempted.AutoPilot
178AutoPilotManager began device enrollment with internal state %1.AutoPilot
179AutoPilotManager began device enrollment phase %1.AutoPilot
180AutoPilotManager failed during device enrollment phase %1.AutoPilot
181AutoPilotManager completed device enrollment phase %1.AutoPilot
182AutoPilotManager reported that the retry timer event was set to %1 milliseconds.AutoPilot
183AutoPilotManager reported that the retry timer event occurredAutoPilot
184AutoPilotManager failed to register for MSA keystate update availability.AutoPilot
300AutoPilotManager device enrollment reported an initialization failure.AutoPilot
301AutoPilotManager device enrollment reported a blocking failure.AutoPilot
302AutoPilotManager device enrollment failed during stage %1 with error %2.AutoPilot
303AutoPilotManager device enrollment succeeded.AutoPilot
310AutoPilot configuration file path: %1 Expanded path:%2 File path source:%3.AutoPilot
311Failed to load AutoPilot configuration file, HRESULT = %1.AutoPilot
312Failed to parse AutoPilot configuration file, HRESULT = %1.AutoPilot
313Invalid ZtdCorrelationId found in Autopilot configuration file, HRESULT = %1.AutoPilot
1000Management service starting.ManagementService
1001Management service started.ManagementService
1002Management service failed to start.ManagementService
1003Management service failed to register.ManagementService
1004Management service shutdown.ManagementService
1005Management service WIL error was reported.ManagementService
1006Management service call %1 is deprecated!ManagementService
1007Management service cleared the local Autopilot cached state.ManagementService
1008Management service failed to clear the local Autopilot cached state.ManagementService
2000Device rename has been blocked through MDM because machine is domain joinedManagementService

Event ID 10 — Configuring ProvXML with category '.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin
Level
4
Samples
1

Message

Configuring ProvXML with category '%1'.

ProvXML data:
%2

Fields

NameDescription
Message1
Message2ProvXML data

Example Event

system:
  provider: Microsoft-Windows-Provisioning-Diagnostics-Provider
  guid: ED8B9BD3-F66E-4FF2-B86B-75C7925F72A9
  event_source_name: ''
  event_id: 10
  version: 0
  level: 4
  task: 0
  opcode: 0
  keywords: 9223372036854775808
  time_created: '2023-11-06T06:25:52.831967+00:00'
  event_record_id: 113
  correlation: {}
  execution:
    process_id: 3584
    thread_id: 3588
  channel: Microsoft-Windows-Provisioning-Diagnostics-Provider/Admin
  computer: WinDev2310Eval
  security:
    user_id: S-1-5-18
event_data:
  Message1: PowerSettings
  Message2: MCSF/Power/Controls/EnergyEstimationEnabled
message: ''

References

Event ID 11 — ProvXML category '.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin
Level
4
Samples
1

Message

ProvXML category '%1' completed successfully. %2

Fields

NameDescription
Message1
Message2

Example Event

system:
  provider: Microsoft-Windows-Provisioning-Diagnostics-Provider
  guid: ED8B9BD3-F66E-4FF2-B86B-75C7925F72A9
  event_source_name: ''
  event_id: 11
  version: 0
  level: 4
  task: 0
  opcode: 0
  keywords: 9223372036854775808
  time_created: '2023-11-05T22:26:45.490065+00:00'
  event_record_id: 132
  correlation:
    ActivityID: F590C418-1079-0003-3DF1-90F57910DA01
  execution:
    process_id: 3584
    thread_id: 3588
  channel: Microsoft-Windows-Provisioning-Diagnostics-Provider/Admin
  computer: WinDev2310Eval
  security:
    user_id: S-1-5-18
event_data:
  Message1: PowerSettings
  Message2: Provisioning succeeded
message: ''

References

Event ID 12 — ProvXML category '.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

ProvXML category '%1' failed with '%2' at CSP node '%3'. %4

Fields

NameDescription
Message1
HRESULT
Message2
Message3

Event ID 13 — Setting %1 was ignored because it was not available on this OS build.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

Setting %1 was ignored because it was not available on this OS build

Fields

NameDescription
Message1

Event ID 20 — Applying package '.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin
Level
4
Samples
1

Message

Applying package '%1' ID: %2.

Fields

NameDescription
Message1
Message21' ID.

Example Event

system:
  provider: Microsoft-Windows-Provisioning-Diagnostics-Provider
  guid: ED8B9BD3-F66E-4FF2-B86B-75C7925F72A9
  event_source_name: ''
  event_id: 20
  version: 0
  level: 4
  task: 0
  opcode: 0
  keywords: 9223372036854775808
  time_created: '2023-11-06T06:25:50.949676+00:00'
  event_record_id: 111
  correlation: {}
  execution:
    process_id: 3584
    thread_id: 3588
  channel: Microsoft-Windows-Provisioning-Diagnostics-Provider/Admin
  computer: WinDev2310Eval
  security:
    user_id: S-1-5-18
event_data:
  Message1: Microsoft.Windows.Cosa.Desktop.Client.ppkg
  Message2: '{c8a326e4-f518-4f14-b543-97a57e1a975e}'
message: ''

References

Event ID 21 — Package '.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

Package '%1' has completed.

Fields

NameDescription
Message1

Event ID 22 — Package '.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

Package '%1' failed with '%2'.

Fields

NameDescription
Message1
HRESULT

Event ID 23 — Skipping package '.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

Skipping package '%1' ID: %2.

Fields

NameDescription
Message1
Message2

Event ID 30 — Initiating provisioning turn '.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

Initiating provisioning turn '{Int1}'.

Fields

NameDescription
Int1

Event ID 31 — Provisioning turn '.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

Provisioning turn '{Int1}' has completed.

Fields

NameDescription
Int1

Event ID 32 — Provisioning turn '.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

Provisioning turn '{Int1}' failed with '{HRESULT}'.

Fields

NameDescription
Int1
HRESULT

Event ID 40 — Registry specified search path is invalid.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

Registry specified search path is invalid: %1.

Fields

NameDescription
Message1

Event ID 41 — InitiateSystemShutdownEx succeeded.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

InitiateSystemShutdownEx succeeded.

Event ID 42 — InitiateSystemShutdownEx failed.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

InitiateSystemShutdownEx failed. HRESULT = %1.

Fields

NameDescription
HRESULT

Event ID 43 — Start RebootSystem.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

Start RebootSystem ...

Event ID 44 — InitiateSystemShutdownEx succeeded.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

InitiateSystemShutdownEx succeeded.

Event ID 45 — InitiateSystemShutdownEx failed.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

InitiateSystemShutdownEx failed. HRESULT = %1.

Fields

NameDescription
HRESULT

Event ID 60 — AddPackage initiated, pathCount = %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

AddPackage initiated, pathCount = %1

Fields

NameDescription
UInt1

Event ID 61 — AddPackage succeeded, targetPath = %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

AddPackage succeeded, targetPath = %1

Fields

NameDescription
Message1

Event ID 62 — AddPackage failed.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

AddPackage failed. HRESULT = %1

Fields

NameDescription
HRESULT

Event ID 63 — RemovePackage initiated, package id = %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

RemovePackage initiated, package id = %1

Fields

NameDescription
Message1

Event ID 64 — RemovePackage succeeded, package id = %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

RemovePackage succeeded, package id = %1

Fields

NameDescription
Message1

Event ID 65 — RemovePackage failed.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

RemovePackage failed. HRESULT = %1, package id = %2, at stage = %3

Fields

NameDescription
HRESULT
Message1
Uint1

Event ID 66 — RemovePackageMetadata succeeded, package id = %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

RemovePackageMetadata succeeded, package id = %1

Fields

NameDescription
Message1

Event ID 67 — RemovePackageMetadata failed.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

RemovePackageMetadata failed. HRESULT = %1, package id = %2, at stage = %3

Fields

NameDescription
HRESULT
Message1
Uint1

Event ID 68 — RemoveResourceManagerPackageMetadataForCsp succeeded, package id = %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

RemoveResourceManagerPackageMetadataForCsp succeeded, package id = %1

Fields

NameDescription
Message1

Event ID 69 — RemoveResourceManagerPackageMetadataForCsp failed.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

RemoveResourceManagerPackageMetadataForCsp failed. HRESULT = %1, package id = %2

Fields

NameDescription
HRESULT
Message1

Event ID 70 — ApplyKnownPackages initiated, turn = %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

ApplyKnownPackages initiated, turn = %1

Fields

NameDescription
Int1

Event ID 71 — ApplyKnownPackages succeeded, turn = %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

ApplyKnownPackages succeeded, turn = %1

Fields

NameDescription
Int1

Event ID 72 — ApplyKnownPackages failed.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

ApplyKnownPackages failed. turn = %1, HRESULT = %2

Fields

NameDescription
Int1
HRESULT

Event ID 73 —

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Operational

Fields

NameDescription
HRESULT

Event ID 73 — PublishDeviceProvisioningLogs failed.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

PublishDeviceProvisioningLogs failed. HRESULT = %1

Fields

NameDescription
HRESULT

Event ID 74 —

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Operational

Event ID 74 — PublishDeviceProvisioningLogs succeeded.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

PublishDeviceProvisioningLogs succeeded.

Event ID 75 —

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Operational

Fields

NameDescription
HRESULT

Event ID 75 — CleanupOOBEProvisioningLogs failed.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

CleanupOOBEProvisioningLogs failed. HRESULT = %1

Fields

NameDescription
HRESULT

Event ID 76 —

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Operational

Event ID 76 — CleanupOOBEProvisioningLogs succeeded.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

CleanupOOBEProvisioningLogs succeeded.

Event ID 80 — GetLastProvisioningResultsAsync succeeded, resultCount = %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

GetLastProvisioningResultsAsync succeeded, resultCount = %1

Fields

NameDescription
UInt1

Event ID 81 — GetLastProvisioningResultsAsync failed.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

GetLastProvisioningResultsAsync failed. HRESULT = %1

Fields

NameDescription
HRESULT

Event ID 82 — GetLastProvisioningCommandResultsAsync succeeded, resultCount = %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

GetLastProvisioningCommandResultsAsync succeeded, resultCount = %1

Fields

NameDescription
UInt1

Event ID 83 — GetLastProvisioningCommandResultsAsync.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

GetLastProvisioningCommandResultsAsync. HRESULT = %1

Fields

NameDescription
HRESULT

Event ID 90 — Settings detail.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin
Level
4
Samples
1

Message

Settings detail.
source = %1.
packageIdToDelete = %2.
packagePathsToAdd = %3.

Fields

NameDescription
Message1
Message2
Message3

Example Event

system:
  provider: Microsoft-Windows-Provisioning-Diagnostics-Provider
  guid: ED8B9BD3-F66E-4FF2-B86B-75C7925F72A9
  event_source_name: ''
  event_id: 90
  version: 0
  level: 4
  task: 0
  opcode: 0
  keywords: 9223372036854775808
  time_created: '2023-11-06T06:25:42.966867+00:00'
  event_record_id: 89
  correlation: {}
  execution:
    process_id: 3584
    thread_id: 3588
  channel: Microsoft-Windows-Provisioning-Diagnostics-Provider/Admin
  computer: WinDev2310Eval
  security:
    user_id: S-1-5-18
event_data:
  Message1: OOBE
  Message2: <Not Present>
  Message3: <Not Present>
message: ''

References

Event ID 91 — RegisterForCspAlerts succeeded.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin
Level
4
Samples
1

Message

RegisterForCspAlerts succeeded. EnrollmentId = %1.

Fields

NameDescription
Message1

Example Event

system:
  provider: Microsoft-Windows-Provisioning-Diagnostics-Provider
  guid: ED8B9BD3-F66E-4FF2-B86B-75C7925F72A9
  event_source_name: ''
  event_id: 91
  version: 0
  level: 4
  task: 0
  opcode: 0
  keywords: 9223372036854775808
  time_created: '2023-11-06T06:25:52.831884+00:00'
  event_record_id: 112
  correlation: {}
  execution:
    process_id: 3584
    thread_id: 3588
  channel: Microsoft-Windows-Provisioning-Diagnostics-Provider/Admin
  computer: WinDev2310Eval
  security:
    user_id: S-1-5-18
event_data:
  Message1: '{1e05dd5d-a022-46c5-963c-b20de341170f}'
message: ''

References

Event ID 92 — RegisterForCspAlerts Failed.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

RegisterForCspAlerts Failed. HResult = %1, EnrollmentId = %2.

Fields

NameDescription
HRESULT
Message1

Event ID 93 — UpdatePendingResultInternal succeeded.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

UpdatePendingResultInternal succeeded. PackageId = %1.

Fields

NameDescription
Message1

Event ID 94 — UpdatePendingResultInternal Failed.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
Admin

Message

UpdatePendingResultInternal Failed. HResult = %1, PackageId = %2.

Fields

NameDescription
HRESULT
Message1

Event ID 100 — AutoPilot policy [.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilot policy [%1] not found.

Fields

NameDescription
Message1

Event ID 101 — AutoPilotGetPolicyDwordByName succeeded: policy name = %1; policy value = %2.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotGetPolicyDwordByName succeeded:  policy name = %1; policy value = %2.

Fields

NameDescription
Message1
Int1

Event ID 102 — AutoPilotGetPolicyDwordByName error: policy name = %2; HRESULT = %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotGetPolicyDwordByName error:  policy name = %2; HRESULT = %1.

Fields

NameDescription
HRESULT
Message1

Event ID 103 — AutoPilotGetPolicyStringByName succeeded: policy name = %1; policy value = %2.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotGetPolicyStringByName succeeded:  policy name = %1; policy value = %2.

Fields

NameDescription
Message1
Message2

Event ID 104 — AutoPilotGetPolicyStringByName error: policy name = %2; HRESULT = %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotGetPolicyStringByName error:  policy name = %2; HRESULT = %1.

Fields

NameDescription
HRESULT
Message1

Event ID 105 — AutoPilotDisable succeeded.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotDisable succeeded.

Event ID 106 — AutoPilotDisable error: HRESULT = %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotDisable error:  HRESULT = %1.

Fields

NameDescription
HRESULT

Event ID 107 — AutoPilot state = %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilot state = %1.

Fields

NameDescription
Message1

Event ID 108 — AutoPilotIsDisabled error: HRESULT = %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotIsDisabled error:  HRESULT = %1.

Fields

NameDescription
HRESULT

Event ID 109 — AutoPilotGetOobeSettingsOverride succeeded: OOBE setting = %1; state = %2.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotGetOobeSettingsOverride succeeded:  OOBE setting = %1; state = %2.

Fields

NameDescription
Message1
Message2

Event ID 110 — AutoPilotGetOobeSettingsOverride error: OOBE setting = %2; HRESULT = %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotGetOobeSettingsOverride error:  OOBE setting = %2; HRESULT = %1.

Fields

NameDescription
HRESULT
Message1

Event ID 111 — AutoPilotRetrieveSettings succeeded.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotRetrieveSettings succeeded.

Event ID 112 — AutoPilotRetrieveSettings error: HRESULT = %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotRetrieveSettings error:  HRESULT = %1.

Fields

NameDescription
HRESULT

Event ID 113 — AutoPilot reported the DLL was unloaded while there were %1 outstanding calls.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

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

Fields

NameDescription
Int1

Event ID 114 — AutoPilotRetrieveSettings was skipped because this version of Windows does not support Azure Active Directory join.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

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

Event ID 115 — Autopilot discovery failed to find a valid MDM.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

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

Fields

NameDescription
HRESULT

Event ID 150 — AutoPilotManager started the MSA service for TPM attestation identity.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager started the MSA service for TPM attestation identity.

Event ID 151 — AutoPilotManager started the TPM task to update TPM attestation.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager started the TPM task to update TPM attestation.

Event ID 152 — AutoPilotManager reported TPM task is complete.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager reported TPM task is complete.

Event ID 153 — AutoPilotManager reported the state changed from %1 to %2.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager reported the state changed from %1 to %2.

Fields

NameDescription
InitialState
UpdateState

Event ID 154 — AutoPilotManager failed to start MSA service.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager failed to start MSA service.  HRESULT = %1.

Fields

NameDescription
HRESULT

Event ID 155 — AutoPilotManager failed to start TPM task.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager failed to start TPM task.  HRESULT = %1.

Fields

NameDescription
HRESULT

Event ID 156 — AutoPilotManager reported that MSA TPM is not configured for hardware TPM attestation even though the profile indicates it is required.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

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

Event ID 157 — AutoPilotManager reported that TPM attestation lasted %1 microseconds.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager reported that TPM attestation lasted %1 microseconds.

Fields

NameDescription
UInt1

Event ID 160 — AutoPilotRetrieveSettings beginning acquisition.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotRetrieveSettings beginning acquisition.

Event ID 161 — AutoPilotManager retrieve settings succeeded.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager retrieve settings succeeded.

Event ID 162 — AutoPilotManager determined download is not required and the device is not provisioned.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

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

Event ID 163 — AutoPilotManager determined download is not required and the device is already provisioned.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

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

Event ID 164 — AutoPilotManager determined Internet is available to attempt policy download.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager determined Internet is available to attempt policy download.

Event ID 165 — AutoPilotManager determined Internet is not available; policy download will queue when available.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

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

Event ID 166 — AutoPilotManager reported Internet is now available.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager reported Internet is now available.

Event ID 167 — AutoPilotManager reported Internet is still not available.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager reported Internet is still not available.

Event ID 168 — AutoPilotManager reported MSA TPM device identity was updated.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager reported MSA TPM device identity was updated.

Event ID 169 — AutoPilotManager set TPM identity confirmed.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager set TPM identity confirmed.

Event ID 170 — AutoPilotManager set AutoPilot profile as available.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager set AutoPilot profile as available.

Event ID 171 — AutoPilotManager failed to set TPM identity confirmed.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager failed to set TPM identity confirmed.  HRESULT = %1.

Fields

NameDescription
HRESULT

Event ID 172 — AutoPilotManager failed to set AutoPilot profile as available.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager failed to set AutoPilot profile as available.  HRESULT = %1.

Fields

NameDescription
HRESULT

Event ID 173 — AutoPilotManager failed to register for network availability.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager failed to register for network availability.  HRESULT = %1.

Fields

NameDescription
HRESULT

Event ID 174 — AutoPilotManager failed to register for device identity availability.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

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

Fields

NameDescription
HRESULT

Event ID 175 — AutoPilotManager failed to register for device identity task update.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

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

Fields

NameDescription
HRESULT

Event ID 176 — MSA TPM keystate has been updated.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

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

Fields

NameDescription
Uint1
Uint2

Event ID 177 — TPM attestation retry is being attempted.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

TPM attestation retry is being attempted.  Current retry attempt %1 of %2 maximum

Fields

NameDescription
Uint1
Uint2

Event ID 178 — AutoPilotManager began device enrollment with internal state %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager began device enrollment with internal state %1.

Fields

NameDescription
Int1

Event ID 179 — AutoPilotManager began device enrollment phase %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager began device enrollment phase %1.

Fields

NameDescription
State

Event ID 180 — AutoPilotManager failed during device enrollment phase %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager failed during device enrollment phase %1.  HRESULT = %2

Fields

NameDescription
State
HRESULT

Event ID 181 — AutoPilotManager completed device enrollment phase %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager completed device enrollment phase %1.  HRESULT = %2

Fields

NameDescription
State
HRESULT

Event ID 182 — AutoPilotManager reported that the retry timer event was set to %1 milliseconds.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

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

Fields

NameDescription
UInt1

Event ID 183 — AutoPilotManager reported that the retry timer event occurred

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager reported that the retry timer event occurred

Event ID 184 — AutoPilotManager failed to register for MSA keystate update availability.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

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

Fields

NameDescription
HRESULT

Event ID 300 — AutoPilotManager device enrollment reported an initialization failure.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager device enrollment reported an initialization failure.  HRESULT = %1.

Fields

NameDescription
HRESULT

Event ID 301 — AutoPilotManager device enrollment reported a blocking failure.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

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

Fields

NameDescription
State
HRESULT

Event ID 302 — AutoPilotManager device enrollment failed during stage %1 with error %2.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager device enrollment failed during stage %1 with error %2.

Fields

NameDescription
State
HRESULT

Event ID 303 — AutoPilotManager device enrollment succeeded.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilotManager device enrollment succeeded.  Last valid stage: %1.

Fields

NameDescription
State

Event ID 310 — AutoPilot configuration file path: %1 Expanded path:%2 File path source:%3.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

AutoPilot configuration file path: %1 
Expanded path:%2 
File path source:%3

Fields

NameDescription
AutoPilot_configuration_file_path
Expanded_path
File_path_source
Message1
Message2
Message3

Event ID 311 — Failed to load AutoPilot configuration file, HRESULT = %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

Failed to load AutoPilot configuration file, HRESULT = %1.

Fields

NameDescription
HRESULT

Event ID 312 — Failed to parse AutoPilot configuration file, HRESULT = %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

Failed to parse AutoPilot configuration file, HRESULT = %1.

Fields

NameDescription
HRESULT

Event ID 313 — Invalid ZtdCorrelationId found in Autopilot configuration file, HRESULT = %1.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
AutoPilot

Message

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

Fields

NameDescription
HRESULT
Message1

Event ID 1000 — Management service starting.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
ManagementService

Message

Management service starting.

Event ID 1001 — Management service started.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
ManagementService

Message

Management service started.

Event ID 1002 — Management service failed to start.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
ManagementService

Message

Management service failed to start.  HRESULT = %1

Fields

NameDescription
HRESULT

Event ID 1003 — Management service failed to register.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
ManagementService

Message

Management service failed to register.

Event ID 1004 — Management service shutdown.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
ManagementService

Message

Management service shutdown.

Event ID 1005 — Management service WIL error was reported.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
ManagementService

Message

Management service WIL error was reported.
HRESULT: %1
File: %2, line %3
Message: %4

Fields

NameDescription
HRESULT
File
Message
Line

Event ID 1006 — Management service call %1 is deprecated!

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
ManagementService

Message

Management service call %1 is deprecated!

Fields

NameDescription
Message1

Event ID 1007 — Management service cleared the local Autopilot cached state.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
ManagementService

Message

Management service cleared the local Autopilot cached state.

Event ID 1008 — Management service failed to clear the local Autopilot cached state.

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
ManagementService

Message

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

Fields

NameDescription
HRESULT

Event ID 2000 — Device rename has been blocked through MDM because machine is domain joined

Provider
Microsoft-Windows-Provisioning-Diagnostics-Provider
Channel
ManagementService

Message

Device rename has been blocked through MDM because machine is domain joined