I have made a new package with WPS 6.0 for the vendor MCL LINK Installshield setup. I deployed the new package by GPO to one of my test computers. At first the package seems to install oke. But after some testing, i noticed that every time the application is started by a different user a msi repair starts.

The package validation showed some ICE03 (invalid format string), ICE38 (component install in user profile) and ICE64 (directory is in user profile but is not listed in the removeFile table) errors. I checked this forum and found a post stating that this problem may be caused by a msi inside the installshield setup.

I monitored the installation from the Installshield setup with procmon and noticed the following:
-the installation starts by copying files from the setup file to the installdir and to the "common file" dir
-when all files are in place, another setup is started which installs some files and starts a msi file to install some drivers
-after that, a commandbox is open to execute "netsh exec" to set some firewall setting

I have little experience with repackaging applications, and no experience with repackaging Installshield setup files. I tried to extract the files from the setup, but was unsuccessful. So, any ideas how to handle this will be appreciated.

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


If a package contains any user-level components (i.e. anything which gets put into the user profile, either file- or registry-wise) then the repair/self-heal behaviour is by design.
Answered 04/15/2009 by: VBScab
Red Belt

Please log in to comment
Well yes, it is generally not a great idea to repackage something you know contains an embedded MSI.

Perhaps you could try the UniExtract utility available for download at


to see if you can extract the files - I have had reasonably good results using this utility with InstallShield setup.exe files.

Assuming extraction is possible, you might want to try installing the driver MSI first and then perform the repackage capture and then consider deploying this as two MSI's (one for the main application and the other for the drivers).


Answered 04/15/2009 by: spartacus
Black Belt

Please log in to comment
I will give uniextract a try.

I have one more question about the repair/self-heal. I red in some posts, that in order to keep the repair time as short as possible one can move the components causing the repair into a separate feature. How or where can i see which components are causing the repair?
Answered 04/15/2009 by: TalkingMarble
Orange Belt

Please log in to comment
The Event Viewer's Application log will detail the component ID. You can then find that ID in the 'Component' table.
Answered 04/16/2009 by: VBScab
Red Belt

Please log in to comment
In case you didnt get chance to read this post I am forwarding you the link:
There is detailed information given in this post on how to structure components so repair/per user configration will be quick.
Answered 04/16/2009 by: raviray
Orange Belt

Please log in to comment