Microsoft-Windows-Hyper-V-Chipset

76 events across 4 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
1540		Operational
1540	[Virtual machine %3] %1.	Microsoft-Windows-Hyper-V-Worker-Operational
1550		Operational
1550	[Virtual machine %3] %1.	Microsoft-Windows-Hyper-V-Worker-Operational
1560		Operational
1560	[Virtual machine %3] %1.	Microsoft-Windows-Hyper-V-Worker-Operational
1570		Operational
1570	[Virtual machine %3] %1.	Microsoft-Windows-Hyper-V-Worker-Operational
12530		Operational
12530	'.	Microsoft-Windows-Hyper-V-Worker-Admin
12531		Operational
12531	Device %3 could not allocate guest physical address space.	Microsoft-Windows-Hyper-V-Worker-Admin
12722		Operational
12722	The SMBIOS tables contain data for CPU information that is not valid.	Microsoft-Windows-Hyper-V-Worker-Admin
12723		Operational
12723	The SMBIOS tables contain data for CPU information that is not valid.	Microsoft-Windows-Hyper-V-Worker-Admin
12724		Operational
12724	The virtual machine '.	Microsoft-Windows-Hyper-V-Worker-Admin
12725		Operational
12725	The virtual machine '.	Microsoft-Windows-Hyper-V-Worker-Admin
12730		Operational
12730	The virtual machine '.	Microsoft-Windows-Hyper-V-Worker-Admin
12731		Operational
12731	The virtual machine '.	Microsoft-Windows-Hyper-V-Worker-Admin
18600		Operational
18600	'.	Microsoft-Windows-Hyper-V-Worker-Admin
18601		Operational
18601	'.	Microsoft-Windows-Hyper-V-Worker-Admin
18602		Operational
18602	'.	Microsoft-Windows-Hyper-V-Worker-Admin
18603		Operational
18603	'.	Microsoft-Windows-Hyper-V-Worker-Admin
18604		Operational
18604	'.	Microsoft-Windows-Hyper-V-Worker-Admin
18605		Operational
18605	'.	Microsoft-Windows-Hyper-V-Worker-Admin
18606		Operational
18606	'.	Microsoft-Windows-Hyper-V-Worker-Admin
18607		Operational
18607	'.	Microsoft-Windows-Hyper-V-Worker-Admin
18608		Operational
18608	The virtual machine %1 cannot load device %3 because there are no mutually …	Microsoft-Windows-Hyper-V-Worker-Admin
18609		Operational
18609	The device %3 cannot be loaded because there are no mutually support protocol …	Microsoft-Windows-Hyper-V-Worker-Admin
18610		Operational
18610	'.	Microsoft-Windows-Hyper-V-Worker-Admin
18611		Operational
18611	'.	Microsoft-Windows-Hyper-V-Worker-Admin
18612		Operational
18612	'.	Microsoft-Windows-Hyper-V-Worker-Admin
18613		Operational
18613	'.	Microsoft-Windows-Hyper-V-Worker-Admin
18614		Operational
18614	'.	Microsoft-Windows-Hyper-V-Worker-Admin
18615		Operational
18615	'.	Microsoft-Windows-Hyper-V-Worker-Admin
18616		Operational
18616	'.	Microsoft-Windows-Hyper-V-Worker-Admin
18617		Operational
18617	'.	Microsoft-Windows-Hyper-V-Worker-Admin
18618		Operational
18618	'.	Microsoft-Windows-Hyper-V-Worker-Admin
18620		Operational
18620	'.	Microsoft-Windows-Hyper-V-Worker-Admin
18622		Operational
18622	'.	Microsoft-Windows-Hyper-V-Worker-Admin
18624		Operational
18624	'.	Microsoft-Windows-Hyper-V-Worker-Admin

Event ID 1500 —

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

Fields

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

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

Provider: Microsoft-Windows-Hyper-V-Chipset
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-Chipset
Channel: Operational

Fields

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

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

