It’s a known issue, you will need to follow this KB to fix it:
VMware Knowledge Base
View solution in original post