Skip to main content
New Participant
July 31, 2026
Question

xrCreatePassthroughFB fails with -2 / Failure_NotInitialized over Link — all prerequisites verified

  • July 31, 2026
  • 0 replies
  • 35 views

Passthrough over Link fails to initialize on my setup. Posting in case

anyone has seen this or knows what else to check.

 

■ Environment

Headset : Meta Quest 3S

PC runtime : 1.205.0 (205.0.0.167.543), LIVE channel

Connection : Wired Link (USB 3.2, USB Test passed at 2 Gbps+);

Air Link same result

Unreal : 5.3 / 5.6 (Oculus fork) / 5.7, Meta XR Plugin v65–v205

Unity : 6000.0.66, official Meta sample

Unity-MRUtilityKitSample-205.0.0

 

■ Errors

Unreal:

LogOculusXRPassthrough: Error: xrCreatePassthroughFB failed, error : -2

(-2 = XR_ERROR_RUNTIME_FAILURE)

 

Unity:

Failed to initialize Insight Passthrough. Please ensure that all

prerequisites for running Passthrough over Link are met ...

Error Failure_NotInitialized

 

OVRPlugin.GetInsightPassthroughInitializationState()

-> Failure_NotInitialized

 

Same result regardless of engine, engine version, plugin version,

rendering path (D3D12 / Vulkan Mobile Preview), or connection method.

 

■ Already tried

- All Link app Developer tab toggles ON (Developer Runtime Features,

Passthrough over Link, Spatial Data, etc.)

- Registry values including PassthroughOverLink all set to 1

→ the .reg fix from the thread below does NOT apply, mine are

already 1

- Developer account signed in on both PC app and headset

- OpenXR Runtime set to Meta Horizon Link as active

- Editor restarted after toggling

- Checked the Link service log via OculusDebugTool: the service reads

PassthroughOverLink: uint32: 1 (0x1) correctly, but there is no line

anywhere recording a passthrough init attempt or failure

 

■ Related threads (both unresolved)

https://communityforums.atmeta.com/discussions/Questions_Discussions/failed-to-initialize-insight-passthrough/1367576

https://communityforums.atmeta.com/discussions/PairingConnection/passthrough-over-link-not-available/1357035

 

Has anyone hit this and found what the actual blocker is? Any pointers

on what else to check would be appreciated.