Provider: Microsoft-Windows-Hyper-V-Chipset
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-Chipset
Channel: Operational

Fields

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

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

Provider: Microsoft-Windows-Hyper-V-Chipset
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-Chipset
Channel: Operational

Fields

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

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

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

Message

[Virtual machine %3] %1

Fields

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

Event ID 1540 —

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

Fields

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

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

Provider: Microsoft-Windows-Hyper-V-Chipset
Channel: Microsoft-Windows-Hyper-V-Worker-Operational

Message

[Virtual machine %3] %1

Fields

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

Event ID 1550 —

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

Fields

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

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

Provider: Microsoft-Windows-Hyper-V-Chipset
Channel: Microsoft-Windows-Hyper-V-Worker-Operational

Message

[Virtual machine %3] %1

Fields

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

Event ID 1560 —

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

Fields

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

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

Provider: Microsoft-Windows-Hyper-V-Chipset
Channel: Microsoft-Windows-Hyper-V-Worker-Operational

Message

[Virtual machine %3] %1

Fields

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

Event ID 1570 —

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

Fields

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

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

Provider: Microsoft-Windows-Hyper-V-Chipset
Channel: Microsoft-Windows-Hyper-V-Worker-Operational

Message

[Virtual machine %3] %1

Fields

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

Event ID 12530 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—
`Device`	—

Event ID 12530 — '.

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

Message

