Microsoft-Windows-Hyper-V-Virtual-PMEM

20 events across 3 channels

Event	Title	Channel
1	[VMID VmId]	Operational
1	[VMID VmId] TraceData.	Microsoft-Windows-Hyper-V-Worker-Analytic
2	[VMID VmId]	Operational
2	[VMID VmId] TraceData.	Microsoft-Windows-Hyper-V-Worker-Analytic
3	[VMID VmId]	Operational
3	[VMID VmId] TraceData.	Microsoft-Windows-Hyper-V-Worker-Analytic
4	[VMID VmId]	Operational
4	[VMID VmId] TraceData.	Microsoft-Windows-Hyper-V-Worker-Analytic
10	'VmName': Virtual PMEM device 'Locator' is mapped into virtual machine address …	Operational
10	'VmName': Virtual PMEM device 'Locator' is mapped into virtual machine address …	Microsoft-Windows-Hyper-V-Worker-Admin
11	'VmName': Virtual PMEM device 'String' failed to start	Operational
11	'VmName': Virtual PMEM device 'String' failed to start.	Microsoft-Windows-Hyper-V-Worker-Admin
12	'VmName': Saving, live-migrating or creating a checkpoint of a virtual machine …	Operational
12	'VmName': Saving, live-migrating or creating a checkpoint of a virtual machine …	Microsoft-Windows-Hyper-V-Worker-Admin
13	'VmName': Virtual PMEM device 'String' must be located on a DAX-enabled volume …	Operational
13	'VmName': Virtual PMEM device 'String' must be located on a DAX-enabled volume …	Microsoft-Windows-Hyper-V-Worker-Admin
14	'VmName': This virtual machine has been configured with a virtual PMEM device	Operational
14	'VmName': This virtual machine has been configured with a virtual PMEM device.	Microsoft-Windows-Hyper-V-Worker-Admin
15	'VmName': This virtual machine has been configured with a Physically backed PMEM …	Operational
15	'VmName': This virtual machine has been configured with a Physically backed PMEM …	Microsoft-Windows-Hyper-V-Worker-Admin

Event ID 1: [VMID VmId]

Provider: Microsoft-Windows-Hyper-V-Virtual-PMEM
Channel: Operational

Fields #

Name	Description
`TraceData` UnicodeString
`VmName` UnicodeString
`VmId` UnicodeString
`StackFrameCount` UInt32
`StackFrame` Pointer
`ModuleCount` UInt32
`Module` Int32

Event ID 1: [VMID VmId] TraceData.

Provider: Microsoft-Windows-Hyper-V-Virtual-PMEM
Channel: Microsoft-Windows-Hyper-V-Worker-Analytic

Message #

[VMID %3] %1

Fields #

Name	Description
`TraceData` UnicodeString
`VmName` UnicodeString
`VmId` UnicodeString
`StackFrameCount` UInt32
`StackFrame` Pointer
`ModuleCount` UInt32
`Module` Int32

Event ID 2: [VMID VmId]

Provider: Microsoft-Windows-Hyper-V-Virtual-PMEM
Channel: Operational

Fields #

Name	Description
`TraceData` UnicodeString
`VmName` UnicodeString
`VmId` UnicodeString
`StackFrameCount` UInt32
`StackFrame` Pointer
`ModuleCount` UInt32
`Module` Int32

Event ID 2: [VMID VmId] TraceData.

Provider: Microsoft-Windows-Hyper-V-Virtual-PMEM
Channel: Microsoft-Windows-Hyper-V-Worker-Analytic

Message #

[VMID %3] %1

Fields #

Name	Description
`TraceData` UnicodeString
`VmName` UnicodeString
`VmId` UnicodeString
`StackFrameCount` UInt32
`StackFrame` Pointer
`ModuleCount` UInt32
`Module` Int32

Event ID 3: [VMID VmId]

Provider: Microsoft-Windows-Hyper-V-Virtual-PMEM
Channel: Operational

Fields #

Name	Description
`TraceData` UnicodeString
`VmName` UnicodeString
`VmId` UnicodeString
`StackFrameCount` UInt32
`StackFrame` Pointer
`ModuleCount` UInt32
`Module` Int32

Event ID 3: [VMID VmId] TraceData.

Provider: Microsoft-Windows-Hyper-V-Virtual-PMEM
Channel: Microsoft-Windows-Hyper-V-Worker-Analytic

Message #

[VMID %3] %1

Fields #

