Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Vmware Workstation Pro 14.x Unable to connect to the MKS


  • Please log in to reply
2 replies to this topic

#1 UnknownUser

UnknownUser

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:12:37 PM

Posted 22 October 2017 - 07:15 AM

After installing Vmware Workstation Pro 14.x, I'm unable to access any vm which were in my library. Those were working properly in Vmware Workstation Pro 12.5.x. But Not in the latest version, as everytime I try to open any vm it's showing, "Unable to connect to the MKS: Too many socket connect attempts; giving up". Changing hardware compatibility didn't work. How to resolve it without downgrading or waiting for upgrade/update?


Edited by UnknownUser, 22 October 2017 - 07:42 AM.


BC AdBot (Login to Remove)

 


#2 sflatechguy

sflatechguy

  • BC Advisor
  • 2,226 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:07 AM

Posted 22 October 2017 - 11:17 AM

Based on this thread, check to make sure the vmx86, hcmon and VMAuthdService services running in service.msc on the host computer. If they are, try running it in the background:

 

https://communities.vmware.com/thread/572964



#3 UnknownUser

UnknownUser
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:12:37 PM

Posted 22 October 2017 - 03:07 PM

Based on this thread, check to make sure the vmx86, hcmon and VMAuthdService services running in service.msc on the host computer. If they are, try running it in the background:

 

https://communities.vmware.com/thread/572964

Thanks for responding. My problem is similar but the  suggested methods didn't work for me. Seems I've to put this question in vmware community. 






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users