Link v2.07 Troubleshooting

GOOD NEWS 😃😃😃 [Workaround] Meta Quest Link freezing on newer NVIDIA drivers, no driver downgrade needed : r/OculusQuest

The latest updates have rendered Meta Quest PC Link completely unusable. I’ve been having issues with the wired Link connection since early 2026; after about 10 minutes, the headset freezes during gameplay. The only way to get another 10–15 minutes of playtime before it freezes again is to disconnect the USB cable and terminate the OVRServer_x64.exe process. I’ve tried every conceivable fix—some even allowed me to play for an hour—but since I primarily use it for racing games, the current situation makes it pointless.Since the last update, I can’t even launch a game anymore; the headset freezes while still in the Link app—basically right after I start Link. I haven't been able to use my headset with my PC for over six months now.With no update providing a solution—and the latest one making it truly unusable—I have to wonder if the people involved know what they’re doing; it’s a disgrace.

Hi,My Quest 3 used to work perfectly with Link over USB 3 (about 2.4 Gbps in the Link USB test). Since the Windows 11 26H2 update, the headset is always detected as USB 2.0 and I'm capped at about 340 Mbps.SetupCPU: Intel Core i9 14900KGPU: NVIDIA RTX 4080 Super, with the driver version recommended on Meta's support siteMotherboard: Gigabyte Z790 AORUS Pro X WiFi 7OS: Windows 11 26H2Cable: third-party USB-A to USB-C cable (USB 3), which worked fine before the update, plugged into a USB 3 Type-A port on the motherboardWhat I observedUSB Tree Viewer shows the Quest 3 as High-Speed (USB 2.0).On the exact same port, a USB 3 flash drive is correctly shown as SuperSpeed, so the port and the controller work at USB 3.Same result on a second PC, also on Windows 11 26H2.Even at USB 2 speed, Link is unusable: black screen at launch, or heavy freezes (the image stays frozen when I turn my head), crashes, and around 15 FPS.What I already triedFlipping the USB-C connector on the headset side: no cha

591.86 WHQL — January 27, 2026 was the last working drivers from Nvidia that meta quest link supports. Since February 26, 2026. Nvidia 595.59 WHQL update and onward has caused a wide spread issue were Meta quest headsets have been crashing (screen freezes on a frame and tears) after 1 to 20 mins. For me personally its about a minute.It has been exactly 193 days since there has been a working version quest link for currnt drivers. I have multiple friends that have experienced this problem. I see countless post on reddit even now and even on these forums about this issue. And it hasn't been address at all. Its been just over half a year since I have been able to play games on the latest Nvidia drivers without having to install older Nvidia drivers to use for VR games. This is how me and many other people have gotten around this problem since many new games don't work with older drivers. I have upgraded from a 3080 to a 5080 / new pc (not related to VR breaking) and prayed that it would f

I’ve been dealing with this for about a month now and I’m completely out of ideas.My Quest 3 constantly says “Charge Only Cable Detected” when connected to my PC instead of connecting through Quest Link.I’ve already tried:2 different dedicated USB cablesMultiple USB ports (front + rear motherboard ports)A completely different PCUSB/Windows power-management settingsUpdating/reverting NVIDIA drivers (tested both)Updating motherboard USB driversReinstalling and repairing Meta Quest Link countless timesFactory resetting the headset 3 timesDeveloper USB mode on/off (both tested)Restarting everything dozens of timesReversing the USB-C cablePretty much every other troubleshooting step I could findThe exact same issue happens on another PC, so this doesn’t appear to be isolated to my computer. And NO it is NOT my computer my specs are the following,Amd Ryzen 7 7800X3DRTX 5060 ti32 DDR5 Ram 

 SummarySeverity: High — prevents reliable extended PCVR useAffected product: Meta Quest 3 / Wired PC LinkConnection: USB 3 wired LinkCurrent Link version: 208.0.0.57.535Previously affected: 207.0.0.133.434Quest OS: v2.7 — Build 5243367.3600.520NVIDIA driver: 591.86 WHQLOne-line failure descriptionDuring an otherwise functional wired Link session, the Quest display stops receiving/updating PCVR video frames while headset tracking continues to be delivered to the PC. The PC application/game continues running.This appears to be a partial Link failure rather than a complete USB disconnect or complete loss of the headset session.Test EnvironmentComponentConfigurationHeadsetMeta Quest 3Link connectionWired USB, 5 m cableOSWindows 10CPUIntel Core i7-6700 @ 4.0 GHzGPUNVIDIA GeForce RTX 5070 TiRAM64 GBMotherboardASUS Maximus VIII RangerQuest OSv2.7 / Build 5243367.3600.520Meta Horizon PC208.0.0.57.535Previous Meta Horizon PC207.0.0.133.434NVIDIA driver591.86 WHQLRefresh rate90 HzApplication us

