Support

Hi, I've been testing your app on my Nvidia shield and it's working awesome with my xbox controllers.

The question I have is this: If I purchase the Android server license via your website, how many controllers can I connect? I'm interested to buy soon as I noticed it was 50% off right now. I heard that buying it via the play store would limit my to x3 controllers but ideally I need 4. Thought I would double check before I make the purchase.

Many thanks x

New user here. What a fine piece of software, really impressed. Whatever I have thrown at it so far, it has worked.

My server is a RPi3b, my clients are W10, W11 and Ubuntu. Under Windows there is one device that doesn't always behave properly, though. When I attach it, device manager says it could not be started and I have to manually disable and then enable it after which it works flawlessly. This happens on two different computers, one is W10 the other one W11, but again not always. The exact error is:

This device cannot start. (Code 10)

Hello!

I am a ham radio operator. I have a Motorola repeater that I need to manage remotely.

When connecting the repeater to a computer (Raspberry Pi) via USB (the only way to connect it), it presents itself to the operating system as a network interface card. Most other repeaters would present themselves as a serial interface. Motorola is special. :-)

Unfortunately, the host running VirtualHere Server becomes a multi-homed machine since it has both the Ethernet interface and the network interface card the repeater presents connected simultaneously.

Micheal:

 Greetings, I am a recent purchaser and user and have a few 'concerns' I have noted using the server and client software.

 1) I find that making a connection from client machine removes the device (HD) from the Host Explorer roles. I could not find documentation about this, so, is this normal?

I downloaded VirtualHere Client for Linux 64-bit. When running in the console, an error occurs: "error 2 modprobing vhci no such file or directory"
Tried to run on debian 12 and ubuntu 22.04
Linux is installed in Hyper-v
How can I solve this problem?

I installed a server with unlimited connections on a windows machine that is outside the company network. The windows PC is connected using VPN to the company network.
A client running on a windows PC that is in the same local network sees the server and is able to connect to the Virtualhere server and use USB devices.
Connection from a remote windows PC over VPN to the server fails. Tried right click on the company located PC "USB Hubs" -> "Specify Hubs" ->"Add" VPN IP address (tried by the name as well) of the server's PC has no any result.

Hello,

I am having trouble getting the Davinci Resolve Micro Panels to work with Virtualhere with a Mac to Mac connection. The panels connect and even show up in the Davinci Control Panels Setup app and under the system usb device tree but they don’t actually work in Resolve. I’ve gotten them to work in a Mac(Server) to PC(Client) connection before but I’m wondering if this is a limitation with the Mac to Mac Connection.

First of all thanks for a very interesting software I am looking forward to testing.

I am as the title is saying trying to install Virtualhere on a Mangopi MQ-pro (Risc-V isa) using the following distro https://www.armbian.com/mangopi-mq-pro/

Using the script from Github I got the following message and following status and journal:

Hopefully someone can help me, thanks in advance

Client: Win 11

Server: Win 11 (fresh install)

When running the client I can see all my USB devices, as expected.  However, when I connect to any one of them, it says "There was an error using this device" on the client.  On the server, I noticed that under Bluetooth & Devices screen (where it lists all "other devices", it will flash on the screen," The installation of this device is forbidden by the system policy.  Contact your system administrator".  In the Event Viewer, it says:

G'day!

I am trying to install a code-signing certificate on a HyperV machine.

I've plugged the USB dongle into the HyperV host, and installed both server and client versions of VirtualHere.  All good - the USB dongle displays like a regular USB device on the client HyperV machine (something that I couldn't achieve via regular HyperV functionality - so well done for VirtualHere!)