VMware vSphere Client in 2026: how to access and manage vCenter

If you’ve arrived here looking for where to download the VMware vSphere Client, you’re in the right place – although the answer isn’t what you might expect: there is no longer any vSphere Client file to download.

This article explains what happened, how to access vCenter today, and which tools to use to manage VMware environments in production in 2026.

What happened to the vSphere Client?

The old desktop client – the so-called C# client or thick client – has been out of production for years. The transition began with vSphere 6.5 (2016), when VMware introduced the HTML5-based vSphere Client alongside the existing Flash-based Web Client. The full timeline:

• vSphere Client C# (thick client): removed in vSphere 6.5 (2016); vSphere 6.0 was the last release to include it.
• vSphere Web Client (Flash/Flex): deprecated with vSphere 6.7, fully removed in vSphere 7.0.
• vSphere Client HTML5: the only client in VCSA from vSphere 7.0 onwards (when the Flash Web Client was fully removed), fully integrated into vCenter, no download required.

The latest releases on both branches confirm this direction: vSphere 8.0 Update 3k (July 29, 2026) on the 8.x line, and ESX 9.x / vCenter 9.x delivered as part of VMware Cloud Foundation (VCF) 9.1 (May 2026) on the 9.x line. Across both branches, the only client is the browser-based HTML5 vSphere Client – there is no .exe installer, no standalone download, no desktop application to maintain.

Both the standalone vSphere 8.x line (currently at vCenter Server 8.0 Update 3k) and the vCenter component integrated into VCF 9 / VVF 9 are supported releases for the management layer.

Note on the portal: The download portal has also changed. VMware Customer Connect no longer exists; the current reference point is the Broadcom Support Portal, where you can access licenses, downloads, and support.

How to access vCenter today

You don’t need to install anything. All you need is a modern browser and the address of your vCenter Server:

https://<vcenter-name-or-ip>/ui

The HTML5 vSphere Client is compatible with current versions of Chrome, Firefox, Edge, and Safari, and is included by default in every installation of vCenter Server Appliance (VCSA) – the only format available from vSphere 7 onwards.

A note on SSL certificates

In production environments, some advanced features and the VM console via browser may behave differently depending on the browser and OS. If an SSL certificate warning appears, it is expected with self-signed certificates. In production, it is best to replace them with certificates signed by a trusted CA (internal or public) to avoid disruptions in MSP workflows and multi-admin environments.

Direct access to a standalone ESXi host

If you manage ESXi hosts without vCenter, you can use the VMware Host Client, also accessible via browser:

https://<esxi-ip>/ui

This allows you to manage VMs, storage, and networking directly on the host without going through vCenter. If you have just accessed an ESXi host and want to start creating new virtual machines, you can follow our guide on how to create a virtual machine on a VMware ESX(i)/vSphere host.

Free ESXi Hypervisor: it’s back

A significant update for those managing labs or test environments: Broadcom has reintroduced the free version of VMware vSphere Hypervisor 8, which had been discontinued in early 2024. It is available for download after creating a free Broadcom Support Portal account, starting with the ESXi 8.0 Update 3e release (April 2025).

The free edition is intended for labs, training, and non-production use. The main limitations to be aware of are:

