Search This Blog

Sunday, January 6, 2013

Error Message “Video Remoting Was Disconnected” When VM Connect to a Virtual Machine



Several virtual machine are running on a Hyper-V Machine but then when you try to remote into a VM using Hyper-V Manager or Failover Cluster Manager snap-in but was not able to connect to the VM. The error message that you received was

“Video Remoting Was Disconnected”.

Few things that you’ve try:-

a) Turn off VM and boot up that VM

b) RDP to VM and can access

But each time when try console using Hyper-V Manager snap-in, you will receive “Video Remoting Was Disconnected”. Plan to restart the entire Hyper-V Host, but cannot as i got a lot of Production virtual machine which is running.


Therefore this is one of the trick that i have tried

1. Go to physical NIC and disable

a) TCP Connection Offload (Ipv4 /ipv6)

b) TCP/UDP Checksum Offload (Ipv4 / ipv6)


Then i try again and was able to connect to the VM without any problem. So give it a try and this solution probably will fix your issue.


  1. I experienced the same issue, however the physical NIC did not support the offload functions described above.

    In my case, restarting Hyper-v manager was sufficient to resolve the issue, which may have been because there were two users logged onto the Hyper-v server, and the second had connected to the VM, ignoring the message about another user already being connected. The first user was the one experiencing the issue.

  2. I experienced the same symptoms but this approach didn't help solve the problem. In my case, the "Broadcom Advanced Control Suite 3" application couldn't even run until I first installed .NET framework 2.0. That in itself is fairly ridiculous, and how you have to install it on Server 2012 is unsurprisingly quite different from prior versions of windows -- you can't just download it and run it, but instead have to go through Server Manager to add the new feature, which it turns out is already in the C:\Windows\WinSxS directory (and you have to point it there as the source). Finally, when I get that BACS3 app running, I don't have the general TCP Connection Offload to disable. I did have the TCP/UDP Checksum Offload switches, which I turned off. No help. And then there were also "Large Send Offload" switches, which I turned off, and again it didn't help.

    It's all fairly nuts. There certainly is no other user logged in by RDP, and there couldn't be as soon as Windows finishes booting (which is when it tells me that it was disconnected due to another user being logged in via RDP). But in my case the issue is coming from RemoteFX (where the hyper-v host's GPU capabilities from a video card can be doled out to the guest VM's). When I had first added the RemoteFX adapter, it worked fine. But the client VM (Windows 7) noticed something new (probably the graphics stuff) and automatically added a new driver for it. Upon reboot, it has not worked since. So something is amiss in there somewhere.

    In the meantime, I've tried removing the RemoteFX graphics adapter from the VM settings, and then it seems to work just fine again. But I really want to be able to use the GPU from the VM. Problem still not resolved.

  3. Thanks, solved my problems with "Video Remoting Was Disconnected"

  4. This blog is so nice to me. I will continue to come here again and again. Visit my link as well. Good luck
    obat aborsi
    cara menggugurkan kandungan

  5. Excellent and very exciting site. Love to watch. Keep Rocking. film norwich

  6. Celebrities prefer to purchase twitter followers as a strategy to increase status in a small span. buy permanent twitter followers

  7. Mine was because the VM (Server 2016) was still working on applying that ridiculous "Cumulative Update" That thing takes forever. But once it finishes applying the updates during the shutdown and restart, everything goes back to normal.

    1. This is really not acceptable... Yes, when a machine is rebooting, I cannot view / interact with the VM-- uh, you're a hypervisor, you are supposed to allow me to access a VM as if it were a physical workstation, without excuse, at all stages, including shutdown, and boot. Hyper-V frustrates me sometimes. This type of thing never occurs with VMWare, which I'm beginning to respect more and more.


Note: Only a member of this blog may post a comment.