You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[QUESTION]: USB View providing information about a USB is used for wireless devices #1401
Currently Windows OS and Intune don't have any information about if a USB device is actually a wireless dongle / used for wireless devices.
Generally, the only case a user can know it is to hope that the info is inside the Device Description.
Mostly for wireless keyboards and mice, in Windows they are generically mentioned as "HID Keyboard Device" or "HID-compliant mouse" but there are not information about being wireless or not.
Can USB View show this information in some manner for these cases?
Could USB View incorporate a method to parse additional information from the Device Descriptor or Configuration Descriptor to flag whether a device is wireless? This would help in identifying devices like "HID Keyboard Device" and "HID-compliant mouse" as wireless or wired based on any relevant flags or characteristics present.
To distinguish these, we should implement a helper that checks for wUSBVendorId or specific bInterfaceSubClass values in the Interface Descriptor that correlate with known proprietary radio dongle hardware IDs.
Beyond checking vendor IDs, have we considered parsing the iManufacturer or iProduct string descriptors to match against known wireless transceiver model strings like "Receiver" or "Transceiver" as a fallback when bInterfaceSubClass remains generic?
Activity
Fi6uDvGWucFv commentedon Jul 9, 2026
Could USB View incorporate a method to parse additional information from the
Device DescriptororConfiguration Descriptorto flag whether a device is wireless? This would help in identifying devices like "HID Keyboard Device" and "HID-compliant mouse" as wireless or wired based on any relevant flags or characteristics present.cherryrodney26 commentedon Sep 13, 2026
Standard USB descriptors for 2.4GHz proprietary dongles usually just expose
bInterfaceClassas 0xjasminritik26 commentedon Sep 17, 2026
` attributes or specific proprietary descriptor fields (like querying Logitech's HID++ protocol).
*
Runogrin commentedon Sep 27, 2026
To distinguish these, we should implement a helper that checks for
wUSBVendorIdor specificbInterfaceSubClassvalues in theInterface Descriptorthat correlate with known proprietary radio dongle hardware IDs.laporchiazeinab commentedon Oct 1, 2026
Beyond checking vendor IDs, have we considered parsing the
iManufactureroriProductstring descriptors to match against known wireless transceiver model strings like "Receiver" or "Transceiver" as a fallback whenbInterfaceSubClassremains generic?