VMware Communities
wgbell
Contributor
Contributor

VM Hangs on Startup - Windows 10

Hi,

Using 15.0.3 build-12422535 with a Ubuntu 16.04 guest the VM will not start.  Screen is black and the VM appears to be hung.  The last portion of the log always looks like this (see below).   If I remove the NIC (bridged) I can start the VM but of course it then serves no function. However,  once I do this I can re-add the NIC and it will start.  I have to do this just about every time I stop and restart the VM.   I also have a WIndows Server 2012 VM that does the same thing and I just had it happen when trying to create a brand new VM.   I realize that the version of Windows 10 may be responsible since's it's not officially released but if anyone has advice or a more graceful workaround I'd love to hear it.

2019-03-24T14:18:25.488-05:00| vmx| I125: USB: Found device [name:Seagate\ RSS\ BUP\ Slim\ BK vid:0bc2 pid:ab26 path:1/1/4/3/1 speed:super family:storage,storage-bulk instanceId:USB\\VID_0BC2&PID_AB26\\MSFT30NA9CYXG8 serialnum:MSFT30NA9CYXG8 arbRuntimeKey:2 version:3]

2019-03-24T14:18:25.488-05:00| vmx| I125: USB: Found device [name:Virtual\ Bluetooth\ Adapter vid:0e0f pid:0008 speed:full family:wireless,bluetooth virtPath:usb:2 deviceType:virtual-bluetooth info:0000001 version:3], connected to usb:1 port 0.

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)

0 Kudos
0 Replies