OK, I can certainly do that, but not eager to do it more than once. But the program and definitions HAVE updated successfully in the past, so I don't think I have a corrupt install any more than I really think my FW is blocking your updater(s).
1) Odd that this just started happening after a previous successful update (manual), so the FW rules as written WERE acceptable in the past.
2) Odd that the screen shows a specific server number was reached, so I don't think my firewall is blocking the updater from getting to a server. I've allowed "out" those files that appear to be needed for updating and then some, so let me know if there is a file I've not given permission "out" that needs access to the server.
I'll do the uninstall/reinstall steps as you suggest and certainly hope that resolves the issue. Will report back my results and come back later in the month as well if a future program update causes a recurrence of the scenario of update events/error messages.
Somewhere in an old thread I found searching last night on the forums indicated that this issue has happened to numerous people before. The Avast helper in that discussion said something to the effect that when the program updated to a new version new FW rule(s) might be necessary. Why, if rules already in place that allow updating just fine? File name changes? That would appear to be a SW design flaw if that is truly the case. It would intimate this problem will recur every time Avast updates the program to a new version?
I certainly hope after I go through the uninstall/reinstall process, I don't see this issue again, because if this reoccurs, I'm going to think this issue really is a SW design flaw. I'm just not willing to uninstall/reinstall every single time ASW updates to a new version and in that case, would have to find a different AV.
Thanks for your suggestion though, and I'll keep my fingers crossed it solves the issue.
