VirtualHere stops working after Win11 PC resumes from long Sleep State

Hi Support,

This is new problem for me that I encountered recently; not sure if there was some random Windows Update or Driver update that somehow broke my VirtualHere Setup.  But I realized recently if my computer goes to sleep now and then once it wakes up; the VirtualHere service stops works.  My workaround is that I can reboot my Win11 computer and then VirtualHere works again.  Sometimes I can ipconfig /release and ipconfig /renew and that sometimes can fix it.... but not always.   

Host setup (VirtualHere Client 5.9.3):
U9-285K, asus Z890 via Ethernet i226-V (I've also tried disabling "allow the computer to turn off device to save power"... but the problem remains)
Nvidia 5080
Win11 24H2

Android (VirtualHere Server):
Nvidia shield pro with latest patches as of today
I believe I'm on the latest VirtualHere Server Version
Connect various videogame controllers (8bitdo ultimate and Xbox Series X controllers via TPlink BT 5.0 adapter)

I can look at the Windows Event Viewer and I see numerous "incorrect function" logs, the details will say things like "Could not connect to 192.168.50.85:7575".  Not sure what's going on.  

Posted an Export of Window Event Viewer here:  https://drive.google.com/file/d/1fNzMmQXi5IvA7V2m582EPeVspGaGZX4K/view?…

Hoping you're familiar and help give clues to solve this.  
Thanks!  

#2

Thanks for the log.

Yes for the service, the logging is done in the "Details" tab in Event Viewer not in the General tab.

I don't think the virtualhere service is crashing. Does it show VirtualHere USB Sharing service is Running in Windows  Service Manager? Under Windows Logs -> Application does its show a error mark saying vhui64.exe has Crashed or something similar in there?

I just keeps repeating "Could not connect to 192.168.50.85:7575" as you said. Can you ping that IP when virtualhere is complaining?

My feeling is that the network just hasnt recovered properly and so virtualhere client just keeps trying to connect to that IP

#3

I may have found the culprit, Surfshark.  I'm not sure what exactly happened but I think there's something amiss with whatever new update came out.  If I deactivate Surshark/VPN, then VirtualHere works again.  I didn't realize earlier, but it seems like when it was in a state where VirtualHere wouldn't connect, I couldn't even ping local network devices (the Nvidia Shield, Router, etc.).   

I added some local IP addresses to the VPN Surfshark Bypass and it seems to kinda/sorta work now.  The one thing that seems to be broken is Plex server on my Win11 Desktop; if Surfshark is on, then Nvidia Shield can't seem to access Plex properly.  But turning off Surfshark let Plex work again properly.  What's weird is that I can still use Plex on iPhone/iPad even if Surfshark is enabled on my Win11 PC.  I tried putting Plex on the Surshark VPN App list but it seems to make no difference and Nvidia Shield Plex doesn't work properly when Surfshark VPN is enabled.  

I think some Surfshark update is busted as I've never had this problem before, so I'll deactivate Surfshark for now.