Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: nedo78 on February 27, 2017, 11:48:29 AM
-
Hello,
I have an unexpected behavior on XP Mode (that is virtual Windows XP running on Windows 7) with Avast Free 17.
This unexpected behavior is apparently related to which wired connection I use to connect to the web from my notebook.
With Avast Free 12 everything was just fine since August 2016 when Avast Free 12 was released. Meaning, Avast Free 12 was regularly updating the definition files on my XP Mode independently on which wired connection I used to connect to the web (as I would expect it to do). And the definitions are still correctly updated right now with Avast Free 12 if I simply don't update it to the new version 17.
After updating (via the corresponding button in the "Update" section of the settings) Avast Free 12 to Avast Free 17 on XP Mode (so with no other changes on both XP Mode and Windows 7), I have that Avast Free 17 is able to update the definitions only from one wired connection I use to connect to the web and not another one.
I stress again that with Avast Free 12 all has been perfectly fine since its release date (and still now) and I am able to correctly update the definitions independently on the wired connection I use to connect to the web.
With the "wrong" wired connection Avast Free 17 seems to get first stuck while downloading servers.def.vpx for which I get an unknown error (as such it is classified by Avast Free 17).
In addition to using the corresponding button in the "Update" section of the settings of Avast Free 12, I also tried a full uninstall of Avast Free 12 by means of avastclear.exe run in safe mode and a following fresh install of Avast Free 17 by means of avast_free_antivirus_setup_offline.exe but the results are the same: Avast Free 17 on my XP Mode is able to update the definitions only from one wired connection I use to connect to the web and not another one (again: with Avast Free 12 all has been fine, and still is fine as of today, since Avast Free 12 was released in 2016 and the definitions are correctly updated independently from which of those two same wired connections I use to connect to the web).
Can you help me solving this issue and have Avast Free 17 updating definitions independently from which wired connection I use to connect to the web like it used to happen, and like it still happens, with Avast Free 12?
If a log files from Avast Free will be needed, could you also provide details on how to obtain those log files?
Thank you
Best Regards
-
Could my problem be related to this one?
https://forum.avast.com/index.php?topic=162445.msg1372338#msg1372338
later on I'll give it a go to see if turning off Avast's "Enable Hardware-Assisted Virtualization" will help my case and post back here.
-
Could my problem be related to this one?
https://forum.avast.com/index.php?topic=162445.msg1372338#msg1372338 (https://forum.avast.com/index.php?topic=162445.msg1372338#msg1372338)
later on I'll give it a go to see if turning off Avast's "Enable Hardware-Assisted Virtualization" will help my case and post back here.
The easiest way to check is to try it. :)
-
No, turning off Avast's "Enable Hardware-Assisted Virtualization" didn't help at all my case.
Now I'll give it a go to the new Avast Free 17.2.2288 to see if it gets any better with respect to previous/first version of Avast Free 17 (the one not properly working in my hands).
-
Updating (via the corresponding button in the "Update" section of the settings) Avast Free 12 to the latest Avast Free 17 (that is 17.2.2288) from the "wrong" wired connection gets first stuck at the same point I mentioned before regarding definitions update: while downloading servers.def.vpx for which I get an unknown error (as such it is classified by Avast Free).
Can someone please help with this?
With Avast Free 12 all is OK while with the second release of Avast Free 17 I'm still having this problem...
-
Updating (via the corresponding button in the "Update" section of the settings) Avast Free 12 to the latest Avast Free 17 (that is 17.2.2288) from the "wrong" wired connection gets first stuck at the same point I mentioned before regarding definitions update: while downloading servers.def.vpx for which I get an unknown error (as such it is classified by Avast Free).
Can someone please help with this?
With Avast Free 12 all is OK while with the second release of Avast Free 17 I'm still having this problem...
Clean Install of Avast:
https://goo.gl/4Ptzkf
-
As I initially mentioned, I already tried a clean install while passing from Avast Free 12 to Avast Free 17.1.2286 and, from the "wrong connection" (again, see above for the details), it didn't work.
Sure, I'll try a clean install (and post back here) also for passing from Avast Free 12 to Avast Free 17.2.2288 but I suspect it won't work since I would expect that if everything was OK with Avast Free 17 the update should work seamlessly directly via the corresponding button in the "Update" section of the settings without having a single problem in downloading the servers.def.vpx and others file in the first place, independently on which wired connection I use to connect to the web (like it correctly still happens right now for Avast Free 12).
BTW The "Enable Hardware-Assisted Virtualization" disappeared from Avast Free 12 in my hands (both on XP Mode and true XP) in the last few days; I guess this was done via definitions update...
-
Clean install did not work even with the latest Avast Free 17.2.2288 release.
Summarizing, on my XP Mode I have these two situations:
- When using wired connection 1: Avast Free 12 correctly updates its definitions; I can correctly update Avast Free 12 to the latest Avast Free 17 either via the corresponding button in the "Update" section of the settings or via a clean install; once installed Avast Free 17 correctly updates its definitions.
- When using wired connection 2: Avast Free 12 correctly updates its definitions; all the other stuff mentioned in the previous point fails apparently due to inability to download files required for those processes (see my example for the unknown error of servers.def.vpx).
Still not able to properly take advantage of the latest Avast Free...
-
nedo78 - I am having a very, very similar problem. In my XP Mode on Win Pro, I am unable to install Avast AV Free 17 because the online installer is not connecting to the Avast servers. The same servers.def.vpx don't connect.
I just posted about this. Go to https://forum.avast.com/index.php?topic=198863.0 (https://forum.avast.com/index.php?topic=198863.0) to see the complete error log generated by the Avast online installer.
Unlike you, I have only one router connected to my Win 7 Pro host (wired). I don't have another connection option.
And, before, Avast was working fine in XP Mode.
This one is weird, man.
-
Everyone - where can I get a full off-line download of the PREVIOUS issue of Avast Free? I think it was 12 ??
That one worked (and updated its definitions) in my XP Mode without the problems nedo78 and I are having with 17.
Reminder that I will be installing it in XP Mode, which is 32-bit.
Thanks.
-
Thanks to Mr. Bone in another thread - I have successfully downloaded and installed Avast AV Free 12 in my XP Mode, was able to update definitions ONLY, and it's now running a boot-time scan.
Proof positive that Avast 17 is faulty.
Many thanks to all for suggestions !!! Avast 17 still needs to be fixed.
-
Thanks to Mr. Bone in another thread - I have successfully downloaded and installed Avast AV Free 12 in my XP Mode, was able to update definitions ONLY, and it's now running a boot-time scan.
Proof positive that Avast 17 is faulty.
Many thanks to all for suggestions !!! Avast 17 still needs to be fixed.
Incorrect statement. Since the latest version works on other XP systems, it can hardly be considered faulty.
What may be faulty is to continue to expect Avast to continue a product that hasn't been supported by MS for a very long time.
The model T no longer has parts available directly from Ford.
-
Bob - Good morning.
Please take a look at this entire thread from nedo. Come on - it's XP's fault?
By the way, many of us with XP continue to get updates via the POS hack. I'm sure many POS machines still use Avast as protection as well. Avast just made some kind of extra-bizarre mistake in version 17 and on its servers and, not for the first time, will have to fix it.
-
Totally agree with you, glnz.
-
Avast Free 17.3.2291 doesn't change a single thing in what I reported above.
I guess Avast guys could do much better here.
-
Just like version 17.4.2294 and all the previous 17.x versions, also the recent Avast Free Antivirus 17.5.2302 encounters unknown errors while downloading servers.def.vpx and prod-pgm.vpx (the list is not complete; those two files are the ones I was able to notice but I cannot say for sure that there weren't others).
I really don't understand why apparently Avast developers cannot fix this problem which to a non-expert like me has something to do with their servers and the way Windows XP connects to them to retrieve those files (see this thread in full for details).
-
Change the DNS to the one from Google and all should work.
-
Sure, that works (and thanks for that Eddie).
But it is highly sub-optimal.
With Google DNSs Avast Free 12 nicely upgraded to Avast Free 17 but then one has to stick to Google DNSs otherwise the software won't get the regular definitions update.
There was no need to specify a certain DNS with respect to the default ones offered by my ISP (like for instance 81.139.56.100 and 81.139.57.100) while I nicely passed from Avast Free 11 to Avast Free 12 a while ago.
I have no need to stick to Google DNSs with respect to the ones provided by default by my ISP.
I would say that Avast developers should fix this and allow the default DNSs provided by ISPs to be again OK with their Avast Free 17 (and future releases) as it was before.
-
When it come to this, avast doesn't have to fix anything in their software.
The problem is with the (DNS) servers, not with the av.
-
Come on mate.
I guess you can get what I wrote above. It's summarized below.
Whatever the tech blunder and whose fault is:
- Avast Free 17 has this problem with certain DNSs from certains ISPs while previous version didn't have this problem
- Other A/V do not have this problem at all
...
-
Try checking: Use Nested Virtualization Where Available .. It is under Settings, Troubleshooting .. This may fix the issue as it is supposed to be used when working a Virtual Machine
-
Hi bruce_b,
no such "Use Nested Virtualization Where Available" setting available for me in 17.5.2302.
And the above one "Enable Hardware-Assisted Virtualization" didn't help either (see at the beginning of this thread).
As one can read above, my problem is that servers.def.vpx and prod-pgm.vpx (and I maybe other files as well) are not downloaded in the presence of DNS servers provided by default by certain ISPs.
Avast Free is the first case where I get this type of behavior...
In the same OS system (and all the other OSs which I use as well) all the other software is not picky at all with respect to the DNS servers provided by default by my ISP...
-
nedo - On my XP machine (which I keep updated with the POS hack), Avast is now at 17.5.2302. After one of Avast's recent sub-updates, in Troubleshooting, the recent "nested virtualization" subcategory under "Enable hardware-assisted virtualization" disappeared; there is now only "Enable hardware-assisted virtualization". So that is apparently normal for Avast on an XP machine.
(However, on my Win 7 Pro 64-bit machine, I still cannot turn on XP Mode unless I UNcheck "Enable hardware-assisted virtualization" in its Avast; that has never been fixed. This remains so even though the "nested virtualization" subcategory still exists in Win 7 under "Enable hardware-assisted virtualization" with both checked.)
I no longer have a problem getting Avast's updates on any machine. However, a long time ago, I programmed my router to use the OpenDNS IP addresses for DNS lookup. That's an added safety step that everyone should take. You might Google for "OpenDNS in router". I also run the OpenDNS Updater on my XP machine as a startup item.
Good luck.
-
See the screenshot I posted just above. I have the same 17.5.2302 Avast Free version and it is in there.
* * Just looked at my XP PRO SP3 computer and all it has is: "Enable Hardware Assisted Virtualization" * *
Perhaps you need to Uncheck it for it to work . . . The default is Checked (or enabled)
If not, then maybe someone from Avast with a bit more knowledge will chime in.
-
Just to complete this matrix:
On my XP machine, "Enable hardware-assisted virtualization" is checked, and I AM getting Avast updates. But, as I noted, my router uses the OpenDNS IP addresses for DNS lookup.
Avast should check that its DNS info has been widely disseminated to all ISPs, or whether there might be some man-in-the-middle attacks going on against Avast. This is a security issue for Avast itself - to make sure there are no DNS hijackings going on to its servers.
-
Hi glnz,
thanks for the info.
As said above I am perfectly able to do everything (that is upgrade Avast Free to the latest version and regularly receive definitions updates for it) by using the Google DNSs suggested by Eddy (and I guess the OpenDNS ones as well).
My point is I don't want to stick to DNSs others than the ones provided by default by my ISP.
Avast Free is the ONLY software SINCE EVER which would force me to do something like that (and I use/used a BUNCH of software which regularly gets/got online updates).
I really see no reason for changing the default DNSs provided by my default ISP.
I instead think Avast should fix this one.
Otherwise Avast should state somewhere in their OFFICIAL DOCUMENTATION that their A/V might not work with all the DNSs provided by default by some ISPs (while ALL the other software apparently does not have this limitation)...
Is something like that reported somewhere in their official docs?...
-
You would need to do a Tracert to the IP where Avast downloads it's definitions from. Then submit the report either to your ISP and perhaps also to Avast so they can see where the connection is failing. Once that is known, then they can fix it.
You can look at the file on your computer to see where in your part of the world Avast goes for the definitions.
server.def file contain the servers accessed by avast
-
Problem can be that the servers listed are changing constantly.
Better is to monitor the data traffic and check to what exact server avast is trying to connect when it tries to update/get a new VPS.
-
So why is it Avast Free 12 not affected by this, in the presence of exactly the same DNSs which block Avast Free 17 stuff?
-
When avast 12 was around (almost) no IPV6 was used.
-
If that is the case, the OP needs to check and see if his computer, router and ISP are supporting IPv6
He can test that with this link: http://test-ipv6.com/
-
Is that the case for sure?
Is Avast the ONLY one denying their software to users for that reason?
-
avast isn't denying their software to users at all.
To keep it really simple:
If the request is IPV4 and the server is set to only accept IPV6, there a problem.
The server will not understand what is asked.
And of course the other way around is the same.
It is like two people trying to talk to each other while each only speaks a language that the other don't understand.
-
Two different OSs (XP Mode and Win 7) tested on "connection 1" (the one that has no problems in downloading the files) and "connection 2" (the one has problems in downloading the files).
"connection 1" and "connection 2" provide EXACTLY the same results on http://test-ipv6.com/ ...
bruce_b, Eddy, my point currently still holds (despite it is clear that you don't like this): Avast simply needs to fix this one.
Instead forcing users to play with DNSs, routers, IPv4 vs. IPv6 and other stuff like that, Avast simply needs to provide software which works like all the other software do (and like it was in their version 12); that is WITHOUT tweaking ANY of that stuff...
-
You should be setting up your computers and routers for IPv6 anyway. IPv4 is going the way of the dinosaur and sooner or later you will need IPv6 enabled to get to a lot of web sites. There are not that many that use it yet, but if your hardware and ISP support it, you should enable it. I have it enabled on both my Dell Deminsion 8200 P4 1.8Ghz XP PRO SP3 and also on my Toshiab C855 series laptop with Windows 10 Home 64 Bit .. The test results from the IPv6 site I linked to above shows it is fully working through my ISP AT&T U-verse internet here in Apex, NC
-
Also the latest Avast Free 17.5.2303 doesn't let me properly complete the update procedure since servers.def.vpx and prod-pgm.vpx (and I guess also other files) are not downloaded with the default DNS servers provided by my ISP.
By this point in time (with version 17.1.2286 being released in February 2017) it's really surprising how much Avast does not care about this DNS thingy that they should properly handle.
-
I have the same problem with servers.def.vpx and prod-pgm.vpx are not downloaded. Is there any solution for this problem? I can't update Avast definitions during last month.