HP Reverb G2 SteamVR Setup: A Field Checklist for When the Demo Is in 2 Hours

If you've ever had a VR headset throw a "check your cable" error 20 minutes before a client demo, you know the specific cold sweat that comes with it. I'm a VR deployment coordinator at an immersive tech company, and in the last three years I've handled around 200 rush setups — maybe 180, I'd have to pull the logs — including same-day turnarounds for trade show clients. The HP Reverb G2 is the headset I've configured the most, and the process has steps that are non-negotiable when the clock is running.

In March 2024, a client called at 7 PM the night before an investor demo. The headset had worked for months, then SteamVR suddenly stopped seeing it. Their previous IT contact suggested reinstalling Windows. We walked through the WMR side of things remotely, found that a Windows Update had reset the default audio device — which made the whole SteamVR session fail at launch — and had the demo running in 20 minutes. This checklist is the condensed version of days like that.

This guide is for anyone getting an HP Reverb G2 working with SteamVR, whether it's a fresh unit or one that's been sitting in a storage closet since last quarter. It won't recap the full spec sheet — you can get that from any solid HP Reverb G2 virtual reality headset review. What it gives you is the order of operations I use when a demo is two hours out, plus the maintenance detail most reviews skip entirely.

Seven steps. Thirty minutes if you've done it before. Ninety if you haven't.

Before Anything: Get the Software Stack Right

It's tempting to think you can plug the Reverb G2 in, launch SteamVR, and go. But the Reverb G2 is a Windows Mixed Reality headset first and a SteamVR headset second. The order matters more than it should.

Here's what needs to be in place before you touch the hardware:

• Windows 10 or 11 with current updates. The G2 genuinely does not like stale builds.
• The Windows Mixed Reality app from the Microsoft Store, set up at least once, with any firmware update applied.
• SteamVR installed, plus the Windows Mixed Reality for SteamVR plugin.
• A GPU that can actually push 2160x2160 per eye — that's the display resolution per HP (hp.com, accessed January 2025). A GTX 1060 will technically run it. Technically.

The "just works" tone in a lot of HP Reverb G2 reviews assumes a healthy WMR runtime underneath. In our experience, about half the "broken" headsets we've received were tested by someone who skipped the WMR setup entirely. The headset wasn't broken. The order was wrong.

Step 1: Run WMR Setup Before SteamVR Even Opens

When I'm triaging a rush setup, the WMR Portal is the first thing I open. Let it complete the device setup, apply any firmware update it asks for, and walk through the boundary configuration. This is also where the displays first come alive at the correct refresh rate. If something is going to fail, I want it to fail here, not in front of a client.

Here's the common misstep: someone opens SteamVR first, sees "headset not found," and spends an hour reinstalling SteamVR, updating graphics drivers, and reading forum threads. SteamVR isn't the problem. The WMR runtime has to recognize the headset first. WMR is the driver layer; SteamVR is the storefront.

Checkpoint: In the WMR Portal, you should see a live feed from the headset's cameras and tracked controllers. If that works, move on. If not, solve it here — no amount of SteamVR configuration will fix a WMR-level failure.

Step 2: Pick the USB Port, Then Check the Cable

The Reverb G2 is picky about power delivery, and USB connectivity is the most common field failure with this headset. On our first few deployments, we burned hours on "check your USB connection" errors from front-panel ports. Rear-panel USB 3.0 ports deliver more stable power, so that's our default now. For laptops, use the USB-C port if it supports DisplayPort Alt Mode.

Don't hold me to the exact ratio, but I'd estimate 70% of our "headset not detected" tickets are USB-related. It has nothing to do with the headset itself. It's the port.

While you're down there, feel the cable where it enters the headset. The strain relief is decent, but in shared demo environments the cable gets yanked more than it should. A loose connector causes intermittent SteamVR disconnects that look exactly like a software bug. If it wiggles, reseat it.

Step 3: Launch SteamVR From Inside the WMR Portal

One detail that separates smooth deployments from messy ones: don't launch SteamVR from your desktop shortcut. Launch it from inside the WMR Portal, either from the quick actions bar or by opening a SteamVR title directly. The Windows Mixed Reality for SteamVR plugin does the handshake, and it's most reliable when WMR is already active.

First-time setup will ask you to confirm the room boundary and floor height. Pay attention to floor height. On carpeted demo floors, it's off by default more often than you'd expect, and a wrong floor height makes every app feel broken because your virtual ground doesn't match the real one.

Checkpoint: Open the SteamVR status panel. Headset, controllers, and tracking should all show green. The G2 uses inside-out camera tracking, so you don't need base stations for the headset or controllers — one less thing to go wrong.

Step 4: Set the Audio Routing Before You Need It

