Unable to Get Winusb handle in UMDF 2.0 USB driver

With UMDF 1.x, driver can use WinUSB APIs directly instead of USB I/O target.
To use WinUSB API, handle is obtained either by using IWDFUsbInterface::GetWinUsbHandle or ‘retrieve device name using IWDFDevice::RetrieveDeviceName and pass it to CreateFile API’

UMDF 2.0 supports WINUSB. But I couldn’t find a way to obtain a winusb handle in UMDF 2.0 driver. Though there is a way to use USB I/O target, I am looking at ways to obtain winusb handle/retrieve device name so that it simplifies porting effort.

Can anyone let me know if this is possible in UMDF 2.0?

Thank you

With umdf 2.0 the idea is that your uhave source code that can easily be recompiled for kmdf. Winusb doesn’t exist for KM at all, so exposing it doesn’t make a lot of sense. And umdf 2.0 doesn’t use winusb as the transport mechanism anymore.

Bent from my phone


From: xxxxx@lists.osr.com on behalf of xxxxx@hotmail.com
Sent: Thursday, May 25, 2017 5:46:02 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Unable to Get Winusb handle in UMDF 2.0 USB driver

With UMDF 1.x, driver can use WinUSB APIs directly instead of USB I/O target.
To use WinUSB API, handle is obtained either by using IWDFUsbInterface::GetWinUsbHandle or ‘retrieve device name using IWDFDevice::RetrieveDeviceName and pass it to CreateFile API’

UMDF 2.0 supports WINUSB. But I couldn’t find a way to obtain a winusb handle in UMDF 2.0 driver. Though there is a way to use USB I/O target, I am looking at ways to obtain winusb handle/retrieve device name so that it simplifies porting effort.

Can anyone let me know if this is possible in UMDF 2.0?

Thank you


NTDEV is sponsored by OSR

Visit the list online at: https:

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at https:

To unsubscribe, visit the List Server section of OSR Online at https:</https:></https:></https:>