Ajay Ladsaria wrote: Hi Jordan, It wasn't clear from your response whether you have applied the hotfix - so could you confirm if you have? If it doesn't resolve the issue, then we recommend contacting our support team. They should be able to work with you to try and reproduce and troubleshoot the problem. Since each installation package is different we would need to test with the one with which you are encountering the problem. Regards, Ajay Hi Ajay, I have applied the hotfix however, the problem still remains when we are converting packages that have multiple shortcuts. Legion SpaceWorks for example has 9 different shortcuts (please see attachment) yet, we cannot find the correct icons for each shortcut within the newly packaged .msi Is there a work around for this? It is becoming highly frustrating as there is no clear guidance for this issue. Many thanks, Jordan ... View more

Hi, Thanks for reporting this problem. It turns out that an issue with the same symptoms was recently reported and fixed. We have a KB article with a hotfix download for AdminStudio 2016 SP1. Please find the link here: https://flexeracommunity.force.com/customer/articles/en_US/ISSUE/Repackaged-Application-Creates-a-Blank-Shortcut Let me know if it resolves this issue for you. Regards, Ajay ... View more

Hi Jørn, Thanks for reporting this problem. It turns out that an issue with the same symptoms was recently reported and fixed. We have a KB article with a hotfix download for AdminStudio 2016 SP1. Please find the link here: https://flexeracommunity.force.com/customer/articles/en_US/ISSUE/Repackaged-Application-Creates-a-Blank-Shortcut Let me know if it resolves this issue for you. Regards, Ajay ... View more

Ajay, thanks very much for the advice and your insight. I'm sure others will also be interested. Regards ... View more

Hello, I am not sure why the registry information in your MSI file is not being transferred into the App-V package (SFT) file. I am familiar with the CustomAction table problem that you outlined, and I believe it should be fixed in our most recent release (AS 9.5). Could you tell me what version of AdminStudio you are using? Is the registry problem just present with a single MSI or with all MSIs that you have tried? Thanks, Ajay ... View more

Just done a new package capture and it looks to be working fine. I'm sure we get this sometimes where some packages just don't work ?? ... View more

Hi Mike, Thanks for bringing this to our attention. I was able to reproduce the problem with your suggested setup (XnView), and then was also able to reproduce the problem with a new simple MSI package that I created with InstallShield. It looks like the capture phase of Repackager worked correctly, but the build phase is not handling brackets correctly. I reported an issue for this behavior with number #IOA-000058270. Thanks, -Ajay ... View more

I'm working on repackaging a setup.exe for Envisionware PC Reservation. When I repackage it with AdminStudio, it drops dll's for Visual C++ redistributables, or, it installs them in the wrong location, for example the base C drive instead of the program directory. ... View more

Thanks Ajay - prompt, useful replies as always. Took your advice and got a working project. Cheers, Mike ... View more

Ok well, glad to hear that you have a working solution! ... View more

Selecting the correct side-by-side (sxs) merge modules is one of the more complex parts of the Repackaging process. You may be able to alter which merge modules are present in the Modules\i386 sub-folder of Repackager. There is a file in the System sub-folder of Repackager that controls which merge module gets substituted for a given assembly - PlatformFilesToModules.ini. It may be possible to modify this to select a newer version of the merge module as a replacement. If you just want to work-around this issue, you can open the ISM file in InstallShield Editor and remove the older merge modules in the Redistributables view and browse for the correct merge modules. Then build the MSI from here, and you should be good to go. ... View more

Hi, It's not clear why the additional file you included in the transform file did not get installed. I suggest taking a look at the following article to for best practices in adding a file via a transform: Using Transforms to Add Resources http://msdn.microsoft.com/en-us/library/aa372460(v=VS.85).aspx So make sure that you are new file is in a new component which is in a new feature as is recommended in the above article. Then test to see if it works. Create a MSI log file in case it does not work. Then you can check the log file for the InstallValidate action to see if your new feature and component were marked to be installed locally. See the following article about how to enable logging: How to enable Windows Installer logging http://support.microsoft.com/kb/223300 -Ajay ... View more

Hi Nicklas, There is a way to set the value for INSTALLDIR through the Repackager IDE. You can do this in the Captured Installation view - Original target folder setting. You may need to save and close and reopen the Repackager IDE to make sure this setting sticks. We have fixed a bug so that it will be easy to change INSTALLDIR when using InstallShield Editor to edit an ISM file created by Repackager. Until this fix gets released, you can always open the ISM with InstallShield and go to the Direct Editor view and edit the Directory table to get your desired INSTALLDIR setting. This is a bit more advanced and requires understanding the slightly complicated Directory table structure. Directory Table http://msdn.microsoft.com/en-us/library/aa368295(VS.85).aspx Regards, Ajay ... View more

Thanks 😄 Nicklas ... View more