When set it can force all the traffic through the EHCI host rather than default xHCI. Most recent BIOS doesn't have the feature to do this any more but turns out there is a register you can set in the Intel PCH that controls a hardware MUX to accomplish this called XUSB2PR. I was following sporadic reports of certain USB2 devices having quirks when used on a USB3 host controller, mostly from the early days of USB3, and the claims were that disabling USB3 worked in those cases. Any ideas appreciated.Īfter some more digging I am pretty confident the problem is actually a bug in the Microsoft xHCI driver. The signature expired in 2010 and the client is running with a fade date of 2013 (again same on all 3 hosts). The drivers are signed, SHA1 as they are pretty old. I have a feeling there is some driver security / signing thing that the newer PCs are expecting that the old one is not checking for but I don't have clear evidence of that. I have other similar ones for different manufacturers running in the same base VM that work just fine on all of these same hosts. Tried running the device in a WinXP VM also, with the same outcome.įor what it's worth, this USB device is an automotive tool to communicate with a particular make of car.
Tried disabling Hypervisor & Hyper-V, no difference. I have tried older versions of Player with no difference. Using USB 2.0 in the VM, but have tried 1.1 and 3.1 with the same behavior. I mention the processor type because when starting up the VM for the first time on a new host, that is the only thing that the client detects as new, otherwise there is nothing that happens when starting the VM for the first time. Might also be worth noting that the x220 host is Windows 10 upgraded from Win7 and the other two were fresh installs of Win10 The other two are newer PCs a Lenovo T460 i5-core6300 and a NUC desktop i5 7250. The one host that works is a Lenovo x220 with a core i5 2520 processor.
Running the same copy the client across all 3
I've tried this on 3 different hosts and the device and driver works fine on 1 and fails to start on 2.
0 kommentar(er)
