Air Link stuck in infinite loading loop – OculusDash.exe keeps crashing (COM initialization failure)
When trying to connect horizon link with airlink, loading is keep going over and over, never end. First of all , i stated to observe task manager. and i found the OCULUS-DASH.exe process was keep shutting down, whenever start link to horizon. Here is the Oculus Dash Log 2026-01-19T17:24:28.866133 [I]: C:\Program Files\Meta Horizon\Support\oculus-dash\dash\bin\OculusDash.exe startup: 2026-01-19T17:24:28.867130 [W]: Invalid prop name: oculus.signalFenceInDX 2026-01-19T17:24:28.868127 [W]: Invalid prop name: oculus.signalFenceInDXEarly 2026-01-19T17:24:28.868127 [W]: Invalid prop name: debug.saveLogToMiniDump 2026-01-19T17:24:28.868127 [I]: CLAYLOG - Entering App::run 2026-01-19T17:24:28.868127 [I]: LOGFILE: C:/Users/PC/AppData/LocalLow/Oculus/Dash/log/Dash.log 2026-01-19T17:24:28.893061 [I]: App::run isVRMode m_windowShouldClose 0 2026-01-19T17:24:28.893061 [I]: OculusUtil::_init() 2026-01-19T17:24:29.478517 [I]: OculusUtil::_initHMD() 2026-01-19T17:24:29.478517 [I]: HMD: Oculus Quest2 (FW -11901.0) 2026-01-19T17:24:29.479522 [I]: HMD: (2816x1472) 2026-01-19T17:24:29.479522 [I]: RT : L(4160x2096) R(4160x2096) 2026-01-19T17:24:29.479522 [I]: OculusUtil::newControllerFactory() 2026-01-19T17:24:29.479522 [I]: Medium: Branch [systemux] Build [0] 2026-01-19T17:24:29.480517 [W]: Unable to find loader for Texture resource at path 'textures/test/checkerboard'. File may not exist. 2026-01-19T17:24:29.592752 [I]: Audio will play through VR device '헤드폰(Oculus Virtual Audio Device)'. 2026-01-19T17:24:29.706830 [I]: OAF Initialized 2026-01-19T17:24:29.709811 [I]: Dash Ready 2026-01-19T17:24:29.710318 [I]: RenderDeviceSystem::_onAddedToScene() 2026-01-19T17:24:29.714985 [I]: NVAPI initialized: driver version 57602 2026-01-19T17:24:29.714985 [I]: RenderDevice::RenderDevice() 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_KHR_device_group_creation (1) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_KHR_external_fence_capabilities (1) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_KHR_external_memory_capabilities (1) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_KHR_external_semaphore_capabilities (1) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_KHR_get_physical_device_properties2 (2) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_KHR_get_surface_capabilities2 (1) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_KHR_surface (25) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_KHR_surface_protected_capabilities (1) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_KHR_win32_surface (6) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_EXT_debug_report (10) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_EXT_debug_utils (2) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_EXT_surface_maintenance1 (1) 2026-01-19T17:24:29.834813 [I]: Vulkan supported extension: VK_EXT_swapchain_colorspace (5) 2026-01-19T17:24:29.834813 [I]: Vulkan supported extension: VK_NV_external_memory_capabilities (1) 2026-01-19T17:24:29.834813 [I]: Vulkan supported extension: VK_KHR_portability_enumeration (1) 2026-01-19T17:24:29.834813 [I]: Vulkan supported extension: VK_LUNARG_direct_driver_loading (1) 2026-01-19T17:24:29.905648 [I]: INFO: ovr_GetSessionPhysicalDeviceVk inHmd = 00000234B29F8048 vulkanDevice = 00000234B3744220 vulkanDevice->m_instance = 00000234B390C080 2026-01-19T17:24:29.906188 [I]: INFO: ovr_GetSessionPhysicalDeviceVk vulkanDevice = 00000234B3744220 vulkanDevice->m_physicalDevice = 00000234B3FCFB40 2026-01-19T17:24:29.906188 [I]: INFO: API 0.64.65.47 2026-01-19T17:24:29.906188 [I]: INFO: DRV 144.0.128.0 2026-01-19T17:24:29.906188 [I]: INFO: VEN 0x10de 2026-01-19T17:24:29.906188 [I]: INFO: DEV 0x2216 "NVIDIA GeForce RTX 3080" 2026-01-19T17:24:29.982235 [I]: gpu vendor id is 10de 2026-01-19T17:24:29.994762 [W]: Unable to find loader for Texture resource at path 'textures/test/color_ramp'. File may not exist. 2026-01-19T17:24:29.996757 [W]: [GuardianDraw.glfx:269]: Program 'GuardianDrawFloor': can't find depth state 'depth' 2026-01-19T17:24:30.104946 [W]: Unable to find loader for Mesh resource at path 'models/tools_hand/ToolOrient_CursorLeft'. File may not exist. 2026-01-19T17:24:30.105917 [W]: Unable to find loader for Mesh resource at path 'models/tools_hand/ToolOrient_CursorRight'. File may not exist. 2026-01-19T17:24:30.105917 [W]: Unable to find loader for Mesh resource at path 'models/tools_hand/Tool_CursorLeft'. File may not exist. 2026-01-19T17:24:30.105917 [W]: Unable to find loader for Mesh resource at path 'models/tools_hand/Tool_CursorRight'. File may not exist. 2026-01-19T17:24:30.107484 [W]: Unable to find loader for Material resource at path 'materials/tools_ui/Crosshair'. File may not exist. 2026-01-19T17:24:30.107484 [W]: Unable to find loader for Material resource at path 'materials/tools_ui/Arrow'. File may not exist. 2026-01-19T17:24:30.108452 [W]: Unable to find loader for Texture resource at path 'textures/tools_ui/Hand_D'. File may not exist. 2026-01-19T17:24:30.108452 [W]: Unable to find loader for Texture resource at path 'textures/tools_ui/Hand_M'. File may not exist. 2026-01-19T17:24:30.248989 [I]: Didn't find existing sound '/UI/Key_Hover' using default '/UI/Button_Hover'. 2026-01-19T17:24:30.249984 [I]: Didn't find existing sound '/UI/Key_Click' using default '/UI/Button_Click'. 2026-01-19T17:24:30.257988 [S]: Could not initialize COM
Oculus Quest 2 Horizon Link pairing stuck issue
Hello there, I`ve bought Oculus Quest 2 and wanted to pair it with Horizon Link I`ve downloaded mobile app then opened it and started pairing process, so I also have turned on my Oculus Quest 2 then typed 5-symbol code to app and it was paired successfully, I can see it in my devices but there is a problem - Mobile App said that I need to continue configuring my Oculus Quest 2 actualy on my device, but then I weared it on there was nothing changed, It steel shows link code and nothing happens. Then I also tried to reset it with recovery mode -> went to boot menu and selected factory reset, when it booted it steel shows this link code and steel nothing happens. Did someone had same issue, how did you solved it ?
Quest Link desktop "blocked"
I have a Quest 3. My son has a computer. He wants to use Link to play PC games. Attempting to login to the desktop Link app with his account results in an error saying something like no permission or unauthorized or something. When I login with my account on Link it lets me do so, but then attempting to link via his account on the Quest 3 headset results in a message stating "blocked" or similar and prompts that the parent can update his account to enable Link access. There is no such menu option in Family center to enable linking. Additionally, when not connected to his PC, while logged in through his Meta account, going to settings > Link and attempting to enable results in the same message; something about it being blocked Where can I enable my son's meta account to connect via Link. Currently he cannot connect to his PC with the Quest 3, unless he uses my meta account on both the headset and the desktop software. I see no option in the family center to enable Link
New drivers are required for Meta Quest Link
I've updated to the latest, non-beta for both the newly named 'Meta Horizon Link' software as well as the Quest 2 now on v83.0. The Meta Horizon Link software doesn't seem quite finished and ready for prime time. I have a persistent beam across the top of the app stating "New drivers are required for Meta Quest Link. Update now" - When I click "Update now", the app shuts but nothing more happens. I've waited several minutes thinking it might be doing something silently - it isn't. I then reopen the app which is a preceded by a 'Repair' screen. Getting back into the app, I see that same "Update now" button, click it but now it fails because the required services were stopped in the previous attempt. I restart the services and then the app, click the "Update now" button and we're back to point 1 with it closing the app and nothing happening. I've tried completely removing the app and its registry amends using Revo Uninstaller so I can completely start with a clean slate and the issue persists after a reset and re-installation. Is there a download url to the most recent link driver outside of the app available? Or is this a false notification due to a naming mismatch between the link driver and the newly named Horizon Link software? Many thanks in advance.
Quest Pro does not connect automatically to Link
After PC power on, or PC wake up from sleep (also turning on the Meta Quest Link win11 app, if not already running), I put the headset on my head, and the main screen appears. In Quick Settings, I can see that Quest Pro doesn't automatically connect to Link via cable (it says a message "Disconnected"). This used to work few months ago (2 patches ago actually). To connect it back, I have to unplug and plug the cable back into the headset. This seems to become a new bug, or rather some software glitch, headset not connecting to pc directly.
PLEASE DISABLE LINKAPP AUTOSTART in Microsoft Windows !
Please add a simple option to "start minimized" or disable autostart.. in settings of Meta Link PC APP. No regedit, no secret autostart commands. We want to be able to control which window opens at Windows startup! Meta has been denying this option for years! Reddit is full of this. Greetings!
