tried updating but mine still shows 10.3.2225 7/28 ???
Bud
From what I have been reading on petr_matrix comments and how avast might deal with this, it probably won’t require a program update to resolve. It could either be during the virus definitions and engines update or as an emergency update. I rather suspect that it would be done during the virus definitions and engines update.
You could also check the file properties (date time updated, etc.) as catavast in the attached image.
This was my experience. There was a ‘routine’ virus definition update which also downloaded a new version of the problematic file. On reboot, the new file replaced the old one. Maybe all you need to do is reboot and test.
Thanks for the confirmation.