Version: 20.1 (February 2020)

[helena.potancokova]

UI Failed to Load after update! This is really embarrassing. Your protection is running, but the UI is having a really bad day.

Avast really??? All users, be careful about updates.
v20.1.2397

[Asyn]

UI Failed to Load after update! This is really embarrassing. Your protection is running, but the UI is having a really bad day.

-> https://support.avast.com/article/Troubleshoot-Embarrassing-UI-Failed-load

[bob3160]

UI Failed to Load after update! This is really embarrassing. Your protection is running, but the UI is having a really bad day.

-> https://support.avast.com/article/Troubleshoot-Embarrassing-UI-Failed-load

Unfortunately these instructions are outdated. Time for Avast to revise the instructions.
The interface no longer has a Component option.

[chris..]

UI Failed to Load after update! This is really embarrassing. Your protection is running, but the UI is having a really bad day.

-> https://support.avast.com/article/Troubleshoot-Embarrassing-UI-Failed-load

Unfortunately these instructions are outdated. Time for Avast to revise the instructions.
The interface no longer has a Component option.

I don't understand, for me the instructions of the article are good , there is no more question about Component option.
Simply starting or restarting avast antivirus in the Windows Services console (explained in the article) is enough to remove the message "UI failed to load"....at least for me and my experience last week on one of my devices that had this problem.

[Asyn]

UI Failed to Load after update! This is really embarrassing. Your protection is running, but the UI is having a really bad day.

-> https://support.avast.com/article/Troubleshoot-Embarrassing-UI-Failed-load

Unfortunately these instructions are outdated. Time for Avast to revise the instructions.
The interface no longer has a Component option.

I don't understand, for me the instructions of the article are good , there is no more question about Component option.
Simply starting or restarting avast antivirus in the Windows Services console (explained in the article) is enough to remove the message "UI failed to load"....at least for me and my experience last week on one of my devices that had this problem.

+1 No idea what Bob means.

[bob3160]

My reply was for the Further recommendations section.

[chris..]

Was your intervention required on this post-it topic? 
Especially starting with "unfortunately" which can stop the member from trying the basic procedure in the article (restart the avast service)... which has a good chance to work before going to "Further recommendations".
You have other ways - I think  - to point out to avast that their FAQs are a bit outdated.

[bob3160]

Was your intervention required on this post-it topic? 
Especially starting with "unfortunately" which can stop the member from trying the basic procedure in the article (restart the avast service)... which has a good chance to work before going to "Further recommendations".
You have other ways - I think  - to point out to avast that their FAQs are a bit outdated.

Did you get up on the wrong side of the bed this morning

[chris..]

Was your intervention required on this post-it topic? 
Especially starting with "unfortunately" which can stop the member from trying the basic procedure in the article (restart the avast service)... which has a good chance to work before going to "Further recommendations".
You have other ways - I think  - to point out to avast that their FAQs are a bit outdated.

Did you get up on the wrong side of the bed this morning

That wasn't my question, and you didn't answer it.
I'm not asking if you came across a virus yesterday in San Diego...

[bob3160]

Was your intervention required on this post-it topic? 
Especially starting with "unfortunately" which can stop the member from trying the basic procedure in the article (restart the avast service)... which has a good chance to work before going to "Further recommendations".
You have other ways - I think  - to point out to avast that their FAQs are a bit outdated.

Did you get up on the wrong side of the bed this morning

That wasn't my question, and you didn't answer it.
I'm not asking if you came across a virus yesterday in San Diego...

I might have   I'm currently taking cold and flew medication.
Part one of the instructions are fine but if you need to go beyond that, then you run into a problem.
I have informed Avast via another method to look into updating their facts section.
Have a nice day.

[menziller]

I also encountered the same "self-updating" behaviour reported by other users:
my Win10 system with Avast free has updated today to 20.1 (from 19.3) despite my setting "Ask when an update is available".
Indeed, to be precise, the program yesterday popped up a notice about a new release being available (just as it had done with the updates between 19.3 and 20.1, which I refused) but, despite my denial, at the following system boot (this morning) I got a message saying something like "Congratulations! Your Avast has been updated".

-> https://forum.avast.com/index.php?topic=232420.msg1537052#msg1537052

Thanks.

[extrememk]

Hi

With latest update (ver. 20.1.2397 - build 20.1.5069.558) "Password Protect" doesn't work for "right click on Avast System try icon and disable it", but works when i want to open avast.
Please fix this, because everyone can disable it.

Thanks in advance.

[bob3160]

Hi

With latest update (ver. 20.1.2397 - build 20.1.5069.558) "Password Protect" doesn't work for "right click on Avast System try icon and disable it", but works when i want to open avast.
Please fix this, because everyone can disable it.

Thanks in advance.

This definitively needs work.
I can disable the shields without the password but need to enter the password to turn the protection on again.
Which makes no sense. I'm alerting Avast Thanks for reporting.

[Asyn]

I also encountered the same "self-updating" behaviour reported by other users:
my Win10 system with Avast free has updated today to 20.1 (from 19.3) despite my setting "Ask when an update is available".
Indeed, to be precise, the program yesterday popped up a notice about a new release being available (just as it had done with the updates between 19.3 and 20.1, which I refused) but, despite my denial, at the following system boot (this morning) I got a message saying something like "Congratulations! Your Avast has been updated".

-> https://forum.avast.com/index.php?topic=232420.msg1537052#msg1537052

Thanks.

You're welcome.

[jacques.subileau]

I was asked to restart my computer this morning by avast so I did. I still have the same build 20.1.2397 (version 20.1.5069.559) and the same version interface 1.0.460. So why did Avast asked me to restart as I can't see any change ?