[Solved] install of windows 10 v 1709 usb bus controller doesnt work

[jcricket]

Installed Virtual box on intel core i5 machine I tried both a 32 bit system and a 64 bit system. USB bus controller doesn't load .

Installed on a AMD system 64 bit running the same version/load and the controller works.

The same version of VBox worked before the upgrade to V 1709 build 16299.309.

Is there a fix or workaround??

[socratis]

Host?
Guest?
VirtualBox?

Exact, complete and with full details please.

[jcricket]

Host: windows 10 Enterprise 64 Bit V 1709 Build 16299.309 Processor Intel core i5-6300u @240ghz 8gb Ram Laptop computer
Guest: Windows 7 professional 32 bit 1.00GB ram product id 00371-177-4667606-85049
VirtualBox: 5.2.8 r 121009 (Qt5.6.2) With Oracle VM VirtualBox Extension Pack Version 5.2.8r121009 Device Manager does not show any of the usb bus controller components

I tried the same setup on a windows 10 Enterprise 32 bit V1709 Build 162799.309 Processor Intel core i5-6300u @240 Ghz 8gb Ram using the same guest and virtual box components, the device manager shows two components of the USB controller but the load fails.

I tested on my AMD processor, (Desktop) windows 10 Professional, V1709 build 162799.309 using the same guest and virtual box components, and it loads and appears to be fully functional.

Thanks.

[andyp73]

I guess we want to see a log file (VBox.log) and possibly also the guest configuration file (.vbox) for the guest on the problematic host.

-Andy.

[jcricket]

Host: windows 10 Enterprise 64 Bit V 1709 Build 16299.309 Processor Intel core i5-6300u @240ghz 8gb Ram Laptop computer
Guest: Windows 7 professional 32 bit 1.00GB ram product id 00371-177-4667606-85049
VirtualBox: 5.2.8 r 121009 (Qt5.6.2) With Oracle VM VirtualBox Extension Pack Version 5.2.8r121009 Device Manager does not show any of the usb bus controller components

I tried the same setup on a windows 10 Enterprise 32 bit V1709 Build 162799.309 Processor Intel core i5-6300u @240 Ghz 8gb Ram using the same guest and virtual box components, the device manager shows two components of the USB controller but the load fails.

I tested on my AMD processor, (Desktop) windows 10 Professional, V1709 build 162799.309 using the same guest and virtual box components, and it loads and appears to be fully functional.

Thanks.

[andyp73]

The .vbox file seems to show that you have configured a USB3 (xhci) controller for the guest. It looks like you copied the VBox.log file while the guest was still running which means we don't have all the information but you may want to fix this for starters:

00:00:02.783350 HM: HMR3Init: Falling back to raw-mode: VT-x is disabled in the BIOS for all CPU modes

Your Core i7 processor definitely supports it and it may cause you other problems with your guests if you don't enable it. I don't know enough about the USB stack in VirtualBox to say whether it causes your initial problem though!

-Andy.

[jcricket]

where - how do I fix the error you found?? then I will shut down the VM and send another config file..

[socratis]

You need to fix it in your computer. You need to go to your computer's BIOS and enable VT-x, or Hardware virtualization, or something similar.

[jcricket]

VT-x and Virtualization for directed devices is now on. Didnt seem to make any difference

Here is a new config file.

[jcricket]

After turning both VT-x and Virtualization for directed devices I get the attached err when I start the VM . Do I need to reinstall something??

[andyp73]

It looks like you need to follow the guidance posted around the forum and in I have a 64bit host, but can't install 64bit guests about disabling Hyper-V as it doesn't play nicely with VirtualBox.

-Andy.

[jcricket]

After your last suggestion I am back at square one, vbox starts but no usb controller installed.

I have just completed a virgin install of windows 10 enterprise 64 bit v 1703, build 15063.483 on which I installed virtual box 5.2.8 r 121009 (qt5.6.2) please see attached screenshot which shows that the usb controller works in version 1703, but not in version 1709.

thanks

[socratis]

You'll need to start making things a little bit clearer. For example what is your exact definition of "USB Bus controller doesn't work". Doesn't work where? In the host? The guest? How do you check? If it's the guest you are referring to, we'll need to see a ZIPPED VBox.log from a complete start/login/shutdown cycle of the VM.

[jcricket]

The device manager in the guest machine tries to install the device driver I presume for the usb bus controller, and gives a message that the driver was not successfully loaded. attached are screen shots of the guest device manager showing the usb bus controller with an error indication. I then completed the cycle by turning off the guest machine and getting the logs you requested. and then took a screen shot to show that the host device manager shows the usb controller to be installed and loaded correctly.

The guest machine is the place where the error in loading the device driver occurs, when I attach a USB to Serial adapter, TripLite USA 19HS. This device functions on the host machine when its not trying to be used by the guest machine.

Also as I said in a previous post, I have another machine (exact same make and model - hardware) on which I installed windows 10 v 1703 build 16299.309, and then vbox 5.2.8 and windows 7 32 bit guest OS where the USB to serial adapter works in either the host or the guest machine. I can get a log file from that machine if it would help.

[jcricket]

I just went to the system running 1709, and vbox 5.2.8 and unchecked the usb controller v 3.0 (xHCI) controller and checked v 1.1 OHCI controller then the machine started - loaded the driver for the controller and started completely..... usb to serial device then loaded in the new configuration!!!!

Thanks for all of your time and assistance.