Quest Link stopped working...

[RedLion]

Hello!

I have a question for those who use Quest 3 with Oculus Link Software.

In my case, no extra tools, no extra settings, original Oculus link cable. I have used Quest 3 for almost 2 years. No issues, never!

My Link and device both received updates some days before. Since then, very randomly, the "Link stopped working" error. Sometimes it happens after minutes of gameplay and sometimes I am able to finish the mission.  

Nothing helpful from Meta support.  

I tried to repair the Link Software, factory reset my Quest. Nothing helps!

Has anyone experienced this ever? Any help appreciated!

Thanks!

[av8orDave]

1 hour ago, RedLion said:

Hello!

I have a question for those who use Quest 3 with Oculus Link Software.

In my case, no extra tools, no extra settings, original Oculus link cable. I have used Quest 3 for almost 2 years. No issues, never!

My Link and device both received updates some days before. Since then, very randomly, the "Link stopped working" error. Sometimes it happens after minutes of gameplay and sometimes I am able to finish the mission.  

Nothing helpful from Meta support.  

I tried to repair the Link Software, factory reset my Quest. Nothing helps!

Has anyone experienced this ever? Any help appreciated!

Thanks!

I updated the Meta App, the device, and the NVidia drivers all on the same day a few days ago. Since then, my Quest 3 crashes regularly while in DCS as well as doing other unusual stuff. I've been using Virtual Desktop since then, which also just released a pretty impressive beta update, and it is working as well as I've seen it work. I'd say it is a good solution until Meta gets their act together, which I believe is causing the current Link issues.

[Tensorial_Architect]

When the sh#tz developers at Meta fix one bug they often introduce two new ones. Go to Control Panel -> Device Manager -> Expand the "Display Adapters" sub-section -> Right click on the "Meta Virtual Monitor" -> Choose "Uninstall Device" -> Click Confirm

Now, repeat the process for "Human Interface Devices" sub-section by clicking on every single grayed out HID-compliant consumer control device and uninstalling those as well (this will not hurt anything on your desktop rig).

 

Now, reboot your rig and reboot your Quest 3 (with it attached to your desktop computer by the Quest Link cable). Device manager will create new entries for you. 

There is a roughly 70% chance that your Quest 3 will be back to good working order.

Edited April 28 by Tensorial_Architect

[RedLion]

Thanks guys!

I will post an update for the status asap!

Edited April 29 by RedLion

[AeroGrappler]

Same thing happened to me yesterday after the update so I decided to try (link cable-less) Virtual Desktop, and I'm glad I did!  So much easier to start up DCS in VR and the graphics are WAY better on the basic DCS VR settings than they ever were after making all the tweaks after literally years of watching YouTube videos on how to get the "perfect" setting in about 6 different apps! Haven't felt so good about VR in DCS in probably a year! Highly recommend!

[flybull]

Meta Quest Link broken since last Meta update for many users.  Awaiting fix.  Literally pulled my hair out for a day, reinstalling, restarting, trouble shooting until I found out.  You are not alone - hope that gives some comfort!

[Zligor]

In task manager (win10) i kill all processes related to meta/oculus, then i insert link cable and put headset on, turn it on, start link from headset and it works.

I did not have time to try turning of human interface devices...in device manager.

 

[timcat]

Turn off USB power savings in device manager for all USB hubs. Somehow this got turned back on in one of the updates. It is under properties > power management.

 

[Mik32]

В 28.04.2025 в 21:31, Tensorial_Architect сказал:

When the sh#tz developers at Meta fix one bug they often introduce two new ones. Go to Control Panel -> Device Manager -> Expand the "Display Adapters" sub-section -> Right click on the "Meta Virtual Monitor" -> Choose "Uninstall Device" -> Click Confirm

Now, repeat the process for "Human Interface Devices" sub-section by clicking on every single grayed out HID-compliant consumer control device and uninstalling those as well (this will not hurt anything on your desktop rig).

 

Now, reboot your rig and reboot your Quest 3 (with it attached to your desktop computer by the Quest Link cable). Device manager will create new entries for you. 

There is a roughly 70% chance that your Quest 3 will be back to good working order.

Great! It helps in my case. Thanks a lot!

[Jar_VFA-113]

Yes can confirm, latest update broke my Quest 3 PC link and I was unable to fly our Friday night mission.

Will try out the above fix.

[RedLion]

Hi All

Sorry for the delay 

1. Uninstalled Meta device, by the way after new driver was installed, now it is called Oculus XRSP Interface.

2. Disabled the Power Management on all hubs

3. Quest 3 received some minor update since then.

Unfortunately, nothing works for me! It's a disaster. With no other choice, I'm going to test the Virtual Desktop. Actually, I am really skeptical about it. 1Gb wireless can't be better than 3Gb (in my case) optic cable! Finally, the cable itself cost me $80 and I need to spend $25 more!

Thanks guys!

[Qcumber]

2 hours ago, RedLion said:

Hi All

Sorry for the delay 

1. Uninstalled Meta device, by the way after new driver was installed, now it is called Oculus XRSP Interface.

2. Disabled the Power Management on all hubs

3. Quest 3 received some minor update since then.

Unfortunately, nothing works for me! It's a disaster. With no other choice, I'm going to test the Virtual Desktop. Actually, I am really skeptical about it. 1Gb wireless can't be better than 3Gb (in my case) optic cable! Finally, the cable itself cost me $80 and I need to spend $25 more!

Thanks guys!

Link cable is working for me since the last update (Quest Pro). Have you done another cable test to see if the cable is damaged? Another thing to try is to make sure that the Meta link app is set to open XR. 

