Just connected to version 6.5 of esxi and see the same error. I guess you did not fix that at all as you claim at 6.0 release.
