I have VirtualHere running on Raspberry Pi 3 server and a client running on Windows 10 home 64 bit. However in some cases, especially after coming back from hibernate (but this morning after a fresh start too) the devices attached to the raspberry are not seen by the Windows system.
I use USB to Uart devices attached to raspberry Pi 3 and on the windows side the devices not listed at the development environment as COM ports. On the other hand they are discovered by the service when I issue a vhui64.exe -t list command:
C:\Users\gyorgyc\Desktop>"vhui64.exe" -t list
C:\Users\gyorgyc\Desktop>VirtualHere IPC, below are the available devices:
(Value in brackets = address, * = Auto-Use)
Raspberry Hub (raspberrypi:7575)
*--> FT232R USB UART (raspberrypi.1144) (In-use by you)
*--> FT232R USB UART (raspberrypi.1143) (In-use by you)
Auto-Find currently on
Auto-Use All currently on
Reverse Lookup currently off
VirtualHere is running as a service
A fresh restart of the Windows system solves the issue. I use 3.6.4 client and 2.8.9 arm version as server. Is this something with VirtualHere or with Windows? How could I resolve it so that the attached devices are consistently seen.
Found bug
I found the bug which occurs when the computer sleeps and the client is windows 10.
This should be fixed now in 3.6.5 of the client.
Note to update the service you need to uninstall it first like this
vhui64.exe -uthen you need to copy over the new version of the client then install the service again like this
vhui64.exe -iAs i had the same problem but
As i had the same problem but i didnt run windows 10 but windows 7 32bit. First i looked at the problem was created by an other peace of software. after closing the software as this client the comports were available to my other software.
My case is an raspi-2 connected to an virtual windwos 7 installation on an nas (qnap)
thanks for fixing the bug (also on win7 32bit)