Support

I have inherited a project that is using a VH server on a remote device (not even sure what hardware the server is at the moment) whereby the server is exposing a serial com port to the client Windows 10 PC. I have been tasked with installing the client and following instructions I connected to the VH server via WiFi and changed the settings to fixed IP address to align with the network that the device and the PC are on. This is a local LAN on an industrial bit of machinery.

i put a license on pi zero 2 WH with a usb hat.
installed raspberry pi lite (32 bit).
its hardwired to ethernet.
pi zero on 1st floor, connected to hardwired PC in the attic (3 floors away).

some things are working great:
bluetooth adapter.
older xbox controller (pre-bluetooth) wired with micro usb, including chatpad.

but these aren't working:
xbox pc wireless adapters (tried both the newer (smaller) one and the previous (larger) version, the led never lit up on either).
newer xbox series controller wired with usb-c.

I have a weird issue where on my Mac, I can’t see the usb server I have on the network yet my windows laptop can. The second I select the option on Mac to “install client as service” I can now see the server? Any ideas why that would be? 

I’m only doing a one to one link to extend a streamdeck over the network so don’t need the functions of purchasing the server licence yet but the Mac won’t connect to a non purchased server all the while it’s installed as client. Any thoughts why the standalone Mac install can’t find the server? 

Hello

I am trying to get VirtualHere working on my Steam Link - I have purchased and installed the app through Steam directly.

When trying to get the link to work the system message log just repeats the same "Could not connect to 192.168.0.87:7575"

The PC and SteamLink are on the same network etc.

Any help would be greatly appreciated. Thanks

Hello

 If I buy a new NAS Synology instead of my current one, do I need to repurchase a license? 

Thank you. 

Sincerely,

Hi,
I'm having a problem with VirtualHere Server because it keeps shutting down for no apparent reason.
It runs on a Windows Server 2019 standard host and, of course, passes the license key (flash drive) to Hyper-V (also Windows 2019 standard) where remote connections are made for users.
I have a license for this program.

The last outage was at night between 04-05.08

I have a QNAP NAS running the server software and two networked Macs running the client.

The USB device is attached to the Server (iLok USB dongle).

I can access from one machine but on disconnecting and trying to connect on second machine I get this error message.

"ILok Sharing Error
An iLok cannot be shared across multiple
operating systems or computers.
Disconnect and reconnect your iLok
when switching to another OS/Computer."

I didn't see any warnings at purchase that this specific device does not work with USB Virtual Here. 

Hi, 

I'm unable to share a webcam attached to a mac server to a windows client. In the client when I try to use the webcam, I initially will see an image but it will then time out.

macOS Sequoia 15.5

Windows 11

Logs as follows:

>>> Starting VirtualHere USB Server v4.8.1 (Built: Jul 21 2025, 11:51:36)<<<

2 11:23:57 2025 LOG_WARNING Warning, cannot lookup the exe path, 22 (Invalid argument) (defaulting to HOME)

Listening on all network interfaces at TCP port 7575 (IPv6 dual-stack)

Hey,

First of all, love the tool. I have used it for arduino ide and matlab so far and it's great. So I accidently clicked always connect on the prompt. Normally this is fine, but i could like to undo this so I can get the prompt. I want to be able to manually select if I want the usb to be shared.

Is there a way to do this?

Thanks

Hello,

I recently purchased a VirtualHere license to use my Oddor handbrake remotely. The device is correctly detected in Windows (it shows up in joy.cpl), but when I try to calibrate or test it, no input is being registered.

To rule out a hardware problem, I tested the Oddor handbrake directly connected to the target PC, and it works perfectly in that configuration. The issue only occurs when using VirtualHere.

Could you please advise if there is a specific configuration, driver, or setting I should use to get this device fully functional through VirtualHere?