Thanks for citing rewolf's blog solving a pretty pervasive problem.

Wondering, how it could escape VMware's thorough testing before releasing the update, and also why that issue is unknown in the KB.

:smileyplus: