Skip to main content
Participant
April 30, 2025

Link consistently fails to connect over USB and Air

  • April 30, 2025
  • 7 replies
  • 1140 views

Things were working this morning -- after a lot of restarts, to be fair -- but they were working. When I returned from lunch, I woke up my computer and woke up my headset, which already had the USB cable connected. It was stuck at the "White Meta Logo" screen.

I unplugged the cable, restarted the Quest 3, and force quit / relaunched Link (because clicking Exit in the System Tray doesn't work).

When I connected the cable this time, the Quest tried to open Link, then quit with no explanation and returned me to the home screen.

When I checked the Link settings, somehow the Developer Mode was turned off. Trying to turn it on again did nothing: literally, I could not flick it back to "on".

I disconnected the Quest and restarted everything, including the computer.

I started Link. (it takes 2 minutes to start, which is new) I checked the Beta settings. Developer Mode was on. OK...

I connected the USB cable to my Quest. It loaded to the White Meta Logo screen and hung there. I had 3DOF but every once in a while the logo would get juddery, like the CPU was overloaded and it was having trouble rendering at 60fps.

I quit Link on the Quest and tried to connect via Air Link. Same result.

Checked Link on the computer again. Dev Mode was set to off again. And again it did not respond to button clicks.

This appears to be broken.

Happy to send logs or whatever you need to help diagnose.

Setup

  • Link on Windows 11: 76.0.0.452.315
  • Quest 3: 76.1024
  • USB-C connection or Air Link (same issue with both methods)

 

    7 replies

    New Participant
    May 1, 2025

    Hello,

    I had the same issue from update 76 onwards the connection with the device and computer via cable/link air is not working anymore, i had an older q2 that still had v68 and upgrade it to 74 which works well. The pc recognizes it and i can push builds to it. I tried also with 76.1023 both on quest and on meta link software which is now 77.0.0.469.329 but still broken. I hoped that 1024 fixed  the cable issue but unfortunatelly not, i see the issue is happening here as well. 

     

    Kind regards,

    Alexandru Buzdugan

    New Participant
    May 1, 2025

    The issue to me looks like the icon to allow the computer interaction in developer mode in quest is not working anymore properly in 76, it does appear from time to time twice in a row and even if i allow always from this computer it seems to not work. Also the ui is broken, there are now 3 buttons and the always allow one is broken you can half press it. So i think something happened regarding that permision and that is why the pc does not see the device and vice versa.

    MetaStoreHelp
    Community Manager
    May 1, 2025

    Hey there tedbrownxr ,

     

    We see you're having some issues with Quest Link and Air Link connectivity especially after the recent update and we'd like to thank you for putting out the issue here in such detail.

     

    For us to gather more details around this and provide you with any troubleshooting steps, we'd request you to send us a PM.

     

    Please remember, you must be signed into the community first to send us a private message.

    If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
    MetaStoreHelp
    Community Manager
    May 2, 2025

    Hey again tedbrownxr 

     

    We wonder if you still require assistance for this?

     

    Feel free to let us know.

    If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
    Participant
    May 2, 2025

    DM sent. Appreciated.

    New Participant
    May 2, 2025

    Same issue.
    USBView detiails.
    [bmAttributes] are of note...?

     

    MetaStoreHelp
    Community Manager
    May 2, 2025

    Hi @M991, we see you're having some issues with Quest Link and Air Link connectivity especially after the recent update.

     

    For us to gather more details around this and provide you with any troubleshooting steps, we'd request you to send us a PM.

     

    Please remember, you must be signed into the Community first to send us a private message.

     

    Hope to hear from you soon!
     


     

     

    If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!