There are a number of issues regarding USB 3.0 controllers primarily with Windows 7. This article highlights some of the more common problems as well as work-arounds for them. A driver package tor the four most common groups of USB 3.0 controllers is available at the end of this article.
The main controllers addresses by this article are:
Native support for most of these controllers is available from within Windows 8.1; the Windows 8 / Windows 8.1 in-box driver is not affected by the issues discussed in this article.
Applications which monitor the USB ports on a system may not work, or USB devices in the system may have intermittent issues
The USB 3.0 Controllers above install their own port monitoring application by default. This notifies you, for example, if you plug a USB 3.0 device into a USB 2.0 port. The monitoring application monitors all ports on the system including USB 2.0 ports and issues can be seen across all ports in the system.
The conflict between the driver's port monitoring application and an add-application which is also probing the USB ports can cause either program to cease working, or the USB ports themselves may intermittently fail to respond or detect devices.
See also Problem 5 for a similar issue around Smart Technologies Smartboard or Smarttablet drivers.
In this situation VMWare products are not able to take control of the USB device and pass it through to the guest operating system. When you attempt to connect the device to the guest operating system, you get an error message that the device is in use on the host.
Ensure the VMWare USB Arbitration service is running in Computer Management > Services.
Use the same resolution as for Problem 1. Then once you have removed the USB monitoring program, you should be able to assign the USB device to the guest operating system.
When you use the INF driver and deploy this through a driver package, the Intel 7 or 8/9 driver may not install properly. The "Intel(R) USB 3.0 Root Hub" is listed in device manager as an Unknown device, or with a yellow exclamation mark on it. Device Manager reports that the driver is not installed correctly.
The cause is a problem with the way the driver and driver ID is constructed. The device has an ID of USB3\ROOT_HUB30&VID_8086_PID_1E31 whilst the driver does not have an INF that matches closely enough for the deployment process such as WDS to use it.
If you attempt to upgrade to Windows 8 from Windows 7 the upgrade checker may report that the USB 3.0 controller driver is not compatible.
Similar to Problem 1, some versions of the Smart Technologies Product Drivers can cause problems when a USB 3.0 controller is installed in the system. This has been verified on Windows 7 and the 2010 version of the Smart Technologies driver package.
When you boot the system, the keboard and or mouse may be unresponsive until you remove them and then plug them back in.
Removing the USB 3.0 controller monitor program does not resolve the problem. The problem has been seen on H61, B75, Q77 and H81 systems.
The drivers themselves appear to cause system problems as they were not designed to be aware of USB 3.0 controllers. The issues are evident even if you are not using the USB 3.0 ports on the system.
Either seek updated drivers from Smart Technologies, or if you are not connecting the Smartboard / Smarttable to the problem system, just uninstall the Smart Technologies driver package from Control Panel. The rest of the Smart Technology software will continue to function without the driver package.
A driver package is available that contains the most up to date Windows 7 USB 3.0 controller drivers for all six mentioned controllers as of 25/7/16. This package includes:
Windows 7 Drivers for x86 and x64 are included. Download here.