Linker IT Software
Google
Web www.oraxcel.com
menubar-top-links menubar-top-rechts
Home Help Search Login
Welcome, Guest. Please Login.
SQL*XL: Database to Excel bridge litLIB: Excel power functions pack ExcelLock: Locking and securing your valuable Excel spreadsheets encOffice: Protect your Excel file easy and safe encOffice: Protect your Excel file easy and safe
Pages: 1
Changing msi installers to bypass installer checks (Read 20580 times)
Gerrit-Jan Linker
YaBB Administrator
*****




Posts: 75
Changing msi installers to bypass installer checks
07.08.10 at 17:32:08
 
Changing msi installers to bypass installer checks
 
Sometimes it can be handy to be able to change installers or setup packages. When checks are done if a particular browser is installed or whether you install on a certain windows version, you may want to bypass those checks. Especially when new versions come along these checks may fail as the version numbers are not what the original developers thought they would be.
 
First check whether the installer is a MSI installer. Run the setup or install package. Usually they unpack in the temporary directory. Point your windows explorer to %temp% to see the files it creates (you may want to clean the temp dir first so the new files are easier to locate). When there is a .MSI installer created it is usually sufficient that when the installer hangs on the check you wish to remove, to rename the folders in the temp directory so they will not be removed after the failed install. (You can copy them too of course.)
 
So now you have the msi file what can you do?  
Two things actually. You can download the orca tool and remove checks. Or you can play with options you give to the MSI installer itself.
 
Removing install checks from a MSI file:
Download and install the ORCA tool. This tool is a microsoft tool that allows you to edit the MSI file. Once Orca opens it will display a long list of categories. Select "CustomActions". Subcategories will now be displayed. You can delete an item by right clicking and selecting delete row.  
Save the MSI file and try the install again by double clicking the MSI file.
 
Play with MSI installer options:
The installer can be run with several options. Drop to the command prompt and go to the %temp% directory. Suppose the name of your installer is a.msi then type a.msi /?  
For me the list of options below appears.  
 
To bypass my particular check (a check for .Net version 1.1) I chose to run the MSI installer with option /passive which did the trick. I am running windows 7 and I am sure my .Net version is higher than 1.1:
a.msi /passive
 
Quote:
Windows Installer. V 5.0.7600.16385

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log <LogFile>
Equivalent of /l* <LogFile>
Update Options
/update <Update1.msp>[;Update2.msp]
Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]

Consult the Windows Installer SDK for additional documentation on the
command line syntax.

Copyright Microsoft Corporation. All rights reserved.
Portions of this software are based in part on the work of the Independent JPEG Group.

Back to top
 
« Last Edit: 07.08.10 at 17:33:17 by Gerrit-Jan Linker »  

Gerrit-Jan Linker
Linker IT Software
Email WWW Gerrit-Jan Linker   IP Logged
Gerrit-Jan Linker
YaBB Administrator
*****




Posts: 75
Changing msi installers to bypass installer checks
Reply #1 - 02.09.10 at 09:37:49
 
Changing msi installers to bypass installer checks
 
Probably using another msi installer version the above syntax did not work. I used the following to bypass the checks in the installer:
msiexec /package myfile.msi /passive
Back to top
 
« Last Edit: 02.09.10 at 09:42:58 by Gerrit-Jan Linker »  

Gerrit-Jan Linker
Linker IT Software
Email WWW Gerrit-Jan Linker   IP Logged
Pages: 1