The VMRC Console Has Disconnected. Attempting To Reconnect. Failed To Open Console – VMware vSphere Client, Windows 8

When you try to open a console window to a VM from a VMware vSphere Client running on Windows 8, you may find that you just get a black / blank screen with the following error:

The VMRC console has disconnected… attempting to reconnect.

There is hearsay on the internet that the open console aspect of the vSphere client relies on APIs in Internet Explorer that are no longer available in IE 10 (which ships with Windows 8). Unfortunately, at this point in time there is no fix for this issue. The VMware vSphere Client is just not compatible with Windows 8 at this time. A workaround is to install a Hyper V VM running a previous operating system, such as Windows 7 and run the vSphere Client on that VM instead.

Adendum: The VMRC Console Has Disconnected issue has now been fixed with the latest version of the vSphere client (free download from VMware) 🙂

Thanks to a comment from sticks221, who highlights that the VMRC console has disconnected error can be fixed by uninstalling Internet Explorer 10, if you are using a version of windows prior to Windows 8 😉

Thanks also to Tsumu, who pointed out that the VMRC console disconnected issue can also be caused by your anti-virus blocking the IE plugin 😮

VN:F [1.9.22_1171]
Rating: 9.4/10 (8 votes cast)
The VMRC Console Has Disconnected. Attempting To Reconnect. Failed To Open Console - VMware vSphere Client, Windows 8, 9.4 out of 10 based on 8 ratings

14 thoughts on “The VMRC Console Has Disconnected. Attempting To Reconnect. Failed To Open Console – VMware vSphere Client, Windows 8

    • Yes, you can install vSphere into a previous version of Windows inside a Hyper-V VM running on the Windows 8 computer… As you say, not really a solution, more of a workaround.

      VN:F [1.9.22_1171]
      Rating: 0 (from 0 votes)
  1. Hey guys,
    just update your vSphere client to the latest version 5.1.0.2083 and it should work better 😉
    Dom

    VA:F [1.9.22_1171]
    Rating: 0 (from 0 votes)
    • Good to know VMware have finally released a vSphere client update to fix the VMRC console has disconnected error!

      Thanks Dom.

      VN:F [1.9.22_1171]
      Rating: 0 (from 0 votes)
  2. Hi all, I have no problem with version 5.0 of vsphere end with any client, 5.0 or 5.1, only 5.1 with a client 5.1.

    is this?

    VA:F [1.9.22_1171]
    Rating: 0 (from 0 votes)
  3. Thank you so much for this tip! – been driving me mad for weeks, reinstalled coutless versions if vSphere client countless times, eventually on the verge of a PC rebuild but thanks to this post it really was as simple as uninstalling IE10.

    Thanks again!

    VA:F [1.9.22_1171]
    Rating: +1 (from 1 vote)
    • No probs, strange that the new version of the vSphere Client didn’t fix the VMRC console has disconnected… attempting to reconnect error… Glad that this gave you the info required to fix the issue though 😀

      VN:F [1.9.22_1171]
      Rating: 0 (from 0 votes)
  4. Hi, all

    I updated esxi from 4.0 to 5.1u1 and installed 5.1 vsphere client (latest 5.1.0-1064113) on a windows XP client machine, so no IE10. I keep getting the VMRC console has disconnected… attempting to reconnect error. Any clues?

    VA:F [1.9.22_1171]
    Rating: 0 (from 0 votes)
  5. Solved.

    I may have rushed for help, sorry about that.
    Anyway AV Sophos was blocking the IE plugin for VMRC.
    After that all fine.

    Hope it helps

    VA:F [1.9.22_1171]
    Rating: 0 (from 0 votes)
    • Thanks Tsumu, Sorry for the late reply. Doubt I would have picked that one out, but useful for anyone else searching with the same issue 🙂

      VN:F [1.9.22_1171]
      Rating: 0 (from 0 votes)
  6. On Windows 8 •VMware vSphere Client v5.0 Update 2 : VMware-viclient-all-5.0.0-913577 works perfectly.

    No need to remove the IE10

    VA:F [1.9.22_1171]
    Rating: 0 (from 0 votes)
    • I know the 5.1 Clients work but for those who are still on ESX 5.0 they cannot use the 5.1 clients. Use the •VMware vSphere Client v5.0 Update 2 : VMware-viclient-all-5.0.0-913577 to resolve the issue.

      VA:F [1.9.22_1171]
      Rating: 0 (from 0 votes)
  7. Did try the new client, didn’t work for me. Ended up having to open taskmgr.exe and kill the vmware-vmrc.exe processes (after existing out of client first). Then starting vsphere client and it worked.

    Cheers!

    VA:F [1.9.22_1171]
    Rating: 0 (from 0 votes)

Leave a comment

Your email address will not be published. Required fields are marked *