My 15" Retina MacBook Pro has spent more than half its waking hours running a Win 7 Enterprise Fusion 6 VM (encrypted by Credant whole disk encryption), with the host Mac OS being 10.9.x "Mavericks." The new connectivity between Mac and iOS devices in Mac OS 10.10 was enough to trigger me to upgrade my host OS, but after I did so I've had graphics anomalies while running the VM in full screen mode. For example, the screen "flashes" if I push the cursor to the top of the screen, just before the menubar of the host Mac OS slides into view, and it flashes once again when I pull the cursor back down from the top of the screen after the Mac menubar has disappeared.
Because the promotional materials for Fusion 7 state that it improves graphics performance for retina display Macs, I decided to install the trial version of Fusion 7 and see if these annoying glitches really would be banished. However, when I tried to use a copy of my functional Windows 7 VM that had worked just fine in Fusion 6/Mavericks in Fusion 7/Yosemite, the Windows boot process hung at the pulsing Windows logo.
I wondered if the reason for this was that the Credant whole disk encryption was somehow preventing my VM from booting because the updates applied to make the VM compatible with Fusion 7 had somehow triggered Credant's encryption security. Our IT consultant obtained a utility for me to uninstall the encryption. The decrypted Fusion 6 VM runs in Yosemite (with the above-described graphics anomalies still present). However, when I tried to run this VM in Fusion 7, the boot process hung at exactly the same spot (pulsing Windows logo). If I shut down the VM at that point (using the commands in the Fusion 7 Mac Menubar, since no GUI is available within the "stuck" Windows VM display), I'm sometimes presented with a black/white screen that offers to run "Windows Startup Repair", but that utility doesn't run; selecting it basically leads recursively to the same choice screen, and selecting the other choice ("Start Windows Normally") reboots the VM but the boot process hangs again at the same point (pulsing Windows logo).
I've noticed that when I open a VM file from Fusion 6 for the first time in Fusion 7, I'm offered a choice to update the VM file for Fusion 7 or not to update the file. I haven't tried selecting the latter choice. Is it possible that doing so would allow the VM to boot to completion, after which I could install the updated VMware Tools and do whatever housekeeping is needed? Any other ideas why a VM that runs in Fusion 6 can't be run in Fusion 7?
Thanks so much for any suggestions,
Jim Robertson