| 500 | Diagnostic Policy Service |
Diagnostic Policy Service |
| 501 | The Diagnostic Policy Service enables problem detection, troubleshooting and resolution for Windows components. If this service is stopped, diagnostics will no longer function. |
The Diagnostic Policy Service enables problem detection, troubleshooting and resolution for Windows components. If this service is stopped, diagnostics will no longer function. |
| 600 | Microsoft Corporation |
Microsoft Corporation |
| 602 | The Windows Diagnostic Infrastructure Resolution host enables interactive resolutions for system problems detected by the Diagnostic Policy Service. It is triggered when necessary by the Diagnostic Policy Service in the appropriate user session. If the Diagnostic Policy Service is not running, the task will not run |
The Windows Diagnostic Infrastructure Resolution host enables interactive resolutions for system problems detected by the Diagnostic Policy Service. It is triggered when necessary by the Diagnostic Policy Service in the appropriate user session. If the Diagnostic Policy Service is not running, the task will not run |
| 0x1000000A | Memory tracing events |
Memory tracing events |
| 0x10000021 | Timing Events |
Timing Events |
| 0x10000022 | Scenario trigger events |
Scenario trigger events |
| 0x10000023 | Debug events |
Debug events |
| 0x10000024 | Scenario lifecycle events |
Scenario lifecycle events |
| 0x10000025 | Diagnostic Module notification events |
Diagnostic Module notification events |
| 0x3000000A | The Diagnostic Policy Service started |
The Diagnostic Policy Service started |
| 0x3000000B | A diagnostic scenario was misconfigured |
A diagnostic scenario was misconfigured |
| 0x3000000C | A diagnostic module detected a problem |
A diagnostic module detected a problem |
| 0x3000000D | A scenario instance was dispatched for troubleshooting |
A scenario instance was dispatched for troubleshooting |
| 0x3000000E | A diagnostic module completed troubleshooting without setting a resolution |
A diagnostic module completed troubleshooting without setting a resolution |
| 0x3000000F | A diagnostic module completed troubleshooting and set an immediate resolution |
A diagnostic module completed troubleshooting and set an immediate resolution |
| 0x30000010 | A diagnostic module finished troubleshooting and set an queued resolution |
A diagnostic module finished troubleshooting and set an queued resolution |
| 0x30000011 | A scenario instance was dispatched for resolution |
A scenario instance was dispatched for resolution |
| 0x30000012 | A diagnostic module queued itself for later invocation |
A diagnostic module queued itself for later invocation |
| 0x30000013 | A diagnostic module completed resolution |
A diagnostic module completed resolution |
| 0x30000014 | The Diagnostic Policy Service was not able to instantiate a diagnostic module host |
The Diagnostic Policy Service was not able to instantiate a diagnostic module host |
| 0x30000015 | This event is raised when a scenario fails |
This event is raised when a scenario fails |
| 0x30000016 | A diagnostic module was moved to a broken state |
A diagnostic module was moved to a broken state |
| 0x30000017 | Debug event |
Debug event |
| 0x30000018 | This event is raised at the ServiceMain for the service |
This event is raised at the ServiceMain for the service |
| 0x30000019 | This event is raised when the DPS signals its status as RUNNING to the SCM |
This event is raised when the DPS signals its status as RUNNING to the SCM |
| 0x3000001A | This event is raised when the service receives a shutdown/stop notification from the SCM |
This event is raised when the service receives a shutdown/stop notification from the SCM |
| 0x3000001B | This event is raised when the service is successfully stopped |
This event is raised when the service is successfully stopped |
| 0x3000001C | This event is raised when DPS refreshes group policy |
This event is raised when DPS refreshes group policy |
| 0x50000002 | Error |
Error |
| 0x50000003 | Warning |
Warning |
| 0x50000004 | Information |
Information |
| 0x50000005 | Verbose |
Verbose |
| 0x70000001 | Scenario Lifecycle |
Scenario Lifecycle |
| 0x70000002 | Debug task |
Debug task |
| 0x70000003 | DPS Initialization |
DPS Initialization |
| 0x70000004 | Notification task |
Notification task |
| 0x90000001 | Microsoft-Windows-Diagnosis-DPS |
Microsoft-Windows-Diagnosis-DPS |
| 0x90000002 | Microsoft-Windows-Diagnosis-DPS/Debug |
Microsoft-Windows-Diagnosis-DPS/Debug |
| 0x90000003 | Microsoft-Windows-Diagnosis-DPS/Operational |
Microsoft-Windows-Diagnosis-DPS/Operational |
| 0x90000004 | Microsoft-Windows-Diagnosis-DPS/Analytic |
Microsoft-Windows-Diagnosis-DPS/Analytic |
| 0x91000001 | Microsoft-Windows-Diagnosis-WDI |
Microsoft-Windows-Diagnosis-WDI |
| 0x91000002 | Microsoft-Windows-Diagnosis-WDI/Debug |
Microsoft-Windows-Diagnosis-WDI/Debug |
| 0xB0000001 | The Diagnostic Policy Service started. This event signals diagnostic modules for delayed processing after the service is initialized. |
The Diagnostic Policy Service started. This event signals diagnostic modules for delayed processing after the service is initialized. |
| 0xB0000002 | The Diagnostic Policy Service started. This event signals diagnostic modules for immediate processing after the service is initialized. |
The Diagnostic Policy Service started. This event signals diagnostic modules for immediate processing after the service is initialized. |
| 0xB0000005 | The scenario %1 has a configuration error or has been explicitly disabled in the WDI registry namespace. The Diagnostic Policy Service will ignore the scenario. |
The scenario %1 has a configuration error or has been explicitly disabled in the WDI registry namespace. The Diagnostic Policy Service will ignore the scenario. |
| 0xB0000064 | Diagnostic module %5 (%4) detected a problem for scenario %1, instance %2, original activity ID %3. |
Diagnostic module %5 (%4) detected a problem for scenario %1, instance %2, original activity ID %3. |
| 0xB0000069 | Diagnostic module %5 (%4) started troubleshooting scenario %1, instance %2, original activity ID %3. |
Diagnostic module %5 (%4) started troubleshooting scenario %1, instance %2, original activity ID %3. |
| 0xB000006E | Diagnostic module %5 (%4) finished troubleshooting scenario %1, instance %2, original activity ID %3. No resolution was set by the diagnostic module. |
Diagnostic module %5 (%4) finished troubleshooting scenario %1, instance %2, original activity ID %3. No resolution was set by the diagnostic module. |
| 0xB0000073 | Diagnostic module %9 (%4) finished troubleshooting scenario %1, instance %2, original activity ID %3. It set resolution %5 for user %6 in session %7 with expiration date %8. The resolution will be started immediately. |
Diagnostic module %9 (%4) finished troubleshooting scenario %1, instance %2, original activity ID %3. It set resolution %5 for user %6 in session %7 with expiration date %8. The resolution will be started immediately. |
| 0xB0000078 | Diagnostic module %9 (%4) finished troubleshooting scenario %1, instance %2, original activity ID %3. It set resolution %5 for user %6 in session %7 with expiration date %8. The resolution was queued to start later. |
Diagnostic module %9 (%4) finished troubleshooting scenario %1, instance %2, original activity ID %3. It set resolution %5 for user %6 in session %7 with expiration date %8. The resolution was queued to start later. |
| 0xB000007D | Diagnostic module %5 (%4) started resolving scenario %1, instance %2, original activity ID %3. |
Diagnostic module %5 (%4) started resolving scenario %1, instance %2, original activity ID %3. |
| 0xB000007E | Diagnostic module %5 (%4) was queued to start later for scenario %1, instance %2, original activity ID %3. |
Diagnostic module %5 (%4) was queued to start later for scenario %1, instance %2, original activity ID %3. |
| 0xB0000082 | Diagnostic module %5 (%4) finished resolving scenario %1, instance %2, original activity ID %3. |
Diagnostic module %5 (%4) finished resolving scenario %1, instance %2, original activity ID %3. |
| 0xB0000087 | The Diagnostic Policy Service could not create a diagnostic module host instance for diagnostic module %6 (%5). The error code was %4. The scenario %1, instance %2, original activity ID %3 will be discarded. |
The Diagnostic Policy Service could not create a diagnostic module host instance for diagnostic module %6 (%5). The error code was %4. The scenario %1, instance %2, original activity ID %3 will be discarded. |
| 0xB000008C | The Diagnostic Policy Service encountered an error in file %1, function %2, line %3: %4. |
The Diagnostic Policy Service encountered an error in file %1, function %2, line %3: %4. |
| 0xB0000091 | This event is raised when the SCM loads the service DLL |
This event is raised when the SCM loads the service DLL |
| 0xB0000096 | This event is raised when the service enters a SERVICE_RUNNING state |
This event is raised when the service enters a SERVICE_RUNNING state |
| 0xB000009B | This event is raised when the SCM signals the service to shut down. |
This event is raised when the SCM signals the service to shut down. |
| 0xB00000A5 | The Diagnostic Policy Service encountered an error while handling scenario %1 with diagnostic module %6 (%5), instance %2, original activity ID %3. The error code was %4. |
The Diagnostic Policy Service encountered an error while handling scenario %1 with diagnostic module %6 (%5), instance %2, original activity ID %3. The error code was %4. |
| 0xB00000AA | Diagnostic module %6 (%4) encountered an error while handling scenario %1, instance %2, original activity ID %3. The error code was %5. |
Diagnostic module %6 (%4) encountered an error while handling scenario %1, instance %2, original activity ID %3. The error code was %5. |
| 0xB00000AF | Scenario %1, instance %2, original activity ID %3 was dropped by diagnostic module %6 (%4). The error code was %5. |
Scenario %1, instance %2, original activity ID %3 was dropped by diagnostic module %6 (%4). The error code was %5. |
| 0xB00000B4 | The Diagnostic Policy Service just refreshed the Group Policy. This event notifies the diagnostic modules about the Group Policy changes. |
The Diagnostic Policy Service just refreshed the Group Policy. This event notifies the diagnostic modules about the Group Policy changes. |
| 0xB00000B9 | Diagnostic module %2 (%1) was moved into a broken state. The error code was %3. |
Diagnostic module %2 (%1) was moved into a broken state. The error code was %3. |
| 0xB0001398 | The Diagnostic Policy Service just made a heap allocation |
The Diagnostic Policy Service just made a heap allocation |
| 0xB0001399 | The Diagnostic Policy Service just freed a previously made heap allocation |
The Diagnostic Policy Service just freed a previously made heap allocation |
| 0xB1001398 | The Diagnostic Infrastructure just made a heap allocation |
The Diagnostic Infrastructure just made a heap allocation |
| 0xB1001399 | The Diagnostic Infrastructure just freed a previously made heap allocation |
The Diagnostic Infrastructure just freed a previously made heap allocation |