VRHow / All sections / VR How-To Guides / Disconnecting headset

Why is my VR headset disconnecting?

Short answer: a recurring disconnect is usually a physical link, a wireless-network interruption, or a PC-side software/driver problem. First note whether the headset disconnects everywhere or only during PC VR, then do the low-risk checks below. Last checked October 11, 2026.

Diagnose the pattern first

If the headset loses its own display or powers off, stop using it and check its charger, power connection and temperature; do not open the headset or battery. If the headset stays on but PC VR drops, the failure is more likely in the cable, USB/DisplayPort path, Wi-Fi path, or PC VR software. A problem that follows one cable or port is useful evidence of a connection problem; it is not proof that the headset itself has failed.

For Meta Quest, test a standalone app briefly. If standalone VR is stable but Link drops, troubleshoot the PC connection. For SteamVR, note the exact status-window message: Valve specifically groups “Headset Display Disconnected” and “Headset not Detected” with connection checks and a headset restart [1].

Safe checks for any wired headset

  1. End the session, remove the headset, and reseat every user-accessible connector. Check both ends of the cable, the PC connection, and any link box or breakaway connector. Do not force a plug or bend the cable sharply.
  2. Try a different compatible USB or DisplayPort port, connected directly to the computer rather than through a hub. Change one thing at a time so you can identify what helped.
  3. Restart the headset and the PC VR software. If the headset is hot, let it cool in a ventilated place before testing again. Do not cover vents or continue if there is swelling, a damaged cable, burning smell, or unusual heat.
  4. Install updates offered by the headset vendor, the PC VR app, and the graphics driver. Valve’s general SteamVR procedure also includes restarting SteamVR, restarting Windows, and verifying SteamVR tool files [1].

If you use Meta Quest Link or Air Link

Wired Link: use a compatible data cable and try another direct USB port or cable. Meta says USB compatibility, the port and cable are common causes, and recommends trying a wired connection when Air Link is unreliable. Turn Air Link off while testing USB because the headset can use only one connection at a time [2].

Air Link: confirm the headset and Windows computer are on the same Wi-Fi network. Restart the headset, computer and, if needed, the router. Move closer to the router and test without downloads or other heavy network use. Meta’s Wi-Fi guidance says to verify that the network works for other devices, that the password is correct, and to try another Wi-Fi network as a diagnostic [3]. A different network working points toward the original network configuration, not necessarily a bad headset.

Meta’s current support labels and menu locations can change. Follow the linked support article if your app says “Meta Horizon Link” or shows different wording. Do not disable firewall or antivirus protection permanently; Meta lists temporarily disabling software that interferes with Link as a troubleshooting step, so restore protection immediately after a controlled test [2].

If you use SteamVR

In the SteamVR status window, use Devices > Restart headset when available. For a tethered headset, recheck power, USB, DisplayPort, the main cable and any breakaway connector. Valve’s Index guidance says the tether can look connected when it is not, and recommends moving USB and DisplayPort connections to different ports if available [4]. If only SteamVR fails, test SteamVR safe mode or contact Steam Support rather than repeatedly unplugging a powered connector.

When to stop troubleshooting

If disconnection continues across a known-good compatible cable, more than one port or network, and a clean restart, record the headset model, connection method, exact error, and what changed. Use the vendor’s support channel. A factory reset is not a first-line connection repair: it erases local settings and should be considered only when the vendor explicitly recommends it for your model and you have backed up what you need.

Sources