Can’t install Virtual Machine Additions – Managing your servers can streamline the performance of your team by allowing them to complete complex tasks faster. Plus, it can enable them to detect problems early on before they get out of hand and compromise your business. As a result, the risk of experiencing operational setbacks is drastically lower.
But the only way to make the most of your server management is to perform it correctly. And to help you do so, this article will share nine tips on improving your server management and fix some problem about windows, virtual-machines, windows-installer, , .
I’ve got a virtual machine running Windows Server 2008 (client) on a Windows Server 2003 (host). I’m running Virtual Server 2005 R2 with SP 1. I can not install Virtual Machine Additions on the client. I’ve tried running via the ISO as well as copying the MSI to the client machine, but every installation attempt ends the same:
Setup was interrupted before Virtual Machine Additions could be completely installed.
I’ve tried uninstalling previous versions of VMA but the uninstall never works either.
I’ve tried altering safe mode to allow for uninstalls and that fails, I’ve tried safe mode installation and that fails. I’m running as administrator.
Did you check the installer log file? Start the installation using:
msiexec.exe /i yoursetupfile.msi /lvoicewarmupx logfile.txt
After installation, search the log file for errors and warnings.
(Note: you obviously need write permissions for the path to log file)
I presume you already googled for 1603, but here are some notes (found on MSDN) anyway:
You may receive this error message if any one of the following conditions is true:
- The folder that you are trying to install the Windows Installer package to is encrypted.
- The drive that contains the folder that you are trying to install the Windows Installer package to is accessed as a substitute drive.
- The SYSTEM account does not have full control permissions on the folder that you are trying to install the Windows Installer package to. You notice the error message because the Windows Installer service uses the SYSTEM account to install software.
Some additional information can be found on InstallShield site (although your installer is not InstallShield based):
- Short file name creation is disabled on the target machine.
- An InstallScript custom action is prototyped incorrectly.
- Some file is locked and cannot be overwritten.
- The Microsoft Windows Installer service is not installed correctly.
- The Windows Temp folders are full.
- File and Printer sharing is not enabled or was not installed when installing Windows.