After any of my Windows VM's boot up, they freeze more often than not and I get an error that Windows has stopped responding and needs rebooted. I sometimes have to reboot 3 times before it will actually boot up and be usable.
This NEVER happened with previous versions of Fusion.
PLEASE FIX THIS BUG
thanks for letting us know its still broken but i'm assuming from the earlier response from vmware that the fix involves both sides so 8.5.2 may fix the fusion side and we need the next release of sierra to fix that side.
I can also confirm that Fusion 8.5.2 running on Sierra 10.12.1 did not solve the problem.
I use Fusion almost every day and following these 3 rules seems to have helped minimize my crashes to maybe 1 per week:
Have the same problem; intermittent crashes on resume. Use fusion all the time and always suspend the VM at the end of the day (use a large monitor, so want to preserve the screen layout). Crashing every few days on resume, i.e. starting up Fusion in the morning after I've re-connected the monitor to the MBP.
Obviously a VMWare feature. Hasn't happened on previous releases.
Fusion 8.5.2 running Windows 2012 r2, Sierra 10.12.1, MacBook Pro (Retina, 15-inch, Mid 2015, 2.8 GHz Intel Core i7)
Seems to be related to it being run in full screen.
- restore to run windows in a window (i.e. come out of full screen)
- suspend (close the window)
... time passes, Mac's slept, etc. ...
- Open the VM again in a window -- all OK
- maximise it - crash... "fusion encountered an error and we'll ruin your day..."
I updated to Mac OS to Sierra 10.12.1 and updated to Fusion 8.5.2 and the crashing is still happening. If I shut down the VM and have a fresh startup, it doesn't appear to crash for that session. The problem now only appears to be with restoring a suspended VM. It doesn't crash every time after restoring a suspended VM, but very often. I encounter the issue multiple time a day. With the 8.5.2 version you get a message that an error was encountered and the VM has to be restarted and a button is disabled to restart the VM.
Hmm, 8.5.3 also crashes.
I have copied my VmWare image to a new MacBook Pro and VmWare comes up exactly once. Then it crashes every time.
I can copy the disk image again, VmWare will start it once, ... this is a bit annoying, no problems whatsoever on the old Mac... currently have to run Parallels to be able to work and that does not make me happy.
I get this (looks very similar to the error in 8.5.2):
Process: VMware Fusion 
Path: /Applications/VMware Fusion.app/Contents/MacOS/VMware Fusion
Identifier: VMware Fusion
Version: 8.5.3 (4696910)
Code Type: X86-64 (Native)
Parent Process: ??? 
Responsible: VMware Fusion 
User ID: 501
Date/Time: 2016-11-30 07:35:12.800 +0100
OS Version: Mac OS X 10.12.1 (16B2659)
Report Version: 12
Anonymous UUID: A130FB91-D96E-1185-BCC3-55443A3E6AE9
Time Awake Since Boot: 1000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
*** multi-threaded process forked ***
crashed on child side of fork pre-exec
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fffeb956dda __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fffeba42787 pthread_kill + 90
2 libvmwarebase.dylib 0x000000010c804913 SigCoreDumpViaChild + 963
3 libvmwarebase.dylib 0x000000010c804ac7 Sig_CoreDump + 39
4 libvmwarebase.dylib 0x000000010c58966d Panic_Panic + 141
5 libvmwarebase.dylib 0x000000010c5897d2 Panic + 130
6 libvmwarebase.dylib 0x000000010c803d60 0x10c53e000 + 2907488
7 libsystem_platform.dylib 0x00007fffeba35bba _sigtramp + 26
8 ??? 0x000060000086f250 0 + 105553125110352
9 com.apple.CoreFoundation 0x00007fffd65c9d74 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
10 com.apple.CoreFoundation 0x00007fffd65c99ff __CFRunLoopDoTimer + 1071
11 com.apple.CoreFoundation 0x00007fffd65c955a __CFRunLoopDoTimers + 298
12 com.apple.CoreFoundation 0x00007fffd65c0f81 __CFRunLoopRun + 2065
13 com.apple.CoreFoundation 0x00007fffd65c0514 CFRunLoopRunSpecific + 420
14 com.apple.HIToolbox 0x00007fffd5b512ac RunCurrentEventLoopInMode + 240
15 com.apple.HIToolbox 0x00007fffd5b50fe9 ReceiveNextEventCommon + 184
16 com.apple.HIToolbox 0x00007fffd5b50f16 _BlockUntilNextEventMatchingListInModeWithFilter + 71
17 com.apple.AppKit 0x00007fffd41536cd _DPSNextEvent + 1093
18 com.apple.AppKit 0x00007fffd48ca830 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 2730
19 com.apple.AppKit 0x00007fffd414806d -[NSApplication run] + 926
20 com.apple.AppKit 0x00007fffd4112983 NSApplicationMain + 1237
21 com.vmware.fusion 0x000000010b1a73c5 0x10b19c000 + 46021
22 libdyld.dylib 0x00007fffeb828255 start + 1
I am so sorry about your issue.
Could you help me to collect some logs to find the root cause?
a. ~/Library/Logs/VMware Fusion/vmware-vmfusion.log
b. vmware.log inside VM bundle vmware.log
Thanks and Regards
I would like to confirm a couple of things with you:
1) You said the crash does not happen on your old Mac machine, but happens on your new Mac machine, what is the Mac OS version on your old Mac? What is the Mac OS version on your new Mac machine?
2) Is it a Fusion UI crash (Fusion quits with the VM's vmx process still running) or a vmx crash (Fusion still runs but the VM shut down abruptly)?
3) After the crash, please relaunch Fusion if needed, then click Fusion menu 'Help' > 'Collect Support Information' to collect all the logs that would be helpful for our developers to check the issue and attach the resultant .zip bundle.