VMware just recalled their latest update for vSphere and vCenter Server 7.0 U3b is no longer available for download. If a vCenter has already been upgraded to vCenter 7.0 U3b (or earlier) and is experiencing the symptoms mentioned in this KB 86191, please remove the i40enu driver.
Furthermore here is a table of the critical issues identified with vSphere 7.0 Update 3:
| Summary | KB | Impact | Fix / Workaround |
| ESXi 7.0 Update 3 hosts can experience a PSOD when virtual machines on a VMFS6 thin disk execute UNMAP/TRIM functions. | 86100 | Potential ESXi host crash | This issue is planned to be resolved in an upcoming release. Please check KB for noted workaround. |
| Starting with vSphere 7.0 Update 3, the inbox i40enu network driver for ESXi changes name back to i40en. This can result in ESXi failing to update with the error: “host returned esxupdate code –1″ | 85982 | Upgrade Blocking | This issue is planned to be resolved in an upcoming release. Please check KB for noted workaround. |
| In vCenter 7.0 Update 3 FIPS compliance was enabled by default; This has the impact of blocking the SMB protocol; VAMI backup fails using SMB Protocol on vCenter 7.0 U3 with the error: “Path not exported by remote file system” | 86069 | BCDR Impacting | This issue is planned to be resolved in an upcoming release. Please check KB for noted workaround. |
| Enabling vSphere HA might fail or never complete on hosts that were upgraded to ESXi 7.0 Update 3. | 86191 | Environmental Stability | This issue is planned to be resolved in an upcoming release. Please check KB for noted workaround. |
How to remove i40enu driver:
Disable vSphere HA on the cluster with the affected hosts
Put the ESXi in maintenance mode, then run the following command to remove the obsolete i40enu VIB :
esxcli software vib remove –vibname=i40enu
Once the VIB has been removed, reboot the ESXi host. When this has been done for all hosts in the cluster, HA can be enabled again.
Closing Note
hope it has been useful to you. See you next!