No changes at all, but program updater now not show icons next to program name which was mentioned in Beta forum. No care i see…no reason create Beta version if stable version is released after 2 days without any change.
I can’t believe, beta 17.5.2303 released on Friday, new stable version 17.5.2303 released on Tuesday. I wonder what could have been achieved in the beta release.
If “this version contains mainly fixes under the hood for SMB customers.” What benefit for non SMB customers ?
I’d like to know which of the many bugs that were in the last release have been fixed in this one ???
With the timeframe from beta to final release, why bother having a beta version at all ???
Well it didn’t fix the HTTPS Scanning Problem that is affecting XP and Vista users.
All it did was put my Vista laptop right through the mill >:(
My CPU was stuck at 100% for about 10 minutes. And I really didn’t think the update was ever going to finish.
Still got to update my sons Windows 7 desktop yet. Not looking forward to it!
Updated OK on my Win10 and WinXP machines via Settings/Update route. XP restart was a bit slow but no problems. Seems to have got rid of NEW flag against Data Shredder that was persistent on XP.
Ed
Did the manual update using the full off line installer on both my Win 10 Home 64 laptop and on my Dell 8200 XP PRO SP3 box … both went without problems. Maybe it fixed the behavior shield not starting on the XP box … time will tell. Said to be fixed for sure in the next 17.6 release whenever that is due.
i never use it, i did normal scan & fast scan, but i haven’t done any scan for a year cause i see no issues that may be malware & virus, so no idea does it work for me or not
Never use what ??? Https scanning allows avast to check https sites for malicious code.
Unless you’ve turned it off, it happens every time you visit an https website.
Applied the update via the Avast user interface. Rebooted when requested. The box (i7 Win7(64) Pro Lenovo) is still sitting at the BIOS boot screen (very pre-Windows logo) after 15 minutes with the disk drive activity light on constantly.
Not. Happy.
Take a chance and do a forced shutdown? Sit tight and hope for the best? Kill a chicken and sprinkle its blood on the keyboard??
Over the years, there have been many security vulnerabilities in Microsoft's implementation of the protocol or components on which it directly relies. Other vendors' security vulnerabilities lie primarily in a lack of support for newer authentication protocols like NTLMv2 and Kerberos in favor of protocols like NTLMv1, LanMan, or plaintext passwords. Real-time attack tracking shows that SMB is one of the primary attack vectors for intrusion attempts, for example the 2014 Sony Pictures attack, [b]and the WannaCry ransomware attack of 2017[/b]
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
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.