Latest updates have broken OpenXR for 32-bit applications in Link. Tested and verified with Richard Burns Rally (Rallisimfans version) and HelloXR.It works when running using SteamVR and also with VirtualDesktop. Link works with 64-bit OpenXR applications, only 32-bit that is broken.

For the past three nights, I've ran into multiple different issues (kind of similar), all with different fixes except for tonight. For the last two I've changed the codec to h.265 (common fix for other people), disabling other settings in the debug tool, and reinstalling the app, which all worked up until tonight. I've tried power plans, usb power, global c-state settings in the bios and none of those have fixed the delayed/wobbly display to my quest 3. I have ruled out different cables as well (problem eventually persisted on both). I have no idea what else to try since I've ruled out everything to my knowledge without a fix. I have to assume its from one of the many broken updates.Edit: it ended up being the bitrate set too high (was at 500mbps, setting it to 200 fixed it)

I am reporting what appears to be a regression involving Quest Link after updating to NVIDIA Studio Driver 616.92.System configuration:Quest 3Alienware Area-51 laptopNVIDIA RTX 5090 Laptop GPU (24 GB)Intel Core Ultra 9 27564 GB RAMWindows 11Meta Horizon Link version 207.0.0.133.434Unreal Engine 5.7.4The issue is not specific to Unreal Engine.The Quest works normally in standalone mode.When Quest Link is enabled, one of two things happens.Open Dash remains on "Attempting to connect to PC" indefinitely.Or, PCVR opens successfully but the headset displays severe rendering artifacts.The rendering artifact consists of a correct image in the center of the headset surrounded by a wide black border with irregular zigzag edges. Outside that border are repeated gray zigzag patterns and duplicated fragments of the scene that resemble a lattice.The PC monitor renders the scene correctly.The same rendering artifact occurs with Unreal Engine completely closed while simply navigating the Meta PCVR en

SummaryThe Meta Horizon Link PC app shows "You won't be able to use the Link feature, as your system's hardware is incompatible with it" on a desktop with an NVIDIA GeForce RTX 4070. The card passes every individual check in the service log but is marked FAIL because the Link GPU whitelist only lists the RTX 4070 under PCI device ID 2786 (AD104). Newer RTX 4070 cards built on the AD103 die report device ID 2709, which is not in the whitelist. System- GPU: NVIDIA GeForce RTX 4070 12 GB (MSI), PCI\VEN_10DE&DEV_2709&SUBSYS_51381462&REV_A1- GPU driver: NVIDIA 610.47 (32.0.16.1047), dated 19 May 2026- CPU: AMD Ryzen 5 7600 (whitelisted, reported MINSPEC/WHITELISTED in log)- RAM: 32 GB- OS: Windows 11 Pro 26200- Meta Horizon Link PC app: v207 (OVRServiceLauncher 207.0.0.133.434)- Headset: Meta Quest 3, connected over USB-C Link cable, enumerates fine- Motherboard: MSI B650M GAMING WIFI (MS-7E30) Evidence from the service log (%LOCALAPPDATA%\Oculus\Service_*.txt)- OVRSer

