A man uses VR controllers to explore a fantasy landscape, with a glowing interface showing his gaming setup’s network status.
Quest Air Link still streams PC VR from a Quest headset to a Windows PC over Wi-Fi, and the usual cause of a bad session is the network, not the headset. This guide sets up Air Link on Windows 10 or 11 and then measures whether your Wi-Fi can carry the stream. It covers the pairing steps, the router tuning, a small Python logger, and fixes for the common failures.

Some of the numbers below are my own starting points. Where that is true, I say so. Where Meta documents something, I attribute it.

A man uses VR controllers to explore a fantasy landscape, with a glowing interface showing his gaming setup’s network status. What Air Link is, and what is supported​

Meta's help pages separate two things that people often mix up.

  • Meta Horizon Link is the Windows desktop app. It was formerly called Oculus Link or Quest Link, so older guides may point you at differently labelled downloads.
  • Air Link is the wireless mode that runs through that app.
  • Wired Link is the cable mode. Meta says it needs a USB-C 3.2 cable that supports at least 5 Gbps.

Meta's requirements for connecting are the Link app on your computer, a Quest with the latest software, a Windows computer that meets the minimum requirements, and a Wi-Fi network, preferably 5 GHz, for Air Link.

Older headsets​

Meta announced on November 2, 2026 that Quest 2 and Quest Pro have reached end of feature development. Version 2.13 is the last feature release and reaches all devices by March 2027. Quarterly security patches and critical bug fixes continue through the end of 2027. Meta also said PC VR through Link keeps working on both headsets.

That makes it a feature freeze, not a shutdown. It does not promise that every future PC-app change will stay compatible forever. Treat Air Link on those headsets as supported but frozen.

Prerequisites​

ItemWhat you needHow to check
HeadsetQuest 3 or 3S (Quest 2 and Pro still work)Settings, About
Headset softwareLatest Horizon OS updateSoftware update page
WindowsWindows 10 or 11, 64-bitRun winver
GPU driverCurrent NVIDIA, AMD or Intel drivernvidia-smi or the vendor control panel
PC networkPC on Ethernet to the same router the headset usesGet-NetAdapter in PowerShell
RouterDual-band with a 5 GHz networkRouter admin page
Optional loggingPython 3.10+, Google platform-tools (ADB)python --version, adb version

Check your PC against Meta's published Horizon Link requirements. Update the GPU driver first, because an outdated driver can look just like a Wi-Fi fault.

Steps 1–3: Prepare the PC and router​

Step 1: Versions and power plan​

Run winver, check your GPU driver, and run powercfg /getactivescheme. If you are on a desktop with the Balanced plan, you can switch to High performance from an elevated PowerShell with powercfg /setactive SCHEME_MIN. Laptops on battery should skip this. Install any pending headset update and reboot the headset afterwards.

Step 2: Wire the PC and check the profile​

Connect the PC to the router by Ethernet, using Cat 5e cable or better. Then confirm what the adapter negotiated:

Code:
Get-NetAdapter -Physical | Where-Object Status -eq 'Up' | Format-Table Name, PhysicalMediaType, LinkSpeed
Get-NetConnectionProfile

A link stuck at 100 Mbps usually points to a bad cable or port. If your network is marked Public, Windows hides the PC from other devices, which can stop the headset from finding it. On a network you trust, you can change it from an elevated window:

Set-NetConnectionProfile -InterfaceAlias "Ethernet" -NetworkCategory Private

Your adapter name may differ from "Ethernet".

Step 3: Router settings for the headset​

Treat the items below as experiments. Meta documents 5 GHz as the preferred band. The other items are common tuning practice that depends on your router's features and your local interference. One third-party guide, from Owl3D, also suggests locking the channel width to 80 MHz where the router allows it.

  • Give the 5 GHz radio its own network name, so the headset cannot silently slide onto 2.4 GHz.
  • Choose a channel width of 80 MHz if your router offers it.
  • Pick a quiet channel by hand, since auto-selection can change channels mid-session. Note the number so you can compare channels later.
  • Turn off band steering for this network.
  • Keep the router or access point in the play room, close to the play space.

