From the log file attached, it looks like vSphere 6.0 Client is used to connect to an ESXi 6.5 host. This is not an officially supported configuration.
[ :startup :W: 1] 2018-01-31 17:14:12.997 Log for vSphere Client Launcher, pid=14508, version=6.0.0, build=build-5112508, option=release
[ :QuickInf:P:15] 2018-01-31 17:14:40.433 Loading catalog '/catalog/coreLocale/en/fault.vmsg' from C:\Users\mrf23\AppData\Local\VMware\vpx\catalog\HostAgent\6.5.0\en\vim\fault_9320fbcfe92541441523c2f0c3cd5ed7.vmsg
While it may work in some cases, this error you encounter now might be the case that you are bumping into the one of many reasons why vSphere Client 6.0 is not officially supported for ESXi 6.5 hosts. Certainly, there will be things that vSphere 6.0 client won't be able to handle properly that are ESXi 6.5 only (e.g. virtual NVMe in a VM).
The direction is to use the ESXi 6.5 embedded host client instead of the vSphere client. From the log, in your case you would use a browser (Chrome or Firefox would do) and point to the ESXi host.
You can download an updated VIB from here