Why would anyone want to update to a minor revision from a perfectly working version? All versions prior to this minor revision required some every boot “hacking” of the ethernet driver if you also want to run a USB NIC, which is very handy when you’re using a NIC and want a second interface.
Enter Maintenance Mode.
esxcli software profile update -p ESXi-7.0U1b-17168206-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
I recently ran into an issue with one of my SSDs failing in my ESXi v6.7 NUC. All of my client VMs were house on this, now dead, datastore so all VMs were showing in vSphere Web as “Invalid.” One of the unfortunate side-effects of this error is the complete inability to really do anything to the VM – you can’t edit settings, you can’t unregister, and you definitely can’t delete.
Luckily, it is possible to delete these abominations. Unluckily, it requires some command-line magic.
The first step is to enable SSH on the ESXi host. No reboot is needed to enable SSH.
Once SSH is enabled, access the ESXi host and login.
Will list all VMs either currently or previously registered to this particular ESXi instance. I don’t remember the exact verbiage but it reported something to the effect of:
Skipping invalid VM 1
This error repeated for each VM that had been taken along with the now defunct SSD. Once the list of failed VMs is shown, run the following command for each VM:
vim-cmd /vmsvc/unregister <id>
And that’s it. All ghosts of the former VMs should be removed and your ESXi WebUI should be clear of errored clients.