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.
Can't disable Xbox controller from interacting with my headset
When a controller is connected to my PC while using (wired) Oculus Link and I am viewing my monitors from within the headset, there will be a dot on the screen that follows my head movements. If I press 'A' on my Xbox Elite 2 Controller, it will act as if I left-clicked where that dot is, 'B' brings up the In-Headset keyboard context menu, left-trigger moves my in headset window, and right-trigger seems to snap my cursor back to the dot. The thing is, I don't want my controller interacting with my headset at all. I want to use my headset, with my computer viewing my monitors in headset and play a game with my controller without those inputs that were meant for the game, also interact with the headset. Another example is that if I'm playing something like Elite Dangerous, which is (very!) VR capable, but needs more input capability like the mouse and keyboard or bunches and bunches of mapped buttons on a controller. To be honest, the controller is easier for games like Elite Dangerous for most tasks but I can't have my 'A' button interfacing with the headset. Not related to Elite, but I also don't need my left-trigger to suddenly start launching in-headset window that I'm currently looking at all over the place. If I need input within my headset, I will grab my headset-controllers that I've set safely just off to the side, or if I can't find them, I can take off my headset to look for them. What's more, if I'm going to interface with my computer's monitors, I'll either be close enough to the computer to use the mouse and keyboard or I'll put back on and use the headset's controllers. I'm honestly not sure how this wasn't a user scenario when designing it. I've seen other posts from years ago and there hasn't been any change in this behavior to accommodate this scenario. I understand that this doesn't fit all persons because maybe the computer is far away from the Oculus and the only input you have in your hands is the controller but, in my situation, I need the ability to disable that. Is it possible to do this?Meta Quest Link Update: Link Launch Issue Resolved
Hi everyone, We recently identified an issue with Meta Quest Link unable to launch which caused users to be stuck in the app launch loading screen. We’ve now released an update that should resolve this problem. What’s changed: The main issue is fixed, and you should be able to use Meta Quest Link as expected. Please note: For now, you won’t be able to see your hands in Dash. However, raycasts are visible, and you should be able to interact with games and other content as usual. Thank you for your patience while we worked on this fix! If you continue to experience any issues, please let us know in the comments.
can't set oculus as active openxr runtime
i have a quest 2 and use it on link but it wont work at all because when i click the button here it just does nothing in the quest when i click enable link it loads for a few seconds and just reloads the home area (nothing happens) please help my quest 2 is unusable for pcvr like this and it seems like such a simple thingMeta Link freezes after a few seconds
After installing latest Meta Horizon Windows app update (85.0.0.239.552), the display inside headset freezes (sometimes goes black, similar to when proximity sensor kicks in, but while still wearing VR headset) after a few seconds after establishing cabled link (official 5m cable). Have to restart PC and re-establish Link to get it to work again, but then same happens after a few seconds. Can still hear audio inside headset, and when using games it seems to do head tracking (monitor screen updates, but not inside headset). This also happens inside the Meta Link view (grey environment with grid floor and ceiling inside VR headset after establishing link). Firmware in VR headset is also on latest version, This happened after updating Meta Horizon Windows app on 3rd/4th March. Before this it was working perfect. Have tested this on 4 different PC's, with 3 different Meta Quest 3 headsets and one Quest Pro, with same result. Hardware on test PC's: Windows 11, different i9 processors (13th/14th gen, Intel Core Ultra 9), RTX 5090 laptop, RTX 5070 Ti Desktop, RTX 4090 desktop. 64GB RAM, NVIDIA GeForce Graphics Drivers 595.71 WHQL driver + latest Windows updatesKnown Issue: Closing Steam VR crashes Dash
Hi everyone! We're seeing a small group of Steam VR users finding that Dash is crashing on headset and that their PC is becoming unresponsive once they quit the app. The team is working on identifying and fixing the root cause of this issue, and right now the investigation shows that this is likely related to Hardware Accelerated GPU Scheduling being enabled when using certain Nvidia GPUs. If you're having this issue, there is a workaround In the meantime! You can prevent this happening by disabling the Hardware Accelerated GPU Scheduling feature. To do so, follow these instructions. If you need any further help or have noticed other bugs around Steam VR, please comment below. Let me know if you have any questions!
