Why do you think that is ?
I did nothing special, just installed 5.0 over 4.8 and it worked and I’m supposedly on an OS (XP) that is susceptible to this problem according to others.
Me I only had one of the beta builds (about midway through the beta testing) for a short time on my live system, I felt it wasn’t right for a live system at that time and went back to 4.8. During that time though I have been monitoring the beta forums and at the time of the release the beta forums weren’t awash with serious problems. So I downloaded the release version and installed it.
One thing different from the beta trial though with the early builds it was recommended to do a clean install and that is what most did. Subsequent to that many would have been updating from beta to beta so not so many issues regarding updating.
However, towards the end of the beta it was suggested it would be OK to install over the top of 4.8 for those who didn’t already have the beta installed. Some experienced problems, though not masses of them and a clean reinstall resolved the problem. They too would be updating beta to beta so no major issues for most.
The major difference on the release is the much greater volumes of people updating by installing 5.0 over 4.8 (as suggested on the website) so the flood of topics from those experiencing problems. But given the same large volumes of updates, I don’t know if this is as severe as it looks, yes if it is effecting you it is very severe.
DavidR, I agree with what you are saying, mostly. In the overall scheme of thing the volumes complaining could be only 3-4%. Avast may know that. However, since we don’t work around BSOD’s all day they come off as Catastrophic. I realize some of you guys know a whole lot more computer stuff that I do, I never learned how to read code. I do know that when I work on my computer, a BSOD really ticks me off. I never spent the time Beta testing anybody’s software for them. I have plenty of other things to do. I do know that I don’t like losing work because of a BSOD. Since I had been using 5.0, I didn’t get much of any small glitches, I got BSOD’s. So I warrant my concerns that it shouldn’t have been release this early.
I put back 4.8, at least for another revision or two. Even 4.8 has it’s gliches. Somebody tell me why it can’t read it’s own download for updates continually. I have had this error three days in a Row.
"Information about current update:
Last encountered error: Invalid file signature. Setup will terminate.
Total time: 1:08"
Now this version has been released now for a LONG time and still this error. But it is NOT a BSOD, so I can live with that.
First of all I introduce myself, I just register, and tell them I’m Artagatis that version 5 of avast! R, I downloaded and automatically uninstalled version 4.8, but version 5 is inactive and can not be activated, by clicking on the icon opens the instructions but said that implementation remains inconsistent even if you press the button start system or fix, then the icons disappear, then tried to uninstall 4.8 to start from scratch and I said that this enabled self-protection avast! and I should uninstall it via Safe Mode or troubleshooting page.
Is there someone who can advise? I am unprotected
I mostly agree, although the issues I ran into don’t involve compatibility problems. I encountered three bugs during the first day after updating Avast 4.8 to Avast 5 last Saturday. Two of bugs are relatively minor. I can work around all three of them. If they’re fixed in a future release, so much the better.
Bogus “Avast has detected a Virus in the operating memory” warning dialog after I did a Quick Scan. I wouldn’t call this minor. I heeded the warning and immediately did a boot scan, which took two hours and found only the eicar test files. Later I discovered this is a known bug. Over two hours of my time wasted. I’ll ignore the warning from now on. http://forum.avast.com/index.php?topic=53787.0
The Avast main window keeps resizing itself to the full height of the screen after I click on one of its selections. It doesn’t always happen right away, and I haven’t been able to narrow the trigger down to any particular selection. I can live with this. I remember that I did resize it up to full screen height on purpose for a while after first installation. I wanted to see everything without scrolling. The window seems to be remembering my initial preference. Problem is it expands itself even when I don’t need it too. Workaround: ignore it as a minor annoyance.
I added the full pathname of an executable I wanted to exclude in the Settings > Exclusions dialog. Although the documentation says the exclusion includes the real-time shields, the executable is still stopped by the File System Shield.
Workaround: Added the exact same pathname to the File System Shield Expert settings. I can now use that program.
I updated to 5 from 4.8 and had no problem on my Vista laptop.I updated the programme version first though to make sure that was up to date as someone once mentioned I believe that the programme update was to prepare for the new release.Then installed it over the top of 4.8.I have noticed in a few threads that failures seem to be happening more on those that are choosing custom installation.I may be wrong but I did not choose custom installation.
I hope everyone gets it sorted soon.Because to me the new version is a Lean Mean Flying Computer Machine.
I have to say yes, it was sooner than I expected. There are some things that aren’t smooth/fixed yet.
Program upgrade from v4 to v5 has some issues
BSODs
Sandbox issues
Wrong Boot Time Scan prompts
Misaligned buttons in sliding popups (buttons are too close to the edge). From what I know, this issue is not in the previous builds
Sometimes, shields will not turn on and requires reboot or worse, repair
Sometimes, Attention in tray icon is still displayed even though all shields, updates, etc are fine. This occurs after the duration I set avast to be disabled passed and avast is active again
Removable media scan does not all removable media (some are skipped)
I think that old adage applies Bob.You can please some of the people all of the time,all of the people some of the time.But you can’t please all of the people all of the time. ;D
Ok guys, I suspected when I posted this it would tend to polarize replies between Avast longtime users and newer users. I personally have been using Avast 4 free for a number of years without any problems and was delighted to join this Forum on Avast 5 beta testing. My point was and is simply that it was being rushed into final release too soon, given reported conflicts with Malwarebytes Pro ( me ), PowerDVD, erratic broadband connections / speeds, BSOD’s, failing to update virus defs, having to go into safe mode for some actions, not recognizing registration details, fresh install / install over prev version indecision. I personally think it is also unaccceptable to ask users of Avast 5 free to uninstall other previously installed products from other developers to avoid conflicts with Avast, as this seems to me to be a back to front workaround.
Good synopsis enddays, and I would like to whole heartly AGREE with your statement. I also had used Avast for years since it was the only one that could clear a specific worm for me years ago. This release just came to fast, but I have all the Faith they will fix the problems and we will have a new machine to combat viruses
I personally think it is also unaccceptable to ask users of Avast 5 free to uninstall other previously installed products from other developers to avoid conflicts with Avast, as this seems to me to be a back to front workaround.
I don't know which program you're referring to but, that practice is something Microsoft has done for years.
??? Yes. I’ve asked when the next beta release(s) would be but I don’t remember testifying for releasing it. Changing topic, it is probable to have an update soon. Hope it fixes the issues.
so what ? do a bit a search and find out that it’s a normal behavior. That’s what safe mode is for, troubleshooting Windows, drivers are disabled etc…and you probably logged in in safe mode with network disabled too, so having the AV off is no big deal ;D
That as has been said is the whole point of safe mode, if you have a problem and it is driver related, the last thing you want is for it to be carried over to safe mode, you wouldn’t be able to resolve it. You should be able to start avast in safe mode though to do a scan by using the avast5 desktop shortcut I believe.
Though the big question has to be why are you in safe mode in the first place, what is it that you wanted to do that required safe mode ?
Not sure if Avast! is to blame, but I have been receiving several BSODs since upgrading to the recent 5.0.377 build. I’ve however that this error only seems to occur while running IE8. I’ve temporarily switched to Google Chrome to see if this resolves the problem. So far there’s been no problems while running Chrome. I will reinstall IE8 and see if the problem persists… what do you guys think about this? ???
Problem is it expands itself even when I don’t need it too. Workaround: ignore it as a minor annoyance.