igor0
9
I’m not saying that it’s not an avast! problem - of course, it’s possible; but since the order of the application startup is really kind of “random” in windows, I’m a little sceptic about the reproducibility and possibility to find & fix the error 
Are you sure that avast blocked access to network resources, other than POP/SMPT/IMAP, on startup? If yes, I think it’s again some kind of problem with (concurent) network library initialization - because as far as I know, avast doesn’t have anything to do with SSH etc.