Skip to main content
Meta Employee
January 20, 2026
Question

Meta Quest Link Update: Link Launch Issue Resolved

Hi everyone,
We recently identified an issue with Meta Quest Link unable to launch which caused users to be stuck in the app launch loading screen. We’ve now released an update that should resolve this problem.
What’s changed:

  • The main issue is fixed, and you should be able to use Meta Quest Link as expected.
  • Please note: For now, you won’t be able to see your hands in Dash. However, raycasts are visible, and you should be able to interact with games and other content as usual.

Thank you for your patience while we worked on this fix! If you continue to experience any issues, please let us know in the comments.

154 replies

Up and Coming
January 23, 2026

Look how much RESOLVED it is:
This is a LOOP of messages , mostly ERRORS from the DebugTool CONSOLE. This is with the headset not even CONNECTED to the PC. After you connect the headset there are even MORE errors while you try you play, imagine the LOAD on the CPU having all those ERRORS and at the same time you are playing, maybe THOSE ERROR are the ROOT CAUSE of ALL THE STUTTERING and high bitrate problems, connections, etc?. YES OF COURSE THEY ARE, so FIX PLEASE FIX ALL THAT!, thanks.

23/01 09:15:10.227 {WARNING} [RuntimeIPCSystem [RUNTIMEIPC]] Init: BrokerMethods::Get().Init FAILED

23/01 09:15:10.227 {INFO} [RipcClientMgr [RUNTIMEIPC]] RipcClientMgr::Shutdown

23/01 09:15:10.227 {!ERROR!} [xrstreaming] [V3] Link over DISCO: DiscoHighwindDapHostRipcClient InitClient() failed!

23/01 09:15:10.227 {!ERROR!} [Kernel:Error] OVR Error:

Code: -6100 -- ovrError_XRStreamingGeneralIssue

Description: Link over DISCO: DiscoHighwindDapHostRipcClient InitClient() failed!

OVRTime: 2344.345272

Time: 2026-01-23 09:15:10 [227:729:300]

 

23/01 09:15:10.227 {DEBUG} [xrstreaming] [V3] TypesafeLogger: Error INITIALIZATION_FAILED

23/01 09:15:10.227 {DEBUG} [xrstreaming] [V3] TypesafeLogger: Logging event pc_link_error_initialization_failed

23/01 09:15:10.227 {INFO} [xrstreaming] [V3] Link over DISCO: initializing DiscoHighwindDapHostRipcClient attempt: 7.

23/01 09:15:10.227 {INFO} [RuntimeIPCSystem [RUNTIMEIPC]] RuntimeIPCSystem: Init called: Version: 81, Platform: Windows, Build Date: 1, Build Time: 1, BuildMode: shared

23/01 09:15:10.227 {INFO} [IPCTelemetryHelper [RUNTIMEIPC]] Initialize: ENABLE_IPC_TELEMETRY not defined

23/01 09:15:11.109 {DEBUG} [RiftDML:HMDManager] No HMD enumerating

REFLECT [RUNTIMEIPC] WARN@ buck-out\v2\gen\fbsource\arvr\libraries\disco\highwind\ripc\__highwind_dap_host_ripc_generated_cpp__\3ffef6483574762d\buck-headers\disco/highwind/ripc/generated/HighwindDapHostRipcClient.h(44): InitClient: InitIPCApi failed

23/01 09:15:11.109 {INFO} [DML:HMDNormal] HMD Reporting state change: {'State':'NotDetected','IsDetected':0,'IsReady':0,'Mode':'Unknown','IsWirelessReady':0,'IsRebooting':1,'IsFirmwareOutOfDate':0}

23/01 09:15:11.109 {DEBUG} [RiftDML:HMDManager] Waiting for HMD to enumerate...

23/01 09:15:12.252 {WARNING} [RuntimeIPCSystem [RUNTIMEIPC]] Init: BrokerMethods::Get().Init FAILED

23/01 09:15:12.252 {INFO} [RipcClientMgr [RUNTIMEIPC]] RipcClientMgr::Shutdown

23/01 09:15:12.252 {!ERROR!} [xrstreaming] [V3] Link over DISCO: DiscoHighwindDapHostRipcClient InitClient() failed!

23/01 09:15:12.252 {!ERROR!} [Kernel:Error] OVR Error:

Up and Coming
January 23, 2026

My recommendation, use STEAM LINK until all this META stuff get fixed, Steam Link works perfectly, you can even UNINSTALL all Meta Horizon Stuff from your PC, and will work anyways.

Participant
January 26, 2026

Some of us dont have the set-up to run wirelessly, we need a solution from meta that fixes the link cable issues with their own software.

Participant
January 23, 2026

Ok, but how do i access the update?  

 

Participant
January 23, 2026

This is extremely aggravating.  I've just removed KB5074109, and I still cannot link.  Ive done everything I've looked up, and nothing works still.  

New Participant
January 25, 2026

I cannot understand what is going on. Since this cluster F*#" of an update I've gone from being unable to play. To having a good session to having choppy sessions and now totally unplayable. On PCVR. And in-between sessions not changing a single thing. And yet. I turn on virtual desktop and it just works!  I prefer the link cable as to me it seems sharper and smoother when working. But given the totally unreliable experience through no fault of my own I'm going to have to ditch it until you can provide a worthy service to your customers. 

Up and Coming
January 25, 2026

Try STEAM LINK, it's better than Virtual Desktop. (both are wireless, but you could connect the USB cable to keep the headset charging)

New Participant
January 25, 2026

I teach a  class in VR and all my students could not connect this week with AirLink or Link. It was a nightmare. I rebooted everything, checked Link was up to date. I managed to get it running sometimes, but the screen was black on the quest.  Tried multiple days nothing. Even unistalled the Microsoft security patch, still no joy. PLEASE PLEASE fix this ASAP.

New Participant
January 25, 2026

I just opened my system for the first time in 5 days, I didn't want the aggravation.  Upon opening, Windows 11 did a new update and the Oculus also ran an update.  I ran 2 full races in iracing without issue with my PC Link cable.  There was some jitters when I first opened MetaLink but all ran good.  My FPS was at 120 99% of the time with some drop to 60 which is irregular for me.  I was running at 200 clean before all this bs.  There are still some glitches with the headset with the home screen and lobby jumping around but I got through that.  Hoping for further testing and fixes from Meta asap!

Participant
January 26, 2026

So I got a new gpu yesterday, used virtual desktop for most of the night.  Decided today to try meta link because I forgot last night about new gpu.  Plugged it in worked fine for all about an hour.  Black screen all day today.  ðŸ¥²ðŸ˜¤

New Participant
January 27, 2026

So how does one go about getting this update?  I'm on 83.0.0.333.349.  Is this the new one or old one?  I've had this headset for a week and haven't been able to use it once on my PC because it won't connect.  Not feeling real good about my purchase choice here...

New Participant
January 29, 2026

I've had two stable days in a row now. With frames back to where they were...am I just lucky or are others seeing the same? Id hate to become complacent but if this has been fixed in the background, well done Meta.