Reverting to a previous version of ESXi 6.x, 7.x or 8.x

Products

• VMware vSphere ESXi

Issue/Introduction

This article explains how to revert to a previous version/build of ESXi using the Direct Console User Interface (DCUI).

Roll back ESXi upgrade.

Environment

VMware vSphere ESXi 6.x
VMware vSphere ESXi 7.x
VMware vSphere ESXi 8.x

Resolution

Process to revert to a previous version of ESXi:

Video Tutorial to revert to a previous version of ESXi:

Steps to revert to a previous version of ESXi:

Notes before starting:

• Backup the configuration data before making any changes. For more information, see How to back up and restore the ESXi host configuration.
• Reverting to a previous build does not revert the tools-light vib version installed on the ESXi host.
• Reverting an ESXi host is only valid if the host was updated using these methods:
  • VIB installation or removal
  • Profile installation or removal
  • ESXi host update using VMware Update Manager
  • Updated from a ISO
• Reverting to an earlier version is not possible after upgrading to ESXi 7.0 due to partition changes to the boot device.

Note: To use an earlier version of ESXi after upgrading to version 7.0, create a backup of the boot device before the upgrade or reinstall the desired version.

• Reverting from ESXi 8.0 to 7.0 is possible as there are no partition changes between the two versions.

1. Reboot the host.
2. When the Hypervisor progress bar starts loading, press Shift+R. This must be done while the bar is loading, not after.
   
   Ideally, press Shift+R repeatedly once the "system is preparing to boot" message appears.
   
   The following warning will show:
   Current hypervisor will permanently be replaced
with build: X.X.X-XXXXXX. Are you sure? [y/n]
    
3. Press Y to roll back to the selected build.
4. Press Enter to boot.

 

 

 

Additional Information

The following issues may occur. Please see below for more details: Possible Inventory Issues Observed After Host Rollback

 

In some cases it is not possible to roll back ESXi version.

Bootbank Directory:

$ less boot.cfg
bootstate=0
title=Loading VMware ESXi
timeout=5
prefix=
kernel=b.b00
kernelopt=autoPartition=FALSE
modules=jumpstrt.gz --- useropts.gz --- features.gz --- k.b00 --- uc_intel.b00 --- uc_amd.b00 --- uc_hygon.b00 --- procfs.b00 --- vmx.v00 --- vim.v00 --- tpm.v00 --- sb.v00 --- s.v00 
....
--- vsanheal.v00 --- vsanmgmt.v00 --- xorg.v00 --- gc.v00 --- imgdb.tgz --- basemisc.tgz --- state.tgz
build=7.0.3-0.125.23794027
updated=6

Altbootbank Directory:

$ less boot.cfg
bootstate=0
title=Loading VMware ESXi
timeout=5
prefix=
kernel=b.b00
kernelopt=autoPartition=FALSE
modules=jumpstrt.gz --- useropts.gz --- features.gz --- k.b00 --- uc_intel.b00 --- uc_amd.b00 --- uc_hygon.b00 --- procfs.b00 --- vmx.v00 --- vim.v00 --- tpm.v00 --- sb.v00 ---
...
vsanmgmt.v00 --- xorg.v00 --- gc.v00 --- imgdb.tgz --- basemisc.tgz --- state.tgz
build=7.0.3-0.125.23794027
updated=7

Notes:

• Actions such as ESXi upgrade/update or VIB installation/removal will discard the older (n-2) copy in the altbootbank folder and only retain the (n-1) copy.
• After the first reboot following a successful ESXi host upgrade, if any changes are made, such as installing software VIB's that require another reboot, the option to roll back to the previous version will be lost.

After removing the host from Maintenance Mode, if the host is part of an High Availability cluster, the Fault Domain Manager VIB will be installed on the host. The Fault Domain Manager VIB does not require a reboot.