USRB B210 does not work correctly with USB 3 #953

Activity

1. soroshsabz commented on Nov 5, 2026

   

   soroshsabz

   on Nov 5, 2026

   Author

   More actions

   if I reboot system and attach USB 3 cable firstly, my system does not recognize USRB with below event logs

   Device settings for USB\VID_0000&PID_0002\6&e3175b8&0&3 were not migrated from previous OS installation due to partial or ambiguous device match.
   
   Last Device Instance ID: USB\VID_0E8D&PID_1887\K0GM1OI1527_________
   Class GUID: {36fc9e60-c465-11cf-8056-444553540000}
   Location Path: 
   Migration Rank: 0xF000FFFFFFFFF132
   Present: false
   Status: 0xC0000719
   

   Device USB\VID_0000&PID_0002\6&e3175b8&0&3 was configured.
   
   Driver Name: usb.inf
   Driver Package ID: usb.inf_amd64_e77a1b8e73716e1c
   Class GUID: {36fc9e60-c465-11cf-8056-444553540000}
   Driver Date: 06/21/2006
   Driver Version: 10.0.26100.9818
   Driver Provider: Microsoft
   Driver Section: BADDEVICE.Dev.NT
   Driver Rank: 0xFF0000
   Matching Device ID: USB\DEVICE_DESCRIPTOR_FAILURE
   Outranked Drivers: usb.inf:USB\DEVICE_DESCRIPTOR_FAILURE:00FF2000
   Device Updated: false
   Parent Device: USB\VID_058F&PID_6254\5&2cf64626&0&4
   

   Device USB\VID_0000&PID_0002\6&e3175b8&0&3 had a problem starting.
   
   Driver Name: usb.inf
   Class GUID: {36fc9e60-c465-11cf-8056-444553540000}
   Service: 
   Lower Filters: 
   Upper Filters: 
   Problem: 0x2B
   Problem Status: 0x0
   
2. soroshsabz commented on Nov 5, 2026

   

   soroshsabz

   on Nov 5, 2026

   Author

   More actions

   Root-cause analysis (Windows 11 26H2, UHD 4.11, B210)

   Debugging through the Windows PnP topology and libusb traces (LIBUSB_DEBUG=4) shows three separate layers, only one of them UHD-related (none):

   1. The original Device Descriptor Request Failed / VID_0000&PID_0002 events were caused by a USB hub in the path.
   The failing instance was attached under USB\VID_058F&PID_6254 (Alcor Micro USB 2.0 hub \u2014 internal card-reader/front-panel hub):

   B210 -> Generic USB Hub (058F:6254, USB 2.0-only) -> USB Root Hub (USB 3.0) -> Intel USB 3.20 XHCI
   

   Plugging the B210 directly into a rear motherboard USB 3 port (same Intel 3.20 controller, no hub) fixed enumeration: device comes up as VID_2500&PID_0020, Ettus WinUSB driver binds, firmware + FPGA load, uhd_usrp_probe succeeds. The not migrated ... Last Device Instance ID: USB\VID_0E8D&PID_1887 line was a red herring (ghost devnode match from an unrelated MediaTek device).

   2. Problem: 0xA / WINUSB start failure right after the driver bound was the device dropping off the bus behind that same hub (re-enumeration while the driver started).

   3. Remaining issue: the link negotiates USB 2 even on a verified-direct Intel USB 3.20 port. With the port verified good, this points at the USB 3 Type-B cable (missing/defective SuperSpeed pairs \u2014 common with printer-style USB3 Type-B cables; USB2 fallback is spec-compliant behavior). Will confirm with a known-good USB3 device in the same port and a replacement cable.

   Conclusion so far: not a UHD software bug \u2014 a chain of USB physical-layer issues. Possibly worth a KB note: B210 on Windows must be on a controller port, never behind internal hubs, and counterfeit USB3 Type-B cables silently downgrade to USB2.
3. soroshsabz

   closed this as completedon Nov 5, 2026