addkerop.blogg.se

1. #USB XHCI COMPLIANT HOST CONTROLLER NOT WORKING CODE 39 SERIAL#
2. #USB XHCI COMPLIANT HOST CONTROLLER NOT WORKING CODE 39 DRIVERS#

This util was useful enough to me that I wish it had been installed by default on the Surface and plugged into the built-in Windows Troubleshooting feature. My USB 2.0 ports weren't (and still aren't) working, so it's not just 3.0.

#USB XHCI COMPLIANT HOST CONTROLLER NOT WORKING CODE 39 DRIVERS#

I tried updating the drivers through windows, which changed it to USB xHCI Compliant Host Controller, but I've ended up stuck in the same place with the same errors. It reset my USB Controller and put in the right driver and I'm back in business. It was originally Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft). It checks hardware and software versions and found a number of little drivers things wrong.and fixed them. There are a number of utilities you can check out but the most useful is the Surface Diagnostic Toolkit. I think MS really did a good job in win8 in terms of unifying all the device drivers. In fact, these were updated just yesterday! Note that you have to choose the USB xHCI Compliant Host Controller for the driver in the device manager, otherwise, ASMedia's own driver won't be compatible with Kinect at all. I had to do everything with the touchscreen.Īfter a little poking around on Microsoft Support websites, a friend turned me onto the " Surface Tools for IT." These are the tools that IT Departments use when they are rolling out a bunch of Surfaces to an organization and they are regularly updated. Because the main USB device was dead that meant my Surface Type Keyboard didn't work, my mouse didn't work, nothing. I tried the usual stuff like Uninstalling the Device and rebooting, hoping Windows would heal it but it didn't work. I just wanted the Surface back the way it was, working, with the standard drivers. I know it's an Intel USB 3.0 xHCI Host Controller but I didn't want to go installing random Intel Drivers. That means everything USB didn't work since everything USB hangs off that root device node.

#USB XHCI COMPLIANT HOST CONTROLLER NOT WORKING CODE 39 SERIAL#

That "banged out" device in my Device Manager is the root Universal Serial Bus (USB) Controller for the Surface. However, yesterday while installing a 3rd party USB device something got goofed around with the drivers and I ended up in this state. It's worked great for years and I haven't had any issues with it. I've got a personal Surface Pro 3 that I like very much.