I'm running Windows 7 64-bit and I'm trying install VMware Player 4.0.3.
I get an error:
The MSI 'C:\users…..\Local\Temp\vmware_1338456060\vmwarevmcisockets64.msi' failed.
I had installed this previously, and had to uninstall the application. This attempt was a re-install.
Best Answer
Documenting VMware Player 4.0.2 Install on a Windows 7 64-bit Host OS
Hurdle #1 Getting the installer to work:
C:\Temp
if it doesn't already exist. Delete everything in there and put the self-extracting executable in it. In my case the file is called VMware-player-4.0.2-591240.exe. Open up your command prompt(Start->Run->cmd.exe)
and then navigate to the folder where the .exe file is located by typingcd C:\Temp
. Then type thisC:\Temp>VMware-player-4.0.2-591240.exe /e
C:\Temp\VMware-player-4.0.2-591240.exe
. This creates a folder insideC:\Users\%username%\AppData\Local\Temp\vmware_%random_number%
. (In my case this is where installation stopped prematurely) copy this folder\vmware_%random_number%
intoC:\Temp\
folder.msiexec
with/qn
option [/q Sets User Interface level /n Sets it to None] was what did it for me so don't mess with these options. Player will "quietly" install and you won't even know it's there until you check your Start menu.Hurdle #2 Getting VMPlayer to run the ISO image:
Of Course it didn't end there!!! There was one other error I was getting when I tried to install CentOS_64-bit from an ISO image. This error below:
Could not get vmci driver version: The handle is invalid. You have an incorrect version of driver "vmci.sys". Try reinstalling VMware Workstation. Module DevicePowerOn power on failed.
C:\Program Files(x86)\VMware Player
folder as well asC:\Windows\System32\drivers
vmci0.present = false
.This sums up 4 Hours of my life I will never get back, but now I have a VMware Player up and running on my Windows 7 64bit system. Hope this helps...
PS: If and when you get a notification from VMWare player to update/upgrade to a newer version you will not be able to do so because the installation/upgrade package is still broken. Possibly uninstalling the current version and reinstalling using the new file following the steps from above might help you resolve the issue.