The article definitely needs some more precise details.
They've removed "Update 1" from the KB title, which indicates the issue is not specific to Update 1.

Also, in the Resolution section, it lists "Downgrade ESXi to 6.0 U2" as a workaround. This is additional confirmation the issue is known to exist in 6.5 prior to U1. The presence of "U2" here makes me wonder if the issue also exists in ESXi 6.0 U3, although there's nothing else to indicate that.
