I still think this is a bug introduced (via the Sept. patch Tuesday updates) into the API VMware Workstation has to use when the Windows hyper-v platform is active. Are you sure that you have completely disabled the hyper-v platform on startup? Here is the workaround I used, From an elevated PowerShell, I ran: