Unlike the install command, update does not overwrite custom configurations or vendor-specific drivers, minimizing the risk of boot failures and hardware compatibility issues.
You can directly upgrade from the command line using public VMware repositories, which is useful for quick patching, though it requires internet access on the host.
If you are using VMware Update Manager from a version prior to ESXi 7.0 Update 2, it is strongly recommended to use the rollup bulletin in the patch baseline to ensure all dependencies are satisfied. vmware esxi 70 patch download link
If you need specific patch numbers or build information, use the official lifecycle and build trackers to identify the exact file name. Step 1: Identify Your Required Build Number
If you are patching hosts from a version prior to ESXi 7.0 Update 2 using VMware Update Manager, it is strongly recommended to use the rollup bulletin in the patch baseline. If the rollup bulletin cannot be used, ensure that all of the following packages are included in the patching baseline; otherwise, the update operation will fail: Unlike the install command, update does not overwrite
Run the upgrade command using the target profile name found in the step above:
Remember these key URLs:
For legacy environments still running vSphere 6.x or earlier update mechanisms, VMware Update Manager provides an alternative patching method. However, for ESXi 7.0, transitioning to vSphere Lifecycle Manager is the strategic direction and strongly recommended.