So I'm planning on using VirtualHere for Wii Emulation with Dolphin using bluetooth passthrough and steam in home streaming, i've managed to get everything working but the libusbk driver that I install to the bluetooth adpter will get replace back to stock when I disconnect from VirtualHere.
I can install the driver and remove the adpter and plug it in to another computer without it being replaced as well as unplug it and replug it into the same computer that the VirtualHere Server is running on without the driver being replaced.
But if I connect to the adpter through a client, use it as i need is no problem but soon as the Server stops or the Client removes the adpter then soon as the server gives back the device to the host system the driver will be back to the Bluetooth one and not libusbk. I have windows driver updates turned off, so it's not automatically installing drivers. I've even unplug my router from the internet so it is only a local network.
Any help on this issue would be great. Thanks
.
When a device is released, the virtualhere server asks windows to replace the driver with the best one it can. Im wondering if the libusbk driver is not in fact on the best one and there is some override you do to install the libusbk. Is this win10 or win7 running the server? As the driver mechanism is quite different between them. The win7 will search for drivers online first whereas win10 wont.
Yes to install libusbk I use
Yes to install libusbk I use the tool Zadig (http://zadig.akeo.ie/) to install the driver to the adpter. Both the client and the server are on windows 10. I've got a extra computer and will try to see if the same issue happens when using that as a server, it's also windows 10.
.
So I've done some more testing, it works perfectly on my laptop. So what I did to solve this problem is install the official driver for the adpter off the website ( rather than letting windows look for one) then reinstall libusbk and tried it again and libusk stays on the device along with the other drivers. Weird issue, windows fault, not virtualhere.
Thank you for you time anyway
.
Would there be anyway to stop virtualhere from asking windows to replace the driver?
.
The way the virtualhere server works on disconnect is that it removes the redirection driver, then windows will now have a device without a driver. So virtualhere server asks windows to install the best driver it can. If virtualhere doesnt do this, then the driver with be an "unknown device" listed in the Device Manager and if you right click and select "Scan for hardware changes" in Device manager it will again be bound to the proper driver. I dont think it will help much virtualhere not binding the driver as windows will figure it out next time there is a device change (plug/unplug of a physical device) and just bind the driver again to the device automatically anyway.