VLK and et all:
This is a very intriquing problem although it is simple to fix.
I have to admit that I am ashamed that I did not do what I normally do with a problem file....rename it. I would have been able to send you a copy. However, I do not believe that the files are the problem, nor AVAST.
This information may help. In examining the 3 files on my XP system, I did notice that the older files were version 7.0.9447.0 dated 2001 which is the date when my laptop was purchased. It is my belief that the files were OE installs. Furthermore, I have found that for some unknown reason, MS likes to attach "read only" status to files in the Runtime Library to protect them.
Bah! hahaha
None of the files on my computer are BETA. These would have to be voluntarily downloaded which I do not do often unless testing a program in a contained environment.
The repair was simple...very simple....
It did not require copying over, or deleting, or removing reboot.txt or anything like that. Users should not try to do anything with the registry either. It is not necessary in this case. Extreme measures will usually bring about extreme results....some unwanted!
In one of the posts, Yildi brought up the attribute status.
If the Read Only is removed from the 3 files, AVAST has no trouble replacing the older files with the newer 7.0.9466.0
The only way to rectify this automatically would be to have Avast "exit" Windows, enter Dos and start a batch exe file to check attribute, remove attribute, set files and then exit back to windows.
This is not only excess work, but I do not like to hand over control of my operating system in Dos mode to another program.
At this point, making users aware of the simple corrective measure is the best course of action.
Another post by Nexus mentioned the Microsoft.Net framework update. This is not a BETA release. Updating MAY even correct the file problem. Since MS won't comment on this.....it is kind of up to us to see where this goes.
I do believe in using the MS Windows Update often but only download and install those programs that are relevant. Just because MS "recommends" doesn't mean that I "need" !
It is extremely difficult for a software vendor to anticipate any and all events that might occur between their program and others.
It is our task as AVAST afficianados to do what they cannot!
LONG LIVE AVAST AND THE PEOPLE WHO SUPPORT IT!!
Sorry for the long post. It takes a bit of time sometimes to get my thoughts out.