after the Windows 10 64bit upgrade the virtual machine cannot be started.
Ther are two different error messages: "internal error", or "cannot find a velid peer to conect to".
The VMPlayer version is 15.1.0-13591040 set up with VMWare Workstation.
- it on two different PC-s,
- remove and re-install the Player again,
- start it with administrartion privileges,
- create a new, clear virtual machine, but the error is same
... so I have no more idea! Anyone has?
The situation is more complicated (if is it possible): sometimes, but very rare, the Player starts, and working well.
My IT professional friend said, thet the answare in the Windows10 process management methode: if other working processes are more important by the "process management's opinion", then it doesn't give enough resource to the VM Player and put it onto a "waiting list", but if the VM Player is too "impatient", then it reports an error and stops untimely.
We are searching for the solution yet ...
I got the same error.
I try to explain it ...
Yesterday I worked without problem in my virtual machines.
From this morning I can not open any of my virtual machines.
all the time ...
Host Microsoft Windows 10 64 bit ... version 1803
Vmware Workstation Pro 15.1.0
Guests : Ubuntu Studio 16.04 LTS
Microsoft Windows 10 64 bit ... version 1903
I tried to :
1) repair Workstation 15.1 ... no luck
2) uninstall Workstation 15.1 and reinstall Workstation 15.0
I) first run Ubuntu and Centos worked, then no more do, Windows 10 doesn't (neither the first)
II) next runs no machine worked at all
I need a rapid solution while all my works are in virtual machines and my customers need I terminate all of the works.
What can be done ?????