1 person found this helpful
It's a known issue. After a few minutes, the remote control will become not responding.
A workaround is that close the VM window, then select another VM in library, wait about 6 seconds, open that VM again. Hope it can work to you.
Hi thanks for the workaround, it works.
I'm facing same issue, I guess it's linked to Catalina upgrade.
Anyone has info about a fix?
I also faced with this issue.
The workaround works! thanks
Essentially the same for me. Fusion to a remote VM on a vCenter and ESXi (all current versions and patches). After some tens of minutes without any of my activity on that remote screen, it freezes. The remote VM (win10) doesn't have a screen saver and all power save is off. I'm working continuously on the local so no screen saver or power pauses.
I right-click the VCSA object in the Fusion console, Disconnect then I'm able to re-Connect and continue right along. When the remote is frozen, my local Win VM has also frozen. Most of Fusion is frozen in fact but I can still do this disconnect/connect. Once the connection is working to the remote again, the local also is also working again.
All since Catalina, no issues before. Today's Fusion update did not resolve (11.5.1 15018442).
This is just scandalous and vmware do nothing about this !
Very disappointed !
I've also been waiting for VMWare to fix this. Since I updated to Catalina, Fusion 11.5 connections to VMs on ESXi servers will freeze after a variable amount of time. It can time-out after only a minute or rarely after a few hours but more commonly after around 30 minutes. Disconnecting and re-connecting to the ESXi server is insufficient to unfreeze. So is refreshing. The only thing that works is quitting Fusion, restarting it, reconnecting to the ESXi server and re-opening the VMs. I'm now doing this up to a dozen times a day so it's a major PITA.
I don't pay for Fusion to spend my time quitting and relaunching it to kludge around their bugs so I'll be opening a case with support to find out what they say.
If I find out anything, I'll update the thread.
I have support request 19073076410 open for this issue. I'd recommend anyone else having this problem reference the same support request so we can get some movement.
Please add me to the list of those that are plagued by this frustrating defect.
Just an FYI, but I've had the team investigate this. First I've seen it, but I've been away from the forums for a little bit.
It seems I don't connect to my remote hosts for very long, so I've never hit the issue.
In any case, just wanted to let folks know that we're working on it.
Our sincere apologies for the experience.