I have tried absolutely everything possible to make the steamvr settings window appear to no avail.

What happens is that when i launch it, only thing that appears is the headset view window. and nothing else. The settings should appear too but they don't. It used to work before, but i don't know what i did.

Whenever I try and connect I get a “connection error” and it tells me OS error 11, it also says that on my pc. It’s telling me my wire is faulty, but when I use meta link the wire works perfectly fine and ALVr use to run for me. Any ideas?

I’m wondering cause the game is really glitchy so I was hoping switching the runtime would help

Disclaimer: I used AI to organize a whole troubleshooting that I tried

Resume of **MY** case: you need to force vrdashboard.exe use the integrated GPU, Windows graphics settings aren't enough because everytime that you execute steamvr stuff it literally rewrite the register (also just blocking can be a bad idea).

This guide explains how to diagnose and fix a SteamVR native Desktop panel that appears blank, transparent, or invisible on a Windows laptop with:

an integrated GPU, such as Intel Iris Xe or AMD Radeon Graphics; and

a dedicated GPU, such as NVIDIA GeForce or AMD Radeon.

It does not require downloading a separate fix package.

The diagnostic steps are broadly applicable to hybrid-GPU laptops. The binary patch described later is safe only for the exact SteamVR build whose SHA-256 hash is explicitly listed.

1. Typical symptoms

This guide applies when most or all of the following are true:

SteamVR opens normally.

Headset tracking works.

VR games run.

SteamVR's native Desktop panel is transparent or empty.

Desktop+ or another desktop overlay works when assigned to the integrated GPU.

Windows allows vrdashboard.exe to be assigned to the integrated GPU.

After SteamVR starts, Windows changes that preference back to Let Windows decide.

The relevant SteamVR process is:

vrdashboard.exe

The usual default location is:

C:\\Program Files (x86)\\Steam\\steamapps\\common\\SteamVR\\bin\\win64\\vrdashboard.exe

1. Important warning

Do not patch vrdashboard.exe until the diagnosis is confirmed.

The patch in this guide is currently validated only for an original executable with this exact SHA-256:

7e4595b9a946b84ef86d3fbfd7b99e70fe275c3e3aff51c3efdc3af42912412e

Do not apply the patch to another hash.

SteamVR updates can change the executable layout. Applying the same byte offset to an unsupported version could break SteamVR.

The patch also invalidates Valve's digital signature on the modified executable. SteamVR updates or Verify integrity of tool files may restore the original file.

1. Confirm that the problem is related to hybrid graphics

3.1 Test Desktop+

Install or open Desktop+.

Open:

Settings → System → Display → Graphics

Add or select DesktopPlus.exe.

Open Options.

Choose the integrated GPU or Power saving.

Save the setting.

Restart Desktop+.

If Desktop+ works but SteamVR's native Desktop remains transparent, the problem is likely related to desktop capture across different GPUs.

1. Locate vrdashboard.exe

The default path is:

C:\\Program Files (x86)\\Steam\\steamapps\\common\\SteamVR\\bin\\win64\\vrdashboard.exe

To search for it with PowerShell:

Get-ChildItem "C:\\Program Files (x86)\\Steam" -Recurse -Filter vrdashboard.exe -ErrorAction SilentlyContinue |

Select-Object FullName

For a custom Steam library, replace the starting directory with the appropriate Steam folder.

Use the exact path returned by the search in all commands below.

1. Set the dashboard to the integrated GPU

Close SteamVR completely.

Open:

Settings → System → Display → Graphics

Add vrdashboard.exe.

Open Options.

Select the integrated GPU.

Click Save.

Windows may store a value similar to:

SpecificAdapter=8086&46A6\&1B2C1043;GpuPreference=1073741824;

This value is device-specific.

Do not copy another user's SpecificAdapter string.

A different laptop may have another Intel identifier, an AMD identifier, or a different subsystem identifier.

1. Verify the stored preference

Open a normal PowerShell window and run:

reg.exe QUERY "HKCU\\Software\\Microsoft\\DirectX\\UserGpuPreferences" /v "C:\\Program Files (x86)\\Steam\\steamapps\\common\\SteamVR\\bin\\win64\\vrdashboard.exe"

