How to Set Up Virtual Desktop for Quest 3 and 3S on Windows 10 and 11

What you are installing​

Both the Quest app and the Windows Streamer are required. Watch for similarly named products. A similarly named desktop application, an unofficial APK or the Streamer by itself is not enough. The Virtual Desktop site lists Quest 3 and 3S as supported headsets. It also lists Windows 10 or 11 (64-bit) as computer requirements. The site says PC VR game streaming needs a VR-ready PC running Windows, and it states the feature won't work on a Mac.

A few points about versions and price:

• The developer's site currently lists Streamer release notes for version 1.34.25. Some guides still cite 1.34.22, which GitHub dates to October 22. That release restored 96 fps and 100 fps options on Quest and improved CPU performance on the headset and Streamer. Download the Streamer from the official site and read the release notes for the build you install.
• The app costs $24.99, according to one other setup guide (Tech-Insider) and the original walkthrough. The official page I checked doesn't state a price, so confirm it on the store listing before you buy.
• Updating the headset app and the Streamer together is sensible troubleshooting. I found no official statement that the two versions must match exactly.

Step by step​

1. Wire the PC to the router​

Virtual Desktop's FAQ says to connect the computer to the router by Ethernet, not Wi-Fi, if desktop streaming is choppy. It gives the same advice for black screens when launching games. A community walkthrough for Elite Dangerous says the same: Virtual Desktop requires your PC to be ethernet cable connected to your router.

You can check the negotiated link speed in PowerShell:

Get-NetAdapter | Where-Object Status -eq 'Up' | Select-Object Name, InterfaceDescription, LinkSpeed, PhysicalMediaType

A wired adapter should report 1 Gbps. A 100 Mbps reading usually points to a bad cable or port. That is a rule of thumb, not an official figure.

2. Put the headset on 5 GHz, on the same network​

The official requirement is a wired computer connected to a 5 GHz AC or AX router. The FAQ says a 5 GHz connection is required. A "Not on same network" warning can appear if the headset is on a different network, such as a guest network. Some practical tips:

• Give the 5 GHz band its own network name so the headset can't fall back to 2.4 GHz. This is common practice, not an official instruction.
• Keep the router close to the play area. Another guide notes that a clean 5 GHz channel and a router close to the play area usually matter as much as the Wi-Fi standard.
• Fixing a channel and an 80 MHz width is a common community tweak. I could not confirm it from the developer's own page. Treat it as an experiment.
• Some guides allow 5 or 6 GHz. Test both in your own room if your router supports 6 GHz, and keep the one that performs better.

3. Prepare Windows​

Update your GPU driver first. The FAQ ties "measuring bandwidth" disconnects and black-screen game launches to outdated GPU drivers. It also lists HDR or wide color gamut enabled in Windows display settings as a cause. Then work through these:

1. Install Steam and SteamVR. Virtual Desktop streams SteamVR games, and a guide for flight simulators adds that VDXR or SteamVR is selected as required.
2. Install the Streamer and let it run. It sits in the system tray.
3. Set your wired connection to Private so Windows doesn't treat it as a hostile network. Run this in an elevated PowerShell window, substituting your adapter alias:

Set-NetConnectionProfile -InterfaceAlias "Ethernet" -NetworkCategory Private

1. Allow the Streamer through Windows Firewall on private networks. The FAQ names Windows Firewall as a possible blocker. It also tells Avast and AVG users to set the firewall profile to Private. For McAfee, Norton and other antivirus products, it suggests adding an exception or disabling the product to test. It also says to make sure the PC isn't running VPN software.
2. Optionally set the Windows power plan to High performance. This is general advice for streaming sessions, not an official requirement.

4. Install the headset app and pair​

Buy Virtual Desktop in the Quest Store and launch it once. On the PC, sign in to the Streamer with the same Meta account. As one tutorial puts it: Log in using the same Meta account used on your Quest 3. Then open the app and select your computer.

5. Launch games from the Games tab​

The developer's FAQ says to launch games from the Games tab in the Virtual Desktop menu in VR. It also warns that not every game is compatible. Starting a VR title from the flat Steam window can leave it on the monitor view. For OpenXR titles, the Streamer has a preferred-runtime option. A community Elite Dangerous guide says to set it to VDXR for that setup. Release notes for 1.34.8 say VDXR is used by default when the runtime is set to Automatic. If an OpenXR game shows a black screen, check which runtime is active.

6. Tune one setting at a time​

A guide for SteamVR players suggests a moderate bitrate, a standard refresh rate and H.264, then raising settings one at a time. That matches how I would approach it. Refresh rate, codec and bitrate limits depend on your GPU, room and router. No single figure applies everywhere.

Troubleshooting​

Remote-over-internet connections have separate requirements. You need "Allow remote connections" ticked, and UPnP or manual port forwarding. A normal home-network session doesn't need either.

A homemade preflight check​

The original walkthrough includes a PowerShell script and a Python report. The script checks a few things:

• the route and link speed to the headset's IP
• the Windows network category
• the power plan
• GPU driver age
• whether a Streamer process is running

It then sends about 120 pings to the headset. It logs average, 95th-percentile and maximum latency, jitter and packet loss to a CSV file. The Python script summarizes that file across sessions.

The log is useful for spotting patterns, such as a bad evening versus a good one. Treat it as a rough sanity check, though, for these reasons:

• Ping is not stream latency. ICMP round-trip time to the headset doesn't measure video delivery or frame pacing. A clean ping doesn't guarantee a smooth game, and a blocked reply doesn't prove a broken link. The author acknowledges that a ping runs over a quieter path than the stream.
• The thresholds are the author's own. The defaults are 6 ms average, 12 ms at the 95th percentile, 0.5% loss and a 180-day driver age. They are not Meta or Virtual Desktop specifications. Tune them to your own baseline.
• Jitter here is a simple measure. It is the mean difference between consecutive successful ping times. Failed pings are left out of that calculation.
• The sample output is illustrative. Its timestamp is later than the article's publication time, so it is not a real test result.
• Test before you rely on it. The script exits on route-discovery errors, and I have not run it. Run it on your own machine first and read through it before using it as a pass/fail gate.

To run it in a PowerShell window, use the commands one after another. The execution-policy change applies only to that window:

cd C:\VR
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
.\vd-preflight.ps1 -QuestIp 192.168.1.50 -Count 200
python .\jitter_report.py .\vd-preflight-log.csv

Replace the IP address with your headset's. Reserve that address in your router so it doesn't change between sessions. The headset must be awake, or the script will report no replies. Router client or AP isolation can also block pings.

Bottom line​

The setup is short: install both apps, wire the PC, put the headset on 5 GHz, allow the Streamer through the firewall and launch from the Games tab. The developer's own FAQ backs the wired PC and the 5 GHz band most strongly. The router channel width, power plan, codec tuning and 6 GHz tests are worth trying, but treat them as experiments. If stutter persists, compare against another wireless route such as Air Link. If both stutter, suspect the network. If only one does, suspect that tool's settings.