Support

Hi there,

I'm running the CloudHub version 4.8.5 on a Raspberry Pi 5 with a powered hub, two sinden lightguns and a bluetooth dongle.

For the client I'm running Batocera Linux v42 with kernel 6.15.11 with VirtualHere client version 5.9.4.
Kernel command line:
BOOT_IMAGE=/boot/linux label=BATOCERA console=tty3 quiet loglevel=0 vt.global_cursor_default=0 initrd=/boot/initrd.gz

Both guns have been updated to the latest firmware version 2.1.

Now the bluetooth dongle is working fine, however the guns are not.

I’m using VirtualHere Client version 5.9.4 on Windows 10 and noticed that logs are now available in the Event Viewer under Application. That’s great, but the problem is that they don't appear correctly in default format - message is always "Incorrect function", as seen in the screenshot. I still can read the actual message in XML format. Is this a configuration issue on my side, or is there a way to fix it so that the messages are displayed properly in text format, not only in XML?
https://prnt.sc/F1OOw1kpRCng

Hello

I have installed VirtualHere on a Raspberry Pi system. I can access the server locally from a client. Externally, the client cannot find the server. I have set everything up as specified. The client and server are also connected to EasyFind, but still cannot find each other.

Linux client server fails with segfaul on AltSP linux with kernel 6.1.114. Unfortunatelly there is no option to upgrade ther kernel.
Any ideas what could be wrond and how it could be fixed? THanks

[Чт окт 30 12:15:32 2025] vhci_hcd vhci_hcd.0: pdev(0) rhport(0) sockfd(11) 
[Чт окт 30 12:15:32 2025] vhci_hcd vhci_hcd.0: devid(4) speed(2) speed_str(full-speed) 
[Чт окт 30 12:15:32 2025] vhci_hcd vhci_hcd.0: Device attached 
[Чт окт 30 12:15:32 2025] vhci_hcd: vhci_device speed not set 

Hi

So I'm getting this weird issue in a raspberrypi with virtualhere server where when connectin a teensy 4.1 (arduino similar device) I can receive data on a virtualhere client (windows 10) but not send any serial data to the remote device (The teensy 4.1) Programming the teenys remotely work great, though this is done in programming mode (i guess in a different USB driver/mode?) 

I've tried mani options. Currently 2 different raspberrypies (version 1 and version 3 B+) various OSes, dietpi, raspbian... and all have the same weird issue.

Hello! My apologies if this is a repeat topic, but I can't find a fix for this anywhere.

I am attempting to share a Logitech Extreme 3D Pro joystick over Tailscale using VirtualHere. The connection is from my Windows 10 desktop client to my Windows 10 desktop server.

Summary
Currently, when a USB device is already in use by another client, any additional user attempting to connect simply receives the message:

“Device already in use.”
There is no built-in way for the waiting user to request access from the current one or to queue for the device.

Problem Description

Hi,
on my Hyper-V host running WinSrv22Std I have a licensed copy of VirtualHere Server.

Everytime I logout from my administrator user VirtualHere stops and all the clients running VirtualHere client do not see USB devices anymore.

Everytime I need to keep the user logged-in in order to make it work. Is there any possibility to run this software as a system service at system startup?

Yours Faithfully.

I’m successfully working with the ClientAuthorization script with 1 device, using the proposed bash script. 

But when using it with 2 devices, it authenticates only on the first one. On the second, it sends a login attempt without a password. Both devices are configured with AUTO USE and both work correctly without using ClientAuthorization. 

I used 312b8a6c015b49e9.8993.9693 because it’s the one set to 1 by AUTO USE DEVICE.

VirtualHere Client IPC, below are the available devices:
(Value in brackets = address, * = Auto-Use)

Hey there,

I just purchased VH because I'm trying to figure out how to free up a USB-C port on my Mac (for an additional display). It seems that the only devices that I'm able to get working are Keyboard and Mouse at this point. I read some older messages saying that Mac had some limitations in the last 3 major releases of OS... wondering if this has been rectified.

Devices not working: