Skip to main content
Participant
May 3, 2025
Question

Random disconnecting after Meta Quest 3 v76 update (April 2025)

Hello everyone,

I would like to ask if anyone has been encountering issues after the last April update, around 24th April to be exact. I mainly use the headset with wired link to play VR sim racing. Before this update, I had absolutely no issue, shortly after the install, the VR connection is lost after about 15-30, after an intense session.

Is there any fix for this? I saw that there is no way to roll back the driver... which is quite a shame. I was so excited after I bought it and set it up, only to have it crash now every half an hour.

    122 replies

    Participant
    May 10, 2025

    If link is not starting on Windows, kill it with the task manager, then restart the oculus VR services via services.exe. Then launch meta quest link again.

    As soon as that runs, you can connect with the headset.

    Participant
    May 10, 2025

    Unfortunately I did experience another hang

    Participant
    May 10, 2025

    Ok... I tried it right now with the new (working) USB port and I can confirm (on my part) that meta quest link app does NOT work online no matter what.  It took 20-30 seconds (on splash screen) to start, then I launched the desktop link and it got stuck on the meta logo (with the black background.) couldn't connect to desktop.

    Whereas if I block internet connection of Meta Quest Link app (before even starting it) the app will open instantly and the desktop link works instantly. Which means that there is some kind of problem to communicate with the server or.. who knows.

    I have a

    • clean windows installation
    • working cable
    • working USB port for sure.
    • clean installation of Meta Quest Link app  

    If the app starts in "offline mode", everything works like a charm.

    Restarting the OVRserver service doesn't work on my part.  So personally I will keep using it offline for a while.

    Participant
    May 10, 2025

    This is exactly what I did: 

    • Disable wifi connection on Quest 3 and turn it off.
    • Seek for the already present entry in windows defender's advanced firewall rules called "Oculus-client:Oculus Client.exe Outbound" and block the connection.
    • Restart computer and/or restart OVR service.

    From now on (until it is kept offline)  both the Meta Quest Link app and the connection with the desktop will open and never hang, even after restarting. 

    https://streamable.com/h52q7y

     

     

     

    Participant
    May 10, 2025

    That didn't work for me. Still crashes

    New Participant
    May 10, 2025

    I’m having the exact same problem. I also use it for Sim Racing which I can’t play currently. If you go into program files or wherever you have, the Meta software downloaded go into the oculus folder and then go into the oculus set up. It will give you the option to fix the software, which will temporarily Fix the problem. Temporarily meaning, maybe an hour . it sucks and I haven’t seen anything from Meta acknowledging this at all. If they don’t Fix this I’ll never buy another Quest/headset/smart glasses or anything Meta 

    Inspiring
    May 11, 2025

    Your crashes are really strange.
    Since V76, I couldn't even get into my game from the Oculus Link home screen (the 3D area with the lines on a gray background) because there were lags and artifacts when I moved my head.
    I was using the official Oculus USB-C cable.
    If you see the Meta logo with the dots, stop, it means the program is down, so repair the program either via Windows in Settings/Applications/Modifier, which will allow you to repair it. Or by downloading the program again, which will see that the program is already installed, allowing you to repair it.
    During this operation, do not connect your QUEST 3!
    Then restart Windows -> open the Oculus program -> connect your QUEST.
    If you're using the Oculus cable, you should no longer connect it directly to a USB-C port on your PC! Use a USB-C to USB-A adapter (with blue data transfer) and connect it to a blue USB-A port on your PC. NOT a red or black one, a blue one!!!
    OR buy a USB-C to USB-A cable online, like the INIU DI-401 for €27. This cable requires connecting the QUEST charger, and your QUEST will remain at 100% battery life at all times.
    If you're still experiencing crashes, it may be because your settings in the Oculus Debugging Tool and the LINK program are no longer correct or too high!
    Run some tests at the recommended 72Hz to verify this, and reset the Oculus Debugging settings.
    It might also be a good idea to uninstall the LINK program and clean up any remaining Oculus files (APP DATA in USER, they're hidden, so change the folder display in Windows). And then perform a clean install.
    Removing Windows' fast startup feature may also be a solution worth trying.

    Participant
    May 10, 2025

    Hey everyone,

    They pushed an update 2 days ago still under v76. The problem is, I couldn't test for more than 10 min and see if the disconnection issue has been solved because they screwed the frame pacing. Same settings as before, it stutters every 5 seconds and the game is unplayable.

    At this point I am lost for words, I keep the headset on the table as a paper weight. 

    Participant
    May 11, 2025

    Updated to v76.1025, it's a no go. Actually, upon connecting to the PC, the headset freezes within 10 seconds. Before v76.1025, it would disconnect after about 5 ~ 10 minutes. I have reached out to support (email) and chat without resolution unfortunately. 

    Participant
    May 11, 2025

    META really needs to fix this issue ASAP. However, has anyone tried a splitter - 1 for power and 1 for data? Like this: https://www.amazon.se/Seminer-OTG-Adapter-Typ-C-Laddare-Splitter-Chromecast/dp/B0DCBNGXKG/

    Inspiring
    May 11, 2025
    Participant
    May 11, 2025

    Do you own this and does it work without crashing link? Also does the charging level never drop to 0%?

    Participant
    May 11, 2025

    The cable and/or converter options do not work for me.