The sample (27, 9) decodes to IRP_MJ_PNP with IRP_MN_QUERY_CAPABILITIES, so it represents a Plug and Play capabilities query—not a device connection or disconnection.
Meaning of the values
- 27 decimal (
0x1B) — the WDM major functionIRP_MJ_PNP. PnP requests consist of a major function plus a minor function identifying the requested operation.^1^ - 9 decimal (
0x09) — the PnP minor functionIRP_MN_QUERY_CAPABILITIES. The documented PnP minor-function table is the appropriate reference for decoding this part of the payload.^2^ - Task 37 — a provider-defined grouping value. Tasks can represent any component or operation chosen by the event provider; their numeric values are not universal.^3^
- Opcode 1 — the standard ETW
Startopcode, meaning the beginning of an ETW activity. It does not mean that the physical device was connected.^4^
Therefore, this event says approximately:
UMDF started processing a PnP request that queries the capabilities of the specified device.
It is normal lifecycle activity and does not, by itself, identify why the device failed to connect.
Retrieve the schema installed on that Windows build
The installed provider metadata is the best source for that system’s event IDs, templates, field names, task labels, opcodes, and message text. Run the following from an elevated Command Prompt on a machine where the provider and matching message resources are installed:
wevtutil gp Microsoft-Windows-DriverFrameworks-UserMode /ge:true /gm:true /f:xml > "%TEMP%\UMDF-provider.xml"
wevtutil qe "Microsoft-Windows-DriverFrameworks-UserMode/Operational" /rd:true /c:20 /f:xml > "%TEMP%\UMDF-events.xml"
wevtutil gp retrieves publisher metadata, while qe queries events.^5^ Provider metadata maps numeric task and opcode values to the names or message strings supplied by the provider.^6^
The metadata can expose the event template and its field names, but it might not translate payload enum values such as 27 and 9; those must be interpreted against the applicable driver IRP definitions. If message resources are unavailable, rendered Message values can be empty or unresolved, so inspect the event XML directly.
Narrow the log to this device
The string beginning with USB\VID_17E9... is the device instance ID, which identifies a particular device node and persists across restarts.^7^
First constrain by time and search the event XML, while displaying the Event ID before Task and Opcode:
$log = 'Microsoft-Windows-DriverFrameworks-UserMode/Operational'
$id = 'USB\VID_17E9&PID_6015&MI_01\7&34BBCC50&0&0001'
$start = (Get-Date).AddHours(-2)
Get-WinEvent -FilterHashtable @{LogName=$log; StartTime=$start} |
Where-Object { $_.ToXml() -like "*$id*" } |
Select-Object TimeCreated, Id, Task, OpcodeDisplayName,
@{n='Opcode';e={$_.Opcode}},
@{n='XML';e={$_.ToXml()}}
Open one matching event’s XML and note the <Data Name="..."> field containing the instance ID. Once its exact name is known, use an indexed XPath query instead of scanning rendered messages:
$log = 'Microsoft-Windows-DriverFrameworks-UserMode/Operational'
$xpath = "*[EventData[Data[@Name='DeviceInstanceId']=" +
"'USB\VID_17E9&PID_6015&MI_01\7&34BBCC50&0&0001']]"
Get-WinEvent -LogName $log -FilterXPath $xpath |
Select-Object TimeCreated, Id, Task, OpcodeDisplayName
Replace DeviceInstanceId with the exact field name found in that event’s XML. Windows Event Log supports filtering through XPath and Get-WinEvent -FilterXPath can be used to test the query locally.^8^
Identify removal and arrival sequences
For disconnection analysis, look for the same instance ID around these PnP operations:
-
IRP_MN_QUERY_REMOVE_DEVICE— orderly removal is being requested. -
IRP_MN_SURPRISE_REMOVAL— the device disappeared without orderly removal. -
IRP_MN_REMOVE_DEVICE— Windows is removing the device’s software representation.^9^
IRP_MN_REMOVE_DEVICE is not absolute proof of a physical unplug: Windows can also issue it after a failed start or during a driver update.
There is no equivalent single UMDF opcode that universally means “USB connected.” Arrival is generally established by correlating:
- The first appearance of the device instance ID.
- Enumeration/start and hardware-preparation events.
- Nearby Kernel-PnP events in Event Viewer → Windows Logs → System.
- Any UMDF failure events at the same timestamp, particularly 10110, 10111, or 10112, which indicate host failure or a device going offline.^10^
References