What device are you seeing this with? Any chance it's a USB 3.0 device that's falling back to 2.0 mode in a 2.0 port? In that case the behavior you're seeing makes sense. We have code in place to attempt to pass 2.0 devices plugged into 3.0 physical ports to 2.0 virtual ports but it cannot handle every case.
↧