(I am an electrical engineer and long-time developer)
I isolated two small problems with the link aspect of the Meta Quest Link desktop app software. No guarantee that they will accept my fixes but I did submit the code to Failbook (Meta). Knowing them, … they will probably sit on it for seven months 
I have all sorts of problems whit link cable now, not sure if it’s the oculus software or usb port problem (bought a new cable but same problem)
So now I’m using airlink and it’s working really good, but i have a dedicated wifi 6 router, so not a solution for everyone. Virtual desktop is also an option, but for me airlink gives me a better picture.
Digging around a little more I started checking events in the windows event viewer. Right when I connected (and then was immediately disconnected from) the link app, I see this:
Process C:\Program Files\Oculus\Support\oculus-runtime\OVRServer_x64.exe (process ID:17864) reset policy scheme from {8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c} to {381b4222-f694-41f0-9685-ff5bb260df2e}
Quick internet searching says this could be caused by power management settings??
I checked to see that in device manager I have unchecked the box that allows my pc to put usb devices to sleep. Also in my power management settings, I have the usb settings set to never sleep…
But maybe we are on to something here with the link cable connectivity issues? Anybody have thoughts or areas where I can dig deeper? Feel like this is my mission for the day… I’d really like to use msfs in VR again 
Watching this thread with anticipation as I keep having problems. Just find a new workaround and the next time it doesn’t work.
This is so so annoying and I’m seriously thinking of getting a WIFI 6E Router and going down the road of Virtual Desktop!
Can in all honesty say Meta won’t be getting another penny off me when I upgrade from a Quest 2. They are not the only VR Headsets out there!
I completely agree. This is ridiculous. And it’s not the first time one of their updates has messed up PCVR. Scouring the interwebs shows countless people experiencing link connectivity issues after the 76 update. Not just with MSFS. Something either in the headset firmware update and/or the Link App update messed something up. I have spent the last two days playing software/hardware tester and I’m not real happy about it. I have been a VR flightsimmer for four or five years and this is the most frustrated I have been.
Well I have had enough, I too am so frustrated that I have just ordered myself a WIFI 6E router off Amazon as no other shops have them in stock where I live, so as of tomorrow I’ll be ditching the Link Cable and using Virtual Desktop instead.
Just can’t be dealing with Meta Link Software anymore, and as soon as I can afford it, I’ll be ditching my Quest 2 for something different lol
It just annoys the heck out of me that I’ve had to spend £109 today just because of META!
I agree. I am very close to ordering a router to plug in to my PC and just switching over to VD. Which has its own share of issues, I have read… but it has to be better than this garbage.
Have you all tried my fix (post 27 here)? It has worked for everyone who ties it except for one. I am using it and it hasn’t failed once. I played for 3 hours the other day and this morning spend a couple hours dialing in some graphic settings requiring multiple pc restarts. Link app opens easily each time and connected the q3 to the pc every time. If you haven’t yet tried it you might want to give it a try.
Yes tried it and it worked for a while. Seems sometimes the Automatic Delayed Start doesn’t work. When I reboot PC it will sometimes load the Link app other times it won’t, seems strange and I’ve checked the services.msc and it still set to Auto Delayed Start, so it’s a strange one.
Just been so fed up trying workarounds, and after a while I do get it working but now I’m fed up with META and I’m going to use VD instead, that way the next update they release shouldn’t affect me (fingers crossed) and if I find I can’t get on with VD or find I don’t get the performance or clarity I did with Link then I can always go back to using the cable lol.
But time is ticking and us Quest users can’t wait forever for a fix, so with that META have lost me and my cash, and hopefully a whole boat load of other people will feel the same and that’s a great way to hit them where it hurts!
I had tried that previously… with no luck. Here is what I just did -
Factory reset my headset.
Delayed start the oculus service (in services)
Made sure my power settings didn’t suspend USB
Unchecked the power management options for all USB device controllers and HID devices (that would allow it)
And…
I have a data point of exactly 1 try so far…
But… It worked. I have a work call now, but later tonight I’m going to test it out again to see if it sticks. Fingers crossed here…
But still, for the price you are paying for a Quest comparing to the alternatives..
And even the most expensive headsets out there seams to have all kind of problems according to the vr communities i follow.
Vr technology isn’t just there yet, and the userbase is still low, so i think we need a major breakthrough in production contra price, because as long you need a +4000 usd rig to run vr in high quality it’s never going to be mainstream, and therfore not a priority for developers.
You sort of brought me back to reality (and I had this thought an hour ago when I was going to smash my Q2 into very small components )
I (we) go through fits of rage followed by days and months of pure amazing enjoyment with VR. So I guess this is just one of those times when we have to fight it a bit to get it to work.
Now… I got it to connect and stay connected on the first try after jumping through a bunch of hoops. And it may fail next time I try… but…
This is what we go through as VR users Keep the faith, folks! Eventually, maybe there will be enough of us to make developers and hardware manufacturers treat us like actual customers instead of third-rate, oddball users.
That’s true @BanKhokklan, will manage for now lol however I just got it working, only lasted 15mins though so very annoyed.
Too true as well, but for tonight I give up. If I can’t even do a 30min flight then I’m going to have to wait till I get my Router tomorrow and then the fun begins 
Trying to set it all up and get it looking as good as with Link, and it’ll be just my luck META release a fix tomorrow just when I get VD working (if)
The big problem here is once you use VR and get it to where you are happy with it, it becomes a massive addiction! There’s no going back at any COST So Guess I’m just going to have to start saving every penny lol, no more buying any new Aircraft, till that one I really really neeeed comes out tomorrow haha
As the saying goes tomorrow will be a better day 
I’m with ya there man. I will NEVER buy another Meta product. After all of us (and there are a lot of us) having the exact same ■■■■ problem they won’t even admit there is a problem. Their support feeds us with the same useless bs which most of us know won’t work. And they want to lead the world to AI but their “engineers” can’t fix a vr app they built? Let’s face it pcvr is not important to them but they support it to squeeze a bit more revenue for the Meta Kingdom. Freakin rubbish!
Reading these comments, … so f#$%#@! true! (and I am an engineer) Meta has outsourced so much to AI that picking a headset to use these days has come down to a choice of the “least messed up.” 
Slightly off topic here but just wanted to let you all know, WIFI 6E Router arrived about 2 hours ago. Easy to set up, just did a quick flight in FS24 using Virtual Desktop for the first time and I’m blown away by how good it is! FPS locked to 36 via ASW - no God Mode available but that’s probably my lowly 4060ti GPU - but in all honesty I can say its just as good as with Link cable and smooth as butter!
The only thing I will say is that with Link the detail in the distance does seem to be better but a bit more tinkering with settings in OpenXR Toolkit should sort it. But everything else is sharp and crystal clear.
As I say, I haven’t had the time to tinker much with the settings as everything was at default, but I’m happy enough. And if Meta do release an update soon well I’m just going to stick with Virtual Desktop.
As good as VD is, I’ve never been able to make it look as clear overall as link cable, but it’s good to have something to fall back on each time these link issues (related to updates) happen.
That’s true. I thought I’d re-install Link software again last night to give it another try. It worked for about 5mins. Agreed VD doesn’t look as good in the distance as link does, but the colours do look much better in VD and it’s so much more stable. No having to use ODT, just click and go.
Still no update on Oculus link and this problem started on the 25th of April! It’s outrageous that META could leave it this long, when all you have to do is google the issue and see just how many users are suffering. All they care about is FB and the income they generate from that!
I’m on the PTC and did indeed have the issue a couple of days ago. It got to the point of not connecting AirLink at all. I reinstalled PC software and it’s jumped back to the retail version (which I’ve only just realised)
I’ve since had two headset-side updates and it seems to now be resolved.
I’ll post back here shortly with the version numbers from the headset/PC.
EDIT: Yep, PC still as per thread title 76.0.0.452.315 (so, non-PTC)
Headset version is 77.1025 build 5080163.6010.340
Not sure if they personally used the two fixes I sent them but I can confirm that WheelieMonsta’s comments are correct. If you have a Quest 3 or Quest Pro, enable the Public Test Channel under the Beta tab in the Meta Quest Link desktop app. This will update your Meta Link software to version 77 and your in-headset firmware to 77.1025. Reboot your computer and your headset. Then go to the Meta Quest Link desktop app and switch off the Public Test Channel. This will revert your Meta Link desktop app back to 76.0.0.452.315 but leave your in-headset firmware at 77.1025 which seems to fix the problem. Tried both my Quest 3 and Quest Pro and the problem has not reappeared, … at least, … so far.