OS Error 11, have to restart alot of times to connect properly

[dualposition]

trafficstars

Description

General Troubleshooting

• [x] I carefully followed the instructions in the README and successfully completed the setup wizard
• [x] I read the ALVR GitHub Wiki

Environment

Hardware windows 11 home ver 23H2 asus tuf gaming f15 fx506lh_fx506lh

Note: for Linux, an upload to the hw-probe database is preferred: hw-probe -all -upload

CPU: Intel(R) Core(TM) i5-10300H CPU @ 2.50GHz 2.50 GHz

GPU: I cant find it anywhere but I'm sure its some nvidia GeForce gtx shit

GPU Driver Version: where do I find tha

Audio: what

Installation

ALVR Version: the newest

ALVR Settings File: ???

SteamVR Version: also the newest

Install Type:

• [ ] Packaged (exe, deb, rpm, etc)
• [x] Portable (zip) yes
• [ ] Source

OS Name and Version (winver on Windows or grep PRETTY_NAME /etc/os-release on most Linux distributions): winver????

[dualposition]

also gestures no work

[danielkariv]

Can confirm this issue too. My system is I7 4770, RTX 3060Ti, 32gb ram, running Windows 10. The headset is Quets 3. ALVR is usually running together with ADBforward for usb connection but I also saw the problem when running wirelessly too. I notice this issue since v20.7, till recent v20.9.1 version and also in developer builds over the last few months.

I don't know what makes this issue pop up. Most of the times, I have basically open ALVR-SteamVR, open ALVR client app, get the error 11 (handshake failed), and then I am closing SteamVR and open it again, and then it should works. But it isn't 100% of the times, I have found myself having to spend like 30 mins of closing and openning, or even playing with settings just to make it finally connect. The biggest issue with it that even if you pass all of it, the moment the headset disconnect (like, if I take it off for a few minutes and come back), it usually just fails to reconnect, it shows this error again, and I could restart SteamVR to 'fix it' but it also means that whatever I run before need to reopen too, making it a long process to come back to where I was each time (which, does limits how and how much I use VR right now..).

[zmerp]

I'm having the same issue, on and off. It's too random for me to even begin to debug. @danielkariv so you say this started happening in 20.7? is this accurate? have you tried installing v20.6 now and test?

[danielkariv]

I'm having the same issue, on and off. It's too random for me to even begin to debug. @danielkariv so you say this started happening in 20.7? is this accurate? have you tried installing v20.6 now and test?

Sorry, I wasn't clear about it, no, I didn't test it on older versions than v20.7. I more of wanted to say that I notice it for long period of time, over multiple versions, but not that it necessarily started with v20.7.

[zmerp]

@danielkariv could you give a try to older versions? Using the launcher is rather easy

[The-personified-devil]

@danielkariv could you give a try to older versions? Using the launcher is rather easy

tbh maybe the opposite would help, namely trying mdns in nightly

[danielkariv]

I think I got a reliable way to make this error appear. I tried it on v20.9.1 version. When you run a game, and the headset try to reconnect (in my case, I just turn the screen off and on), it fails to do so with error 11, with PC side showing Handshake error for XXXX.client: try again This happens only with games with anti cheat! I tried it on VRChat, Contrators Showdown and Pavlov. It doesn't show this problem with games without anti cheat like, Beat Saber and Underdog. If I just close the game, it take like 10-20 seconds (probably for the anticheat to be closed) and it automatically reconnect.

The anti cheat for all those game is 'easy anti cheat'.

But I think the newer versions (nightly builds) got it fix. I tried v21.0.0-dev01+nightly.2024.07.29 and I can't get error 11 again. Reconnect is working whatever the game has anti cheat or not. There is a bug where connection is successful but the screen is black but it can be resolve by turn the headset off and on again.

I will use the nightly version more and see if it isn't just a case of 'it is working because I am looking for it'.

[zmerp]

@danielkariv from experience, I also don't seem to reproduce the bug anymore recently. Not sure what caused it. But I'm pretty sure I had error 11 also on the SteamVR home.

[dualposition]

@danielkariv from experience, I also don't seem to reproduce the bug anymore recently. Not sure what caused it. But I'm pretty sure I had error 11 also on the SteamVR home.

