Hi EcoEric,
Which version of Fusion are you running? The workaround only applies to Fusion 4.1.0 or 4.1.1; we have not prepared a workaround for earlier versions of Fusion.
Depending on how this failure situation is occurring (which, as HPReg stated, we don't yet fully understand), it might be necessary to restart your host system once after installing the workaround. All we know is that something on affected hosts is preventing our kernel extension from unloading and reloading in the normal way... and that means that it might not be possible for us to unload the existing (sans-workaround) kernel extension and load the workaround-enabled one without a restart of the host to clear out the old "stuck" kext.
Cheers,
--
Darius
