Issue with VH Host Controller driver - WIN10

16 posts / 0 new
Last post
ajarni
Issue with VH Host Controller driver - WIN10

The VHC driver seemed to have stopped working on windows with and error:

This device is not present, is not working properly, or does not have all its drivers installed. (Code 24)

I have tried everything. Uninstalling the driver, rebooting, reinstalling the driver from the latest client (automatically as well as manually by extracting the driver).
The event log shows the following problem: The driver \Driver\WsResetDevice failed to load for the device USB\ROOT_HUB30\1&2b53a856&6&0.

I have Intel USB 3.1 eXtensible Host Controller 1.10 - (version 10.0.18362.693 - Microsoft) and USB Root Hub (USB3.0) 1.10 - (10.0.18362.836 - Microsoft).
If I uninstall all physical USB devices, the VH Host Controller will install, but I have no USB support for my actual physical devices then.

Please help.

Michael
.

Yes i dont know when this will be fixed. You can see here https://answers.microsoft.com/en-us/windows/forum/all/kb4524147-and-virt... the thread.

ajarni
I have been searching the web

I have been searching the web and found multiple threads regarding the conflict between the Intel and VH host controllers.
Do you have any info about that? I apologize for being pushy, but this is really important for me right now.
We are using a paid VH server for our security tokens and I cannot do my job...

ajarni
Thanks Michael. Is there any

Thanks Michael. Is there any workarounds that you know about?

Michael
.

Its not my driver, its intel. There is nothing i can do about that. Why has this starting occuring for you? Did you get a new pc or?

ajarni
No, actually it just stopped

No, actually it just stopped working. I did not need VH for two weeks and now when I again need it, it stopped working. I am going through the updates in this period, will try to uninstall Win updates in this period and see if any changes.

ajarni
Actually there is one

Actually there is one difference from the report in the link you have sent me. The problem as I understand in that case is that physical USB and Intel drivers stopped responding. In my case, actually your driver doesn't load. The Intel looks like it is working fine...

Michael
.

Ok i will revisit this issue now and see if i can find a workaround...

Michael
.

Could you try something for me:

After your machine boots (and the intel 3.1 controller is running ok) could you open Windows Device Manager -> USB and find the "VirtualHere USB 3 eXtensible Host Controller" and then right click and Disable then Enable and see if it will load at that point. Try running the virtualhere client now and see if it works ok

ajarni
Hi Michael, I have tried

Hi Michael, I have tried disabling and enabling the device mentioned, but the device does not change state at all.
Even when disabled it has the previous orange triangle and the state of the driver remains:

This device is not present, is not working properly, or does not have all its drivers installed. (Code 24)
Windows did not start a related device driver. To learn more, click the Driver tab and then click Driver Details.

Michael
.

Can i have a quick look via teamviewer? if so email the teamviewer details to mail@virtualhere.com

ajarni
Michael, I think I have a

Michael, I think I have a workaround for it.

The problem was not in the VH xHCI driver, even though it is still showing the orange triangle warning in Device Manager. The problem was in the USB 3.0 Hub which is created for the VH xHCI driver. In my case the driver details of this device shows "No drivers are installed for this device." in the Device status.

What I did:
- Installed the drivers normally and ignored that VirtualHost 3 eXtensible Host Controller has an orange warning in the Device Manager (This device is not present, is not working properly, or does not have all its drivers installed. (Code 24))
- Opened up the correct USB Root Hub (USB 3.0), the correct one has "Location on VirtualHere USB 3 eXtensible Host Controller" if I open the USB Root Hub device
- Disabled the USB Root Hub and then Enabled the Root Hub - after the reset the device shows "This device is working properly." in the Device status.

This solution however does not survive reboot and so the procedure needs to be repeated everytime the machine is rebooted. I don't know if this has something to do with the driver load order (VH xHCI driver and designated USB 3.0 Hub) or that I have 2x HW USB 3.0 Hub and 1x VH USB 3.0 Hub and they are competing for same ID. If I have the time, I will try to diagnose further.

Michael
.

Thanks for letting me know. That is interesting.

Ive created a possible workaround, could you

1. On the Client PC, open regedt32 and add the entry under

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vhusb3hc\Parameters

New REG_DWORD name HCD value 3

2. Reboot the client pc

Let me know if it is/not resolved.

ajarni
Breakthrough

Hi Michael,

Thank you so much for modifying the driver, but that didn't work for me. I tried HCD 1 to 4 and always made a clean driver installation with reset.

I did however find something else that resolved the issue completely and now even the VH XHCi driver is properly installed. I will try to explain.
Apparently Windows has something called upper and lower driver filters that are triggered when a driver is installed. The attached filters for all USB devices are set in the registry in the path: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\36FC9E60-C465-11CF-8056-444553540000\Class upper filters
The identification 36FC9E60-C465-11CF-8056-444553540000 is for all USB devices.
In my case I had a WsResetDevice class upper filter which was messing up with the installation of the drivers. The WSResetDevice seems to be some filter that Wondershare is using for their dr.fone package and it actually attaches to ALL usb drivers... As soon as I removed the entry in the registry all started working.

Maybe this can come handy to someone else or in your process of debugging.

ajarni
Filters
Michael
.

Ah ok, thanks for that deep dive! I'm familiar with filters, i think there is definitely a bug in their filter. It should never cause a Microsoft USB 3 hub to fail to load.

Log in or register to post comments