VMware vSphere 8.0 Update 3 | 25 JUN 2024

VMware Host Client 2.18.0 | 25 JUN 2024 | Build 23595382

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

VMware Host Client Overview

The VMware Host Client is an HTML5-based client that is used to connect to and manage single ESXi hosts. It can be used to perform administrative tasks to manage host resources such as virtual machines, networking, and storage. The VMware Host Client can also be helpful for troubleshooting individual virtual machines or hosts if vCenter Server and the vSphere Client are unavailable.

For more information, see the vSphere 8.0 Update 2 Documentation.

Previous Releases

  • VMware Host Client 2.14.0

  • VMware Host Client 2.12.0

  • VMware Host Client 2.5.0

  • VMware Host Client 1.37.0

  • VMware Host Client 1.34.8

  • VMware Host Client 1.34.4

  • VMware Host Client 1.34.0

  • VMware Host Client 1.33.3

  • VMware Host Client 1.30.0

  • VMware Host Client 1.25.0

  • VMware Host Client 1.21

  • VMware Host Client 1.8

  • VMware Host Client 1.4

  • VMware Host Client 1.2

  • VMware Host Client 1.0

Product Support Notice

Beginning with the next major release, we will be reducing the number of supported localization languages. The three supported languages will be:

  • Japanese

  • Spanish

  • French

The following languages will no longer be supported:

  • Italian, German, Brazilian, Portuguese, Traditional Chinese, Korean, Simplified Chinese


  • Users who have been using the deprecated languages will no longer receive updates or support in these languages.

  • All user interfaces, help documentation, and customer support will be available only in English or in the three supported languages mentioned above.

Resolved Issues

  • You can select the guest operating system type that has supportedForCreate=0

    Hardware version 18 now includes the following guest operating systems that were not previously available in the list of options in the New Virtual Machine wizard.

    • Amazon Linux 3 (64-bit)

    • Apple macOS 10.17

    • Asianux 9 (64-bit)

    • CentOS 9 (64-bit)

    • Microsoft Windows Server 2021

    • Oracle Linux 9 (64-bit)

    • Red Hat Enterprise Linux 9 (64-bit)

    • SUSE Linux Enterprise 16 (64-bit)

    This issue is resolved in this release.

Known Issues from Previous Releases

  • The names of future Windows OS releases appear with placeholders or code names

    Because the official names of the future Windows OS releases Windows 12 and Windows 2025 are still unknown when you create a virtual machine, you might see placeholders or code names on the Select a name and guest OS page of the New virtual machine wizard.

    Workaround: None

  • The vendor's name of some local storage devices displays incorrect or incomplete

    In the VMware Host Client inventory, when you navigate to Storage > Devices, in the Vendor column of the table, you might see part of the device model name instead of the vendor's name.

    Workaround: None

  • You cannot customize the firewall rule configuration with the option 'Only allow connections from the following networks' on ESXi hosts

    Starting with vSphere 8.0 Update 2, you cannot customize the firewall rule configuration with the option Only allow connections from the following networks on ESXi hosts.

    Perform the following steps.

    1. Navigate to Networking > Firewall rules, and select DHCP client.

    2. Click Edit settings.

    3. Select Only allow connections from the following networks and enter an IP address.

    When you click OK, the operation fails with an error such as Operation failed, diagnostics report: Invalid operation requested: Can not change allowed ip list this ruleset, it is owned by system service.

    This is expected behavior.

    Workaround: None

  • You might not change the Load balancing setting of NIC teaming

    The Load balancing setting of NIC teaming might not change when you select the Inherit from vSwitch option.

    Perform the following steps to reproduce the issue:

    1. Open Google Chrome and log in to the VMware Host Client.

    2. Click Networking in the VMware Host Client inventory and click Management Network.

    3. Click Edit settings.

      Result: The Edit port group - Management Network window appears.

    4. Expand NIC teaming.

      1. From the Load balancing drop-down menu, select Inherit from vSwitch and click Save.

    5. Complete steps 1-4.

    6. The Load balancing option remains unchanged.


    Override the Policy with the same settings as vSwitch, without using Inherit from vSwitch.

    Do not edit configstore.

  • When you create a VM through the vSphere Client and the VMware Host Client, the maximum number of cores per socket might be different for the same guest OS

    When you create a virtual machine for the same guest operating system through the vSphere Client and the VMware Host Client, the CPU Cores per Socket drop-down menu might display different numbers.

    Use vSphere Client because the VMware Host Client is in maintenance mode.

  • The Current reading parameter of the Fan Redundancy health sensor displays Redundancy lost

    Although the system fan health sensor is in green status, the Current reading parameter displays Redundancy lost. When you run the ESXCLI command esxcli hardware ipmi sdr list, the Computed reading returns a Fully Redundant value. As both Current reading and Computed reading parameters are the same, the Redundancy lost value is false.

    Perform the following steps to reproduce this issue:

    1. Install an ESXi 8.0 guest operating system.

    2. Log in to the VMware Host Client.

    3. Click Monitor in the VMware Host Client inventory.

    4. On the Hardware tab, click System sensors.

    5. Search for Fan sensors.   

      Result: Current reading column for System Board 1 Fan Redundancy 0 displays Redundancy lost.

    Workaround: None

check-circle-line exclamation-circle-line close-line
Scroll to top icon