Hi all.
Same problem for me under W7.
Yes I got the IE10 critical update notification also, but windows update doesn’t show an update for IE10, mine is for win7 32bit, so I don’t know if this is the same for 64bit OS versions.
As miguelgrado said:
“It seems a bug of microsoft and not avast .in internet explorer -about is correct version but not in properties of file”
The problem is that this mismatch within IE10 build number info makes the avast software updater believe there is a later version available.
Just now I wrote about the IE10 via Microsoft Answers Forum. I hope to get a reply soon or later.
I found miguelgrado’s comment fascinating:
if you go to the IExpolore.exe file itself, and right-click on Properties > Details, one sees that the file & product version listed there is indeed 10.0.9200.16611
yet despite this, when one runs IE and clicks on Help > About Internet Explorer, we are told that the version we’re running is 10.0.9200.16618
In other words, there’s an inconsistency in the information reported by Microsoft. And based on the first result, that may explain why avast is allegedly finding that particular “old” version.
So is it a Microsoft reporting issue? Or an avast analysis issue? — since this just started happening yesterday I can’t definitively place the blame here.
As noted above, today’s definitions 13 06 18 - 0 have NOT changed/fixed anything.
Suffice it to say: We should do nothing now to “fix” IE. Just sit back. Relax. Take no action. And wait until the powers-that-be realize what’s happening, and correct it.
Uh… this is very interesting! The avast! software updater issue with IE10 is gone after manual updating my vps to 130618-3. I did a manual scan of avast! software updater and it reports software health: Good as mentioned from avast! software updater as follows:
Internet Explorer
Microsoft Corporation (up-to-date)
Local version: 10.0.9200.16611
New version: 10.0.9200.16576
My IE10 version is 10.0.9200.16618 and is up-to-date
Well avast! once they are aware of it, could well remove that IE10 update entry from the software updater database.
The VPS update does more than just update the virus definitions, it updates the malicious sites list used by the network shield and also the software updater database.
This being a workaround to the incorrect version number in the iexplore.exe file properties, which hopefully should resolve itself when the next IE update happens if MS have the correct version number in the iexplore.exe file properties.
Well avast! once they are aware of it, could well remove that IE10 update entry from the software updater database.
The VPS update does more than just update the virus definitions, it updates the malicious sites list used by the network shield and also the software updater database.
This being a workaround to the incorrect version number in the iexplore.exe file properties, which hopefully should resolve itself when the next IE update happens if MS have the correct version number in the iexplore.exe file properties.
[/quote]
WOW!!! I didn’t know vps does more than just update the virus definitions ;D. Glad to know it’s all fine now… Before I thought it was a MS bug in IE10. Local version number mentioned in avast! software updater is same as in the iexplore.exe file properties My computer>C>Program Files(x86)>Internet Explorer>iexplore.exe. Right click iexplore.exe click on properties and click on details. ;D
It is an MS bug, this is avast doing a workaround to prevent the software updater constantly flagging it as out of date.
Oh really!!! Good on avast. Yeah hopefully soon MS comes up with an IE10 update.
Well it isn’t really that serious as the about IE shows the correct version.
As sure as eggs are eggs there will probably be a cumulative IE update on the Next Patch Tuesday. I can’t recall many months going by without a windows update IE update.
Everything is working for me as well. Great job Avast Team.
Avast must have fixed this issue; as of this morning Internet Explorer shows it is up to date and everything is working properly!
Previous posts state what has been done to get around this.
Avast haven’t fixed it, that is down to Microsoft to have the correct IE version number in the iexplore.exe file properties. All avast has done is make a modification to the software updater database not to flag this MS error as requiring an update.
Avast just updated for me. I went to check the updater and everything seems to be working fine now. Thanks Avast team. ;D
Hi all.
See the screen shots attachments.
Thanks
@ GaAs
Have you got the latest avast virus definitions as the IE issue was resolved a couple of days ago on the 19th of June 2013.
I can’t speak for the other anomalies, but the one for IE was resolved, which presumably means your virus definitions aren’t up to date and that may account for the other anomalies also.
updates shows BUONO which is good
AVAST is papering over a Microsoft version number problem
not to worry especially when Windows update shows nothing available