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
Quest 3 - connects, but PC no longer sees it (v85)
SITUATION: When I connect my Q3 to laptop, (as I've done for years), it beeps, and charges, but doesn't pop-up in explorer (nor show the access files dialogue box). BACKGROUND: I have used windows explorer for years with no issue across multiple Quest headsets. I don't believe I have changed any settings. I have also looked through Quest device settings (and web), and can't find the way to force the access files pop-up. [possible solution?] PURPOSE: My intent is to download recorded content from my device and edit before publishing to YouTube, etc. HOW TO REPLICATE: Plug in Q3 to PC/laptop with trusted cable. NOTES: Currently on v85 Connecting to my PC brings up the charging indicator light as expected Connecting makes the affirmation beep Link still works (can see desktop, play VR games) SideQuest works The usual pop-up "allow connected device to access files" doesn't show I recently had a temporary warning that it detected water in the port. Yet that was random (no where near water), and went away within 30 minutes. Rebooting both devices doesn't change anything. I've spent a few hours trying to figure this out, and would love any ideas you have.
No option to disconnect VR-headset via PC (Air Link)
Situation/Context: I am in a position where I work with multiple Meta Quest 3 VR-headsets (one at a time, but multiple lying around). Since I do not work alone these multiple Meta Quest 3's belong to a pool of VR-headsets, freely usable by anyone around. Problem: When having a Meta Quest 3 linked to a computer via the Meta Quest Link app (Air Link), a new connection with another Meta Quest 3 cannot be established — neither is it possible to have multiple VR-headsets connected at the same time, nor does a new connection (attempt) disconnect the current one. If a VR-headset is connected to some computer and not actively disconnected, it will try to connect to this very computer everytime both devices are turned on and connected to the same WiFi. If the paired VR-headset is now being used by someone else, who is not using the Air Link option, this very connection stays active. As a result the computer, which is still linked to the now-away-VR-headset, cannot be used with another VR-headset — neither via Air Link, nor via a cable connection. There simply is no option from the pc-side to cancel an active connection. Restarting the Meta Quest Link app (through the beta-version feature) will result in the connection being instantly established again. This also happens after restarting the entire computer — as soon as the Meta Quest Link app has started and the WiFi connection is active, the paired VR-headset is connected again. Further questions: Are there any methods to disconnect a vr-headset-pc-connection without access to the vr-headset? Any other tipps to avoid the above described situation (other than 'just disconnect the VR-headset before you stop using it')? Possible solution: Adding a button inside the Meta Quest Link app to actively disconnect a VR-headset would solve this issue in an instant. I would think that there are a couple of people out there who are developing with the Meta hardware and would appreciate such a feature (as to no longer hunt for the currently connected VR-headset and politely ask the current user to disonnect the Air Link connection..). ThanksResolved - Unstable wifi coverage with Quest 3 on some Router Brands.
Update January 2024 - full post history below Hi. Let me try to give a quick TLDR summery. Since the launch of the Quest 3, numerous users have encountered difficulties with their Wi-Fi connections related to wireless PCVR. A notable bug affects certain mid-range AX and AXE routers, such as TP-Link's AXE75, leading to significant packet losses and varying negotiation rates. Consequently, connection speeds fluctuate between 480 and 1921 Mbps, occasionally reaching 2161 Mbps but rarely achieving the full 2401 Mbps speed. In contrast, the Quest 2 maintains a stable 1200 Mbps on 5GHz dedicated networks. However, on release, the Quest 3 struggled to reach 720 Mbps, with speed fluctuations occurring every other second. Meta was promptly notified of this issue on launch day and has been working on resolving it through build updates. Versions v.57 to v.60 have seen a dramatic reduction in negotiation rates, making wireless VR "usable" under certain conditions, particularly when in close proximity to the router and within the line of sight. Nevertheless, users still report random speed reductions to unusable levels (below 740 Mbps), even at close range. TP-Link has been diligently working on resolving the issue since the initial launch. Unfortunately, their latest update indicates that they couldn't make a breakthrough on their end, and they believe the problem persists on the client side. They've conducted thorough tests with various chipsets, including MTK, BCM, and QCA routers, and it seems these routers are experiencing similar issues. Their focus shifted to Meta software updates, and their most recent test with the Quest3 V60 suggests that while the negotiation rate still varies, the occasional streaming lag seems to have disappeared. A glance at this threads posts reveals that TP-Link is not the only affected brand; users with Asus and other AX and AXE routers also face similar challenges. The root cause seems to be linked to either Meta or Qualcomm. Users have noted similar issues with the Google Pixel 7, leading to speculation about problems with the XR2 Gen2/Snapdragon 8 Gen2 drivers. So in other words it's in Meta and Qualcomm's hands at the moment. Please reply to this thread and post your information as per Metas instructions: "December 14th Update from MetaStoreHelp Hey everyone! I wanted to let you all know that I heard back from our engineering team. It looks like there might've been some changes with the recent v60 update. I recommend checking your headset to make sure that it is updated to the latest version, and then checking your Wi-Fi connection with your headset. If you're still having trouble after updating your headset, please let me know the below information and I'll pass it along to our engineering team so this can be looked into further. 1. Router make and model. 2. Router firmware. 3. Full Headset version. (59.0.0.##) Go to Settings > System > Software Update" You can also make a video grab of your issue and send it to Meta over the "report a problem" option in the headset. For video references on the issue here is a playlist in chronological order NOTE: If you have a working setup with a different router and not experiencing any issues please post the details on this separate thread: https://communityforums.atmeta.com/t5/Get-Help/What-Wifi-6e-routers-currently-works-bug-free-with-the-Quest-3/td-p/1101778 Original post October 10th 2023 On my Quest 3 the WIFI signal is hopping from 720 - 864 - 960 But my Quest 2 ti stable at 1200 Mbps I am sitting 1 m from the Ruter Is my Quest 3 broken or is this a bug? Edit FYI: This is a firmware bug with communication between some brand of routers. Please post your info here as a reply. (Se MetaQuestSupports reply) The team has been made aware and is currently looking into the unstable connection reports. Meta needs to know: What version is your headset running? (Full number, i.e. 57.0.0.####) Quick Settings > System > Software Update Which router do you currently have? Tag MetaStoreHelp Also.. Remember to send a bug report via Oculus apps or headset... Here is how: https://www.youtube.com/watch?v=7i9Q_h_yeQQ Edit 2, to be clear: The issue is not dependent on AirLink or VirtualDesktop. It's a clear communication issue between the Quest 3 and certain routers in Quest build vertion 57. That effects both 5Ghz and 6Ghz. Quest 2 is unaffected. Here is the issue we are facing demonstrated to TP-link: https://youtu.be/JFrl9rTJH8E?si=2vBOI6E2PjGvPL_7 If you're r not experiencing any issues please post the details on this seperate thread: https://communityforums.atmeta.com/t5/Get-Help/What-Wifi-6e-routers-currently-works-bug-free-with-the-Quest-3/td-p/1101778 Edit 3 - Update: Version 59 showed no improvement. TP-Link has received a unit and are experiencing the same negotiation rate problems. They are investigating the problem. MetaStoreHelp has stated that they are working on the issue and it will be fixed in a future firmware update. https://communityforums.atmeta.com/t5/Get-Help/Unstable-wifi-covarage-with-Quest-3-on-some-Router-Brands-Known/m-p/1099915#M241197 Edit 4 - Update... TP-Watched @VirtualOmnipresence 's video and confirmed: Our Wireless RD found that it might be the case Quest3 are kind Quest3's wireless connection rate strategy is more aggressive in terms of speed reduction. Once it encounters wireless packet loss or interference, it will reduce the negotiation rate on a large scale, thus affecting the actual wireless performance. In other words, it is actually unnecessarily overly sensitive... especially when interference is basically impossible at 6GHz. We've tested the Quest3 v57(haven't got v59 yet) so far with almost all our routers from wifi6e to wifi7 with QCA/BCM chipest... Also thanks a lot for your updates about that article, we will also notice to get the previous quest2 sample to check how it works with our router in old firmware, then upgrade it to newer one for checking. We will also focus on this issue later quickly if there's new firmware released. Edit 5 - November 20th 2023 Still no more contact with meta and the silence is deafening. Though with the new update to v.59 it is actually a lot better on AXE75 for both 5g and 6g. It's fluxing, but not below 1200 in 6g and not below 720 in 5g. Making it... "usable"... if you are relatively close to your router. Here is my video in my test with v. 59. We still want to take advantage of the 2401 Mbps so that we are not reliant on no interference and being 2 to 3 meters from the access point. Any working 6Ghz device connected to a 6 Ghz router, dedicated at close range should output a connection at 2401Mbps. If it doesn't it's simply not working correctly. So I'm not giving you a pass just yet Meta. 😉 Edit 6 December 8th A lot of new posts here and in my community on still experiencing this issue making their wireless experience unbearable. The uptick has been noticeable since the release of SteamLink bringing more people over to PC wireless. I also go a new confirmation from MetaSupport over email: Meta Store Support following up on your issue. To clarify, the issue you are experiencing is most likely to be patched up with a new software update. I know how inconvenient this may be for you. We really appreciate your extended patience and utmost understanding regarding this matter. As much as I would like to give you an exact timeline, since this is still a known issue, I'm afraid we are still unable to provide an exact date for it. This is also for our customers, as we don't want to set you an expectation that is vague. We value transparency here at Meta, and we can assure you that we will quickly contact you as soon as possible once the issue is resolved or workarounds are provided. We're eager to have this one sorted out for you, so we'll keep an eye on this issue. Looking forward to solve this issue at your earliest convenience so you can proceed enjoying your VR experience. ---- later: I can confirm that your issue regarding Wi-Fi connection has been coordinated with our engineering team; however, they didn't provide an exact time; maybe they are still figuring out the root cause of the issue. By the way, thank you for the clear explanation of your issue; that helps us a lot. Edit December 14th Update from MetaStoreHelp Hey everyone! I wanted to let you all know that I heard back from our engineering team. It looks like there might've been some changes with the recent v60 update. I recommend checking your headset to make sure that it is updated to the latest version, and then checking your Wi-Fi connection with your headset. If you're still having trouble after updating your headset, please let me know the below information and I'll pass it along to our engineering team so this can be looked into further. Router make and model. Router firmware. Full Headset version. (59.0.0.##) Settings > System > Software Update --- Here is my video on testing version 60
