Skip to main content
Participant
August 28, 2026
Question

The latest updates have rendered Meta Quest PC Link completely unusable.

  • August 28, 2026
  • 73 replies
  • 5113 views

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.

73 replies

Participant
September 13, 2026

Last year meta screwed link cable with an update that remained for months without fix, ever since I downloaded the updated that fixed it, I havent updated the firmware and I am still getting this issue now

New Participant
September 13, 2026

Same here, the casting doesnt even last around 5 minutes before my meta quests view completely freezes but you could give the time around another 15 minutes by changing the codec in the oculus debug menu 

 

New Participant
September 15, 2026

For those who blame nvidia only, please answer these questions.:
why after the "freeze" if you disconnect cable you still get "connected" status in the link app? also the headset itself still "thinks" it's connected to link so I'm having to reboot headset, why?
I see 2 problems in sender and receiver. so after update the sender "link server" crashes and hangs in the memory of pc, so link app sees it as active connection.
on receiver side (headset) after the latest update it thinks it's connected as link app doesn't send handshake request. so yeah both of the sides are cooked.
Nvidia is for rendering and encoding. so if you see incorrect rendering or bad encoding you can blame Nvidia but for the software that supposed to connect your pc and the headset all the blame and shame on meta. 
what happened for about a month? nothing. yeah there were some updates but nothing was fixed. waiting for Nvidia? for what? Meta should adapt under Nvidia not the way around.  

Participant
September 17, 2026

hello , the only thing meta found for the bug , Bravo Meta....

 

steve40
Honored Contributor
September 18, 2026
New Participant
September 18, 2026

Rift S – Meta Horizon Link crashes and becomes completely unresponsive after recent updates

I would like to report a recurring problem with Meta Horizon Link and Rift S that appeared after the recent Meta Link updates.

My setup:

  • Headset: Oculus Rift S
  • GPU: NVIDIA RTX 4070 Super
  • CPU: Ryzen 9 3900X
  • RAM: 64 GB
  • OS: Windows 11
  • Meta Horizon Link: 207.0.133.434
  • PCVR games: mainly Assetto Corsa and Elite Dangerous

The problem has two related symptoms.

  1. Random crash during VR

During a normal VR session, the Rift S suddenly goes black. There is usually a short beep followed by a brief "radio/static" sound. The headset then disconnects and restarts.

At the same time, Meta Horizon Link may crash or become completely unresponsive.

Windows Event Viewer showed multiple crashes involving the Meta/Oculus runtime.

One of the Oculus exception reports showed:

OVRServer_x64.exe
Version: 207.0.133.434
Exception: ACCESS_VIOLATION
Exception location: OVRInterfaceShutdown

The call stack contained multiple entries from:

RiftS.dll
RiftSTracker.dll

including Rift S HID-related functions.

Another Event Viewer crash showed:

Application: dwm.exe
Faulting module: nvwgf2umx.dll
Exception code: c0000005

So there appears to be an interaction between Meta Link, Rift S components and the NVIDIA graphics stack.

  1. Rift S sleep/wake problem

There is another reproducible problem which occurs when I remove the headset for several minutes.

The Rift S goes into standby/sleep. When I put it back on, the headset does not wake up and the VR session is not restored.

The game itself can continue running on the monitor, but the VR session is lost.

In some cases Meta Horizon Link also becomes completely frozen. The application cannot be closed normally and has to be terminated through Task Manager.

Restarting the Oculus/Meta service using a third-party VR service utility restores the headset and PCVR functionality without rebooting Windows.

This makes me suspect that the problem is not simply the Rift S proximity sensor or USB connection, but that the Meta Link runtime gets stuck while trying to restore or terminate the Rift S session.

NVIDIA driver testing

I also tested different NVIDIA drivers.

The current Meta recommendation led me to NVIDIA 591.59, but the crashes still occurred on that driver.

I then performed a clean installation of NVIDIA 572.83.

So far, after switching to 572.83, the random black-screen/crash problem appears to have disappeared, although I need more time to confirm this conclusively.

The sleep/wake problem still needs to be tested separately.

This is interesting because it suggests that the NVIDIA driver can be a trigger, but may not necessarily be the root cause.

The same hardware worked normally with newer NVIDIA drivers several months ago, before the recent Meta Link software changes.

My conclusion

Based on the logs and testing, I suspect there is a regression in the recent Meta Horizon Link PC software, particularly in the Rift S runtime/session management.

The NVIDIA driver may expose or trigger the problem, but simply stating that "NVIDIA drivers are the problem" does not fully explain the behavior.

In my case, the Meta runtime itself is crashing in:

OVRServer_x64.exe
- RiftS.dll
- OVRInterfaceShutdown
- ACCESS_VIOLATION

and RiftSTracker.dll is also heavily represented in the crash stack.

I would really appreciate it if the Meta engineering team could investigate the recent Link releases, especially the Rift S runtime and the sleep/wake/session recovery mechanism.

There are many reports from other users describing very similar behavior, including Quest headsets as well as Rift S, so this does not appear to be limited to a single defective headset.

Please investigate the Meta Link software/runtime rather than treating this only as an NVIDIA driver issue.

Inspiring
September 18, 2026

I think my system is working correctly again, been through a bad week with this, the cable link looks like it is finally working correctly again,, just now,,, countless hours of getting it straightened out.

Asus Strix Z790-H, Intel 13900 CPU. Nivida RTX 5070-TI OC video. 64 GB Ram.  5TB SSD memory. Oculus Rift S.
ReiDivine
New Participant
September 24, 2026

Ah.. and they still haven't fixed the issue yet..

New Participant
September 25, 2026

I don't normally leave replies or reviews, but this is seriously ticking me off. So I can link through meta quest link, that part is fine, it's what's right after that's not. I sit in a black screen forever, and I mean forever. Everything is up to date, no firewall, or antivirus is blocking GPU, and all that's good, but I just see a black screen. Like it loads then nothing, and i've already tried what acouple of you have recommended but still nothing. So like Meta wth!!!

New Participant
September 26, 2026

Also having this issue and nothing I've read will fix it. Headset freezes but everything else keeps running as normal. Guaranteed freezes after 10-30 minutes.

Win 11, 4080, 32gb DDR4, i7 12700K, using Meta USB-C link cable

Unacceptable