Skip to main content
Highoctan
Participant
August 28, 2026
Question

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

  • August 28, 2026
  • 73 replies
  • 5109 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

    Show previous replies
    SirMittensIV
    New Participant
    August 29, 2026

    It's always such a pain whenever they update literally anything. Really doesn't seem like they know what they're doing

      Maccyb123
      Honored Contributor
      August 29, 2026

      SirMittens_IV​ It's a bit more complicated than just blaming Meta. It's a double edged sword. Meta update their link software based on existing drivers, then PC makers bring out updated drivers that again, the Meta team have to adapt to. The big problem is that pc updates don't take into account how it will affect 3rd party software like Meta's link. People are also under the mistaken impression that it only happens to Quest headsets. It's not. If you check reddit posts, every headset brand has the same frequent problems due to PC updating. What makes it even more confusing is that the updates that mess up link are not arriving on all PC's at the same time, so some will have absolutely no problem because the update took so long Meta had time to fix it. In fact the vast majority of people have no issues. So, it's overly simplistic to blame Meta or other brands that have this problem as they are always playing catch up. Crying about it won't change that. My buddy has a Vive and he tells me it's happening every month without fail after driver updates from Nvidia to his pc. It's an issue that should be solved but maybe pc makers don't think VR is important enough to consider when updating. 

        BulczeskY
        New Participant
        August 29, 2026

        Hi guys,

        I have exactly the same problem.

        I’m using an Oculus Quest 2. After launching any game via cable, the game freezes in the headset after a short while. The image gets stuck in the googles. Distorted black borders appear at the edges of the view when I move my head from side to side. Meanwhile, the game continues to run without issues on the PC.

        I’ve never had this problem before. I have the latest graphics card drivers installed: NVIDIA 616.56.

        My PC specs:

        5090 Zotac Solid
        Intel 14900K
        64GB DDR5 6000 MHz
        Windows 11

         

        the cause might be the new version of the Meta Horizon Link software 2.7

        Let's hope the developers look into this matter quickly.

        Thank You.

        Best Regards.

          dariocs
          Participant
          August 29, 2026

          Hello again,

          In the DCS forums they say it may be caused by some strange interaction between the latest Nvidia drivers and the latest Meta Link software. The temporary solution could be rolling back Nvidia drivers to v610.74, since fortunately Nvidia allows that. See:

          https://forum.dcs.world/topic/391597-vr-freeze/?do=findComment&comment=5807372

           

          herve177
          Participant
          August 29, 2026

          Hi, that’s exactly the problem. Yesterday I updated my Nvidia drivers to the latest version and experienced freezes every 10 minutes. I reverted to version 610.74, and I haven't had any issues since.

            dariocs
            Participant
            August 29, 2026

            It seems we have two solutions, the H.265 codec and the Nvidia drivers. Can we confirm both are working? It would give a hint of the root cause of the problem to the developers.

            HighoctanAuthor
            Participant
            August 29, 2026

            I installed the latest Nvidia driver (version 616.56 from August 26, 2026), and switching to the H.265 video codec solved the problem for me.

              markhagan146
              New Participant
              August 31, 2026

              Quest 3 wired Link repeatedly freezes after ~15–20 minutes — Meta Horizon Link 207.0.0.133.434

              I'm experiencing what appears to be the same wired Quest Link problem being reported with the current v207 Meta Horizon Link software.

              System:

              • Meta Quest 3
              • Wired USB Link connection
              • Meta Horizon Link PC version: 207.0.0.133.434
              • MSFS 2024
              • NVIDIA GPU
              • Virtual Desktop is not being used

              The Link connection initially works normally and I can fly in MSFS 2024 in VR without any problems. However, after approximately 15–20 minutes, the VR display freezes and the graphics inside the headset become corrupted/strange. The PC and MSFS continue running normally in the background.

              After this happens, the Quest reports:

              "Can't connect to PC. Make sure Meta Horizon Link is installed and running."

              The Meta Horizon app is running and the USB cable is still connected and charging the headset.

              I have tried:

              • Restarting the Quest 3
              • Restarting the Meta Horizon PC app
              • Different USB ports
              • H.264 and H.265 video codecs
              • Leaving the headset connected to Link for an extended period beforehand

              The most useful finding is that restarting OVRService / Oculus VR Runtime Service restores the Link connection. I can then reconnect and fly again, but the problem returns after another period of VR use.

              I have now reproduced this several times. The PC itself does not crash during these VR freezes — MSFS and Windows remain running.

              This only started happening after the recent major Meta Link update. The previous version was working normally for me.

              The H.265 workaround mentioned in this thread did not resolve the problem in my case.

              Hopefully this helps Meta identify what is happening with the v207 Link runtime.

                dariocs
                Participant
                August 31, 2026

                Try also rolling back Nvidia drivers to v610.74 or earlier. This has worked at least for some DCS users.

                  Hitmanhepp
                  Up and Coming
                  August 31, 2026

                  I'm also having this problem. Changing the codec to H.265 doesn't work, I'm using a quest pro

                    Slipknot765432
                    New Participant
                    September 1, 2026

                    video codec fix h.265 did not fix.
                    nvidia driver roll back did not fix the problem either.
                    maybe AI coders f ing it up? judging by quantity of recent updates.
                    Anyways after fix I'm never gonna update link app anymore. (just by back-uping stable one)
                    Marking the issue as "SOLVED" makes it worse. it's not fix or solution it's workaround for some. if meta doesn't care it means no future purchases and its product going to straight into garbage. 

                      herve177
                      Participant
                      September 3, 2026

                      Hello , its not meta ,it"s nvidia problem:

                      NVIDIA's recently released GeForce Game Ready 616.56 WHQL driver has developed a noteworthy display regression, with users reporting flickering, brief black-screen flashes and unexpected brightness changes on monitors operating with 8-bit-per-channel output. The issue appeared in the days following the August 26 driver release and has now been reproduced across multiple monitors and GeForce generations. Reports indicate that the problem can occur on the Windows desktop and inside Chromium-based applications rather than being restricted to games, pointing toward the display pipeline rather than an individual game's rendering engine. The most consistent workaround discovered so far is unusually simple: switch the monitor from 8 bpc to 10 bpc color output. Affected users with compatible displays can open the NVIDIA App or NVIDIA Control Panel and change Output Color Depth to 10 bpc. Multiple reports indicate that the flickering stops immediately after doing so. Windows Automatic Color Management (ACM) has also reportedly eliminated the issue in some configurations.

                      property of meta quest 3 screen:

                      uses standard 8-bit LCD screens (per eye), rather than 10-bit panels.

                        markhagan146
                        New Participant
                        September 7, 2026

                        No, this is a different problem caused by the recent update to the Meta Link software. Symptomatic issues are freezing, where the game continues to play in the background, and strange graphic displays. This occurs anywhere between 5-30 minutes of vr use and started occurring, at least for me, before the last two Nvidia driver updates.

                        JayDewa26
                        New Participant
                        September 8, 2026

                        I am having the same problems, at the start I could run Iracing for 30 mins until the vr freezes causing me to disconnect from a race. Now I cant even launch into the Meta Vr. Anything we can do? or just have to wait till Meta fixes it?

                        Show more replies
                        Terms & ConditionsAccessibility statement