Updating ESXi 8.0U3e to 8.0U3h Without Paying: Is It Allowed?

Downloading something labeled "free" comes with its own brand of optimism. It feels like you've beaten the system: you grabbed enterprise-grade virtualization software without pulling out a credit card. You're running ESXi 8.0U3e, it boots, it works, your lab is humming, and life is good.

Then the question hits: can you update it to 8.0U3h without buying anything?

That's when the optimism fades, because what looks like a simple patch upgrade quickly turns into a maze of licensing terms, portal access restrictions, dead update servers, and a whole lot of "technically." Welcome to the new reality of "free" ESXi.

The illusion of free: what you actually downloaded

Free ESXi has always been a limited experience, and that's no secret. It's a feature-restricted hypervisor meant for labs, testing, and small non-production environments. Historically, you'd grab the ISO, install it, apply a free license key, and call it a day.

Updates are where the story changes. The version you downloaded, 8.0U3e, is what you're entitled to at the moment of download. According to multiple voices in the discussion, that entitlement doesn't automatically extend to future patch levels like 8.0U3h. One commenter put it bluntly: free ESXi is what it is, and you get the version you get.

There's no magical "but it's just a minor update" loophole hiding in the fine print. And now that VMware lives under Broadcom, the whole situation feels even more complicated.

The portal problem: if you can't see it, you can't touch it

One of the most practical answers in the discussion was also the simplest: do you even have access to the update in the Broadcom portal?

If 8.0U3h doesn't appear in your account downloads, you don't have entitlement. You could call that gatekeeping, but it's simply how licensing enforcement works now: access is the license.

There's no more public patch repository sitting out in the open. In fact, hostupdate.vmware.com was shut down in April 2025, so that old-school patching workflow is gone. If you're thinking about pointing your host to an update depot and calling it a day, that door's closed.

So the practical question is less "is it legal?" and more "can you even get the bits without a subscription?" If you can't get the ISO or depot file from the official portal tied to your account, you're not entitled to it. That's how it's structured now.

"Technically not entitled": the gray zone nobody likes

One commenter summed it up with a phrase that stings: "Technically you are not entitled to download updates".

That word, technically, carries weight. From a pure functionality standpoint, ESXi doesn't stop you from running esxcli software profile update. The command still works, and the hypervisor doesn't phone home mid-upgrade and throw you in license jail. If you somehow acquire the correct depot files and validate them with checksums, the system will update.

That doesn't make it compliant, and it's the line most homelabbers dance around. Functionality isn't the same as entitlement, and a door that opens doesn't mean you're allowed inside.

Historically, even before the Broadcom era, patching beyond your SnS (Support and Subscription) contract wasn't permitted under the VMware EULA. One commenter even pointed out that people had it backwards: under Broadcom, some restrictions were loosened for critical CVE 9.0 security patches, not tightened.

That nuance matters, but the basic rule stays the same: updates are tied to active subscriptions.

Free means feature-limited, and that's not new

There's another layer that often gets overlooked in the upgrade debate: the free edition is already heavily restricted. It has no vCenter management, no VADP-based backups, and no storage API access.

Someone asked whether free ESXi allows API access with Veeam. The short answer is no. VADP is a licensed feature, which means agent-based backups only. None of this is new either; another commenter made it clear that ESXi FREE has always been like this.

So framing the current situation as some sudden betrayal isn't entirely accurate. Free ESXi has never been a rolling entitlement to future patches and enterprise capabilities. It's a snapshot in time: you install what you're allowed to install and run it as-is. That's the deal.

The Broadcom factor: stability or whiplash?

Then there's the elephant in the room, Broadcom.

There's anxiety in the community. Some users argue that what's legal today might not be tomorrow. Licensing language shifts, portal structures change, and access policies tighten or relax. Given the track record, that worry is pattern recognition more than paranoia.

Broadcom has already reshaped VMware's licensing into subscription-centric models. Perpetual licensing is effectively sidelined, and entitlements live and die inside account portals.

That unpredictability creates hesitation. If you're trying to "stay legit," as one commenter put it, the safest move is simple: if it doesn't show in your portal, don't touch it. Call it compliance hygiene rather than fearmongering. It's also the same subscription-centric shift driving the cost increases covered in the harsh reality of VMware licensing in 2026.

So… can you legally update to 8.0U3h?

Strip away the noise and here's the grounded answer based on what surfaced in the discussion:

• If 8.0U3h is available in your Broadcom account portal under your entitlement, yes, you can update.
• If it is not available to you via official channels tied to your account, you are not entitled to download or apply it.
• Free ESXi does not grant blanket access to future patch levels.
• Critical security patches may be treated differently in specific policy contexts, but that doesn't automatically apply to every update.

In other words, access equals license, and without portal access there is no legal upgrade. It's that simple, and that frustrating.

Why this feels worse than it is

Part of what makes this sting is the licensing model, and part of it is the expectation gap.

For years, homelabbers built entire ecosystems around free ESXi. It became the default hypervisor for learning VMware, it powered certification labs, and it was the sandbox for future enterprise architects. When the update path narrows, it feels personal.

From a vendor perspective, though, free editions are marketing funnels rather than long-term entitlement programs. They're designed to give you a taste, not a lifetime supply. That doesn't make it less annoying, but it does make it predictable.

What homelabbers have to accept

If you want continuous updates, you need a subscription. If you want full API access and modern backup integration, you need a license. If you want zero ambiguity about what's allowed, you need entitlement visibility in your account portal. Otherwise, you're living in the frozen snapshot of whatever free ISO you downloaded.

And maybe that's okay. For a static lab, 8.0U3e might be perfectly fine. If there's no critical CVE forcing your hand, you can run it as-is, and stability isn't the enemy.

If you're chasing every minor letter revision out of habit, though, you'll run headfirst into licensing walls.

The bigger picture: compliance vs capability

Does the update command work? It does. Does someone somewhere have a copy of 8.0U3h? They do. Neither of those settles anything, because the deciding factor is entitlement.

Enterprise software licensing has shifted toward identity-bound access, where what your account can download defines what you're allowed to run. The days of loosely accessible public patch repositories are fading. Free ESXi still works fine; it's constrained by design.

So before you go hunting for 8.0U3h, log into your Broadcom portal. If it's there, you're good. If it's not, that's your answer. It's a frustrating answer but a clear one, and in this case "free" doesn't mean future-proof.