Microsoft-Windows-Hyper-V-Debug

22 events across 3 channels

Event ID	Title	Channel
1500		Operational
1500	[Virtual machine %3] %1.	Microsoft-Windows-Hyper-V-Worker-Analytic
1510		Operational
1510	[Virtual machine %3] %1.	Microsoft-Windows-Hyper-V-Worker-Analytic
1520		Operational
1520	[Virtual machine %3] %1.	Microsoft-Windows-Hyper-V-Worker-Analytic
1530		Operational
1530	[Virtual machine %3] %1.	Microsoft-Windows-Hyper-V-Worker-Analytic
23015		Operational
23015	Virtual machine '.	Microsoft-Windows-Hyper-V-Worker-Admin
23016		Operational
23016	Virtual machine '.	Microsoft-Windows-Hyper-V-Worker-Admin
23017		Operational
23017	Virtual machine '.	Microsoft-Windows-Hyper-V-Worker-Admin
23018		Operational
23018	Virtual machine '.	Microsoft-Windows-Hyper-V-Worker-Admin
23019		Operational
23019	Virtual machine '.	Microsoft-Windows-Hyper-V-Worker-Admin
23020		Operational
23020	The virtual machine %1 cannot load device %3 because there are no mutually …	Microsoft-Windows-Hyper-V-Worker-Admin
23021		Operational
23021	The device %3 cannot be loaded because there are no mutually support protocol …	Microsoft-Windows-Hyper-V-Worker-Admin

Event ID 1500 —

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Operational

Fields

Name	Description
`TraceData`	—
`VmName`	—
`VmId`	—
`StackFrameCount`	—
`StackFrame`	—
`ModuleCount`	—
`Module`	—

Event ID 1500 — [Virtual machine %3] %1.

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Microsoft-Windows-Hyper-V-Worker-Analytic

Message

[Virtual machine %3] %1

Fields

Name	Description
`TraceData`	—
`VmName`	—
`VmId`	—
`StackFrameCount`	—
`StackFrame`	—
`ModuleCount`	—
`Module`	—

Event ID 1510 —

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Operational

Fields

Name	Description
`TraceData`	—
`VmName`	—
`VmId`	—
`StackFrameCount`	—
`StackFrame`	—
`ModuleCount`	—
`Module`	—

Event ID 1510 — [Virtual machine %3] %1.

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Microsoft-Windows-Hyper-V-Worker-Analytic

Message

[Virtual machine %3] %1

Fields

Name	Description
`TraceData`	—
`VmName`	—
`VmId`	—
`StackFrameCount`	—
`StackFrame`	—
`ModuleCount`	—
`Module`	—

Event ID 1520 —

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Operational

Fields

Name	Description
`TraceData`	—
`VmName`	—
`VmId`	—
`StackFrameCount`	—
`StackFrame`	—
`ModuleCount`	—
`Module`	—

Event ID 1520 — [Virtual machine %3] %1.

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Microsoft-Windows-Hyper-V-Worker-Analytic

Message

[Virtual machine %3] %1

Fields

Name	Description
`TraceData`	—
`VmName`	—
`VmId`	—
`StackFrameCount`	—
`StackFrame`	—
`ModuleCount`	—
`Module`	—

Event ID 1530 —

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Operational

Fields

Name	Description
`TraceData`	—
`VmName`	—
`VmId`	—
`StackFrameCount`	—
`StackFrame`	—
`ModuleCount`	—
`Module`	—

Event ID 1530 — [Virtual machine %3] %1.

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Microsoft-Windows-Hyper-V-Worker-Analytic

Message

[Virtual machine %3] %1

Fields

Name	Description
`TraceData`	—
`VmName`	—
`VmId`	—
`StackFrameCount`	—
`StackFrame`	—
`ModuleCount`	—
`Module`	—

Event ID 23015 —

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Operational

Fields

Name	Description
`VmName`	—
`Parameter0`	—

Event ID 23015 — Virtual machine '.

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Microsoft-Windows-Hyper-V-Worker-Admin

Message

Virtual machine '%1' cannot assign the UDP port %2 to the synthetic debug device because is in use by another program.

Fields

Name	Description
`VmName`	—
`Parameter0`	—

Event ID 23016 —

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Operational

Fields

Name	Description
`VmName`	—
`Parameter0`	—

Event ID 23016 — Virtual machine '.

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Microsoft-Windows-Hyper-V-Worker-Admin

Message

Virtual machine '%1' cannot assign the UDP port %2 to the synthetic debug device because is not a valid port.

Fields

Name	Description
`VmName`	—
`Parameter0`	—

Event ID 23017 —

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Operational

Fields

Name	Description
`VmName`	—
`Parameter0`	—

Event ID 23017 — Virtual machine '.

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Microsoft-Windows-Hyper-V-Worker-Admin

Message

Virtual machine '%1' the synthetic debug device DebugPortEnabled value %2 is not valid.

Fields

Name	Description
`VmName`	—
`Parameter0`	—

Event ID 23018 —

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Operational

Fields

Name	Description
`VmName`	—
`Parameter0`	—

Event ID 23018 — Virtual machine '.

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Microsoft-Windows-Hyper-V-Worker-Admin

Message

Virtual machine '%1' the synthetic debug device failed to configure the UDP port. Error %2.

Fields

Name	Description
`VmName`	—
`Parameter0`	—

Event ID 23019 —

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Operational

Fields

Name	Description
`VmName`	—
`Parameter0`	—

Event ID 23019 — Virtual machine '.

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Microsoft-Windows-Hyper-V-Worker-Admin

Message

Virtual machine '%1' the synthetic debug device failed to write to the repository. Error %2.

Fields

Name	Description
`VmName`	—
`Parameter0`	—

Event ID 23020 —

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Operational

Fields

Name	Description
`VmName`	—
`VmId`	—
`Device`	—
`ServerVersion`	—
`ClientVersion`	—

Event ID 23020 — The virtual machine %1 cannot load device %3 because there are no mutually supported protocol versions.

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Microsoft-Windows-Hyper-V-Worker-Admin

Message

The virtual machine %1 cannot load device %3 because there are no mutually supported protocol versions. The server version is %4 and the client version is %5 (Virtual machine ID %2).

Fields

Name	Description
`VmName`	—
`VmId`	—
`Device`	—
`ServerVersion`	—
`ClientVersion`	—

Event ID 23021 —

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Operational

Fields

Name	Description
`VmName`	—
`VmId`	—
`Device`	—
`ServerVersion`	—
`ClientVersion`	—

Event ID 23021 — The device %3 cannot be loaded because there are no mutually support protocol versions between the server and client.

Provider: Microsoft-Windows-Hyper-V-Debug
Channel: Microsoft-Windows-Hyper-V-Worker-Admin

Message

The device %3 cannot be loaded because there are no mutually support protocol versions between the server and client.

Fields

Name	Description
`VmName`	—
`VmId`	—
`Device`	—
`ServerVersion`	—
`ClientVersion`	—