My quest 3 will not pair with the controllers and i get a black screen after a controller animation, this happened out of nowhere 

Before you ask yes I have already done the obvious. I formatted my 4.51 TB external hard drive into an NTFS format drive and ran the following command prompt into Windows PowerShell IN ADMINISRATOR MODE:C:\Users\[My username]\Downloads\OculusSetup.exe /drive=DVERBATIM. And yet I am still getting the same error message as displayed below.I will also provide a screenshot of the drive I am attempting to put this on.As you can see, it is formatted properly as an NTFS drive, and has PLENTY of space. My patience has run thin with this blasted app and I just want some help from people who can actually help me out instead of an AI which will only suggest broken code that does nothing. I am at the end of my ropes here. PLEASE if you can, please help me.

Hello Horizon OS Dev Team, I want to report a specific, reproducible software calibration bug regarding the battery controller logic in Horizon OS 2.7 Beta (PTC). This issue originally started in v2.6. Previous Behavior (On Older Firmware)Previously, on all older software versions, the headset performed flawlessly. During PC-VR gameplay via an active Link cable, the battery charge was constantly maintained at 100%. If the headset was connected to the PC with a lower battery percentage, it would immediately start charging during the game, regardless of the high graphical and processing load. Current Bug Description (On Firmware v2.6 and v2.7)1. Now, during long PC-VR Link sessions via the active cable, the system forces the Battery Care protection mode, safely discharging the battery from 100% and freezing it at exactly 80%.2. When the session is finished and I select Power Off via the software menu, the OS correctly triggers the standard post-shutdown cooling loop where

My PC is more than capable (RTX 4070 Ti), and when Link works, it runs incredibly well — smooth, stable, and with excellent image quality. So this is definitely not a performance issue on my side.The problem started after the recent Meta Link updates. After playing for a while, the VR stream can suddenly freeze or disconnect completely, while the game continues running perfectly fine on the PC.I’ve tried different settings and troubleshooting steps, and I’m clearly not the only one experiencing this. There are now many users reporting very similar issues with the latest Link version.Please, Meta, take a serious look at this. We shouldn’t have to spend hours troubleshooting our PCs when everything was working perfectly before the update.Hopefully a proper fix is coming soon, because this is becoming really frustrating. 😭

Hello, For the past few days, I’ve been having a serious performance issue in VR with my Quest/Meta Link. In VR, I get heavy stuttering and freezes, while the PC works perfectly fine on a regular monitor and games remain smooth. I also completely lose the VR video stream after around 5 to 10 minutes, and sometimes it happens almost immediately after starting VR. When this happens, the VR display/Link connection is lost even though the PC itself continues to work normally. My setup: RTX 4070 TiWindows 11 PCMeta Quest using LinkThe problem only occurs in VR, not on a regular screen. I’ve already performed quite a few tests: Windows system repair/check → everything OKHardware checks → nothing abnormal foundTried different graphics settingsDisconnected a small secondary displayRestarted the PC after disconnecting itTried different VR configurationsThe problem is still there. The strange thing is that everything was working perfectly before. The issue

Hello,I am experiencing a serious wired Quest Link freezing issue with Meta Horizon Link v207.My setup:- Meta Quest 3S- NVIDIA GeForce RTX 5070 Ti- Wired USB Link- Meta Horizon Link PC version: 207.0.0.133.434- Game: DCS World- OpenXRThe issue:Meta Link connects normally and DCS initially works correctly.After I join a multiplayer server and the aircraft finishes loading, the image inside the Quest 3S freezes completely after approximately 5–15 minutes.The frozen image does not recover. I have to disconnect/reconnect Link and enter VR again.I have already tested:- Video Codec: Default- H.264- H.265- Encode bitrate: 300 Mbps- Encode bitrate: 450 Mbps- Restarting Oculus/OVR services- Restarting the PC and headsetH.265 is also unusable on my system because it causes severe stuttering even before launching DCS.None of these changes fixed the freezing problem.Important diagnostic information:I tested the same Quest 3S, the same PC, the same USB cable and the same DCS installation using Stea

