Skip to main content
Currosport
New Participant
May 14, 2026
Question

Link connection get freezed

  • May 14, 2026
  • 23 replies
  • 1994 views

ENG: 

Since the major OS update, the Link cable connection has been failing and randomly disconnecting for a moment, freezing the VR image and making it impossible to reconnect without fully restarting the PC.

I mainly use the headset for sim racing (iRacing, LMU), and this happens quite frequently.

My headset settings are not aggressive. After several attempts and configuration changes, it can sometimes last a few hours without issues, but then it suddenly freezes again. The game and the headset itself continue working — I can still see on the monitor that the headset movements are being tracked in-game — but I cannot see anything through the headset anymore.

I do not currently use an official Link cable (although I have ordered the official €80 cable to test whether it solves the issue), but I never experienced problems like this before. Everything started after the major Meta OS update.

Since then, I have also experienced zombie processes that would not close properly, causing the image to run at 2 FPS and leading to crashes. Now this. 

SPA:

Desde la gran actualización donde se cambia el SO, el cable link falla y se desconecta por un momento, congelando la imagen de VR y haciendo imposible volver a conectar sin reiniciar el PC entero.

Suelo jugar a Simracing con ellos (iRacing, LMU) y me pasa con bastante asiduidad. 

La configuración de las gafas no es agresiva. Después de varios intentos y cambios ha aguantado unas horas sin quejarse hasta que de repente se congela. El juego y las gafas siguen funcionando, incluso en la pantalla sigo viendo como las gafas están aun provocando movimientos en el juego, pero no puedo ver nada desde ellas.

No tengo un cable Link oficial (he pedido el cable de 80 euros para ver si con esto se arregla) pero nunca había tenido problemas así, solo desde la gran actualización del SO de Meta. Desde entonces, procesos zombieficados que no se apagaban, provocando que la imagen fuera a 2 Fps y crasheos. Y ahora esto...