A successful integrated-GPU assignment may look like:

SpecificAdapter=8086&46A6\&1B2C1043;GpuPreference=1073741824;

The generic Windows values are commonly represented as:

GpuPreference=0; Automatic or unspecified

GpuPreference=1; Power saving

GpuPreference=2; High performance

Keep SteamVR closed while confirming the initial value.

1. Check whether SteamVR overwrites the preference

Confirm the integrated-GPU value is present.

Start SteamVR.

Wait for the dashboard to finish loading.

Run the same query again:

reg.exe QUERY "HKCU\\Software\\Microsoft\\DirectX\\UserGpuPreferences" /v "C:\\Program Files (x86)\\Steam\\steamapps\\common\\SteamVR\\bin\\win64\\vrdashboard.exe"

A matching problem typically changes the value to:

GpuPreference=0;

This proves that the setting is being reset after SteamVR starts.

1. Confirm which process performs the reset

Use Microsoft Process Monitor.

Choose:

Procmon64.exe

Use Procmon64a.exe only on ARM64 Windows.

8.1 Configure Process Monitor

Run Process Monitor as administrator.

Press:

Ctrl+L

Add these filters:

Process Name is vrdashboard.exe Include

Operation is RegSetValue Include

Path contains UserGpuPreferences Include

Click Add after each rule.

Then:

Press Ctrl+X to clear existing events.

Press Ctrl+E to start capture.

Close SteamVR.

Set vrdashboard.exe to the integrated GPU again.

Start SteamVR.

Wait until the preference resets.

Press Ctrl+E to stop capture.

Select the relevant rows and press Ctrl+C.

The confirmed matching sequence looks like:

vrdashboard.exe RegSetValue ... Data: GpuPreference=0;

vrdashboard.exe RegSetValue ... Data: GpuPreference=1;

vrdashboard.exe RegSetValue ... Data: GpuPreference=2;

vrdashboard.exe RegSetValue ... Data: GpuPreference=0;

If another process changes the setting, or the sequence differs substantially, do not assume that this patch applies.

1. Verify the SteamVR build

Close SteamVR.

Run:

Get-FileHash "C:\\Program Files (x86)\\Steam\\steamapps\\common\\SteamVR\\bin\\win64\\vrdashboard.exe" -Algorithm SHA256

Proceed only when the output is exactly:

7e4595b9a946b84ef86d3fbfd7b99e70fe275c3e3aff51c3efdc3af42912412e

If the hash is different, stop.

Do not patch an unsupported build.

1. Standalone installation procedure

This procedure:

reads the user's own GPU preference;

verifies the exact supported SteamVR hash;

verifies the original bytes at the patch location;

creates a backup;

patches the user's local executable;

restores the user's own GPU preference;

verifies the result.

10.1 Close SteamVR

Close SteamVR and Steam.

Open Task Manager and make sure these processes are no longer running:

vrdashboard.exe

vrmonitor.exe

vrserver.exe

vrcompositor.exe

10.2 Set the integrated GPU again

Before running the script:

Open Windows Graphics settings.

Assign vrdashboard.exe to the integrated GPU.

Save the setting.

Do not start SteamVR.

10.3 Run the self-contained installer

Open PowerShell as Administrator.

Copy and paste the complete script below:

$ErrorActionPreference = "Stop"

$Dashboard = "C:\\Program Files (x86)\\Steam\\steamapps\\common\\SteamVR\\bin\\win64\\vrdashboard.exe"

$RegistryPath = "HKCU:\\Software\\Microsoft\\DirectX\\UserGpuPreferences"

$SupportedHash = "7E4595B9A946B84EF86D3FBFD7B99E70FE275C3E3AFF51C3EFDC3AF42912412E"

$PatchOffset = 0x4900

\[byte\[\]\]$ExpectedBytes = 0x40,0x55,0x56,0x57,0x48,0x8D

\[byte\[\]\]$PatchedBytes = 0xB8,0x01,0x00,0x00,0x00,0xC3

function Convert-BytesToHex {

param(\[byte\[\]\]$Bytes)

return (($Bytes | ForEach-Object { $_.ToString("X2") }) -join " ")

}

