HP reverb (G1) not recognized any more

[Ashnak]

Hi all,
has anyone seen the following issue and might have some ideas on how to further narrow down the oreven solve it?

HP reverb (original/G1)
Ryzen 9 5900 on an Asus ROG MB
32 GB RAM
AMD Radeon 6900 XT, latest drivers (23.10.01)
Windows 10

Headset worked for years. Since maybe one or two weeks ago, it's not recognized any more by the WMR software, which also means it's not recognized by SteamVR. Headset is also not present in Windows Device Manager. So far, looks like any ordinary hardware issue, right? Which means I'd effectively need to buy a new headset - my experience with HP customer service for spares/replacement parts was a bit underwhelming in the past.
But: if I uninstall WMR and reinstall again, the installer recognized my headset (correctly, as HP reverb) and proceeded with the setup and calibration. I skipped the room scale calibration (don't need it for ED). Once the setup was done and Windows switched back to the regular WMR app, the headset was gone, too.
What I found so far was the suggestion that, for the G2, you should manually inastall the drivers via Device Manager. Would have tried (in the vague hope that the drivers would be backwards compatible) - but as the headset doesn't even exist in the device manager, that also doesn't work.

So, anybody experienced something similar, or has any other interesting ideas before I need to decide between a new headset or a 55" fire TV?

 

[dexatron]

Could it be in the Cables? Not sure how could test that.

 

[Helmut Grokenberger]

The part where it gets detected after a WMR reinstall is weird. Does the G1 have the same plug as the G2? My G2 had a damaged connector earlier this year that resulted in the headset not being detected anymore. HP doesn't repair headsets at all, but they would happily sell me a new one. I was lucky as it was still under extended warranty from the seller.

So yeah, might be the connector, it is a mechanical weak point.

 

[Kissamies]

On G2 the problem is very often the cable. Dunno if it applies to G1. I had an issue a couple of months ago with my G2 that got solved by rolling back the Windows Hololens driver by one. I don't know why that worked, but it did. My cable is a little sus as well, but still works well enough.

 

[Ashnak]

Usually, the hardware (including cable) test would involve plugging the thing into a different PC. But the recognition after reinstalling the driver did put me off that track.I'll try to repeat that experiment next, since it isn't too time consuming. This time by checking the hololens driver, if the headset becomes visible in the device manager.