Link to home
Start Free TrialLog in
Avatar of eelou
eelou

asked on

MSIEXEC\windows Installer and Server 2008 R2, problem uninstalling

I have a BASIC MSI (IS 2010 Pro).  It does an upgrade of a product and the removal of a previous version.  Problem is that (before my time), there are two installed products that have the same upgrade code, so, the upgrade table cannot be used as it will uninstall both products.  So I am executing a 'VBscript (msiexec /x [guid} /qn' (tried createprocess and execute shell, but get the message about another installer already running).  This works fine on windows 7, but not on Server 2008 R2.  On the R2 system, the log shows the Vbscript is executed with a Return value of 1), and the uninstall does not happen.  If executed from the command line (with the '/qn'), this works ok, double clicking on the MSI, it does not uninstall the previous version.  If I remove the '/qn', and respond to the user prompts when it executes the vbscript (executing by double clicking the msi file), the previous product is uninstalled when done.  What is gong on on the R2 server?
SOLUTION
Avatar of Vadim Rapp
Vadim Rapp
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of eelou
eelou

ASKER

More research, and as as of yet an unexplained problem.  On systems that I tested that did  not have Macafee installed, there was no problem.  On systems that have Macafee 8.7, or 8.8, the problem happens (the previous installer is not uninstalled)
Avatar of eelou

ASKER

Is is because the parent MSI is using a VBScript\MSIEXEC to do the uninstall of the previous product?
Most virus software implementations do not block VBscript custom actions - but your suspicion could be correct in this case - some virus software sandboxes vbscript at a very low level.

If you could create a verbose log of the failing uninstall, zip it and upload it to this thread I can take a look for you.

Instructions for verbose logging are here: https://www.experts-exchange.com/Programming/Installation/A_5177-Installation-Logging-How-To-Create-a-Verbose-Windows-Installer-Log-and-Submit-it-With-Your-Question-Including-MSIs-That-are-INSIDE-Setup-exes.html

Please follow the instructions rather than use the /L command line as the registry file in the article ensures the maximum log content is captured.
eelou, if these two questions are parts of the same project, maybe it would be more effective if you tell us the big picture, what is the whole thing, and then maybe we would come up with coherent solution from start to finish, rather than addressing small pieces.

For example, if the objective is to remove specific installations of McAfee and then install another product, maybe it's easier to uninstall McAfee from logon or machine start script, and then install product #2 clean, perhaps with condition based on system search ensuring that McAfee is gone - rather than mess with these ten different ways to run vbscripts from ten different places.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
> We cannot ask customers to downgrade or remove their Virus protection

I think, if you re installing another antivirus product, then it's absolutely OK to do. Many antivirus products block the attempt to disable or remove them in general, not only by installation script, but by any means other than their own interface, especially programmatic means - and for a good reason, because it's very likely that malware would try to uninstall the antivirus. For the user who has such a product with this protection activated, it's expected that your installation will definitely fail as soon as it tries to remove that product; it's by design (of that product).
Avatar of eelou

ASKER

I was the one that found that the problem was being caused by McAfee.