You do not need a Wi-Fi 7 router. A wired PC, a clean channel and short distance matter more than the standard on the box.

Steps 4–6: Install, pair, and set graphics​

Step 4: Install Meta Horizon Link​

Install the app from Meta's official Quest setup page and sign in with the same Meta account as the headset. Allow it through the Windows firewall on Private networks. If you missed the prompt, open Windows Security, go to Firewall and network protection, choose Allow an app through firewall, and tick Private for the app. Leave the app open during your session.

Step 5: Pair and launch Air Link​

Meta's documented route is:

  1. Press the Meta button on your controller to open the Navigator.
  2. Open Quick controls.
  3. Select Link, then turn on the toggle next to Use Air Link.
  4. Select your PC in the list of available PCs, then select Pair.
  5. A pairing code appears on the headset. Click Confirm in the computer app, then put your headset back on.
  6. Select Launch.

Link and Air Link are automatically enabled on headsets with the latest Horizon OS updates. If your PC never appears in the list, check three things: the headset and PC are on the same network (not a guest network), the Link app is open, and Windows has the network set to Private.

Step 6: Graphics preferences​

In the Link app, go to Devices, select your headset, then Graphics preferences. Meta's troubleshooting page lists refresh-rate options of 72, 80, 90 and 120 Hz. It also warns that raising refresh rate or render resolution can cost performance.

My suggested starting point is 90 Hz, default render resolution, and a moderate fixed bitrate such as 150 Mbps if your build exposes a bitrate control. These are the starting values I'd try, not Meta recommendations. Meta's documentation does not establish 150 Mbps as an Air Link target.

Play a fast, detailed game for five minutes. Note blocky shadows, a rubber-band feeling when you turn your head, or audio drift. Don't tune anything yet.

Steps 7–9: Optional telemetry with ADB​

The next steps are optional. They add measurement, so you can replace "it feels bad" with numbers.

Step 7: Developer mode and ADB​

Enable developer mode through the Meta Horizon phone app (Devices, your headset, headset settings). The labels vary by build. Install Google's current Android platform-tools and add them to your PATH. Then connect the headset by USB once and accept the debugging prompt on the headset.

The common community route is:

Code:
adb devices
adb tcpip 5555
adb shell ip -f inet addr show wlan0
adb connect <headset-ip>:5555
adb devices

Unplug the cable after adb connect. This tcpip method is a long-standing approach, but Google's current documentation centres on pairing-based wireless debugging for Android 11 and later. I could not confirm this exact sequence against Meta's current Quest instructions, so it may vary by headset build. The setting resets when the headset reboots. If ADB reports unauthorized, accept the prompt in the headset. If it reports offline, run adb kill-server and reconnect.

Steps 8–9: A small logger (airlink_doctor.py)​

The tool has three commands:

  • preflight checks that the PC has a wired adapter at 1000 Mbps or better, that ADB sees the headset, and the headset's Wi-Fi band, standard and signal strength.
  • log records a row every two seconds, with RSSI, link speeds, frequency, band, Wi-Fi standard and the ping time to the headset. A blank ping means the packet was lost.
  • report turns CSV logs into loss, median and 95th-percentile ping, jitter, weakest signal and median receive link speed, plus a pass or warn verdict.

The pass/warn limits I'd use as starting points are:

MetricStarting limitLikely meaning of a breach
PC link speedBelow 1000 MbpsBad cable, bent pins or a port stuck at a low speed
Headset RSSIWeaker than −65 dBmToo far from the router, or a wall or body in the path
95th-percentile pingAbove 25 msInterference, a busy channel or competing traffic
Lost pingsMore than 1%Interference, channel hopping or a flaky radio link

These thresholds are my project-defined starting points. They are not Meta standards, so tune them to your room.

Treat the script as a community tool that needs testing on your own setup, not a validated diagnostic. It has these limits:

  • It reads one line of dumpsys wifi output. A headset update could change that format, and the fields would then come back empty.
  • The PowerShell adapter parsing assumes certain property formats.
  • The verdict logic as originally drafted flags loss, p95 latency and weak signal. It does not fail a run for a slow Ethernet link or missing RSSI.
  • The "jitter" figure is just the mean difference between consecutive successful pings, not a standardized VR metric.

