HP Reverb G2, and Windows 11 22H2 error heads-up
-
@Archer
i will rollback at 22h1…but in this case i dont format or cancel nothing in my pc…correct…? i will only roll back win… -
I’m using 22H2 with a G2 without issue. There was a significant holographic shell bug when it was released that caused many VR problems but it’s been fixed. I’ve rebooted and relaunched 4.37 many times since release and not experienced any VR startup problems or performance degradation that I didn’t cause myself while fiddling with settings.
-
-
@cougar56th can confirm - have tested removing all devices and my issue seems to be with the G2 being initialised on connection/powering up. Can get into game in 2D if I have headset unplugged and fresh reboot but fails in VR and any subsequenty launches.
-
@cougar56th is it this? do the latest nvidia drivers help?
https://windowsreport.com/windows-11-22h2-nvidia-issue/ -
@JENA73 correct I just rollback windows 11 to 21h2 and it works fine
-
@airtex2019 probably. I don’t think it is something with the reverb or BMS. It is something that windows did. Question is how to fix it.
-
@JENA73 Yeah roll back should work just fine. It’s windows update that broke something not BMS or the other games.
-
-
Someone found a fix it seems:
-
@jayb said in HP Reverb G2, and Windows 11 22H2 error heads-up:
Someone found a fix it seems:
Yes, all this “Win10 is better”, “roll Win11 back to 22H1” is really not good advice. Google Holographic Shell Stop batch file (or simply go here). No idea why MS has not fixed this, but apparently they haven’t . Its a simple fix, you can run the tiny bat file each startup or set it to run automatically as a task. I run the very latest Win11 Pro, latest Nvidia drivers, 0 issues.
-
@jayb Yep fixed worked for me too. Good to go with Windows 11 22H2 now.