Audio no longer works when connecting to Windows 11 via AirLink/Link Cable
[Note as of 12/6/2025 - For me, this was fixed by the latest update to the Horizon Link software, and joining the Beta Channel is no longer needed.] The Problem: As of 11/26, I no longer get any audio through my Quest3 headset while I'm connected to my Win11 PC via AirLink. This has worked for me for years, and this is the first time I've had an issue with it. The only change I'm aware of, is that I did a 'Repair' using the Oculus Installer to solve a different issue I was having (a "can't find OculusClient.exe" error). After the Repair (which looked successful), I started having this audio issue. To be clear, audio works fine for me in the headset when I'm not connected over AirLink. Once in AirLink, I get no audio from any desktop Oculus app that I run. I've tested a few. When I leave AirLink, I get local audio in my headset again. Solutions I've Tried: There are a fair number of support threads on this kind of issue here and in Reddit, and I believe I've Googled and found them all. None of them have solved my issue. Here is the list of things I've done: [Note: Just because a solution didn't work for me doesn't mean these are bad solutions. Some of these have worked for others. Indicated by a (*). As of 12/4 the solution marked with (***) now works for me!] (Last updated 12/4/25) Use cable instead of AirLink (*) Run the repair using the Meta Quest Link (Oculus) Installer (*) Uninstall Meta Horizon Link, reboot PC, reinstall the app, reboot PC and Quest 3, and try again Scan the Setup and Driver install logs for errors (I don't see a smoking gun, but the logs are attached to this post) (*) Manually uninstall the Oculus Virtual Audio Device input driver from device manager, then uninstall and reinstall Horizon Link (also rebooting in between steps again, to be sure) (*) Rename my Oculus Virtual Audio Device to "Headphones" (It used to be named "Quest VR", and it worked fine, but I changed it back to Headphones after reading another forum post) (***) Join the Horizon Link Beta Public Test channel, let the app update, reboot my PC and Quest, and trying again Unpair my Quest3, uninstall Horizon Link, delete ...AppData\Local\Oculus directory, reboot, reinstall, repair the Quest and try again Uninstall Horizon Link using Revo Uninstaller, let it do a complete post uninstall clean, reboot, reinstall, try again Reboot my PC and Quest 3 many times by now during various troubleshooting steps Obvious steps: make sure I can get audio on my PC through other outputs, make sure the volumes are correct, make sure that correct audio devices are selected at the right times, etc. My Settings Here are what the relevant settings on my PC look like when I'm connected via AirLink. Audio Devices Meta Link Program I have also tried all the combinations of Hear VR Audio from Computer and Hear Computer Audio in VR, but the screenshot below shows what used to work for me and now no longer works. Audio Devices The Virtual Audio device is present, enabled, and can get audio. It is also named "Headphones". NOTE: Something I find a little bit weird is that when I'm connected via AirLink, the volume is always showing at 1/2 level, even when I have no audio playing on my PC. When I disconect from AirLink, it stops doing this, and only shows the audio bar when something is actually playing. I don't know if this behavior occurred before my issue started, or if it coincides with it. Audio Devices Here are all the audio devices on my PC. I don't know exactly what I'm looking for, so I don't know if this is correct or not. It looks correct, although I do find it a bit strange there is no Oculus Virtual Audio Device under the Sound, video and game controllers section Drivers I can tell that the drivers are being updated whenever I install the Meta Quest Link Program, because the timestamp of these files is always updated NOTE: I do find it a bit strange that the Oculus Virtual Audio Device shows different driver information depending on where I look. Here it is in Win11 basic settings: Here it is in the Device Manager: Worth Mentioning (Windows error after Installation) Whenever I finish an installation or repair, I always get this error. I don't believe this is related to my audio issue, because my installation seems successful, as shown in my previous screenshots. But it's worth mentioning. NOTE: the Meta Quest Client is NO LONGER called 'oculus-client\OculusClient.exe', but simply 'oculus-client\Client.exe'. I don't know where on my PC there is old data pointing to the old filename, but it clearly affects the installer (even though I just downloaded the latest version from the website). I also had to manually fix my Meta Quest Link shortcut that had this same problem. I've been a user since the original retail Oculus, so maybe that's why this happened to me once the devs changed the client exe name; not sure. Again, I doubt it's even relevant. Obviously I didn't have this issue way back when I first bought my Quest 3 and set all this up. Thanks for any help with this issue.
Air Link suddenly not working
When i try to connect my quest 2 to my pc using airlink then it instantly gray's out. If i try to use an another pc and it is unavailable then it takes time to gray out not instantly. If another pc is available then it works normally. I have factory reset my quest and did a clean install of windows 10 and the quest pc app. I have reset my router, anything that could be reset. SteamVR works fine with steam link. I was casually using AirLink and one day i turned my quest off and then the next day it just didnt connect and hasn't since. There werent any updates so that coulnt be the issue.
(Not Resolved) Known Issue - Quest PCVR streaming micro lags and stutter esp. when moving head
Hi team, I'm getting micro lags and stutter in Airlink on my Quest 3 (EU/UK), esp. when moving my head. In the Oculus debug overlay this causes brief spikes in transmit/decode, fps drops and visible stuttering. The issue is not present on my Quest Pro with otherwise identical settings - see below screenshots to illustrate. Few more details: - Issue is not present on Quest Pro with same settings on HMD, router and PC (using same res) - Issue is worse at higher bitrates, esp. >200mbps, but still present <200mbps - Issue is unrelated to PC/game latencies (CPU, GPU, Queue each <5ms) - Stutters/lags are intermittent (every 10-20 seconds) when not moving but happen immediately and reproducibly when moving the head to either side or especially looking downwards (i.e. on any bigger headset movements) - Wifi 6E router (TP Link AXE75 EU/UK) - EDIT: exact same issue with Asus RT-AXE7800 (EU/UK) wifi 6e router - Connection shows as 2,400mbps - Airlink codec H264 (but same on other codecs) - I've attempted factory resetting, installing latest drivers - Updated to v62 and latest Quest Link desktop version (I can see the 120hz option for my Q3) - EDIT: Ordered a separate Quest 3 for testing: presents the exact same issue -EDIT: Same issue on 5ghz 802.11ax 160mhz BUT switching to 802.11ac (!) completely fixed the issue. I cant test this on 6ghz but looks like 802.11ax or something related to how q3 implements it is the culprit As the issue is worse the higher the bitrate and not present on Q Pro with otherwise same settings, I suspect it's related to the below known Wifi issues - but opening a new thread as instructed. https://communityforums.atmeta.com/t5/Get-Help/Known-Isssue-Unstable-wifi-coverage-with-Quest-3-on-some-Router/td-p/1090698 Best, Jens Updates: - Tried separate router: exact same issue with Asus RT-AXE7800 wifi 6e router - Ordered a separate Quest 3: exact same issue on both routers -Same issue on 5ghz 802.11ax 160mhz BUT switching to 802.11ac (!) completely fixed the issue. I cant test this on 6ghz but looks like 802.11ax or something related to how q3 implements it is the culprit
What Wifi 6e routers currently works bug free with the Quest 3?
Hi! Just wanted to post here to get a seperate thread going. As of today there is a major bug in communication between Quest 3 and certain types of Router models. So let's get a list started on Wifi 6e routers that actually work. What Router do you have experience with being stable at 2400 Mbps in dedicated 6e mode? Remember to post Router name and model and screen grabs/video from the Quest 3 showing the speed. (Turn on experimental wifi settings to do so.) This is by no account a list that is for everyone. So far I found that some of the more expensive models between 350-700$/€ have been reported to work. So meta still has a major bug to fix. But if you can afford it, this might be is a way around the problem… ___________________________________________________________________________________________________ The bug explained: There is a bug with negotiation rates with certain router models. Essentially AX and AXE models but more might also be affected. I have been investigating this bug since launch and finally both Meta and TP-Link have confirmed that the Quest3s negotiation protokolls with the routers is very unstable. This problem is totally unrelated to VD or AirPlay functionality, but it's here you'll notice the problem. As of right now the Mbps can flux from approximately 1080 to 1900 on 6G and ocasinaly dip down below 800. Making it stutter and glitch in latency. On 5G it will flux between 1080 and 420 Mbps making it essentially unusable in wireless PC streaming. Both Meta and TP-Link are currently investigating the problem. Meta has stated that the problem will be fixed with a firmware build in the near future. If your experiencing this bug and want to follow its progress you can follow this seperate thread: https://communityforums.atmeta.com/t5/Get-Help/Unstable-wifi-covarage-with-Quest-3-on-some-Router-Brands-Known/m-p/1099915#M241197
Resolved - 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