Name	Description
`TraceData` UnicodeString
`VmName` UnicodeString
`VmId` UnicodeString
`StackFrameCount` UInt32
`StackFrame` Pointer
`ModuleCount` UInt32
`Module` Int32

Event ID 4: [VMID VmId]

Provider: Microsoft-Windows-Hyper-V-Virtual-PMEM
Channel: Operational

Fields #

Name	Description
`TraceData` UnicodeString
`VmName` UnicodeString
`VmId` UnicodeString
`StackFrameCount` UInt32
`StackFrame` Pointer
`ModuleCount` UInt32
`Module` Int32

Event ID 4: [VMID VmId] TraceData.

Provider: Microsoft-Windows-Hyper-V-Virtual-PMEM
Channel: Microsoft-Windows-Hyper-V-Worker-Analytic

Message #

[VMID %3] %1

Fields #

Name	Description
`TraceData` UnicodeString
`VmName` UnicodeString
`VmId` UnicodeString
`StackFrameCount` UInt32
`StackFrame` Pointer
`ModuleCount` UInt32
`Module` Int32

Event ID 10: 'VmName': Virtual PMEM device 'Locator' is mapped into virtual machine address space at base address BaseAddress, size Size bytes

Provider: Microsoft-Windows-Hyper-V-Virtual-PMEM
Channel: Operational

Description

'VmName': Virtual PMEM device 'Locator' is mapped into virtual machine address space at base address BaseAddress, size Size bytes. (Virtual machine ID VmId).

Fields #

Name	Description
`VmName` UnicodeString
`VmId` UnicodeString
`Locator` UnicodeString
`BaseAddress` UInt64
`Size` UInt64

Event ID 10: 'VmName': Virtual PMEM device 'Locator' is mapped into virtual machine address space at base address BaseAddress, size Size bytes.

Provider: Microsoft-Windows-Hyper-V-Virtual-PMEM
Channel: Microsoft-Windows-Hyper-V-Worker-Admin

Description

'VmName': Virtual PMEM device 'Locator' is mapped into virtual machine address space at base address BaseAddress, size Size bytes. (Virtual machine ID VmId).

Message #

'%1': Virtual PMEM device '%3' is mapped into virtual machine address space at base address %4, size %5 bytes. (Virtual machine ID %2)

Fields #

Name	Description
`VmName` UnicodeString
`VmId` UnicodeString
`Locator` UnicodeString
`BaseAddress` UInt64
`Size` UInt64

Event ID 11: 'VmName': Virtual PMEM device 'String' failed to start

Provider: Microsoft-Windows-Hyper-V-Virtual-PMEM
Channel: Operational

Description

'VmName': Virtual PMEM device 'String' failed to start. Error: 'ErrorCodeString' (ErrorCode). (Virtual machine ID VmId).

Fields #

Name	Description
`VmName` UnicodeString
`VmId` UnicodeString
`String` UnicodeString
`ErrorCodeString` UnicodeString
`ErrorCode` UInt32
`Param1` UnicodeString
`Param2` UnicodeString

Event ID 11: 'VmName': Virtual PMEM device 'String' failed to start.

Provider: Microsoft-Windows-Hyper-V-Virtual-PMEM
Channel: Microsoft-Windows-Hyper-V-Worker-Admin

Description

'VmName': Virtual PMEM device 'String' failed to start. Error: 'ErrorCodeString' (ErrorCode). (Virtual machine ID VmId).

Message #

'%1': Virtual PMEM device '%3' failed to start. Error: '%4' (%5). (Virtual machine ID %2)

Fields #

Name	Description
`VmName` UnicodeString
`VmId` UnicodeString
`String` UnicodeString
`ErrorCodeString` UnicodeString
`ErrorCode` UInt32
`Param1` UnicodeString
`Param2` UnicodeString

Event ID 12: 'VmName': Saving, live-migrating or creating a checkpoint of a virtual machine with persistent memory devices is not supported

Provider: Microsoft-Windows-Hyper-V-Virtual-PMEM
Channel: Operational

Description

'VmName': Saving, live-migrating or creating a checkpoint of a virtual machine with persistent memory devices is not supported. Error: 'ErrorCodeString' (ErrorCode). (Virtual machine ID VmId).

Fields #

Name	Description
`VmName` UnicodeString
`VmId` UnicodeString
`String` UnicodeString
`ErrorCodeString` UnicodeString
`ErrorCode` UInt32
`Param1` UnicodeString
`Param2` UnicodeString

