VMware Cloud Community
Stefan007
Contributor
Contributor

VMware Fusion has encountered an error and has shutdown windows

My virtual machines are all crashing with the error 'vmware  has encountered an error and has shutdown windows'. This happens since last week april 3 and started with once a day, but now it crashes just (20-30seconds) after starting the VM. It seems to work longer after stopping Fusion and start it again or restart my MacBook Pro(2017).

In the vmware.log file I found the following messages:

2019-04-09T09:38:46.646+01:00| mks| I125: Msg_Post: Error

2019-04-09T09:38:46.646+01:00| mks| I125: [msg.log.error.unrecoverable] VMware Fusion unrecoverable error: (mks)

2019-04-09T09:38:46.646+01:00| mks| I125+ MKS MacOSKeyboard: Keyboard thread failed to respond to ungrab request

2019-04-09T09:38:46.646+01:00| mks| I125: [msg.panic.haveLog] A log file is available in "/Users/Stefan/Documents/Virtual Machines.localized/MBPW10x64.vmwarevm/vmware.log". 

2019-04-09T09:38:46.646+01:00| mks| I125: [msg.panic.requestSupport.withoutLog] You can request support. 

2019-04-09T09:38:46.646+01:00| mks| I125: [msg.panic.requestSupport.vmSupport.apple.menu]

2019-04-09T09:38:46.646+01:00| mks| I125+ To collect data to submit to VMware support, choose "Collect Support Information" from the "Help" menu.

2019-04-09T09:38:46.646+01:00| mks| I125+ You can also run "VMware Fusion Problem Reporter.tool" inside the VMware Fusion application bundle directly.

2019-04-09T09:38:46.646+01:00| mks| I125: [msg.panic.response] We will respond on the basis of your support entitlement.

2019-04-09T09:38:46.646+01:00| mks| I125: ----------------------------------------

I am running Fusion v10.1.6 (12989998), which I installed using the 'Check for upgrade' option in Fusion. This did not solve the issue.

My Mac is running v10.14.4

I have 3 VM's (MacOS,W7,W10) all of them crashes with the same error.

In the attachment I added the vmware.log file, hopefully this will help finding the solution.

Thanks,

Stefan

0 Kudos
1 Reply
Stefan007
Contributor
Contributor

I just upgraded to v11.0.3, but this did not solve the issue

0 Kudos