Have tried several times to update to version 4.8.1229 clean install, but still get version 4.8.1227. This has never happened before. Could somebody please tell me what I should do.
Thanks !!
birka1
Have tried several times to update to version 4.8.1229 clean install, but still get version 4.8.1227. This has never happened before. Could somebody please tell me what I should do.
Thanks !!
birka1
Hi…
By clean install, you mean that you installed from scratch after uninstalling the previous version?
Best Regards…
Hi ardvark …
That’s exactly what I mean. Uninstalled v. 4.8.1227, then tried to install v. 4.8.1229. But I still get v. 4.8.1227 when I check properties ashAvast.exe.
Hi…
Hmm. Not sure why this is happening, unless vlk or igor can explain. ???
You could try uninstalling using the uninstall utility and/or installing a fresh copy from another download source. This is the only thing I know to recommend in this case.
Best Regards…
Have already tried that ardvark. I can’t explain it either.
Thanks for getting back to me.
Regards !
birka1
This is by design. ashAvast.exe hasn’t changed in avast version 4.8.1229, so its version number (inside the file’s properties) still shows 1227.
The only file that changed in build 1229 is ashWebSv.exe (the WebShield module).
Cheers
Vlk
Thanks vlk, I had no idea.
Best Regards…
Quote from Vlk
This is by design. ashAvast.exe hasn't changed in avast version 4.8.1229, so its version number (inside the file's properties) still shows 1227.The only file that changed in build 1229 is ashWebSv.exe (the WebShield module).
Cheers
Vlk
Thanks so very much for clarifying that Vlk. That totally explains why ashAvast.exe still shows as 1227. Terrific I have the correct version.
Best regards !!
birka1
The correct place to check what version you have is about avast, right click the avast ‘a’ icon, select about avast.
Ok will do that from now on DavidR . Thank you so much for all the replies !!
Best Regards
birka1
You’re welcome.
It wasn’t a chastisement just that about avast doesn’t suffer from the issue that you experienced, one file having not changed retaining the last build number.