NEW Avast Version 22.7 (July 2022)
Hi, all. Please welcome the newest version of Avast AV: 22.7 (22.6.6025) Major public announcement:
Windows Recovery Environment Scan Boot Time Scan now runs inside the Windows RE, on the Avast interface! Now it’s easier to take action and see what the scan finds without having to reboot again.
Check out our new UI Store We’ve created a store within the interface to help with easier access to other Avast applications
Other notable improvements in the release:
Fixed an issue where Ransomware shield would not look after protected files properly
TLS 1.3 enabled in Mailshield
Other important issues and bugs squashed
Big props to the team for another successful release! How to install:
Update from your existing Avast version via Settings → Update → Update program
Or you can download and install files: Online installers (recommended):
since installed the new release Avast Secure browser autolaunch itself when I start computer, even if autolaunch function is disabled. Do you intend to fix the bug or have I to uninstall Secure Browser?
With this new update I am missing the browser threats scan. I now only show two scans, viruses and malaware together and advanced issues. I’ve done a repair etc. Still not showing. My friend has this and hers still has the 3 scans. Is there something wrong with mine? Thanks for any help
Some clarification (more details) on how to initiate the “Boot Time Scan now runs inside the Windows RE, on the Avast interface!” as mentioned in the release notes above.
Since the new update avast blocks outlook orders.
It does not read the server certificates
The avast support is helpless.
does anybody out there now something about this error?
Since the launch of the new version in July, it is impossible to run the looking for viruses from the start function. I have informed Avast and they have asked me all kind of information, but I can´t provide it because the messages on the screen last just a few seconds and it is impossible to print them or take a picture. I am totally sure the cause is a mistake by Avast on the July release, as I had a similar problem a year ago with another new version, and in that case I thought the problem was with my PC. After spending some money having it checked, the solution came with the new release where the mistakes had been solved. They have just released a new August version, but the problem remains the same. Releasing new versions without a proper checking seems an awful client service, expecting the client to find all the mistakes and pay the consequences of that poor service.
See the link given in Reply #8 - quote below - It will give you an idea of what is going on. There are a couple of related topics if my memory is working.
This morning Avast said my AV was not up to date … I let it update from within the UI and when it was done
I found it at 22.8.6030 … Not sure if this is the beta version or not, but I was supposed to be on the regular
release channel … If it did switch me to beta, how can I tell for sure or get back to non beta releases ? ?
Thanks
Never been on the beta channel … And when I look at the UI it does not seem to show it is on beta … Just gives the version number so I am not sure if on the release channel or maybe they are making the beta version the latest real update.
I honestly don’t know how this could happen (accidentally end up on the beta channel), if it is happening I’m sure you won’t be the last to post about it.
22.7 is still the latest regular release, though 22.8 is probably close if you look at program update history being around the end of the month. However, there appears to be around 10 program updates in a 12 month period.
Personally I have Program Updates set to Manual update and I’m still on 22.5.6015 as I haven’t seen much in the bug fixes (I’m not suffering) or enhancements that I feel worth updating.
My system updated this morning also. I think someone maybe just forgot to post it here as released. SUMO and Major Geeks are listing it as final release, too. It seems there would be more people here reporting it, though.
