Académique Documents
Professionnel Documents
Culture Documents
V2.0.0
V2.0.1
V2.0.2
V2.1.0
tree
V2.1.1 - Bugfix: Crash on root-hubs which are not a child device of the host c
ontroller
V2.1.2 - Bugfix: Windows 'app key' (or Shift+F10) opened the context menu in t
he wrong position
V2.1.3 - Bugfix: V2.1.2 always showed wrong error for the device's Address pro
perty
Bugfix: Workaround for font problem
V2.1.4 - Bugfix: V2.1.3 switched back to the default font
V2.1.5 - New: Can write a report
New: Improved device names in the treeview
V2.1.6 - Bugfix: Crash on decoding USB3 standard hubs
- Bugfix: some format glitches on USB3 standard hubs
V2.1.7 - Bugfix: Decoding of bmAttributes in USB 2.0 Extension Descriptor was
wrong
V2.1.8 - Bugfix: Decoding of SuperSpeed Endpoint Companion Descriptors was don
e only for MSC devices
V2.1.8.1 - Bugfix: Crash when saving report to 'long' path
V2.1.9 - Bugfix: Crash on USB-Hubs with more than 16 Ports
- New: Commandline parameter for writing a report, e.g. /R:U:\UsbTreeVi
ew-Report.txt
V2.2.0 - New: Shows some more device properties
- New: Can show the Windows device properties dialog
V2.2.1 - Bugfix: V2.2.0 worked under Windows 7 and 8 only
V2.3.0 - Bugfix: Several bugs which could cause crashes
- New: Decoding of HID descriptors
V2.3.1 - Bugfix: Font color setting was ignored
V2.3.2 - Bugfix: Device Descriptor was called Device Qualifier Descriptor and
a Device Qualifier Descriptor was not decoded
V2.3.3 - Bugfix: Crash when configuration descritor fails to be read
V2.3.4 - Bugfix: Crash with some USB over network products
V2.3.5 - New: Can save report for selected device only
V2.3.6 - Bugfix: Configuration Descriptor's bmAttributes Bit7 decoded wrong
- Bugfix: If a device's Address value is not found then it was shown as
'0', now as '-'
- New: All string descriptors shown in a separate section
- New: Hexdumps with ASCII
V2.3.7 - Bugfix: Damaged display when window is resized from top or left
- New: Safely removed devices get a green "SR" icon instead of the yell
ow error icon
V2.3.8 - Bugfix: USB Hub Descriptor's DeviceRemovable and PowerControlMask err
or shown wrong (Intel ICH6 and VirtualBox with 8 or more ports)
- Bugfix: USB SuperSpeed Hub Descriptor's DeviceRemovable was decoded f
or all ports even the USB3 spec states a maximum of 15 ports
- Bugfix: USB SuperSpeed Hub Descriptor's PowerControlMask was decoded
even it does no more exist
- Bugfix: USB Hub Descriptor's wHubCharacteristics "TT Think Time" deco
ded wrong
V2.3.9 - Bugfix: Wrong Error message about number of frame descriptors when mo
re than one Frame Based Format Type
- Bugfix: Crash when 'Audio Control Feature Unit Descriptor' bControlSi
ze is zero Descriptor
- New: Decoding of bmaControls of 'Audio Control Feature Unit Descripto
r'
V2.4.0 - New: Decoding of MIDI descriptors
- New: On Windows before Windows 8 'H' or 'S' on port icons if High or
SuperSpeed device is attached
V2.4.1 - Bugfix: Wrong 'USB 3.0 Companion Descriptor missing' error removed
- Bugfix: Windows Version under Windows 8 and 10 correctly shown as NT
6.3 and 6.4
V2.4.2 - Bugfix: Wrong item order in the report
- New: "Copy report from here" treeview context menu
- New: Decoding of some USB 3.1 descriptors (untested)
- New: Decoding of some Wireless USB 1.1 descriptors (untested)
V2.4.3 - Bugfix: "Save Report from current Item" made a report of the selected
item only
- Bugfix: "Save Report from current Item" failed if the item name conta
ins a character which is invalid in a file name
V2.4.4 - Bugfix: Since V2.3.9 'S' and 'H' not shown on empty ports unter Win8+
V2.5.0 - New: Audio 2.0 descriptors
V2.5.1 - Bugfix: Since V2.5.0 possible crash when getting a string descriptor
V2.5.2 - New: Option to show the drive numbers in the tree, e.g. Disk3, CdRom1
etc.
V2.5.3 - New/Bugfix: USB Attached SCSI drives (UASPStor) shown with drive lett
er in the tree and in the drives combobox
V2.5.4 - Bugfix: Crash on H.264 WebCams
- Bugfix: Crash when more than 127 USB devices
- New: Reading of the Microsoft specific string descriptor 0xEE
V2.5.5 - Bugfix: Occasional crash after device safe removal or reactivation
V2.5.6 - Bugfix: String descriptors containing invalid characters where not sh
own at all
- Bugfix: Crash when more than 64 ports per hub
- New: On Windows 8 and 10 the Microsoft USB stack returns for USB devi
ces running at SuperSpeed a
Device Bus Speed of 0x02 (High-Speed). So far UsbTreeView faked
it to 0x03 (SuperSpeed) as Microsoft's USBview does.
Now the truely returned value is shown with a hint if it is not
the true speed.
V2.5.7 - New: Display SuperSpeedPlus in Connection Information V2 under Window
s 10
V2.5.8 - Bugfix: Decoding of SuperSpeedPlus descriptor and some others fixed
V2.5.9 - Bugfix: Wrong warning about characters below 0x20 in some string desc
riptors
- Bugfix: Delay on opening a Windows Device Manager device properties d
ialog removed
- New: Decoding of Microsoft string descriptor 0xEE
V2.6.0 - Bugfix: bRefresh field in endpoint descriptors of Audio 1.0 devices w
as not shown
V2.6.1 - Bugfix: Limit of 32 root hubs removed
- Bugfix: 'Other Speed Configuration' Descriptors was not read
- New: Shows progress information in the status bar, when stuck giving
a hint where
- New: Getting Microsoft String Descritor 0xEE can be deactivated becau
se it causes some devices to freeze.
If in the Registry under HKLM\SYSTEM\CurrentControlSet\Control\U
sbFlags\VVVVPPPPRRRR there is a
osvc value != 0 then UsbTreeView reads it anyway because Windows
already read it successfully.
VVVVPPPPRRRR is a 12 digit hex value containing idVendor, idProd
uct and bcdDevice from the USB Device Descriptor
ToDo:
- USB Video Class H.264 decoding
- Maybe Unicode support
So, if you have an unknown descriptor and the interface class is not 0xFF
then please let me know, maybe I find the right specification document
and can add the decoding for it.
HID descriptors usually cannot be read. Probably this is because they
must be requested from the interface rather than the device but the
IOCTL_USB_GET_DESCRIPTOR_FROM_NODE_CONNECTION call doesn't offer the
choice. The parameters are ignored and filled by the USB stack:
"the USB stack ignores the value of bmRequest and inserts a value of 0x80
which indicates standard USB device request".
https://msdn.microsoft.com/en-us/library/windows/hardware/ff539272%28v=vs.85%29.
aspx
For most devices the result is an ERROR_GEN_FAILURE or ERROR_INVALID_PARAMETER.
But some devices return the HID descriptor anyway.
is debug capable and this works indeed (seen on a i945G Chipset with ICH7).
USB Mouses
If an USB mouse is moved while the tool requests its USB properties there
is usually an error because the mouse just has more important things to
do than answering descriptor requests. UsbTreeView tries then for some
seconds to get this information.
You might see the yellow question mark at the mouse's tree node for a
moment which disappears as soon as you stop moving the mouse.
This retry mechanism is done for all type of devices but usually its a
mouse where it helps.
Information shown in the tree-view
UsbTreeView is optimized for speed, therefore USB descriptors are not
gathered before a device is selected in the tree-view. So, information
which come from USB descriptors cannot be shown in the tree-view, it
all comes from the Windows device manager.
This is also why creating a full report takes a moment.