Well, I never got an answer and this is still a problem. The solution I found for this that doesn't mess up networking is to kill all vmware processes and then restart the services. Because I need to do this every 24hrs I've written a simple and slightly buggy powershell script to do this.

param (
    [string]$action = "restart"
)


switch($action) {
    "restart" {$command = "Restart-Service"}
    "stop" {$command = "Stop-Service"}
    "start" {$command = "Start-Service"}
    DEFAULT {exit}
}

if ($action -eq "start" ) {
    Invoke-Expression "$command -Name VMwareHostd"
    Invoke-Expression "$command -Name VMnetDHCP"
    Invoke-Expression "$command -Name VMUSBArbService"
    Invoke-Expression "& $command -Name 'VMware NAT Service'"
} else {
    Stop-Process -Name vmware -force
    Stop-Process -Name vmnetdhcp -force
    Stop-Process -Name vmnat -force
    Stop-Process -Name vmware-authd -force
    Stop-Process -Name vmware-hostd -force
    Stop-Process vmware-usbarbitrator64 -force
    Invoke-Expression "$command -Name VMUSBArbService -force"
    Invoke-Expression "$command -Name VMwareHostd -force"
    Invoke-Expression "$command -Name VMnetDHCP -force"
    Invoke-Expression "& $command -Name 'VMware NAT Service' -force"
}