What VirtualHere does
VirtualHere is a USB-over-IP tool. A server runs on the PC with the device physically attached, and a client runs on the PC that wants to use it. The client then treats the remote device as if it were plugged in locally. In Shareef's setup the mic stays on his primary PC, and the secondary machine picks it up over the network.
Some boundaries matter before you start:
- Windows support. VirtualHere's Windows server page lists version 4.8.8. It supports 64-bit Intel/AMD Windows 10 or Server 2016 and later, plus a separate ARM64 build for Windows 11 on ARM. A Microsoft Store version also exists.
- Free tier. The Windows license lets you share a single USB device at no cost. Sharing more than one device at once requires a purchased license.
- Other platforms. The MakeUseOf piece notes the server also runs on macOS, Linux and Raspberry Pi. Trial rules differ by platform, so don't assume the Windows terms apply elsewhere.
- Client. VirtualHere's purchase page says the client is free and can be installed on any number of machines.
Setting it up on Windows
The steps below follow the MakeUseOf walkthrough, cross-checked against VirtualHere's own documentation where possible.
- Server PC. On the computer with the mic plugged in, download and run the VirtualHere USB Server for Windows. Allow it through Windows Firewall when prompted. The article names the file
vhusbdwin64.exe. VirtualHere's current download page doesn't confirm that filename, so go by what the page offers for your architecture. - Client PC. On the second computer, run the VirtualHere client. The article names
vhui64.exe, with the same caveat about filenames. - Discovery. Per VirtualHere's support forum, the server and client find each other automatically if they are on the same network. The server uses TCP port 7575 by default.
- Use the device. The server PC's USB devices appear in the client. Right-click the mic (the HyperX SoloCast 2 in this case) and choose Use this device. Windows then treats it as locally attached.
- Release it. Right-click again and choose Stop using this device to hand it back to the primary PC.
These menu labels come from the MakeUseOf walkthrough. VirtualHere's documentation corroborates the connection workflow but not every label.
If auto-discovery fails
In the client, right-click USB Hubs, choose Specify Hubs, click Add, and enter the server's IP address. VirtualHere's own forum confirms this path. Add :7575 after the address if you need to be explicit, for example 192.168.1.10:7575.
The article also suggests a static IP or DHCP reservation for the server PC so the address doesn't change. That is sensible network practice, not a VirtualHere requirement.
A forum thread shows another failure point. One user found port 7575 blocked on the client computer. The VirtualHere reply was that changing the port needs a purchased server, because the TCPPort setting is among the advanced parameters VirtualHere's configuration FAQ says are only supported on purchased servers. On a locked-down network, the free tier may therefore leave you stuck on the default port.
Where it falls short: audio
USB audio is the weak spot, and the author says so himself. Microphones use isochronous transfers, which are time-sensitive. VirtualHere's developer explained in a support thread that with large network delay the packets can't come back in time, so audio will stop or skip.
A separate VirtualHere thread says simple devices like headsets usually work acceptably on a LAN. Professional audio gear is more likely to produce artifacts. Both are vendor-forum comments, not benchmarks.
Practical takeaways:
- Dictation. Shareef found it reliable enough, and an occasional skipped word is tolerable.
- Calls, meetings and recording. He wouldn't rely on it for these, and that caution is reasonable. Test your own mic and network before trusting it for anything important.
- Wired Ethernet. He suggests a wired connection to reduce latency. That's a sensible choice over congested Wi-Fi, but it isn't a guarantee against glitches.
- Trusted networks only. The setup is designed for machines on the same LAN. VirtualHere says over-the-internet use will cause dropouts or may not work at all.
Cost versus a hardware switch
Shareef puts the one-time license at $49, against $15–$25 for a physical USB switch. AlternativeTo also lists the perpetual license at $49. Neither is a live checkout price, so confirm the current figure before you buy.
The license is tied to the server hardware. One Hacker News commenter objected to the per-server, non-transferable license. Shareef's article says the same about Android licenses. The Android trial limit is also unsettled. The Play Store listing says the Android app is limited to seven uses in trial mode. A separate VirtualHere trial FAQ cited in our research reportedly says eight. I'd treat the Android number as unverified.
Which should you choose?
| Situation | Better fit |
|---|---|
| One USB device, mostly dictation or casual use, reliable LAN | VirtualHere free tier |
| Several devices shared at once from one server | Weigh the $49 license against a switch |
| Live calls, recording, pro audio gear | A hardware USB switch is the safer choice |
| Locked-down network blocking port 7575 | Likely needs a paid license to change the port |
The case for VirtualHere is real but narrow. It can save you from swapping a cable or buying a switch when you share one peripheral between two PCs on a good network. Shareef also says it works with keyboards, webcams, printers, scanners and external storage. That is his claim, and he tested only the mic. A hardware switch is still the predictable option when timing matters.