Hi Advanced Installer Support Team,
Currently I'm integrating our installer with Auto Updater and would like to get some answers from you if possible:
1. First of all I'd like to draw your attention to a potential problem of Auto Updater: in a very special scenario the updater does not refresh some of our registry entries - for example the version number is not increased - while upgrading our product. Please find my sample projects attached for reproduction and perform the the following steps:
a) Open Sample project.aip (please use Advanced Installer 12.1) and prepare a Major Build (e.g. version 1.0.0)
b) Increase the version number to 1.0.1 and create a new build for patching. Choose Keep existing option.
c) Prepare a patch using the Sample project - Patch project.aip project.
d) Create an update using the Sample project - Update project.aip project. Choose the msp file crated at Step 3 for update.
IMPORTANT: Registry problems occur only if you install your update without elevation, so that the relevant checkbox must be ticked on. Installing the patch file manually (double click on it), or else installing it through the Auto Updater with elevation all works as expected and registry entries will be up-to-date at the end of the installation.
e) Install version 1.0.0 on a 64-bit PC.
f) Confirm that the version number is 1.0.0 in "Programs and Features" as well as in the Registry under HKLM\SOFTWARE\SAMPLE\Installation\InstallVersion.
g) Trigger the update mechanism and let the product to be updated -> "Some components could not be updated..." message appears at the end because "Installed Detection" phase of the updater fails due to wrong version number in the registry.
h) Confirm the the version number is 1.0.1 in "Programs and Features", but still 1.0.0 in the Registry under HKLM\SOFTWARE\SAMPLE\Installation\InstallVersion, which is incorrect.
Some more remarks: As you might have discovered there is a completely empty feature called 32-bit in the Organization section of Sample project.aip. My investigation shows that having an empty feature in the product is a kind of requirement of the registry problem, removing it from the list and performing the reproduction steps one more time would interestingly lead to the correct version number in the registry.
Do you think it's a bug on your side or else the configuration of my project needs to be changed? Could you please have a look at my sample projects and let me know about your thoughts?
2. A bit information about the security of your support service for the updater would be highly appreciated, obviously I'd like to be sure that the service comes along with our product updates our components only and does not install anything else on customers' PC. How do you prevent your service from installing harmful content - e.g. a malware? Enabling the checkbox of "Install only digitally signed update packages with the same certificate that the Updater" of the Updater really makes it secure for us and nobody else (like hackers) can use it?
3. We have to update the digital signiture of our product from time to time, do you think this fact may lead to any problems in the future? For example what if we have an old version of our product is installed on a customer's PC with an old signiture (and of course "Install only digitally signed update packages with the same certificate..." is enabled to increase security) and then we create a new version with a new signature? I believe in this case the customer won't be able to update his product, right? Do you have a proposal or best practice for these situation?
Thanks in advance for your answers!
Best regards,
Zsolt Kollarits
FOLLOW US
Get the latest news in Application Packaging