Support

So I'm running VirtualHereUniversal as a service on a MacOS Virtual Machine. I have a USB dongle that I connect to with 
VirtualHereUniversal -t "USE,<address>"

I get OK, then I disconnect with

VirtualHereUniversal -t "STOP USING,<address>"

And I get FAILED and if I immediately VirtualHereUniversal -t "LIST" it will say the device is still in-use by me, but if I wait around 1 second and list the devices again it will show it is no longer in use by me.

Currently I am using the trial version of your product.   I am using a Proxmox VE (8.4.1) Win10 (19045.4717) VM as the client with my iphone (14 Pro Max with iOS 18.5) virtually attached using VirtualHere.  The server is a Win10 (build 19045.5965) physical device. 

Problem: The VirtualHere client sees the iphone being presented by the VirtualHere server.  As soon as I select "use this device" the client crashes with BSOD indicating SYSTEM SERVICE EXCEPTION with vhusb3hc.sys. The log on the VirtualHere server captured this: 

I just installed a new GL-inet AR300 router running VirtualHere Server 4.8.0 with the new VirtualHere USB hub connected to it.

I can successfully power cycle each port on the hub which is excellent. However, any time the router is power cycled, each port on the hub must be set to power on by default.

The entire purpose of purchasing this hub is I need to leave it connected to a ham radio repeater via a USB/serial adapter at a remote site. 

Hello,

I am looking to get a license for my server so I can run it as a service, but there is no option to License Server. When I click settings, only options I see are View Server Log, Start minimized, Backup and Restore configuration, About. 

Hi

I try to move hasp usb key, software protection. This key was connect to old 2008R2, and i try to move on a new hardware server

server is 2022 and client 2008R2

here is log server :

Have issues with RPi 3 and segmentation fault, this Pi is the server and it's only usage is virtualhere, client is Win11.R e-installed Raspbian Lite 64-bit, then installed vhusbdarm64a53 with script from virtualhere/script. Server is licensed.

VirtualHere Server 4.7.9, client on Win11 is 5.8.8.

Clean server-install with latest OS, everything updated to latest. but still, segmentation fault when looking service status:.

Hello, I was trying to have the Linux USB Server run permanently on my Steam Deck, and just enabling/disabling my VH Client as needed. However, the default installer script tries to write to read-only folders that SteamOS sets.

I'm not very Linux-savvy, but I figured I'd ask some questions anyway.

1.) Is there a way for the installer to instead install the application and the server in a separate folder via the script?

Hey, I am new to VirtualHere so bare with me. I am having a problem using VirtualHere with docker. The image seems to build correctly, however the container fails with a message in the logs "An existing client is not running. Start the client first so it can be connected to" From my understanding I thought I would just have to have the server downloaded and running for my specific OS (in this case windows) in order for the container to build correctly. I checked the firewall settings and the port on my computer and both are configured correctly.

Good afternoon, Mike!

Is there any way to rename specific USB devices on the server? For example, can I rename the device with serial number ffffff84f to 01, and the one with serial ffffff840a to 02? I want to manage these USB names server-side because it’s a pain dealing with so many USBs that have different serials but identical names.

Thanks!

My home has a Windows PC and two NVIDIA Shields:

• Shield #1: Runs VirtualHere Server; on the opposite end of the house from my PC
• Shield #2: Does not run VirtualHere Server; in the same room as my PC

Both rooms have an Xbox Wireless Controller, and I have two Xbox Wireless Adapters: one adapter is plugged into Shield #1, and the other is plugged into the PC. Shield #1's controller connects to the PC via VirtualHere, while Shield #2's connects directly to its dongle via RF because it's in the same room as the PC.