Major Avast Problem! (build 12.2.3126.2)

[ky331]

In an attempt to fix an issue --- that the user interface was randomly opening up on its own --- avast issued an [emergency] update.   However, it appears that this update made things significantly worse --- the avast interface no longer recognizes its own services and database  >:(   There are now MANY dissatisfied users bombarding the avast forum to complain.

I'm not 100% certain of this... but based on what I've read in the forum --- and just now confirmed on one of my computers --- it appears the buggy update is version 12.2.2276 - build 12.2.3126.2  ;  the final digit, 2, distinguishes this update from earlier (good) ones.

For more information, see the ongoing discussions:  You are unprotected! Avast Background service is not running:

https://forum.avast.com/index.php?topic=189221.0

https://forum.avast.com/index.php?topic=189195.0

[ky331]

From http://www.wilderssecurity.com/threads/avast-2016.381211/page-6#post-2605687

The digital signature of the UI [User Interface] process executable (AvastUI.exe) became corrupted during the release process, causing the self-defense driver to block the communication pipe with the service.

In essence, it was just a UI [reporting] problem (the protection service/shields weren't affected at all), but a very visible one.

---------------------------------------------------------------------------------



From https://forum.avast.com/?topic=189221.0

UPDATE:

This is now fixed. All fresh installations are OK from now on.
For 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.

-----------------------------------------------------------------------------------

Remark:   I followed the suggested fix --- to manually run AvastEmUpdate and reboot --- and it worked for me.   However, the fixed version is still identified as 12.2.2276 - build 12.2.3126.2 , which is not particularly helpful to anyone looking at the version numbers

[ky331]

Full explanation and response from avast:  https://forum.avast.com/index.php?topic=189349.0

[ky331]

And the "fun" [sarcastic] continues:  Avast causes Blue Screen after Windows 10 Anniversary Update 
https://forum.avast.com/index.php?topic=189403.0

I have not personally experienced this, as I don't have any Win10 systems here.

Please note reply #61 https://forum.avast.com/index.php?topic=189403.msg1329994#msg1329994

"the issue really seems to occur only on the last generation of Intel CPUs. Previous generations of Intel Core CPUs are fine. Moreover, it did not show up during the testing on the Win 10 preview builds.

We are already working on a fix and hopefully, we are going to deliver it via an emergency update. I will keep you posted.

Thank you also for your patience. We are having a hard time with this update as well."

[ky331]

this issue occurs only on Intel Skylake CPUs when VT-x instructions are enabled in the BIOS. As a workaround, you can temporarily disable the VT-x in BIOS.

[ky331]

Full explanation and response from avast on the Win10 Bluescreen / Skylake problem:
https://forum.avast.com/index.php?topic=189503.0