Problem with UPDATE 071103-0

[oldman]

I tend to agree with DavidR with 1 more reason. Whenever I had a forced up program update go south, and tried to revert back to a previous version, as soon as the vps updated, the new program version came with it. Same problem.

After a couple of tries, I clued in to the fact that it wasn't the version that was a problem, but that the update failed.

Following the steps in DavidR post should resolve this.

[Rick F]

I would say it is a better option to do a clean install of the latest version of avast rather than to install the older version. If you install the 1043 version if all is well you won't know why the problem occurred, by doing a clean install of 1074 and all goes well it is likely to have been a problem with the program update rather than anything to do with the VPS update.

Yep, I think David is right.  Scratch my suggestion.  You won't know what actually caused your problem if you fall back to the prior version... and then it might happen again.

[Lisandro]

I would say it is a better option to do a clean install of the latest version of avast rather than to install the older version.

I follow this.
No problems with latests versions of avast and virus database on Vista 32bits.

[58DaDude]

After reinstalling Avast build number
  4.7.1073
the Standard Shield Issue discussed in this thread has been cleared up
and all is back to Normal as it was before the program updated to
 build number  4.7.1074

Avast Standard Shield are now allowing any & all of the  programs on
my Vista 32 bit Home Premium machine to be opened once again

It will be interesting to see if the problem reoccurs after the
program is updated again to build   4.7.1074
 
Unfortunately I didn't see the suggestions
to do a clean install of build
4.7.1074

But however I did do a clean install of build 4.7.1073

Should the Standard Shield problem reappear
after the program updates again to build 4.7.1074

 I shall post back