HTC Vive Pro 2 Audio Not Working? The Problem Is SteamVR, Not Your Headphones

Friday, 4:30 PM. Two HTC Vive Pro 2 kits were ready for a client's soft opening. SteamVR saw both headsets. Windows saw their Sony headphones. The audio timeline showed nothing. And still: silence. The client had tried a wired JBL pair, too. Same result. From the outside, this looked like a hardware failure.

I've been configuring HTC Vive SteamVR setups for B2B clients since 2017. In that time, I've personally made—and documented—11 significant audio setup mistakes that cost roughly $2,300 in wasted labor and two client relationships. This article is the checklist I wish I'd had on that Friday.

The Surface Problem: It Looks Like Hardware Failure

The complaint is usually one of three versions:

• The headphones aren't getting any sound.
• Sound cuts out when the user moves their head.
• The wireless headset works in Windows but not inside VR.

From the outside, a dead headphone jack looks like a dead headphone jack. The reality is almost always a routing problem. But I didn't learn that until I'd replaced one headset, returned two pairs of JBL headphones, and blamed a client's Sony pair for a full week. The headphones were fine. The configuration wasn't.

Before I recommend any headset, I read the reviews for HTC Vive Pro 2 on B&H Photo-Video-Audio and similar vendor sites. The display feedback is consistently great. The audio section is mostly about the integrated speakers. What reviewers don't address is what to do when a client needs their own headphones for hygiene, comfort, or consistency across a multi-station VR space.

The Deep Cause: SteamVR Audio Routing Is Its Own Layer

Here's the part that took me too long to understand. An HTC Vive SteamVR system has not one but three audio layers:

1. The physical connection: wired, Bluetooth, or a wireless USB dongle.
2. Windows audio device selection: Default Device and Default Communication Device.
3. SteamVR audio routing: Playback Device and Mirror Mode.

Most troubleshooting stops at layer one. If the headphones are connected, people assume the problem is the headset or the game. But SteamVR does not automatically follow Windows settings. It has its own audio dropdown, and it will happily send audio to the integrated VIVE Pro 2 Multimedia device while your Sony headphones sit there, fully connected, showing zero activity.

The question isn't whether the headphones are connected. The question is which device SteamVR is sending audio to. Why does this matter? Because this is why a pair of JBL headphones can work perfectly on the desktop, then go silent the moment you launch SteamVR.

I went back and forth between integrated audio and external headphones for weeks when planning our standard B2B deployment. Integrated audio meant fewer cables and fewer things to break. External headphones meant better hygiene and the option to let each user bring their own audio. In the end, the clients decided for me: most VR arcades and training rooms want external audio. That's when the routing problem started showing up on every other install.

Wireless gaming headsets add a fourth layer: connection priority. Windows can keep multiple audio devices active at the same time. If your wireless headset connects as both a Headphones profile and a Hands-Free profile, the Hands-Free profile can swallow the audio quality, and SteamVR may end up using the wrong one. This is a classic issue with wireless gaming headsets, not just with consumer Bluetooth models from Sony or JBL.

So the order is always: hardware first, then Windows, then SteamVR. In that order. Skip the middle step and even the best HTC Vive setup will sound wrong.

SteamVR's support documentation describes the Playback Device setting as the output for all VR audio. That sounds simple. What it doesn't say is that the dropdown only lists devices Windows has already enabled. If the device is missing there, the fix is in Windows, not SteamVR. As of January 2025, this routing model is still how SteamVR behaves on Windows. I verify current details whenever I see a SteamVR update, because the setting positions have shifted before.

The Cost: What Happened When I Ignored This

Let's talk consequences. Not to scare you, but because I have a long list of avoidable costs to draw from.

The 12-Headset Training Center

In 2022, we delivered 12 HTC Vive Pro 2 kits to a corporate training center. No—11 active stations. I keep mixing it up because there was also a spare unit. We tested the audio on the first station, confirmed it, and packed the rest in. The client's IT department pushed a driver update before launch. That update reset SteamVR's audio device to the integrated VIVE Pro 2 Multimedia output on all 11 stations.

