there is a new beta version ready - 24.2.6102 (build 24.2.8877).
What was fixed
Changes related to product name displayed in Windows Security Center
Boot Time Scan internal changes
Fixed crashes happening mainly during computer shutdown
24.2.6102 is a disaster on my W7 16GB machine! In keeps “fixing” itself by doing what looks like a reinstall, then what looks like a network scan. A usable UI is sometimes available during this and for a significant amount of time DNS lookups are not available. When it appears to settle down, the “you are not protected” shows when trying to get status and the UI says Avast has crashed. Indeed, an eicar.com test file is not flagged is being “bad”. So… I flushed the beta completely and installed the real 24.1 release. All is now good and the EICAR files get flagged as “bad”.
Please refrain from saying get off of W7… How long will you folks support it? I have W11 on a laptop, but MS insists on changing/adding/breaking something each month. The machine that will shortly replace the W7 box is now running Debian. Any chance you’ll have software for Linux that isn’t an expensive business license?
Cheers, -Tom
Hi Karel, I’d love to run the dump package for you, but to recover system functionality I had to run avastclear and install 24.1.6099 (build 24.1.8821.762). When you release beta 6103 I’ll try it. I noticed that the avastdump (or something like that) process was running every time Avast crashed, so maybe it was sending you information? I also caught “Avast emergency update” running some time. The “company name” in the OS process tables changed to “Gen Digital” (your parent company) in 24.2? -Tom
Still no notification of 24.2 in the regular program side of the forum.
But there are some sharp practices going on with this ‘enforced’ update
Generally I wait for program update topic in the forums and decide if (update then or later) but still no official notification on the forums for 24.2. - https://forum.avast.com/index.php?board=2.0#
The fact that you haven’t got the latest program version ‘Shouldn’t generate the fear mongering notice’, the program should still be running and working!
Given what was in the beta subforum for 24.2 there was bugger all in that which should generate this heavy handed notice (which I have never had before) warning you are ‘unprotected’ with a red X over the tray icon.
Very disappointed at this sharp practice when there is nothing in this current beta that would warrant this kind of notification.
Changes related to product name displayed in Windows Security Center
Boot Time Scan internal changes
Fixed crashes happening mainly during computer shutdown
Nada, bugger all, nothing to warrant this heavy handed approach.
You probably get that I annoyed, pissed would be closer to the mark, in almost 20 years using Avast this is the first sharp elbowed approach to program updates.
EDIT Typo.
‘Heavy handed’ is the current fashion in the corporate world. Customers/users should know their place.
I had a system running Windows 11 22H2. The processor is a 7th generation device (Intel(R) Core™ i3-7100 CPU @ 3.90GHz). Microsoft has determined that it is incompatible with Windows 11 23H2. The result is hardware going nowhere beyond the near future, actually October 2024. It was necessary to revert to Windows 10 which reaches end-of-life in Octover 2025. Linux is now favourite.
Having had two systems bricked by Microsoft monthly updates over the years, I am now much more cautious with updates, particularly of operating systems and antivirus software.
Have a current system backup to revert to if this update goes wrong. But to say ‘You are unprotected’ when a system check finds all features and systems running, is like shouting “Fire!” “Fire!” in a crowded movie theater when there isn’t one. People will get hurt and upset if you do that.
Just not done. :o
Will get the offline executable when it shows and download.
How impressed I was, with this version that has already been released, 24.2, as it is full of problems, here on the forum there are a lot of reports about problems in this version.
What is happening?
Today we again refreshed the build in beta - 24.2.8918 build has been released. There are no major visible changes. Just some internal fixes and improvements.
Karel