'%1' device %3 could not allocate guest physical address space. (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—
`Device`	—

Event ID 12531 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—
`Device`	—

Event ID 12531 — Device %3 could not allocate guest physical address space.

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

Message

Device %3 could not allocate guest physical address space.

Fields

Name	Description
`VmName`	—
`VmId`	—
`Device`	—

Event ID 12722 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—
`String`	—
`ErrorCodeString`	—
`ErrorCode`	—
`Param1`	—
`Param2`	—

Event ID 12722 — The SMBIOS tables contain data for CPU information that is not valid.

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

Message

The SMBIOS tables contain data for CPU information that is not valid. Please contact your computer manufacturer for a BIOS update.

Fields

Name	Description
`VmName`	—
`VmId`	—
`String`	—
`ErrorCodeString`	—
`ErrorCode`	—
`Param1`	—
`Param2`	—

Event ID 12723 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—
`String`	—
`ErrorCodeString`	—
`ErrorCode`	—
`Param1`	—
`Param2`	—

Event ID 12723 — The SMBIOS tables contain data for CPU information that is not valid.

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

Message

The SMBIOS tables contain data for CPU information that is not valid. Please contact your computer manufacturer for a BIOS update.

Fields

Name	Description
`VmName`	—
`VmId`	—
`String`	—
`ErrorCodeString`	—
`ErrorCode`	—
`Param1`	—
`Param2`	—

Event ID 12724 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 12724 — The virtual machine '.

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

Message

The virtual machine '%1' cannot start because secure boot is off. Enable secure boot to start a shielded virtual machine. (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 12725 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 12725 — The virtual machine '.

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

Message

The virtual machine '%1' cannot start because secure boot is off.

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 12730 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—
`ErrorMessage`	—
`ErrorCode`	—
`Parameter0`	—

Event ID 12730 — The virtual machine '.

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

Message

The virtual machine '%1' cannot open file '%5': %3 (%4) (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—
`ErrorMessage`	—
`ErrorCode`	—
`Parameter0`	—

Event ID 12731 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—
`ErrorMessage`	—
`ErrorCode`	—
`Parameter0`	—

Event ID 12731 — The virtual machine '.

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

Message

The virtual machine '%1' cannot open file '%5': %3 (%4)

Fields

Name	Description
`VmName`	—
`VmId`	—
`ErrorMessage`	—
`ErrorCode`	—
`Parameter0`	—

Event ID 18600 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18600 — '.

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

Message

'%1' has encountered a watchdog timeout and was reset. If the problem persists, contact Product Support for the guest operating system. (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18601 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—
`BootSourceCount`	—
`BootSourceResult`	—

Event ID 18601 — '.

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

Message

'%1' successfully booted an operating system. (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—
`BootSourceCount`	—
`BootSourceResult`	—

Event ID 18602 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—
`BootSourceCount`	—
`BootSourceResult`	—

Event ID 18602 — '.

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

Message

'%1' successfully booted an operating system, but at least one boot source failed secure boot validation. (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—
`BootSourceCount`	—
`BootSourceResult`	—

Event ID 18603 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—
`BootSourceCount`	—
`BootSourceResult`	—

Event ID 18603 — '.

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

Message

'%1' failed to boot an operating system. (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—
`BootSourceCount`	—
`BootSourceResult`	—

Event ID 18604 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—
`BootSourceCount`	—
`BootSourceResult`	—

Event ID 18604 — '.

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

Message

'%1' failed to boot an operating system. At least one boot source failed secure boot validation. (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—
`BootSourceCount`	—
`BootSourceResult`	—

Event ID 18605 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—
`BootSourceCount`	—
`BootSourceResult`	—

Event ID 18605 — '.

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

Message

'%1' No bootable devices are configured. Use Hyper-V Manager to configure a bootable device. (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—
`BootSourceCount`	—
`BootSourceResult`	—

Event ID 18606 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—
`BootSourceCount`	—
`BootSourceResult`	—

Event ID 18606 — '.

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

Message

'%1' is attempting to boot an operating system. (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—
`BootSourceCount`	—
`BootSourceResult`	—

Event ID 18607 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18607 — '.

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

Message

'%1' was unable to exit UEFI boot services. (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18608 —

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

Fields

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

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

Provider: Microsoft-Windows-Hyper-V-Chipset
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 18609 —

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

Fields

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

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

Provider: Microsoft-Windows-Hyper-V-Chipset
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`	—

Event ID 18610 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18610 — '.

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

Message

'%1' failed to initialize due to a failure in attestation and key release. (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18611 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18611 — '.

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

Message

'%1' cleared VM guest state due to a configuration change. (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18612 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18612 — '.

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

Message

'%1' VM guest state initialization failed. (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18613 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18613 — '.

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

Message

'%1' cleared VM guest state due to invalid data. (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18614 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18614 — '.

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

Message

'%1' cleared VM guest state due to corrupt data. (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18615 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18615 — '.

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

Message

'%1' VM guest state encryption key not released. (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18616 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18616 — '.

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

Message

'%1' failed to decrypt VM guest state disk encryption key. (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18617 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18617 — '.

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

Message

'%1' has encountered a watchdog timeout and was reset. If the problem persists, contact Product Support for the guest operating system. (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18618 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—
`ErrorMessage`	—
`ErrorCode`	—
`Status`	—
`ResultDocument`	—

Event ID 18618 — '.

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

Message

'%1' failed while applying management VTL settings: %6. (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—
`ErrorMessage`	—
`ErrorCode`	—
`Status`	—
`ResultDocument`	—

Event ID 18620 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—
`ErrorMessage`	—
`ErrorCode`	—
`Status`	—
`ResultDocument`	—

Event ID 18620 — '.

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

Message

'%1' failed in the management VTL before starting guest VTL0: %6. (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—
`ErrorMessage`	—
`ErrorCode`	—
`Status`	—
`ResultDocument`	—

Event ID 18622 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18622 — '.

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

Message

'%1' has firmware debugging enabled and cannot be started without COM1 configured. (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—

Event ID 18624 —

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

Fields

Name	Description
`VmName`	—
`VmId`	—
`ErrorMessage`	—
`ErrorCode`	—
`Parameter0`	—

Event ID 18624 — '.

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

Message

'%1' cannot be started because the firmware resource DLL failed to load: %3 (%4). (Virtual machine ID %2)

Fields

Name	Description
`VmName`	—
`VmId`	—
`ErrorMessage`	—
`ErrorCode`	—
`Parameter0`	—