Avast 17.2.2288 is available from the GUI :
Avast - Settings - Update - Program - Update
Greetz, Red.
Thanks Red, more here: https://forum.avast.com/index.php?topic=197955.0
What is the build number on this release ?
I hate it when they don’t change the version number from that of the last beta, it causes confusion and really isn’t necessary.
17.2.2288
Yep sorry, a typo :-[
Greetz, Red.
That isn’t the build number it is the version number.
EDIT: They haven’t even changed the build number (17.2.3419.0) according to the downloaded files.avast.com/iavs9x/avast_free_antivirus_setup_offline.exe file.
So the version number and the build number are identical to the last beta version.
This begs the question what happened to the known issues in the beta release and any other bugs reported ?
EDIT2: These known issues in the last beta don’t appear in the Fixed items of the identical ‘new’ release.
- Cleanup sometimes doesn’t finish optimizing registry
- It’s not possible to remove browser extensions when protector is active
The build number really just adds to the confusion since it changes every micro-update etc.
Users should really just be concerned with the version numbers.
Here you go: 17.2.3419.0
Which is what I said, these are identical no different from the last beta, previously it was stated version number won’t change but the build number did to represent any changes.
See images, 1. taken 2017-2-25 and 2. taken minutes ago after running the off-line installer.
The only difference is the vps version.
I know Dave, don’t shoot the messenger. 
If it does record every micro update, then they really can’t be identical as I have found. I have been banging my head against this brick wall from the time avast started delivering a regular release version with the same version as the beta as it causes confusion. Avast came back with that is why we use the build number.
They can’t really have it both ways as there is no way to differentiate, as we have the version and build numbers the exact same as the last beta version. That shouldn’t be possible if micro updates are recorded.
Well, I did ask a similar question previously regarding why the build number was needed since users were confusing it with new versions.
Reply from Avast team
Version numbers are important for all users, build numbers usually for advanced users, avast developers and our support team. Every big software companies use it (look at Microsoft and their Windows 10 Insider builds). I don’t feel it is quite confusing, it is just 3 numbers. All our internal systems use these build numbers to track micro-updates, release patches, etc. etc.
Which is why I have raised this point, how can a beta release (with known issues) move to a regular release with the same version and build number - with no build number increments - effectively saying there were zero updates from the last beta.