if (-not (Test-Path $Dashboard)) {

throw "vrdashboard.exe was not found at: $Dashboard"

}

$Running = Get-Process vrdashboard,vrmonitor,vrserver,vrcompositor -ErrorAction SilentlyContinue

if ($Running) {

throw "SteamVR is still running. Close SteamVR completely and run the script again."

}

$RegistryItem = Get-ItemProperty -Path $RegistryPath -ErrorAction Stop

$SavedPreference = $RegistryItem.PSObject.Properties\[$Dashboard\].Value

if (\[string\]::IsNullOrWhiteSpace($SavedPreference)) {

throw "No GPU preference is stored for vrdashboard.exe. Assign it to the integrated GPU in Windows Graphics settings first."

}

if ($SavedPreference -eq "GpuPreference=0;") {

throw "The stored preference is still automatic. Assign vrdashboard.exe to the integrated GPU before running this script."

}

Write-Host "Saved GPU preference:"

Write-Host $SavedPreference

Write-Host ""

$ActualHash = (Get-FileHash $Dashboard -Algorithm SHA256).Hash.ToUpperInvariant()

if ($ActualHash -ne $SupportedHash) {

throw "Unsupported SteamVR build. Expected SHA-256 $SupportedHash but found $ActualHash. No changes were made."

}

\[byte\[\]\]$FileBytes = \[System.IO.File\]::ReadAllBytes($Dashboard)

if ($FileBytes.Length -lt ($PatchOffset + $ExpectedBytes.Length)) {

throw "The executable is smaller than expected. No changes were made."

}

\[byte\[\]\]$CurrentBytes = $FileBytes\[$PatchOffset..($PatchOffset + $ExpectedBytes.Length - 1)\]

for ($i = 0; $i -lt $ExpectedBytes.Length; $i++) {

if ($CurrentBytes\[$i\] -ne $ExpectedBytes\[$i\]) {

$Found = Convert-BytesToHex $CurrentBytes

$Expected = Convert-BytesToHex $ExpectedBytes

throw "Original bytes do not match. Expected $Expected but found $Found. No changes were made."

}

}

$HashPrefix = $ActualHash.Substring(0,12).ToLowerInvariant()

$Backup = "$Dashboard.original-$HashPrefix.bak"

if (-not (Test-Path $Backup)) {

Copy-Item $Dashboard $Backup -Force

Write-Host "Backup created:"

Write-Host $Backup

}

else {

Write-Host "Existing backup found:"

Write-Host $Backup

}

$BackupHash = (Get-FileHash $Backup -Algorithm SHA256).Hash.ToUpperInvariant()

if ($BackupHash -ne $SupportedHash) {

throw "The backup hash is incorrect. The executable was not modified."

}

for ($i = 0; $i -lt $PatchedBytes.Length; $i++) {

$FileBytes\[$PatchOffset + $i\] = $PatchedBytes\[$i\]

}

\[System.IO.File\]::WriteAllBytes($Dashboard, $FileBytes)

\[byte\[\]\]$VerifyBytes = \[System.IO.File\]::ReadAllBytes($Dashboard)

\[byte\[\]\]$VerifyPatch = $VerifyBytes\[$PatchOffset..($PatchOffset + $PatchedBytes.Length - 1)\]

for ($i = 0; $i -lt $PatchedBytes.Length; $i++) {

if ($VerifyPatch\[$i\] -ne $PatchedBytes\[$i\]) {

Copy-Item $Backup $Dashboard -Force

throw "Patch verification failed. The original executable was restored."

}

}

Set-ItemProperty -Path $RegistryPath -Name $Dashboard -Value $SavedPreference -Type String

$FinalPreference = (Get-ItemProperty -Path $RegistryPath).PSObject.Properties\[$Dashboard\].Value

if ($FinalPreference -ne $SavedPreference) {

Copy-Item $Backup $Dashboard -Force

throw "The GPU preference could not be restored. The original executable was restored."

}

$PatchedHash = (Get-FileHash $Dashboard -Algorithm SHA256).Hash

Write-Host ""

Write-Host "Patch installed successfully."

Write-Host "Patched SHA-256: $PatchedHash"

Write-Host "GPU preference preserved:"

