Repackager issue : Could not write key Minorversion....
Hi
I just try your app in order to repackage an installshield application setup exe file (for which /r and /s parameter doesn't work).
The repackaging goes well.
When launching the freshly created Msi file I got those kind of error :
Could not write value VersionMinor to key/Products/8D8CF99C44E7BC47B013FC2A5E4C245/InstallProperties. Verify that you have sufficient access to that key, or contact your support personnel.
and
could not write value versionMinor to key\Software\Microsoft\Windows\CurrentVersion\Uninstall\{C99FC8D8-E344-4CB7-B710-F32C5A4E2C54}. Verify that you have sufficien access to that key, or contact your support personnel.
I'm the admin of the workstation...
Any help appreciate
thanks a lot
Runing version 1.2 on Xp workstation
I just try your app in order to repackage an installshield application setup exe file (for which /r and /s parameter doesn't work).
The repackaging goes well.
When launching the freshly created Msi file I got those kind of error :
Could not write value VersionMinor to key/Products/8D8CF99C44E7BC47B013FC2A5E4C245/InstallProperties. Verify that you have sufficient access to that key, or contact your support personnel.
and
could not write value versionMinor to key\Software\Microsoft\Windows\CurrentVersion\Uninstall\{C99FC8D8-E344-4CB7-B710-F32C5A4E2C54}. Verify that you have sufficien access to that key, or contact your support personnel.
I'm the admin of the workstation...
Any help appreciate
thanks a lot
Runing version 1.2 on Xp workstation
0 Comments
[ + ] Show comments
Answers (4)
Answer Summary:
I have seen this many times when repackaging an application. It has always come down to proper formatting of the version number #.##.####.#### with numbers only. Every time I attempted to utilize any character that was not a numeric digit, it failed with this error.
I have seen this many times when repackaging an application. It has always come down to proper formatting of the version number #.##.####.#### with numbers only. Every time I attempted to utilize any character that was not a numeric digit, it failed with this error.
Please log in to answer
Posted by:
stmasi
12 years ago
I have seen this many times when repackaging an application. It has always come down to proper formatting of the version number #.##.####.#### with numbers only. Every time I attempted to utilize any character that was not a numeric digit, it failed with this error. Thanx.
Comments:
-
Hi, can you help to be more specific, how to properly format the version number? I'm facing this same issue - eavenhuang 1 year ago
Posted by:
jbvernejoux
12 years ago
Hello,
I have the same problem with another package (7Zip) that i have created , but on a Windows 7 (UAC disabled).
Even this is not the
I think the root cause is that the MSI package file doesn't include the MSI's execution option: "Use Privilege elevation".
It's a flag added into MSI file to tell Windows installer that this installation must be run in an security context with administrative rights
I don't know if "Application Repackager" can add this flag to the generated MSI file...
I have the same problem with another package (7Zip) that i have created , but on a Windows 7 (UAC disabled).
Even this is not the
I think the root cause is that the MSI package file doesn't include the MSI's execution option: "Use Privilege elevation".
It's a flag added into MSI file to tell Windows installer that this installation must be run in an security context with administrative rights
I don't know if "Application Repackager" can add this flag to the generated MSI file...
Posted by:
orlith
12 years ago
Thx for your comment. I'll see if I can add manually this option in my package.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.