Skip to main content
New Participant
January 18, 2026
Question

Entering Link From Headset "Infinite Loading Screen"

  • January 18, 2026
  • 31 replies
  • 6575 views

Hi, I have been using Metta Quest  3 Link with my PC for a few days and everything has been fine.

Today, I opened Link from the headset and just got a totally black screen, so I exited and tried again. Ever since then, when trying to open link, the loading screen just displays, infinitely.

I can see the Quest "connected" in the Horizon app on the PC, and when the infinite loading screen is displaying, library apps seem to think the headset is connected.

Im brand new to Meta Quest, only had it a couple weeks, and as I say, only been using Link for less than  a week, so I'm probably doing something stupid, but its driving me crazy.

I have tried:

  • Restarting headset
  • Restarting PC
  • Reinstalling Meta Horizon app
  • Repairing Meta Horizon app
  • Repairing headset
  • Removing Temp files
  • Logging out/in of account
  • Restarting runtime service

31 replies

New Participant
August 6, 2026

Just had Link update and now have this same issue. Tried all the fixes also tried by the OP and still not working. I've also tried the turning off internet connection before trying to connect through Link and still no success. When I move my hands around, I can hear the noise you'd hear when Link is established and your cursor is moving over different icons, suggesting perhaps link is open but the visuals are stuck on the infinite load screen.

Anyone else had the same problem after the latest update and able to provide an up to date solution? 

Choleni
Honored Contributor
August 6, 2026
New Participant
September 5, 2026

what I did to fix this was, first I uninstalled meta link software, remove all oculus and meta link folders, in appdata, and mean everywhere you can find them,  program files, gotta go looking, then reinstall your Nvidia video drivers.  It should work again. 

steve40
Honored Contributor
September 5, 2026

Dude, this thread was about a completely different issue that was solved by a software update months ago.