Event ID 12: 'VmName': Saving, live-migrating or creating a checkpoint of a virtual machine with persistent memory devices is not supported.

Provider: Microsoft-Windows-Hyper-V-Virtual-PMEM
Channel: Microsoft-Windows-Hyper-V-Worker-Admin

Description

'VmName': Saving, live-migrating or creating a checkpoint of a virtual machine with persistent memory devices is not supported. Error: 'ErrorCodeString' (ErrorCode). (Virtual machine ID VmId).

Message #

'%1': Saving, live-migrating or creating a checkpoint of a virtual machine with persistent memory devices is not supported. Error: '%4' (%5). (Virtual machine ID %2)

Fields #

Name	Description
`VmName` UnicodeString
`VmId` UnicodeString
`String` UnicodeString
`ErrorCodeString` UnicodeString
`ErrorCode` UInt32
`Param1` UnicodeString
`Param2` UnicodeString

Event ID 13: 'VmName': Virtual PMEM device 'String' must be located on a DAX-enabled volume to be successfully mapped into the virtual machine address space

Provider: Microsoft-Windows-Hyper-V-Virtual-PMEM
Channel: Operational

Description

'VmName': Virtual PMEM device 'String' must be located on a DAX-enabled volume to be successfully mapped into the virtual machine address space. Error: 'ErrorCodeString' (ErrorCode). (Virtual machine ID VmId).

Fields #

Name	Description
`VmName` UnicodeString
`VmId` UnicodeString
`String` UnicodeString
`ErrorCodeString` UnicodeString
`ErrorCode` UInt32
`Param1` UnicodeString
`Param2` UnicodeString

Event ID 13: 'VmName': Virtual PMEM device 'String' must be located on a DAX-enabled volume to be successfully mapped into the virtual machine address space.

Provider: Microsoft-Windows-Hyper-V-Virtual-PMEM
Channel: Microsoft-Windows-Hyper-V-Worker-Admin

Description

Message #

'%1': Virtual PMEM device '%3' must be located on a DAX-enabled volume to be successfully mapped into the virtual machine address space. Error: '%4' (%5). (Virtual machine ID %2)

Fields #

Name	Description
`VmName` UnicodeString
`VmId` UnicodeString
`String` UnicodeString
`ErrorCodeString` UnicodeString
`ErrorCode` UInt32
`Param1` UnicodeString
`Param2` UnicodeString

Event ID 14: 'VmName': This virtual machine has been configured with a virtual PMEM device

Provider: Microsoft-Windows-Hyper-V-Virtual-PMEM
Channel: Operational

Description

'VmName': This virtual machine has been configured with a virtual PMEM device. Virtual PMEM is a preview feature and is not recommended for production use. (Virtual machine ID VmId).

Fields #

Name	Description
`VmName` UnicodeString
`VmId` UnicodeString

Event ID 14: 'VmName': This virtual machine has been configured with a virtual PMEM device.

Provider: Microsoft-Windows-Hyper-V-Virtual-PMEM
Channel: Microsoft-Windows-Hyper-V-Worker-Admin

Description

'VmName': This virtual machine has been configured with a virtual PMEM device. Virtual PMEM is a preview feature and is not recommended for production use. (Virtual machine ID VmId).

Message #

'%1': This virtual machine has been configured with a virtual PMEM device. Virtual PMEM is a preview feature and is not recommended for production use. (Virtual machine ID %2)

Fields #

Name	Description
`VmName` UnicodeString
`VmId` UnicodeString

Event ID 15: 'VmName': This virtual machine has been configured with a Physically backed PMEM controller non-DAX backing store

Provider: Microsoft-Windows-Hyper-V-Virtual-PMEM
Channel: Operational

Description

'VmName': This virtual machine has been configured with a Physically backed PMEM controller non-DAX backing store. (Virtual machine ID VmId).

Fields #

Name	Description
`VmName` UnicodeString
`VmId` UnicodeString

Event ID 15: 'VmName': This virtual machine has been configured with a Physically backed PMEM controller non-DAX backing store.

Provider: Microsoft-Windows-Hyper-V-Virtual-PMEM
Channel: Microsoft-Windows-Hyper-V-Worker-Admin

Description

'VmName': This virtual machine has been configured with a Physically backed PMEM controller non-DAX backing store. (Virtual machine ID VmId).

Message #

