How to stop Avast to offer the 5.1.x

When I start my computer Avast offers me the new software update. How can I stop Avast to do that? When I check the “Download the program updates manually” option Avast doesn’t offer me the updates of 5.0.x. Is there any way to get Avast to update only to possible future 5.0.x updates, but not 5.1.x? The reason, why I don’t want to update to 5.1.x yet is it, that there’s lot of problems with USB devices with 5.1.x.

that there's lot of problems with USB devices with 5.1.x.
i think that is fixed in latest 5.1. version

see reply #59 http://forum.avast.com/index.php?topic=69305.msg582489#msg582489

There will be on other 5.0 updates (5.0.677 being the last), all future updates will be for the 5.1 stream until the next major program update after 5.1.

No there aren’t a lot of USB problems or these forums would be on fire with them, you have to take account that this is a support forum and you are hardly likely to see those with no problems posting. I have had no USB issues with XP Pro or win7 starter 32bit.

There is only one “stream” of avast! updates - basically, the build number (i.e. 677 or 889) is what really marks the version, whatever is before that (5.0, 5.1, 6.0) is just a piece of text shown in the program interface.
[OK, let’s forget about avast! 4.x now - that was a second, parallel stream… which is why it wasn’t possible to update directly from 4.8 to 5.0, but an uninstallation was needed - but there won’t be any update to 4.8 either]

So there certainly won’t be any “future 5.0 update” (and for that matter, there probably won’t be any future 5.1 update either, the next one will most likely be 6.0.something).

If there appears a security hole in 5.0.x will there be a security patch for 5.0.x? I have understood, that 5.0.x will be supported at least for a year.

It seems you don’t understand that 5.0 and 5.1 are not different antivirus versions(something like avast 4 and 5), in fact it’s the same version with a different build number at the end, so if there will be a security hole they will release a new build (let’s say we’re at the build 5.1.999) so the new build will be 5.2.xxx , so in fact 5.0 and 5.1 are the same avast versions with a diferent build number, and that’s all.

Well, hope you get what i mean, as i don’t know a better and more clear way to explain it to you.

You might think of 5.1.889 as a security patch for 5.0.677, if you wish (even though I’m not saying there actually was any security problem in 5.0.677).