Quest 3/ Air Link stopped working/ No connection to PC/ PC found but Start Button is greyed out...

I am in the exact same situation, now I'm starting to think that there is a bug in the recent update v65.

I've posted the same issue here: https://communityforums.atmeta.com/t5/Get-Help/Oculus-Quest-3-AirLink-needs-to-be-paired-again-when-the-headset/td-p/1198340

I've solved partially disabling Link and enabling it back from the Settings. Then I can Pair the device with the pc again.

Problems with AirLink can sometimes be solved by disabling the Quest functions completely. If your PC is peeling with a helmet and works via usb then
In the Quest headset:
Go to the Settings menu.Find the settings tab "Air Link", use it there "Air Link" is disabled/enabled and a window should open with the PC pairing code with the headset. The "Air Link" will not work from the main menu.

Same issue. Have to pair the headset after every reboot. I sent the headset for replacement and it worked fine until using the link cable, now the kernel has been recompiled to accept the link cable but omitted the airlink protocols and reinstalling the firmware is impossible since they use a communist boot loader.

I spent a good three hours trying to tell support there was a bug for the past two weeks, with them typing like a lethargic turtle, 120 seconds for one sentence, geezus.

Not a solution - Marking for visibility

Known Issue

Hello everyone!

I have noticed that a considerable amount of users are currently facing a problem where the Air link button appears grayed out, necessitating the users to re-pair their headsets after each use. I have taken the initiative to inform our internal teams regarding this matter. I would like to express my gratitude to all those who have already shared bug reports and shared their experiences in this discussion.

We would greatly appreciate if everyone could please provide the following information:

1. What's the full version number of your headset? (65.0.0.####### or likewise)
   • Quick Settings > System > Software Update
2. What's the full version number of your PC app? (65.0.0.####### or likewise)
   • General > Scroll down to the bottom of the page.
3. Is your PC app on PTC?
4. Are you enrolled in Quest PTC?
5. Any potential workarounds?
6. Which headset is everyone using? Is this only happening with the Quest 3 currently, or is anyone experiencing the same thing on their Quest 2 and Pro

I'll do my best to keep you all updated as soon as I find out anymore information!

I've tried factory resetting my quest 2 and reinstalling the oculus app on my PC before trying to reconnect. Nothing has been working. Even the link cable has been extremely buggy. It was working fine until around 5 or 6 days ago. No basic troubleshooting has helped it any.

Hello,
Same problem with my Quest2 for 2 days.

I have installed No man's sky 2 days ago.

Meta Quest Link 65.0.0.499.343

Headset Version : 65.0.0.547.341.596252018

Same for me, everything was working great and now not working. I did notice that the QUEST app is at 66.0.0.288.370 and that my QUEST 3 version is at 65.0.0.546.341.596219384 and my QUEST 3 runtime version is at 65.0.0.548.344.596219384.

I am seriously annoyed as i want to play a game and can't. 

Having the same problem. It started maybe 4 days ago. I can get connected by turning off and on in the quest link in the settings menu but I have to pair every time. Also Steam VR home and games appear to launch on my PC but even if they're running they don't appear to launch on the headset anymore.

Headset version: 65.0.0.548.344.596219384

Desktop app version:  65.0.0.499.343

I have the same problem.. and it started after that latest update on Quest 2, I dont have a 3, and it does the same thing on Quest 2 as some have reported on 3, I have done everything even reinstalled windows 11 pro, still didnt fix the issue. the only thing I havent done yet is factory reset my headset. which I really dont want to do. this is an issue with Quest. they need to fix this.. it always worked till last update and now it doesnt work. I have to re-Pair my pc with my headset everytime I want to use PCVR, good news is the Steam Link works without issue.. maybe Quest can learn a thing or two from Steam Developers.. I am beyond PO, with this issue..

Same thing for the last coupe of days via airlink on my Q2.

can get it to work again temporarily (until restarting the quest 2) by disabling and re enabling airlink in settings and re-pairing.

Debug log looks fine, then as soon as my Quest 2 starts up again it repeats the below over and over:

