VMware-Fusion-2.0.4 Upgrade Fail / Don't Bother Downloading

[peacekeeper]

I just downloaded "VMware-Fusion-2.0.4-159196-light.dmg" and tried to upgrade from version 2.0.2. The installation hangs immediately and fails to progress any further. Viewing the install log shows that the installer fails to unload the kernel extensions from the previous version after which installation stops. Below you will find my attached log file. I tried this twice, and both times produced the same result. The second time was after a clean reboot and the first thing I did was try to install vmware. Also, I assume that this is the same for the non-light version (the version without the anti-virus bloat). Since this is the second upgrade to vmware fusion in about 10 days, I assume that there was a problem with 2.0.3? No change log has been posted for 2.0.4 so there is no way to know what it is trying to fix. Perhaps it is necessary to upgrade to 2.0.3 before upgrading to 2.0.4 however this has not been the case in past versions of vmware fusion. Since I am upgrading directly from 2.0.2, perhaps someone else can tell us in the comments whether upgrading from 2.0.3 works. My suggestion is to wait for 2.0.5 before upgrading because 2.0.4 appears dead on arrival.

-

---

LOG----

---

Apr 9 23:38:38 GITS /System/Library/CoreServices/Installer.app/Contents/MacOS/Installer[178]: vm_protect: 0

