We have a application using TWebUpdate that is not auto-updating correctly on Windows 7. The new files download. We get a UAC prompt, accept it, but the the executable does not end up in place. I have looked through the FAQ and saw the comment on digital signing, though I was not totally clear about the full implications.
I am actually not worried about getting oour company name displayed as part of the process. However perhaps the FAQ is saying that the update will not work unless the stub loader is signed and matches signing of the new executable? Is this correct?
Our installer "Indigo Rose" installs the exe fine without signing (we will probably sign soon, but can not get there yet). It is just the auto updating that is giving the problem.
So I guess the question is.... am I totally stuck until we can sign the executable and the TWebUdate stub loader??
Many thanks for any help.
Dave
I have I think answered my own question.
The answer is No I am not totally stuck. I can get auto-update working in W7 without signing the application, or resigning the stub-loader with our own certificate. I do see the "This is signed by TMS Software" message, but for the moment we are happy to live with that.
In fact what happened was that in the upgrade to a new version of the TWebUpdate components a control file that had been working perfectly well stopped working in the Application update section (appcomps= xxxx). No idea why for the moment, but we have changed the control file and the updates are now running.
If you want a your own signed stub, please contact us by direct email and we'll provide source + instructions to do this. Windows 7 UAC rules require signing.
Thanks. I will contact you soon.