I'm still missing your point. To be clear, I'm missing any point in your messages.
My diagnosis is based purely on code I have, because it's the only thing I have right now. There is nothing else in this thread (except for initial message without any setup.log and few rants).
Whilst the code might well say that the code and subsequent 4C7 error is caused by a user cancellation.
The problem is when this 4C7 error is returned when the user 'didn't' cancel or have any input, then 'logically' it is wrong irrespective of what the code says. If a user didn't cancel an update how is it possible to return this error code ? Under what circumstances would avast cancel an update (is one of those returning the wrong code) ?
It just seems strange that we now have a rash of this 0x4C7 error.
I think that there may be a possibility which could account for an unknown user cancel. I personally have almost cancelled an update because I (like many others probably) continue working whilst an update is going on. The avast update process steals focus, so I have frequently been typing (two finger touch typist
, who watches the keyboard, not the screen), only to find that focus has been stolen by the secondary update screen.
If I have clicked the enter key, whilst the update window has focus, the active button is the 'Cancel' button. Fortunately I usually notice the are you sure dialogue window, but I guess it is possible that the cancellation could also be accidentally/unknowingly accepted.
However, this is a big ask to believe that this is what may have happened to the multiple users Alan supports who reported this having done this. Perhaps avast should consider not having the avast pop-up window not steal focus.