Apr 9 23:38:38 GITS Installer[178]: @(#)PROGRAM:Install PROJECT:Install-387

Apr 9 23:38:38 GITS Installer[178]: @(#)PROGRAM:Installer PROJECT:Installer-281

Apr 9 23:38:38 GITS Installer[178]: Hardware: MacBookPro3,1 @ 2.20 GHz (x 2), 4096 MB RAM

Apr 9 23:38:38 GITS Installer[178]: Running OS Build: Mac OS X 10.5.6 (9G55)

Apr 9 23:38:38 GITS Installer[178]: Env: PATH=/usr/bin:/bin:/usr/sbin:/sbin

Apr 9 23:38:38 GITS Installer[178]: Env: TMPDIR=/var/folders/4N/4NqPIB3rGkaXXB8tDCmLg++++TI/-Tmp-/

Apr 9 23:38:38 GITS Installer[178]: Env: SHELL=/bin/bash

Apr 9 23:38:38 GITS Installer[178]: Env: HOME=/Users/peacekeeper

Apr 9 23:38:38 GITS Installer[178]: Env: USER=peacekeeper

Apr 9 23:38:38 GITS Installer[178]: Env: LOGNAME=peacekeeper

Apr 9 23:38:38 GITS Installer[178]: Env: DISPLAY=/tmp/launch-i8kywp/:0

Apr 9 23:38:38 GITS Installer[178]: Env: SSH_AUTH_SOCK=/tmp/launch-xW17iW/Listeners

Apr 9 23:38:38 GITS Installer[178]: Env: Apple_PubSub_Socket_Render=/tmp/launch-wgHw5i/Render

Apr 9 23:38:38 GITS Installer[178]: Env: COMMAND_MODE=unix2003

Apr 9 23:38:38 GITS Installer[178]: Env: SECURITYSESSIONID=b06220

Apr 9 23:38:38 GITS Installer[178]: Env: __CF_USER_TEXT_ENCODING=0x1F5:0:0

Apr 9 23:38:38 GITS Installer[178]: VMware Fusion Installation Log

Apr 9 23:38:38 GITS Installer[178]: Opened from: /Volumes/VMware Fusion/Install VMware Fusion.app/Contents/Resources/Install VMware Fusion.pkg

Apr 9 23:38:41 GITS Installer[178]: fileURLForURL = x-disc://VMware%20Fusion/Install%20VMware%20Fusion.app/Contents/Resources/Install%20VMware%20Fusion.pkg

Apr 9 23:38:41 GITS Installer[178]: fileURLForURL = file://localhost/Volumes/VMware%20Fusion/Install%20VMware%20Fusion.app/Contents/Resources/Install%20VMware%20Fusion.pkg

Apr 9 23:38:41 GITS installdb[188]: started (uid 96)

Apr 9 23:38:41 GITS installdb[188]: Opened receipt database on '/' with schema 17.

Apr 9 23:38:44 GITS Installer[178]: Found receipt (full match) for (Install VMware Fusion / com.vmware.vmware.application): (Install VMware Fusion / com.vmware.vmware.application)

Apr 9 23:38:47 GITS installdb[188]: done. (0.006u + 0.007s)

Apr 9 23:38:51 GITS runner[201]: Administrator authorization granted.

Apr 9 23:38:51 GITS Installer[178]: ================================================================================

Apr 9 23:38:51 GITS Installer[178]: User picked Standard Install

Apr 9 23:38:51 GITS Installer[178]: Choices selected for installation:

Apr 9 23:38:51 GITS Installer[178]: Upgrade: "VMware Fusion"

Apr 9 23:38:51 GITS Installer[178]: Install VMware Fusion.pkg : com.vmware.vmware.application : 2.0.4.2.0

Apr 9 23:38:51 GITS Installer[178]: ================================================================================

Apr 9 23:38:51 GITS Installer[178]: It took 0.00 seconds to summarize the package selections.

Apr 9 23:38:51 GITS Installer[178]: -[IFPKGDerivedDocument sortedPackageLocations]: result = (\n file://localhost\n)

Apr 9 23:38:51 GITS Installer[178]: -[IFDInstallController(Private) _buildInstallPlan]: location = file://localhost

Apr 9 23:38:51 GITS Installer[178]: -[IFDInstallController(Private) _buildInstallPlan]: file://localhost/Volumes/VMware%20Fusion/Install%20VMware%20Fusion.app/Contents/Resources/Install%20VMware%20Fusion.pkg

Apr 9 23:38:51 GITS Installer[178]: _installNextPackage of 1

Apr 9 23:38:52 GITS installdb[205]: started (uid 96)

Apr 9 23:38:52 GITS installdb[205]: Opened receipt database on '/' with schema 17.

Apr 9 23:38:52 GITS Installer[178]: Found receipt (full match) for (Install VMware Fusion / com.vmware.vmware.application): (Install VMware Fusion / com.vmware.vmware.application)

Apr 9 23:38:52 GITS Installer[178]: Starting installation:

Apr 9 23:38:52 GITS Installer[178]: Preparing volume "Mac" for installation

Apr 9 23:38:52 GITS Installer[178]: Configuring volume "Mac"

Apr 9 23:38:53 GITS Installer[178]: Preparing disk for local booted install.

Apr 9 23:38:53 GITS Installer[178]: Free space on "Mac": 168 GB (180520464384 bytes).

Apr 9 23:38:53 GITS Installer[178]: Create temporary directory "/private/tmp/Install VMware Fusion.pkg.178Q3tNu7"

Apr 9 23:38:53 GITS Installer[178]: run preflight script for VMware Fusion

Apr 9 23:38:53 GITS runner[201]: preflight[206]: + export PATH=/bin:/sbin:/usr/bin:/usr/sbin

Apr 9 23:38:53 GITS runner[201]: preflight[206]: + PATH=/bin:/sbin:/usr/bin:/usr/sbin

Apr 9 23:38:53 GITS runner[201]: preflight[206]: + LIBDIR='/Library/Application Support/VMware Fusion'

Apr 9 23:38:53 GITS runner[201]: preflight[206]: + ''

Apr 9 23:38:53 GITS runner[201]: preflight[206]: + '/Library/Application Support/VMware Fusion/boot.sh' --stop

Apr 9 23:38:53 GITS runner[201]: preflight[206]:

Apr 9 23:38:53 GITS runner[201]: preflight[206]: VMware Fusion 147997: Shutting down VMware Fusion:

Apr 9 23:38:53 GITS runner[201]: preflight[206]:

Apr 9 23:38:53 GITS runner[201]: preflight[206]:

Apr 9 23:38:53 GITS runner[201]: preflight[206]: No matching processes were found

Apr 9 23:38:53 GITS runner[201]: preflight[206]:

Apr 9 23:38:53 GITS runner[201]: preflight[206]: No matching processes were found

Apr 9 23:38:53 GITS runner[201]: preflight[206]:

Apr 9 23:38:53 GITS runner[201]: preflight[206]: No matching processes were found

Apr 9 23:38:53 GITS runner[201]: preflight[206]:

Apr 9 23:38:53 GITS runner[201]: preflight[206]: kextunload: unload id com.vmware.kext.vmcrosstalk failed (result code 0xe00002c2)

Apr 9 23:38:53 GITS runner[201]: preflight[206]:

Apr 9 23:38:53 GITS runner[201]: preflight[206]: kextunload: unload id com.vmware.kext.vmmon failed (result code 0xe00002c2)

Apr 9 23:38:53 GITS runner[201]: preflight[206]:

Apr 9 23:38:53 GITS runner[201]: preflight[206]: kextunload: unload kext /Library/Application Support/VMware Fusion/kexts/vmmon.kext succeeded

Apr 9 23:38:53 GITS runner[201]: preflight[206]:

Apr 9 23:38:58 GITS installdb[205]: done. (0.004u + 0.003s)

[WoodyZ]

I had no problems going directly from Fusion 2.0.2 to Fusion 2.0.4!

Did you validate the VMware-Fusion-2.0.4-159196.dmg and or VMware-Fusion-2.0.4-159196-light.dmg disk image files against the published checksums?

VMware-Fusion-2.0.4-159196.dmg

(md5sum:5b63c7ca402588bda6aa590a26d29adf)

(sha1sum:e575ada73da996bd00b880ae2d0bfcef2daf9f8e)

VMware-Fusion-2.0.4-159196-light.dmg

(md5sum:689eaf46746cdc89a595e0ef81b714b3)

(sha1sum:46300075feb00df099d5272b984f762416d33791)

Click for information about using MD5 checksums and SHA1 checksums.

If the checksums match then try the following...

Reboot the Host and do not start Fusion.

In a Terminal (/Applications/Utilities/Terminal) copy and paste the following command and press Enter then type in your password and then press Enter.

sudo '/Library/Application Support/VMware Fusion/boot.sh' --stop 

After the prompt returns then mount the validated .dmg disk image file and make sure that you only have one mounted and showing on the Desktop.

Try installing now.

Another option is to uninstall the currently installed version and reboot the Host afterward and then try installing again. Note: Uninstalling Fusion does not remove ones Virtual Machines.

Also it is not necessary to have Fusion 2.0.3 installed to update to Fusion 2.0.4 from Fusion 2.0.2.

==========

WoodyZ - VMware vEXPERT 2009

[trodemaster]

No problems updating my home system from 2.0.3 to 2.0.4 tonight. VMware tools version that installed is 7.9.3 build-159196.

[peacekeeper]

Sorry, I forgot to mention that I did check the md5 hash values and they matched exactly so it was a "good" download.

[peacekeeper]

Also, I am aware that it is an option to uninstall 2.0.2 and then clean install 2.0.4 however I never had to do that for any of the other upgrades.

[peacekeeper]

I ran the terminal command

sudo '/Library/Application Support/VMware Fusion/boot.sh' --stop

and it would appear that the problem is specific to my installation. Trying to stop fusion using the above line gives the exact same problem. As you can see, the kernel extensions cannot be unloaded. Below is my output from the terminal after running the command.

VMware Fusion 147997: Shutting down VMware Fusion:

No matching processes were found

No matching processes were found

No matching processes were found

No matching processes were found

kextunload: unload id com.vmware.kext.vmcrosstalk failed (result code 0xe00002c2)

kextunload: unload id com.vmware.kext.vmmon failed (result code 0xe00002c2)

kextunload: unload kext /Library/Application Support/VMware Fusion/kexts/vmmon.kext succeeded

kextunload: unload kext /Library/Application Support/VMware Fusion/kexts/vmci.kext succeeded

kextunload: unload kext /Library/Application Support/VMware Fusion/kexts/vmioplug.kext succeeded

kextunload: unload kext /Library/Application Support/VMware Fusion/kexts/vmnet.kext succeeded

[WoodyZ]

Also, I am aware that it is an option to uninstall 2.0.2 and then clean install 2.0.4 however I never had to do that for any of the other upgrades.

Just because you haven't had to do it in the past doesn't mean that you will never have to do it that way ever in the future and if you don't want to try as I suggested that's fine just do as you want then.

[Proconsul]

Version 2.0.4 installed normally over 2.0.3 - no problems. VM Tools also updated without incident......

I see no problems with this version so far - perhaps after perusing the yet to be provided release notes, we can get "specific"......

[WoodyZ · Accepted solution]

Then I'd suggest you uninstall Fusion 2.0.2 or whatever version you have installed, reboot and then install Fusion 2.0.4 otherwise you can remove the "/Library/LaunchDaemons/com.vmware.launchd.vmware.plist" file and then reboot and then the Fusion Kernel Extensions and VMware Virtual Network will not be loaded and then try installing however I'd just uninstall, reboot and install and be done with it as it's just not a big deal and on takes a few minutes.

[peacekeeper]

Fine, I uninstalled 2.0.2 followed by an install of 2.0.4 which was successful.

Note however that this should not be necessary for such a minor revision and an upgrade should work. It is perfectly understandable for a large version change such as migrating from 1.0 to 2.0 but going from 2.0.2 to 2.0.4, you should not have to uninstall/reinstall. Since this is my production system, I would rather keep a stable system that works (patching as necessary) rather than completely uninstalling my software packages as minor sub-sub- versions are released just so that I can upgrade. Complete overkill for a minor bug patch. But that is just my opinion.

[WoodyZ]

First of all I don't disagree with some of what you said, in principle anyway, however what you may not realized or understand is that the Fusion Installer completely uninstalls the previous version before installing the current one being installed so if one has to manually uninstall a previous version minor or major for that matter for whatever the reasons it's just not a big deal and frankly you're just making a big deal out of it for nothing. Also if this is your "production system" then maybe you shouldn't be messing around with minor release and I certainly wouldn't be installing any release of anything on a production system until it's been out for a while and have gathered feedback from the community by looking to see what the know issues are and what issues others are having as well before implementing it myself.

[admin]

Since this is the second upgrade to vmware fusion in about 10 days, I assume that there was a problem with 2.0.3?

My understanding is that 2.0.4 addresses a security problem (not specific to 2.0.3). The release notes will probably be out soonish.

[danielsan1701]

Had an install hang going from 2.0.3 to 2.0.4.

Woody's method worked for me.