vSphere 7 End of Life: ESXi 7.0 and vCenter 7.0 Support Dates

vSphere 7 reached end of general support on 2 October 2025. The date covers ESXi 7.0, vCenter Server 7.0 and vSAN 7.0. From that day Broadcom stopped releasing patches and security fixes for the 7.x line and stopped taking support cases for it. End of Technical Guidance follows on 2 April 2027, but only for customers who still hold a valid VMware contract; Broadcom says that date does not apply to Broadcom contracts. The dates below come from Broadcom's knowledge base and VMware's own announcements, checked on 9 October 2026. Running vSphere 8? Its dates and choices are different, and they are covered in our vSphere 8 guide.

vSphere 7.0 end of support dates

*Broadcom's footnote: the Technical Guidance date does not apply to Broadcom contracts and applies to valid VMware contracts only.

General support was originally due to end on 2 April 2025. In July 2024 Broadcom extended it by six months to 2 October 2025 to give customers more time to plan upgrades. It has not been extended again: Broadcom's end of general support article, updated in August 2026, gives 2 October 2025 as the end of general support and lists no Technical Guidance date at all.

What end of general support means for ESXi 7 and vCenter 7

Nothing switches off. Hosts keep running, virtual machines stay powered on and licensed features stay unlocked; Broadcom's article on expired support confirms there is no automated shutdown. What changed on 2 October 2025 is everything around the software:

• No new patches or security fixes for 7.x. Every ESXi or vCenter vulnerability published since then stays unpatched on a 7.0 host.
• No support cases. Broadcom's reminder notice says customers cannot engage Broadcom Support for 7.x releases after the date.
• Old fixes only, and only while your contract lasts. Patches already published remain available as self-service for the rest of your agreed maintenance period, under Broadcom's maintenance policy.
• A finding waiting to be written. An unsupported hypervisor sits under every workload on the host, which is exactly what security reviews, auditors and cyber-insurance questionnaires look for.

Is Technical Guidance still available for vSphere 7?

It depends on the paper you hold. VMware's announcements put the end of Technical Guidance for ESXi, vCenter and vSAN 7.x at 2 April 2027, with the footnote shown under the table: valid VMware contracts only, not Broadcom contracts. Technical Guidance is not a patch stream either. Broadcom's notice is explicit that patches and updates stopped at the October 2025 date. Broadcom also told customers to ask their representative about the availability of Extended Support, but it has published no terms. Treat it as a quote to request, not a plan to rely on.

Upgrade paths off vSphere 7

The next stop is vSphere 8. Broadcom's vSphere 9.0 notes say a direct upgrade from vSphere 7.0 is not supported and that vCenter 9.0 cannot manage ESX 7.0 or earlier; the minimum host version is ESX 8.0. Any route to version 9 passes through 8 first.

vSphere 8 is on a clock of its own. Its general support ends in October 2027, and Broadcom's product line comparison says vSphere Standard and Enterprise Plus are only available up to 8 Update 3, with vSphere 9.1 features only available in VMware vSphere Foundation (VVF) 9.1 and VMware Cloud Foundation (VCF) 9.1. Moving to 8 buys time. The platform decision comes after it, and the vSphere 8 end-of-life guide works through that decision.

Check your entitlement before the project plan. If you hold perpetual vSphere 7 licenses, Broadcom's knowledge base says a major version upgrade such as 7.x to 8.x requires active Support and Subscription (SnS) for the license conversion, and that patch downloads are restricted to accounts with active SnS. With support lapsed, the upgrade you need runs through a new subscription.

Subscriptions are counted per physical core, with a minimum of 16 cores per CPU, so older hosts with low core counts license above their real size. VVF covers ESXi, vCenter, the operations tooling and a per-core vSAN allowance; VCF adds NSX networking, automation and lifecycle management across the stack. How to count, and which tier fits, are covered in VMware per-core licensing and VCF vs VVF.

Hardware that can block the upgrade to ESXi 8

The 7-to-8 upgrade is where older servers get caught. Check every host against the Broadcom Compatibility Guide before scheduling anything. The vSphere 8.0 release notes list the usual blockers:

• CPUs. vSphere 8.0 no longer supports CPUs that the hardware vendor has marked end of support or end of life. Broadcom's CPU support article explains that the installer blocks a discontinued CPU series for that major release.
• Network and storage adapters. Some devices are no longer supported in ESXi 8.0, including those served by the nmlx4_en driver and devices removed from the 8.0 lpfc driver. Knowledge base article 88172 has the full list.
• Boot media. From ESXi 8.0, legacy SD card and USB boot devices are supported with limitations, and keeping the ESX-OSData partition on them is deprecated. Broadcom's best practice is a separate persistent local device of at least 32 GB.
• Firmware mode. UEFI boot is strongly recommended; some ESXi 8.0 hosts might not boot in legacy BIOS mode.
• Old drivers. ESXi 8.0 install and upgrade workflows block VIBs without a SHA256 checksum, such as VIBs from versions earlier than ESXi 6.7.
• NSX for vSphere. vSphere 8.0 is not compatible with NSX-V, and upgrades from systems running it are not supported.

A host that fails these checks leaves three choices: replace it, size a subscription around the hosts you keep, or hold the old hosts on 7.0 under third-party support until they retire.

Third-party support for vSphere 7

Independent providers support perpetual vSphere 7 estates after Broadcom support ends. You get break-fix on the version you run, configuration help and the provider's own mitigations for published vulnerabilities. You do not get vendor patches, new versions, or the right to add hosts beyond what your perpetual keys already cover. That suits an estate that is frozen and has a retirement date. It does not suit one that must grow, or one that must show a current entitlement to an auditor or customer. Our comparison of third-party VMware support and a Broadcom subscription sets the trade-offs side by side, including the hybrid that most mixed estates end up with.

How AceMQ helps with vSphere 7 end of life

AceMQ is a Broadcom VMware partner. We quote VVF and VCF subscriptions against your actual core counts, so you can see what moving off 7.0 costs before you commit to a path. Request a quote on the VMware licensing page, or see VMware renewal and licensing support if your current partner has lost authorization or your renewal is already due. For the renewal itself, the VMware renewal guide for 2026 covers timing, terms and what to have ready.

Need a number before you decide? Ask for a VMware renewal quote that prices VVF and VCF on your own core count.

• Broadcom KB 415405: End of General Support for vSphere 7.0
• VMware blog: Announcing extension of vSphere 7.x and vSAN 7.x general support period (25 July 2024)
• VMware blog: Reminder: vSphere 7 to reach End of Service on 2 October 2025 (31 March 2025)
• Broadcom KB 429208: Perpetual license functionality after SnS expiration
• VMware blog: What's new with vSphere in VMware Cloud Foundation 9.0
• VMware: vSphere product line comparison
• Broadcom TechDocs: VMware vSphere 8.0 release notes
• Broadcom KB 318697: CPU support deprecation and discontinuation
• Broadcom KB 313548: Counting cores for VMware Cloud Foundation and vSphere Foundation
• Broadcom Compatibility Guide