VirtualBox

Opened 7 years ago

Last modified 2 years ago

#16338 new defect

USB Root Hub Shows Yellow Exclamation Mark in Device Manager

Reported by: Gary_Chen Owned by:
Component: USB Version: VirtualBox 5.1.12
Keywords: Cc:
Guest type: Windows Host type: Windows

Description

Environment:

ASMedia USB 3.0 extended host controller with the vendor driver.
Operating system is Windows.

Steps:

  1. Open VM VirtualBox and create virtual machine (Type is Microsoft Windows).
  2. Open Device Manager and disable ASMedia USB Host Controller.
  3. Enable ASMedia USB Host Controller.
  4. USB Root Hub shows yellow exclamation mark.
  5. Device Manager displays the following message in the USB Root Hub Properties dialog box, on the General tab, in the Device Status text box:
    Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)
    The driver could not be loaded because a previous version of the driver is still in memory.

Change History (15)

comment:1 by Socratis, 7 years ago

May I suggest something? It's usually better and faster, if problems like this one (configuration, question) get first addressed in the forums (https://forums.virtualbox.org/). More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

So, if you can, please open a new thread in the VirtualBox on Windows Hosts section.

in reply to:  1 comment:2 by Gary_Chen, 7 years ago

Replying to socratis:

May I suggest something? It's usually better and faster, if problems like this one (configuration, question) get first addressed in the forums (https://forums.virtualbox.org/). More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

So, if you can, please open a new thread in the VirtualBox on Windows Hosts section.


Thank you for your suggestion. I'll open a new thread in the VirtualBox on Windows Hosts section.

comment:3 by gxh, 7 years ago

I stumbled across the community thread that got opened as response to that ticket. https://forums.virtualbox.org/viewtopic.php?f=6&t=81228

I can reproduce the same issue and wanted to update that ticket so it is better understood and maybe actually get fixed. The problem is that the ASMedia USB Root Hub is part of the devices that loaded and unloaded as part of the docking procedure on the Thunderbolt3 docking station. So unloading that driver is a regular occurrence and it is quite disruptive if the USB does not work on that docking station.

Procedure to reproduce:

  • Boot the system and attach the docking station. This will load the ASMedia USB Root Hub driver.
  • Start Virtualbox (it is not necessary to actual start any VMs)
  • Disconnect the docking station. This will unload the ASMedia USB Root Hub driver.
  • Connect the docking station. This will try to load the ASMedia USB Root Hub driver again but it fails with:

Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38) The driver could not be loaded because a previous version of the driver is still in memory.

Stopping Virtualbox will allow the driver to load properly and the USB on the docking station will then work again. I have observed that Virtualbox (VBoxSVC.exe) does not stop properly on some occasions when closed and need to be killed manually to allow the driver to load.

So in summary this seems to be an interaction between the ASMedia USB Root Hub driver and the Virtualbox VBoxSVC.exe process. I am assuming that installing the Extension pack might be related, but I have not specifically tested it without.

Here is the environment:

  • Software:
    • Windows 10
    • Virtualbox 5.1.22 r115126 (Qt5.6.2) + Extension Pack
    • ASMedia USB Root Hub driver: 1.16.45.1
  • Hardware:
    • HP Zbook 15 G3
    • HP ZBook 150W Thunderbolt 3 Dock Product #: P5Q58AA

The comments in the forum thread suggests that all types of Thunderbold docks are affected by that problem. And it looks like that this is a duplicate of #16382

comment:4 by gxh, 7 years ago

These log entries in the .VirtualBox\VBoxSVC.log file might be relevant to the issue:

00:28:23.102745 USBPROXY Getting USB descriptor failed with error 31
00:28:23.102745 USBPROXY Getting USB descriptor failed with error 31
00:28:23.103283 USBPROXY Getting USB descriptor failed with error 31

comment:5 by J.R., 7 years ago

See my comment in 16382

comment:6 by jdhawk, 6 years ago

Running into the exact same issue on a Dell Precision 5510 with a TB16 Thunderbolt dock, using Version 5.2.0 r118431.

Driver and Firmware updates on the system have not solved the issue, nor does removing the extension pack or disabling USB devices for all VM's

Upon re-connecting the dock, while the VB Manger is running, Device Manager will show the error

Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)
The driver could not be loaded because a previous version of the driver is still in memory.
Last edited 6 years ago by jdhawk (previous) (diff)

comment:7 by jani, 6 years ago

I have a Dell XPS 15 9550 and TB16 dock and I keep hitting this same issue. I took me ages to understand that VirtualBox is causing this issue.

Last edited 6 years ago by jani (previous) (diff)

comment:8 by Hamilton, 6 years ago

Same issue here. I have a new Dell XPS 9570 and a TB16 thunderbolt dock. I updated all the drivers, and the dock's firmware, within the last week, but the issue persists.

Before leaving work, I shut down VB, and unplugged the dock. This morning, my keyboard did not work (this happens every time I unplug and replug the dock). This time I did some investigation, and found the error code 38, which has been reported by other users and lead me here (https://forums.virtualbox.org/viewtopic.php?f=6&t=81228&start=15, also in ticket #16382).

On restarting my computer, I also saw the message that VB still had active connections (even though I had shut down all VM instances). AFAIK, this is still an issue on new hardware with updated drivers/firmware.

comment:9 by Ferni, 6 years ago

Same issue on Dell Precision 5530 with TB16.

If you have VboxSVC.exe running when you plug your TB16 dock in then the ASMedia USB Root Hub has Code 38 error (can't reload drivers) and USB/Network ports on the TB16 dock won't work.

Workaround is to make sure VboxSVC.exe is not running (kill it if needed) when plugging in your TB16 dock and then USB and NIC works.

comment:10 by gawbul, 6 years ago

Same issue on Dell XPS 15 9560 with TB16 Thunderbolt Dock.

comment:11 by ThePants999, 5 years ago

Same issue on Dell Latitude 7490 with TB16 Thunderbolt Dock.

In case it's not clear from all the technical descriptions, this is a really impactful issue. I work primarily in a VM, and I dock and undock all the time. This issue means that every time I do, I have to power off my VM and close VirtualBox, sometimes kill VBoxSVC.exe, dock and then start my VM again. That's obviously incredibly painful!

comment:12 by keoni, 5 years ago

One more experiencing the same issue. Many folks I know are experiencing the same as well.

Dell Precision 5530 with Dell TB16 dock, and VirtualBox 5.2.22.

At least we have a workaround, so I don't have to do a daily morning reboot ritual any longer, but it is kind of painful having to shutdown my VM and VirtualBox Manager every time I return to my desk.

comment:13 by cmosugy, 5 years ago

So when is someone going to fix this thing... I mean come on?! There should be no workarounds here, is someone from the VirtualBox team looking at this?

in reply to:  13 comment:14 by Socratis, 5 years ago

Replying to cmosugy:

is someone from the VirtualBox team looking at this?

As far as I know, the VirtualBox team doesn't have a dock. Donations are accepted, never turned down AFAIK. If this issue is "burning" you, you have two options:

  1. Contribute the code that fixes it.
  1. Donate your dock station and the computer that comes with it.

comment:15 by KI, 2 years ago

This issue is indeed BAD. I.e. I've been using years Virtualbox, and due problem with Dell Thunderbolt dock TB16, I had stop using virtualbox, since otherwise I've to keep rebooting my laptop(s) everytime when I connect/disconnect them from dock.

So had to switch to VMWare player instead, which is able to co-op with connect/disconnect of dock without screwing up whole OS.

I can only wish that someone is able to do something for this.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use