What Version of Workstation did you test with?
have you tested this version in windows 10 1903 build?
Are you running 1903 as Guest or as Host OS?
as a host, Windows 10 1903 is my main pc os, and I have a windows 7 guest and Linux and when trying to start them the hang on a black screen but when I use windows 10 1809 as a host everything is fine so it seems VMware have to upgrade VMware workstation pro to work with the new windows 10 upgrade
So are you running the Insider Preview Build of Windows, as I am not able to find the Updated ISO on MSDN?
yes i am
is there a way they can fix it?
it would be great if you could fix this issue.
First of all I am not in the Workstation Team,
Second as this is still a unreleased Version from Windows 10, I would not suggest running it in Production ;-)
I cannot, and will not make any forward looking statements.
Do you have any error when VM crashes?
Because excluding 2 vms, other vms are running well on my Windows 10 1903 Insider Preview
3 people found this helpful
I can confirm
VMWare 15.0.4 does not really work with Windows10 1903 as Host as it should.
(upgraded from v14, cause I tought v14 is not 1903 ready)
If I create a new Windows10 Vmware with a bootable Windows10 ISO and it is
connected. VMWARE does not boot, only a black screen and Vmware hangs up
(vmware-vmx.exe cant be terminated, have to reboot windows)
So I started the Vmware without, that a ISO is connect, then vmware boots into
bootmenu, there I connected the ISO and could install windows10.
But if the OS is already booted (tried Windows10 and Ubuntu) and wanted
to connect a USB Drive, the same happends as before, Vmware hangs up,
and it is impossible to close it or terminate the vmware-vmx.exe process.
Same, if you drag&drop a file from the host to the vmware machine... freezes again.
tried it now 20 times... (with clean install of vmware and everything..)
there is a big bug in vmware if the host is 1903
I've experienced the same issue. For me, at least, the issue seems to be related to using "Bridged" networking. I can switch the adapter to NAT, boot up my VM with no issue. When I switch the adapter back to bridged and try again it works. That's short lived though as usually if I shut down the VM and restart it it locks up as you'd described. Luckily I don't have to do this too often.
When it locks up, this is what I see at the tail of my vmware.log file.
2019-03-24T14:19:24.974-05:00| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.
2019-03-24T14:20:46.118-05:00| mks| W115: SOCKET 5 (-1) AsyncNamedPipeRecvCallback: failed to get overlapped result: 109.
2019-03-24T14:20:46.118-05:00| mks| I125: MKSControlSocket: MKSControl Remote Disconnect: socket closed.
2019-03-24T14:20:46.118-05:00| mks| I125: MKSControlMgr: disconnected
2019-03-24T14:20:46.118-05:00| vmx| I125: SOCKET 4 (2140) recv error 10054: An existing connection was forcibly closed by the remote host
2019-03-24T14:20:46.118-05:00| vmx| I125: Vix: [mainDispatch.c:2828]: VMAutomation: Connection Error (1) on connection 0.
2019-03-24T14:21:03.048-05:00| WinNotifyThread| I125: Suspending VM from WM_ENDSESSION: U64_Media
2019-03-24T14:21:03.048-05:00| vmx| I125: SUSPEND: Start suspend (flags=0)
Another thing I did that may have helped was switched this line in my VMX file. The default is the E1000
ethernet0.virtualDev = "vmxnet3"