• No vCenter integration: free hosts cannot be added to a vCenter Server and therefore cannot be managed centrally. Each host is administered individually via the VMware Host Client (https://<esxi-ip>/ui).
• Maximum 8 vCPUs per virtual machine: a hard cap on per-VM compute, regardless of the underlying hardware.
• No Broadcom support: no SLA, no patches via support contract, no escalation path. Updates are self-service from the portal.
• API access is read-only: programmatic management via PowerCLI or REST APIs is not supported for write operations.

There is no limit on the number of hosts you can install, but since they cannot be centrally managed, the free edition is not a viable option for anything beyond labs, PoCs, or isolated test environments.

If you are starting from scratch with a new host for your lab, you can follow the guide on how to install and configure VMware ESXi.

vSphere 9 and VCF 9: the new strategic platform

Starting in 2025, Broadcom has decoupled vSphere from its traditional standalone packaging. vSphere 9 (ESX 9.x and vCenter 9.x) is no longer sold as a separate product: it is delivered exclusively as part of VMware Cloud Foundation (VCF) 9 – the full private cloud stack including NSX, vSAN, and SDDC Manager – or VMware vSphere Foundation (VVF) 9, the lighter bundle for customers who only need the core compute and storage stack without the full software-defined networking layer.

Key dates to keep in mind:

• VCF 9.0 GA: June 17, 2025
• VCF 9.1 GA: May 2026 – the current minor release, with maintenance patch 9.1.1 following in September 2026. The headline feature is Enhanced NVMe Memory Tiering, which uses NVMe SSDs as a secondary memory tier alongside DRAM and introduces native software mirroring for Tier 1 redundancy (no hardware RAID required), with claims of up to 40% lower server TCO. Other relevant additions for MSPs: expanded VKS (vSphere Kubernetes Service) scale up to 500 Kubernetes clusters per Supervisor, with faster provisioning, vSAN deduplication and compression with data-at-rest encryption GA, and File Integrity Monitoring aligned with NIST and PCI DSS requirements.

Along with VCF 9, the support model has also changed. The previous 5+2 scheme (5 years of General Support + optional 2 years of Extended Support) has been replaced by a 6+1 model: 6 years of General Support included, with the option to purchase one additional year of Extended Support.

The release cadence has been stretched from a 2-year major cycle to a 3-year major cycle, with minor releases roughly every 9 months. The last minor in each major line (currently expected to be 9.3) will be a Long-Term Support release with around 45 months of support, while earlier minors get approximately 27 months each.

For MSPs, two operational implications:

• The migration path from vSphere 7.x is no longer “to vSphere 8” by default. For new deployments and refresh cycles, the strategic target is VCF 9 / VVF 9, since the 8.x line will reach EoGS on October 11, 2027.
• Downloads, ISOs, custom OEM images, and patches for the 9.x line are published under a separate VCF 9 / VVF 9 area of the Broadcom Support Portal, not under the legacy vSphere component pages. Bookmarks and automation scripts pointing to the old URLs need to be updated.

The HTML5 client described in this article works identically on vCenter 8 and vCenter 9: same https://<vcenter>/ui endpoint, same authentication methods, same browser-only workflow. The major difference under the hood is on the management layer (SDDC Manager, VCF Operations) rather than on the vSphere Client itself.

What if you’re still on vSphere 6.x or 7.0?

Many organizations – especially those managing complex or regulated environments – are still running vSphere 6.7 or 7.0, often for hardware compatibility or software certification reasons. In these cases, the HTML5 client is already available (introduced progressively from 6.5 onwards and the only client in VCSA from vSphere 7.0), but some features may not be fully on par with vSphere 8.

The support timeline to keep in mind:

• vSphere 6.5 and 6.7: End of General Support on October 15, 2022; End of Technical Guidance on November 15, 2023. These versions are now fully out of support: no security patches, no bug fixes, no Broadcom assistance.
• vSphere 7.x (ESXi, vCenter, vSAN): End of General Support on October 2, 2025 – extended by six months from the originally announced April 2, 2025 date. End of Technical Guidance is set for April 2, 2027. After October 2025, no new security patches or fixes are released; only previously published updates remain available via self-service.
• vSphere 8.x: End of General Support announced for October 11, 2027.

For MSPs managing these environments, planning a migration path is no longer optional – especially for vSphere 7, which is now in the Technical Guidance phase and exposed to any new vulnerability without an official patch. The realistic targets today are two: vSphere 8 for organizations that need a short-term, lower-friction upgrade and can live with EoGS on October 11, 2027; or VCF 9 / VVF 9 for those willing to commit to the new platform model and benefit from the longer 6+1 support window. Extended Support contracts can buy additional time on the older lines, but they are increasingly costly and intended as a bridge, not a long-term strategy.

Command-line management: VCF PowerCLI

For those managing production environments, a browser is often not enough. VMware PowerCLI – rebranded as VCF PowerCLI starting with version 9.0 (mid-2025), based on PowerShell 7.4 or later and compatible with Windows, Linux, and macOS – is the standard automation tool for vSphere. It offers over 7,000 cmdlets across the VCF stack to manage VMs, storage, networks, clusters, vSAN, NSX, SDDC Manager.

Install it directly from the PowerShell Gallery:

Install-Module -Name VCF.PowerCLI

If you have VMware.PowerCLI 13.3 or earlier already installed, add the -AllowClobber flag to avoid module conflicts during the upgrade:

Install-Module -Name VCF.PowerCLI -AllowClobber

Requirements: PowerShell 7.4 or later is the officially supported minimum version per Broadcom (KB 409981 and the VCF PowerCLI Compatibility Matrix). Older 7.x builds may still load the module but are out of support. On Windows, make sure you are not using Windows PowerShell 5.1, which is not supported by the current module.

For those who prefer Linux or Python environments, the vSphere REST APIs are accessible via:

https://<vcenter>/api

Full documentation is available on the VCF PowerCLI Developer Portal.

What changes compared to the old client

Feature	C# Client (Old)	HTML5 (2026)
Installation	Local .exe	None, browser-only
Platforms	Windows only	Win / Mac / Linux / Tablet
Updates	Manual	Automatic with vCenter
Auth	Windows SSPI (native, Windows-only)	LDAPS / ADFS / Entra ID / Okta
Functionality	Complete on 5.5; deprecated on 6.0; removed in 6.5	Full parity with legacy client

The transition to the HTML5 client is not just aesthetic. The benefits for MSPs and system administrators are concrete:

No installation, automatic updates. The client updates with every vCenter patch. No more incompatible versions or installers to distribute to admin workstations.

Accessible everywhere. Windows, macOS, Linux, tablet – all you need is a browser. This is particularly useful in MSP environments where work is done from different stations.

EAP plugin support discontinued. The VMware Enhanced Authentication Plugin – used for integrated Single Sign-On with Active Directory – was deprecated with vCenter Server 7.0 Update 2 in 2021 and, following the disclosure of two critical vulnerabilities (CVE-2024-22245, CVSS 9.6, and CVE-2024-22250, CVSS 7.8) detailed in VMSA-2024-0003, Broadcom chose not to patch it. Starting with vSphere 8.0 Update 3, EAP can no longer be used to authenticate to vCenter via the vSphere Client. Authentication now relies on modern methods: LDAPS, ADFS, Okta, and Microsoft Entra ID.

Full functional parity. In early HTML5 versions, some features were missing. With vSphere 7 and vSphere 8, the gap has been closed: everything possible with the old desktop client is now available in the web interface.

How to access: quick procedure

1. Open your browser to https://<vcenter>/ui
2. Enter your credentials (username, password, and domain if required – e.g., vsphere.local or your AD domain).
3. Click LOGIN.

From here, you have full access to hosts, clusters, VMs, storage, and networks.

Where to go from here

There is no longer a VMware vSphere Client to download. The HTML5 client integrated into vCenter is the official solution supported by Broadcom for managing both vSphere 8 and vSphere 9 environments, and VCF PowerCLI is the reference tool for automation and scripted operations across the entire stack.

If you manage VMware environments for clients, the starting point for licenses, downloads, and support is now the Broadcom Support Portal – no longer the old VMware URLs – with VCF 9 / VVF 9 published in a separate area from the legacy vSphere pages.

For MSPs still running vSphere 6.x or 7.x, the next 12–18 months will be critical: with general support for vSphere 7 already ended in October 2025 and vSphere 8 scheduled for October 11, 2027, planning the migration path – either to vSphere 8 as a tactical step or directly to VCF 9 / VVF 9 as a strategic target – is the only way to avoid emergency upgrades and unsupported production workloads.