link

14 Topics

Quest Link / Air Link suddenly stopped working today – session never starts
Device: Meta Quest 3 OS: Windows 11 GPU: NVIDIA RTX 5080 Connection: Air Link and USB Link (same behavior) Quest Link (both Air Link and USB Link) was working normally for months and was working earlier today. After ending a session and starting another one, Link stopped working completely. The headset is detected, the session initializes, but it freezes on the grey/purple Link screen and never reaches VR Home. Eventually the session drops or returns to the headset home. This is not a USB issue, not a network issue, and not a headset pairing issue. Important facts Same hardware and setup working for ~4 months Worked earlier today No hardware change No Windows reinstall No BIOS change No GPU change What I already tried Reinstalled Meta Quest Link multiple times Factory reset the Quest 3 Removed all Oculus / Meta registry entries Clean GPU driver reinstall with DDU Downgraded NVIDIA driver Tested both Air Link and USB Link Repair installation Restarted all Meta/Oculus services Reconfigured the headset from scratch None of the above resolved the issue. Observed behavior PC app detects the headset Session enters VR mode Streaming loop starts Grey / purple Link screen appears No image is ever presented Session freezes or terminates This indicates the session is created, but the compositor never presents a valid frame. Relevant log behavior From Service.log and LinkClient.log (same timestamps): VR session initializes Streaming starts Frames may briefly decode Compositor or transport fails shortly after Errors such as: Failed to read display driver information Graphics adapter state UNKNOWN Elevated Shared Memory failed to initialize Error -1002 Registry/config access failures after reinstall This points to a runtime or compositor state failure, not user configuration. Key point This did not degrade gradually. It stopped working suddenly today after previously working normally. That strongly suggests a silent Meta runtime update or a runtime state corruption that reinstall does not fully reset. Request to Meta Please confirm whether there was a Quest Link / runtime update today Clarify how to perform a true clean runtime reset (not just reinstall) Confirm if there is a known issue with Link compositor initialization Provide a way to roll back the Quest Link runtime At the moment, Quest Link is completely unusable despite supported hardware and exhaustive troubleshooting. I can provide full Service and LinkClient logs with timestamps if needed.
Solved
luizeduardoguaraldi
1 day ago Place Pairing & Connection
4.1KViews
34likes
83Comments
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
Sheep3165
2 days ago Place Pairing & Connection
11Views
0likes
0Comments
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 ?
N4VITEM
4 days ago Place Pairing & Connection
20Views
0likes
0Comments
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
flanktwo
22 days ago Place Pairing & Connection
594Views
0likes
6Comments
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.
mitjabonca
30 days ago Place Pairing & Connection
126Views
0likes
6Comments
I can't install games on Link
im trying to install this game but it just tells me to go to meta quest support and it couldnt install. ive tried restarting my headset and computer. does anyone know how to fix this?
Solved
Acersecomicke
1 month ago Place Pairing & Connection
242Views
0likes
7Comments
Meta PC software can't reach Meta Quest Link services.
as you can see in my screenshot somethings not right. ive searched the internet but i found nothing, i use windows and this error came when i installed the software and it went through a scan to verify everythings alright. I also tried the "repair" button many times and uninstalled and reinstalled the program a couple of times but its still not working. (also restarted my pc many times and i also have a stable internet connection.) Does anyone know what i could try?
chill_alter
1 month ago Place Pairing & Connection
14KViews
2likes
21Comments
Quest 3 — Still no PC audio when using Link via USB-C (2025)
Hi everyone, I am reopening this issue because it still happens in 2025. My Quest 3 loses all PC audio when using Link cable. Windows shows “Oculus Virtual Audio Device” and the audio meter moves, but there is no sound in the headset. Cable has been tested by the app and works at full speed. If I use the “Repair” option in the Meta/Oculus PC app, the audio works again. But after a few days, the problem returns and I have to run Repair again. This happens almost every week. This makes the headset annoying to use because repairing the app takes several minutes and should not be necessary for basic audio output. Why this is a problem: -Repairing the app every time: takes several minutes -closes services and restarts the PC app -sometimes resets parts of the configuration -shouldn’t be necessary for such a basic feature What I already checked: -Oculus Virtual Audio Device set as default in Windows -Volume and sound device settings are correct -Good USB 3 cable and port -Quest audio works fine in standalone mode -Windows 11 fully updated -Meta PC app fully updated What I am looking for: Are other users still experiencing this? Does anyone know what keeps breaking the audio driver? Is there a permanent fix that avoids repairing the app constantly? Meta support: when will this known issue be solved??? Thanks in advance for any help or new information.
rod_cas_bike
1 month ago Place Pairing & Connection
161Views
2likes
6Comments
Meta Quest Link not working
Hello, I used to be able to play on my VR with a link cable perfectly fine, but I recently got a new computer, and it doesn't work. I checked the requirements and my PC meets them without question, but whenever I try to connect the headset, my computer gives me messages like "Meta Quest Link isn't working correctly. Click here to check our support article." I checked that article, but nothing seemed to help. The Quest program on my computer shows that my headset is connected and ready to launch, and so does my headset, but when I launch it through the link cable, it just doesn't load, and it stays on a black screen. I've also tried connecting my headset through a USB hub instead of the actual computer to connect it through USB 3, but it still doesn't work. Is there any way I can troubleshoot it? Thank you!
Solved
Jxrtle
1 month ago Place Pairing & Connection
29KViews
3likes
53Comments
USB 3.0 issues with Quest 2
I see lots of similar posts about things surrounding this issue but they usually get brushed off, I am hoping that making this post and outlining what I have done so far it may finally prompt a fix. Essentially the issue is that when connecting with a USB 2.0 connection, the link is completely stable, it reliably connects for several hours and even if the headset is removed and left to "sleep", it reawakens and is still successfully connected (team events in iRacing if you're asking). When using USB 3.0 however, the exact opposite is true, generally speaking in the best case scenario, when keeping the headset awake the whole time, I can sometimes get an hour before a disconnect, however, nearly every time it goes to sleep, it disconnects and sometimes the connection will be lost within minutes of launching with no explanation. For a bit of history, over the course of trying to find a solution to this issue I have: Used a USB A-C 3.0 cable, 2x USB C-C 3.0 cables (including Oculus' own), a USB A-C 2.0 cable, a USB C-C 2.0 cable, replaced my PC's motherboard with a Asus Prime Z-390A, so I would like to think this firmly rules out the frequently posed "solutions" such as better quality cables or using different ports. I have also tried resetting experimental features as I read that sometimes causes issues but this didn't have an effect, nor has making sure that video drivers and my motherboards firmware are up to date, disabled legacy USB support in my bios settings or ensuring there is no power saving settings activated on USB ports. The most frustrating part of all is that recently I did a factory reset of the headset 'cause I couldn't think of any other fix and seemingly this finally gave me a stable USB 3.0 connection using the official cable, which not only lasted until I disconnected it (several hours), but also through cycles of sleeping and waking the headset. I then didn't play for a week and Oculus app version 38.0.0.51.727 (38.0.0.51.727) / headset version 38.0.0.63.727.351486028 installed themselves and now I'm back to the same problem of 3.0 not working and 2.0 being absolutely fine, the factory reset and experimental features reset has not had an effect this time. To be clear, there have been no hardware changes at this time so given it did work as intended previously, it has nothing to do with cable quality or any mechanical issue. Any other insight of fixes that I have not yet tried would be appreciated, although mostly an indication that this is being sincerely looked into as a known issue not just brushed off as an outlier. Please let me know if you need any additional information and I'll post when I can.
Solved
jonny_b_1990
2 months ago Place Pairing & Connection
92KViews
9likes
49Comments