The result: 11 headsets with sound routed to the integrated speakers and a mirrored feed that created an echo in the room. Total rework: about 8 hours of technician time and $1,120 in labor—maybe $1,300 depending on how you count drive time. The client kept the contract, but the margin on that order disappeared. That's when I added a post-update audio check to our handoff process. I ignored the red flag because we had tested a sample. A sample is useful. A sample is not a rollout.

The Two-Hour Soft Opening

Another time, a two-person VR arcade rental called with audio issues. The order was small—$600, maybe. I almost sent them to our standard email flow and moved on. But their opening was in two hours. Had 120 minutes to decide. Normally I'd run a full diagnostic. There wasn't time. I went with my gut: I checked SteamVR's audio dropdown before checking the hardware. The fix took four minutes.

That small client didn't stay small. Nine months later, they ordered eight headsets. The vendors who took their little requests seriously were the ones they trusted with the big order. Small doesn't mean unimportant—it means potential.

The $3,200 JBL Blame Game

Then there was the $3,200 order where I blamed the client's JBL headphones for a sound outage. I sent them a link to buy new ones. They did. Same problem. The issue was our system image, which had reset the SteamVR playback device after a firmware update. $390 in extra labor and a client who almost switched vendors.

That's when I wrote the lesson on the wall, and now I repeat it to every new tech:

Before you blame the headset, check the routing. Then check it again after any update.

Whether the client is a one-room arcade or a hospital buying 50 headsets, the audio setup is the same. I've learned not to treat smaller orders as not worth the support time. That $600 client became an eight-headset contract. The small order isn't a nuisance; it's a trial.

The Fix: A Short Checklist That Works

The solution is not complicated. It's just not where most people look.

How to Connect JBL Headphones to HTC Vive Pro 2

Here's the checklist we use now. It takes about five minutes.

1. Connect the headphones to the PC first. For JBL wireless models, put them in pairing mode and add them in Windows Settings > Bluetooth & devices. For wired JBL models, plug into the 3.5mm jack on the Vive Pro 2 headset cable.
2. Open SteamVR. Click the dropdown arrow on the SteamVR status window. Go to Settings > Audio.
3. Set Playback Device to the JBL headphones. If they don't appear, they're not registered as a Windows audio output yet—fix that first.
4. Set Mirror Mode to Off unless you specifically need audio on the integrated headset at the same time.
5. Launch a VR app and test. If sound still doesn't work, check Windows Sound Settings and make sure the same device is set as both Default Audio and Default Communication Device.

Sony Headphones? Same Process

The process is the same for Sony headphones, whether it's the WH-1000XM4, WH-1000XM5, or an older model that pairs over Bluetooth. The Sony app is useful for firmware updates, but SteamVR doesn't read from the Sony app. It reads from Windows. If the headset isn't visible in Windows as an output, it won't appear in SteamVR.

For any HTC Vive SteamVR setup, the audio path is: Windows sees the sound device, then SteamVR picks the output, then the VR app follows. Bypass that second step, and no amount of good hardware will save you.

Wireless Gaming Headset Notes

For a wireless gaming headset with a USB dongle, the dongle usually shows up as its own audio device in Windows. Select that exact device in SteamVR. If the headset has separate Game and Chat channels, use the Game channel for VR. Choosing the Chat channel makes audio sound hollow, and sometimes it drops to mono.

Oh, and one more thing: check USB power management. If the wireless dongle is plugged into a USB port, Windows can decide to power it down. Open Device Manager, find the USB Root Hub, and disable 'Allow the computer to turn off this device'. This matters more for wireless gaming headsets than for wired ones.

And a note on the low-latency promises you see in wireless headset marketing: I'm not going to guarantee any specific model here. Per FTC guidelines (ftc.gov), performance claims should be truthful and substantiated. My experience isn't a substitute for testing the actual headset on the actual PC and the actual VR app you plan to run.

The reviews for HTC Vive Pro 2 on B&H Photo-Video-Audio will tell you plenty about the display. They won't tell you how to reconnect a JBL pair after a firmware update. So I'm telling you now: check the routing before you swap hardware.

Bottom line: if your HTC Vive Pro 2 audio is silent, crackly, or cutting out, stop looking at the headphone and start looking at SteamVR's audio settings. I wasted $2,300 learning that. You don't need to.