VMware Cloud Community
silmor_senedlen
Contributor
Contributor

[Bug Report] VMRC 12.0.3 Build 21263813 (Win)

Good day

After updating VMRC to latest version 12.0.3 Build 21263813 (Windows) I found the following problems:

1) VMRC stop sending SNI(Server Name Indication) extension in TLS handshake. As a result, it is impossible to connect VM console (At least in my provider's Cloud Director environment).

2) VMRC don't detect that latest VMRC build already installed and again offers to upgrade to already installed version(12.0.3 Build 21263813).

2 Replies
morningrise
Contributor
Contributor

See in Regedit:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{258A5E00-21C0-421F-8999-4CB9B03A8DA8}

Although build 21263813 has been installed as a security update from version 12.0.3, it does not appear in Regedit --> There is a minor build number in Regedit.

So VMRC does not recognize the installed update and the window pops up again to install the update --> If you repair the update with the option "Repair" (this button appears from the second installation), then the window does not pop up anymore (but only for the same build number) when starting the VM via VSphere Client in Firefox.

But if a new security update appears with a new build number, then the whole thing has to be installed from scratch and then repaired again so that the pop up window for installing the security update doesn't appear for a few days (until the next build number arrives).

Note: After the first installation from 12.0.2 to 12.0.3 this version number was taken over, both in Regedit and under Programs and Features. So there is only a problem with the build number.

We are using Windows 10 22H2 machines and all of them are affected.

The workaround works, but it needs to be fixed by the vendor.

See the PDF and the other screenshots from VMRC and regedit.

Translations in the PDF:

Reparieren --> repair

Error in English: VMRC could not be updated, contact the VMware support or your system administrator.

CatMucius
Contributor
Contributor

Confirming both bugs on the same v12.0.3:

1. SNI not sent, so the SSL negotiation fails;

2. VMRC constantly prompts to update itself to the same version.

Reply
0 Kudos