![]() ![]() And if they clicked on the icon for details, they were immediately advised that You are unprotected! Avast Background service is not running. upon receiving this bad update - which was pushed as an "emergency update" via a scheduled task - users noted a big Red X on the avast icon in their system tray. ![]() Would users of avast been aware of this problem if they did not run on-demand scans?Ībsolutely. 2, which is not particularly helpful to anyone looking at the version numbers However, the fixed version is still identified as - build. Remark: I followed the suggested fix - to manually run AvastEmUpdate and reboot - and it worked for me. All fresh installations are OK from now on.įor existing affected users, if it doesn't update automatically, the fastest way to fix it is to run C:\Program Files\AVAST Software\Avast\AvastEmUpdate.exe and then reboot. In essence, it was just a UI problem ( the protection service/shields weren't affected at all), but a very visible one. The digital signature of the UI process executable (AvastUI.exe) became corrupted during the release process, causing the self-defense driver to block the communication pipe with the service.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |