My conversation with Avast support suggests that 10.3.2505 and 10.2.2505 are the same version - just renumbered. They should have released 10.2.2505 as 10.3.2508 to solve the problem - as the 10.3.2507 bad versions would have "upgraded" to the older 2505 renamed as 2508.
I agree. If the build was withdrawn after official public release, a replacement should have either gone up a revision, or back to the
original which was 10.
2.2505. If they are the same binary as suggested above, my own suspicion is someone made a boo-boo in the rollback data by mistyping as 10.
3.2505 and rather than make the issues worse it was left as-is.
Currently my installs all complain a new version 10.3.2505 is available, but won't upgrade to it. Probably because the 10.2.2505 install is the same so there's actually nothing to do. Still the console complains and will until a newer build (which I can live with).
It sounds like you are really on top of this and in direct discussions with Avast support, Jim. Thanks for your input on this, very helpful.
I'll say again; non-staggered automatic application updates in a production environment are evil IMHO. Useful, but evil