Conflict issues after installing Virtualhere

Submitted by oz457 on #1

Hi all, 

I have been pulling out my hair for 3 days in a row and finally found that VirtualHere client was the culpit of all the issues. 
I got a brand new laptop (Asus ROG Zephyrus G16 MY605) which is a brand new high end laptop. 

It took me 3 days and even a reinstall of windows to find finally find out tha VirtualHere is messing up with my laptop big time. 
After a reboot of the laptop, after the download and first use of Virtualhere, the keyboard of the laptop stopped working, the webcam and therefor also Face Signin stopped working, even every single USB port stopped working. The only way to log in into the computer was using the on-screen keyboard!

Even deleting VirtualHere didn't re-establish the functionality of the keyboard, webcam nor the USB ports. The only way to revert back to a working laptop was using a system restore!!!!!!

This is a serious issue with VirtualHere as it makes my laptop unusable. 

What can I do to still make VirtualHere work? How is it possible VirtualHere can mess up a computer that way? 

It took me 3 full days to understand that it was after running VirtualHere only ONCE would be the cause of all the issues. Am I the only one on planet earth with this issue? 

Submitted by Michael on Fri, 2024/04/05 - 09:25

#2

Sorry to hear that. There is a "bug" in the intel driver for the host controller. Its keeps conflicting with virtualhere on some setups. (https://www.virtualhere.com/comment/8351#comment-8351)

On boot, the virtualhere driver will search for an unused name then assign that as its name usually hcd1 is available. However if the intel xHCI driver loads afterwards -instead of searching for a spare name the intel driver just uses hcd1 as its name, even if it conflicts. Ive emailed intel about this but they say too bad. 

So one would assume defaulting to some higher number for virtualhere to work around this. The problem with that is with USB 4 becoming more prevalent, that has multiple host xHCI controllers setup that take higher numbers so its not as easy as just saying e.g hcd5. As intel may just decide to use that name and not bother checking for conflicts.