cancel
Showing results for 
Search instead for 
Did you mean: 

Connecting vr to my pc via link cable

Ducktape6464
Honored Guest

Quest 2 

I've never had this problem before but my PC out of nowhere has stopped connecting using the link cable. I either get a loading screen followed by the meta logo just in blackness, no loading wheel or dots just the logo or i have the meta logo loading then i immediately get kicked back into my original quest screen. I have tries the following fixes that have not fixed the problem:

- updating PC

- updating drivers

- updating Quest

- updating/removing and reinstalling the meta quest application on my pc

- clearing full storage on pc

- turning off and on again (both pc and quest multiple times)

- getting a new cable

if anyone has any other ways to fix this that would be amazing im racking my brain and im going crazy please let me know!!

17 REPLIES 17

Badstar25
Expert Protege

Hundreds of us have had this problem since V76, they don't care at all!
I contacted support like many others, and they send you pre-prepared messages without even reading your emails.
It's like AI.
All the messages look the same, with the same structure...
Type: LINK in the search bar, you'll see.

I have the same issue. Please post a solution if you find one...

muonox
Protege

That USB 3.2 Gen 1 (5Gbps) port that worked for Badstar25 worked for me too.  Faster ports (Gen 2 10 Gbps or 20 Gbps) had problems.

Badstar25
Expert Protege

Hello Muonox,
So far, I've only had 9 positive responses to my solution.
Meta support has been a nightmare, they're so bad...
Here, I tested it with an INIU DI-401 cable that ends in USB-A. It also works, so the problem really lies with USB-C.
This INIU cable has the ability to charge via an external charger, so the drawback of my adapter solution is solved with it.
I'm increasingly doubtful about Meta's ability to fix this problem. We'll see, but we'll have to be patient 😉

I wonder what % of users had the problem?  I think very few would get so far as to find these forum posts, they get buried quick.  I'd got the connection issues with the 10 Gbps port only after I tested the 20 Gbps port again to submit the bug report for it yesterday.  Hopefully with the bug reports and the included log files they can fix it.  In the meantime I don't dare change anything now that it's working on the slower port 🙄

witorwitor
Explorer

We didn't buy expensive genuine link cables, which worked fine until the update, to now jump through hoops and buy more cables/adaptors. 

PC app got updated to v77. The headset is still on v76. I cannot connect at all. I just get stuck at the aurora borealis screen with 3 dots. I use quest 3 just as a PCVR headset so the latest update made my device useless...

witorwitor
Explorer

By the way, I use the UCB C port on my RTX2080ti graphics card, as this is the only USB C port I have. It worked so far. I also updated the GPU and USB drivers. No change, still cannot connect.

You're absolutely right, Witorwitor, but since I was on vacation, I had time to search for over 20 hours. I communicated for several days with Meta's "support." I sent files twice with the times of my tests. I spent an insane amount of time on all of this, and they didn't respond logically.
I got mind-boggling responses, like, "You need to update your graphics card," even though I had updated to 576.28 the day before. I uninstalled everything with DDU and did a fresh install. I reviewed a file for them to compare, and then they told me it was my hard drives that weren't installed properly. I checked, sent them the screenshots, and then they told me to restart my computer, reconnect the headset, and so on.
They played with me like that for several...
And then they closed my file, and I received the satisfaction survey...
I live in Europe, in Belgium, with French-language support. I hope you have better luck 😉
I bought the cable because I do Simracing on Iracing, and I'm in the middle of a championship. This simulation requires a subscription. I couldn't afford to wait for Meta to find a solution one day, because they're pretty slow on that front. Before with V72 I had no problems, so saying that it is my PC is an aberration because I checked the Windows update history as well as the driver dates and apart from V76, nothing had been done on 04/24/2025 when I started having my problems.