Update:
29. 12. 2017 12:30 CET fix via uupdate channel has been released.
Fix is applied to all users automatically during 12h, during update process or during fresh installation.
I am a bit confused by hectic's words as he says fix has been released that can be implemented via update or fresh install, then offers previous version as temprary fix. Does that mean if update fix doesn't work, then the ultimate backup is to remove and install 17.8?
My experience of 17.9.2322 with Outlook 2010 has been strangely mixed. On my Win10 1709 machine the Avast Add-On did not cause Outlook to disable it. However, on my WINXP SP3 Outlook 2010 combo, Outlook failed to start unless Avast Add-on was agreed to be disabled.
Today, on reading this post, I tried Update Avast on my XP machine. Nothing appeared to update. Anyhow, I then did Repair of Avast and reboot. After that Outlook 2010 started with the Avast Add-on enabled.
I dont know if that is just a fluke or whether something has been updated. I cant tell, as Version of Avast reported on both my Win10 and XP machines is exactly the same. 17.9.2322 (17.9.3761.0).
Have avast kept the same version number although the Avast add-on has been altered? If true, then Avast's attitude to software versions control is poor. I for one would get shot by the quality department if I did that sort of thing.
If someone can somehow explian my observations, then maybe others can benefit.
Happy New Year
Ed