It would be nice if VMware would release some kind of KB article acknowledging this bug...

Ran into the same issue and this thread is the only piece of info I could find, and thus is the only thing that prevented me from calling support.