A search reveals others having this error reported after the latest update. Perhaps it is a glitch in the avast! software?