Page 1 of 1

Windows 7 guest doesn't recognize VBox provided USB3 controller

Posted: 20. Jul 2016, 17:28
by Notorand.IT
HI all.
My host system is Ubuntu 16.04 x86_64. It is running VirtualBox "5.0.24_Ubuntu r108355" with its extension pack.
I installed a Windows 7 x86 (32bit) guest for a test but it's not recognizing the virtual USB3 adapter provided by Virtualbox.
In the Device Manager I get no available USB adapter, while under "Other devices" I find two warnings: one is "Base System Device" (PCI bus 0, device 4, function 9)
and the other one is "Universal Serial Bus (USB) controller" (PCI bus 0, device 12, function 0).
I have tried to lower the no. of CPUs to 1, accordingly to a rather hold workaround I knew about, with no luck.
It's working only when lowering the virtual USB adapter to USB2 *and* attaching the device to a USB2 port in the host.

Is there a way to solve this problem?

TIA.

Re: Windows 7 guest doesn't recognize VBox provided USB3 controller

Posted: 20. Jul 2016, 17:38
by michaln
You'll have to talk to Microsoft about that. You could also try http://download.virtualbox.org/virtualb ... Manual.pdf section 12.3.1 ("No USB 3.0 support in Windows 7 guests").

Re: Windows 7 guest doesn't recognize VBox provided USB3 controller

Posted: 20. Jul 2016, 17:41
by Notorand.IT
If a Windows 7 or Windows Server 2008 R2 guest is configured for USB 3.0 (xHCI) support,
the guest OS will not have any USB support at all. This happens because Windows 7 predates
USB 3.0 and therefore does not ship with any xHCI drivers; Microsoft also does not offer any
vendor-provided xHCI drivers via Windows Update.
To solve this problem, it is necessary to download and install the Intel xHCI driver in the
guest. Intel offers the driver as the USB 3.0 eXtensible Host Controller (xHCI) driver for Intel 7
Series/C216 chipsets.
Note that the driver only supports Windows 7 and Windows Server 2008 R2. The driver
package includes support for both 32-bit and 64-bit OS variants.
That's it, even if it's related to VirtualBox v5.1 and not v5.0!
I only need to fish for that driver, as there's no link referenced...
Any hint?