vCenter Server 5.5 Update 3h | 20 MAR 2018 | Build 7874785

vCenter Server 5.5 Update 3h Installation Package | 20 MAR 2018 | Build 7957701 

 vCenter Server Appliance 5.5 Update 3h | 20 MAR 2018 | Build 7881688 

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

vCenter Server 5.5 Update 3h addresses issues that have been documented in the Resolved Issues section.

The update from vCenter Server 5.5 Update 3f or vCenter Server 5.5 Update 3g to vCenter Server 5.5 Update 3h affects only vCenter Server and VMware vCenter Inventory Service and you must upgrade only vCenter Server and vCenter Inventory Service components.

Earlier Releases of vCenter Server 5.5

Features and known issues of vCenter Server are described in the release notes for each release. Release notes for earlier releases of vCenter Server 5.5 are:


VMware vSphere 5.5 is available in the following languages:

  • English
  • French
  • German
  • Japanese
  • Korean
  • Simplified Chinese
  • Traditional Chinese

Compatibility and Installation

ESXi, vCenter Server, and vSphere Web Client Version Compatibility

The VMware Product Interoperability Matrix provides details about the compatibility of current and earlier versions of VMware vSphere components, including ESXi, VMware vCenter Server, the vSphere Web Client, and optional VMware products. Check the VMware Product Interoperability Matrix also for information about supported management and backup agents before you install ESXi or vCenter Server.

The vSphere Client and the vSphere Web Client are packaged on the vCenter Server ISO. You can install one or both clients by using the VMware vCenter™ Installer wizard.

vSphere Client Connections to Linked Mode Environments with vCenter Server 5.x

vCenter Server 5.5 can exist in Linked Mode only with other instances of vCenter Server 5.5.

Guest Operating System Customization Support

The Guest OS Customization Support Matrix provides details about the guest operating systems supported for customization.

Installation Notes for This Release

Read the   vSphere Installation and Setup documentation for guidance about installing and configuring vCenter Server.

Although the installations are straightforward, several subsequent configuration steps are essential. Read the following documentation:

Upgrades for This Release

For instructions about upgrading vCenter Server, see the vSphere Upgrade documentation.

For more information about the sequence in which vSphere environments need to be updated, see KB 2057795.

Open Source Components for VMware vSphere 5.5

The copyright statements and licenses applicable to the open source software components distributed in vSphere 5.5 are available at, on the Open Source tab. You can also download the source files for any GPL, LGPL, or other similar licenses that require the source code or modifications to source code to be made available for the most recent available release of vSphere.

Product Support Notices

  • vSphere Web Client.

    • Starting with vSphere 5.5 Update 2, Windows XP and Windows Vista are not supported as vSphere Client Operating System. You can find the complete list of operating system supported by vSphere Web Client in the VMware Compatibility Guide.
    • Because Linux platforms are no longer supported by Adobe Flash, vSphere Web Client is not supported on the Linux OS. Third party browsers that add support for Adobe Flash on the Linux desktop OS might continue to function.
  • VMware vCenter Server Appliance. In vSphere 5.5, the VMware vCenter Server Appliance meets high-governance compliance standards through the enforcement of the DISA Security Technical Information Guidelines (STIG). Before you deploy VMware vCenter Server Appliance, see the VMware Hardened Virtual Appliance Operations Guide for information about the new security deployment standards and to ensure successful operations.

  • vCenter Server database. vSphere 5.5 removes support for IBM DB2 as the vCenter Server database.

  • VMware Tools. Beginning with vSphere 5.5, all information about how to install and configure VMware Tools in vSphere is merged with the other vSphere documentation. For information about using VMware Tools in vSphere, see the vSphere documentation. Installing and Configuring VMware Tools is not relevant to vSphere 5.5 and later.

  • vSphere Data Protection. vSphere Data Protection 5.1 is not compatible with vSphere 5.5 because of a change in the way vSphere Web Client operates. vSphere Data Protection 5.1 users who upgrade to vSphere 5.5 must also update vSphere Data Protection to continue using vSphere Data Protection.

Resolved Issues

The resolved issues are grouped as follows.

Security Issues
  • This updated version of vCenter Server provides part of the hypervisor-assisted guest mitigation of CVE-2017-5715 for guest operating systems. For important details on this mitigation, see VMware Security Advisory VMSA-2018-0004.3.

Miscellaneous Issues
  • You are unable to place an ESXi host into an empty Enhanced vMotion Compatibility (EVC) cluster even though the host meets the requirements

    Some EVC modes now contain additional CPU features that were previously not included in the EVC requirements for hosts. To support smooth upgrade, the EVC cluster would implement the new requirements only after all the hosts in it have been upgraded to meet them. However, attempting to add a non-upgraded ESXi host to the empty EVC cluster fails.

    This issue is resolved in this release.

Known Issues

The known issues are grouped as follows.

Miscellaneous Issues
  • An EVC cluster might not show new CPU IDs such as Indirect Branch Predictor Barrier (IBPB) if you add a host in maintenance mode

    If you create an empty EVC cluster and add a host in maintenance mode, you might not see the new CPU IDs exposed by that EVC cluster. The new CPU IDs are the Indirect Branch Restricted Speculation (IBRS), Single Thread Indirect Branch Predictors (STIBP) and Indirect Branch Predictor Barrier (IBPB).

    Workaround: To work around this issue, you must not add hosts in maintenance mode to empty EVC clusters. If you had added a host in maintenance mode to an empty EVC cluster and then added another host, not in maintenance mode, you must exit the first host from maintenance mode and remove the second host. As result, the cluster will upgrade and resync with the new CPU IDs.

  • An EVC cluster might show new CPU IDs such as IBPB even if you revert an ESXi host to an older version

    When you apply the current patch to an ESXi host and add that host to an EVC cluster, if you revert the host to an older version of ESXi, the EVC cluster might still expose the new CPU IDs, such as IBRS, STIBP and IBPB. However, the ESXi host will not have any of the new CPU ID features.

    Workaround: To work around this issue, you must put the ESXi host in maintenance mode and move the host out of the EVC cluster. 

Known Issues from Earlier Releases

To view a list of previous known issues, click here.

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