Above all, the ping measures only the network path from the PC to the headset. It does not measure motion-to-photon latency. Encoding, rendering and decoding sit outside it. A clean log doesn't prove a smooth experience, but a dirty log reliably points to a network problem you can fix.

Steps 10–12: Log, read, and A/B test​

Step 10: Run a 15-minute session​

Start the logger, put the headset on and play. Label each run after the variable you are testing, for example ch36. Fifteen minutes is a sensible minimum, because many wireless faults only appear after the router hops channels or the radio warms up. Pause big downloads while you test.

Step 11: Read the report​

Read the columns in this order:

  1. Loss tells you whether packets vanish.
  2. 95th-percentile ping matters more than the median, because you feel the spikes.
  3. Jitter shows how uneven delivery is.
  4. Weakest RSSI explains why.
  5. Receive link speed shows whether the radio dropped to a slower rate.

If the log is clean but the picture still stutters, suspect the PC: GPU load, thermal throttling or a background process.

Step 12: Change one variable per run​

Compare runs in this rough order of impact: router channel, headset position, bitrate, then refresh rate. Keep everything else identical, including the game scene and the length of play. Raise bitrate in small steps and stop when loss or spikes climb. Then back off one step. Write down the winning channel, width, bitrate, refresh rate and play spot, so the next repair is quick.

Alternatives and fallbacks​

Wired Link is a separate connection mode, not a variant of Air Link. It avoids the wireless leg entirely, and Meta advises it when Air Link misbehaves. It needs the 5 Gbps USB-C 3.2 cable mentioned above.

Virtual Desktop is a paid streaming alternative. Its GitHub release page shows version 1.34.22, released October 22, 2026, with 96 fps and 100 fps options back on Quest. The release notes also list many other changes, including CPU performance improvements and a reduced Streamer installer size. The $24.99 app price comes from the original guide, and I did not independently verify it.

Steam Link is Valve's route to SteamVR. Valve's SteamVR 2.18 announcement adds tethered streaming over USB for Quest, which requires the latest Steam Link app on the headset. It also lists streaming reliability fixes, including fixes for some packet-loss situations and improved automatic bitrate selection. That gives Steam users a cable-based option. It is not evidence that Air Link has been replaced.

All three wireless routes share the same network rules. A log that records the same signals for each route lets you compare them fairly.

Common failure points​

SymptomFirst things to try
PC not in the Link listSame network (not guest), Link app open, Private profile, no VPN, and AP/client isolation off
Black screen after connectingClose Link, reboot the PC, update the GPU driver, reconnect
Stutter every few secondsPin the channel and compare the p95 ping across two channels
Blocky or smeared pictureCheck loss first: if it is high, fix the channel and lower the bitrate; if it is near zero, raise the bitrate one step
Drops after about ten minutesDisable adapter power saving, avoid scheduled channel reshuffles, check whether signal fell first
Air Link option missingUpdate the headset and the Windows app. On Quest 2 or Pro, newer menus may not appear
All pings lost but streaming worksYour network may block client-to-client ping, so turn off client isolation or skip the ping column

Other mistakes to avoid: leaving the PC on Wi-Fi, letting the headset sit on 2.4 GHz, changing several settings at once, testing only beside the router, and relying on a wireless mesh backhaul.

If you suspect a Public network or firewall rule, work through the Step 2 and Step 4 fixes before rebooting at random.

The bottom line​

The method works because it replaces guesswork with evidence. Wire the PC, put the headset on a clean 5 GHz channel, pair following Meta's documented route, and log a real session before you tune anything. If the numbers fail on every wireless route, no app will rescue you. The fix then lives in the room, the router or the cable, and wired Link remains the fallback.

 

References

  1. Quest Air Link: 12 Steps, 55 Min to Wireless PC VR - shattered.io shattered.io 2026-11-20T11:00:34+00:00
  2. How to set up Meta Horizon Link and Air Link meta.com
  3. Set up and connect Meta Horizon Link and Air Link meta.com