'%1': This virtual machine has been configured with a Physically backed PMEM controller non-DAX backing store. (Virtual machine ID %2)

Fields #

Name	Description
`VmName` UnicodeString
`VmId` UnicodeString

Provenance

Where this provider's schema came from, and which Windows build it was observed on. Windows can change a provider's event schema between builds, so use this to judge whether it matches the build you collect from.

ETW provider GUID ae3f5bf8-ab9f-56d6-29c8-8c312e2faec2

Defined in vmpmem.dll, which carries the event manifest.

Observed on:

Win11-26200.6584 · schema read from the registered manifest · binary version 10.0.26100.1 · captured 2026-06-02

Downloads

Microsoft-Windows-Hyper-V-Virtual-PMEM registered manifest XML (Win11-26200.6584) manifest-xml

Credits

Microsoft - authored the ETW manifests and PDBs the schema comes from
jdu2600 - the event-schema TSV format this catalog adopted
nasbench - the tool that dumps registered providers and manifests

`j` / `k`	Scroll down / up
`d` / `u`	Half-page down / up
`gg` / `G`	Top / bottom
`h` / `l`	History back / forward
`f`	Follow link (`Shift` = new tab)
`/`	Focus search
`?`	Toggle this help
`↑` / `↓`	Navigate search results
`Enter`	Open highlighted result
`Esc`	Close results / dialog

`type:`	`events` / `rules` / `providers`
`vendor:`	`sigma` / `elastic` / `splunk` / `kusto` / `chronicle` (vendor name alone also works: `sigma:`, `kql:`, `secops:`…)
`tactic:`	TA-id, slug, or name: `credential_access`, `TA0006`
`technique:`	technique or sub-technique ID: `T1003`, `T1003.001` (alias `tech:`)
`severity:`	`critical` / `high` / `medium` / `low` / `informational` (alias `sev:`)
`stages:`	Rules with exactly N pipeline stages
`correlation:`	`single_event` / `sequence` / `alternatives` / `alternatives_cross_log` / `all_required` / `correlated`
`with:`	Co-occurrence event-id; stacks (`with:4624 with:4769`) to require all, while a comma list in one occurrence (`with:4624,4769`) is an either-or group. Implies multi-event
`like:`	Structural neighbors of a rule slug (equivalents + subsumption stricter / broader): `like:comsvcs_lsass_memory_dump-splunk-sysmon`
`groupby:`	Entity-grouping substring match against `group_by_keys`: `groupby:user`, `groupby:host`
`uses:`	Rules whose predicate tree touches the field (any kind, any value): `uses:CommandLine`
`excludes:`	Rules with top-level `not()` clauses on the field (FP whitelists): `excludes:ParentImage`
`field:` / `value:`	Predicate search; narrows rule cards to those with a matching leaf and drives the indicator tier. Unquoted = substring, wildcards allowed (`value:mimikatz`)
`indicator:`	Shorthand for `field:F value:V`: `indicator:Image=*\powershell.exe`
`kind:`	Filter by predicate kind. Narrows rule cards to those carrying a matching predicate leaf (`vendor:elastic kind:cidr_match`) and drives the indicator tier: `contains` / `starts_with` / `ends_with` / `regex` / `cidr` / `eq` / `in` … (operator aliases `op:`/`match:`)
`has:` / `no:`	`sample`, `field`, `notes`, `refs`, `trace`, `thirdparty`, `rule`, `pattern`, `timewindow`, `threshold`, `newterms`, `sigma`/`elastic`/`splunk`/`kusto`/`chronicle`
`-op:val`	Exclude matches; works on most operators but not `type:`/`like:`/`has:`/`no:` (use `no:<flag>` to exclude a rule flag): `tactic:execution -vendor:splunk`. Standalone `-kind:`/`-field:`/`-value:` drop every rule carrying a matching predicate leaf (`type:rules -kind:is_null`)
`field:"…"` / `value:"…"`	Quoted value = anchored exact match (also allows spaces): `value:"net user"`
`a,b`	Comma = OR inside one operator (`vendor:sigma,elastic`, `severity:high,critical`); repeating a facet merges the same way. `field:`/`value:` never split (literal commas)
`vendors:` / `stage:`	Singular and plural spellings fold to the canonical operator and value: `tactics:` = `tactic:`, `type:event` = `type:events`, `correlation:sequences` = `correlation:sequence`, `has:thresholds` = `has:threshold`
`"quoted phrase"`	Exact-match a multi-word phrase (free text)