Is anyone from VMware able to acknowledge this issue and confirm a fix is forthcoming? At least in my scenario it's reproducible every time.
