We develop a application that has many changes and updates, there for we will launch a new setup/installers every ±month or so.
Now when we do this IE9 doesn't like this because not many users have this file/setup installed. (SmartScreen Filter)
We do have the code signed with a trused service, but I understand this doesn't effect the popularity/trust.
To refresh your memory, the warning looks something like this, except ours looks a bit different because the code has been signed.

What will be the best approach? I was things:
1.) We will develop a page where the user will get a explanation for this IE9 message when he downloads the setup.
2.) The installer is always the same and the setup/installer will download the current version that needs to be installed.
And so my question is, mostly part2... is this done more common with advanced installer: Setup/installer is small file that downloads the main setup? Perhaps there some examples, or how to's? I did not yet dive in the code or in advanced installer.
FOLLOW US
Get the latest news in Application Packaging