Update VMware ESXi via command line using offline patch files from the Broadcom portal. Covers ESXi 6, 7, 8, and 9.
This guide covers updating VMware ESXi using the command-line interface (ESXCLI). Since Broadcom acquired VMware, the public online depot (hostupdate.vmware.com) has been shut down. All updates now go through the Broadcom Support Portal using offline patch files uploaded to a datastore.
The offline datastore method is now the only supported approach via ESXCLI
A Broadcom account with valid VMware entitlements is required to download patches
If your host has internet access, you can set up a self-hosted HTTP depot using nginx or Pythonβs http.server and point ESXCLI at it. See Method 2 below.
update vs install: Patch or Major Upgrade?
ESXCLI has two profile commands with different behaviours:
Command
Purpose
Same-version patch
Major upgrade (6β7, 7β8)
esxcli software profile update
Apply newer content only
β Yes
β No
esxcli software profile install
Full overwrite, any version
β Yes (overkill)
β Yes
update applies only newer VIBs than whatβs currently installed. It skips packages with lower revision numbers. Use this for patching within the same major version (e.g., 8.0U2 β 8.0U3).
install overwrites all packages regardless of version. It can install older, newer, or entirely different versions. Use --allow-downgrades if the target profile has any older packages. This is what you need for cross-version upgrades (6.x β 7.x, 7.x β 8.x, etc.).
Hardware compatibility check: Always verify your hardware is supported on the target ESXi version before a major upgrade. Check the VMware Compatibility Guide. ESXi 8.x dropped support for many older CPUs β upgrading a 6.x host to 8.x may fail on unsupported hardware.
--allow-downgrades is needed because the target profile may contain VIBs with lower revision numbers than whatβs installed. Without it, the install will fail if ANY VIB would be downgraded.
If you want an βonline-likeβ workflow (e.g., multiple hosts pulling from a central server), host the depot ZIP on an internal HTTP server:
Step 1: Serve the Depot ZIP over HTTP
Extract the downloaded ZIP to a directory and serve it:
# On your Linux server/workstationmkdir -p /srv/esxi-depotcd /srv/esxi-depotunzip /path/to/VMware-ESXi-8.0U3d-24585383-depot.zip# Serve with Python (no auth, LAN-only)python3 -m http.server 8080
Or with nginx:
server { listen 80; server_name depot.internal.lan; root /srv/esxi-depot; autoindex on;}
The depot ZIP contains an index.xml at the root. ESXCLI reads it to discover profiles and VIBs, same as it did with the old VMware online depot.
Method 3: Single VIB File (Legacy Drivers) π’π΅
For applying individual driver updates or async VIBs (e.g., NIC drivers, HBA firmware):
# π’π΅ ESXi 6.x & 7.x : from a local VIB fileesxcli software vib install -v /vmfs/volumes/datastore1/drivers/DriverName.vib# π’π΅ ESXi 6.x & 7.x : from a local ZIP bundleesxcli software vib update -d /vmfs/volumes/datastore1/drivers/driver-bundle.zip
π£π ESXi 8.0U2+: individual VIB installation is no longer supported. Use esxcli software profile update with the full depot ZIP instead.
Legacy: MemoryError Workaround (ESXi 8.x)
When listing profiles from a large depot (online or self-hosted), ESXi 8.x may throw [MemoryError]. The default ESXCLI memory limit is 300MB:
esxcli system settings advanced set -o /VisorFS/VisorFSPristineTardisk -i 0cp /usr/lib/vmware/esxcli-software /usr/lib/vmware/esxcli-software.baksed -i 's/mem=300/mem=500/g' /usr/lib/vmware/esxcli-software.bakmv /usr/lib/vmware/esxcli-software.bak /usr/lib/vmware/esxcli-software -fesxcli system settings advanced set -o /VisorFS/VisorFSPristineTardisk -i 1
Version Compatibility Summary
Feature
π’ ESXi 6.x
π΅ ESXi 7.x
π£ ESXi 8.x
π ESXi 9.x
esxcli software vib update
β Supported
β Supported
β Deprecated (8.0U2+)
β Not available
esxcli software profile update
β Supported
β Supported
β Required (8.0U2+)
β Required
Offline datastore patch
β
β
β
β
Self-hosted HTTP depot
β
β
β
β
Broadcom portal downloads
β
β
β
β
Old hostupdate.vmware.com
β Dead
β Dead
β Dead
β Dead
MemoryError workaround needed
No
No
Yes (8.x)
Yes
Common Pitfalls
Forgetting to shut down VMs before entering maintenance mode. The host will refuse maintenance mode if VMs are still running.
Using esxcli software vib update on ESXi 8.0U2+. This returns an error: switch to esxcli software profile update.
Wrong datastore path. Use the full path: /vmfs/volumes/DATASTORE_NAME/... or /vmfs/volumes/UUID/....
Broadcom portal access. If you cannot find your ESXi downloads, verify your Broadcom account has the correct entitlements (tied to your VMware license/support contract).