Forum Discussion

unavi3g's avatar
unavi3g
Honored Guest
1 month ago
Solved

Link needing PC restart to reconnect

Hello,

I've started having this issue just recently, as it was working fine before. Basically the meta link would work fine until 5-10 minutes in, then the headset display would freeze, though the audio and head movement did not. Restarting the headset and re-plugging the link cable in don't work, and if I were to disconnect the horizon link, then no matter what I did, the link would not connect anymore. The only way to get the link started again that I've found is to just do a full PC restart.

I'm using a Quest 3 and a brand new link cable, but I doubt those are the issue. I've tried some fixes I've seen on here but none worked. And before you tell me about AirLink, no, it's too unstable for me to use.

  • unavi3g's avatar
    unavi3g
    1 month ago

    I think I may have found the issue. I did some basic testing and everything seems to work fine now. Granted, I tried a lot of different "fixes" for this, so it might be a combination of different things. Regardless, I'll list everything I tried beforehand

    Latest and most likely actual fix: Downgrading to an older version of the NVDIA Drivers (for Windows 10 in my case), more specifically 951.86 from Jan 27, which you can find with a quick google search.
    From what I've read in another thread, the most recent drivers (595.71 from Mar 2nd) is unstable for VR links.

    Other things I've done before that^:
    - All the fixes listed on the Horizon Meta Link support page
    - Sideloaded the headset software from the Meta website
    - Blocked "Oculus-dash:dash\bin\OculusDash.exe" in Outbound Rules within 'Windows Defender Firewall with Advanced Security' (what a mouthful)

    I'd love to give the credit to the person that I saw the fix from, but I can't find the thread anymore unfortunately T^T

3 Replies

    • unavi3g's avatar
      unavi3g
      Honored Guest

      I think I may have found the issue. I did some basic testing and everything seems to work fine now. Granted, I tried a lot of different "fixes" for this, so it might be a combination of different things. Regardless, I'll list everything I tried beforehand

      Latest and most likely actual fix: Downgrading to an older version of the NVDIA Drivers (for Windows 10 in my case), more specifically 951.86 from Jan 27, which you can find with a quick google search.
      From what I've read in another thread, the most recent drivers (595.71 from Mar 2nd) is unstable for VR links.

      Other things I've done before that^:
      - All the fixes listed on the Horizon Meta Link support page
      - Sideloaded the headset software from the Meta website
      - Blocked "Oculus-dash:dash\bin\OculusDash.exe" in Outbound Rules within 'Windows Defender Firewall with Advanced Security' (what a mouthful)

      I'd love to give the credit to the person that I saw the fix from, but I can't find the thread anymore unfortunately T^T