J.R., great reading…thx !

I agree that while the responsibility of ones machine is our own that software like A/V should know how intrusive by nature they are. It is one thing to truly clean a system…as you outlined…including reg cleaner (eg. CCleaner will show un-used trees), etc. However, I think it is another thing for the A/V company installing their software to scan the PC for known files they know can cause conflict. Avast merely has to scan to see what resident or old Prog files or directories that are there and send a warning with perhaps their FAQ link with the uninstallers. Heck, many folks perhaps don’t recall which software may have been resident…in fact a factory load could have been altered and some resident still there.

Anyway, my point is there are many posts where the senior folks on this panel have to help via FRST to remove old A/V that is mucking things up…or Avast that has locked because of old A/V. My suggestion is a simple initial scan to see what conflicts could be there and warn. Many software companies do this during installs…just think Avast should too. Avast clearly wants all users installing their software to keep/pay and be long time customers. The failed…or worse locked up…installs will not be blamed on what users don’t know or forgot about…Avast will get the black eye. I just think a simple extra step up front would allow for better results.