http://www.macfixit.com/article.php?story=20070810124707771
Can Vmware team confirm this??
No problems with it here on a brand new 2.2 Ghz MacBook Pro.
Eek. I just updated last night to fix my unresponsive keyboard problem and now i have this. Bummer. That sounds exactly like what is going on now.
That article is sooo old. Back in August, lots has changed since then. Make sure you're running Fusion 1.1 and you'll be fine.
Well those are the symptoms my machine was experiencing today running fusion 1.1 after installing the macbook pro update 1.1
I tried clearing the kext cache as the article suggested. I will be back if the problem continues; otherwise you may assume things are once again hunky dory.
I have access to two MacBook Pros that I've applied the 1.1 "keyboard" update to, one Core Duo and one pre-SR Core2 Duo with no problems. It's possible cached kernel extensions may need refreshing after an update but this update is not conflicting with Fusion 100% of the time. This isn't a scientific sample, but I think a lot more people would be posting about problems here. I always run a Disk Utility permission check before rebooting after applying fixes (to avoid past issues) and I verify my disk about once a week to catch any latent disk errors.