Microsoft-Windows-USB-USB4DeviceRouter-EventLogs

2 events across 1 channel

Event	Title	Channel	Sample
1	A monitor attached to your hub or dock was successfully enumerated by the USB4 …	System	N
2	A monitor attached to your hub or dock could not be enumerated by the USB4 …	System	N

Event ID 1: A monitor attached to your hub or dock was successfully enumerated by the USB4 Connection Manager.

Provider: Microsoft-Windows-USB-USB4DeviceRouter-EventLogs
Channel: System
Task: DPtunnelcreation

Description

A monitor attached to your hub or dock was successfully enumerated by the USB4 Connection Manager.

Message #

A monitor attached to your hub or dock was successfully enumerated by the USB4 Connection Manager.

Fields #

Name	Description
`fid_DomainId` UInt32
`fid_DpOutRouterTopologyId` UInt8
`fid_DpcdCmId` UInt8
`fid_DpOutAdapterNumber` UInt8
`fid_DpInRouterDepth` UInt8
`fid_DpInAdapterNumber` UInt8
`fid_IsRebuilding` Boolean
`fid_Attempts` UInt32
`fid_DpOutLocalCapabilities` UInt32
`fid_DpInLocalCapabilities` UInt32
`fid_MaskedRemoteCapabilities` UInt32
`fid_DpRxPollingDuration` UInt64
`fid_CommonCapabilities` UInt32
`fid_BandwidthUsed` UInt16
`fid_DpBwAllocationModeSupported` Boolean
`fid_DpBwAllocationModeEnabled` Boolean
`fid_ALPMEnabled` Boolean
`fid_LastCL1ExitTime` UInt8

Event ID 2: A monitor attached to your hub or dock could not be enumerated by the USB4 Connection Manager.

Provider: Microsoft-Windows-USB-USB4DeviceRouter-EventLogs
Channel: System
Task: DPtunnelcreation
Opcode: Error

Description

A monitor attached to your hub or dock could not be enumerated by the USB4 Connection Manager. This may be expected if the dock or system does not have sufficient resources or bandwidth to support the monitor. ReasonCode1:fid_ReasonCode1 ReasonCode2:fid_ReasonCode2 Status:fid_Status

Message #

A monitor attached to your hub or dock could not be enumerated by the USB4 Connection Manager. This may be expected if the dock or system does not have sufficient resources or bandwidth to support the monitor. ReasonCode1:%13 ReasonCode2:%14 Status:%15

Fields #

Name	Description
`fid_DomainId` UInt32
`fid_DpOutRouterTopologyId` UInt8
`fid_DpcdCmId` UInt8
`fid_DPOutAdapterNumber` UInt8
`fid_DpInRouterDepth` UInt8
`fid_DPInAdapterNumber` UInt8
`fid_IsRebuilding` Boolean
`fid_Attempts` UInt32
`fid_DpOutLocalCapabilities` UInt32
`fid_DpInLocalCapabilities` UInt32
`fid_MaskedRemoteCapabilities` UInt32
`fid_DpRxPollingDuration` UInt64
`fid_ReasonCode1` UInt64
`fid_ReasonCode2` UInt64
`fid_Status` UInt32

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 d07e8c3f-78fb-4c22-b77c-2203d00bfdf3

Defined in Usb4DeviceRouter.sys, the binary that emits these events.

Observed on:

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

Downloads

Microsoft-Windows-USB-USB4DeviceRouter-EventLogs registered manifest XML (in the Win11-26200.6584 manifest pack, 2.0 MB) manifest-xml

`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:`)
`risk_score`	Numeric comparison on the Elastic risk score (0 to 100): `risk_score>50`, `risk_score<=20`, `risk_score=99` (alias `risk`; Elastic rules only)
`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)

Microsoft-Windows-USB-USB4DeviceRouter-EventLogs

Event ID 1: A monitor attached to your hub or dock was successfully enumerated by the USB4 Connection Manager.

Description

Message #

Fields #

Event ID 2: A monitor attached to your hub or dock could not be enumerated by the USB4 Connection Manager.

Description

Message #

Fields #

Provenance

Downloads

Keyboard shortcuts

Search operators