Many may not be having these issues because they can afford to keep their hardware up to date. Being a school district, we have to stretch what little money we get for computer systems. We are using systems that are going on six and seven years old, and even have systems that are 10 years old still operating.
Age isn't so much a problem, it's usually combinations of things that cause glitches and are almost always impossible for vendors to thoroughly test for.
I understand your position though. I look after about about 15 PCs for a non-profit organization. Only ever had a problem with 2 PCs of the same make and model which happened to be Core i3-based and newer than most of the Core 2 Duo machines in the building, so you can't always blame older hardware
The solution to my specific issue was to update the network driver (and not from the motherboard vendor either).
Glad you are able to identify only machines that are migrated from AES as being a problem. That's useful info and would be worth dropping a line to Tech Support should you choose to proceed with Avast. Trying avastclear would be their first recommendation to I am sure. Personally I had MORE tech problems with other AV products than I ever did with Avast, so go with what works for you. If you are going to change, I'd still recommend running
https://www.avast.com/uninstall-utility just to be sure the problematic machines are really clean because adding another vendor's product on top of an already existing issue could give you just as much grief.
Where people normally get into trouble for any kind of software deployment is trying to do too many too quickly. A long testing phase on a select group and staged deployment is always best if you have limited resources.
Good luck !
