Skip to main content
Participant
January 18, 2026
Solved

Horizon link not working

  • January 18, 2026
  • 318 replies
  • 26468 views

My Q3 was linking fine to my PC this afternoon, then literally an hour or two later, will not link.

I'm using a usb 3.0 cable, it is in a USB 3 port, power management of USB port is set correctly.

I get a notification saying 'Meta Quest Link isn't working correctly. Click here to check our support article'.

There is no support article.

I have restarted the headset and PC, repaired the Horizon app, logged out and back into the Horizon app, restarted the OVR service and I still can't get it to work.

Anyone else having or had similar issues recently? 

Horizon software 83.0.0.333.349

Headset V83.1034 build 5156385.14650.520

Grateful for any ideas.

Best answer by helijoe

SOLUTION
Thanks to all those who mentioned this link and the autor of it, you made my day 😁
Horizon link not working | Meta Community Forums - 1362707

318 replies

New Participant
January 18, 2026

See LitBurner link to solve this issue until Meta sort it out:

https://communityforums.atmeta.com/users/LitBurner/1807360

New Participant
January 18, 2026

I'm having the same problem.

New Participant
January 18, 2026

Same issue as OP. Across multiple headsets (Quest 2 and Quest 3), none can connect as of this morning (EST) via wired USB 3 link. Have all been working flawlessly day-in and day-out for months. 

For developers working on building experiences for this Meta Quest ecosystem, the auto-update-that-bricks-all-devices is unbearable. I'm just trying to update a GUI in Unity and literally can't do anything because Link is a POS.

Meta... please, do better. 

Maybe spend less time firing your VR developers and more time on keeping the underlying technologies at a basic working level. 

Choleni
Honored Contributor
January 18, 2026

SEND BUG REPORTS!  COMPLAINING IN THE FORUM IS NOT ENOUGH!

Report a bug on Meta Quest

Participant
January 18, 2026

Exactly, we all have nothing better to do.

The best part is, when bug reports are sent, Meta usually starts a completely nonsensical and useless workaround. That's been my experience.

Choleni
Honored Contributor
January 18, 2026

At least they get aware that something is wrong, which not happens if everyone just posted "same here"

Participant
January 18, 2026

It worked this afternoon, but a few hours later it stopped working. Always the same problem. 

Could this be an authentication or connection problem with the metaservers?

AirLink isn't working either. In my opinion, there's a problem with the internet connection for authentication.

New Participant
January 18, 2026

Тоже самое произошло. Вчера работало. пол дня работало. Потом внезапно отключилось и все

New Participant
January 18, 2026

Same here on my quest 2. Been trying to troubleshoot for 2 hours to no avail.

New Participant
January 18, 2026

I am experiencing the exact same issue on my Meta Quest 3. Ever since the update to version 83.0.0.333.349, I am stuck on the infinite loading screen (aka. spinning dots) in the headset.

What’s frustrating is that the Meta Horizon Link app on my PC shows the status as 'Active' with a green icon, but the link interface never actually loads in the headset. My setup was working perfectly until this specific update.

It seems like this version has a fundamental bug in how it handles the video handshake or encoding. Hopefully, a hotfix is released soon as this has made PCVR unusable.

Participant
January 18, 2026
New Participant
January 18, 2026

Thank you so much for sharing this! I can confirm this workaround works on my Q3 with an RTX 4070 Ti running version 83.0.0.333.349.

However, while this 'no internet' trick gets me past the infinite loading screen, it is a major inconvenience. Meta needs to prioritize a real fix for this. We shouldn't have to go offline to use a wired VR setup.

New Participant
January 18, 2026

Same. Happened to me immediately after I rebooted and a Win11 update installed. Quest 3 here. What OS is everyone using? Support told me they have a number of reports about this, they're working on a fix