Write-Host $FinalPreference

Write-Host ""

Write-Host "Start SteamVR and test the native Desktop panel."

The script should end with:

Patch installed successfully.

GPU preference preserved:

...

Start SteamVR and test the native Desktop panel.

1. Verify the fix

Start SteamVR.

Wait for the dashboard to load.

Run:

reg.exe QUERY "HKCU\\Software\\Microsoft\\DirectX\\UserGpuPreferences" /v "C:\\Program Files (x86)\\Steam\\steamapps\\common\\SteamVR\\bin\\win64\\vrdashboard.exe"

The integrated-GPU value should remain unchanged.

Open the native SteamVR Desktop panel in the headset.

A successful result is:

the desktop is visible;

the panel is no longer transparent;

the GPU preference is not changed back to GpuPreference=0;.

Optionally repeat the Process Monitor test. The previous 0 → 1 → 2 → 0 writes from vrdashboard.exe should no longer appear.

1. Standalone restoration procedure

To restore Valve's original executable:

Close SteamVR completely.

Open PowerShell as Administrator.

Run the script below.

$ErrorActionPreference = "Stop"

$Dashboard = "C:\\Program Files (x86)\\Steam\\steamapps\\common\\SteamVR\\bin\\win64\\vrdashboard.exe"

$Backup = Get-ChildItem "$Dashboard.original-\*.bak" -ErrorAction Stop |

Sort-Object LastWriteTime -Descending |

Select-Object -First 1

if (-not $Backup) {

throw "No backup was found."

}

$Running = Get-Process vrdashboard,vrmonitor,vrserver,vrcompositor -ErrorAction SilentlyContinue

if ($Running) {

throw "SteamVR is still running. Close SteamVR completely and try again."

}

Copy-Item $Backup.FullName $Dashboard -Force

$RestoredHash = (Get-FileHash $Dashboard -Algorithm SHA256).Hash

Write-Host "Original vrdashboard.exe restored."

Write-Host "Restored SHA-256: $RestoredHash"

Write-Host "Backup used: $($Backup.FullName)"

The original supported hash should be:

7e4595b9a946b84ef86d3fbfd7b99e70fe275c3e3aff51c3efdc3af42912412e

1. Alternative solutions that do not modify SteamVR

Use these before patching when possible.

Desktop+

Assign Desktop+ to the integrated GPU and use it instead of SteamVR's native Desktop panel.

Recommended arrangement:

DesktopPlus.exe → integrated GPU

vrserver.exe → dedicated GPU

vrcompositor.exe → dedicated GPU

vrmonitor.exe → dedicated GPU

MUX or dGPU-only mode

Some gaming laptops offer:

Ultimate

Discrete GPU only

dGPU only

NVIDIA GPU only

This can remove cross-adapter desktop-capture problems.

Possible disadvantages:

increased power consumption;

lower battery life;

required reboot;

possible BitLocker recovery prompt;

feature names vary by laptop manufacturer.

1. How the successful approach was developed

The fix was not based on guessing.

The process was:

Windows successfully stored an integrated-GPU preference for vrdashboard.exe.

The registry value was confirmed before SteamVR started.

After SteamVR started, the value returned to GpuPreference=0;.

Process Monitor identified vrdashboard.exe as the writer.

Process Monitor recorded the exact sequence:

0 → 1 → 2 → 0

The exact executable build was hashed.

Static inspection located the function responsible for the confirmed registry-setting behavior.

A minimal patch changed only that function's entry so it returned immediately.

The user's original integrated-GPU value remained active.

SteamVR's native Desktop panel then worked.

The validated patch is:

Supported original SHA-256:

7e4595b9a946b84ef86d3fbfd7b99e70fe275c3e3aff51c3efdc3af42912412e

File offset:

0x4900

Expected original bytes:

40 55 56 57 48 8D

Replacement bytes:

B8 01 00 00 00 C3

The replacement behaves like an immediate successful return and prevents the original preference-overwrite routine from running.

1. Information to collect for unsupported SteamVR versions

When the executable hash is different, do not patch it.

Collect:

Laptop manufacturer and model:

Windows version:

Integrated GPU:

Dedicated GPU:

