I'm beginning to wonder if VMware Fusion has been pushed to the back burner.
Since upgrading from Fusion Professional 5 to Fusion Professional 6 when I upgraded to Mavericks several months ago, I've had two glaring issues with both my Windows 7 x64 and Windows XP x86 VMs.
Whenever I launch VMware Fusion and select a VM to open in full screen, the menu bar appears at the top of the VM window but it is all gray. There is no text. The menu bar persists at the top of the VM window after the VM is powered on and only goes away if I shrink the VM window down from full screen and then make it full screen once again. While the gray menu bar is visible, I can left click on it and get the traditional menus to appear. I also encounter this same problem if a VM is already running and I wake my MacBook Pro up from sleep. I always run my VMs on an external monitor, if that makes any difference.
The other issue is that I Fusion 6.0.2 doesn't seem to remember USB settings. In Fusion 5, I was able to go into the preferences for each VM and see each of my USB devices and tell it to either "Connect to Windows", "Connect to Mac" or "Ask What to Do". I have a USB dongle that a software I use requires. Every time I boot up the VM that contains this software (XP x86), I have to go to the Virtual Machine menu, down to USB, and click "Connect Aladdin USB Key". It connects right away but as soon as I shut down XP and power it back on, it doesn't remember to connect the USB dongle again. I've checked and re-checked my USB settings for the XP VM. The USB dongle is set to "Connect to Windows" but it refuses to automatically connect when I power on the VM. It used to work just fine.
I've attached two screenshots of the gray menu bar bug. I first mentioned it in these forums months ago but it has yet to be fixed. I think someone mentioned in my original post about the gray menu bar that it was a Mavericks bug; but I haven't encountered the bug with any other software I run full screen in Mavericks. That leads me to believe that it is, in fact, a VMware Fusion bug. I'm wondering if anyone else out there is encountering the same problems I'm having?