Forum Discussion

olavrv.2025's avatar
olavrv.2025
Protege
1 month ago

Meta Link freezes after a few seconds

After installing latest Meta Horizon Windows app update (85.0.0.239.552), the display inside headset freezes (sometimes goes black, similar to when proximity sensor kicks in, but while still wearing VR headset)  after a few seconds after establishing cabled link (official 5m cable). Have to restart PC and re-establish Link to get it to work again, but then same happens after a few seconds. Can still hear audio inside headset, and when using games it seems to do head tracking (monitor screen updates, but not inside headset). This also happens inside the Meta Link view (grey environment with grid floor and ceiling inside VR headset after establishing link).

Firmware in VR headset is also on latest version,

This happened after updating Meta Horizon Windows app on 3rd/4th March. Before this it was working perfect.

Have tested this on 4 different PC's, with 3 different Meta Quest 3 headsets and one Quest Pro, with same result.

Hardware on test PC's:

Windows 11, different i9 processors (13th/14th gen, Intel Core Ultra 9), RTX 5090 laptop, RTX 5070 Ti Desktop, RTX 4090 desktop. 64GB RAM, 

NVIDIA GeForce Graphics Drivers 595.71 WHQL driver + latest Windows updates

30 Replies

  • steve_40's avatar
    steve_40
    Honored Visionary
    1 month ago

    Seems like a few people are having this issue. Is it only affecting cable connections, not AirLink?

    I'm also on v85.0.0.239.552, but I haven't tried playing any PCVR games since the last update yet.

    similar to when proximity sensor kicks in

    Have you tried setting the Oculus Debug Tool "Bypass Proximity Sensor Check" toggle to "ON"?

    Report the bug via the Link PC app Help Centre>Provide Feedback.

    manny.prerelease68​ it looks like there may be a new emerging Link bug affecting cable connections. The issue is also reported here:

    VR screen is grey after 5 ish minutes of use on quest link | Meta Community Forums - 1368350

    • olavrv.2025's avatar
      olavrv.2025
      Protege
      1 month ago

      I think you are correct, thanks for sharing info! It seems to work with airlink

  • olavrv.2025's avatar
    olavrv.2025
    Protege
    1 month ago

    Seems like reverting to an older NVIDIA driver from january 2026 resolves this issue.

    • totaison's avatar
      totaison
      Honored Guest
      30 days ago

      i have the same issue, its related to nvidia drivers? what driver version is still working?

  • Neuz4n's avatar
    Neuz4n
    Honored Guest
    29 days ago

    Exactly the same thing happens to me, have you found a solution? or do you just have to wait for them to fix it?

  • TomCgcmfc's avatar
    TomCgcmfc
    MVP
    29 days ago

    I suggest you roll back your nvidia driver to 591.74.  You also may want to consider using DDU in Safe Mode to fully uninstall previous drivers beforehand (google how to do this).  The nvidia 595.xx series still seems a bit buggy imho.

  • NeilCHicks's avatar
    NeilCHicks
    Honored Guest
    29 days ago

    Same issue. The problem is solved by installing an older version of the Nvidia drivers. I'm using 591.86 and it's all working fine now.

    I haven't experimented with the Air Link option, so I can't say whether that's also affected.

    Specs: Alienware 18 Area-51, Intel Ultra 9 275HX, Nvidia RTX 5070, 32GB RAM, Windows 11 (25H2), official Oculus 5M Link cable.  Optimus disabled.

    • TomCgcmfc's avatar
      TomCgcmfc
      MVP
      29 days ago

      I found that 591.74 performance was a tiny bit better than 591.86, but there wasn't much in it.  Both are good drivers imho.  The nvidia 595.xx series has been a buggy mess, lol!

  • crispydawg_1's avatar
    crispydawg_1
    Honored Guest
    29 days ago

    Does anyone know if the new 595.79 update fixes it, it says it fixes application and timeouts?

    • TomCgcmfc's avatar
      TomCgcmfc
      MVP
      29 days ago

      I tried 595.79 and it worked ok for me.  I rolled back to 591.74 because I think it gives me a little better pcvr performance.

  • mcdousker's avatar
    mcdousker
    Honored Guest
    29 days ago

    I just purchased a Quest 3s a few days ago and havent been able to get it to connect via Link Cable to save my life. Ive tried so many different fixes on the internet and none have fixed it. 

    I use a AMVR Link Cable with Charging, plugged into a 3.2 USB Port on the IO of my mother board, rated for 10Gbs. Half the time the quest detects there's a USB plugged in but doesn't give the Link option. When it does give the link option I hit launch. THEN there's a 50/50 shot it freezes in the purple horizon loading screen or it loads into the desktop VR. When it loads, I open VRC for example, the game will get about 10 seconds into loading then it freezes/BlackScreens. Then I have to re attempt the whole process. Ive gotten it to work ONE time and that was 2 nights ago. Zero clue what I did differently but that shows me its possible.

    I want to avoid AirLink/Virtual Desktop because I want to take advantage of my PC's specs. And also I don't have access to my router for a wired internet connection. 

    I know this probably inst the forum to post this in but im so fed up with trying to make this $300 paper weight to work the way its supposed to. Been stuck using an Rift S until I can get the Quest to function normally. 

    • totaison's avatar
      totaison
      Honored Guest
      29 days ago

      In my case, before to roll back to january nvidia drivers, I make a clean reinstall of newest nvidia drivers (595.79) like image below, not easy installation, but custom, and click perform a clean installation. And it works well for me. Other thing you can try is test your cable in meta link software, yo know if its fully compatible (nearly 2,5 gb mine). And if still no working, use directly Virtual Desktop (paid) or Steam link (free) via wifi, it works nearly perfect. Meta software always have some issues or bugs, honestly.

      Its a internet image, dont look at version :) 

    • NeilCHicks's avatar
      NeilCHicks
      Honored Guest
      29 days ago

      Hi,

      Like you, I only purchased my Quest 3 a few days ago. I've been using a HTC Vive Pro 2 to date, so the whole Meta thing was new to me. With everything fully up to date on my system, it just continually crashed once I launched into the PCVR Link 'purple' screen. If I was lucky, it would work for, maybe, five minutes, but would generally freeze after 30 to 60 seconds. Frankly, I was ready to junk the Q3, until I went into this forum! As suggested by many, I downloaded and installed an older version of the nvidia drivers, dating back to January 2026 (no fancy deleting the old drivers, btw. Just a quick double click on the .exe!), and it fixed the problem. Just to satisfy my masochistic tendencies, I re-tried the latest nvidia drivers for a second time, and the problem returned, 100% of the time. I then re-reinstalled 'ye olde' v591.86, and it was back to 100% good!

      Easy fix!

      • alex.kew1's avatar
        alex.kew1
        Protege
        19 days ago

        Quest Pro user here.

        591.86 worked for me too, like you just downloaded and ran the exe - no fuss!

  • Lellyna's avatar
    Lellyna
    Honored Guest
    23 days ago

    this has caused me so much headache i bought a new cable cos i thought mine was damaged but it turns out all i need to do is downgrade my drivers lol

  • Foapyslies's avatar
    Foapyslies
    Explorer
    20 days ago

    I’ve been having this exact issue. I’m able to play Ghosts of Tabor for mayybbeee a couple raids and then itll freeze. Still have tracking, and sound and can move around in game but it’s stuck on one image. I’m going to try what you said. Reverting to januarys driver on nvidia because I had no problems until I downloaded the new drivers