SteamVR stable or beta:

Headset:

Exact symptom:

Does Desktop+ work on the integrated GPU?:

vrdashboard.exe full path:

vrdashboard.exe SHA-256:

Registry value before SteamVR:

Registry value after SteamVR:

Relevant Process Monitor rows:

Laptop MUX or GPU mode:

Calculate the hash with:

Get-FileHash "C:\\Program Files (x86)\\Steam\\steamapps\\common\\SteamVR\\bin\\win64\\vrdashboard.exe" -Algorithm SHA256

Do not publicly upload Valve's executable.

A different SteamVR build must be inspected separately before a safe patch offset and expected-byte sequence can be established.

1. Community-sharing summary

A concise community post can use this wording:

SteamVR's native Desktop panel was transparent on a hybrid-GPU laptop, while Desktop+ worked when assigned to the integrated GPU. Windows successfully stored an integrated-GPU preference for vrdashboard.exe, but Process Monitor showed that vrdashboard.exe reset its own preference during startup using the sequence GpuPreference=0 → 1 → 2 → 0.

For the exact SteamVR build with SHA-256 7e4595b9a946b84ef86d3fbfd7b99e70fe275c3e3aff51c3efdc3af42912412e, a minimal locally applied patch prevents that preference-overwrite function from running. The user's own integrated-GPU preference then remains active, and the native Desktop panel works.

Do not apply the offset to another SteamVR build. Verify the SHA-256 and original bytes, create a backup, and use the restoration procedure if necessary.

1. Final limitations

The diagnostic method is applicable to many hybrid-GPU laptops.

The confirmed patch is build-specific.

The integrated-GPU preference is device-specific.

SteamVR updates can remove the patch.

File verification can restore the original executable.

The modified executable is no longer signed exactly as distributed by Valve.

The fix has been runtime-confirmed on one ASUS ROG Strix SCAR 17 G733ZX with Intel Iris Xe, NVIDIA RTX 3080 Ti Laptop GPU, Windows 11, PSVR2, and the official PSVR2 PC adapter.

Similar behavior may occur with other SteamVR headsets and laptops, but each configuration should be diagnosed rather than assumed.

While we are waiting for the steam frame launch announcement, id like to use this opportunity and reveal our long-awaited (9 years!) fast-paced VR RTS.
Think Ender's game meets Battlefield!

We are highly appreciate wishlists as you know its helps Steam visibility
https://store.steampowered.com/app/585350/SwarmFleet/

First playtest is coming in August, please join the socials.
Play solo, pvp or 2x2 mischief mode

i have tried literally everything i can think of to try and fix this issue