PD: I tried a clean install of Nvidia Drivers + Turn off Meta Notifications. After some days testing, Meta Link crashed again and freezes. Doesnt work

    23 replies

    repalesfin
    New Participant
    May 15, 2026

    same problem. I bought quest and link caple last october so these arent even old yet.

    I also use link and ques only for simracing.  I play Raceroom and in best times i can drive even couple of laps in sigle play.  

    But when i start racing online quest crashes usually in first lap. Picture freezes and game continue but i cant see anything. I can hear soud of the game.

    It seems like link suddenly disappears because quest cant find link caple anymore.

    I have dried use another port in my pc but nothing is helping.

    I use official Meta link caple. first i think that problem is in caple but now i read your message and i think problem might be in somewhere else...

    repalesfin
    New Participant
    May 15, 2026

    And link starts working only after starting my computer again...

    But my quest is useles without working link...

    kike81
    New Participant
    May 15, 2026

    Exactamente el mismo problema con cualquier juego. Es desesperante y nadie ayuda ni se obtienen respuestas desde Meta. Ahora mismo si me piden que les recomienden son un 0 absoluto. Siento que he tirado el dinero con las meta quest 3

    DragonGirl118
    New Participant
    May 16, 2026

    I been having the same issue ever since my NVIDIA drivers updated. Many say rolling back helps but at the same time it takes away from other apps that needs the new update to function. At this point im begging Meta app to update their drivers or hope next NVIDIA update helps but im unsure at this point

    CurrosportAuthor
    New Participant
    May 17, 2026

    After some reads, I decided to test the option of a clean install of Nvidia Drivers + turn off Meta notifications. Still looking for freezes but everything seems ok. I will update

      perfectirony
      New Participant
      May 19, 2026

      I am getting the same issue. I am using recent Nvidia drivers and official meta quest link cable. I run endurance races in iRacing and have all year competed in 3+ hours races with no issues.

      However just over a week ago I was 45 minutes into my race and VR stopped working. The game continued running on my PC however and I could use the headset to still look around. Inside the headset image frozen but if I look behind me black and white graphical artifacts. . I restarted PC, restarted Meta app and headset and re-joined, I was able to then complete the rest of my stint and spectate my team for the next 3 hours no issue whilst in VR.

      Since then though I have been heavily testing, and have run multiple 90 minute sessions+ this week with no issues, but randomly on 2-3 occasions I get the same issue after 25-45 minutes (never longer, if it goes longer than 45 minutes without crashing it doesn't seem to crash at all and goes on indefnetly)

      But now I am very nervous gaming.. especially as we are doing an event at the weekend.

      I don't believe anything has changed with my drivers, settings, PC etc and I am loath to make any big changes as I don't believe anything to be faulty. 

        CurrosportAuthor
        New Participant
        May 20, 2026

        same here. Im in a iRacing League and my 1st race with DNF because VR freeze. Im testing now the "solution" what is about take Nvidia Driver to 591.86. I hope tomorrow's race doesnt get ruined by this again

          CurrosportAuthor
          New Participant
          May 31, 2026

          UPDATE: I tried reverting to an older NVIDIA driver version, and the issue appears to be resolved. Until I see reports confirming that the latest NVIDIA drivers no longer cause problems, I think sticking with an older driver is the best solution for now.

            robergv5
            New Participant
            June 20, 2026

            Hi all

            I have the same problem since the last major OS update. I play LMU and it is very frustrating when the Quest freeze in the middle of a race. I will try to install the last NVIDIA driver (610.62 from June 16) and if it still fails I will downgrade.

            Hopefully Meta looks into this problem

            Thanks

            Wulfaxe
            New Participant
            July 21, 2026

            same problem with AMD tho it just took longer to start, cannot connect via USB3, using ports freeze link, i can only play on USB2, and i don't have good Wi-Fi to play airlink 

            steve40
            steve40
            Honored Contributor
            July 22, 2026

            You already posted elsewhere that it was due to a bad cable 🤷‍♂️.

              Wulfaxe
              New Participant
              July 26, 2026

              yeah, i did, me and a friend have the same cable so he lend me to test it, now i know, yall got mad at me for not having all the cables while i was desperate searching for a solution, thanks

              JPSmall007
              New Participant
              July 29, 2026

              Meta Support doesn’t monitor these threads?  Seems they may be able to help on the Meta Link driver side instead of users rolling back their Nvidia drivers.  Hmmm

              Maccyb123
              Honored Contributor
              July 29, 2026

              Yes, unfortunately since the end of 2025, nobody from Meta is monitoring these threads. 

                RenaudS
                Participant
                August 3, 2026

                This issue has been around for years.

                I resolved it by doing the following:

                - Reinstalled the latest NVIDIA drivers using a "Clean Install" to reset any corrupted configs... You lose nothing by doing this.

                - Removed the outbound firewall rules for: "oculus-client:Client.exe Outbound" and "oculus-dash\dash\bin\OculusDash.exe Outbound"

                In the Debug Tool, I adjusted these settings:

                - Video Codec: Forced to H.264 (this is crucial because my RTX 5080 uses H.265, and Meta's drivers are completely buggy)

                Meta's H.265 encoder is known to crash the OVRServer_x64.exe service after a few minutes of load due to poor handling of missing packet recovery. Forcing H.264 bypasses Meta's proprietary encoding libraries and uses NVIDIA's ultra-stable hardware encoder (NVENC).


                - Dynamic Bitrate Max: 0 (Disabled)

                Meta's dynamic bitrate algorithm continuously calculates available USB/Wi-Fi bandwidth. On high-end setups, it tries to scale too aggressively or experiences micro-fluctuations. Any slight hesitation causes the encoder to crash. Setting this to 0 disables dynamic calculation entirely.

                 

                - Encode Bitrate (Mbps): 300-400 (I set mine to 300)

                With fixed H.264, a bitrate between 300 and 400 Mbps offers near-perfect image quality without risking buffer overflow on the Quest 3 headset (which freezes or lags when exceeding 500-700 Mbps on the Snapdragon processor).

                 

                Since then, I haven't had any freezing in my headset.

                Hope this helps!

                  mrbob12344
                  New Participant
                  September 10, 2026

                  Do I have to rollback to the 205v version? Or does following these steps work? Im not sure if I should make an attempt to try and downgrade to an older update and try and block updates. Ive already followed all the steps, I havent tried my VR out though. Im basically wondering in these steps you provided are enough


                  Also, another question. Does deleting the outbound firewall rules you mentioned stop it, or does the traffic keep getting controlled by the rule? Im not sure if deleting it immediately stops it; because I deleted both of them.

                  I look forward to your response!

                  Show more replies
                  Terms & ConditionsAccessibility statement