As the title says I've been having a long occurring PCVR issue where the image in my headset, a quest pro, will freeze while all other data, being tracking and audio, works perfectly fine, this doesn't happen during steam links new beta that uses USB, though i have other issues with that app, so I'm certain the issue ISNT my cable or my portsi do run other programs but again, steam link didn't have an issue with them and neither did quest link pre v76, if anyone else has or had this issue please let me know what you did to fix it or how are you currently trying to combat it My specs are 4070s Ryzen 5 5600x32gb of ddr4 ramThe programs i run along side meta link are OBSSlimevr serverVoicemodSpace calibratorOVR advanced settingsSteamvrI've attached a video of the frozen in-headset image, whilst recording this everything was tracked fine on my monitor mirroring

Since a few days I have had the issue that every time I start a game the link works fine for about 5-10 Min but then the picture freezes and stays like that. I can still move around hear everything etc. But the picuture stays freezed or gets fully black. I had this a few months ago aswell but managed to fix it somehow now its back again and nothing I tried fixed it.

After around 30 minutes to an hour of playing, the screen freezes and turns off followed by an orange light. I would peek over at the monitor to see that the app itself has crashed rather than the Rift S. It restarts after a couple seconds. Guessing this is a software issue rather than my Rift S bugging out. Could anyone help me with this?

Quest 3 running Horizon OS 2.7 build 5243367.3600.520 has completely lost USB data functionality. The headset charges but does not enumerate as a USB device on multiple PCs. It also does not offer USB data/MTP when connected to an Android phone. The issue persists in bootloader/recovery mode. Multiple known-good data cables have been tested, including cables that successfully transfer data between phones and PCs. Factory reset and port cleaning have also been performed. When you click on link, it just says "Charge only device connected" for every cable.

Hello. Lately, I have been having an issue where when I try to play my Steam VR games using Meta's Horizon Link app, it will randomly disconnect the VR headset from the link entirely. In some cases, the game (from the headset) will freeze and glitch out if I move my head at all. I have never had this issue from my +1 year of playing PCVR with this headset and now this issue has started occurring. I have tried resetting the headset, using a different cable, switching OpenXR(s), and even changing my encoder (from the debug tool) from H264 to H265. I think it might be due to a recent Link update, but I am not sure. 

I have the Meta Quest 3 and I can't reboot, factory reset or side load.  I need my device back.  Has anyone faced this issue?

I don't know why but for some reason I can't launch any games on meta horizon link. It tries opening but then it just closes. I tried reinstalling them, but it didn't work, and I don't know what to do.

Hi everyone,I'm having a frustrating issue trying to launch PCVR on my Meta Quest 2 using a wired Link connection. The headset connects to my PC completely fine, and the Meta Horizon PC app recognizes the connection as active and green. However, the moment I actually try to launch the PCVR/Link environment inside the headset, it gets stuck in an infinite loading screen (the endless 3 loading dots) and never actually launches into the desktop home environment.Here are my system specifications:- Headset: Meta Quest 2- Connection Type: Wired Link Cable (USB 3.0)- PC / Laptop Model: HP Omen 16 Laptop- Processor (CPU): AMD Ryzen 7- Dedicated Graphics (GPU): NVIDIA RX6600MWhat I have checked so far:1. The Link cable test in the Meta PC app passes and shows a solid, stable high-speed connection.2. The Meta Horizon app on the PC is open, updated, and running.3. Audio/Visual drivers on the PC are technically active.Because it's just stuck on the endless loading loop inside the headset, I c

Notification appears every time I try to boot Link.This is a recent issue I have run into since the software was butchered last month. So what's going on with this notification? What on earth is even causing this issue? Nothing that the community have found that would get around this issue works anymore as it's the same error over and over, I have reinstalled the software at least 30 times by now just so I can get thing to connect to oculus dash and it won't even do that.So where is this support article that the notification claims to exist because when I click on it to open the article....I get my account's friends list instead. WHOOPS.