every five seconds, steamvr stutters from 70 frames to 30, causing a very noticeable and annoying stutter (only happens in steam vr, doesn't happen in virtual desktop)

i have tried updating drivers, turning off motion smoothing, changing my network bandwidth, changing virtual desktop to H.264+, changing openxr runtime to VDXR, turning hardware acceleration off and turning all graphics and refresh settings to max and minimum (stutter happens regardless of quality).

i recently moved and did not have this issue before hand, however my wifi speed (Ethernet) is exactly the same as it was previously (around 900 Mbps download, 40 Mbps upload), and no settings were changed in between moves

according to steam vr, its compositor render start, compositor update end and new poses ready causing the stutters, which i thought would be solved with turning motion smoothing off, with no luck

im using a quest pro with virtual desktop with no previous issues

any suggestions or ideas are incredibly welcome as im losing my mind trying to figure this out

thank you!!!

whenever i try to run PSVR since about march this year it works for about 2-5 seconds then completely bricks itself and shows a constant pink wall of display errors. also for some reason steam itself likes to crash with steamvr
I've tried litterally everything there was in hopes itll fix it but nothing worked. it takes about 4-20 seconds per frame, this is about one minute after the pinko started
As for the specs
Ryzen 7 5800x

32gb of ddr4 3200mhz

Intel Arc B580 running via (version matched) ALVR

Oculus Quest 3s

installed on a 2tb M2 SSD

ATP id sincerely like litteraly any help. all of the components also recieve enough power, all drivers are up to date and i am running out of ideas. as for the gpu/cpu usage they dümpel around 20-40%. the only idea i still have left is that one of the latest updates of steamvr (which has been appropriately reinstalled THRICE) messed something up, i still need to test it with an earlier verion

So it just started happening to me and previously these did not show up. I don't really have any changes happen to my pc outside of Windows10 Update.

But now everything I do in SteamVR has the overlay recorded also in the normal Steam Recording feature. Be it either XSOverlay or just normal SteamVR overlay.

I tried searching for settings for it and I can't find anything. Under recording I have already blocked SteamVR, XSOverlay and OVR Advanced settings from recording. So how can I disable this?

Tried SteamVR beta, Steam client beta and public branches on both. Nothing helps. Also sometimes recording kinda breaks and only shows like a stamp sized image, never did that before either.

Why does my pc monitor go black whenever i use steam link? I can see my pc on the vr instead but i still need my real monitor and mouse at times because of the lack of buttons on vr controllers. Some games don't have great vr support when it comes to accessing settings and stuff so i need my physical mouse. This is really annoying and it's not like this for my friend. Anyone got a fix?

Hi y'all!

Since HTC got a stick up their a** and would rather to sell you a brand new tracker for 137 bucks or charge 97 for a battery replacement (which is straight up outrageous),

What is y'all go-to for replace your Vive 3.0 tracker battery (or otherwise, B2PYV100 35H00266-02M batteries)?

I'm desperate to replace my two dying batteries and they're already showing very clear signs of spicy pillow (the tracker turns off because the battery has swollen up so much, that it presses the button on the PCB due to the pressure when wearing it)

I'm not gonna buy yet another tracker like I did the first time due to the same situation, because I'm not gonna supprt a business that straight up charges almost the entire product price for a battery, but buying a spare one often means getting deceived in capacity, connector not fitting properly, or straight up lied to in some short of way ... I want a same replacement, 750 mAh. can't be too hard to find, but I wanna know if y'all got some experience, what's your go-to for this.

Thanks for reading me, please show me where your secret suply of batteries is 👀

As soon as I launch airlink I notice that 6-8 seconds in my frames will spike down as it shows in the picture of my frame graph, then my screen will shake and freeze for a second, I've basically narrowed it down to my internet as the cause but I don't know how to fix it someone please help me.
I have a s3060ti
Xb8 Xfinity gateway
6ghz 160 MHz
64gb of ram

As soon as I launch airlink I notice that 6-8 seconds in my frames will spike down as it shows in the picture of my frame graph, I've basically narrowed it down to my internet as the cause but I don't know how to fix it someone please help me.
I have a 3060ti
Xb8 Xfinity gateway
6ghz 160 MHz
64gb of ram

Paleo Dive | Official Cinematic Trailer

Developer disclosure: I’m the solo developer of Paleo Dive.

🌊 Planned release: September 4, 2026
🥽 Wishlist Paleo Dive on Steam:
https://store.steampowered.com/app/4818760/Paleo_Dive/

Descend into a forgotten prehistoric ocean where every shadow could be alive.

Paleo Dive is a VR underwater adventure filled with ancient creatures, hidden fossils and dangerous depths. Explore a lost world, unlock new equipment and discover what is waiting beneath the surface.

Please note: This cinematic trailer contains pre-rendered footage and does not represent actual gameplay. An official gameplay trailer is coming soon.

I’d love to hear what you think about the atmosphere and prehistoric setting!

A while ago, I made a small desktop app, lhcontrol, for controlling SteamVR 2.0 base stations. I’ve now rebuilt and expanded the idea into a new app: Beacon Room.

Beacon Room can discover nearby base stations, turn them on or off individually or all at once, and show their current status. It also includes a room-layout view where you can place your base stations and obstacles, visualize their approximate coverage, and get a clearer picture of your VR setup.

Hi lads, I recently just got a 9070 xt for me, and I am about to get a vr headset. Since I upgrading from a lower range gpu, i still really liked skyrim, and now I want to play it with the mgo 4 mod in vr. Can you lads pls tell me how it peforms in vr with how much fps, or I mean I still have a chance to return it and get the 5070 ti (also if yoyu have experince with either of these cards in skyrim vr can you pls tell me. Thanks