for me the bug still happens

[zmerp]

@cheezygt have you tried any prior version? can you find a version not affected by this error?

[dualposition]

@cheezygt have you tried any prior version? can you find a version not affected by this error?

i don't use prior versions, I started using alvr recently cuz steam link and quest link for some reason don't work, steam link says that I have to use a local network even if I'm on a local network. i feel like the issue is kinda luck based, if you're lucky it will connect first try, if you're not you have to restart steamvr for it to connect, if you're extremely unlucky it will never connect

[dualposition]

also the bug happens on phonevr too

[zmerp]

Hm. Try older versions as i told you. Remember to install matching versions for streamer and client

[unluckycord]

I tried older versions and nothing fixed this. The install APK option does absolutely nothing other than fail, regardless of what version I use, so there is no way to GET an older version on the quest. why does this app do this? The only time this app worked was before I rebooted my computer to get the VB app driver to load. could it be related to VB?

[Vixea]

Did you run vb's installer as admin?

[unluckycord]

yes, I tried deleting the driver and it made no difference lol, it seems this app has never really worked properly for a lot of users, as there are countless examples of people having the same issue, with no way to fix it, then they give up and the thread gets closed before a solution is actually found.

[zmerp]

@unluckycord do downgrade an app using adb you first need to uninstall the app manually.

Maybe we could add a uninstall command in the launcher.

[unluckycord]

@unluckycord do downgrade an app using adb you first need to uninstall the app manually.

Maybe we could add a uninstall command in the launcher.

Ah, thank you so much! When you say uninstall it first, do you mean uninstall the quest app or the desktop app? The app I have on my quest is the official ALVR app on the meta store, as side quest will only point me there anyway.

[zmerp]

@unluckycord I meant the Quest app. This is an Android/ADB limitation. they have a check that make succeed installation only if the version is greater than the current installed one.

[Timocop]

Is anyone here using VoiceMeeter by any chance? I had this issue too and i figured out that the VoiceMeeter preset is causing it. Using "Custom" and entering "VoiceMeeter Input" in sink and "VoiceMeeter Output" in source fixed the problem. I can reproduce this issue 100%

[ANBAL534]

I don't think is related to Voicemeeter, for me its happening in Windows 10 and also in Linux with Alsa/Pipewire . Same behaviour, having to restart SteamVR multiple times for the handshake error to dissapear, and if the headset goes to sleep, when reactivated, the error sometimes appear again.

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[Krutonium]

Continues happening to me.

@The-personified-devil Please re-open.

[Krutonium]

@The-personified-devil Thank you!

[Eldritch6847]

Same issue here, trying to play blade and sorcery and even after a hard restart for both my quest 2 and my pc, I still get error 11 over and over. Interesting note is I only started getting this error after updating my windows to version 23H2.

Specs are as listed: GPU: Radeon rx 7800 XT CPU: Ryzen 7 3700x RAM: 32gb 3200mHz OS: Windows 11 23H2

[dualposition]

doesnt happen for me anymore but other people have this issue still so idk ill leave this open

[dualposition]

uh devs i think you did something in 20.12.0, it started happening again, it didnt happen in 20.11.0

[zmerp]

On Windows 23H2 and enabling microphone streaming I can reproduce the same error. Im not sure the will land in v20.12.1 but it will be fixed soon

[gongfuture]

I probably found a way to solve this problem, if someone have same environment with me. I use Voicemeeter Patato, and use Automatic or Voicemeeter Aux as headset microphone in ALVR will cause this problem. I tried set them custom and it works. Set like this ↓

It may can set any devices, names can be found at ...... sorry I'm using Windows in Chinese so I don't know what are they called exactly in English, but I can show where you can find it ↓ (read from right to left)

NOTICE! If you just right click, then copy and paste it, it may not work! Just like the device shows above, it will copy the name as "VB-Audio VoiceMeeter AUX VAIO " Yes, It has a newline at end, so remember delete it.

That's all. I can use headset microphone after I did these.

~When I use, I found I can't use headset speakers :(~ OK, set like this can work in my computer

[InfiniteTerrarian]

i can confirm this is still an issue today has happened multiple times, unsure how to fix