Upgrade your vSphere 6.5 host to 6.7


A while back I wrote a post on how to update your vSphere server if you do not have a vCenter. The same method to patch your server with security updates can also be used to do an upgrade to a newer version. You can read the full post here.

Before you continue you realy should read the release notes at VMware’s KB docs

So by now you know that “There is no supported upgrade path from vSphere 6.5 Update 2 to vSphere 6.7” and “Support for some devices are deprecated in ESXi 6.7. During an upgrade, these device drivers may still be installed on the ESXi 6.7 host, and may continue to function, but the device is no longer officially supported on ESXi 6.7”

There is a large amount of CPU’s that is not supported this time. While it’s not clear what the reason of all this has been some users are reporting that an upgrade from 6.5 to 6.7 can bypass the “CPU NOT SUPPORTED” installation failure when you try to do a clean installation with 6.7 from media.

To be clear it is not impossible to upgrade from 6.5 U2 to 6.7 now that an updated 6.7 was launched.


The upgrade from 6.5 or 6.0 to version 6.7 can be done in just five steps.

  • ENABLE the httpClient:
esxcli network firewall ruleset set -e true -r httpClient
  • Find the profile you want to upgrade to:
esxcli software sources profile list -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml | grep 6.7.0

This command will output a few profiles. While you could update to the release version ‘ESXi-6.7.0-8169922-standard’ and do some other updates after this, you can also upgrade to the latest available profile directly. At the moment this is ‘ESXi-6.7.0-20180704001-standard’

  • Update to the profile you want:
esxcli software profile update -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml -p ESXi-6.7.0-20180704001-standard
  • And close the httpClient when you are done:
esxcli network firewall ruleset set -e false -r httpClient

After this you need to reboot the host to have your server boot with the updates vSphere software.


Disclaimer: Ofcourse you can’t blame me if something during an upgrade goes wrong. This is not the real proper full blown way to maintain VMware. However it can work and can be used for homebrew setups or testing enviroments (Well not the real testing enviroments because you would need to test the proper upgrade path but you know what I mean)

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s