I'm not an audio engineer, so I can't speak to frequency response curves. What I can tell you from a deployment perspective is that Windows gets confused about audio routing with this headset. It sometimes picks "Mixed Reality Headset," sometimes "Headphones," and sometimes your laptop speakers, with no obvious logic. The result: the demo looks fine but the sound is coming from a laptop three feet away.

The practical fix is two parts: set the default output device to the Reverb G2 in Windows sound settings, then open SteamVR Settings → Audio and enable "mirror audio to desktop." Do that once and it usually sticks. Usually.

Also, the microphone has a physical privacy switch on the left speaker boom. If the mic is dead, that switch is the first thing to check. It has personally embarrassed me, so it's near the top of this list for a reason.

Step 5: The SteamVR Performance Test Is Not Optional

For a rush deployment, skipping this is how you end up with a stuttering demo. Open the SteamVR video settings and watch the frame timing graph. If you see red spikes at the default render resolution, drop the render scale. The Reverb G2's native 2160x2160 per eye is excellent, but a demo that runs smoothly at 80% scale is worth ten that hit 100% and stutter. In our B2B demo experience, most users don't notice 80%. They absolutely notice reprojection ghosting.

Motion smoothing is a per-app decision. Some titles look fine with it; others get that rubbery warping effect. The per-app settings in SteamVR exist for a reason — use them.

Checkpoint: Load the exact app you'll demo, not SteamVR Home. Play it for three full minutes, including loading screens and at least one scene transition. That's enough time for the jank to surface.

Step 6: Clean the Foam and Lenses Before the Client Arrives

This is the maintenance item that makes me sound like a dad, but after running shared headsets at events, I'm fine with that. The face foam is the first thing that grosses out a new user and the last thing anyone thinks to clean.

The G2's face cushion is magnetic and comes off with a firm, gentle pull. If the headset has heavy usage history — think that Jynxzi-style single-spot headset dent from months of one person's constant wear — the foam is already compressed and needs replacing. Hygiene is the bigger issue, though.

Here's what actually works for how to clean VR headset foam:

• Remove the face cushion from the headset.
• Hand-wash with mild soap and warm water. Not hot. Dish soap works fine.
• Squeeze, don't wring. Wringing tears the foam backing.
• Air dry fully. That takes four to six hours, which is why this gets done the night before, not the morning of.

The lenses get a dry microfiber cloth. For stubborn spots, put one drop of lens cleaner on the cloth — never directly on the lens. A lot of online advice recommends alcohol wipes for cleaning VR headset foam and lenses, but alcohol can damage the lens coating over time. That's consistent with HP's guidance, and I'm inclined to follow it given how expensive replacement lenses are. I'm not an optics specialist, so I can't speak to the exact coating chemistry. I just know that scratched G2 lenses are a costly replacement.

While you're at it, check the lenses for existing scratches. These lenses are impressively easy to scratch with a zipper or watch strap in storage. A lens cover costs less than the replacement. Buy it.

Step 7: Run the Full Demo Loop Twice

Here's the step everyone skips when time is short, which is exactly when it matters. Run the complete sequence end-to-end: headset on → WMR Portal loads → SteamVR loads → the actual app launches → audio is correct → mic works → controllers track → boundary is safe. Then take the headset off, put it back on, and do it again.

The second run catches the failures that only appear on relaunch: apps that crash the second time, save files that corrupt, cloud syncs that hang. If your demo uses a flatscreen title with a community VR mod — Ready or Not has one, for instance — the double loop matters even more, because modded titles are less forgiving about state. In our incident logs, the most common demo failure isn't hardware. It's an app that worked on the first launch and died on the third.

Common Mistakes in the Field

If you have five minutes left, these are the compressed lessons:

1. Reinstalling SteamVR when the issue is WMR. The "uninstall and reinstall" advice is a classic oversimplification. Check the WMR Portal first.
2. Setting the boundary too tight to the walls. A controller that clips through the boundary is a broken demo. Set it a foot inward from any wall.
3. Skipping foam hygiene for multi-user sessions. If several people will wear the headset in sequence, hand each one a fresh wipe. Small gesture, but enterprise clients notice it.
4. Ignoring the mic privacy switch. Small, on the boom, and almost invisible when you're in a hurry.
5. Assuming the included cable reaches for room-scale. It's six meters, which is enough for most spaces — but test the reach with the boundary in its final position before the user puts the headset on.

One more thing: the "always use the SteamVR beta" advice is fine if you develop content. For client demos, the stable branch is better. The beta is where features break, and features break at the worst possible moment.

Switching from our old ad-hoc approach to this checklist cut our average deployment time from about 45 minutes to under 15, and it reduced on-site failures noticeably. That's the real point of a checklist: it converts tribal knowledge into a repeatable sequence. When a client is watching, repeatable is everything.

Product specifications and availability as of January 2025. Verify current requirements at hp.com and Steam support, as details may have changed.