If you do you do go for VD it is very similar to link cable in terms of performance and quality. If anything the latest VD update (4 days ago) has the edge due to 2-pass encoding with 10-bit HEVC. However, you will need a dedicated WiFi 6 router connected directly to your PC with an ethernet cable. I bought mine for about £35 so not too bad. 

BTW $80 is a lot for a usb cable. Third party ones cost about $12 and work just as well. 

[RedLion]

15 hours ago, Qcumber said:

Link cable is working for me since the last update (Quest Pro). Have you done another cable test to see if the cable is damaged? Another thing to try is to make sure that the Meta link app is set to open XR. 

If you do you do go for VD it is very similar to link cable in terms of performance and quality. If anything the latest VD update (4 days ago) has the edge due to 2-pass encoding with 10-bit HEVC. However, you will need a dedicated WiFi 6 router connected directly to your PC with an ethernet cable. I bought mine for about £35 so not too bad. 

BTW $80 is a lot for a usb cable. Third party ones cost about $12 and work just as well. 

Hi Qcumber,

The reason for the higher price is that this is not an ordinary USB cable, but the fiber optic cable with a bandwidth of up to 5 Gbps.

https://www.meta.com/quest/accessories/link-cable/

Yes, the Link app is default to OpenXR. I am beginning to suspect the cable itself...

I have a WiFi5 mesh node which is connected to my fiber router with CAT5 cable and PC is connected to the same router with CAT5 as well. I believe this is enough to do the job.

Edited May 5 by RedLion

[Qcumber]

55 minutes ago, RedLion said:

The reason for the higher price is that this is not an ordinary USB cable, but the fiber optic cable with a bandwidth of up to 5 Gbps.

Yes. I have a 3rd party one which meets the requirements. It would be worth considering if you need to replace your cable. Save a few dollars. 

This is the one I got with a charging port. 

https://amzn.eu/d/0eyVfnZ

 

[Hadeda]

On 5/4/2025 at 9:54 PM, Qcumber said:

Link cable is working for me since the last update (Quest Pro). Have you done another cable test to see if the cable is damaged? Another thing to try is to make sure that the Meta link app is set to open XR. 

If you do you do go for VD it is very similar to link cable in terms of performance and quality. If anything the latest VD update (4 days ago) has the edge due to 2-pass encoding with 10-bit HEVC. However, you will need a dedicated WiFi 6 router connected directly to your PC with an ethernet cable. I bought mine for about £35 so not too bad. 

BTW $80 is a lot for a usb cable. Third party ones cost about $12 and work just as well. 

Is the 10-bit HEVC coupled with the new 2-pass encoding the best codec to use in DCS? I'm struggling to find much useful info about it. 

 

Oh, and to stay on topic, my Link cable also stopped being recognised by my QPro about 4 months ago so have been using Virtual Desktop ever since, and am quite happy with it.

Edited May 6 by Hadeda

[timcat]

I've tried everything above and link cable keeps disconnecting. I even purchased a new $80.00 Meta cable and it still disconnects. So now I guess I will try a Wifi 6 router and VD. Let the research begin. 

[dutchili]

I've been in contact with ED support and Meta support on this issue. 

The OVRserver log and oculus dash log reveals a deadlock, meaning the main rendering threat hangs.

It seems very much to be an Oculus bug in either Dash (the virtual dasboard you see before switching to the windows desktop) or OVRserver.
It correlates with the issue of the Meta Link App no longer starting at Windows start (which can be fixed by going to 'services' in Windows and restart the oculus vr service. Then starting meta quest link).

However, getting meta quest link to work does not fix 'this' issue.

 

I delivered the meta logs to Meta in an email chat with support, but it is the developers that need to fix it.

[Ratfink]

This is why since V76 in both QPro and Meta Link, I've switched off auto updates. I get Meta can't test every combination after an update, but I don't expect to become an Android dev just to fix the problems they create! 

Thankfully there's some good, knowledgable and friendly people in communities like this and on Meta forums that provide good suggestions

 

[dutchili]

Good news on my initial test after following this meta support advice:

- Set meta quest link app to 'non beta'.

- set headset to NOT apply automatic software update

- factory reset the headset (via the meta horizon app)

- don't update after the factory reset.

- my meta quest link is now on 76.0.0.452.315

- my headset is (back) on v76.0 (i had v76.1023)

- i played DCS for over 10 minutes without the link or pc crashing.

- the windows event viewer is still flooded with 'OculusVadApoEventTrace' errors, but yet it worked fine.

 

Love to hear if it works for you too.

btw: still need to manually restart the OVR service to get meta quest link to work.

Meta acknowledged that 'there is a potential issue with v76 and PCVR'

[Jar_VFA-113]

UPDATE - Meta Link still broken.

I just checked today after a Meta update and it’s not even connecting to the PC at all now, just stuck on the new loading screen.

I haven’t had time to try your process Dutch but thanks for posting. Am hoping they just fix their software.

[BluesRocket]

Good Lord, it's not just me. If anyone has a router to suggest, I'm all ears. I'm tired of this cabled crap...

[Qcumber]

It looks like this is only affecting Q3. I have not had any issues with QP. 

For VD I use this router but you should also check out the VD discord as they have a list of routers that they recommend based on user experience. 

https://amzn.eu/d/esuOXUa

 

[dutchili]

VD din't work for me either since this issue exists

[Qcumber]

Another thing to try is to make sure you do not have incompatibility issues with open XR laters. 

https://github.com/fredemmott/OpenXR-API-Layers-GUI

Try disabling all layers first to see if that helps with link connection. 

[dutchili]

v76.1025 dropped on the headset, but no change.