Oculus Quest 2 Failing to connect via link

richard.szydelko

Hi,

My Quest 2 refuses to connect to my PC with the following errors

Hardware Notification

Oculus isn't working correctly. Click here to check our support article.

And sometimes, 'We can't find your headset. Please connect your headset'.

In the oculus software

  

 Quest 2 and Touch has a green tick and shows as active.

 The usb test shows a green tick with Compatible connection and a bandwidth of 2.3 Gbps on US3.

 

 In the quest

 It shows the usual message 'Enable Oculus Link'

 When I click this, the screen goes black and the three white dots appear for about 5 seconds, then goes back to normal screen without connecting.

 

 Link was working correctly since Christmas and has recently stopped, seems to coincide with the latest firmware update.

 

 Seems like the problem is at the Headset end of things and not the pc?

 

 GPU is a nvidia GTX 1650 super and is on the compatible list, switched off In Game overlay, and has the latest drivers.

 Processor is a Ryzen 5 3600 6 core.

 Windows is on the latest update.

 Have done a complete update of the Oculus Link software, and not allowing Public beta tests.

 Oculus software version is 25.0.0.57.658 

 Oculus headset firmware is 25.0.0.72.658.270434822

 

 As I mainly use the Oculus to play PC games (mainly race sims) and Virtual desktop doesnt quite cut it (but works reasonably well). I would appreciate any help with this issue.

 

 I am beginning to suspect a literal Hardware problem.

 

 Any help/suggestions would be greatly appreciated. Let me know if you need any further information.

 

 Cheers

 Richard

MrNaffNaff

Hello, I have exactly the same issue as described above. Using the official Oculus Link cable.
Stopped working overnight after the headset updated to v25.

richard.szydelko

Thanks. Let me know if you solve it, I've been trying everything for the last 3 days. Very frustrating.

Chappie8824

This is a definitely a Link cable issue with Build 25. A lot of people are complaining about Build 25 with Link. I was able to rollback to Build 23 because I had a hard drive image of the Oculus folder. Build 23 works fine with Link.

BadnessDio

I've got the Quest and the same thing is happening to me also. It just started today, funny thing is it worked last night.

EDIT: I Factory reset the Quest, then I uninstalled/re-installed the Quest Software and the Link works.

GENXVR

I'm just glad I'm not the only one. I was gifted a Quest 2 this week and I haven't been able to set up the link so far. Hopefully they will fix this so I can get back to playing my Steam games.

wilza7

got almost the same hardware spec for pc.  anker cable instead of official oculus one.  running v25 on the quest, though pc software was v23 last time i looked.  expected the pc software to go to v25 as well.  no issues thankfully.  i'd suggest uninstall and reinstall the oculus software.  i had to do that a while ago to solve a missing oculus sound devices issue.  the oculus headphones and microphone didn't show up.  

MrNaffNaff

thanks wilza7, already tried that and it didn't work.
Also tried:
- Using another 10 gbps third party usb C to usb C cable
- Resetting everything on Oculus Debug Tool to the default settings
- Resetting all developer options on the headset to default
- Turning laptop and Quest 2 on and off a gazillion times

Chappie8824

Yea i tried to remove and re-install software and that did not work. Went back to a imaged version of Build 23.

Resistiv

I am also having this issue and have tried everything above, and the fix found in this post: https://forums.oculusvr.com/community/discussion/42165/
I'm having the exact problem described, and I'm noticing similar behaviour coinciding with updates to the UserModePowerService service within my Windows event logs, which is done by the OVRServer_x64.exe program.
Anyone been able to fix this on Build 25?

richard.szydelko

Thanks for all the answers. Seems I'm not alone then. Seems we'll have to wait for a fix from Oculus?
I have also put in a service support ticket. I will post the answer here if I get a response.

wilza7

laptop and quest 2 seems a common combo for people with problems.  just something i've noted from various posts on here.  no new bright ideas for fixing it though

BooSparx1

Same problem with me. Just got Quest 2 today . . setup stand-alone NO PROBLEM ! Download Quest Link on PC (Windows 10 - i-9 intel / 32 Gigs of ram / AMD RX580 w/ 8 gigs of VRam) using the Oculus cable type-C connector to the PC recognized cable - headset and looked like all was well . . but at enable screen . . keeps on kicking me back to Deny / Allow data connection and then to Link App quit / more info.

Zaire3928

Same issue here, it's working fine all these days, stopped working over night, just checked,  mine is on v25 now....please let us know if there is any known fix...

Zaire3928

Chappie8824 said:

This is a definitely a Link cable issue with Build 25. A lot of people are complaining about Build 25 with Link. I was able to rollback to Build 23 because I had a hard drive image of the Oculus folder. Build 23 works fine with Link.

Is there any instruction on how to rollback? thanks!

Mourbius

we need a copy of he hard drive image of the v23 any way you could do that so we could download, maybe you tube
we all need to back to v23 until they fix this

Abigor79

Similar problem here... but only just with one game: DCS Wolrd. It was working fine with v23, but since the v25 Update, the link goes down after a few minutes of play. Anyone can explain how to rollback to v23 and avoid at all future updates? I only use the Quest 2 to play this simulator...

Paul_LondonLad

I know I've posted this reply into several other threads, but I'm hoping that this will give a better noitifcation (and with log) to the QA/developers.

====

I recommend using the 'Oculus Log Gather' to report issues encountered with the device.

I only found about this included tool a few days ago while I have encountered issues. I am am going to assume that this will reach the relevant QA & Development teams for investigation and resolution far faster than our posts on here. 

You'll find the relevant here (your installation path may vary if not the default install)

Located: "C:\Program Files\Oculus\Support\oculus-diagnostics\OculusLogGatherer.exe"

Once run, set the Collection date period, and check the full logs and auto submit check-boxes, and finally complete the field explaining your issue.

I'm hoping that the more reports that are received in this manner is noticed and any priorities are changed to resolve any identified issues.

ronbok

Same issue here, can't seem to stay longer than a few minutes connected to oculus link. Started a few days ago. Can we get rollback to v23?

richard.szydelko

No response so far from oculus. Disappointing customer service.