Short answer: this vCenter version history lists every vCenter Server release from Broadcom KB 326316. The order is the order of the KB: line by line, newest first within a line. Each release shows its release name, version, release date and build numbers. The build numbers are the VAMI build, the MOB / vpxd.log build where it differs, and the installer build of the old releases. Each release also links to the official release notes on Broadcom TechDocs. For the 8.0, 9.0 and 9.1 releases the tool adds the What’s New, Resolved Issues and Known Issues of the release notes. So you get from a version or a build number to what changed in two keystrokes. Type a version (8.0U3k, vCenter 9.1.1.0), a release name or a build number (25600417) to identify it. Then open the table to sort and export, or pick two releases in Upgrade path to read everything that changed between them. The data comes from KB 326316 and from the vCenter release notes on Broadcom TechDocs. Releases before 7.0 have no release-notes link in the KB. The ESXi side of the same lookup is the ESXi version history with release notes.
Prefer a full window? Open the tool full screen →
How to use the vCenter version history
- Look up a release. Type what you have: a short version such as
8.0U3kor7.0 Update 3w, a release name, a KB version such as8.0.3.01000, or any build number of the KB. An exact hit is explained above the list, for example “25600417 is the build number of vCenter Server 8.0 Update 3k”. The release-notes button sits next to it. From three characters the search also looks inside the What’s New and the issue lists. - Releases. One card per release in the order of the KB, with a heading per line (vCenter 9.1, vCenter 9.0, vCenter Server 8.0 and so on). The 6.7 appliance and the 6.7 Windows tables stay apart, as in the KB. A card shows the release name and version, the builds, the date, the line and the CVEs of the notes. Below them, What’s New, Resolved Issues, Known Issues and Known Issues from previous releases are collapsible blocks. The Line chips narrow the list to one release line. Only keeps the GA releases, the releases with a notes extract or the releases with a release-notes link. Show picks the sections.
- Table. The KB rows as a sortable table: line, release name, version, date, build, other builds and release-notes link. The CSV download has the VAMI, MOB and installer builds in their own columns. The Markdown button copies the current rows. A release name opens its card.
- Upgrade path. Pick the release you run and the release you go to. Every release of the target line in between is listed with its notes open, so you read in one pass what the upgrade brings. Markdown of this range copies it for a change ticket.
- Deep links.
?version=8.0U3kor?build=25600417on this page opens the tool on that release. The Link button on a card copies such a link.
How to read the vCenter versions and build numbers
- Release name vs. version. The release name is what the release notes are called, for example vCenter Server 8.0 Update 3k. The version is the five-part number the appliance reports, for example 8.0.3.01000 (line, update, patch). vCenter 9.x releases carry a four-part number such as 9.1.1.0100, which is the name and the version at once. The 9.1 and 9.0.0.0 rows are the GA releases of VCF 9.1 and 9.0.
- Build numbers. The build is the number the vCenter Server Management Interface (VAMI) and the KB “Build Number” column show. For the 7.0 and 6.7 releases the Managed Object Browser and vpxd.log report a different build. The tool lists it as the MOB / vpxd.log build. The 6.5 and older rows add the build of the installer. All of them are searchable and work in
?build=. - Appliance and Windows. The 6.7 line has two tables in the KB: vCenter Server Appliance and vCenter Server for Windows. Both share the VAMI build but differ in the MOB build, and the Windows rows are tagged. The 6.5 and older table covers both forms. vCenter Server for Windows was removed with 7.0.
- Notes extract. Taken from the release notes of the 8.0 and 9.x releases on Broadcom TechDocs. The GA releases of 9.0 and 9.1 carry the vCenter known and resolved issues of the VCF GA notes. Releases without an extract still have the release-notes link from the KB; the 7.0 U3k and older 7.0 notes are PDFs. Releases before 7.0 have no link in the KB at all.
Frequently asked questions
How do I find the build number of my vCenter Server?
Open the vCenter Server Management Interface on port 5480: the Summary page shows the version and the build. In the vSphere Client, Help > About shows the same build. On the appliance shell, vpxd -v prints it as well. Then type that build into the search box above to get the release name, the date and the release notes.
What is the latest vCenter version?
The tool marks the newest release of the KB with a latest tag. At the time of writing it is vCenter 9.1.1.0100, build 25784172, released on 2026-10-12. The tool is regenerated from KB 326316, so the tag moves with the KB.
Why do the VAMI and the MOB show different build numbers?
Up to vCenter Server 7.0 the appliance and the vpxd service were built separately. The VAMI reports the appliance build, while the Managed Object Browser and vpxd.log report the vpxd build. The KB lists both, and so does this page. Broadcom uses the VAMI build in the KB and in the release notes, so quote that one in a support case.
Where are the vCenter release notes?
On Broadcom TechDocs. The 8.0 and 7.0 notes live under the vSphere release notes, the 9.x notes under the VMware Cloud Foundation release notes. Every card above links to its notes, and the 8.0 and 9.x cards carry the extract. The 7.0 U3k and older 7.0 notes are PDFs. For 6.7 and older the KB links no release notes.
Does the list include vCenter Server for Windows?
Yes. The 6.7 line has a separate Windows table with its own MOB builds, and the 6.5 and older table covers both the appliance and Windows. vCenter Server for Windows was removed with vSphere 7.0, so every 7.0 and newer release is an appliance.