Nothing kills a gaming session faster than launching the Quest link interface, hitting Connect, and watching the headset hang on a gray screen before spitting out “Connection failed” or “Couldn’t connect to your PC.” Sometimes the Air Link tile spins endlessly, sometimes the PC shows up in your devices list but refuses to pair, and sometimes the connection drops the moment you put the headset on. The frustration is real: your PC might be running the game perfectly, but the wireless bridge between the Quest and your desktop just won’t cooperate.
The good news is that this is almost never a hardware failure. Air Link failures in 2026 are overwhelmingly caused by network configuration, driver mismatches, or firewall behavior — all fixable in under an hour with the steps below. Work through the fixes in order, since the earliest ones resolve the majority of cases.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Headset and PC on different network bands or subnets | Check the IP addresses: Quest (Settings → Wi-Fi → your network → Advanced) vs. PC (run ipconfig in Command Prompt). If the first three number groups differ, they’re isolated. |
Easy |
| Windows Firewall or third-party antivirus blocking Oculus/Quest Link | Temporarily disable the firewall and try connecting. If it works, the firewall is the culprit. | Easy |
| Outdated or broken GPU driver | Check the driver version in Device Manager → Display adapters → Properties → Driver tab, or in the NVIDIA/AMD app. | Easy |
| Router QoS, AP isolation, or client isolation enabled | Log into your router’s admin page (usually 192.168.1.1) and look for “AP Isolation,” “Client Isolation,” or “Wireless Isolation” under wireless settings. | Moderate |
| Meta Quest Link app cache or service failure | The Oculus VRB server or OVRServer process hangs — Task Manager shows OVRServer_x64 not running or stuck at high CPU while the headset won’t pair. | Moderate |
| 5 GHz channel congestion or DFS channel switching | Your connection works at night but fails during peak hours, or drops every few minutes. Use a Wi-Fi analyzer app to check channel usage on your 5 GHz band. | Moderate |
Fix 1: Verify Both Devices Are on the Same Network
What causes it
Air Link requires the Quest and PC to see each other on the same local network. Dual-band routers often broadcast separate 2.4 GHz and 5 GHz network names, and a PC on Ethernet while the headset is on a guest network or different band will fail to pair. Some mesh systems also place devices on different nodes with isolation between them.
How to check
On the Quest, go to Settings → Wi-Fi, tap your connected network, and open Advanced to see the IP address. On the PC, open Command Prompt and run ipconfig. Both devices should share the same first three octets (for example, 192.168.1.x). Also confirm the headset is on the 5 GHz band — 2.4 GHz technically works but is too congested for reliable streaming.
What to do
Connect both devices to the same SSID, ideally the 5 GHz one. If your router combines both bands under one name, log into the router and split them into separate SSIDs so you can force the Quest onto 5 GHz. If you use a mesh system, ensure both devices connect to the same node or disable band steering temporarily to test.
How to undo it
Rejoin the original network on either device if you switched. Nothing here is permanent — you’re just changing Wi-Fi associations.
Fix 2: Restart Everything in the Right Order
What causes it
The Quest Link runtime depends on several Windows services and background processes (OVRServer_x64, OVRServiceLauncher, and the Quest Link desktop app). Any of them can hang after a Windows update or a sleep/wake cycle, leaving the connection handshake broken even though everything looks fine on the surface.
How to check
Open Task Manager (Ctrl+Shift+Esc) and look for OVRServer_x64 under Processes. If it’s absent while Quest Link is running, or stuck consuming abnormal CPU, the runtime has hung.
What to do
Quit Quest Link completely: right-click the Quest Link icon in the system tray and choose Exit. In Task Manager, end any remaining OVRServer or OculusVR processes. Restart the PC. Then, on the Quest, hold the power button, choose Restart, and wait for the headset to fully reboot. Only then relaunch Quest Link on the PC and reattempt the connection from the headset’s Quick Settings → Quest Link panel.
How to undo it
Not needed — a restart carries no persistent changes.
Fix 3: Allow Quest Link Through the Windows Firewall
What causes it
Windows Defender Firewall or a third-party security suite (Norton, McAfee, Bitdefender) can block the inbound UDP and TCP traffic Air Link needs for discovery and streaming. Windows sometimes silently blocks the app after an update if you dismissed the permission prompt.
How to check
Open Windows Security → Firewall & network protection → Allow an app through firewall. Scroll to find “Oculus VR” or “Quest Link” entries and confirm both Private and Public boxes are checked. If the app isn’t listed at all, it was never granted an exception.
What to do
Click Change settings → Allow another app, browse to C:\Program Files\Oculus\Support\oculus-runtime\OVRServer_x64.exe (and the Quest Link executable in C:\Program Files\Meta Quest Link\ if you use the newer install path), and add it for Private networks. If you use third-party antivirus, add the same exclusions in its firewall settings. Then retest.
How to undo it
Return to the firewall exception list and uncheck or remove the entries you added. If you added exclusions in third-party software, remove them the same way.
Fix 4: Update or Clean-Reinstall the GPU Driver
What causes it
Air Link’s encoder runs on the GPU. A corrupted or outdated driver — especially after a major Windows update — can prevent the encoding session from starting, which shows up on the headset as a connection failure even though pairing succeeded.
How to check
Open the NVIDIA App or AMD Adrenalin and compare your installed driver version against the latest listed for your card. Also check Device Manager → Display adapters for a yellow warning icon.
What to do
Download the latest driver directly from NVIDIA or AMD. For a clean install, run the installer, choose Custom (NVIDIA) or Factory Reset install (AMD), and check “Perform a clean installation.” Reboot afterward. If problems started immediately after a driver update, use DDU (Display Driver Uninstaller) in Windows Safe Mode to wipe the driver completely, then reinstall the stable branch.
How to undo it
Roll back via Device Manager → Display adapters → Properties → Driver tab → Roll Back Driver, or reinstall a previous version from the vendor’s archive.
Fix 5: Disable Router AP/Client Isolation and Check QoS
What causes it
Guest networks and some routers enable AP isolation, which prevents wireless clients from communicating with each other directly — the Quest can’t see the PC even though both are online. Aggressive QoS or bandwidth-limiting rules can also throttle or drop the streaming traffic entirely.
How to check
Log into your router’s admin interface (the address is usually printed on the router, often 192.168.1.1 or 192.168.0.1). Look under Wireless or Guest Network settings for “AP Isolation,” “Client Isolation,” or “Wireless Isolation.” Check QoS or bandwidth management rules for anything limiting the Quest’s device.
What to do
Disable AP/client isolation on the network the Quest uses. If the headset is on a guest SSID, move it to the main network — guest networks are almost always isolated by design. Remove or raise any per-device bandwidth caps on the Quest and the PC. On routers supporting it, create a QoS priority rule that favors the Quest’s MAC address during VR sessions.
How to undo it
Re-enable isolation or restore your previous QoS rules from the same menus. Note down the original settings before changing them.
Fix 6: Switch the 5 GHz Channel and Avoid DFS
What causes it
Dense Wi-Fi environments — apartments, dorms, homes near neighbors — crowd the 5 GHz band. Worse, some auto-selected channels are DFS (Dynamic Frequency Selection) channels shared with radar; when radar is detected, the router must vacate the channel within seconds, instantly dropping Air Link.
How to check
Install a free Wi-Fi analyzer app on your phone and scan the 5 GHz band. Note which channels (36–48, 52–144, 149–165) are crowded. If failures correlate with intermittent drops for all devices, DFS channel switching is likely.
What to do
In your router’s wireless settings, set the 5 GHz channel manually to 36, 40, 44, or 48 — the non-DFS UNII-1 block, which is legal everywhere and never triggers radar shutdowns. Set channel width to 80 MHz. Avoid channels above 100 unless you know DFS behaves well in your area. Save and let the router reboot, then reconnect the Quest.
How to undo it
Set the channel back to Auto in the same menu.
Fix 7: Clear the Quest Link App Cache and Reinstall
What causes it
The Meta Quest Link desktop app stores pairing data and runtime configuration that can corrupt after interrupted updates, leaving the PC visible to the headset but unable to complete the handshake.
How to check
Suspect cache corruption if the headset sees your PC’s name but connection fails at the same stage every time, even after restarts and firewall changes. Repeated Quest Link app updates failing or hanging are another sign.
What to do
Close Quest Link, then uninstall it via Settings → Apps → Installed apps → Meta Quest Link → Uninstall. Delete the leftover folders C:\Users\[YourName]\AppData\Local\Oculus and C:\Users\[YourName]\AppData\Roaming\Oculus (enable hidden files in File Explorer’s View menu to see AppData). Download a fresh installer from Meta’s official site and reinstall. Re-pair the headset from scratch.
How to undo it
Not applicable — a reinstall replaces the old state entirely. Your game library and saves (stored with each game or in the cloud) are unaffected.
Fix 8: Use a Static IP and Disable IPv6 on the PC
What causes it
Some home networks hand out leases via DHCP in ways that confuse the Air Link discovery process, particularly when IPv6 and IPv4 coexist and the headset attempts discovery over the wrong stack.
How to check
Run ipconfig /all in Command Prompt. If you see both IPv4 and long IPv6 addresses on the active adapter and connection fails at the discovery stage, try this fix.
What to do
Open Settings → Network & internet → your adapter → IP assignment → Edit. Set a static IPv4 configuration outside your router’s DHCP pool but inside its subnet — for example, if the router is 192.168.1.1 and hands out .100 and above, assign the PC 192.168.1.50 with subnet 255.255.255.0 and gateway 192.168.1.1. To disable IPv6, open Control Panel → Network and Sharing Center → Change adapter settings, right-click the adapter, Properties, and uncheck “Internet Protocol Version 6 (TCP/IPv6).” Reboot and retest.
How to undo it
Set IP assignment back to Automatic (DHCP) and re-check the IPv6 box in adapter properties.
If Nothing Works
If you’ve exhausted every fix above, rule out the last two variables: the headset itself and your PC’s networking hardware. Test the Quest on a different network entirely — a phone hotspot works for a pairing test, though it won’t sustain gameplay. If Air Link connects there, the problem is your router, and a firmware update or replacement (or a dedicated Wi-Fi 6 router for VR) is the realistic path forward. If it fails everywhere, contact Meta support through the Quest mobile app under Device Support, since persistent hardware-level Wi-Fi failure does occur on older Quest 2 units. As a stopgap, a wired Link cable connection bypasses the wireless stack completely and will confirm whether your PC and headset are otherwise healthy.
FAQ
Why does Air Link work sometimes but fail other times?
Intermittent failures usually point to wireless interference or DFS channel switching. Your neighbors’ networks come and go, and radar activity can force your router off DFS channels mid-session. Set a fixed non-DFS 5 GHz channel (36–48) and see if the failures stop.
Does Air Link work over 2.4 GHz Wi-Fi?
Technically the headset will associate, but the bandwidth is far too low for VR streaming — expect a connection error or an unusable slideshow. Always use 5 GHz or, ideally, Wi-Fi 6 on the 5 GHz band for both the headset and, if wireless, the PC.
Can I use Air Link with the PC connected by Ethernet?
Yes, and you should. A wired PC connection to the router removes one wireless hop entirely, leaving only the headset-to-router link as wireless. This is the most stable configuration and eliminates a whole category of dropouts.
Is Quest Link still supported after Meta rebranded the software?
Yes. The desktop app is now called Meta Quest Link and the setup flow lives in the headset under Quick Settings → Quest Link, but the underlying Air Link streaming technology and its failure modes are the same. All the fixes in this guide apply regardless of the app name on your system.
