Support Request: HP Reverb G2 - Windows 11 Compatibility & Browser VR Display Issue

[dswainston]

Subject: Support Request: HP Reverb G2 - Windows 11 Compatibility & Browser VR Display Issue

Device: HP Reverb G2 (Original Purchase Price: ~$1,000) Operating System: Windows 11

Issue Description: Since upgrading to Windows 11, my HP Reverb G2 headset has experienced severe connection and display issues. I recently went through an extensive troubleshooting session to resolve a black screen/display startup failure. While the core display is now functioning in SteamVR, web-based VR playback is still failing.

Troubleshooting Steps Already Completed:

1. Platform Migration: Confirmed that the native Windows Mixed Reality portal was failing on Windows 11. I transitioned to running the headset through SteamVR with Oasis installed.

2. Connection Reset: SteamVR initially detected the headset but failed to open the display. I performed a full physical reset (unplugged power, USB, and DisplayPort for 30 seconds, then reconnected to a USB 3.0 port and directly to the GPU).

3. Software Repair: I ran the Oasis headset repair setup tool, which successfully cleared the startup display error.

4. Current Status: The headset now successfully boots into SteamVR Home, and the headset/controllers are active and tracking.

Remaining Issue: While SteamVR Home works, WebXR/browser-based VR is failing. When attempting to play VR video content through Google Chrome (specifically seeing references to Chrome 153), the headset fails to launch into immersive VR mode. Instead, it either throws an error or only displays a flat 2D browser window inside the headset.

I would like assistance resolving this final browser integration issue, or exploring warranty/replacement options if this is a known hardware/firmware compatibility issue with Windows 11.

[VikramTheGreat]

Hi @dswainston,

Welcome to the HP Support Community.
 

Thank you for the detailed update. It is good to know that the Reverb G2 now starts correctly in SteamVR Home and the controllers are tracking.

Since the remaining problem is only with browser/WebXR content, I would first like to confirm the Windows version, as this is important for the Reverb G2. HP confirms that the Reverb G2 requires Windows Mixed Reality, and Windows 11 24H2 removed Windows Mixed Reality. HP currently recommends remaining on Windows 11 23H2 or earlier for these headsets.

Please check:

1. Press Windows + R, type winver, and press Enter.
2. Reply with the Windows 11 version and OS build shown there.
3. Also provide the exact Chrome version from chrome://settings/help and the website where WebXR fails.

Once we have those details, we can determine whether the browser issue is related to the Windows Mixed Reality compatibility rather than a hardware fault.

At this point, I would not recommend replacing the headset, since SteamVR Home and tracking are working normally.

Take care and have an amazing day!

[dswainston]

These were the versions recorded during troubleshooting on 27 September:

• Windows 11 25H2, OS build 26200.9550

• Chrome 153.0.8010.53

• SteamVR 2.17.10

• Oasis Driver 1.0.3

I’m using Oasis to run the Reverb G2 on this Windows version. SteamVR Home works, and the official Khronos Hello XR test using DirectX 11 successfully displays coloured cubes inside the headset.

The browser problem also occurs with this neutral WebXR sample:
https://immersive-web.github.io/webxr-samples/immersive-vr-session.html

Entering VR leaves a floating “Google Chrome 153 — Next Up” card. Edge 153 produces the same result. Chrome hardware acceleration is enabled and its GPU diagnostics confirm the RTX 3080 Ti is active.

Given that native OpenXR rendering works, what browser-specific diagnostics would you recommend?

[VikramTheGreat]

Hi @dswainston,

Thank you for providing the detailed test results. The HP Reverb G2 starts in SteamVR Home, the controllers track correctly, and the Khronos Hello XR DirectX 11 test renders successfully. These results indicate that the headset display, tracking, GPU connection, and native OpenXR rendering path are working.

The remaining issue is limited to browser-based WebXR. The “Google Chrome 153 — Next Up” card suggests that SteamVR sees the browser launch request, but the immersive WebXR session does not complete.

Windows 11 compatibility
The computer is running Windows 11 25H2, OS build 26200.9550. Microsoft removed Windows Mixed Reality beginning with Windows 11 24H2. The HP Reverb G2 was designed to operate through Windows Mixed Reality, and HP does not provide an official replacement for the removed Windows Mixed Reality components on Windows 11 24H2 or 25H2.

Oasis allows the headset to operate with SteamVR in the current configuration, but Oasis is not HP software and is not an HP-supported replacement for Windows Mixed Reality. Therefore, HP cannot confirm WebXR compatibility between Oasis, SteamVR, Chrome, Edge, and Windows 11 25H2.

What the tests confirm
The results show that:

• SteamVR Home displays correctly.
• Headset and controller tracking are working.
• Native OpenXR rendering works with DirectX 11.
• Chrome and Edge produce the same WebXR behavior.
• The neutral Immersive Web WebXR sample does not enter immersive mode.
• The issue is specific to the browser-to-OpenXR/SteamVR connection.

This does not currently indicate a headset hardware or firmware failure. Replacing the HP Reverb G2 would not be expected to correct a browser-runtime integration issue.

Recommended checks

1. Confirm in SteamVR that SteamVR is set as the current OpenXR runtime.
2. Run the WebXR sample again with SteamVR already open and the headset active.
3. Check the SteamVR developer or system report for an OpenXR or application-launch error generated when Enter VR is selected.
4. Report the issue to the Oasis developer with the following details:  
   • Windows 11 25H2, build 26200.9550
   • SteamVR 2.17.10
   • Oasis Driver 1.0.3
   • Chrome 153.0.8010.53
   • Edge 153
   • Native Khronos OpenXR test works
   • Browser WebXR remains on the “Next Up” screen

Next step: Because Windows Mixed Reality is unavailable on Windows 11 25H2 and the remaining failure involves Oasis and browser WebXR integration, further browser-specific investigation needs to be handled through the Oasis, SteamVR, or browser support channels.

Based on the successful SteamVR and native OpenXR tests, a warranty replacement is not recommended for this symptom.

Take care and have an amazing day!