Windows 10 Pro
Quest Pro
ALVR 20.14.1 (latest stable)
Steam Client Build 1780705203 (June 5, 2026)
SteamVR current stable branch
Issue:
After a recent Steam client update, steam.exe appears to load driver_alvr_server.dll before SteamVR starts. When ALVR is registered as an OpenVR driver before Steam launches, Steam begins listening on ALVR's configured web port, and ALVR behaves as if SteamVR is already active.
When SteamVR is launched afterward, ALVR eventually crashes with:
Unhandled exception: C0000005
Stack trace repeatedly points to:
set_device_openvr_props
Observed behavior:
- Register ALVR driver.
- Launch Steam.
- steam.exe loads driver_alvr_server.dll.
- ALVR reports SteamVR is connected before SteamVR is actually running.
- Launch SteamVR.
- SteamVR resets/restarts.
- ALVR crashes with C0000005.
Workaround:
- Unregister ALVR driver.
- Launch Steam.
- Register ALVR driver.
- Launch SteamVR.
- Quest Pro connects normally.
Additional findings:
- Launching SteamVR directly via vrmonitor.exe works.
- SteamVR functions normally when ALVR is not registered.
- The issue appears related to steam.exe loading driver_alvr_server.dll before SteamVR startup.
- Reinstalling ALVR does not resolve the issue.
- Reinstalling Steam does not resolve the issue.
- The behavior started immediately after a Steam client update on June 5, 2026.
Windows 10 Pro
Quest Pro
ALVR 20.14.1 (latest stable)
Steam Client Build 1780705203 (June 5, 2026)
SteamVR current stable branch
Issue:
After a recent Steam client update, steam.exe appears to load driver_alvr_server.dll before SteamVR starts. When ALVR is registered as an OpenVR driver before Steam launches, Steam begins listening on ALVR's configured web port, and ALVR behaves as if SteamVR is already active.
When SteamVR is launched afterward, ALVR eventually crashes with:
Unhandled exception: C0000005
Stack trace repeatedly points to:
set_device_openvr_props
Observed behavior:
Workaround:
Additional findings: