Manually remove Fusion 10.11.1 from Mac

[gangelo]

I wanted to uninstall and reinstall Fusion on my Mac because I believe something got corrupted. I followed these instructions laid out here and downloaded/reinstalled Fusion 10.1.1. When I started up what I thought would have been a clean install, Fusion jumped right into my existing VM and seems to contain the exact same Fusion settings as the previous install. Something doesn't seem right. How do I remove EVERYTHING from a previous install (minus the VM)????

[Mikero]

So, you deleted the 'preferences' file in ~/Library/VMware Fusion/ ?

and the folder /Library/Application Support/VMware/VMware Fusion/ ?

That's it, there isn't any other files on your system that record the library or contents outside of the VM itself.

THAT BEING SAID... it's possible that we're just reading your VM which is in the default directory when we launch Fusion (which we do).

The VM is not attached to the Installation of Fusion. You can equate it to Microsoft Word (Fusion) vs. a Word Document (your VM).

So if you re-launch it after re-installing Fusion, the VM (and it's settings) is going to be the same as before you re-installed.

Is there a particular indication that something got 'corrupted'?

Errors? Logs? Crashes?

[gangelo]

"Is there a particular indication that something got 'corrupted'?

Errors? Logs? Crashes?"

TBH, there are more than a few error logs on the VM itself (/var/log) as well as in the VM file itself with a lot of things that look suspicious. In particular, EE errors to the effect that there's nothing available to display the UI. All this took place after resizing the VM disk for some reason, so I'm a little perplexed by it especially in light of the fact that the hd looks good when I ssh into the guest o/s. I spent 2 days trying to find answers and trying to fix it. In the end, I downloaded VirtualBox, extracted the hd, and everything works fine after installing the VirtualBox guest package.

So...I imagine this has something to do with the vmware virtual video drivers - somehow they've gotten corrupted, removed, who knows.

If there's a simple way to reinstall them, I'd give it a try, but the only thing I could think of is reinstalling open vm tools which I did and it didn't fix the issue.