Client left running, server stopped... how best to get it going again

Submitted by emcee2 on #1

Hello,

I've got a mac server running and a windows 10 client installed as a service.  Sometimes when I reconnect to my remote session the VH client list isn't populated/can't connect to the server - probably because the mac went to sleep overnight or the user changed or something.

Regardless, if I select the tasktray icon for VH and right click>exit, it seems it doesn't as I often to open Windows task manager and end the task.  And then I restart the VH service.  But the tasktray icon never reappears, and the VH client list doesn't come show unless I actually run the vhui64.exe file again.

How do I get the tasktray icon to repopulate after restarting the service?

Thanks

Submitted by Michael on Fri, 2023/03/31 - 08:02

#2

That sounds like a bug in the virtualhere client actually. Can you uninstall the virtualhere client service by right clicking USB Hubs->Uninstall Service.

Then download the virtualhere client again from this website (currently version 5.4.5) and overwrite the old file on your PC. Then start the new virtualhere client and right click USB Hubs->Install Service

See if that works OK as you will be running the latest version now. If not let me know.

Submitted by emcee2 on Thu, 2023/04/06 - 03:02

#3

HI,

Sorry for taking so long to respond.  As it happens I had the current version installed and the service running, but "uninstall client service" was not available - only "install as service" (or whatever the exact wording is).
Anyway, I messed about a bit, and there have been some reboots, and it seems to be working.
Except it does seem that A) I have to restart the service again occassionally if the server has gone away for some time - i.e. that server computer has been asleep for a while and B) when I restart the service the tasktray icon does not appear unless I start the vhui64.exe file resident on my desktop.
Anyway, for now, things are working.

Thanks!

Submitted by Michael on Thu, 2023/04/06 - 07:36

#4

Ok if/when it happens again can you look in windows Event Manager and see if you can find information about a crash

 

(For example instructions see here e.g https://www.cyberlink.com/support/faq-content.do?id=10449)

Copy the text into a post here