+1 with this issue. Not impressed as 5.0.1 was rock solid, but 5.0.2 is buggy. Windows has crashed and had to restart about 3 times already when using Office 2010 apps and I've only had it installed for one hour. I think it appears to be related to Unity.
I retract my speculative comment that it was related to Unity. The same crash is happening in Full Screen as well.
What I did find is another communities thread regarding Fusion 5.0.2 is crashing out a VM but in a seemingly unrelated scenario. I've tried the same fix as stated in this thread, and the problem has gone away.
Quote: With your VM powered off, go into the Virtual Machine > Settings, then choose Display, and turn off theAccelerate 3D Graphics option. Then close the Settings window and try to power on your VM.
Hi Vlad, and welcome to the VMware Communities!
Your crash is the same as several others we've seen in the last day or so.
As fishtanked has already suggested, you should try the workaround from the other thread: With your VM powered off, go into the Virtual Machine > Settings, then choose Display, and turn off the Accelerate 3D Graphics option. Then close the Settings window and try to power on your VM.
It is most unfortunate for us that the release of Fusion 5.0.2 coincided with the release of the Apple Software Update which has brought about this problem! :smileyangry:
We'll continue to investigate through our internal bug report, and hopefully we'll soon figure out how to fix this problem.
I'm seeing a similar problem with 5.0.2 and windows 7 with a Lion host.. I get BSOD on boot.
Tried turning off 3D acceleration as described above but no luck.
I really don't think it's appropriate to put the blame on Apple's update ... The same is happening to me. However, I applied the Apple update and had no issues with Ubuntu 12.10 until I updated to VMWare Fusion 5.02. So, I was running 5.01 under Mountain Lion and with the Apple Software updates and This is not the type of thing that should happen on a minor maintenace update.
Where is someone explicitly and specifically blaming Apple for this? Nowhere that I can see! The issue is being looked into and for now the workaround is to disable the Accelerate 3D Graphics option until the issue is resolved!
Dariusd is blaming Apple and accentuating it with his Mad face. In any event, as I said, everything worked fine with Apple's updates. It was only after upgrading to Fusion 5.02 that everything broke.
Please be open to the possibility that there are multiple issues here.
There may be an issue with Fusion 5.0.2 that we're yet to figure out. I never said there wasn't, and have not been dismissive of those who've been willing to discuss and explore the issue.
What we know for sure is that there is absolutely an issue with the combination of MacBook Air and MacBook Pro Update 2.0 and Fusion 5.0.x. That includes both Fusion 5.0.1 and Fusion 5.0.2 You might have been lucky enough to avoid the symptoms until upgrading to Fusion 5.0.2. Lots of people have already incorrectly blamed Fusion 5.0.2 for this specific problem, and the information from the support bundles they've provided backs me up on my assessment.
I don't believe I ever blamed Apple for the problem, and if I did so, it was a slip and I apologise for doing so. The Apple's Software Update has made a problem apparent, manifesting as a crash of Fusion, and we do not yet have a root cause. I thought I'd been pretty clear that it might be a problem with the Software Update itself, or it may be that the Software Update has brought out a latent problem in Fusion. We don't yet know, and we're working on it as quickly as we can.
The mad face is at the bad luck that our update release coincided so neatly with the release of Apple's Software Update, which has led to this epic confusion!
If you have any questions about a problem you're encountering, feel free to upload your support bundle and I'll take a look.
I can't speak for Darius however I think your interpretation of what's being said is totally off base and wrong! In another thread on this issue, which you posted to as well, he explicitly and specifically states "We'll continue to investigate the problem to determine whether it is a defect in Fusion or a defect in the updated graphics driver from Apple." so I don't take his comments in this thread (or the other) to be that of one explicitly and specifically blaming Apple for this!
Message was edited by: WoodyZ
Darius... It seems clear that you are blaming Apple software and I was just lucky... Well, this same exact issue happend on a 2008 MacBook Pro which did not receive any software updates and others on the forum that have not received any Apple updates also are experiencing the proiblem only when 5.02 was in the mix. So, tell me how the Apple software update of which there was none for my 2008 MacBook Pro caused the issue when I upgraded to Fusion 5.02. Unless magic was involved how could that happen ? In any event, Apple releases software to developers prior to release. Did VMWare test with it. I think this finger pointing is not valuable as well. How can you say that VMWare was incorrectly blamed ? It is their software that was not tested appropriately and this is very clear. I am having issues on two very different Macs and they both only started having issues with a VMWare software update. So, how can you say that all us lowly customers are incorrect. That is leaving a bitter taste in my mouth. This should not be happening and it is very muchVMWare's responsibility,
Uhmmm... Did you even read the post to which you replied? Not to put too fine a point on it, but you seem to have ignored absolutely everything I wrote.
I did not ignore anything you wrote. And btw, software that I'm running on my Macs is not due to any luck or lack thereof and it's insulting to say otherwise.
@DallasJeff, if you like to contribute to the resolution of this or whatever issues you have with VMware Fusion then provide the support bundle from each of your affected systems either here or through proper support avenues otherwise go be a troll elsewhere!
I am trying to find the solution and am not the one blaming Apple. I merely pointed out that blaming Apple is inappropriate and anti productive and it is you WoodyZ that has resorted to name calling.
I am glad to have found this post but very annoyed that this is happening. I feel like I am in a beta software program.
Windows 8 VM crashes repeatedly....grrr.
From what you've said you do not appear to be asking for help with whatever VMware Fusion issues you're having and have only tried to make and continue to make an unfounded point about something Darius never said and doing so in a manner considered troll like so if the shoe fits as the saying goes...
If you're serious about wanting support then either file the appropriate support request or you can also try and get help here in the VMware Fusion community forum, which is not official support. However until you provide adequate details, which the support bundle usually does, then there is not much more to offer if you have the same issue then what has already been offered. You continuing to harp on Darius is unwarranted and counterproductive to the real issue at hand and disrespectful to the other members that have asked for help and supplied the support information!
And you must think you are adding value WoodyZ… SInce VMWare is blaming Apple's software update and i guess my "luck" for the issues that has to be addressed because part of of problem resolution also involves knowing the problem cause. If anyone is trolling ti seems to be you. What makes you pivotal to these discussions ?
I've already added far more value to this community then you probably ever will so I'm fine with what I've said here and since you want to continue to act delusional about something that was never said to begin with and also will not provide any relevant information that can be used to aid in the overall and ongoing diagnostic/troubleshooting process for this issue (or whatever VMware Fusion issue you have) I have nothing more to say to you and will not be baited any further by your now incessant trolling!
Can I please ask everyone to keep this thread related to this problem instead of pointing fingers to who did what