Upgraded from ver 12 pro. All VM's were working fine, 14 upgrade just gives a blank vm screen now
machine is windows 10 pro, fully patched with 32 gb memory
restored host machine back to ver 12, and restored the vm also, works now
1.I have found the file preferences.ini in the address “C:\Users\Administrator\AppData\Roaming\VMware\preferences.ini” .
I have append the line -- ui.log.filelevel = "trivia" in preferences.ini.
2.I have running Workstation with admin user.
3. My VM version is 14.0.0 build-6661328
4. My VMware tools's version is 10.1.6,build-5214329.
My VM still hit the black screen.The log please see Appendix for details .
Do you have some solution for this? I have the same problem and I need my VMs. What a bad experience has been this upgrade 😕
I too experience the same problem with VMware 14, have since downgraded back to 12 and everything works fine. I have GeForce GTX 1060 if it gives any troubleshooting direction.
Hi all,
According to our investigation, this issue is related to Windows LSP changed by other software.
We can use the command "netsh winsock show catalog" to check the LSP status.
To solve the issue, please use Windows command to reset the LSP status: "netsh winsock reset", then reinstall VMware workstation and reboot the host.
Please have a try to see if it works.
Works fine for me, thanks
Works for me too. Thanks for your answer.
Winsock reset is a solution but not the good one.
I'm using open text socks client pro version and after the reset VMware was OK but my socks client was no more working.
Now I have setup again my Socks client and VMware produce a black screen
I have the same problem and this fix did not work for me. Any other ideas on how to fix this problem please?
Regards
Christopher
I think everyone is ignoring us!
From you attached log, I see it was not caused by winsock error.
Can you please upload the UI log and VM log together so that I can investigate it more.
2017-10-25T06:47:37.019-05:00| vmui| W115: Poll_SocketPair: Error creating a inet socket pair: 10013/An attempt was made to access a socket in a way forbidden by its access permissions
Create socket failed.A Socket Error 10013 can and will occur if there are settings on your computer that are not properly configured. In many instances it is an anti-virus software that will either not scan your computer properly or will take too long to scan them and thus prompt the error. (see How do I fix error code 10013 for IE11 and windows 7? - Microsoft Community ).
Can someone tell me how to get the log report for VMware Workstation Pro? I would like to upload them here so can get some help on what the cause of the black screen is.
Menu Help -> About VMware Workstation.
Then in the opened 'About ' dialog, you can see the log files location.
Please upload both UI log and vm log.
The log file you uploaded shows that you didn't power on a VM. Please try and upload the logs again.
1. Open Workstation.
2. Power on a VM.
3. Wait a miniute, and see if the guest OS picture shows.
4. If a black picture is seen, please collect the logs.
5. To collect logs, you need click menu help > About VMware Workstation.
6. In the About dialog, you should see UI log file location and also VM log file location. Please upload both of them. Thanks.
Thank you for your offer of help but I found the problem. I had previously installed ZoneAlarm. I have uninstalled the program, however it had left some files behind. These files could not be removed manually as it would cause more problems, like my LAN Network adapter would stop working. I was able to get a clean tool from ZoneAlarm for windows 10, which I then ran on my PC. After all files were removed I rebooted, everything worked perfectly afterwards. If anyone else need this tool please PM me.
Thanks again.
I found the problem. I had previously installed ZoneAlarm. I have uninstalled the program, however it had left some files behind. These files could not be removed manually as it would cause more problems, like my LAN Network adapter would stop working. I was able to get a clean tool from ZoneAlarm for windows 10, which I then ran on my PC. After all files were removed I rebooted, everything worked perfectly afterwards. If anyone else need this tool please PM me.
Thanks again.