I reported this to MS but its something of note, that mebby some adjustements to SL could help with
Theres been an annoying issue iv had with Onecare... When Second Life (Linden Labs) forces an update, the dialog authorizing onecare firewall pops up, you accept, but Second Life will timeout the update and the main app has to be restarted, reconnect to the programs own servers, and then it will re-ask for the force update and then Onecare will let it through.... Is there a better way than having to do this for *every* update of the software package?
Response was
Jolted,
Does the version number for the updater executable itself change with each new update? If so, this is the problem, since OneCare firewall will see this as a new application.
One way that this situation can be easily solved is if Linden Research would digitally sign their updates, since signed executables are allowed access automatically without prompting. Another way would be to avoid updating the updater itself, at least if not absolutely necessary.
Another idea *I* had was if SL and SL Updater retried to connect in a set period of time if it cant get though the firewall, giving time to allow it through and reconnect.