*** INTRODUCING: New pre-release build of avast [NOW 5.0.504] ***

[Zyndstoff (aka Steven Gail)]

Frankly spoken: I don't know, as nobody really knows. I assume that it searches for some non-standard registry entries and deletes them and forces an uninstall in case the normal uninstall can't be done due to locked files (just a guess).

Good to hear it worked for you.

Have fun. 

[avast fan]

Just updated from 499 to 504 and so far things are looking great on my windows 7 home premium x86,Thanx again Alwil Team!!

[XMAS]

I've updated to the latest beta 5.0.504 and I still got the GUI crashes  :'(
I'm using Win 7 Ultimate x64. The crashes appear when I use the quick scanner to scan a folder from the context menu. Here' what happens - I can reproduce that every time:
1 - the scanning of the folder begins
2 - when the scan is completed and there is a virus found the result window appear automatically
3 - when I close the result window the GUI process crash.

[Zyndstoff (aka Steven Gail)]

The screenshot shows Avast Version 5.0.498.
Looks like you did not update successfully.

I'd recommend an unistall / reinstall of 5.0.504.

[Hermite15]

The screenshot shows Avast Version 5.0.498.
Looks like you did not update successfully.

I'd recommend an unistall / reinstall of 5.0.504.

498 there was 492, and then 499...where does that 498 come from (may be people running 462 got an 498 upgrade...)

[XMAS]

The screenshot shows Avast Version 5.0.498.
Looks like you did not update successfully.

I'd recommend an unistall / reinstall of 5.0.504.

Yes, I saw that, but the update was successful according to the program updater. Also I've noticed that sometime the program components have different version numbers. Thats why I decided to report the problem.

[Zyndstoff (aka Steven Gail)]

No, they didn't - at least I didn't.

I saw that funny 498 in some other post already. Don't know what it is, where it comes from... That's why I recommended installation from scratch.

[XMAS]

No, they didn't - at least I didn't.

I saw that funny 498 in some other post already. Don't know what it is, where it comes from... That's why I recommended installation from scratch.

Let's see what Alwil will say about that

[Hermite15]

yeah I just checked on another laptop running 462 and there's no upgrade to 498 offered

[Asyn]

No, they didn't - at least I didn't.
I saw that funny 498 in some other post already. Don't know what it is, where it comes from... That's why I recommended installation from scratch.

Yes, we already ran into this...
Read here, what DavidR posted:
http://forum.avast.com/index.php?topic=58183.msg492813#msg492813
asyn

[Yandros]

I think the 498 thing is a red herring...I think it's just that a version number that hasn't been updated.  In my case I DEFINITELY had 499 (ie I deinstalled and safe mode cleaned 462 before reinstall), but the faulting exe was showing as 498.

Note as well that my bug was fixed in 504, so had nothing to do with the '498' side issue.  

[Asyn]

Woohoo! problem solved   
Thanks for the heads-up Asyn. 

No problem, glad to hear it's solved...
asyn

[XMAS]

I've just updated to version 5.0.507 and the crash is gone. But just one question - is this the final version or it's still a test ?

EDIT: after checking I confirm that this is an official final version 

[Vock]

Also just found that version 5.0.507 is out - but Avast did not notify me to update from version 5.0.504! It still showed version 5.0.504 as actual and up-to-date and I found only by coincidence that a new version (and not a pre-release) is available. So something seems to have gone wrong with the version 5.0.504 with identifying a new version - I hope this is not a new bug which also remains in version 5.0.507; otherwise many people would not recognize new versions.

[bong2x]

yes im updated

the fastest dial up update from 462 to 507

and i notice that the system files in the chest that 4.8 remain is gone too.

thank you!!!