Version: Avast 17.5.2303

[FrFc1908]

update went smooth and this version runs nicely! thanks avast!!

[NON]

Thanks for the update

[REDACTED]

Avast's recent habit of giving minimal descriptions of changes is unsatisfactory.  In this case, the term "SMB customers" is ambiguous, with at least two meanings in the IT world.  Can somebody from Avast confirm whether this is:

• Small & Medium Business (the addition of the word customers seems to imply this)
• Server Message Block - the protocol exploited by WannaCry etc, as some forum participants have concluded

Thanks

GAry

[chris...]

Yes , Avast should really call a cat a cat especially when it comes to release notes

Was jan.svoboda so tired to write a single sentence clearly ?

[bob3160]

IMHO, abbreviations are a great way to add confusion to something that needs to be exact.
If you intend to use abbreviations then in the beginning that abbreviation needs to made clear
so everyone know what it stands for.

[DavidR]

Avast's recent habit of giving minimal descriptions of changes is unsatisfactory.  In this case, the term "SMB customers" is ambiguous, with at least two meanings in the IT world.  Can somebody from Avast confirm whether this is:

• Small & Medium Business (the addition of the word customers seems to imply this)
• Server Message Block - the protocol exploited by WannaCry etc, as some forum participants have concluded

<snip>

Not only is it ambiguous.

Personally abbreviations should be avoided, unless having used the full term and bracketed the abbreviation. If the term is only used once there should be no abbreviation.

[Alikhan]

To clarify, this release is mainly for business. SMB (Small & Medium Business).

[midnight]

I installed this version on one of my win 10 computers today, got an error message when I clicked on SafeZone, done a repair, rebooted, still got the error message,  modified, unticked SafeZone, rebooted, went to component's installed Safezone.  Went to settings and none of them were the way I had them set so had to change all of them.  What  a pain!  Won't be installing this version on any of my other computer's.

EDIT:typo

[bob3160]

I installed this version on one of my win 10 computers today, got an error message when I clicked on SafeZone, done a repair, rebooted, still got the error message,  modified, unticked SafeZone, rebooted, went to component's installed Safezone.  Went to settings and none of them were the way I had them set so had to change all of them.  What  a pain!  Won't be installing this version on any of my other computer's.

EDIT:typo

Without stating the error you received, it's hard to give you an answer or a reason for whatever that error might have been.

[midnight]

@bob3160,

This error.

[bob3160]

@bob3160,

This error.

https://forum.avast.com/index.php?topic=195019.msg1360325#msg1360325

[REDACTED]

I updated to 17.5.2303 (build 17.5.3585.182), but then was unable to connect to websites with Firefox; the browser seemed to have trouble with the TLS handshake. Disabling Web Shield for 10 minutes made the problem go away, but it recurred after the 10 minutes were up. Enabling Web Shield but disabling the HTTPS scan seems to have fixed the problem permanently.

Also, after making the changes via the Avast interface, the Avast windows remained unresponsive and greyed out for over 30 minutes, at which point I had to try turning Windows off and back on again. Some regression testing should be added to your to-do list.

Oh, and your CAPTCHA posting verification images are the worst I have ever seen; if you don't want people to post messages, just disable the Reply button.

- Alan

[bob3160]

I updated to 17.5.2303 (build 17.5.3585.182), but then was unable to connect to websites with Firefox; the browser seemed to have trouble with the TLS handshake. Disabling Web Shield for 10 minutes made the problem go away, but it recurred after the 10 minutes were up. Enabling Web Shield but disabling the HTTPS scan seems to have fixed the problem permanently.

Also, after making the changes via the Avast interface, the Avast windows remained unresponsive and greyed out for over 30 minutes, at which point I had to try turning Windows off and back on again. Some regression testing should be added to your to-do list.

Oh, and your CAPTCHA posting verification images are the worst I have ever seen; if you don't want people to post messages, just disable the Reply button.

- Alan

If you're using XP or Vista, there's a known problem with https sites.
Disabling https scanning in the WebShield should fix the problem till Avast addresses this known bug.
Settings, Components, WebShield, Customize, uncheck Enable HTTPS scanning then select OK at the bottom.


Captcha is there for the first 3 posts to deter Spammers. (Sorry about that.)

[REDACTED]

Nope, using Windows 7, not XP or Vista.

[bob3160]

Nope, using Windows 7, not XP or Vista.

It's still worth a try. If it works, you're in luck if not, change it back and try the following:

Repair Avast:
Control Panel> Program and Features (Add/remove program)>Select Avast> Select Repair. Reboot when completed
https://www.avast.com/faq.php?article=AVKB204


If Repair doesn't fix the problem, try the following:
Clean Install of Avast:
https://goo.gl/4Ptzkf
If you need additional help with the Clean Install, watch this:
https://youtu.be/p-h3myRD51A