Meta Quest Link Update: Link Launch Issue Resolved

Making the changes below as suggested by TomCgcmfc allowed me to fly for 20 minutes without Link crashing.  Link has been crashing for weeks now after 5-10 minutes.  This is the first try and I'll update regarding future flights.  Here are the changes I made: Oculus Debug Tool (ODT) all defaults/zeroes except link settings distortion low, dynamic bitrate encoding enabled, and 750mbps max dynamic bitrate.  Update: Since the initial successful flight, I've had 2 more without Link failing.  However, I did find that switching from 3d to 2d in the middle of the flight caused Link to fail.  TomCgcmfc: Thank you for at least giving me a way to fly my Meta Quest 2 in 3d mode.  At least until they correct whatever they did to create this Link problem. Thanks again. 

I have found a potential "fix" to the issue. An actual fix needs to be implemented by Meta. When the issue happens, if I click the headset power button on/off (quick, not holding it) - VR Link stream resumes inside VR headset... 

As of 28/03/2026, this is still broken. Got an infinite loading screen when trying to start quest link in menu.  
Tried
Completely wiping meta and oculus of pc and reinstall
Start with no internet
Block Oculas via windows firewall

Oculas debug comes back with 

//

Error INITIALIZATION_FAILED

Logging event pc_link_error_initialization_failed

XrsTransportApiClient: Failed to initialize transport api client.

Link over DISCO: initializing DiscoHighwindDapHostRipcClient attempt: 302.   # Its been trying for a while #

28/03 20:42:29.545 {!ERROR!} [Kernel:Error] OVR Error:

Code: -6100 -- ovrError_XRStreamingGeneralIssue

Description: XrsTransportApiClient: Failed to initialize transport api client.

OVRTime: 4997.498389

Time: 2026-03-28 20:42:29 [546:86:700]

initializing transport api client (attempt 302)

Searching for: highwind_dap_server. ignorePackageAndProcess: true

Server (highwind_dap_server) not found. Dumping all connections/servers:

//



Also log gather is broken, fails to auto-submit 
//
Error uploading bug report: System.AggregateException: One or more errors occurred. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel. at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context)
   at System.Net.Http.HttpClientHandler.GetRequestStreamCallback(IAsyncResult ar)
   --- End of inner exception stack trace ---

//

Not happy thats its been a week without getting this thing to work and play with friends.

Spambot. Reported.

Are we all still on the old drivers or have we been able to update with new meta update?

24/04 17:46:07.320 {!ERROR!} [xrstreaming] [V2] Failed to set output surface: -1010

24/04 17:46:07.320 {!ERROR!} [Kernel:Error] OVR Error:

Code: -6100 -- ovrError_XRStreamingGeneralIssue

Description: Failed to set output surface: -1010

OVRTime: 1341.378147

Time: 2026-04-24 17:46:07 [320:403:300]

24/04 17:46:07.320 {!ERROR!} [RemoteHeadset] [V2] failed to create surface

24/04 17:46:07.320 {!ERROR!} [Kernel:Error] OVR Error:

Code: -6101 -- ovrError_XRStreamingPluginIssue

Description: failed to create surface

OVRTime: 1341.378180

Time: 2026-04-24 17:46:07 [320:436:300]

24/04 17:46:07.320 {!ERROR!} [Kernel:Error] OVR Error:

Code: -3000 -- ovrError_Initialize

Description: Failed to create direct display surface.

OVRTime: 1341.378188

Time: 2026-04-24 17:46:07 [320:443:900]

24/04 17:46:07.321 {!ERROR!} [DisplayManager] [DisplayManager] Failed to set power profile.

ovrError_XRStreamingGeneralIssue (-6100)

InitClient FAILED

highwind_dap_server not found

Dear  octagonal.elf​  In the space of 10 minutes you have posted 4 comments on the same issue. Please put your thoughts into one comment. Four will not make a difference to your issue and multiple posts in quick succession could be flagged as spam and can result in a ban. There are many threads with solutions to this. Unfortunately not every issue is exactly the same. You should check through the forum. You might find a solution. If not,, contact Meta Support. There are no Meta employees here here, only headset users. I understand your frustration but posting multiple one liners without detailing anything of the process you tried doesn't help. Saying 'it isn't working" is not much good to anyone who wants to help. 

I started having a serious PC Link issue a few days ago that appears very similar to the launch issue described in this thread. When I connect my Quest to my PC by USB and launch PC Link, the headset displays the animated Meta logo indefinitely instead of loading Dash. There is sometimes a split-second black flicker around the point where Dash would normally appear, but it never finishes loading. The headset works normally on its own. After a 60-second hard reset, the home environment, controllers, tracking, and menus all work correctly. The USB connection is also detected normally. The problem begins as soon as I launch PC Link. Disconnecting the cable produces the expected "PC Disconnected" message, although during some failed attempts the looping Meta logo has remained visible over the Quest home environment afterward. I’ve restarted both the PC and headset, performed the 60-second hard reset, reconnected the USB cable, and tested Link immediately after clean restarts. I also tested restarting the relevant Meta PC processes while the failure was occurring. None of this resolved the problem. The PC logs appear to show the failure. Around the affected Link launches, there are repeated messages that highwind_dap_server cannot be found, followed by XrsTransportApiClient initialization failures, DiscoHighwindDapHostRipcClient InitClient() failures, and repeated initialization attempts. PC Link was working normally for me until just a few days ago. I have screenshots of these errors and the complete Oculus logs available if someone from Meta would like them. I’m happy to provide any other diagnostics that would help investigate this.