This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- .msu files as suite packages?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 30, 2011
10:47 AM
.msu files as suite packages?
I am attempting to convert all the the prerequisites in my current installer into packages in a new suite project. Some of these (namely Windows installer 4.5 for Vista) are actually packaged as .msu files. I don't see any way of including a .msu file as a package file. Is there a way to do this?
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 03, 2012
02:40 PM
Hi There,
I would look into using ShellExecute.exe to invoke the *.msu file (which will in turn open it up with wusa.exe, a system component):
http://www.optimumx.com/downloads.html#ShellExecute
There's always other similar wrappers out there if you have problems, or even the capability to author your own wrapper as well.
Hope this helps!
--Cary
I would look into using ShellExecute.exe to invoke the *.msu file (which will in turn open it up with wusa.exe, a system component):
http://www.optimumx.com/downloads.html#ShellExecute
There's always other similar wrappers out there if you have problems, or even the capability to author your own wrapper as well.
Hope this helps!
--Cary
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 04, 2012
08:54 AM
The advice above is fine, but I'd probably just specify [SystemFolder]wusa.exe as the target of an exe package containing the .msu file.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 10, 2012
01:37 PM
Thank you Michael. Your approach did work for me once I played around with it a bit. Since I couldn't add just an .msu file as the only file in a package, I had to add a bogus .exe file, add the adjacent files (the .msu file) and then delete the bogus .exe. I defined the operations as follows:
Target: [SystemFolder]wusa.exe
EXE Command Line: "[ISPREREQDIR]\Windows6.0-KB958655-v2-x86.msu" /quiet /norestart
EXE Silent Command Line: "[ISPREREQDIR]\Windows6.0-KB958655-v2-x86.msu" /quiet /norestart
Exit Behavior: Ask whether to continue the setup
Reboot Request: Prompt, then exit or reboot the machine
Reboot Codes: 3010,8192,1641
Target: [SystemFolder]wusa.exe
EXE Command Line: "[ISPREREQDIR]\Windows6.0-KB958655-v2-x86.msu" /quiet /norestart
EXE Silent Command Line: "[ISPREREQDIR]\Windows6.0-KB958655-v2-x86.msu" /quiet /norestart
Exit Behavior: Ask whether to continue the setup
Reboot Request: Prompt, then exit or reboot the machine
Reboot Codes: 3010,8192,1641