Some users may experience issues accessing the case portal. For more information, please click here.

This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
ssabev
Level 2
‎Nov 22, 2010 11:58 AM

Repackager does not transfer registry settings from .msi to .sft

Hi,
I am using the repackager to convert an .msi to an app-v .sft; the conversion is successful, but the produced .sft does not have any of the registry settings that are part of the .msi.

Is there anything specific in the .msi that will trigger the transfer of the registry settings?

I noticed I had to create an empty CustomActions table to get around this error:
-9001 An unknown exception occurred
0 Kudos

This thread has been automatically locked due to inactivity.

To continue the discussion, please start a new thread.
1 Reply
Ajay_Ladsaria
Level 7
‎Dec 01, 2010 07:57 PM

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
0 Kudos