Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: emteec on June 18, 2013, 12:04:28 AM
-
Why does Software Updater think the local version of IE is 10.0.9200.16611, when according to IE itself I have the latest update 10.0.9200.16618?
-
idem in vps 131706-02 have been set to the reverse in updating the local version and the new version ;D
-
same issue here. maybe a bug from a database update?
-
same issue, running win7 64bit
-
I'd say this is a "bug" --- or "false positive". I would NOT act upon it... just wait-it-out.
As best as I can tell, this occurs with database 13-06-17-2... it wasn't happening before this.
-
I am having the same issue that Emteec is having?
According to ky331 "As best as I can tell, this occurs with database 13-06-17-2... it wasn't happening before this". I agree to that as a "bug" or a "false positive". Prior to having database 130617-2, I didn't check my software updater relating to the IE10, but I do think this is a bug or a false positive.
-
"Prior to having database 130617-2, I didn't check my software updater relating to the IE10..."
In fact, I received a pop-up message from avast alleging that my system's security was "critical"... and THAT'S when I ran the software updater to see what it thought was happening. On that basis (of the pop-up warning), I am assuming it was not part of earlier updates, as I've been online quite a bit today.
-
Oh! I didn't get a pop-up message from avast telling my system's security was "critical". I normally do a manual software updater check everyday or once every week. So after I did a manual software updater check it showed me that my system's security as "critical" and then I found out that my IE10 is out-dated which in fact it is not as I checked my IE10 version number which is up-to-date.
It must be a bug or a false positive from software updater. Avast! team need to do something about this asap!
-
Add me to the list of people affected by the IE10 update false positive.
-
I also got this notification and my IE is up to date as well. This should be an easy fix. I hope it gets fixed soon.
-
I think it's fair to say that this "glitch" is impacting ALL users of IE 10 on Win7 x64... and perhaps other configurations as well. It is NOT a "one-person" issue.
-
Oh! I didn't get a pop-up message from avast telling my system's security was "critical". I normally do a manual software updater check everyday or once every week. So after I did a manual software updater check it showed me that my system's security as "critical" and then I found out that my IE10 is out-dated which in fact it is not as I checked my IE10 version number which is up-to-date.
It must be a bug or a false positive from software updater. Avast! team need to do something about this asap!
Would it be helpful to send this issue to virus at avast dot com just as a issue to be addressed and sending a screenshot along with it? :)
-
Its a bug people come on. Not that hard to figure out. If you run Windows Update and there are no updates to IE then its obvious Avast has an issue. Relax. ::)
-
Just got the same "critical" toaster from Software Updater re IE 10 version update needed 10.0.9200.1611 to 10.0.9200.1618. As I have double-checked the validity of the alert using other installed programs, and also Google, and found nothing amiss, have to put this down to a possible erroneous vps update by avast!
I would not do anything with this alert and wait a couple of days to see if anything changes with new vps's coming in later on. No new out-of-band patches for IE 10 have been issued today or in the last few days, and all security updates were released on June 11, 2013 by Microsoft.
Secunia PSI is not yet reporting a critical update for IE 10, and here, as in Software Updater, the .exe is reported as 10.0.9200.1611, but no update is called for or needed. If PSI confirms version .1618 is indeed missing, then and only then would I apply the sub_version update. As Software Updater is still a newer program, I'd wait for Secunia to alert and use that to update IE before I used SU.
All Microsoft Updates were applied successfully on Microsoft Tuesday when they came in.
-
Same Problem for me under Windows 8!
-
It seems a bug of microsoft and not avast .in internet explorer -about is correct version but not in properties of file
-
Hey guys,
I don't think this problem don't have anything to do with vps update. Just now I received a vps update 130618-0. Still the same problem is happening with Software Updater detecting IE10 out-of-date as we all have up-to-date IE10 for users with Windows 7 and Windows 8. As for false positive, I don't think so. I think it's a bug in Software Updater in Avast! programs. I think Avast! team should release an program update for all avast! programs to fix this issue.
-
It seems a bug of microsoft and not avast .in internet explorer -about is correct version but not in properties of file
Yeah I have that too, but when you open up IE10 and at the top right hand corner you see a screw icon and you click on the screw button and click on "About Internet Explorer" and the version says 10.0.9200.16618. On the software updater the local version for IE10 says 10.0.9200.1611 and the new version says 10.0.9200.16618.
-
I guess avast updater software detects the version in file properties binaries and therefore cannot be fixed by avast .have be microsoft who to solve it
-
Uh... I think I have to agree with you. MSE (Microsoft Security Essentials) once had that similar problem incorrectly detecting file properties binaries and correct version. I can't remember exactly.... I will go to Microsoft answers forum and see what they say about this issue.
-
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
-
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.
-
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