Alarasheed Blog · July 16, 2023 0

How to update to VMware ESXi 8.0 Update 1a build 21813344

The purpose of this blog post is to provide the guidance and the steps needed to update my current ESXi 8 environment (ESXi 8.0 Update 1 build 21495797) to ESXi 8.0 Update 1a build 21813344.

Release notes for ESXi 8.0 Update 1a build 21813344 can be found here. Below is a screenshot of my current environment (ESXi 8.0 Update 1 build 21495797) prior to update 1a build 21813344. Previous build numbers can be found here.

ESXi 8.0 Update 1 build 21495797

** Please keep in mind, this guides applies to my personal home lab environment so please proceed with caution and take the appropriate steps including documentation to ensure you have a successful update. **

I decided to use the ESXCLI command method to proceed with the ESXI Host update and there is no better resource to act as a guide than Paul Braren‘s blog post found here.

In order to use the command provided by Paul, the first step is to enable SSH on the host. Log into your ESXi host interface, right-click the ESXi Host, followed by Services, and then select Enable Secure Shell (SSH):

Enable Secure Shell (SSH)

Next, SSH into the ESXi Host (I use Putty) and then log in using your Root credentials:

I included the command found in the screenshot below but since my Dell PowerEdge R720 server is not found on the VMware Compatibility List, it triggered a No Hardware Warning alert.


esxcli software profile update -p ESXi-7.0U3k-21313628-standard -d

In order to get around this alert, you’ll need to add –no-hardware-warning to the end of the command.


esxcli software profile update -p ESXi-7.0U3k-21313628-standard -d –no-hardware-warning

Note: there are two dashes\hyphens prior to the word No in the command above. For whatever reason, it doesn’t display properly when I publish this post.

I also included the command in the first image below.

Once the command has been successfully applied, the update process begins and you’ll then be prompted to reboot your ESXi host. I was able to keep track of the reboot process using my idrac session.

If I have missed anything or if you have any suggestions, please let me know.

If you’re interested in anything related to VMware on my blog, please click on this link.

<– Read More on –>