11/06 22:16:38.891 {INFO} [xrstreaming_v2] Waiting for 0 connection instances to terminate
11/06 22:16:38.891 {DEBUG} [xrstreaming_v2] Checking running connection - 0 remaining references
11/06 22:16:38.891 {INFO} [xrstreaming_v2] All connection references released in 0.000 seconds.
11/06 22:16:38.891 {INFO} [xrstreaming_v2] oculus_xrs_apk_connection_release_duration release_duration: 0.000004s
11/06 22:16:38.891 {INFO} [xrstreaming_v2] All connection instances terminated
11/06 22:16:38.891 {INFO} [xrstreaming_v2] Creating channel to tlsserver,any-port
11/06 22:16:39.856 {INFO} [DML:HMDNormal] HMD Reporting state change: {'State':'NotDetected','IsDetected':0,'IsReady':0,'Mode':'Unknown','IsWirelessReady':0,'IsRebooting':1,'IsFirmwareOutOfDate':0}
11/06 22:16:40.885 {INFO} [xrstreaming_v2] XrspSocketTransport accepted TCP connection for TCP retransmit storm workaround via socket 6100 from DELETED
11/06 22:16:40.885 {DEBUG} [xrstreaming_v2] Setting TCP Keepalive
11/06 22:16:40.885 {DEBUG} [xrstreaming_v2] Set receive buffer for TCP retransmit storm workaround to 32768 kB
11/06 22:16:40.885 {DEBUG} [xrstreaming_v2] Set send buffer for TCP retransmit storm workaround to 32768 kB
11/06 22:16:40.887 {INFO} [xrstreaming_v2] XrspSocketTransport accepted TCP connection for regular connection via socket 6064 from DELETED
11/06 22:16:40.887 {DEBUG} [xrstreaming_v2] Setting TCP Keepalive
11/06 22:16:40.887 {DEBUG} [xrstreaming_v2] Set receive buffer for regular connection to 32768 kB
11/06 22:16:40.887 {DEBUG} [xrstreaming_v2] Set send buffer for regular connection to 32768 kB
11/06 22:16:40.887 {DEBUG} [xrstreaming_v2] Constructing socket flow for socket 6064 to DELETED
11/06 22:16:40.887 {DEBUG} [xrstreaming_v2] Setup QoS for socket 6064 with traffic 4
11/06 22:16:40.887 {DEBUG} [xrstreaming_v2] Constructing socket flow for socket 6100 to DELETED
11/06 22:16:40.888 {DEBUG} [xrstreaming_v2] Setup QoS for socket 6100 with traffic 4
11/06 22:16:40.888 {!ERROR!} [xrstreaming_v2] socket_wr_fd was closed, aborting
11/06 22:16:40.888 {!ERROR!} [Kernel:Error] OVR Error:
Code: -6102 -- ovrError_XRStreamingUSBIssue
Description: socket_wr_fd was closed, aborting
OVRTime: 8212.238191
Time: 2024-06-11 22:16:40 [888:650:0]

11/06 22:16:40.888 {!ERROR!} [xrstreaming_v2] QOSRemoveSocketFromFlow(handle=0x00000000000015e0, socket=6064, flow=1235): An operation was attempted on something that is not a socket. (10038)
11/06 22:16:40.888 {!ERROR!} [Kernel:Error] OVR Error:
Code: -6102 -- ovrError_XRStreamingUSBIssue
Description: QOSRemoveSocketFromFlow(handle=0x00000000000015e0, socket=6064, flow=1235): An operation was attempted on something that is not a socket. (10038)
OVRTime: 8212.238263
Time: 2024-06-11 22:16:40 [888:721:400]

11/06 22:16:40.888 {!ERROR!} [xrstreaming_v2] QOSRemoveSocketFromFlow(handle=0x00000000000015e0, socket=6100, flow=1236): An operation was attempted on something that is not a socket. (10038)
11/06 22:16:40.888 {!ERROR!} [Kernel:Error] OVR Error:
Code: -6102 -- ovrError_XRStreamingUSBIssue
Description: QOSRemoveSocketFromFlow(handle=0x00000000000015e0, socket=6100, flow=1236): An operation was attempted on something that is not a socket. (10038)
OVRTime: 8212.238281
Time: 2024-06-11 22:16:40 [888:739:100]

11/06 22:16:40.888 {WARNING} [xrstreaming_v2] Failed to construct channel for tlsserver,any-port