HP Reverb G2 Headset Checklist: Price, Setup, and the “Why Can I Hear Myself” Fix

Let me make one thing clear: if you’re deploying VR headsets on a tight deadline, you don’t need another long-winded review. You need a checklist.

I’m a deployment specialist at an IT services company. I’ve handled 40+ HP Reverb G2 setups in two years, including a call at 9pm where a client needed six headsets ready by 8am. This is the checklist I use when there’s no time to waste.

Wait: what are you actually buying?

If you search “HP Reverb VR3000 G2 virtual reality reviews,” you’ll see product titles that look like different models. They’re not. The product is the HP Reverb G2. “VR3000” appears in seller titles and SEO pages, but it’s not an official model name. If the box says “HP Reverb G2,” you’re good. If it says anything else, check the SKU before you buy.

Looking back, I should have checked the SKU more carefully on two “new in box” units. At the time, the price seemed safe. It wasn’t—they were refurbs with third-party cables. Took an extra week to get proper replacements.

As for the HP Reverb G2 VR headset price, it varies a lot. Based on public U.S. retailer listings in January 2025, a complete kit with controllers and cables runs roughly $299 to $449. Some marketplace listings go lower, but they’re often open-box or missing the DisplayPort cable. Prices change quickly, so verify current rates before you order.

Check the PC before you unbox

Most problems that get blamed on this headset are actually PC compatibility problems. Seriously. This list takes five minutes and saves you a ton of frustration:

1. Windows 10/11 64-bit, fully updated.
2. A discrete GPU at or above an NVIDIA GTX 1080 / RTX 2060 or AMD RX 5700.
3. DisplayPort 1.3 output, not HDMI.
4. USB 3.0 port, either Type-A or Type-C.

If you’re on a laptop with only USB-C, confirm that port supports DisplayPort Alt Mode. A passive USB-C to HDMI cable won’t work. This is one of those details that looks minor until nothing turns on.

To be fair, the Reverb G2 is less picky than older VR headsets. But “less picky” still means “not plug-and-play.” The difference between a setup that works and one that doesn’t is way more about drivers and ports than about the headset itself.

Update everything before you plug it in

This is the step almost everyone skips, and it’s why so many “defective” headsets get returned. Trust me on this one: update first.

Run Windows Update until it says you’re current. Update the GPU driver from NVIDIA or AMD. Then make sure Windows Mixed Reality is installed. (Settings > Apps > Optional features > Add a feature > Windows Mixed Reality).

After three failed demos with outdated drivers, our policy is simple: no updates, no headset. If you skip this, you’ll probably spend an hour chasing a black screen that’s actually a driver issue.

Also update the headset firmware when Windows Mixed Reality asks. I know another setup prompt feels annoying, but one firmware update fixed a flickering screen for us. So let it run.

Setup: 10 minutes if you do it in order

Once everything is updated, the hardware setup is straightforward:

• Connect the DisplayPort and USB cables, then the power cable.
• Start the Windows Mixed Reality portal and set your boundary. Use “standing or seated” if you’re short on time.
• Let the headset install any firmware updates.
• Adjust the IPD. This is the little slider near the bottom of the headset. When the IPD is right, the display is very sharp—the Reverb G2 uses two 2160×2160 LCD panels (Source: HP product page, accessed January 2025).
• Pair the controllers by holding the Windows button until the light changes.

If you do it in this order, the average setup takes about 10 minutes. That’s from box to loaded into the VR home environment. We cut our average deployment from 40 minutes to under 15 just by standardizing this sequence.

Even after choosing the Reverb G2 for our client standard, I kept second-guessing the inside-out tracking. What if the room was too dark or too bright? The week until the first pilot was stressful. It worked fine once we paid attention to lighting. So if you’re worried—you’re probably fine.

Why do I hear myself in my headset?

If you’ve searched “why can I hear myself in my headset,” you’re not alone. It’s usually one of two things.

Cause 1: the open speakers

The Reverb G2 doesn’t use sealed ear cups. It uses off-ear speakers that sit near your ears. That design means you’ll hear your own voice naturally when you talk. This is intentional. It also means you won’t get the fully isolated feeling of a closed-back PC headset with mic.

Some people love the open feel. Others don’t. If you want full isolation, you’d need to wear separate headphones, but that gets uncomfortable under a VR headset.

Cause 2: microphone monitoring

If your voice is loud in your ears or there’s an echo, Windows is probably playing your microphone back to you. The fix:

1. Right-click the speaker icon in the taskbar and open Sound settings.
2. Go to the Recording tab.
3. Select your microphone and open Properties.
4. Go to the Listen tab.
5. Uncheck “Listen to this device.”

That fix applies to any mic, whether it’s the Reverb G2’s built-in mic, a PC headset with mic, or a Plantronics wireless headset you use for calls. Same Windows setting, same result. I’ve spent an entire afternoon on an echo that was just that one checkbox. So turn it off before you blame hardware.

Also check SteamVR’s audio settings. If “mirror audio” is on, it can cause feedback. Set it to “Room” or turn it off depending on what your app needs. Launch a test app and talk. If you still hear yourself, check if your communication app (Teams, Zoom) is doing its own monitoring.

The most frustrating part of audio issues is that they always look like a hardware failure. You’d think a $600 headset would handle audio cleanly, but Windows controls the sound stack. Once you know where the setting lives, it’s a two-second fix. So glad we found it before the CEO demo.

Test everything before the event

Don’t call a deployment done just because the Windows Mixed Reality portal opens. Run the 5-minute test:

• Move the controllers around the whole boundary. Watch for drift or position jumps.
• Press every button. The thumbstick click, trigger, grip, menu buttons.
• Speak into the mic and check the recording level in Windows.
• Turn around slowly to make sure the cable doesn’t pull the headset.

Fix smaller issues now. In March 2024, a client called 36 hours before a training event: their main headset had a broken cable. Overnight shipping cost us $150 extra, but that was still cheaper than cancelling. We paid the rush fee and made the deadline. Ever since, we keep one spare cable for every five headsets.

Even simple problems turn into emergencies when you’re on the clock. A checklist like this is what lets you spot them early.

Common mistakes I still see

After dozens of deployments, a few issues come up again and again:

• Leaving the lenses facing direct sunlight. Sunlight can damage the displays through the lenses. Put it away properly after use.
• Too much or too little room light. Inside-out tracking needs steady, adequate light. A dim room will make controllers jump around.
• Not switching the default audio back when the headset is unplugged. Your desktop speakers stay silent until you change the default device back. It’s a Windows setting, not a broken computer.
• Buying replacement cables that don’t match the headset revision. The G2 has had cable revisions over the years. Check the part number.

To be fair, these aren’t unique to the Reverb G2. Any PC VR headset has its own quirks. But if you’ve already got experience with a regular PC headset with mic, you’re halfway there. The rest is just learning where the VR-specific settings live.