Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Determining VMware Software Version and Build Number (392)

Details

How do I determine what version of a VMware product I'm running?

Solution

VMware products use unique build numbers for each product release.

Depending on which VMware product you are running, there are several ways to determine the version information.

From the menu

Choose Help > About if you are using any of these applications:
  • ACE
  • GSX Server for Windows
  • Remote Console for Windows
  • VirtualCenter Client
  • Virtual Machine Console for Windows
  • Workstation for Windows
  • Player for Windows

In the ESXi/ESX 4.x and ESXi 5.x Service Console

Determine the build number and the latest update applied by running the command:

vmware -vl

For more information, see:

In the ESX Server 3.5 Service Console

Get summary information about the base build number and subsequently installed patches by typing esxupdate query at the command line. For more information on determining detailed build number information for ESX Server hosts, see Determining detailed build number version information for VMware ESX 3.0.x and 3.5.x hosts (1001179).

From the command line

Get the information by typing vmware -v at a command prompt in the host operating system while running any of these:
  • GSX Server for Windows
  • GSX Server for Linux
  • Workstation for Windows
  • Workstation for Linux

    Note: On Windows systems, include the full path to vmware.exe. For example, type (including the quotes):
    "c:\Program Files\VMware\VMware Workstation\vmware" -v

Using the Management Interface

If you are using ESX Server or GSX Server, log onto the Management Interface. After you successfully log on, the product version information appears in the upper left corner of the page.

Using the vSphere Client

If you are using ESX/ESX:
  1. Log in to the vSphere Client.
  2. Go to the Summary tab. The product version displays at the top of the page.

For P2V Assistant

To determine the version of P2V Assistant you have installed, start P2V Assistant and click Version and License Info.

For vCenter Server

To identify which version of vCenter Server you are running, type (including the quotes):

"C:\Program Files\VMware\Infrastructure\VirtualCenter Server\vpxd.exe" -v

Note: The path shown above is the default. Adjust it to suit your particular installation.

For VMware Tools

VMware Tools releases also have build numbers. To identify the build number of the VMware Tools release:
  • When running VMware Tools in a Windows virtual machine, right-click the VMware Tools icon (generally in the system tray at the end of the taskbar), click Open VMware Tools and select About.

  • When running VMware Tools in a Linux or FreeBSD virtual machine, start vmware-toolbox in X-windows and choose Help > About. If X-windows is unavailable, use this command from a console prompt:

    vmware-toolbox --version

  • To check the version of VMware Tools in a NetWare virtual machine:
    • In X-windows, click Novell > Settings > VMware Tools for NetWare, then click the VMware Tools tab.
    • At a console prompt, type:

      vmwtool version

Additional Information

For more information, see Correlating vCenter Server and ESXi/ESX host build numbers to update levels (1014508).

For translated versions of this article, see:
 

Tags

determine-version-build

Keywords

392; version; release; patch; upgrade; update; install; CD; tar; support; request; SR

Update History

05/27/2011 - Added instructions to find the product version using vSphere Client. 10/24/2013 - Added command for ESXi/ESX 4.x and ESXi 5.x.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 26 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 26 Ratings
Actions
KB: