You know - in this day and age where decent QA is expected on paid for software, this particular error during a supposed promised automatic 669 update getting applied to 667 (and most every other version update the same has been promised on before too ) is simply unacceptable. With every new release, I keep seeing that users continue to report the update of the latest version not getting successfully applied - just like I again experienced too .................. This is what the event log is saying about the problem (just like I have seen others reporting) Why can you guys at ESET not figure (just like myself) that the ESET service needs to be stopped first before the update can be applied and then include that instruction in the installer? - why must the user go and manually stop the service before the update can continue and complete? Based on repeated personal experience, I beg to differ till you guys get your ducks in a row.