MacOS 10.12.6 breaks Fusion

[haroldku]

This morning I installed the MacOs update to 10.12.6 and Fusion 8.5.8 no longer loads my VM's.

Eventually I get an "Internal Error"

[Mikero]

Does it persist after a reboot?

If so, does re-installing Fusion help?

[jwl2017]

Same problem.  Persists after reboot. Reinstalled with no improvement.

[Mikero]

Would either of you be able to post a log bundle so we can review?

(Help > Collect Support Information)

[JessieZhang · Accepted solution]

Hello haroldku,

Could you please try below steps to see if it can solve your problem?

1. Remove Fusion completely

2. Execute below commands:
    xattr -l ~/Downloads/VMware-Fusion-8.5.8-5824040.dmg

    xattr -dr com.apple.quarantine ~/Downloads/VMware-Fusion-8.5.8-5824040.dmg

3. Reinstall VMware Fusion from the dmg

[haroldku]

This fixed the problem ......Thanks

[HenryAZ]

Hello haroldku,

Could you please try below steps to see if it can solve your problem?

1. Remove Fusion completely

2. Execute below commands:
    xattr -l ~/Downloads/VMware-Fusion-8.5.8-5824040.dmg

    xattr -dr com.apple.quarantine ~/Downloads/VMware-Fusion-8.5.8-5824040.dmg

3. Reinstall VMware Fusion from the dmg

JessieZhang, this is very helpful, and did indeed fix the "Internal Error" problem for me on a 10.12.6 fresh install.

But I am curious, how did the VMware-Fusion-8.5.8-5824040.dmg image come to acquire this "com.apple.quarantine" extended attribute in the first place? 

Out of further curiosity, I ran xattr -l on all of my saved versions of Fusion 8.x, including 8.0, 8.0.1, 8.1, 8.1.1, 8.5, 8.5.1, 8.5.2, 8.5.3, 8.5.6, and 8.5.7, and they all have the com.apple.quarantine attribute.  I also ran the command on a random selection of other OSX software dmg's I have archived, and they all have it too.

[ColoradoMarmot]

Any code that's downloaded from the internet has that set - it's how Gatekeeper operates.

[HenryAZ]

Any code that's downloaded from the internet has that set - it's how Gatekeeper operates.

I have since figured that much out.  But my question remains about how that "fix" is necessary for Fusion, and isn't there some way VMWare can make it work without this hack.