This issue has been fixed with the 4.5 release.

Read more at: http://communities.vmware.com/message/1496778